|
The Job Report System (JRS) of CFS enables Enter jobs and DO procedures to be started and monitored.
In contrast to the /DO and /ENTER BS2000 commands, JRS offers the following additional facilities:
1) In addition to Enter files, DO procedures can also be started in batch mode. For DO procedures, JRS will create an Enter job which calls the DO procedure.
2) When running a DO procedure in Enter mode, the necessary parameters will first be analysed by JRS and can be supplied from a parameter mask.
3) JRS notifies the user following termination of the Enter job. The SYSOUT or SYSLST protocols, or any other specified file can be displayed, in addition to general status information concerning the job. If CFS is no longer loaded when the job terminates, the user will be notified the next time CFS is loaded from that same userid and account number. Notification of the termination of the job is performed regardless of whether the user is in the main CFS task or in a Connection.
4) CFS provides its own status command (STAJ) for displaying information about all Enter jobs and File Transfer requests being monitored by JRS.
5) If a /DO command is issued from within a Connection, JRS automatically performs the parameter analysis. A full screen parameter mask will be displayed if any parameters are missing. The user is thus presented with a formatted list of all parameters necessary for the procedure, and can provide the missing parameters before the job runs, although this is not obligatory. If the Connection is opened under another userid or on another system, this function is not available.
If the Connection was opened to a dialog task in another userid, JRS can be used to run DO procedures if they are shareable.
6) JRS can also be used to monitor Enter jobs that were not started under CFS. The user can be kept informed of any steps within the job. Any other events linked to a Job variable can also be monitored.
7) JRS can also monitor File Transfer requests started from CFS with a FT command.
The Job Report function is only available if the Job Variable software product is installed on the BS2000 system.
JRS Commands
DO procedures and Enter jobs can be started with JRS from files, LMS-ISAM libraries and PLAM libraries.
Start and Monitor Enter Jobs and DO Procedures
The 4 variants of the E (Enter) command and their syntax are first described, followed by the parameters of the E command.
Start Enter Job
E { enter-file | lib(element) } [ /enter-params | , ? ] [, JRF=jr-file]
Start DO procedure in Enter mode
E[N,] { DO procedure | lib(element) } [, DO-params | , ? ] [ / [ enter-params] [, JRF=jr-file] [, JN=jobname] ]
Start Enter job or DO procedure with predefined parameters
E[N,] %name | %? [, jrsave]
The parameters must have been saved previously with an SP (Save Params) command. The SP command can only be given in the command field of the parameter mask.
E Specifying the E command without any operands will cause the parameter mask to be displayed with the parameter values from the last DO procedure or Enter job already filled in.
Parameters:
N Suffixing the E command with N will suppress the parameter analysis for a DO procedure (see page 11-). All the required parameters must be specified in the E command.
enter-file Name of the Enter file to be started. This file must begin with a LOGON command and end with a LOGOFF command, or with the respective SDF commands. If a protocol listing (SYSOUT/SYSLST) is to be displayed after the termination of the job, the relevant SYSFILE SYSOUT or SYSFILE SYSLST command, or its respective SDF command must be inserted.
DO procedure Name of the DO procedure to be started in Enter mode. The DO procedure must begin with a PROC statement and end with an ENDP statement, or with the respective SDF commands. The necessary /SYSFILE SYSOUT and/SYSFILE SYSLST commands will be inserted by JRS when it creates the Enter file containing the CALL to the DO procedure.
lib(element) The Enter file or DO procedure is stored in the specified library element. In PLAM libraries, the element must be stored as a J-type element.
%name Name of the parameter set in the JRSAVE file. The parameter mask saved with SP %name will be presented to the Enter job. %name establishes a relationship between a DO procedure and a particular set of parameters (for further information see the description of the SP (Save Parameters) command on page 11-).
%? All relevant parameter sets will be displayed in a list, from which one may be selected by marking it.
jrsave JRSAVE file to be used. This name should only be specified if the parameter set is not stored in the standard JRSAVE file. The naming convention for the JRSAVE file is described in Chapter 27 "CFS Files and Job Variables" under the CFS.JRSAVE section.
DO-params Parameters for the DO procedure about to be started. The DO-params can be omitted if the DO procedure does not contain any parameters, or when all parameters have already been assigned using standard values, or when the user wishes to enter the values from the parameter mask. Parameters cannot be specified together with %name.
? Entering "?" instead of DO parameters will always display the parameter mask, even if all the parameters have been assigned, or even if the procedure does not have parameters.
/enter-params BS2000 Enter parameters. Any BS2000 Enter command parameters can be specified, e.g.TIME=nn,JOB-CLASS=xxxx,PRIORITY=nnn
If a valid Enter file should be started using JRS, then the slash in the E enter-file/enter-params command can be replaced with a comma to maintain compatibility with the BS2000 Enter command: E enter-file,enter-params.
The Enter parameters can also be predefined with the JREP command, or in the JRP mask. The predefined Enter parameters in the E command will replace the predefined parameters (on a keyword basis).
? Entering "?" instead of the parameters will cause a mask to be displayed containing the standard Enter parameters (see JREP command on page 11-), which can then be amended.
JRF= SYSOUT | SYSLST
{ file | *LIB(lib,element[(vers)] [,typ] } , SYSOUT | SYSLST | JRFILE]
If a library element has been specified (*LIB ...) without the type indicator, the element will be saved as Type P.
This optional JRF parameter determines the file to be displayed when the job terminates.
Normally, the job's SYSOUT file will be displayed. If nothing is specified, the name of the SYSOUT file or another JRFILE will be extracted from the Enter or DO procedure. JRS will scan the procedure file for the following statements: SYSFILE, ASSIGN-SYSOUT, ASSIGN-SYSLST or REMARK JRF=....
If a DO procedure is started as an Enter job, then, depending on the current JRF option, JRS will create the following files:
CFS.SYSOUT.tsn.hhmmss or
CFS.SYSLST.tsn.hhmmss
If a SYSLST protocol is specified, an "OPTION MSG=FH" will be generated in the Enter file.
Depending on the option specified in the JRSH command or in the JRP mask, the SYSOUT/SYSLST files will be cataloged as SHARE=YES or NO (standard: SHARE= NO). Specifying SHARE in the JRSH command has the advantage that the JR and STAJ commands will also be available to other userid's.
The JRF parameter can also be specified via a REMARK statement in the Enter file (/REMARK JRF=...).
JN=jobname one to eight character Job name for the Enter job to be started.
Testing the DO Procedure Parameters
If a DO procedure is started with an E command, this will first be validated by JRS detecting the PROC statement in the file to be started. Further plausibility checks will then be carried out. JRS will recognise, for example, when an expected parameter (positional or keyword) has not been provided (no specification via DO-params in the E command and no standard value in the PROC statement). In this case, the user will be presented with a mask of all the parameters, together with their current values. In addition to the parameter name, comments relating to the parameters will also be displayed in the mask (up to a length of 40 bytes).
Example: If the PROC statement contains a line such as: /&FILE=TEST, "Name of the file to be processed"-
then this DO parameter will be displayed as follows:
FILE Name of the file to be processed =TEST
If the comment begins with ":", then that comment will be displayed without the parameter name.
Example: If the PROC statement contains a line such as: /&FILE, ":Name of the file to be processed"-
then this DO parameter will be displayed as follows:
Name of the file to be processed :
Normally, one line per procedure parameter is reserved in the parameter mask. This means that only parameter values of less than 40 bytes may be entered. Specifying #n (n < 4) will reserve one to three additional input fields, each of 40 bytes, for a parameter. #n must appear after the first ", or ": .
Example: If the PROC statement contains a line such as: /&FILE=TEST, ":#3Name of the file to be processed"-
then this DO parameter will be displayed as follows:
Name of the file to be processed =TEST
:
:
:
#DU | :#DU #DU will turn the input field dark.
Example: /&PASSW=, ":#DULogon Password for Userid"-
:#- #- will prevent the parameter appearing in the mask.
Example: /&PASSW=C'ABC', ":#- Logon Password not in mask"-
Notes:
The comments for the procedure parameters can be used to make the parameter mask clearer and more informative.
Procedure parameters that were not supplied at all, or only partially supplied in the DO command can be supplied in the parameter mask. Entering E in the command field of the parameter mask will start the job.
Pressing the K1 key in the parameter mask will abort the E command, i.e. the Enter job will not be started.
Entering "?" at the DO or Enter parameter field will display the parameter mask. The command E DO-proc,? or E lib (element),? can also be used if the user is purely interested in seeing an overview of the positional and keyword parameters, and their current values. To avoid starting the Enter job in this case, K1 should be pressed. The predefined or user-modified contents of the parameter mask can be saved for future use with the SP command. Use E %name to activate these parameter values.
Example:
The DO procedure DO.COB contains the following PROC statement:
/PROC N,(&MODUL, - / &COLNAS=N, "#L1" - / &COLLIST=Y, "#L1" - / &COLCOB=Y, "#L1" - / &COBOLCOMPILER=Y, "#L1" - / &COLNUMC=Y, "#L1" - / &COBLIB=$COPLIB, "Cobol-COPY-Lib" - / &COBLIB1=$COPLIB, - / &COBLIB2=$COPLIB, - / ©CLIB1=$COPLIB, "Columbus-COPY-Lib" - / ©CLIB2=$COPLIB, - / &MODLIB=MODLIB, - / &COLLISTLISTE=, - / ),SUBDTA=&
After entering
E CFS.S.LMSLIB(ASSEMB)/TIME=40,JOB-CLASS=JCBALL
the following parameter mask will be displayed:
With a mouseclick you get a describtion of the screen item.
Positional parameters for the PROC statement are denoted by "=" in the parameter mask, and keyword parameters are denoted by "=" .
Entries in the Parameter Mask Command Field
+ | - Page forward or backward one screen.
++ | -- Position at the first/last screen.
Sending an empty command field with DUE1 will also scroll forward one screen.
A Abort the parameter analysis (same effect as pressing the K1 key).
/ Interrupt CFS and switch to operating system mode.
/cmd Execute BS2000 command.
STAJ Display the status of the jobs being monitored. See page 11-.
JR | NJR Activate / deactivate JRS . See page 11-.
JRP Set global JRS parameters. See page 11-.
Save Parameters. This command will save the current parameter mask under the specified name to a file CFS.JRSAVE [.jobname]. If the jrsave option was not specified, it will be saved to a file that has been assigned as follows: FILE file,LINK= JRSAVE. The naming convention for the JRSAVE file name is described in Chapter 27 "CFS Files and Job Variables" in the CFS.JRSAVE section.
%name The parameter set %name contains the DO parameter assignments, the name of the DO procedure, as well as any Enter parameters that may have been specified. If a /FILE file,LINK=JRSAVE command is executed, the parameter file to be used can be assigned by the user.
jrsave Name of the JRSAVE file. This name should only be specified if the parameters are stored in a file with a name that differs from the standard CFS JRSAVE name (see above).
Entering the command E %name will pass the parameter set stored under that name to the Enter job.
Entering the command DO %name in a Connection under the same userid will also display the parameter mask. DO %name can thus be used to run a previously saved DO procedure with a particular parameter set in dialog mode.
In Connections the user can also simply enter 'DO '. This will display the last DO procedure that was processed, together with the parameters last used (the last parameter mask is displayed).
E Start an ENTER job (or press the K3 key). Normally, the E will already be displayed in the command field if the user had specified the full commmand: E do-procedure, ...
The command E can also be given when starting DO procedures in Connections if the mask of the procedure covers many screens, and the user does not wish to page through to the last screen.
Display the Status of the Current Enter Jobs
The STAJ command can be entered in the CFS command line, in the Job Report parameter mask (E command), or in the Job Report mask (result or SYSOUT listing).
STAJ [$userid | jr-id | $user-id . jr-id]
jr-id This option will cause only the status of the specific job that was started under that Job Report ID to be displayed. See the JRID command on page 11-.
If no parameters are specified with the STAJ command, all jobs started under the standard JR-ID (= acct-nr or Job name) will be displayed, or those under a JR-ID whose monitoring had been explicitly activated using the JR command.
In some screen modes (TCHNG READ=U), or with some terminal emulations, it can happen that the screen contents are erased after displaying the STAJ information. This problem can normally be overcome by setting Task Switch 2 (/SETSW ON=2).
Examples:
STAJ
normally displays the status of all Enter jobs started from JRS under the same userid.
STAJ $XYZ
displays the status of all JR Enter jobs started or running under the userid XYZ.
The following information will be displayed for the Enter jobs as a result of the STAJ command:
TSN
Name of the Enter file / DO procedure / library(element)
DO parameter, Enter parameter
elapsed CPU time
Status information: Queue/Run/Term/Abort
Start time: age in days (0/1/...), Start time
Information provided by the STAJ Command:
TSN Job-File JRID: $user-id.xxxx CPU-used Status Age Time
4712 CFS.S.LMSLIB(ASSEMB),(CFSMAIN,IDA=NO,XRE 21.0037 Run JR 0 15:16:34
4726 CFS.PLAM2(ASS),(CEXIT0,VERS=080,IDA=YES, 11.2072 Run JR 0 15:23:42
4733 CFS.PLAM2(ENTER) 9.7786 Run JR 0 15:25:52
| | | | | | |
| {_________} | | | | |
| | | | | _____}
| | {_________________________________} | | |
| | | |
CPU time used
Enter Job was
| | | |
started n days
| | | |
ago at hh:mm:ss
| | {________________________________________} |
| | |
Status of the Enter Job
| | |
RUN: Job is active
| | |
QUEUE: Job is queued
| | |
TERM: Job has terminated
| | |
| | {____________________________________________}
| |
Monitor Status of the Enter Job
| |
JR: Monitoring enabled. The termination of the Job
| |
will be indicated to the user
| |
NJR: Monitoring disabled. The termination of the Job
| |
will not be indicated to the user
| | | | |
Name of the Enter file or DO procedure
|
and respective parameters
|
|
TSN of the Enter Job
The Job Report mask will be displayed when an Enter job started by the Job Report System has ended. Statistical information about the job, as well as the JR file (SYSOUT, SYSLST or any other file) will be displayed.
An example of the Job Report mask for a job which was started with an E command, and which has finished, is given below.
With a mouseclick you get a describtion of the screen item.
The Job Report mask contains a command field, similar to the field in the CFS file list. A number of commands can be entered here to scroll through the listing.
Possible Entries in the Job Report Mask Command Field
+ | - Scroll forward or backward by one screen (Standard: if nothing is entered, scroll forward towards the end of the listing).
+n | -n Scroll forward or backward by n records.
++ | -- Position at the beginning or end of the file.
DS | DL [DW] Display short / Display Long.
DS: Only the first 80 bytes of each record of the SYSOUT protocol is displayed.
DL (DW): Records longer than 80 bytes will wrap around to the next line (Standard).
A change to the DS/DL mode will remain in force until the end of the CFS session.
S,'string' Find and move to the first occurrence of the specified search string. If the string does not occur in the file, the cursor will be positioned at the beginning of the JR file. For a full description of the Search command syntax, see page 8-.
S Position the cursor at the next occurrence of the previously defined search string.
/cmd Execute a BS2000 command.
/ Switch to BS2000 command mode.
E | K1 End + Erase SYSOUT + ERAJV monjv.
The "inform user about the termination of the Enter job" transaction will be closed. If the JR file displays a SYSOUT protocol, this will be erased, or recataloged to a temporary file if the ERT mode is set. The Monitor Job variable is also erased. SYSLST and other JR files are not erased. For further information on the ERT mode, see page 18-.
Note:
If the user was processing a file in Format mode of EDT before displaying the Job Report mask, the original screen contents will normally have been overwritten by the Job Report mask. The original EDT screen can be restored by pressing the K3 key.
EP [x] End + Print. In addition to End, the contents of the JR file (SYSOUT, SYSLST, or any other file), are printed.
x Any variant of the Print Action Code can be specified for x .
Examples:
EPSE End + Print Space=E,Erase.
EPDnS End + Print on Device n, Space=E
For a full description of the P Action Code variants, see page 6-.
K End + Keep. The "inform user about the termination of the Enter job" transaction will be closed, but the SYSOUT protocol will not be erased.
KP [x] End + Keep + Print. In addition to Keep, the displayed JR file (SYSOUT, SYSLST, or any other file) will be printed.
x see above: Command EPx.
N No action. The display of the Job Report information will be aborted, but the "inform user about the termination of the Enter job" transaction will not be closed.
Entering N is only relevant if the mask displays information about a job that has not started, or if the display of the JR file is to be interrupted. This Job Report mask will be displayed again the next time CFS is loaded, or when the JR command is next executed. This mask will remain active until the user acknowledges it with K, E or by pressing the K1 key.
If the Job Report display is aborted with N, it will be re-displayed at the point at which it was interrupted the next time that same JR file is activated by a JR command.
The display of the JR file can thus be interrupted with an N command, and then resumed with a JR command.
Note:
Occasionally it can happen that a 0D9A DMS error occurs when trying to display the JR file in the Job Report mask. This can be overcome by pressing the DUE1 key, or by entering N (No Action) and then a JR command.
NP [x] No Action + Print. In addition to the No Action function, the displayed JR file (SYSOUT, SYSLST, or any other file) will be printed. This is analogous to the EP command, see above.
NJR | K3 No Job Report. Same as for N (No Action), but in addition, the Job Report masks for all other jobs already started will be suppressed.
STAJ [jr-id] Display the status of all Enter jobs started with an E command.
The following commands are also permitted in the Job Report mask:
JRP / JRF / JRIC / JREP / JRID / JRSH. A description of these can be found in the "Set Job Report Parameters" section on page 11-.
Monitoring Enter Jobs not started by CFS
The CFS Job Report System enables Jobs to be monitored which were not started with a CFS E command. The following three conditions must be fulfilled for the monitoring by CFS to take place:
1) The Enter jobs to be monitored must have been started with a Monitor Job variable. The name of the Monitor Job variable must be in the following format: CFS.JR.jrid.xxxx . jrid is the Job Report ID under which the job should be monitored. xxxx is a user-defined name.
2) Before starting CFS, the user must have created a Job variable with the name CFS.JR.jrid.JRINIT. jrid is the Job Report ID under which the Enter job should be monitored.
3) After the Enter job has been started successfully, column 1 and 2 of the CFS.JR.jrid.JRINIT Job variable must contain the value '$T', set either during execution of the job, or from within the job. Optionally, a '#' can be entered in column 129, and the name of the Monitor Job variable associated with the Enter job (to a length of 54 bytes) can be entered from column 131.
Monitoring the Enter job occurs as follows:
After an Enter job has been started, and the associated Monitor Job variable created, the CFS.JR.jrid.JRINIT is set the the value '$T' . CFS, which is monitoring this Job Report ID, then causes the Job Report System to set a JR command internally. All new Job variables with the format CFS.JR.jrid.xxxx will be monitored. If the name of a Monjv was entered in the JRINIT Job variable, then the internal JR command will be targeted specifically at this Monjv.
Monitor User-defined Events with Job Variables
The Job Report System of CFS offers the possibility of monitoring any events linked to a Job variable. Information can be passed to the user by means of the Job variable or a file.
The Job variables evaluated by CFS must conform to the following conventions:
Name CFS.JR.jr-id.xxxx
jr-id Job Report Id of the user monitoring the event linked to this JV. Normally, the JR-Id is set to the Job name in the LOGON command. The user can also set it explicitly to any value with the JRID command.
xxxxx Partial name freely selectable by the user.
The Job variable to be used must have been declared a Monitor Job variable. It is therefore possible for the user, via SETJV commands or SETJV macro calls, to insert a value such as '$T' (see below) at column 1 of the Job variable, and thus produce an event for the Job Report System.
Contents of the Job variables
Column Length
1 2 $T normal Termination (activates the Job Report)
$A abnormal Termination (activates the Job Report)
$R running (for STAJ display)
$S Queue (for STAJ display)
The meaning of the values is described below
3 126 not used
129 2 #F the following 54 bytes represents the name of a Job Report file. The contents of this file will be presented to the Job Report user after $T or $A is written to the Job variable.
#_ a message with a maximum length of 80 bytes will be displayed in the terminal system line if $T/$A is written to the Job variable.
131 54 Name of the Job Report file if '#F' was entered in the previous field.
185 26 Job Report System command to be executed when the Job Report mask is displayed. For example, a search can be initiated for a particular record in the Sysout file. For further information, see the JRIC command.
131 80 Text to be displayed to the user in the system line, should the event occur.
211 40 Job-Id. This is a free text field through which the event may be identified in the STAJ command. A message of up to 40 bytes long may also be entered here to provide information via the STAJ command about the current state of the Enter job.
251 4 not used
256 1 C After acknowledging the Job Report screen with the K1 key, or by entering E (End), the following fields of the Job variable will be replaced with blanks: the Job ID field (column 211, length 40) and the user text or JR file name (column 131, length 80).
Setting an Event
To be monitored, the Job variable must already exist when the user invokes CFS or executes a JR command. If the user wishes to monitor an event via a Job variable, the following steps are necessary:
Sequential SETJV commands must be issued to load the Job variable as from column 129 with the required information.
The user will be notified of the event (either by having the Job Report mask displayed, or by receiving a message in the system line of the terminal) as soon as the first column of the Job variable is overwritten with $T or $A.
User Action when notified about Events
Two cases should be distinguished:
a) If the name of a JR file was specified in the Job variable, that file will be displayed in a Job Report mask.
If the user acknowledges the Job Report mask by pressing the K1 key, the JRS will overwrite the Job variable from column 1 with the string '$S'. The Job variable is then released, and can be used to monitor other events.
If the command N is entered in the Job Report mask, the JRS will not modify the Job variable. The "inform user on the occurrence of an event" transaction will not be regarded as closed. The user will be notified of the event again when CFS is reloaded, or when the JR command is next executed.
b) The message to be displayed is written in the Job variable directly (Columns 131-211) and will be displayed on the system line of the user's terminal.
In this case, the JRS will automatically overwrite columns 1-2 with '$S'. The "inform user on the occurrence of an event" transaction will be regarded as closed.
The commands described below are for setting global parameters in the Job Report System. The commands can be entered in the CFS command line, in the Job Report parameter mask (E command), as well as in the Job Report mask (SYSOUT listing of a terminated task).
Activate / Deactivate the Job Report System
JR [$userid | jr-id] [$userid . jr-id] [*RES]
The monitoring of all Enter jobs started under the specified jr-id is activated. The jobs that have already terminated will be displayed immediately. Only those jobs are monitored that had already been started at the time the JR command was executed. If no jr-id is specified, then either the currently valid jr-id, or the jr-id specified explicitly with a JRID command will be activated.
The command can be repeated as often as required with different jr-id's. In this case, all previously activated jr-id's remain active. jr-id can also be specified in the JRP mask (JRP command).
JR-id's of other userid's ($userid) can only be specified if the SHARE=YES option in the JRSH or JRP command is set.
*RES Restore. JR *RES can be used to restore all JRIDs previously active, following an NJR command.
If a STAJ command is entered without a jr-id, then information on the monitored jobs of all active Job Report Id's will be displayed.
Standard for JRID: Job name, or Account number if no Job name has been specified.
NJR The Job Report monitor is reset globally, i.e. for all jr-id's.
JREP enter-params Job Report Enter Parameters.
All jobs started via the Job Report System will use the specified values as parameters for the Enter command.
enter-params Any valid BS2000 Enter parameter can be specified. These parameters will then be valid for all following E commands. The Enter parameters predefined with the JREP command can be enhanced by further parameters in the E command and/or in the DO procedure parameter mask. The Enter parameters can also be specified in the JRP mask (see JRP command on page 11-).
JRF [ file | *LIB(lib,element[(vers)],typ ] [,E] [ , SYSOUT | SYSLST | JRFILE]
The JRF command will cause the selected file to be displayed in the Job Report mask after termination of each of the following jobs. The parameters for this command can also be entered using the same format in the E command.
The operands in the JRF command, the JRF parameters in the E command, or the parameters in a /REMARK command of the procedure to be started all have the same effect:
file The specified file should be displayed after all Enter jobs started hereafter with the E command have terminated. This could be useful, for example, if all the Enter jobs log their output to the same file, opened in EXTEND mode.
The construction of the file name can utilise the following variables:
&TSN TSN of the CFS task which started the Enter job.
&DATE Start date of the Enter job in yymmdd format.
&TIME Start time of the Enter job in hhmmss format.
&LOGNAM Job name of the CFS task which started the Enter job.
*LIB(lib,element[(vers)] ,typ
The specified library element will be displayed (from OSD V1).
E The SYSOUT / SYSLST file is opened in Extend mode.
SYSOUT | SYSLST
The first SYSOUT or SYSLST file assigned with a /SYSFILE SYSOUT, /ASSIGN SYSOUT, /SYSFILE SYSLST, or /ASSIGN SYSLST command in the procedure file will be displayed in the Job Report mask. The SYSFILE or ASSIGN command must appear in the first 20 records following the LOGON command.
For a DO procedure started in Enter mode that does not contain any SYSFILE command, CFS will generate a SYSFILE command in the Enter file with the following form:
/SYSFILE SYSOUT=CFS.SYSOUT.tsn.time or
/SYSFILE SYSLST=CFS.SYSLST.tsn.time.
When starting a DO procedure in Enter mode, and if JRF=SYSLST was specified, then an /OPTION MSG=FH command will be inserted in addition to the /SYSFILE SYSLST command. This will ensure that the SYSOUT statements will also appear in the SYSLST file.
JRFILE The file specified in the first /REMARK JRF=file command in the procedure will be displayed in the Job Report mask.
Standard for JRF: SYSOUT.
Examples:
E CFS.DO.TEST,PAR1=XY/TIME=10,JRF=CFS.FILE.XYZ
E CFS.DO.TEST/JRF=SYSLST
Notes:
The JRF command parameters can also be specified in a REMARK command in the DO or Enter procedure file.
Example: /REMARK JRF=CFS.FILE.XYZ , JRFILE.
The REMARK command must occur within the first 20 records of the Enter or Proc file. If a REMARK JRF command appears in a DO or Enter procedure, then the JRF option will only be valid for that Enter job.
The different sources for specifying the JR file will be evaluated according to the following priorities (1 being the highest priority):
1) Explicit specification of the JR file in the parameter mask.
2) Explicit specification of the JR file in the E command.
3) JR file from a /REMARK command or SYSFILE SYSOUT/SYSLST command in the procedure file.
4) File from the Job Report command JRF or the JRP mask.
5) The standard name CFS.SYSOUT.tsn.time or CFS.SYSLST.tsn.time, as generated in the SYSFILE command by JRS.
The name of the file to be displayed in the Job Report mask will be displayed in the parameter mask (see page 11-), and can be amended from there.
Activate Job Report after the Termination of File Transfer Requests
JRFT Setting the JRFT command causes all following file transfer requests (FT-BS2000 from V3.0) which were started from CFS and which have the PROTOCOL-LISTING: YES option set to be linked to a Monitor Job variable. This will result in the protocol being displayed by the CFS Job Report following termination of the FT request.
Note:
After setting the JRFT option, the user is no longer interested in the asynchronous execution message from FT-BS2000 ("FILE TRANSFERRED. TRANSFER-ID xxxx"). This message can be suppressed with the BS2000 command /BCNTRL MES=N. However, this command will suppress all messages, particularly also messages sent from the operator to a particular user with a /MES tsn,... command. Broadcast messages are not affected.
NJRFT File transfer requests are no longer linked to a Monitor Job variable, and hence also no longer linked to the Job Report System. This is the same as if the PROTOCOL-LISTING parameter in the File Transfer mask is set to the standard value of NO. Systems with a version of FT-BS2000 below 3.0 will also have NJRFT as the standard setting. FT Version 2 must be noted in the CFS module CFSMAIN. For further information, see the CFS Manual for System Administrators in the "Installation of CFS, delivery files" section.
JRIC cmd Job Report Initial Command.
When displaying the Job Report mask following termination of an Enter job, the specified command will be the first command executed. The JRIC command is aimed at displaying the JR file from the beginning, or to search for a particular string. This can reduce the scrolling or searching for specific information to a minimum.
cmd Any command that may be entered in the command field of the Job Report mask.
For a summary of all valid commands, see page 11-.
Examples:
JRIC ++
JRIC S,'FLAGS IN '
Notes:
The JRIC command parameters can also be specified in a REMARK statement in the Enter or DO procedure. Example: /REMARK JRIC cmd
The REMARK command must appear in the first 20 records following the LOGON, PROC or START-PROC command in the DO or Enter procedure. If a REMARK JRIC command appears in the procedure, then the JRIC specification will remain valid only for that Enter job.
If the specified command cannot be executed in the Job Report mask, or if the specified search argument cannot be found, then the standard case will apply, i.e. the Job Report File will be displayed from the beginning.
JRID jr-id Specify internal JR-Identification (JRID).
jr-id A user-definable internal identification code comprising a maximum of 8 characters, that will be linked to all following Enter jobs, and which allows the jobs to be monitored (STAJ jr-id).
If the CFS session is ended before a running Enter job has terminated, and CFS is later reloaded, then the standard Job Report ID will be valid. That means that the user will be informed of the termination of all the jobs under the JR-ID jobname or acct-nr.
This can lead to undesirable consequences if many users work under the same userid and account number, or with the same job name. To prevent this happening, each user can create a unique JRID by issuing a JRID command after loading CFS.
The JRID command will cause the following Enter jobs to be monitored under the specified Job Report ID. The JRID command will not cause Enter jobs having this JRID that were started earlier to be displayed automatically after termination - that can be achieved with the JR command.
Standard for JRID: Job name of the dialog task from which CFS was loaded. If no Job name was specified in the LOGON command, then the account number will be used as the jr-id.
JRP This command will display a mask showing the current values for the Job Report Parameters: JRID, JRF, JREP, JRSH and JRIC. The values of these parameters can then be modified by the user.
The JRP mask has the following layout:
With a mouseclick you get a describtion of the screen item.
Preliminary Command before a CALL to a DO Procedure
JRPRE cmd If a DO procedure is being executed in Enter mode under control of the Job Report System, a BS2000 command can be defined using JRPRE which will be executed in the Enter job before the CALL-PROC command is issued.
Standard: No additional command will be executed before the CALL-PROC command is issued to the DO procedure.
Multi-user Access to Job Report Files
JRSH The SYSOUT/SYSLST files and Job variables created by JRS will be cataloged as SHARE=YES. It will therefore be possible to initialise the job monitoring with a JR $user-id command, or to query the status of jobs being monitored by JRS, from a foreign userid.
NJRSH The SYSOUT/SYSLST files and Job variables created by JRS will be cataloged as SHARE=NO. In this case, JRID's of foreign userid's cannot be specified in JR and STAJ commands.
Standard: NJRSH. The system administrator can change the default to JRSH (see CFSMAIN).