Starting Using the Console

If the PARM= parameter is not specified on the MVS START command for JES2, you are choosing to start JES2 by specifying options from the console. JES2 issues message $HASP426:

*id $HASP426 SPECIFY OPTIONS - JES jeslevel SSNAME=ssname

You should respond by using the MVS REPLY command to specify the JES2 options determined by your installation procedures. (See z/OS MVS System Commands, SA38-0666 for a complete description of the REPLY command.)

REPLY id,options

For example, if the id for a reply is "003", the $HASP426 message is:

003 $HASP426 SPECIFY OPTIONS..... message

You would reply as follows:

REPLY 003,options...........

Note:

You are only allowed to type one line on the operator console to provide the JES2 options in your reply.
The reply to supply options must follow the rules for JES2 initialization statements.

The examples below illustrate correct responses:

REPLY 003,a,b,c,d,e
REPLY 003,'a,b,c,d,e'
REPLY 003,a,b,x=144,d,e

The option table below, Table 1, lists the JES2 start options and an explanation of each. If you respond to message $HASP426 with the $PJES2 command, JES2 will terminate.

If this is the first start of JES2, the following sequence applies:

You should specify the COLD (or FORMAT) option. If COLD (or FORMAT) is not specified, JES2 issues the following messages:

$HASP479 UNABLE TO OBTAIN CKPT DATA SET LOCK - I/O ERROR
$HASP454 SHOULD JES2 BYPASS THE MULTI-MEMBER INTEGRITY LOCK?
         (Y OR N)

Reply Y to message $HASP454. JES2 will then issue the following messages:

$HASP478 INITIAL CHECKPOINT READ IS FROM CKPTn
         (dsname ON volser)
$HASP434 INVALID CHECKPOINT RECORD ON CKPTn DATASET
$HASP285 JES2 CHECKPOINT RECONFIGURATION IN PROGRESS
$HASP289 CKPT1 AND/OR CKPT2 SPECIFICATIONS ARE REQUIRED.
$HASP272 ENTER RESPONSE

Reply TERM to the $HASP289 and $HASP272 message pair. Then you have to restart JES2 specifying the COLD (or FORMAT) option.

All options can be entered in uppercase or lowercase and must be separated by commas.
If two options are entered that are considered opposite, for example (WARM,COLD), the last option specified is the one JES uses.
If FORMAT is specified, the system will perform a cold start even though WARM is also specified.

The operator then enters the options using the standard reply format.

JES2 must be started and completely initialized before initiators accept work.

Table 1. JES2 Start Options
Option	Explanation
FORMAT NOFMT	FORMAT specifies that JES2 is to format all existing spool volumes. If you add unformatted spool volumes, JES2 automatically formats them whether FORMAT is specified or not. When you specify FORMAT, JES2 will automatically be cold started. Note: The FORMAT option is denied if this is a multi-access spool configuration, and JES2 is processing in one or more of the other members. *Default*: NOFMT specifies that JES2 is not to format existing spool volumes unless JES2 determines that formatting is required.

COLD WARM	COLD specifies that JES2 is to be cold started. All jobs in the member are lost. Note: The COLD option is denied if this is a multi-access spool configuration and JES2 is processing in one or more of the other members. If the member to be warm started is in a multi-access spool configuration with any other active members, only this member is warm started. When JES2 is cold started, it will by default start with z11 functions activated unless the UNACT parameter is also specified. *Default*: WARM specifies that JES2 is to be warm started. JES2 will continue processing jobs from where they were stopped. If the FORMAT option was also coded, then JES2 will ignore the WARM specification and will cold start.

NOREQ REQ	NOREQ specifies that the $HASP400 (ENTER REQUESTS) message is to be suppressed and that JES2 is to automatically start processing when initialization is complete. *Default*: REQ specifies that the $HASP400 (ENTER REQUESTS) message is to be written at the console. This message allows the operator to restore the MVS environment (VTAM, for example) to what it was before the preceding shutdown and start JES2 processing with the $S command. This can be overridden with OPTSDEF.

NOLIST LIST	NOLIST specifies that JES2 is not to print the contents of the initialization data set or any error flags that occur during initialization. If you specify NOLIST, JES2 ignores any LIST control statements in the initialization data set. The z/OS JES2 Initialization and Tuning Reference, SA32-0992 presents an example of an initialization data set listing produced by using the list option. *Default*: LIST specifies that JES2 is to print all the statements in the initialization data set and any error flags that occur during initialization. (JES2 prints these statements if a printer is defined for that purpose when JES2 is started.) LIST will not print any statements that follow a NOLIST control statement in the initialization data set. This can be overridden with OPTSDEF.

