![]() |
- E |Start Enter job
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.
JN=jobname one to eight character Job name for the Enter job created by CFS.
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.
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=...).