| 000 |
10 |
Possible enqueue error. Programmer Response: Ensure
the program reestablished the enqueues upon restart.
|
| 001 |
08 |
A CHECKPOINT parameter list error was encountered. Programmer
Response: Correct the parameter list.
|
| 002 |
08 |
The DD statement for the checkpoint data set is missing. Programmer
Response: Ensure that the DD statement is correct and is included.
|
| 003 |
08, S13F |
Insufficient storage for a checkpoint or restart. Programmer
Response: Use a larger storage area. If the IEALIMIT routine has
been modified, it may be necessary to alter it to request less storage.
|
| 004 |
0C |
Open failed for checkpoint data set. Programmer Response: Locate
the problem and correct it.
|
| 005 |
08 |
The checkpoint data set key length was not equal to zero. Programmer
Response: Ensure that the checkpoint data set is not a keyed data
set.
|
| 006 |
08 |
The checkpoint data set record format was not U. Programmer
Response: Ensure that the record format is U.
|
| 007 |
08 |
The data control block (DCB) for the checkpoint data set was
opened for other than BSAM or BPAM processing. Programmer Response: Ensure
that only BSAM or BPAM is used.
|
| 008 |
08 |
The time interval specified in a STIMER macro had not elapsed.
Programmer Response: Cancel the time interval before issuing
the CHKPT macro instruction, and restore the interval after a restart.
|
| 009 |
08 |
The CHKPT macro instruction was issued in an exit routine other
than the end-of-volume exit routine, or an RB of an unacceptable type
was found on the RB chain. Programmer Response: Ensure
that the CHKPT macro instruction is not issued in an exit routine
other than the end-of-volume exit routine.
|
| 010 |
08 |
An open graphic data control block (DCB) has been detected,
but it is not supported in Checkpoint/Restart. Programmer Response: Ensure
that the CHKPT macro instruction is not issued while graphic DCBs
are open.
|
| 011 |
08 |
The current task is a subtask or is not represented by the
first job step TCB. Programmer Response: Ensure that the
CHKPT macro instruction is not issued when multiple tasks (created
by the ATTACH macro instruction) exist.
|
| 012 |
08 |
The current task has a subtask. Programmer Response: Ensure
that the CHKPT macro instruction is not issued when multiple tasks
(created by the ATTACH macro instruction) exist.
|
| 013 |
08 |
At the time the checkpoint was attempted, the job had issued
the PCLINK macro instruction with the STACK option, but had not issued
a corresponding PCLINK macro instruction with the UNSTACK parameter.
(That is, the PCLINK stack was not empty.) Programmer Response: Ensure
that the PCLINK stack is empty.
|
| 014 |
08 |
A WTOR macro instruction was issued prior to the CHKPT macro,
and a reply had not been received. Programmer Response: Issue
a WAIT macro instruction after the WTOR macro instruction, or a DOM
macro instruction for any outstanding WTORs before the CHKPT macro
instruction.
|
| 015 |
08 |
An incorrect checkpoint identification length or format was
encountered. Programmer Response: When supplying a checkpoint
identification, ensure that the length and format are correct.
|
| 016 |
08 |
The checkpoint data set device type was not magnetic tape or
direct access. Programmer Response: Take checkpoints only
to tape or DASD.
|
| 017 |
10 |
Insufficient storage to check enqueues—possible error. Programmer
Response: Provide a larger storage area.
|
| 018 |
10 |
GQSCAN found an abnormal condition. Programmer Response: See
the information provided by the GQSCAN service to locate and correct
the problem.
|
| 019 |
08 |
Either MACRF=W was not specified for the checkpoint data control
block (DCB), or the data control block was opened by the user's program,
but was not opened for output. Programmer Response: Ensure
that the DCB for the checkpoint data set has MACRF=W and, if opened,
is opened for output.
|
| 020 |
0C |
I/O error during open of CHKPT data set. Programmer
Response: Locate the cause of the I/O error and correct the problem.
|
| 021 |
08 |
LABEL was coded in the DD statement for the checkpoint data
set with a value other than SL or SUL. Other values for the LABEL
parameter must not be used in a checkpoint data set DD statement.
Programmer Response: A tape data set to be used for creating
a checkpoint data set must have standard labels. Correct the JCL and/or
tape label.
|
| 022 |
0C |
Error occurred reading or writing a SWA control block. Programmer
Response: This is probably an error in the SWA manager. Contact
your software support personnel.
|
| 023 |
0C, S13F |
An uncorrectable input/output error occurred while writing
the checkpoint data set. Programmer Response: Locate the
cause of the I/O error and correct it.
|
| 024 |
S13F |
A data set has more than five volumes, but there is no JFCBX.
Programmer Response: This is probably an error in the SWA
manager. Contact your software support personnel.
|
| 025 |
08 |
A CHKPT request was made by a task that was open to a PDSE,
or a PDSE was specified as a checkpoint data set. Programmer
Response: Close PDSEs open at the time of checkpoint.
|
| 026 |
0C |
Execution of a STOW macro instruction was unsuccessful; a permanent
input/output error occurred. Programmer Response: Locate
the cause of the I/O error and correct it.
|
| 027 |
08 |
End-of-volume occurred while writing a checkpoint data set
entry on a direct access volume, and secondary allocation was requested
and allocated more than once; or end-of-volume occurred twice while
writing a checkpoint data set entry on tape. Programmer Response: Ensure
that all volumes (or DASD extents) have enough room for more than
one checkpoint entry.
|
| 028 |
0C, S33F, 10 |
I/O error occurred during SYNCDEV to a user data set. The user's
data set may not be available for a restart. Programmer Response: Locate
the cause of the I/O error and correct it.
|
| 029 |
08 |
The OPTCD=Q subparameter of the DCB parameter was coded. The
value coded is not acceptable for a checkpoint data set. ASCII translation
on checkpoint data set is not allowed. Programmer Response: Correct
the indicated error and resubmit the job.
|
| 030 |
0C |
An uncorrectable I/O error occurred while quiescing pending
I/O requests. The I/O error occurred with BSAM or with QSAM EROPT
not equal to ACC. Programmer Response: Code EROPT=ACC (on
your DD statement or DCB) for QSAM data sets, or locate the cause
of the I/O error and correct it.
|
| 031 |
S13F |
An uncorrectable I/O error occurred while reading from the
checkpoint data set. Programmer Response: Locate the cause
of the I/O error and correct it. If all restrictions are met for a
deferred restart, you can submit a deferred restart. Either restart
at an earlier checkpoint or repeat the original execution using a
different volume.
|
| 033 |
08 |
Cannot reposition to a tape data set or record because the
block count in the DCB is negative. This may be caused by the label
type being NL or BLP and the data set being open for RDBACK. |
| 034 |
S13F |
A DD statement was missing for the restart step. Programmer
Response: Supply the missing DD statement.
|
| 035 |
S13F |
Wrong length record detected when reading checkpoint data set.
Programmer Response: Locate and correct the problem. Be
alert for a possible security violation.
|
| 036 |
0C |
Checkpoint received a nonzero return code from the MVS™™ supervisor concerning the number of SSCR
records it requires. Programmer Response: See Modules and Return Codes for IHJ Messages for IHJ Messages.
|
| 037 |
0C |
Checkpoint received a nonzero return code after requesting
that the MVS supervisor fill
in the SSCR records with checkpoint data. Programmer Response: See Modules and Return Codes for IHJ Messages for IHJ Messages.
|
| 038 |
S13F |
Restart received a nonzero return code when it passed the SSCR
records containing MVS supervisors'
checkpoint data. Programmer Response: See Modules and Return Codes for IHJ Messages for IHJ Messages.
|
| 039 |
08 |
A PDS was converted to a PDSE between the time a checkpoint
was taken and the time an attempt was made to restart at the checkpoint. |
| 040 |
S13F |
An uncorrectable I/O error occurred while reading standard
volume labels. Programmer Response: Locate the cause of
the I/O error and correct it.
|
| 041 |
08 |
CHKPT was issued with a VSAM data set open for create mode
processing, and no reposition was specified. Programmer Response Ensure
that a checkpoint is not issued when this condition exists, or correct
this condition.
|
| 042 |
0C |
An error occurred during repositioning for a VSAM data set.
Programmer Response: Locate the error and correct it.
|
| 043 |
08 |
CHKPT was issued with an entry-sequenced data set open for
output, an upgrade set open over it, and reposition required. NRE
or NRC must be specified in the DD statement. Programmer Response: Locate
the error and correct it.
|
| 044 |
08 |
CHKPT was issued for a relative-record data set open for create
mode direct processing. Programmer Response: Ensure that
a checkpoint is not issued when this condition exists, or correct
this condition.
|
| 045 |
08 |
CHKPT was issued with a VSAM data set open with the GSR option.
Programmer Response: Ensure that a checkpoint is not issued
when this condition exists, or correct this condition.
|
| 046 |
08 |
A checkpoint is not allowed if any of the VSAM data sets in
the address space are utilizing the control block update facility
processing, or if any of the VSAM data sets in the address space are
associated with an alternate index that was using the enhanced share
option 4 processing. Programmer Response: Change the data
set to be DISP=OLD or close the data set prior to issuing the CHKPT.
|
| 047 |
08 |
CHKPT was attempted with a VSAM data set that was using the
UBF or CBIC option. Programmer Response: Ensure that a
checkpoint is not issued when this condition exists, or correct this
condition.
|
| 048 |
08 |
VSAM—media manager was in use. Programmer Response: Remove
the CHKPT macro instruction.
|
| 049 |
08 |
VSAM RLS was in use. Programmer Response: Remove
the CHKPT macro instruction.
|
| 050 |
S13F |
A volume serial number at restart is not the same as it was
when the checkpoint was taken. Programmer Response: Ensure
that the volumes used at checkpoint are the same at restart and that
units are available to mount them.
|
| 051 |
08 |
A SPIE or ESPIE exit was active when CHKPT request was made.
Programmer Response: Do not issue a CHKPT request from
a SPIE or ESPIE exit.
|
| 052 |
S13F |
A module that was loaded in the link pack area (LPA) or the
nucleus and was being used by the current job when the checkpoint
was taken, is not in the LPA or nucleus at restart. Programmer
Response: Ensure that the nucleus and LPA are the same at restart
as when the checkpoint was taken.
|
| 053 |
S13F |
A module has a different entry point address in the link pack
area (LPA) or nucleus at restart than it did when the checkpoint was
taken. Programmer Response: Ensure that the nucleus and
LPA are the same at restart as when the checkpoint was taken.
|
| 054 |
08 |
A primary address space ID or secondary address space ID is
not the same as the home address space ID. Cross-memory addressing
was active when a checkpoint was requested. Programmer Response: Do
not issue the CHKPT macro when in cross memory mode.
|
| 055 |
0C |
Unacceptable return code received from system routine (VSMREGN)
used to obtain starting address and size of private area regions.
Programmer Response: Information about this problem should
have been provided by the VSMREGN service of VSM (virtual storage
manager).
|
| 056 |
0C, 14 |
Unacceptable return code received from system routine (VSMLIST)
used to obtain ranges of virtual storage allocated. Programmer
Response: Information about this problem should have been provided
by the VSMLIST service of VSM (virtual storage manager).
|
| 057 |
08 |
Checkpoint DD statement is concatenated. Programmer
Response: Checkpoint data sets must not be concatenated.
|
| 058 |
14, S13F |
Internal parameter list is incorrect. Programmer Response: Use
the diagnostic information provided by checkpoint/restart to locate
and correct the problem.
|
| 059 |
14, S13F |
Internal unexpected return code was received. Programmer
Response: Use the diagnostic information provided by checkpoint/restart
to locate and correct the problem.
|
| 060 |
14 |
Scheduler checkpoint routine discovered error in SWA control
block. Programmer Response: This is probably an error in
the SWA manager. Contact your software support personnel.
|
| 061 |
08 |
Caller of CHKPT was in secondary addressing mode. Programmer
Response: Do not issue the CHKPT macro when in cross memory mode.
|
| 062 |
0C, 14 |
Checkpoint or Restart detected an internal error while processing
checkpoint records. Programmer Response: This is probably
an error in the SWA manager. Contact your software support personnel.
|
| 063 |
S13F |
I/O error while repositioning a tape to a record within a data
set. Programmer Response: Either restart at an earlier
checkpoint or repeat the original execution, using a different volume.
|
| 064 |
10 |
DLPA module detected on load list. Programmer Response: Be
sure that the dynamic link pack area is not altered until you no longer
intend to attempt a restart from the identified checkpoint.
|
| 065 |
0C |
Checkpoint received a nonzero return code from the MVS supervisor due to internal errors. Programmer
Response: This is probably an error in the checkpoint/restart MVS supervisor routine. Contact your
software support personnel.
|
| 066 |
0C |
Restart received a nonzero return code from the MVS Supervisor due to internal errors. Programmer
Response: This is probably an error in the checkpoint/restart MVS supervisor routine. Contact your
software support personnel.
|
| 067 |
0C |
Checkpoint received a nonzero return code from the MVS supervisor because a service routine failed.
Programmer Response: This is probably an error in the checkpoint/restart MVS supervisor routine. Contact your
software support personnel.
|
| 068 |
0C |
Restart received a nonzero return code from the MVS supervisor because a service routine failed.
Programmer Response: This is probably an error in the checkpoint/restart MVS supervisor routine. Contact your
software support personnel.
|
| 069 |
08 |
Too much VSMLIST data—user's storage is fragmented beyond checkpoint's
capabilities. Programmer Response: Reduce the region size,
change the program to reduce storage fragmentation, or increase the
size of extended private storage.
|
| 070 |
0C |
Checkpoint received a nonzero return code from the MVS Contents Supervisor, because a provider routine
return code was not zero. Programmer Response: This is
probably an error in the checkpoint/restart MVS supervisor routine. Contact your software
support personnel.
|
| 071 |
0C |
Restart received a nonzero return code from the MVS contents supervisor, because a provider routine
return code was not zero. Programmer Response: This is
probably an error in the checkpoint/restart MVS supervisor routine. Contact your software
support personnel.
|
| 072 |
0C |
Checkpoint received a nonzero return code from the MVS supervisor because a provider routine return
code was not zero. Programmer Response: This is probably
an error in the checkpoint/restart MVS supervisor
routine. Contact your software support personnel.
|
| 073 |
0C |
Restart received a nonzero code from the MVS supervisor because a provider routine return
code was not zero. Programmer Response: This is probably
an error in the checkpoint/restart MVS supervisor
routine. Contact your software support personnel.
|
| 074 |
S13F |
An unacceptable I/O error occurred while reading a data set
control block (DSCB). This reason code can also be issued if a data
set was being scratched or deleted. Programmer Response: If
it is during restart and the restart was deferred, the restart may
be attempted again. If a preceding input/output error message for
the restarted job identified the device in error, locate and correct
the error. Ensure that no data set has been scratched or deleted.
|
| 075 |
08 |
STOW encountered a full directory on the checkpoint data set.
Programmer Response: Increase the size of the directory
for the checkpoint data set.
|
| 076 |
S13F |
A direct access data set (other than a spooled data set) being
processed for input did not occupy the same extent as it did originally;
that is, discrepancies were found in comparing the space allocations
described in the data extent block (DEB) and the data set control
block (DSCB). Programmer Response: Ensure that no input
data set (other than a spooled data set) has been expanded or rewritten
in its original volume.
|
| 078 |
S13F |
Restart was attempted on a different level of the system than
when the checkpoint was taken. Programmer Response: Restart
the job in the same processing environment as the one in which it
was checkpointed.
|
| 079 |
S13F |
DUMMY was specified for an open data set; and either the data
set was not being processed by the basic or queued sequential access
methods, or the checkpoint at which restart was to occur was established
in an end-of-volume exit routine for the data set. Programmer
Response: Ensure that DUMMY is specified only for data sets being
processed by the queued or basic sequential access methods. Also ensure
that restart is not to occur at a checkpoint that was established
in an end-of-volume exit routine for a data set that has been made
DUMMY.
|
| 080 |
S13F |
A subsystem data set was made DUMMY at restart. This usually
refers to a spooled data set. Programmer Response: Do not
make subsystem data sets DUMMY.
|
| 081 |
S13F |
The checkpoint job or step specified ADDRSPC=REAL(V=R) and
the restarting job or step did not, or vice versa. Programmer
Response: Ensure that the V=R status of both the checkpoint and
restarting job or step are the same. That is, if ADDRSPC=REAL was
specified at checkpoint time, it can only be specified (and must be
specified) at restart time.
|
| 082 |
S13F |
The TCAM control program was not active at restart, but a TCAM
DCB was open at checkpoint. Programmer Response: Ensure
that the TCAM control program region is active and is large enough
to add control blocks.
|
| 083 |
S13F |
The value of the QNAME keyword parameter on the DD statement
is not defined in the TCAM table. Programmer Response: Correct
the DD statement or define the QNAME value in the TCAM table.
|
| 084 |
S13F |
The process entry defined by the QNAME is already in use by
another application program. Programmer Response: Restart
the job when the specified QNAME is not being used.
|
| 085 |
S13F |
A GETMAIN failed during TCAM restart. Programmer Response: Provide
more storage.
|
| 086 |
S13F, 08 |
An abend occurred during a checkpoint or restart. Programmer
Response: Use the diagnostic information provided to correct the
error.
|
| 087 |
S13F |
Record order on checkpoint data set incorrect and was detected
by restart. Programmer Response: Use the diagnostic information
provided to correct the error. Be alert for a possible security violation.
|
| 088 |
S13F |
Storage not allocated as expected and was detected by restart.
Programmer Response: Use the diagnostic information provided
to correct the error.
|
| 090 |
14 |
Checkpoint or restart detected an error internal to checkpoint/restart.
Programmer Response: Use the diagnostic information provided
to correct the error.
|
| 091 |
S13F, 14 |
Error building a message. Checkpoint/restart detected an error
while building a message for the operator. Programmer Response: Use
the diagnostic information provided to correct the error.
|
| 092 |
S13F |
An error occurred during basic partitioned access method (BPAM)
processing. For example, an error was detected after the convert routine,
or after reading the directory blocks. Programmer Response: Locate
the problem and correct it.
|
| 093 |
14 |
An internal parameter list in an MVS supervisor
call is incorrect. Programmer Response: This is probably
an error in the checkpoint/restart MVS supervisor
routine. Contact your software support personnel.
|
| 094 |
S13F |
Nucleus routines or tables have moved or been deleted since
checkpoint. LPA module entry points, which reside in the nucleus table,
have been altered. This may result from a change link pack area (CLPA).
Programmer Response: Resubmit the job on the same system
with the same nucleus and LPA on which the checkpoint was taken.
|
| 095 |
14, 08 |
A control block chaining error occurred. |
| 096 |
S13F |
An error occurred during use of the STOW macro instruction
to delete a member from the directory of a PDS. Programmer
Response: Locate the cause of the error and correct it.
|
| 097 |
S13F |
An unacceptable I/O error occurred in the installation's nonstandard
label (NSL) routine (NSLREPOS). Programmer Response: Locate
the cause of the I/O error and correct it.
|
| 098 |
S13F |
Insufficient number of devices were available for restart.
Programmer Response: Ensure that the UNIT parameter of
the DD statement accurately reflects the device requirements for the
data set.
|
| 099 |
S13F |
A data set association block (DSAB) is missing at restart.
This probably means a DD statement was omitted. Programmer
Response: Probable system error. Locate and correct the problem.
|
| 100 |
S13F |
MSS error occurred during mount processing. This is a probable
system error. |
| 101 |
S13F |
An uncorrectable I/O error occurred while reading a volume
label on a direct access device. Programmer Response: Locate
the cause of the I/O error and correct it.
|
| 103 |
S13F |
A subsystem checkpoint record (SSCR) was written, but the corresponding
DCB is not in the open data set table at restart. Programmer
Response: Probable error in checkpoint/restart. Contact your software
support personnel.
|
| 104 |
S13F |
An I/O error occurred while repositioning to the correct data
set on tape. Programmer Response: Locate the cause of the
I/O error and correct it.
|
| 105 |
S43F |
Library Automation services detected an error while processing
a tape. See message text following message IHJ014I for detailed information
about the error. Programmer Response: Probable system error.
Contact your software support personnel.
|
| 106 |
S53F |
A Tape Library Dataserver tape
volume was mounted, and the internal label serial number did not match
the volume serial number of the tape requested. Programmer
Response: After verifying that the correct tape is available,
resubmit the job.
|
| 107 |
S53F |
The file protect status for a Tape Library Dataserver tape
volume was incorrect. Restart attempted to reset it using PSF, but
encountered an error. Programmer Response: Insure that
the tape volume is correctly file protected, then resubmit the job.
|
| 108 |
04 |
Restart was unable to update statistics (i.e., last mount date
and last write date) for a Tape Library Dataserver tape
volume, because SMS was not active. Programmer Response: This
is a warning indicating that checkpoint/restart was unable to update
the tape configuration data base (TCDB) tape volume record; however,
the restart has completed successfully.
|
| 109 |
04 |
Restart was unable to update statistics (i.e., last mount date
and last write date) for a Tape Library Dataserver tape
volume. An error return code was returned from the SSI call. Programmer
Response: This is a warning indicating that checkpoint/restart
was unable to update the tape configuration data base (TCDB) tape
volume record; however, the restart has completed successfully.
|
| 110 |
04 |
Restart was unable to update statistics (i.e., last mount date
and last write date) for a Tape Library Dataserver tape
volume. An error code was returned by SMS. Programmer Response: This
is a warning indicating that checkpoint/restart was unable to update
the tape configuration data base (TCDB) tape volume record; however,
the restart has completed successfully.
|
| 112 |
0C |
Checkpoint was unable to load the MVS CSV
(Contents Supervisor) routine. Programmer Response: This
is probably an error with the CSV routine. Contact your software support
personnel.
|
| 113 |
0C |
Restart was unable to load the MVS CSV
(Contents Supervisor) routine. Programmer Response: This
is probably an error with the CSV routine. Contact your software support
personnel.
|
| 114 |
08 |
UNIX® system services
is active in the current address space. Programmer Response: Checkpoint
is not supported for HFS files. Contact your software support personnel.
|
| 117 |
08 |
The
system cannot take the checkpoint because the checkpoint data set
was dynamically allocated with the XTIOT option, with the DSAB-above-the-line
option or without UCB capture.
Programmer Response: Remove
the CHKPT macro instruction or remove the XTIOT, NOCAPTURE and DSAB-above-the-line
options from the checkpoint data set allocation.
|
| 124 |
08 |
A CHKPT request was made by a task that was open to a checkpoint
data set with a DCBE. Programmer Response: Ensure that
checkpoint is not issued while this condition exists. DCBE's are not
supported by checkpoint.
|
| 125 |
08 |
A CHKPT request was made by a task that was open to a sequential
extended format data set, or an extended format data set was specified
as a checkpoint data set. Programmer Response: Ensure that
checkpoint is not issued while this condition exists, or correct this
condition.
|
| 126 |
08 |
A PDS was converted to an extended format data set between
the time a checkpoint was taken and the time an attempt was made to
restart at the checkpoint. Programmer Response: Ensure
that the restart is not issued while this condition exists, or correct
this condition.
|
| 181 |
S13F |
An error occurred during VSAM restart preformat routine. yyy is
the value from the RPL error code. Programmer Response: The
error is for VSAM only. For more information see the RPL error codes
in z/OS DFSMS Macro Instructions for Data Sets for
VSAM data sets.
|
| 182 |
S13F |
An error occurred during VSAM restart verify routine. yyy is
the value from the RPL error code. Programmer Response: The
error is for VSAM only. For more information see the RPL error codes
in z/OS DFSMS Macro Instructions for Data Sets for
VSAM data sets.
|
| 183 |
S13F |
An error occurred during VSAM restart put routine. www is
the value from the RPL error code. Programmer Response: The
error is for VSAM only. For more information see the RPL error codes
in z/OS DFSMS Macro Instructions for Data Sets for
VSAM data sets.
|
| 184 |
S13F |
An error occurred during VSAM restart index put routine. www is
the value from the RPL error code. Programmer Response: The
error is for VSAM only. For more information see the RPL error codes
in z/OS DFSMS Macro Instructions for Data Sets for
VSAM data sets.
|
| 185 |
S13F |
VSAM open error during restart. www is the value from
the ACB error code. Programmer Response: See message IEC161I
or IEC252I.
|
| 186 |
0C |
VSAM close error. www is the value from the ACB error
code. Programmer Response: The message is for VSAM only.
See message IEC161I or IEC252I.
|
| 190 |
S13F |
An error occurred while attempting to obtain catalog information
for the cluster identified by the ddname in message IHJ0091. Programmer
Response: The error is for VSAM only. For more information, see
messages IEC331I and IDA3009I, if issued.
|
| 191 |
S13F |
An error occurred while attempting to mount volumes for the
ddname identified by message IHJ0091. Programmer Response: Increase
the number of units allocated for the ddname.
The
error is for VSAM only. For more information, see message IEC161I
or IEC252I, if issued.
|
| 193 |
S13F |
Checkpoint was taken during VSAM create mode, but, at restart
time, the data set was no longer in create mode. Programmer
Response: A restart is not allowed. Take the checkpoint after
the data set is loaded.
|
| 194 |
S13F |
The catalog entries for a VSAM upgrade path have been altered
since checkpoint. Programmer Response: If the upgrade path
can be restored to its condition at checkpoint, the restart may be
resubmitted.
|
| 195 |
S13F, 0C |
Insufficient storage is available for a VSAM restart. Programmer
Response: Increase the available storage.
|
| 196 |
S13F |
The catalog for one or more VSAM data sets has been updated,
indicating that another job successfully processed the data set after
the checkpoint was taken. Restart cannot restore the data set to its
checkpoint status. Programmer Response: Override the condition,
and allow restart by coding AMP='CROPS=NCK’ in the DD statement for
the data set. Be aware, however, that changes might have been made
to the data between the time the checkpoint was taken and when restart
is attempted. A data set that has been extended to span volumes since
the checkpoint was taken cannot be restarted.
The error is
for VSAM only. For more information, see messages IEC161I or IEC252I,
if issued.
|
| 197 |
S13F |
A restart is not allowed for control block update facility
(CBUF) processing. Programmer Response: Do not issue the
CHKPT macro instruction while using CBUF processing.
|
| 198 |
S13F |
A VSAM data set extended to a new volume after the checkpoint
was taken. Programmer Response: The checkpoint cannot be
restarted. For a deferred restart, resubmit the job selecting a checkpoint
taken after the data set extended to the new volume.
The error
is for VSAM only. For more information, see message IEC161I or IEC252l,
if issued.
|
| 199 |
S13F |
An error occurred during BLDVRP processing in VSAM restart. www is
the return code from the BLDVRP request. Programmer Response: The
error is for VSAM only. For more information see z/OS DFSMS Macro Instructions for Data Sets.
|
| 200 |
0C |
A PURGE I/O request failed. Programmer Response: Locate
and correct the error.
|
| 201 |
S13F |
Page Fix (PGSER) failed. This is an uncorrectable error. Programmer
Response: Probable system error. Contact your software support
personnel.
|
| 202 |
0C, S13F |
SETLOCK failed. This is an uncorrectable error. Programmer
Response: Probable system error. Contact your software support
personnel.
|
| 203 |
S13F |
An invalid attempt has been made to invoke RESTART SVC routines.
Programmer Response: Only the scheduler may invoke RESTART.
Remove either the JCL or program logic that attempts to execute RESTART.
|
| 204 |
0C |
VIO data sets could not be checkpointed for a subsequent automatic
restart. This checkpoint is unavailable for automatic restarts; however,
deferred restarts are possible if the VIO data sets are made DUMMY.
Programmer Response: An error occurred while checkpointing
VIO data sets to the job journal. Deferred restarts may be accomplished
on the checkpoint entry; however, the VIO data sets must be made DUMMY.
Locate and correct the error.
|
| 205 |
0C |
VIO data sets could not be checkpointed for a subsequent automatic
restart. Any checkpoints taken during this step are ineligible for
automatic restarts; however, deferred restarts are possible if the
VIO data sets are made DUMMY. An automatic restart cannot occur until
a new and successful checkpoint is taken. Programmer Response: An
error occurred while checkpointing VIO data sets to the job journal.
Deferred restarts may be accomplished on the checkpoint entry; however,
the VIO data sets must be made DUMMY. Locate and correct the error.
|
| 206 |
08 |
A VTAM®® ACB
was open when a CHKPT was attempted. Programmer Response: Ensure
that all VTAM® ACBs
are closed prior to issuing CHKPT.
|
| 207 |
0C, S13F |
Failure in the subsystem interface when checkpointing or restarting
subsystem data sets. Programmer Response: Probable subsystem
error. Contact your software support personnel.
|
| 208 |
08 |
Erroneous data exists in tape for the new checkpoint data set
presented by the user. The integrity of this data set is uncertain
and therefore unusable. Programmer Response: If the new
checkpoint data set is a sequential data set, the failure occurred
because the data set was open for MOD and residual data was found.
Either remove the MOD disposition, reinitialize the data set to an
empty status, or reallocate the data set. If the data set is a PDS,
the failure occurred as a result of residual members in the directory.
Either scratch the members or reallocate the data set.
|
| 209 |
08 |
Another user DCB is concurrently open to the checkpoint data
set presented by the user. Programmer Response: Remove
the code that violates this restriction, or change the DD statement
for the checkpoint data set.
|
| 210 |
08 |
The checkpoint data set presented by the user was defined with
DISP=SHR. Programmer Response: Change the JCL to reflect
a disposition other than SHR for the checkpoint data set.
|
| 211 |
08 |
An attempt to create a new checkpoint data set has failed because
it resides on an insecure volume. Programmer Response: The
candidate volume for a checkpoint data set was rejected by the operator
as not being secure. Contact installation personnel and verify the
eligibility of the volume for creating checkpoint data sets.
|
| 213 |
08 |
The checkpoint data set offered by the user is a subsystem
data set. Subsystem data sets cannot be used as checkpoint data sets.
Programmer Response: Correct the JCL and resubmit the job.
|
| 214 |
08 |
The new checkpoint data set offered by the user exists on a
shared direct access device. Concurrent opens cannot be controlled;
therefore, the data set is unacceptable. Programmer Response: Contact
operations personnel to ensure that this does not occur. See also Coding the DD Statement for a Checkpoint Data Set.
|
| 215 |
18 |
An error occurred while restoring the purged I/O operations.
A checkpoint entry was successfully written; however, continuation
of the user's program may produce errors. Programmer Response: Locate
and correct the error.
|
| 216 |
S13F |
Residual subpool allocations in the user's region prevented
a successful reallocation of the user's checkpoint-time region image.
Programmer Response: Locate and correct the error. Possible
system problem.
|
| 219 |
S13F |
There is a password error for a password-protected tape data
set. Programmer Response: Obtain the proper password for
the password-protected data set.
|
| 220 |
S13F |
The data set control block (DSCB) address of a data set to
be repositioned has changed since the checkpoint was taken. Programmer
Response: If possible, return the volume to the condition it was
in at checkpoint.
|
| 221 |
S13F |
The wrong password was given for a password-protected data
set that was to be repositioned. Programmer Response: Obtain
the proper password for the password-protected data set.
|
| 222 |
S13F |
The tape data set name, recorded in header label 1, has changed
since the checkpoint was taken. Programmer Response: If
possible, return the volume to the condition it was in at checkpoint.
|
| 224 |
08 |
An open data set has a type of ACB that checkpoint does not
support. Checkpoint supports VSAM ACB's and an ACB that the system
builds when the user opens a DCB for a subsystem data set, such as
spooled data sets. Programmer Response: Ensure that all
data sets of this type are closed prior to issuing the checkpoint.
|
| 240 |
0C, S13F |
A recovery (ESTAE) environment could not be established. Programmer
Response: Probable system error. Contact your software support
personnel.
|
| 241 |
0C, S13F |
An indeterminate error occurred when processing VSAM data sets.
Programmer Response: Locate and correct the error using
the diagnostic information provided.
|
| 242 |
0C, S13F |
A machine check occurred while processing VSAM data sets. Programmer
Response: If the machine check was transitory, resubmit the job.
Otherwise, have the problem fixed before resubmitting the job.
|
| 243 |
S13F |
An invalid SSCR record was encountered in the checkpoint data
set entry when repositioning VSAM data sets. This is a probable system
logic error. Programmer Response: Resubmit the job, selecting
another checkpoint entry. Be alert for a possible security violation.
|
| 250 |
08 |
SYS1.IMAGELIB data set open with the IMGLIB macro when checkpoint
taken. Programmer Response: Ensure that all IMAGELIB DCBs
are closed prior to issuing CHKPT. See also IMGLIB.
|
| 251 |
S23F |
A data set that was not a checkpoint data set at checkpoint
time was found to be open as a secure checkpoint data set at restart
time. Programmer Response: Ensure the proper data set volume
was mounted at restart time. Also, verify the status of the subject
volume by contacting the operations personnel. Be alert for a possible
security violation.
|
| 252 |
S23F |
In a job using more than one checkpoint data set, one of the
checkpoint data sets (not the one used for restart) was deemed not
secure. Programmer Response: Ensure the proper data set
volume was mounted at restart time. Also verify the status of the
subject volume by contacting the operations personnel. Be alert for
a possible security violation.
|
| 255 |
S13F, S23F |
Security violation—user not authorized to access a RACF®® protected data
set at restart. Programmer Response: See IHJ101I or IHJ102I
for information. Be alert for a possible security violation.
|
| 513 |
14 |
An internal error was detected for a bad parameter list identifier.
Programmer Response: This is probably an error in checkpoint/restart
record management. Contact your software support personnel.
|
| 514 |
14 |
An internal error was detected for an incorrect parameter list
level. Programmer Response: This is probably an error in
checkpoint/restart record management. Contact your software support
personnel.
|
| 515 |
14 |
An internal parameter list is too short. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 516 |
14 |
An internal storage list has been invalidated. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 517 |
14 |
More than one internal requester flag was selected. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 518 |
14 |
A reserved field in an internal parameter list is not zeros.
Programmer Response: This is probably an error in checkpoint/restart
record management. Contact your software support personnel.
|
| 519 |
14 |
An invalid request code was passed in an internal parameter
list for record management processing. Programmer Response: This
is probably an error in checkpoint/restart record management. Contact
your software support personnel.
|
| 520 |
14 |
A write request was made with an invalid record address. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 521 |
14 |
A write request was made with an invalid record length. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 522 |
14 |
No record header address was provided in a write request and
the record ID is for a record type that requires a separate record
header. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
| 523 |
14 |
No record header length was provided in a write request when
a record header was provided. Programmer Response: This
is probably an error in checkpoint/restart record management. Contact
your software support personnel.
|
| 524 |
14 |
The caller of an internal request is an input function and
requested an output operation or vice versa. Programmer Response: This
is probably an error in checkpoint/restart record management. Contact
your software support personnel.
|
| 526 |
14 |
A DCB address was not passed on an OPEN for output. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 527 |
14 |
No length was specified on a write request for a record appendage.
Programmer Response: This is probably an error in checkpoint/restart
record management. Contact your software support personnel.
|
| 528 |
14 |
Error positioning to the checkpoint data set. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 529 |
14 |
An OPEN for input or output must precede any other operation
requests. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
| 530 |
20 |
An invalid record type was found in the checkpoint data set.
Programmer Response: This is probably an error in checkpoint/restart
record management. Be alert for a possible security violation. Contact
your software support personnel.
|
| 531 |
20 |
An unrecognizable record code was found in the checkpoint data
set. Programmer Response: This is probably an error in
checkpoint/restart record management. Be alert for a possible security
violation. Contact your software support personnel.
|
| 533 |
12 |
A checkpoint/restart GETMAIN request received a nonzero return
code. Programmer Response: This is probably an error in
checkpoint/restart record management. Contact your software support
personnel.
|
| 537 |
12 |
An attempt to open the checkpoint data set failed. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 538 |
20 |
A buffer with data was found when none was expected. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 539 |
20 |
A buffer that should have been full was found to be only partially
filled. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
| 540 |
14 |
The storage list pointer in an internal parameter list is zero.
Programmer Response: This is probably an error in checkpoint/restart
record management. Contact your software support personnel.
|
| 541 |
14 |
An attempt to do a DEB validity check failed. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 542 |
14 |
The record code passed for a write request is an end-of-block
code. This code can not be passed as a record code. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 543 |
14 |
A request to write a record included a record too big for a
buffer and of a type that can not be split. Programmer Response: This
is probably an error in checkpoint/restart record management. Contact
your software support personnel.
|
| 544 |
08 |
A checkpoint ID was specified that is not a member of the checkpoint
PDS. Programmer Response: This is probably an error in
checkpoint/restart record management. Possible user error. Contact
your software support personnel.
|
| 545 |
08 |
An OPEN for input was attempted to a data set that is not a
secure checkpoint data set. Programmer Response: This is
probably an error in checkpoint/restart record management. Contact
your software support personnel.
|
| 546 |
08 |
A requested checkpoint ID could not be found in the checkpoint
data set. Programmer Response: This is probably an error
in checkpoint/restart record management. Possible user error. Contact
your software support personnel.
|
| 547 |
20 |
A buffer that should have been empty was marked full. Programmer
Response: This is probably an error in checkpoint/restart record
management. Contact your software support personnel.
|
| 548 |
08 |
A volume switch occurred while writing a checkpoint entry in
the checkpoint data set. Programmer Response: This is probably
an error in checkpoint/restart record management. Contact your software
support personnel.
|
| 549 |
14 |
A request to write an SSCR record was passed with an incorrect
header length. Programmer Response: This is probably an
error in checkpoint/restart record management. Contact your software
support personnel.
|
| 550 |
14 |
A request to write an SSCR record was passed with nonzero values
in reserved fields. Programmer Response: This is probably
an error in checkpoint/restart record management. Contact your software
support personnel.
|
| 551 |
14 |
A request to write an SSCR record was passed with its data
length set to zero. Programmer Response: This is probably
an error in checkpoint/restart record management. Contact your software
support personnel.
|
| 552 |
14 |
A request to write an SSCR record was passed with the DCB address
set to zero. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
| 553 |
14 |
A request to write a record was passed with an unknown record
code. Programmer Response: This is probably an error in
checkpoint/restart record management. Contact your software support
personnel.
|
| 554 |
14 |
The DCB passed for OPEN for output was not a checkpoint protected
DCB. Programmer Response: This is probably an error in
checkpoint/restart record management. Contact your software support
personnel.
|
| 555 |
08 |
The ddname passed in an open for input request is not allocated.
Programmer Response: This is probably an error in checkpoint/restart
record management. Contact your software support personnel.
|
| 556 |
12 |
On a call to SWA to read a JFCB, a nonzero return code was
received. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
| 557 |
14 |
No ddname was passed on an OPEN for input request by scheduler
restart. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
| 558 |
14 |
No checkpoint ID address was passed on an OPEN for input request
by scheduler restart. Programmer Response: This is probably
an error in checkpoint/restart record management. Contact your software
support personnel.
|
| 559 |
14 |
A zero length was passed for the checkpoint ID by scheduler
restart. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
| 560 |
14 |
No checkpoint header record address was passed on an OPEN for
input request by scheduler restart. Programmer Response: This
is probably an error in checkpoint/restart record management. Contact
your software support personnel.
|
| 561 |
14 |
A zero length was passed for the checkpoint header record by
scheduler restart. Programmer Response: This is probably
an error in checkpoint/restart record management. Contact your software
support personnel.
|
| 562 |
12 |
An error occurred while calculating block size for the checkpoint
data set. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
| 563 |
12 |
An optimum block size could not be calculated for the checkpoint
data set. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
| 564 |
08 |
An attempt was made by scheduler restart to open a checkpoint
data set that was created on a release of DFP or MVS/SP that did not have complete
scheduler checkpoint support. Programmer Response: This
is probably an error in checkpoint/restart record management. Contact
your software support personnel.
|
| 565 |
12 |
A nonzero return code was returned from an ESTAE service request.
Programmer Response: This is probably an error in checkpoint/restart
record management. Contact your software support personnel.
|
| 566 |
08 |
The extents of a DASD checkpoint data set have been extended.
Programmer Response: This is probably an error in checkpoint/restart
record management. Contact your software support personnel.
|
| 567 |
14 |
A record split was requested for a record type that cannot
be split. Programmer Response: This is probably an error
in checkpoint/restart record management. Contact your software support
personnel.
|
z/OS DFSMSdfp Checkpoint/Restart
Copyright IBM Corporation 1990, 2014