NOLOG LOG	NOLOG specifies that JES2 is not to copy initialization statements or initialization errors to the HARDCPY console. If you specify NOLOG, JES2 ignores LOG control statements in the initialization data set. *Default*: LOG specifies that JES2 is to honor any LOG statements in the initialization data set. This can be overridden with OPTSDEF.

SPOOL=VALIDATE SPOOL=NOVALIDATE	VALIDATE specifies that the track group map is validated on a JES2 all-member warm start in addition to the 7–day, ongoing track group validation cycle. This option when used in conjunction with job queue validation is useful for several special situations that require immediate track group map validation. Refer to the z/OS JES2 Initialization and Tuning Guide, SA32-0991 for a further discussion of using SPOOL=VALIDATE. *Default*: SPOOL=NOVALIDATE specifies that the track group map is not validated when JES2 restarts (single-member and all-member warm start and hot start).

CKPT1 CKPT2	CKPT1 specifies that JES2 reads the CKPT1 data set as the source of the checkpoint data for building the JES2 work queues.CKPT2 specifies that JES2 reads the CKPT2 data set as the source of checkpoint data for building the JES2 work queues. Note: This option is valid only on an all-member warm start. *Default*: If you do not specify this option, JES2 determines which checkpoint data set to initially read based on information in the checkpoint data set. This can be overridden with OPTSDEF or CKPTDEF.

RECONFIG	RECONFIG specifies that JES2 will use the checkpoint data set definitions as specified on the CKPTDEF statement in the initialization data set. JES2 overrides any modifications to the checkpoint data set definitions previously made either by the $T CKPTDEF command or through the use of the checkpoint reconfiguration dialog. Specifying RECONFIG will also cause JES2 to enter the reconfiguration dialog during initialization; and issue message $HASP289 CKPT1 AND/OR CKPT2 SPECIFICATIONS ARE REQUIRED. The CKPTDEF statement definition cannot contain the most current checkpoint definition if you have previously reconfigured your checkpoint configuration through the checkpoint reconfiguration dialog because changes made through the dialog are not saved in the input stream data set. Note: This option is valid only on an all-member warm start. Specifying PARM=RECONFIG has the same affect as specifying RECONFIG=YES on the CKPTDEF initialization statement.

HASPPARM=ddname HASPPARM=HASPPARM	HASPPARM=ddname specifies the name of the data definition (DD) statement that defines the data set containing the initialization statements that JES2 is to use for this initialization. *Default:HASPPARM=HASPPARM* specifies that JES2 is to be initialized using the initialization statements in the data set defined by the HASPPARM DD statement in the JES2 procedure. Mutually exclusive with MEMBER=.

MEMBER=membname or PARMLIB_MEMBER= membname MEMBER=HASjesx	MEMBER=membname specifies the member of the default PARMLIB concatination containing the initialization statments that JES2 is to use for this initialization. PARMLIB_MEMBER= is a synonym for MEMBER=. MEMBER is mutually exclusive with HASPPARM=. The order of processing is: MEMBER= if specified HASPPARM= if specified default HASPPARM=HASPPARM if DD can be opened default MEMBER=HASjesx member of the default PARMLIB concatination

CONSOLE	Causes JES2 to simulate receiving a CONSOLE initialization statement after all initialization statements are processed. That is, if CONSOLE is specified, JES2 will divert to the operator console for further parameter input after all PARMLIB parameter input is exhausted. (Refer to the CONSOLE initialization control statement, above, for further information.) This can be overridden with OPTSDEF.

NONE U N	NONE, U, or N character specifies that JES2 is to use all the default start options. There is no difference between these three options. These options are equivalent. When NONE, U, or N is specified, JES2 uses the default start options which are: NOFMT WARM REQ LIST LOG

UNACT	UNACT unactivates the new JES2 functions introduced in z/OS Version 1 Release 11. This option reverses the ACTIVATE level=z11 setting. It can be used on an all-member WARM or HOT start or a COLD start. *Default*: On a WARM or HOT start, JES2 takes no action and the checkpoint release level stays at the previous setting. On a COLD start, JES2 starts in z/OS Version 1 Release 11 (z11) mode.

$P JES2	If specified, instructs JES2 to terminate immediately.