Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Example reconfiguration dialog at initialization z/OS JES2 Initialization and Tuning Guide SA32-0991-00 |
|
The following example illustrates a typical console sequence when the operator initiates a checkpoint reconfiguration dialog by specifying RECONFIG on the start JES2 command. The system configuration is based on the following checkpoint definition.
Assume you need to restart JES2 to change the MODE= specification
from DUAL to DUPLEX. This change requires an all-member warm start.
Restart JES2 by entering: S JES2,PARM='WARM,RECONFIG'... in order that JES2 will enter a reconfiguration dialog to allow
you to make the change. You then receive the following series of
messages:
Attention: If, on a JES2 restart, you specify RECONFIG as an option in response to the $HASP426 SPECIFY OPTIONS message or you have previously added RECONFIG to the EXEC statement of the JES2 PROC, JES2 will ignore all prior checkpoint data set forwarding performed by previous checkpoint reconfigurations. JES2 will override all forwarding and use the checkpoint data set definitions as defined in your initialization data set. (See Using the NEWCKPTn data sets for a discussion of JES2 checkpoint data set forwarding.) If this is inappropriate to your restart situation, be certain to have either redefined your checkpoint data sets in your initialization data set or do not use the RECONFIG option. See Specifying the Start Options for information on specifying JES2 start options and z/OS MVS JCL Reference for specifying the JES2 PROC statement. |
Copyright IBM Corporation 1990, 2014
|