Welcome
Reference information
The reference sections of the information contain reference information that you need when you use CICS® VR.
CICS® VR Messages and abend codes
This section includes the messages and abend codes that are used by CICS VR, and also includes instructions to successfully complete the recovery of CICS VSAM data.
CICS® VR messages
Messages and their format.
DWW0550W
A gap is encountered between record nn1 and record nn2 on log dddd when reading backward. Processing continues.

What's new in CICS VR 6.3
CICS® VR 6.3 contains these changes.
Operating environment
CICS® VR uses logs to recover your VSAM data.
CICS VR Overview
Getting Started
CICS® VR and CICS® TS
CICS VR Exits
Running CICS® VR forward recovery
CICS® VR forward recovery consists of a restore and then forward recovery.
Running CICS® VR backup
The information in the following topics describe how to take a backup using CICS® VR. The panels and secondary windows are in the sequence that they are displayed during a backup job generation.
Running CICS® VR reorganization
You can reorganize a VSAM sphere using CICS® VR. VSAM sphere reorganization can increase the space of a sphere and its alternate indexes. It can also change the control interval sizes for a sphere's components.
Working with other VSAM sphere list pull-down menus
The CICS® VR recovery and backup functions are typically accessed using the Utilities pull-down menu after selecting VSAM spheres.
Working with CICS® Backout Failed spheres
The CICS® Backout Failed sphere list shows the CICS spheres registered for manual recovery or reorganization after CICS notification of a backout failure.
Working with logs
Using ISMF data set lists with CICS® VR
CICS® VR is integrated with ISMF so that you can create a CICS VR recovery job for the data sets in an ISMF data set list by entering the VSAMREC line operator or list command. When you enter the VSAMREC line operator or list command, the necessary CICS VR panels are called and you can create a recovery job for the VSAM sphere.
Running CICS® VR manually
IBM® recommends that you use the CICS® VR panel interface to create recovery jobs for your VSAM spheres. Using the CICS VR panel interface eliminates the need for you to manually keep track of daily update activity, logs, backups, etc. Also, the CICS VR panel interface automatically creates the recovery JCL for you.
Running CICS® VR batch backout
The CICS® VR batch backout utility allows you to remove updates that were made to KSDS, ESDS, RRDS, and VRRDS VSAM spheres by steps in a batch job. This section describes how to run the CICS VR batch backout utility.
Understanding CICS® VR reports
The CICS® VR forward recovery and batch backout utilities produce a set of reports upon successful completion. The reports are written to the data set allocated to the DWWPRINT ddname. However, the set of reports written for the forward recovery backout utilities differ from the set of reports written for the batch backout utilities.
Understanding IBM® program support
The IBM® Customer Engineering Program Support structure helps you resolve problems with IBM products, and ensures that you can make the best use of your IBM computing systems.
Problem determination procedures
If you have to contact IBM® personnel about a CICS® VR problem, you must classify and describe the problem.
Diagnosing the causes of abends
You can determine the cause of a CICS® VR abend in a number of ways.
Reference information
The reference sections of the information contain reference information that you need when you use CICS® VR.
- CICS VR command reference
  Descriptions of the CICS VR command rules and how to read the syntax diagrams.
- CICS® VR commands
  A table of descriptions of CICS® VR functions and commands used with CICS TS.
