Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
JES2-initiated because of I/O error z/OS JES2 Initialization and Tuning Guide SA32-0991-00 |
|
You can minimize or eliminate operator involvement during the checkpoint reconfiguration process prompted by JES2 because of an I/O error by defining replacement checkpoint data set(s) in advance. Further, specify OPVERIFY=NO on the CKPTDEF initialization statement or use the $T CKPTDEF OPVERIFY=NO command to eliminate operator involvement. During a checkpoint reconfiguration because of an I/O error, JES2 attempts to allocate and use a replacement checkpoint data set. If you do not predefine a replacement checkpoint data set, JES2 prompts the operator for the DASD definition (name and volume serial number) or coupling facility structure name of a suitable replacement. Several prompt messages (for example, $HASP273 and $HASP282) allow you to tell JES2 to suspend using a particular data set, modify CKPTDEF initialization statement options, cancel the reconfiguration, or terminate JES2. Use the NEWCKPT1= and NEWCKPT2= options on the $T CKPTDEF command (outside a checkpoint reconfiguration) to predefine replacement checkpoint data sets. |
Copyright IBM Corporation 1990, 2014
|