JES2 initialization control statements

JES2 initialization control statements can be used to control the listing and entry of initialization statements while JES2 processes the initialization stream. Initialization control statements do not set JES2 processing values. Table 1 lists the JES2-supported control statements.

Table 1. JES2 Initialization Control Statements
Statement	Explanation
LIST=NO	Ends the listing of statements on devices defined by the HASPLIST DD card. LIST=NO remains in effect until a LIST=YES statement is encountered.
LOG=YES*	Copies the current and subsequent initialization statements to the HARDCPY console. Logging remains in effect until a LOG=NO statement is encountered.
LOG=NO	Ends the logging of initialization statements. LOG=NO is automatically in effect initially and remains in effect until a LOG=YES statement is encountered.
/*	Designates the beginning of a comment. Comments can appear anywhere a blank can be coded, except within vectors or subscripts. The comment is listed or logged as appropriate but is otherwise ignored.
*/	Designates the end of a comment. Comments can appear anywhere a blank can be coded, except within vectors or subscripts. The comment is listed or logged as appropriate but is otherwise ignored.
DISPLAY D	Displays the value of specified JES2 initialization statements or specific parameters on those statements. All parameter values are displayed unless specific parameters are listed. You can add multiple statements to one DISPLAY statement; use commas between statement names. (See the following syntax.) Your message can also be displayed by following the command with message text enclosed in single quotation marks as the following example shows. ┌───────────────────────────────────────────────────────┐ │ &{DISPLAY&}'message text',stmt-name=(parm1,...parmn),│ │ &{D &} stmt-name=(parm1...) │ └───────────────────────────────────────────────────────┘ Note: Place the DISPLAY statement following the initialization statement that you need to display in order for JES2 to read these statements before building the “DISPLAY” response.
CONSOLE	Causes JES2 to get subsequent initialization parameter statements from the operator through the system console. The operator's reply to the message issued as a result of the CONSOLE statement can be any valid statement. JES2 remains in console mode until the operator replies END in response to the $HASP469 (REPLY PARAMETER STATEMENT, CANCEL, OR END) message. Optionally, the operator can reply CANCEL in response to the $HASP469 message to end JES2 initialization. Two methods of adding additional initialization statements to the JES2 initialization data set are available to the operator through use of the CONSOLE option. The first method can be used only if the JES2 initialization data set initially includes the CONSOLE control statement. This causes JES2 to enter console mode at the time the CONSOLE statement is read. At this time the operator can add or override additional initialization statements. The second method is to use the CONSOLE option to stop JES2 initialization processing after all initialization statements have been read and processed before any subsequent initialization processing. The operator is permitted to add additional statements at this time. Consistent with JES2 initialization, if JES2 reads more than one initialization statement for a particular parameter, the last value read is used. This allows the operator either to add new statements to the initialization deck or to change any statements previously entered.
*	These statements are also controlled by options specified at the time you start JES2. You will only produce output if the start options, LIST and LOG, are specified. To display the current start options, use the DISPLAY OPTSDEF command (during JES2 initialization) and then override the options (using the OPTSDEF statement) from the console, if necessary. See z/OS JES2 Initialization and Tuning Reference for more information.
INCLUDE	The include initialization statement allows new initialization data sets or members of the default PARMLIB concatenation to be processed. JES2 will immediately start reading records from the new data set and processing them. When all statements in the included data set have been processed, JES2 initialization resumes processing records from the original data set. Include statements can be nested (included initialization data set can include other data set). There is code to detect a nested include loop (data set A includes data set B that then includes data set A). If a loop is detected, the include request will fail.