- CICS® VR Messages and abend codes
  This section includes the messages and abend codes that are used by CICS VR, and also includes instructions to successfully complete the recovery of CICS VSAM data.
  - CICS® VR messages
    Messages and their format.
    - DWW0000T
      Module: mmmmm, reason: rrrr.
    - DWW0010I
      CICS® VR is started at yy⁄mm⁄dd hh:mm:ss.
    - DWW0011I
      CICS® VR processing complete. Maximum condition code is cc.
    - DWW0100S
      Too many positional parameters are specified after pppp.
    - DWW0101S
      Constant vvvv exceeds length limit.
    - DWW0102I
      Above text bypassed until next command. Condition code is 12.
    - DWW0105S
      Delimiter n is not properly preceded by a constant or a keyword.
    - DWW0106I
      An improperly placed comma is found and ignored.
    - DWW0107I
      Remainder of command input stream is ignored.
    - DWW0108S
      A left parenthesis is missing following the keyword kkkk.
    - DWW0109S
      A right parenthesis is missing after vvvv.
    - DWW0110S
      Invalid or missing parentheses for specifying repeated subparameter list.
    - DWW0111S
      Keyword kkkk is incorrect.
    - DWW0112S
      An invalid left parenthesis appears after pppp.
    - DWW0113S
      Keyword kkkk appears too often.
    - DWW0114S
      A hex or binary constant is specified improperly.
    - DWW0116S
      Too many repeated subparameter lists appear.
    - DWW0117S
      Verb name cccc is unknown.
    - DWW0118S
      An improper numeric digit is found in pppp.
    - DWW0119S
      Constant vvvv is not within the value range.
    - DWW0120I
      Warning: command-end delimiter appears within apostrophes.
    - DWW0121S
      Too many constants are in the list beginning at vvvv.
    - DWW0122S
      Required (sub)parameter of pppp is missing.
    - DWW0123S
      Inconsistent parameters appeared involving kkkk.
    - DWW0124I
      Too many right parentheses are found. Excess ignored.
    - DWW0125I
      Warning: too few right parentheses are found at end of command.
    - DWW0126S
      Input stream end-of-file is found before end of command.
    - DWW0128S
      Command cccc appears too often.
    - DWW0129S
      Item vvvv does not adhere to restrictions.
    - DWW0130I
      Above text is bypassed until the next command. Condition code is 12.
    - DWW0132I
      Remainder of command input stream is ignored.
    - DWW0133I
      CICS® VR V1 command is found and ignored.
    - DWW0134I
      Redundant or CICS® VR V1 parameter(s) are found and ignored.
    - DWW0135S
      The ALLOCATE command contains an invalid parameter, or the number of values in the volume and unit parameters are inconsistent.
    - DWW0136S
      Data set name dddd in the RELATE command is not a path but a base cluster.
    - DWW0137S
      The number of values in the FILEID and CICSID keywords are inconsistent.
    - DWW0150S
      Invalid character appears at position qq in the date and time field starttime⁄stoptime.
    - DWW0151S
      Invalid day number appears in date and time field starttime⁄stoptime.
    - DWW0152S
      Invalid number of hours appears in date⁄time field starttime⁄stoptime.
    - DWW0153S
      Invalid number of minutes appears in date and time field starttime⁄stoptime.
    - DWW0154S
      Invalid number of seconds appears in date and time field starttime⁄stoptime.
    - DWW0155S
      Invalid day number appears in date and time field for a non-leap year starttime⁄stoptime.
    - DWW0156S
      Incomplete field specification appears at position xx in the date and time field starttime⁄stoptime.
    - DWW0157S
      Too many characters are in the date and time field.
    - DWW0158S
      The STARTTIME value is higher than STOPTIME value.
    - DWW0162S
      Duplicate FCTCOMP commands are specified for ddname ddn.
    - DWW0165S
      dddd appears in more than one RECOVER or BACKOUT command.
    - DWW0169E
      Data set dddd is restored from a backup-while-open copy but the extracted recovery point time of vvvv from the ICF catalog cannot be used.
    - DWW0170S
      For data set dddd the registered time of yydddhhmmss comes before the specified STARTTIME.
    - DWW0171S
      For data set dddd the registered time of yydddhhmmss comes after the specified STOPTIME.
    - DWW0172W
      For data set dddd the registered time of yydddhhmmss comes after the specified STARTTIME.
    - DWW0175I
      For data set dddd recovery will start from the registered time (or user STARTTIME if supplied) of yydddhhmmss.
    - DWW0176E
      GMT must not be specified for data set dddd in the STARTTIME or STOPTIME parameter because there is a BWO recovery point for this data set.
    - DWW0177E
      Unexpected result attempting to use the VSAM IGWARLS facility for VSAM sphere dddd. The VSAM IGWARLS load module was not available.
    - DWW0178E
      Unexpected result from the VSAM IGWARLS facility for VSAM sphere dddd. The VSAM IGWARLS load module was not available. The return code is aa, and the reason code is bb. The problem determination data is X'cc'.
    - DWW0179E
      The ARCGIVER server for the ARCXTRCT macro was not available when processing VSAM sphere dddd.
    - DWW0180E
      An error occurred while using the ARCXTRCT macro for VSAM sphere dddd. The return code is X'aa' and the reason code is X'bb'.
    - DWW0181I
      For data set dddd recovery will start from the default time yydddhhmmss. This data set had version but no STARTTIME specified.
    - DWW0182E
      Specified backup dddd1 of VSAM sphere dddd2 is not an online backup.
    - DWW0183E
      The STARTTIME value does not match with the timestamp in the RCDS for backup dddd1 of VSAM sphere dddd2. Please change or omit STARTTIME value.
    - DWW0200S
      Both the RECOVER and the BACKOUT commands are specified.
    - DWW0201S
      No RECOVER or BACKOUT command is specified.
    - DWW0202S
      Logs are defined both via the ALLOCATE command and via the JCL.
    - DWW0203S
      No logs are defined via the ALLOCATE command or the JCL.
    - DWW0204S
      A GDG or concatenated DD statements defining logs is specified for backout processing.
    - DWW0205S
      The DD statements that define logs are incorrect.
    - DWW0206S
      The exit load module xxxx cannot be found.
    - DWW0208S
      Both the MVSLOG and the BACKOUT commands are specified. You cannot specify MVSLOG with the BACKOUT command.
    - DWW0209S
      A GMT value is specified for a time field. This is only supported if the MVSLOG command is also specified.
    - DWW0210I
      Error condition is ignored as specified in the error exit. Processing continues.
    - DWW0211S
      An error condition occurred. Processing terminates as specified in the error exit.
    - DWW0212S
      Preceding I⁄O error has forced termination.
    - DWW0213I
      Label record is missing. Statistics and start time comparison might be inaccurate.
    - DWW0214I
      The log dddd contains no relevant records.
    - DWW0215S
      Both the MVSLOG command with keyword CATALOG or NAME and the ALLOCATE command are specified. When recovering with an MVS™ log stream, no other log can be specified as input to CICS® VR.
    - DWW0216S
      You cannot use the old type of preapply exit when you are recovering with an MVS™ log stream.
    - DWW0217S
      The data sets that were specified for the shadow function have earlier been shadowed separately.
    - DWW0241E
      Preceding I/O error has forced termination.
    - DWW0242E
      Open of data set dddd failed. VSAM return codes are R15=X'cc', FDBK=X'nn'.
    - DWW0243E
      An illegal record length is in the after-image record. The data set is dddd .
    - DWW0244I
      The keyword AUTOJOURNALS was specified in the RECOVER command but no MVSLOG command was found. The keyword AUTOJOURNALS is only supported together with the MVSLOG command.
    - DWW0400S
      The DD statement that defines logs for a forward recovery run is incorrect.
    - DWW0401S
      The first record on the current log is not a label record.
    - DWW0450W
      A gap is encountered between record nn1 and record nn2 on log dddd when reading forward. Processing continues.
    - DWW0451S
      A gap is encountered between record nn1 and record nn2 on log dddd when reading forward. Processing terminates.
    - DWW0452W
      Record nn1 is found out of sequence when reading forward on log dddd. The preceding record is nn2. Processing continues.
    - DWW0453S
      Record nn1 is found out of sequence when reading forward on log dddd. The preceding record is nn2. Processing terminates.
    - DWW0454W
      An unexpected zero sequence number is found when reading forward on log dddd. The preceding record is nn1. Processing continues.
    - DWW0455S
      An unexpected zero sequence number is found when reading forward on log dddd. The preceding record is nn1. Processing terminates.
    - DWW0456W
      A gap is encountered when switching logs and reading forward. Record nn1 on log dddd1 precedes record nn2 on log dddd2. Processing continues.
    - DWW0457S
      A gap is encountered when switching logs and reading forward. Record nn1 on log dddd1 precedes record nn2 on log dddd2. Processing terminates.
    - DWW0458W
      A record is found out of sequence when switching logs and reading forward. Record nn1 on log dddd1 precedes record nn2 on log dddd2. Processing continues.
    - DWW0459S
      A record is found out of sequence when switching logs and reading forward. Record nn1 on log dddd1 precedes record nn2 on log dddd2. Processing terminates.
    - DWW0460W
      A record with a zero sequence number is found when switching logs and reading forward. Record nn1 on log dddd1 precedes record nn2 on log dddd2. Processing continues.
    - DWW0461S
      A record with a zero sequence number is found when switching logs and reading forward. Record nn1 on log dddd1 precedes record nn2 on log dddd2. Processing terminates.
    - DWW0462I
      A preformatted log dddd does not have an end-of-file marker.
    - DWW0470S
      A record that is too short to contain the file control system prefix is found on the log dddd. The minimum expected length is nn1. The actual length is nn2.
    - DWW0471S
      The file control system prefix of a record found on the log dddd is too long. The maximum expected length is nn1. The actual length is nn2.
    - DWW0472S
      A change from CICS® Version 2 record types to CICS Version 3 record types is found on, or at the start of log dddd. Processing terminates.
    - DWW0473S
      A change from CICS® Version 3 record types to CICS Version 2 record types is found on, or at the start of log dddd. Processing terminates.
    - DWW0474S
      A DSNAME record found on log dddd is too short. The minimum expected length was nn1. The actual record length was nn2. Processing terminates.
    - DWW0475S
      A DSNAME record with an incorrect version has been found on log dddd. Processing terminates.
    - DWW0476S
      A record with an invalid access path key offset or length is found on log dddd. The offset is nn1, and the length is nn2. Processing terminates.
    - DWW0477S
      A record with an invalid base key offset or length is found on log dddd. The offset is nn1, and the length is nn2. Processing terminates.
    - DWW0478S
      A record with an invalid redo part offset or length is found on log dddd. The offset is nn1, and the length is nn2. Processing terminates.
    - DWW0479W
      Log records with FCT entry name fff for the data set dddd are processed as being in variable format. But nn1 out of nn2 add or update log records did not meet variable format checks.
    - DWW0480W
      Log records with FCT entry name fff for the data set dddd are processed as being in fixed format. But all the nn add or update log records met variable format checks.
    - DWW0481S
      The record format of log dddd is fixed.
    - DWW0500A
      Additional logs are needed to finish backout. Enter the name of a log or STOP.
    - DWW0501A
      Log dddd is not allocated. Enter the new name or STOP.
    - DWW0502S
      Not enough logs are supplied. Processing terminates.
    - DWW0503A
      **** Reply is invalid **** Please enter the name of the log or STOP.
    - DWW0504S
      The time limit of the log is passed but one or more tasks are not completely backed out. Current® log is dddd. Processing terminates.
    - DWW0505S
      Delete of a record on an ESDS is requested. The data set name is dddd. Processing terminates.
    - DWW0507S
      No updates are applied or the backout is incomplete for dddd.
    - DWW0550W
      A gap is encountered between record nn1 and record nn2 on log dddd when reading backward. Processing continues.
    - DWW0551S
      A gap is encountered between record nn1 and record nn2 on log dddd when reading backward. Processing terminates.
    - DWW0552W
      A record nn1 is found out of sequence when reading backward on log dddd. The preceding record is nn2. Processing continues.
    - DWW0553S
      Record nn1 is found out of sequence when reading backward on log dddd. The preceding record is nn2. Processing terminates.
    - DWW0554W
      An unexpected zero sequence number was found when reading backward on log dddd. The zero record precedes record nn1. Processing continues.
    - DWW0555S
      An unexpected zero sequence number is found when reading backward on log dddd. The zero record precedes record nn1. Processing terminates.
    - DWW0556W
      A gap is encountered when switching logs and reading backward. Record nn2 on log dddd2 precedes record nn1 on log dddd1. Processing continues.
    - DWW0557S
      A gap is encountered when switching logs and reading backward. Record nn2 on log dddd2 precedes record nn1 on log dddd1. Processing terminates.
    - DWW0558W
      A record is found out of sequence when switching logs and reading backward. Record nn2 on log dddd2 precedes record nn1 on log dddd1. Processing continues.
    - DWW0559S
      A record is found out of sequence when switching logs and reading backward. Record nn2 on log dddd2 precedes record nn1 on log dddd1. Processing terminates.
    - DWW0560W
      A record with a zero sequence number is found when switching logs and reading backward. Record nn2 on log dddd2 precedes record nn1 on log dddd1. Processing continues.
    - DWW0561S
      A record with a zero sequence number is found when switching logs and reading backward. Record nn2 on log dddd2 precedes record nn1 on log dddd1. Processing terminates.
    - DWW0562S
      Connect to the MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW0563S
      Start browse of MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW0564S
      End browse of MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW0565S
      Disconnect from MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW0566S
      Browse of MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW0567I
      MVS™ log stream name llll is specified as input for recovery of dddd. However, the catalog returns MVS log stream name llll1. The name specified as input is used for recovery.
    - DWW0568S
      The MVS™ log stream name for sphere dddd could not be retrieved since the service was not available.
    - DWW0569S
      The MVS™ log stream name for sphere dddd could not be retrieved. The return code is aa, and the reason code is bb. The problem determination data is cc.
    - DWW0570S
      The MVS™ log stream needed for sphere dddd1. is llll1, and the MVS log stream needed for sphere llll2 is dddd2. However, only one MVS log stream can be used as input.
    - DWW0571S
      The log type xx defined for sphere dddd does not support forward recovery on an MVS™ log stream.
    - DWW0572W
      A VSAM open record (tieup) written by the CICS® VR batch logger was found but no RCDS was allocated in forward recovery JOB.
    - DWW0600S
      Open of data set dddd failed. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0601I
      I⁄O error after a get request to the dddd data set. The key is key. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0602I
      An I⁄O occurred error after an add request to the dddd data set. The key is key. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0603I
      An I⁄O error occurred after a replace request to the dddd data set. The key is key. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0604I
      An I⁄O error occurred after a delete request to the dddd data set. The key is key. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0605I
      An I⁄O error occurred after an add request to the dddd data set. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0606S
      The VSAM data set dddd is in error. Data set type is datasettype1, original data set type is datasettype2.
    - DWW0607S
      The VSAM data set dddd is in error. Key length is length1, original key length is length2.
    - DWW0608S
      The VSAM data set dddd is in error. Maximum record length is length1, original maximum record length is length2.
    - DWW0609S
      The VSAM data set dddd is in error. Relative key position is ppp, original relative key position is qqq.
    - DWW0610S
      The VSAM data set dddd is in error. Control interval size is cisize1, original control interval size is cisize2.
    - DWW0611S
      The VSAM data set dddd is not a base cluster.
    - DWW0612S
      The data set dddd is not found in the VSAM catalog.
    - DWW0613S
      VSAM failed to build the requested resource pool. VSAM return code is R15=cc.
    - DWW0614S
      BLDVRP command: there is no buffer large enough for the dddd VSAM data set.
    - DWW0615S
      Data set dddd is not a VSAM data set.
    - DWW0616S
      An error occurred when reading the VSAM catalog. Return code is cccc-cc. Data set being processed is dddd.
    - DWW0617I
      The following dddd LSR BUFFER SIZES WILL BE USED: BUF1=N1, BUF2=N2, BUFK=NK
    - DWW0618I
      Ddname ddn relates to both dddd1 and dddd2.
    - DWW0619I
      Logging for ddname ddn is assumed to be in variable format on CICS® logs in the absence of any FCTCOMP commands.
    - DWW0620S
      An illegal record length is in the after-image record. The data set is dddd.
    - DWW0621I
      An I⁄O error occurred after a get request to the aaaa data set. The RBA⁄RRN=bbbbbbbb. VSAM return codes are R15=cc, FDBK=dd.
    - DWW0622I
      An I⁄O error occurred after an add request to the dddd data set. The RRN=cccccccc. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0623I
      An I⁄O error occurred after a replace request to the dddd data set. The RBA⁄RRN=cccccccc. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0624I
      An I⁄O error occurred after a delete request to the dddd data set. The RBA⁄RRN=cccccccc. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0625E
      A non-unique key has been encountered for a CICS® TS log update⁄delete via a path. The path name is dddd. The path key is key. Log record is ignored.
    - DWW0626I
      A path update from a CICS® TS log attempted to change the base key. The path name is dddd. The path key is key. Log record is ignored.
    - DWW0627E
      The key of access from a CICS® TS log record is not the same as the key in the log record. Data set name is dddd. Key of access is keya. Log record key is keyb. Log record is ignored.
    - DWW0628E
      BLDVRP command: specified number of buffers for buffer pool nn is too large. Maximum size allowed is nn.
    - DWW0629I
      An unexpected delete log record has been found for an ESDS. The data set name is dddd. The RBA to be deleted is cccccccc.
    - DWW0630I
      Add log records have been ignored due to matching following delete log records for an ESDS. The number of ignored records is nn. The data set name is dddd.
    - DWW0631I
      Delete log records have been ignored due to record-not-found conditions for an ESDS. The number of ignored records is nn. The data set name is dddd.
    - DWW0632I
      Update log records have been converted to add records due to record-not-found conditions for an ESDS or KSDS. The number of converted records is nn. The data set name is dddd.
    - DWW0633E
      ESDS add log records have been found whose RBA is not higher than preceding adds. The number of such records is nn. The data set name is dddd.
    - DWW0634E
      ESDS write-add RBA from CICS/ESA 4.1 log record is not equal to actual RBA used. Data set name is dddd. logged RBA is cccccccc. Actual RBA is dddddddd. Record appended to data set.
    - DWW0635I
      During the recovery of dddd, duplicate or not found conditions were encountered.
    - DWW0636S
      A non-unique path has been encountered for a CICS® TS log KSDS update or delete. The path name is dddd. Processing terminates.
    - DWW0637E
      Multiple ESDS add log records have been found whose RBA is zero. The number of such records is nn. The data set name is dddd.
    - DWW0638I
      An I⁄O error occurred after a get request to the aaaa data set. The XRBA=bbbbbbbb. VSAM return codes are R15=cc, FDBK=dd.
    - DWW0639E
      ESDS write-add XRBA from CICS® TS log record is not equal to actual XRBA used. Data set name is dddd. Logged XRBA is cccccccc. Actual XRBA is dddddddd. Record appended to data set.
    - DWW0640W
      No records were applied to dddd.
    - DWW0641I
      An I⁄O error occurred after a replace request to the dddd data set. The XRBA=cccccccc. VSAM return codes are R15=cc, FDBK=nn.
    - DWW0642I
      An unexpected delete log record has been found for an ESDS. The data set name is dddd. The XRBA to be deleted is cccccccc.
    - DWW0650S
      Open of log dddd failed.
    - DWW0651I
      Read failed for log dddd.synadinfo.
    - DWW0652S
      CICS® logging has overtaken CICS VR recovery on active log with possible integrity loss. Rerun with the archive of dddd instead.
    - DWW0653S
      Logical I⁄O error on log dddd at block number n has occurred.
    - DWW0654S
      Log data set dddd is a partitioned data set. This data set organization is not supported as a log for backout.
    - DWW0655S
      Log dddd has an invalid BB setting. For first block in a sequence the only valid settings are X'00' and X'01'. The actual setting is xx.
    - DWW0656S
      Log dddd has an invalid BB setting. For middle or last block in a sequence the only valid settings are X'03' and X'02'. The actual setting is xx.
    - DWW0701S
      Dynamic allocation of data set dddd failed. Return code-R15=cc1, MVS™ RC=cc2.
    - DWW0702I
      Dynamic deallocation of data set dddd failed. Return code-R15=cc1, MVS™ RC=cc2.
    - DWW0703S
      An error occurred when opening the data set connected to ddname ddn.
    - DWW0704S
      Read failed for the DWWIN data set, synadinfo.
    - DWW0707S
      Recovery to dddd cannot be performed as the backup-while-open flags in the ICF catalog have a setting of vvv.
    - DWW0708W
      Recovery to dddd will be performed even though the backup-while-open flags in the ICF catalog have a setting of vvv.
    - DWW0709E
      Fetch of backup-while-open flags from the ICF catalog failed for dddd. Return code = cc1, reason code = cc2.
    - DWW0710E
      Update of backup-while-open flags in the ICF catalog failed for dddd prior to cccc. Return code = cc1, reason code = cc2.
    - DWW0711I
      Backup-while-open flags in the ICF catalog are updated to vvv for dddd prior to cccc.
    - DWW0712E
      Update of backup-while-open flags in the ICF catalog failed for VSAM sphere dddd. The return code is X'cc1', and the reason code is X'cc2'.
    - DWW0715S
      Forward recovery request for data set dddd is rejected because it is a backup-while-open copy containing alternate indexes in the upgrade set.
    - DWW0720S
      The FCT entry fff refers to path dddd1 to the base cluster dddd2. However, this path is not currently associated with the base cluster. A RELATE command might be missing. Processing terminates.
    - DWW0721S
      The FCT entry fff refers to path dddd1 (via a RELATE command) to the base cluster dddd2. However, this path is not currently associated with the base cluster. Processing terminates.
    - DWW0722I
      Dynamic allocation of old CA data set dddd failed. Return code-R15=cc1, MVS™ RC=cc2.
    - DWW0723I
      Dynamic allocation of CA data set dddd failed. Return code-R15=cc1, MVS™ RC=cc2.
    - DWW0801S
      SHADOW is requested for at least one VSAM data set. However, the RCDS is not allocated. Recovery stops.
    - DWW0802S
      NOTIEUPS is specified for at least one VSAM data set. However, the RCDS is not allocated. Recovery stops.
    - DWW0901I
      Change accumulation is started at yyyy/mm/dd hh:mm:ss.
    - DWW0902I
      Change accumulation is terminated. The maximum condition code is cc.
    - DWW0903S
      Your external sort product is not at a level that supports CICS® VR processing of very large records.
    - DWW0904S
      The maximum record size bbbb for data set aaaa exceeds the maximum supported record size for change accumulation.
    - DWW0905S
      Unexpected result from the external sort product. The sort return code is aa (decimal).
    - DWW0906I
      Command processing is completed. The maximum condition code is cc.
    - DWW0907S
      The cccc command is specified more than once.
    - DWW0908S
      The cccc command is specified more than 50 times.
    - DWW0909S
      dddd appears in more than one SPHERE command.
    - DWW0910W
      dddd has backout failed records on the system log after the last backup.
    - DWW0911S
      GMT was specified as the time format for the VSAM sphere dddd, but you are using CICS/ESA® logs which do not contain GMT times.
    - DWW0912S
      GMT was specified as the time format for a VSAM sphere backup dddd, but the CA data set does not contain GMT times for that sphere.
    - DWW0913E
      Dynamic allocation of CA data set dddd failed. The SVC 99 return code is 'aa'. The SVC 99 error reason code is 'bb'. The SVC 99 information reason code is 'cc'.
    - DWW0914S
      The end-of-file is found before the end of a command.
    - DWW0915S
      The required command cccc is missing.
    - DWW0916S
      The sort work data set specified in the ddname ddn is not a disk data set.
    - DWW0917W
      No new data was found in the RCDS.
    - DWW0919I
      Unexpected result from DFSMShsm™: return code is aa, reason code is bb.
    - DWW0920S
      The VSAM sphere dddd is not found in the RCDS.
    - DWW0921S
      No backups exist for the VSAM sphere dddd.
    - DWW0922I
      An error occurred when opening the old CA data set dddd.
    - DWW0923W
      Delete of the old CA data set dddd failed.
    - DWW0924W
      All log records were not processed in the change accumulation run.
    - DWW0925W
      No default prefix for CA output dataset was found.
    - DWW0926S
      Data set dddd was not found in the catalog.
    - DWW0927S
      No mvslog name was entered in the ONLY keyword in the CA command and no name was found in the CICS® VR RCDS.
    - DWW0928S
      The ddname DWWCA, which is required for this CA utility, is not present in the JCL.
    - DWW0929S
      The keyword ALL in the SPHERE command is only allowed if the keyword ONLY is specified in the GROUP command.
    - DWW1101I
      The archive utility is started at yy⁄mm⁄dd hh:mm:ss.
    - DWW1102I
      The archive utility is terminated. The maximum condition code is cc.
    - DWW1103S
      The ddname ddn, which is required as input to archive, is not present in the JCL.
    - DWW1104S
      The exit load module xxxx cannot be found.
    - DWW1105S
      The ddname ddn has concatenated DD statements present in the JCL.
    - DWW1106W
      SCAN or REPORTONLY was requested but no log of logs entries are found in the RCDS.
    - DWW1107S
      CICS® VR is not licensed for use on the system.
    - DWW1110E
      The date xx or the time xx is not in the correct format.
    - DWW1111E
      The block number n is not in the correct format.
    - DWW1112E
      The date xx or the time xx is not in the correct format.
    - DWW1113I
      This log has been previously archived.
    - DWW1114E
      The date xx or the time xx is not in the correct format.
    - DWW1115E
      The date xx or the time xx is not in the correct format.
    - DWW1116S
      There is a duplicate key in the RCDS.
    - DWW1117E
      The date xx or the time xx is not in the correct format.
    - DWW1118I
      Register of log of logs dddd is successful.
    - DWW1119I
      Deregister of log of logs dddd is successful.
    - DWW1121E
      The MVS™ log stream llll is already registered in the RCDS.
    - DWW1122W
      The MVS™ log stream llll is not found in the RCDS.
    - DWW1123E
      The MVS™ log stream llll is not found in the RCDS.
    - DWW1124S
      Connect to the MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW1125S
      Start browse of MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW1126S
      End browse of MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW1127S
      Disconnect from MVS™ log stream llll failed. The return code is aa and the reason code is bb. The answer area contains cc.
    - DWW1128S
      Browse of MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW1129S
      Browse of MVS™ log stream llll failed. The return code is aa, and the reason code is bb. The answer area contains cc.
    - DWW1130I
      Automatic delete of blocks before yy.ddd hh:mm:ss GMT time was successful for MVS™ log stream llll.
    - DWW1131W
      An incorrectly placed comma at pppp is ignored.
    - DWW1132W
      An incorrectly placed comma in the parm string is ignored.
    - DWW1133S
      The keyword cccc appears too many times.
    - DWW1134S
      The command cccc is undefined.
    - DWW1135S
      The command is missing or the format is invalid.
    - DWW1136W
      A missing end of comment is assumed at the end of the statement.
    - DWW1137W
      A missing end quote is assumed at the end of the statement.
    - DWW1139S
      An invalid right parenthesis is inserted in pppp.
    - DWW1140S
      An invalid right parenthesis is inserted in the parm string.
    - DWW1141S
      An invalid value vvvv is specified or a keyword is misspelled.
    - DWW1142S
      An invalid separator is specified after pppp.
    - DWW1143S
      A value is missing after pppp.
    - DWW1144S
      Too many left parentheses are inserted in pppp or an invalid value is inserted.
    - DWW1145S
      Too many left parentheses are inserted in the parm string.
    - DWW1146S
      A left parenthesis is missing before pppp.
    - DWW1147S
      An invalid comma is inserted in pppp.
    - DWW1148W
      A missing right parenthesis is assumed after the statement.
    - DWW1149S
      The required keyword kkkk is missing.
    - DWW1150S
      The required keyword is missing. Specify either kkkk or kkkk.
    - DWW1151S
      An invalid item vvvv is inserted in the keyword.
    - DWW1152S
      The keyword(s) for command cccc is missing. At least one keyword must be specified.
    - DWW1153S
      The empty quoted string is invalid for the keyword kkkk.
    - DWW1154S
      A required keyword for command cccc is missing.
    - DWW1155S
      Mutually exclusive keywords are specified. Both cccc1 and cccc2 cannot be specified.
    - DWW1156S
      Mutually exclusive keywords are specified. Both cccc1 and cccc2 cannot be specified.
    - DWW1157S
      Command cccc1 is ignored for command cccc2.
    - DWW1158S
      The entered stop time yyyydddhhmmss is earlier than the start time yyyydddhhmmss.
    - DWW1171S
      The program failed to allocate a work area.
    - DWW1172S
      An open error occurred for the data set allocated to the ddname ddn.
    - DWW1173I
      Command processing is complete. The maximum condition code is cc.
    - DWW1174S
      The end-of-file is found before the end of a command.
    - DWW1175S
      An invalid value vvvv is inserted in the keyword kkkk.
    - DWW1176S
      The required keyword kkkk is missing in the command cccc.
    - DWW1177W
      Duplicate statements were inserted for the command cccc with the ddname ddn. The statement is ignored.
    - DWW1178S
      Contradictory statements are inserted for the command cccc with the ddname ddn.
    - DWW1179S
      An invalid value vvvv is inserted in the keyword kkkk.
    - DWW1180S
      The command cccc is specified more than once.
    - DWW1181S
      The required command cccc is missing.
    - DWW1182I
      The following was entered as input on the parm string:
    - DWW1183S
      The required keyword kkkk is missing in the command cccc.
    - DWW1184S
      The log of logs llll is specified more than once.
    - DWW1201S
      A record that is too short to contain the file control system prefix is found on the log dddd. The minimum expected length is nn1. The actual length is nn2.
    - DWW1202S
      The file control system prefix of a record found on the log dddd is too long. The maximum expected length is nn1. The actual length is nn2.
    - DWW1203S
      The ddname ddn, which is required for the copy, is not present in the JCL.
    - DWW1204S
      The record format of log dddd is fixed.
    - DWW1205S
      The block is too short to contain a BDW. The length is nn1.
    - DWW1206S
      The block length is not the same as in the BDW. The block length is nn1 and the length in the BDW is nn2.
    - DWW1207S
      The record length nn1 is too long for the blocksize nn2 of the output data set dddd.
    - DWW1208S
      The record format of log dddd is fixed.
    - DWW1209S
      An open error occurred for the data set allocated to the ddname ddn.
    - DWW1210S
      An open error occurred for the report data set.
    - DWW1211S
      An open error occurred for the DWWIN data set.
    - DWW1221S
      A backout failing log record (BOFLGREC) found on the log dddd is too short. The minimum expected length is nn1. The actual length is nn2.
    - DWW1222S
      The first record on the log dddd is not a label record.
    - DWW1223W
      The log dddd contains no relevant records.
    - DWW1224W
      The input log is empty.
    - DWW1225S
      The date xx or the time xx is not in the correct format on the first label record.
    - DWW1226S
      A label record that is too short to be from a CICS® Version 2 or Version 3 log is found on the log dddd. The minimum expected length is nn1. The actual length is nn2.
    - DWW1227S
      A label record with an incorrect version is found on the log dddd.
    - DWW1228S
      The log ID jj1, entered as input, differs from the ID jj2 found on the log dddd.
    - DWW1229S
      A change in log ID from jj1 to jj2 is found on the log dddd.
    - DWW1230E
      A time decrease is found on the log dddd.
    - DWW1231E
      An out of sequence label is found on the log dddd. The previous sequence number is nn1. The current sequence number is nn2.
    - DWW1232E
      A zero sequence number is found on the log dddd. The previous sequence number is nn1. The current sequence number is nn2.
    - DWW1233E
      A gap in sequence number is found on the log dddd. The previous sequence number is nn1. The current sequence number is nn2.
    - DWW1234S
      A DSNAME record that is too short is found on the log dddd. The minimum expected length is nn1. The actual length is nn2.
    - DWW1235S
      A DSNAME record with an incorrect version is found on the log dddd.
    - DWW1236W
      Log records with FCT entry name fff for the data set dddd are processed as being in variable format. However, nn1 out of nn2 add or update log records did not meet variable format checks.
    - DWW1237W
      Log records with FCT entry name fff for the data set dddd are processed as being in fixed format. However, all of the nn add or update log records met variable format checks.
    - DWW1238S
      Log of logs llll has been deleted from the RCDS during the scan.
    - DWW1239S
      Log of logs llll has been updated from the RCDS during the scan.
    - DWW1240I
      Scan failed because of the previous errors. No updates will be made to the RCDS.
    - DWW1241I
      No blocks were read for log of logs llll.
    - DWW1242S
      Log of logs llll was not found in the RCDS.
    - DWW1243E
      The attempt to bind the VSAM RLS locks for VSAM sphere dddd, LOG (llll) was not successful. The return code is cc, and the reason code is cc. The error data is cc.
    - DWW1244E
      The attempt to unbind the VSAM RLS locks for VSAM sphere dddd, LOG (llll) was not successful. The return code is cc, and the reason code is cc. The error data is cc.
    - DWW1251W
      No recovery needed for VSAM sphere dddd.
    - DWW1252W
      A problem is found with log llll for VSAM sphere dddd.
    - DWW1253W
      The RCDS is corrupt for VSAM sphere dddd.
    - DWW1254W
      A sequence error occurred for log llll that is needed for the recovery of VSAM sphere dddd.
    - DWW1255W
      Step times overlap for sphere dddd.
    - DWW1256W
      The backout failing log records (BOFLGRECs) are not on the system log for sphere dddd.
    - DWW1257W
      No backout failing log record (BOFLGREC) type 3 is found for sphere dddd.
    - DWW1258W
      No backout failing log record (BOFLGREC) type 1 is found for sphere dddd.
    - DWW1259W
      Backout failing activity overlaps for sphere dddd.
    - DWW1260S
      Keyword kkkk1 and keyword kkkk2 cannot be used in the same command.
    - DWW1261S
      Input stream end-of-file is found before end of command.
    - DWW1266W
      Duplicate log name llll.
    - DWW1267E
      Processing of VSAM sphere dddd failed. Another job that started later is also forward recovering VSAM sphere dddd.
    - DWW1268I
      A forward recovery is started more than once in the same job for VSAM sphere dddd.
    - DWW1269I
      No report can be written for VSAM sphere dddd, because the RCDS is not allocated.
    - DWW1270E
      Processing of VSAM sphere dddd failed. An invalid sequence of events has been detected.
    - DWW1271I
      No attempt was made to switch on the VSAM RLS recovery request indicator for VSAM sphere dddd because it was detected that certain events had not occurred in the correct order.
    - DWW1272I
      No attempt was made to unbind any VSAM RLS locks for VSAM sphere dddd because it was detected that certain events had not occurred in the correct order.
    - DWW1273I
      No attempt was made to restore any DFSMShsm™ backup for VSAM sphere dddd because it was detected that certain events had not occurred in the correct order.
    - DWW1274I
      No attempt was made to remove any alternate indexes from the upgrade set for VSAM sphere dddd because it was detected that certain events had not occurred in the correct order.
    - DWW1275I
      Forward recovery was not attempted for VSAM sphere dddd because it was detected that certain events had not occurred in the correct order.
    - DWW1276I
      No attempt was made to rebuild any alternate indexes for VSAM sphere dddd because it was detected that certain events had not occurred in the correct order.
    - DWW1277I
      No attempt was made to bind any VSAM RLS locks for VSAM sphere dddd because it was detected that certain events had not occurred in the correct order.
    - DWW1278I
      No attempt was made to report to VSAM RLS successful completion of the forward recovery for VSAM sphere dddd because it was detected that certain events had not occurred in the correct order.
    - DWW1279I
      No attempt was made to set the VSAM RLS recovery request indicator for VSAM sphere dddd because of a previously detected error.
    - DWW1280I
      No attempt was made to unbind any VSAM RLS locks for VSAM sphere dddd because of a previously detected error.
    - DWW1281I
      No attempt was made to restore any DFSMShsm™ backup for VSAM sphere dddd because of a previously detected error.
    - DWW1282I
      No attempt was made to remove any alternate indexes from the upgrade set for VSAM sphere dddd because of a previously detected error.
    - DWW1283I
      Forward recovery was not attempted for VSAM sphere dddd because of a previously detected error.
    - DWW1284I
      No attempt was made to rebuild any alternate indexes for VSAM sphere dddd because of a previously detected error.
    - DWW1285I
      No attempt was made to bind any VSAM RLS locks for VSAM sphere dddd because of a previously detected error.
    - DWW1286I
      No attempt was made to report to VSAM RLS successful completion of the forward recovery for VSAM sphere dddd because of a previously detected error.
    - DWW1287I
      No attempt was made to unbind any VSAM RLS locks for VSAM sphere dddd because there is no VSAM RLS support for it.
    - DWW1288I
      No attempt was made to bind any VSAM RLS locks for VSAM sphere dddd because there is no VSAM RLS support for it.
    - DWW1289I
      No attempt was made to report to VSAM RLS successful completion of the forward recovery for VSAM sphere dddd because there is no VSAM RLS support for it.
    - DWW1290I
      No attempt was made to report to VSAM RLS successful completion of the forward recovery for VSAM sphere dddd because one of the forward recovery steps issued a warning message.
    - DWW1292E
      Dynamic allocation of data set failed while processing VSAM sphere dddd. The SVC 99 return code is cc. The SVC 99 error reason code is cc. The SVC 99 information reason code is cc.
    - DWW1293E
      An error occurred in the dynamic invocation of IDCAMS for VSAM sphere dddd to remove alternate indexes from the upgrade set. The return code from IDCAMS is cc.
    - DWW1294E
      An error occurred in the dynamic invocation of IDCAMS for VSAM sphere dddd to place alternate indexes in the upgrade set. The return code from IDCAMS is cc.
    - DWW1295E
      An error occurred in the dynamic invocation of IDCAMS for VSAM sphere dddd to build alternate indexes. The return code from IDCAMS is cc.
    - DWW1296E
      An error occurred while using the ARCXTRCT macro for VSAM sphere is dddd. The return code is cc, and the reason code is cc.
    - DWW1297E
      An error occurred while using the ARCHRCOV macro for VSAM sphere dddd. The return code is aa, and the reason code is bb.
    - DWW1298E
      While preparing to call DFSMShsm™ for VSAM sphere dddd it was detected that the version (cc) does not exist.
    - DWW1299E
      While preparing to call DFSMShsm™ it was detected that there are no backups for VSAM sphere dddd.
    - DWW1300E
      An attempt to dynamically allocate VSAM alternate indexes dddd failed. The SVC 99 return code is cc. The SVC 99 error reason code is cc. The SVC 99 information reason code is cc.
    - DWW1301E
      An attempt to open VSAM alternate index dddd failed. The return code is cc. The ACB ERROR field could not be retrieved. The SHOWCB register 0 error code is cc.
    - DWW1302E
      An attempt to open VSAM alternate index dddd failed. The return code is cc. The ACB ERROR field is cc.
    - DWW1303E
      An attempt to close VSAM alternate index dddd failed. The return code is cc. The ACB ERROR field could not be retrieved. The SHOWCB register 0 error code is cc.
    - DWW1304E
      An attempt to close VSAM alternate index dddd failed. The return code is cc. The ACB ERROR field is cc.
    - DWW1305E
      An attempt to dynamically deallocate VSAM alternate index dddd failed. The SVC 99 return code is cc. The SVC 99 error reason code is cc. The SVC 99 information reason code is cc.
    - DWW1306E
      An attempt to write to a dynamically allocated data set for VSAM sphere dddd failed. The return code is cc, and the reason code is cc.
    - DWW1307E
      All forward recovery processing will be skipped for VSAM sphere dddd because the RCDS is not allocated.
    - DWW1308E
      The attempt to set the VSAM RLS recovery request indicator for VSAM sphere dddd was not successful. The return code is cc, and the reason code is cc. The error data is cc.
    - DWW1309E
      The attempt to bind the VSAM RLS locks for VSAM sphere dddd was not successful. The return code is cc, and the reason code is cc. The error data is cc.
    - DWW1310E
      The attempt to unbind the VSAM RLS locks for VSAM sphere dddd was not successful. The return code is cc, and the reason code is cc. The error data is cc.
    - DWW1311E
      The attempt to relate to VSAM the completion of the forward recovery for VSAM sphere dddd was not successful. The return code is cc, and the reason code is cc. The error data is cc.
    - DWW1312E
      The VSAM RLS recovery request bit was not set for VSAM sphere dddd before the attempt to unbind the VSAM RLS locks.
    - DWW1313E
      The VSAM RLS recovery request bit was not set for VSAM sphere dddd before the attempt to bind the VSAM RLS locks.
    - DWW1314E
      The VSAM RLS recovery request bit was not set for VSAM sphere dddd before the attempt to report to VSAM the successful completion of the forward recovery.
    - DWW1315E
      An attempt to call the VSAM IGWARLS facility for the VSAM sphere dddd while setting on the VSAM RLS recovery requested bit failed. The return code is aa, and the reason code is bb. The problem determination data is cc.
    - DWW1316E
      An attempt to call the VSAM IGWARLS facility for the VSAM sphere dddd while binding VSAM RLS locks failed. The return code is aa, and the reason code is bb. The problem determination data is cc.
    - DWW1317E
      An attempt to call the VSAM IGWARLS facility for the VSAM sphere dddd while unbinding VSAM RLS locks failed. The return code is aa, and the reason code is bb. The problem determination data is cc.
    - DWW1318E
      An attempt to call the VSAM IGWARLS facility for the VSAM sphere dddd while relating to VSAM the completion of forward recovery failed. The return code is aa, and the reason code is bb. The problem determination data is cc.
    - DWW1319E
      An attempt to retrieve catalog information for VSAM sphere dddd failed.
    - DWW1320E
      VSAM sphere dddd is logged on both log llll1 and log llll2 from yydddhhmmss to yydddhhmmss GMT (yydddhhmmss to yydddhhmmss local time). The log use interval registered for llll1 will not be modified by this overlap. The log use interval for llll2 will be shortened.
    - DWW1321E
      VSAM sphere dddd is logged on MVS™ log llll from yydddhhmmss to yydddhhmmss GMT (yydddhhmmss to yydddhhmmss local time). During this period dddd was also logged on at least one other MVS log. The log records on llll for this period will be ignored.
    - DWW1322W
      VSAM sphere dddd logged on MVS™ log stream llll from yydddhhmmss to yydddhhmmss GMT was also logged on another log stream during this time period.
    - DWW1323W
      VSAM sphere dddd logged on MVS™ log stream llll from yydddhhmmss to yydddhhmmss local time was also logged on another log stream during this time period.
    - DWW1324W
      VSAM sphere dddd logged on MVS™ log stream llll from yydddhhmmss to yydddhhmmss GMT was also logged on another log stream during this time period.
    - DWW1325W
      VSAM sphere dddd logged on MVS™ log stream llll from yydddhhmmss to yydddhhmmss local time was also logged on another log stream during this time period.
    - DWW1326E
      The SAM copies of MVS™ log stream llll for VSAM sphere dddd from yydddhhmmss to yydddhhmmss (local time) do not cover the entire interval.
    - DWW1327W
      The SAM copies of MVS™ log stream llll for VSAM sphere dddd from yydddhhmmss to yydddhhmmss (local time) do not cover the end of the interval.
    - DWW1328I
      A mixture of CICS® journals and MVS™ log streams or their copies are needed for VSAM sphere dddd.
    - DWW1329E
      GMT times were specified for VSAM sphere dddd but it was not logged on any MVS™ log stream or log stream copy.
    - DWW1330E
      An error occurred in the dynamic invocation of IDCAMS to process user-supplied IDCAMS commands for VSAM sphere dddd. The return code from IDCAMS is cc.
    - DWW1331E
      An attempt to retrieve catalog information for VSAM sphere dddd failed.
    - DWW1332E
      For VSAM sphere dddd it was detected that alternate index dddd was in the upgrade set.
    - DWW1333W
      VSAM sphere dddd was active before recovery start time.
    - DWW1334W
      VSAM sphere dddd was active after recovery stop time.
    - DWW1335W
      It is uncertain whether the first job step has a stop time after the stop time specified for VSAM sphere dddd.
    - DWW1336W
      A CICS/ESA® V4R1 type log that was within one hour of the recovery interval specified for VSAM sphere dddd has been excluded.
    - DWW1337W
      The start time specified for the forward recovery of VSAM sphere dddd is in GMT time format, but the log does not contain GMT times.
    - DWW1338E
      Unexpected result while attempting to use the VSAM IGWARLS facility for VSAM sphere dddd. The VSAM IGWARLS load module was not available.
    - DWW1339E
      Unexpected result from the VSAM IGWARLS facility for VSAM sphere dddd. The return code is aa, and the reason code is bb. The problem determination data is cc.
    - DWW1340E
      Unexpected result from calling one of the VSAM RLS interfaces for VSAM sphere dddd. The return code is aa, and the reason code is bb. The error data is cc.
    - DWW1341E
      Unexpected result from calling one of the VSAM RLS interfaces for VSAM sphere dddd LOG (llll). The return code is aa, and the reason code is bb. The error data is cc.
    - DWW1342E
      Dynamic allocation of a data set failed while processing VSAM sphere dddd. The SVC 99 return code is cc. The SVC 99 error reason code is cc. The SVC 99 information reason code is cc.
    - DWW1343E
      An attempt to read from a dynamically allocated data set for VSAM sphere dddd failed. The return code is aa, and the reason code is bb.
    - DWW1344E
      An attempt to rebuild VSAM alternate indexes dddd (belonging to VSAM sphere dddd) failed because the alternate indexes are not defined as reusable.
    - DWW1345I
      VSAM sphere dddd has been recalled successfully.
    - DWW1346I
      Unable to recall VSAM sphere dddd The data set is not migrated.
    - DWW1347E
      An error occurred while using the ARCHRCAL macro for VSAM sphere dddd. The return code is X'aa', and the reason code is X'bb'.
    - DWW1401I
      The migration utility is started at yy⁄mm⁄dd hh:mm:ss.
    - DWW1402I
      The migration utility is terminated. The maximum condition code is cc. nn records have been copied.
    - DWW1403W
      The input RCDS contains a record type that is not defined in the destination RCDS.
    - DWW1404W
      A duplicate record is found and is ignored.
    - DWW1405E
      Inconsistent record types are found in the RCDS definitions.
    - DWW1406W
      The input RCDS is at current-level. The migration utility is terminated. No records have been copied.
    - DWW1407W
      The input RCDS is inconsistent or empty. The migration utility is terminated. No records have been copied.
    - DWW1410E
      Unexpected result from the IGWARLS interface for sphere dddd. The return code is aa. The reason code is bb. The problem determination field is X'cc'.
    - DWW1413I
      Command processing has completed. The maximum condition code is cc.
    - DWW1414S
      The end-of-file condition has been detected before the end of a command.
    - DWW1415S
      The MIGRATE command is specified more than once.
    - DWW1501I
      The MVS™ log stream copy utility is started at yy⁄mm⁄dd hh:mm:ss.
    - DWW1502I
      The MVS™ log stream copy utility is terminated. The maximum condition code is cc.
    - DWW1503S
      The exit load module xxxx cannot be found.
    - DWW1504S
      Browse of MVS™ log stream llll failed. The return code is cc, and the reason code is cc. The answer area contains cc.
    - DWW1505S
      An error occurred while attempting to gain access to the RCDS. The reason code is aa.
    - DWW1506S
      Incorrect number of copies nn was specified while using cursors control options.
    - DWW1507S
      The BR cursor was not set or null.
    - DWW1508I
      The MVS™ log stream tail delete was requested but not performed.
    - DWW1509I
      No relevant log blocks have been found on llll log stream. No blocks were processed.
    - DWW1520S
      Invalid TOD value or time format was inserted in the kkkk keyword.
    - DWW1541I
      The MVS™ log stream tail delete was requested but CICS VR does not permit it.
    - DWW1551I
      The RCDS utility is started at yy/mm/dd hh:mm:ss.
    - DWW1552I
      The RCDS utility has terminated. The maximum condition code is cc .
    - DWW1553I
      Command syntax checking is complete. The maximum condition code is cc.
    - DWW1554S
      The end-of-life file is found before the end of a command.
    - DWW1555S
      The required command cccc is missing.
    - DWW1556S
      The ddname ddn , which is required for the RCDS export utility is not present in the JCL.
    - DWW1556W
      No records were exported from the RCDS.
    - DWW1557S
      The ddname ddn , which is required as input to the RCDS import utility, is not present in the JCL.
    - DWW1557W
      No records were imported to the RCDS.
    - DWW1558S
      The command cccc is specified more than once.
    - DWW1568S
      The Data-In-Virtual (DIV) Identify service for data set dddd failed. The return code is rc and the reason code is rs.
    - DWW1571S
      The Data-In-Virtual (DIV) Save service for data set dddd failed. The return code is rc and the reason code is rs.
    - DWW1572S
      The Data-In-Virtual (DIV) Unidentify service for data set dddd failed. The return code is rc and the reason code is rs.
    - DWW1573I
      RCDS reset is successful for data set dddd.
    - DWW1601S
      The RCDS is full.
    - DWW1602S
      The RCDS is missing or incorrectly specified.
    - DWW1603S
      The RCDS is back-level.
    - DWW1604S
      There is a severe problem with the RCDS. The DIV abend code is aa. The DIV reason code is bbbb.
    - DWW1605I
      DWWCONn is full.
    - DWW1606I
      DWWCONn is missing or incorrectly specified.
    - DWW1607I
      DWWCONn is back-level.
    - DWW1608I
      There is a severe problem with the DWWCONn. The DIV abend code is aa. The DIV reason code is bbbb.
    - DWW1701I
      The batch backout utility is started at yy/mm/dd hh:mm:ss
    - DWW1702I
      The batch backout utility is terminated. The maximum condition code is cc.
    - DWW1703I
      Command processing is completed. The maximum condition code is cc.
    - DWW1704S
      The end-of-file condition is detected before the end of a command.
    - DWW1705I
      The following was entered as input on the parameter string:
    - DWW1706S
      The cccc command is specified more than once.
    - DWW1707S
      Batch Backout with RCDS(YES) is requested but no RCDS is allocated.
    - DWW1708S
      Batch Backout for jobname jjjj is requested but no information for this jobname is found in the RCDS.
    - DWW1709S
      Batch Backout for jobname jjjj and jobstep ssss is requested but no information for this step is found in the RCDS.
    - DWW1710S
      Batch Backout of the failed job step for job jjjj is requested. However, information in the RCDS indicates that the last step in the latest execution of the specified job did not fail.
    - DWW1711S
      Batch Backout for several steps are requested but more than one mvslog was used for undo logging.
    - DWW1712E
      An I/O error occurred after an add request to the dddd data set. The key is key. VSAM return codes are R15=cc, FDBK=nn.
    - DWW1713E
      An I/O error occurred after a replace request to the dddd data set. The key is key. VSAM return codes are R15=cc, FDBK=nn.
    - DWW1714E
      An I/O error occurred after a delete request to the dddd data set. The key is key. VSAM return codes are R15=cc, FDBK=nn.
    - DWW1715S
      Batch backout of an add on an ESDS is requested but no ESDS delete exit is defined. The data set name is dddd.
    - DWW1716S
      Batch Backout of an add on an ESDS is requested and the ESDS delete exit provided told Batch Backout to stop. The data set name is dddd.
    - DWW1717S
      Batch Backout of the failed job step for job jjjj is requested. However, information read from the log stream indicates that the last step in the latest execution of the specified job did not fail.
    - DWW1718S
      The exit load module xxxx cannot be found.
    - DWW1719S
      The required command cccc is missing.
    - DWW1720S
      The name of the original data set dddd plus the dsnextension .xxxx exceeds the maximum allowable length for a dataset name.
    - DWW1721I
      Batch Backout for jobname jobname and jobid jobid is requested but no information for this jobname with this jobid is found in the RCDS.
    - DWW1722I
      No records were backed out from sphere dddd.
    - DWW1723W
      The attempt to unbind the VSAM RLS locks for VSAM sphere dddd LOG(llll) was not successful. The return code is cc, and the reason code is cc. The error data is cc.
    - DWW1724W
      The attempt to bind the VSAM RLS locks for VSAM sphere dddd LOG(llll) was not successful. The return code is cc, and the reason code is cc. The error data is cc.
    - DWW1727S
      The undo log stream llll is empty.
    - DWW1728W
      Expected UNDO END log record not found on log stream llll for job step stepname.
    - DWW1729I
      The VSAM sphere dddd is specified more than once.
    - DWW1731W
      Unexpected result from calling one of the VSAM RLS interfaces for VSAM sphere dddd. The return code is aa, and the reason code is bb. The error data is cc.
    - DWW1732W
      Unexpected result attempting to use the VSAM IGWARLS facility for VSAM sphere dddd. The VSAM IGWARLS load module was not available.
    - DWW1733W
      Unexpected result from the VSAM IGWARLS facility for VSAM sphere dddd. The return code is aa, and the reason code is bb. The problem determination data is X'cc'.
    - DWW1734S
      Open of data set dddd failed. VSAM return codes are R15=cc, FDBK=nn.
    - DWW1735S
      Close of data set dddd failed. VSAM return codes are R15=cc, FDBK=nn.
    - DWW1736W
      The requested batch backout for the specified job includes backing out updates made to VSAM sphere dddd. However, this sphere might have been updated after the specified job completed.
    - DWW1737S
      The VSAM data set dddd to be backed out is not found in the VSAM catalog.
    - DWW1738S
      The VSAM data set dddd to be backed out is not a VSAM data set.
    - DWW1739S
      The VSAM data set dddd to be backed out is not a base cluster.
    - DWW1740E
      Dynamic allocation of data set dddd failed. The SVC 99 return code is cccc. The SVC 99 error reason code is eeee. The SVC 99 information reason code is nnnn.
    - DWW1741E
      Generation of ACB for data set dddd failed. VSAM return codes are R15=cccc, R0=ssss.
    - DWW1742E
      Generation of RPL for data set dddd failed. VSAM return codes are R15=cccc, R0=ssss.
    - DWW1743E
      SHOWCB ACB for data set dddd failed. VSAM return codes are R15=cccc, R0=ssss.
    - DWW1744S
      An error occurred when reading the VSAM catalog entry for VSAM data set dddd. Return code is cccc.
    - DWW1745S
      The VSAM data set dddd to be backed out is in error. Key length taken from the VSAM catalog is length1, key length taken from the undo log is length2.
    - DWW1746S
      The VSAM data set dddd to be backed out is in error. Relative key position taken from the VSAM catalog is key1, relative key position taken from the undo log is key2.
    - DWW1747S
      The VSAM data set dddd to be backed out is in error. Data set type taken from the VSAM catalog is datasettype1, data set type taken from the undo log is datasettype2.
    - DWW1750S
      An unacceptable error condition was encountered when attempting to read a block from log stream llll. The return code is: aa. The reason code is: bb. The answer area contains: cc.
    - DWW1751W
      No relevant before-image log records have been found on log stream llll between yy.ddd hh:mm:ss GMT and yy.ddd hh:mm:ss GMT.
    - DWW1752I
      One or more log records were applied during batch backout processing that ended with the previously reported error. The timestamp of the first block applied is yy.ddd hh:mm:ss GMT. The timestamp of the last block applied is yy.ddd hh:mm:ss GMT.
    - DWW1753I
      No log records were applied during batch backout processing that ended with the previously reported error.
    - DWW1754S
      Batch backout processing did not find any before-image log records on log stream llll for the specified step. The timestamp of the first block read is yy.ddd hh:mm:ss GMT. The timestamp of the last block read is yy.ddd hh:mm:ss GMT.
    - DWW1755S
      Required log blocks not found on log stream llll. CICS VR batch backout requires log blocks that contain log records between yy.ddd hh:mm:ss GMT and yy.ddd hh:mm:ss GMT to perform the specified batch backout processing.
    - DWW1756S
      CICS VR batch backout completed before finding all expected logrecords on log stream llll. The timestamp of the first block read is yy.ddd hh:mm:ss GMT. The timestamp of the last block read is yy.ddd hh:mm:ss GMT.
    - DWW1757S
      CICS VR batch backout reached end-of-data on log stream llll before finding all expected log records. The timestamp of the first block read is yy.ddd hh:mm:ss GMT. The timestamp of the last block read is yy.ddd hh:mm:ss GMT. The timestamp of the last expected log record is yy.ddd hh:mm:ss GMT.
    - DWW1758S
      CICS VR batch backout reached the expected stop time without finding all relevant log records on log stream llll for the specified batch backout processing. The timestamp of the first block read is yy.ddd hh:mm:ss GMT. The timestamp of the last block read is yy.ddd hh:mm:ss GMT. The timestamp of the last expected log record is yy.ddd hh:mm:ss GMT.
    - DWW1801I
      RCDS Delete is started at yy/mm/dd hh:mm:ss
    - DWW1802I
      RCDS Delete is terminated. The number of deleted entries are cccc
    - DWW1811I
      The Journal Print utility is started at yyyy/mm/dd hh:mm:ss.
    - DWW1812I
      The Journal Print utility is terminated. The maximum condition code is cc.
    - DWW1813I
      Command processing is completed. The maximum condition code is cc.
    - DWW1814S
      The end-of-file is found before the end of a command.
    - DWW1815S
      The cccc command is specified more than once.
    - DWW1816S
      The required command cccc is missing.
    - DWW1817S
      The ddname DWWCOPY1, which is required for this utility, is not present in the JCL.
    - DWW2500W
      An attempt to obtain data set properties for a data set dsname failed. The completion code is cc. The diagnostic return code is rc. The diagnostic reason code is rsnc. The diagnostic problem code is probc.
    - DWW3000I
      CICS VR server address space is initialized at yy/mm/dd hh:mm:ss.
    - DWW3002S
      Initialization of the CICS VR server address space is terminated at yy/mm/dd hh:mm:ss.
    - DWW3500I
      The CICS VR server address space maintenance message has been written to the operator console yy/mm/dd hh:mm:ss operator console message.
    - DWW8000W
      VSAM sphere not found in the RCDS: dddd.
    - DWW8001I
      Duplicate VSAM sphere name dddd encountered.
    - DWW8002W
      The most recent logical backup for VSAM sphere dddd is not in GMT format. The time format for this VSAM sphere is changed to local time.
    - DWW8003W
      The concatenation of the VSAM sphere name dddd1 and the entered extension dddd2 exceeded 44 characters.
    - DWW8004W
      A logical backup could not be found for VSAM sphere dddd.
    - DWW8005W
      The entered stop time yydddhhmmss is earlier than the start time yydddhhmmss for VSAM sphere dddd.
    - DWW8006W
      A problem is found with a log for VSAM sphere dddd.
    - DWW8007W
      Unresolved ddname dddd1 for VSAM sphere dddd2.
    - DWW8008S
      Invalid CICS VR parameter dddd specified.
    - DWW8009S
      ISMF data set list does not exist.
    - DWW8010W
      A matching restore JCL skeleton was not found for the most recent logical backup of VSAM sphere dddd.
    - DWW8020E
      VSAM sphere not found in the RCDS: dddd.
    - DWW8021E
      A logical backup could not be found for VSAM sphere dddd.
    - DWW8022I
      Logical backup is to be used for VSAM sphere dddd : bbbb.
    - DWW8023I
      Logical backup is to be used for VSAM sphere dddd : HSM version cc.
    - DWW8024E
      The logical backup dddd is not cataloged.
    - DWW8025E
      Logical backup cccc not found in the RCDS for VSAM sphere dddd.
    - DWW8026E
      HSM logical backup version cc does not exist for VSAM sphere dddd.
    - DWW8027E
      Restore skeleton cccc was not found for the logical backup dddd.
    - DWW8028E
      New data set name dddd was specified for more than one VSAM sphere.
    - DWW8029W
      The selected or the default backup did not have backup time in GMT.
    - DWW8030W
      The time format for VSAM sphere dddd is changed to local.
    - DWW8031I
      Default time format is to be used : cccc.
    - DWW8032E
      ISPF cccc error. Return code = rc.
    - DWW8101I
      The reorganization utility is started at yy/mm/dd hh:mm:ss.
    - DWW8102I
      The reorganization utility is terminated. The maximum condition code is cc.
    - DWW8103I
      Command processing is completed. The maximum condition code is cc.
    - DWW8104S
      The end-of-file condition is detected before the end of a command.
    - DWW8105I
      The following was entered as input on the parameter string:
    - DWW8106S
      The cccc command is specified more than once.
    - DWW8107S
      The attempt to obtain information for VSAM sphere dddd failed.
    - DWW8108S
      The attempt to build the new sphere dddd failed. The return code is cc.
    - DWW8109S
      The attempt to build alternate indexes for the new sphere dddd failed. The return code is cc.
    - DWW8110S
      The attempt to alter the new sphere dddd failed. The return code is cc.
    - DWW8111S
      The attempt to find the alternate index with non unique keys attribute for VSAM sphere dddd failed.
    - DWW8112S
      The required command cccc is missing.
    - DWW8151I
      The NOTIFY utility started at yy/mm/dd hh:mm:ss
    - DWW8152I
      The NOTIFY utility is terminated. The maximum condition code is cc1. The reason code is cc2.
    - DWW8153S
      The end-of-file condition is detected before the end of a command.
    - DWW8154I
      Command processing is completed. The maximum condition code is cc.
    - DWW8155S
      The required command cccc is missing.
    - DWW8156S
      The cccc command is specified more than once.
    - DWW8157I
      The following was entered as input on the parameter string:
    - DWW8158S
      The required keyword DSNAME is missing.
    - DWW8159S
      The required keyword BACKUPNAME is missing.
    - DWW8160S
      The required keyword PRODUCT is missing.
    - DWW8161S
      The value specified for the keyword PRODUCT has an invalid length.
    - DWW8301I
      The VSAM Recovery Tool utility is started at yyyy/mm/dd hh:mm:ss.
    - DWW8302I
      The VSAM Recovery Tool utility is terminated. The maximum condition code is cc.
    - DWW8303S
      The end-of-file condition has been detected before the end of a command.
    - DWW8304S
      The required command cccc is missing.
    - DWW8305I
      Command processing has completed. The maximum condition code is cc.
    - DWW8306S
      The VSAM sphere dddd is specified more than once.
    - DWW8307S
      The command cccc is specified more than once.
    - DWW8308E
      The RESETBWO command failed for VSAM sphere dddd. The return code is X'cc1', and the reason code is X'cc2'
    - DWW8309I
      The RESETBWO command successfully completed for VSAM sphere dddd.
  - Operator messages
    Operator messages are listed sequentially and contain an explanation of how the entries are formatted.
  - CICS VR return codes and reason codes in non-CICS VR messages
    Tables of reason and return codes.
  - Service diagnostic messages
    The following messages are CICS VR service diagnostic messages for use by IBM field support personnel.
  - Abend codes
    This section explains the CICS VR abend codes, and provides instructions for you to successfully complete the recovery of your CICS® VSAM data. Each abend code is explained using the following format.
- CICS® VR ddnames
  A table that contains the ddnames for CICS® VR.
- UNDO log structure overview
  Every undo log block consists of a Block Header (MVSLogBlockHeader type), followed by log records. Every log record includes a standard General Log Header (GenLogRecord type), followed by record data.
- DWWBKNT REXX
  The REXX procedure DWWBKNT performs multiple calls of the CICS VR NOTIFY utility DWWNT for IDCAMS REPRO backups listed in the input data set. It can be used in TSO and in a batch environment.
- Customization parameters
  The table lists parameters that you can specify on the DWWCST01 panel to customize members of &HLQ.SDWWCNTL.OUT and &HLQ.SDWWSENU/SJPN.OUT data sets.
- User replaceable JCL skeleton
  You can replace the CICS® VR supplied JCL skeleton DWWUJOB with one of your own ones that satisfies your requirements.
Glossary
The terms in this glossary are defined as they pertain to the CICS VSAM Recovery documentation.
Edition notice
This is the information for CICS VSAM Recovery for z/OS. It applies to CICS VSAM Recovery for z/OS Version 6.3, and to all subsequent versions, releases, and modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the product.
Download PDF
Download the PDF format documentation for CICS VSAM Recovery for z/OS 6.3

DWW0550W

A gap is encountered between record nn1 and record nn2 on log dddd when reading backward. Processing continues.

A sequence number gap was found between two label records in log dddd; the sequence numbers are not in sequence. The records are in the correct time sequence. That is, record nn2, which precedes record nn1 on the log, has an earlier time stamp. This message means that records needed for backout are probably missing. Some possible causes are:

A log was skipped during archiving.
Label records were skipped over by a selective archiving program; records needed for backout might also be skipped.
The journal archive control data set (JACD) is damaged or inaccessible, causing the wrong sequence numbers to be used on label records.
A log had data other than log records.

This message is issued if command SEQCHKR GAPINSEQUENCE(WARNING) is specified, or if WARNING is specified in the sequence checking secondary window.

CICS® VR continues the backout.

Batch–If a log was missing, archive this log and rerun CICS® VR.
If all logs are present, find out why there is a gap in the label records. (Check the contents of the log to see whether all records needed for backout are present.)
Remember to restore the VSAM data sets from the backup copies before you rerun CICS® VR.
Online–If a log was missing, archive this log and rerun CICS® VR.
If all logs are present, find out why there is a gap in the label records. (Check the contents of the log to see whether all records needed for backout are present.) Remember to restore the VSAM data sets from the backup copies before you resubmit the recovery job.