Return codes

Return codes are listed in numerical order for reference.

Table 1. GZDAKEY and GZDLKEY
Code	Description
0	Explanation Normal return code. Passed authority checking with license key. Authorization is good. System Action zDMF authorization records are updated to permit migrations.
4	Explanation Normal return code. Passed authority checking with an override. Authorization is limited to Trial Feature. System Action zDMF authorization records are updated to permit migrations under the Trial Feature.
8	Explanation Failed authority checking as the CPU is not defined to zDMF. System Action zDMF authorization records are not updated. System Programmer Response Verify that the CPU is authorized to run zDMF. If additional assistance is needed, contact the technical support.
28	Explanation Failed authority checking as the license to use zDMF has expired. System Action zDMF authorization records are not updated. System Programmer Response Verify that the key is correct. Check the expiration date of the key, or that the key was installed within five days of issuance. If additional assistance is needed, contact the IBM Technical Support.
64	Explanation A program check occurred. System Action zDMF authorization records are not updated. System Programmer Response Verify input statements. If additional assistance is needed, contact the technical support.
516	Explanation Error loading module GZDUKEY. System Action zDMF authorization terminates. System Programmer Response Verify that the correct load library is referenced on the STEPLIB DD JCL statement. If additional assistance is needed, contact the technical support.
520	Explanation Error locating CPU PCCA. System Action zDMF authorization terminates. System Programmer Response Re-run the authorization job. If additional assistance is needed, contact the technical support.
524	Explanation Error in caller identification. System Action zDMF authorization terminates. System Programmer Response Contact the technical support for assistance.
528	Explanation Error in date conversion. System Action zDMF authorization terminates. System Programmer Response Verify that the Express statement and key are correct. Re-run the failing authorization job or contact the technical support for assistance.
532	Explanation Error with Enterprise key. System Action zDMF authorization terminates. System Programmer Response Verify that the key is correct and check the key expiration date. If additional assistance is needed, contact the technical support.
540	Explanation Error with Trial Express key. System Action zDMF authorization terminates. System Programmer Response Verify that the key is correct and check the key expiration date. If additional assistance is needed, contact the technical support.
544	Explanation Error with TeraByte key. System Action zDMF authorization terminates. System Programmer Response Verify that the key is correct and check the key expiration date. If additional assistance is needed, contact the technical support.
552	Explanation Error with zDMF version definition. System Action zDMF authorization terminates. System Programmer Response Verify that the proper zDMF version is specified. If additional assistance is needed, contact the technical support.
556	Explanation Program error. System Action zDMF authorization terminates. System Programmer Response Contact the technical support for assistance.
4096	Explanation No valid keys detected. System Action zDMF authorization terminates. Problem Determination Uninitialized key data set. System Programmer Response Run the SYSOPTN batch job.

Table 2. GZDCDIO
Code	Description
1	Explanation Failure in DEVTYPE macro. Problem Determination: The reason code contains the DEVTYPE return code.
2	Explanation COMMDS OPEN failed. Problem Determination The reason code contains the return code from OPEN.
3	Explanation The TTR0 conversion routine failed or the SYSCOM DD statement does not point to a valid Communications Data Set (COMMDS).
4	Explanation I/O error accessing the Communications Data Set (COMMDS).
5	Explanation Invalid parameter list passed to GZDCDIO. Program logic error.
7	Explanation Invalid record number detected. Program logic error.
9	Explanation Sequence error (program logic error).
10	Explanation The Communications Data Set (COMMDS) was created by an unsupported zDMF version or release.
16	Explanation The SYSCOM DD JCL statement defines multiple or concatenated data sets.

Table 3. GZDCLIP
Code	Description
0	Explanation Program completed successfully.
8	Explanation A Point-In-Time target device was not offline.
12	Explanation The general purpose Communications Data Set access module, GZDCDIO, returned a non-zero return code in response to a request to access the specified data set. System Programmer Response See GZDCDIO on "GZDCDIO" for more information.
20	Explanation No successful migrations in the session. The program successfully read the migration control blocks from the Communications Data Set (COMMDS). None of the migration volumes were found to have completed without an error indication. This system was not involved in migration session The MVS system was not a participating Master or Agent system in the migration session described by the Communications Data Set (COMMDS) provided. Mix of Swap and Point-In-Time volumes. The supplied Communications Data Set (COMMDS) was generated in a session that included both Swap and Point-in-Time volume migrations. The GZDCLIP program will only generate control statements for one ICKDSF function. Swap source volumes: Agent system. The supplied Communications Data Set (COMMDS) was generated in a session for which this system was a zDMF agent. The ICKDSF "INIT" function is only valid on the original Master system. Swap source volumes: Missing "MODEL" DD statement. The DD statement used by GZDCLIP to extract the required VTOC and index configuration for the ICKDSF "INIT" function has not been supplied. Swap source volumes: "MODEL" volume not in use. The program cannot access the VTOC Information Block (VIB) for the volume referenced by the "MODEL" DD statement. Problem Determination: In most cases, return code 20 is accompanied by an explanatory message in the job log.

Table 4. GZDCLUP
Code	Description
0	Explanation Normal exit from GZDCLUP. System Action zDMF virtual storage and migration device clean up was successful (or unnecessary).
4	Explanation One or more warning messages were issued by GZDCLUP. System Action An unusual condition was encountered during virtual storage or device validation and clean up. The program was unable to determine whether a problem exists, or has failed to write the zDMF messages and control blocks to the original SYSCOM data set. Problem Determination This return code is always accompanied by one or more explanatory warning messages (suffix "W"). User Response Examine the warning message(s) and respond accordingly.
8	Explanation One or more error messages were issued by GZDCLUP. System Action An error condition was encountered during virtual storage or device validation and clean up. Problem Determination This return code is always accompanied by one or more error messages (suffix "E"). These messages should be used to diagnose the problem. User Response Evaluate the error message(s), together with any warning messages that might also have been issued, and respond accordingly.
12	Explanation One or more severe error messages were issued by GZDCLUP. System Action The program is not APF authorized, the SYSPRINT DD statement is missing, or a system macro instruction set an unacceptable return code. Problem Determination This return code is always accompanied by a severe error message (suffix "S"), either in the SYSPRINT output or the job log. User Response Respond as described for the severe error message that was issued.

Table 5. GZDDOVA. See also Table 7.
Code	Description
0	Explanation Program completed successfully.
12	Explanation GZDDOVA sets return code 12 and terminates without invoking the zDMF main task module, GZDMAIN, for one of the following reasons: No successful PIT migrations in the session.p Of the volume migration(s) described by the supplied Communications Data set, none is a successfully completed Point-In-Time copy migration. Delayed Offline Volume Access (Delayed OVA) cannot be used with these volumes. This system was not involved in migration session. The MVS system was not a participating Master or Agent system in the migration session described by the Communications Data set specified on the SYSCOM DD statement. Target volser changed. One of the Point-In-Time migration target volumes described in the supplied Communications Data set has been relabeled since the zDMF job was run and can no longer be considered a valid copy. Target volume unknown on this system. The UCB for one of the migration target devices was not available to the original zDMF session. Target UCB invalid. The UCB address found for a migration target device by the original zDMF session no longer points to the target UCB. Unable to read Communications Data set. Problem Determination In all cases, when GZDDOVA set a return code of 12, an explanatory message is written to the job log.

Table 6. GZDLOGS. General purpose register 15 on completion of GZDLOGS contains both the reason code in bits 0-15 and the return code in bits 16-31.
Code	Description
0	Explanation Successful execution. System Action GZDLOGS completed normally.
400	Explanation History Logging not installed. System Programmer Response Contact the technical support for assistance.
404	Explanation RACF authority checking failed. System Action GZDLOGS completed in error. Problem Determination The reason code in bits 0-15 is the return code from the RACROUTE macro request. System Programmer Response Evaluate the return code from RACROUTE and respond accordingly. If further assistance is needed, contact the technical support.
408	Explanation ESTAE recovery error. System Action GZDLOGS completed in error. System Programmer Response Contact the technical support for assistance.
412	Explanation ENQ for History Data set failed. An attempt to acquire exclusive control of the History Data set was not successful; if the reason code is four, the program's 30 second timer elapsed while waiting for the data set to become available. This code is only returned to APF authorized callers (for others, the ENQ is performed by the DYNALLOC SVC and code 424 will be returned). System Action GZDLOGS completed in error. System Programmer Response: Contact the technical support for assistance.
416	Explanation RDJFCB error for the SYSCOM data set. System Action GZDLOGS completed in error. Problem Determination The reason code in bits 0-15 is the return code from the RDJFCB macro request. System Programmer Response Evaluate the return code from RDJFCB and respond accordingly. If further assistance is needed, contact the technical support.
420	Explanation Parsing of the data set name failed. System Action GZDLOGS completed in error. System Programmer Response Contact the technical support for assistance.
424	Explanation DYNALLOC error during allocation of data set. The reason code in bits 0-15 is the return code from the DYNALLOC macro request. The dynamic allocation will fail if the History Logging data set is currently in use by another job or TSO user. The name of the History Logging data set is one of the installation options and can be displayed using the TSO monitor (Display Installation Options and Environment). System Action GZDLOGS completed in error. Problem Determination If GZDLOGS was called from a batch job, a dynamic allocation error message will be written to the job log. System Programmer Response Evaluate the return code from DYNALLOC, or find the associated IKJnnnnnx message, and respond accordingly. If further assistance is needed, contact the technical support.
428	Explanation RDJFCB error for the History Logging data set. System Action GZDLOGS completed in error. Problem Determination The reason code in bits 0-15 is the return code from the RDJFCB macro request. System Programmer Response Evaluate the return code from RDJFCB and respond accordingly. If further assistance is needed, contact the technical support.
432	Explanation OPEN of the History Logging data set failed. System Action GZDLOGS completed in error. System Programmer Response Contact the technical support for assistance.
436	Explanation DYNALLOC error during deallocation of data set. System Action GZDLOGS completed in error. Problem Determination The reason code in bits 0-15 is the return code from the DYNALLOC macro request. System Programmer Response Evaluate the return code from DYNALLOC and respond accordingly. If further assistance is needed, contact the technical support.
440	Explanation History Logging data set incorrectly defined. System Action GZDLOGS completed in error. Problem Determination Bits 0-15 of the return code are the return code from the OBTAIN SEARCH macro request. If these bits are zero, the data set was found on the volume but is not a sequential data set with 80 byte fixed length records. System Programmer Response Contact the technical support for assistance.
444	Explanation Invalid call. System Action GZDLOGS completed in error. System Programmer Response Contact the technical support for assistance.
448	Explanation Error writing log entry. System Action GZDLOGS completed in error. Problem Determination The reason code in bits 0-15 is the ABEND code. System Programmer Response Contact the technical support for assistance.

Table 7. GZDMAIN
Code	Description
0	Explanation Normal exit from zDMF. System Action zDMF sessions completed successfully.
4	Explanation One or more warning messages were issued by zDMF. System Action zDMF sessions completed successfully. Problem Determination Review the output from the migration job. User Response Evaluate the warning messages and respond accordingly.
8	Explanation One or more error messages were issued by zDMF. System Action One or more volume migrations did not complete successfully. Problem Determination Review the output from the master migration job and all agent systems. User Response Evaluate the error messages and respond accordingly.
12	Explanation One or more severe error messages were issued by zDMF. System Action One or more volume migrations did not complete successfully. Problem Determination Review the output from the master migration job and all agent systems. User Response Evaluate the error messages and respond accordingly.

Table 8. GZDMUCB
Code	Description
0	Explanation None of the devices passed to the program are involved in a zDMF session. Problem Determination R0 contains the number of active zDMF sessions.
4	Explanation One or more of the specified devices is the source for a zDMF session. Problem Determination R0 contains the number of active zDMF sessions.
8	Explanation One or more of the specified devices is the target for a zDMF session. Problem Determination R0 contains the number of active zDMF sessions.
12	Explanation One or more of the specified devices could not be located or is offline. Problem Determination R0 contains the number of active zDMF sessions.
16	Explanation An error occurred in the GQSCAN routine. Problem Determination R0 bits 0-15 contain the GQSCAN reason code; bits 16-31 contain the GQSCAN return code.
20	Explanation An error occurred in GZDMUCB. Problem Determination R0 contains the abend code (the contents of SDWAABCC at entry to the recovery routine).
24	Explanation An error was detected in the caller's parameter list. Problem Determination R0 contains a reason code, as follows: 01 The number of devices is negative. 02 The function code is non-zero. 03 The device specification type is not within the range 0:2.
28	Explanation An unsupported version of zDMF is active. Problem Determination R0 contains the address of the main zDMF control block for the session.

Table 9. GZDQDSK
Code	Description
0	Explanation Normal exit from GZDQDSK. System Action GZDQDSK completed normally.
4	Explanation One or more warning messages were issued by GZDQDSK. System Action GZDQDSK completed with warnings. Problem Determination Review the output from the GZDQDSK job. User Response Evaluate the warning messages and respond accordingly.
8	Explanation One or more error messages were issued by zDMF. System Action One or more volume migrations did not complete successfully. Problem Determination Review the output from the GZDQDSK job. User Response Evaluate the error messages and respond accordingly. System Programmer Response If further assistance is needed, contact the technical support.

Table 10. GZDSCAN
Code	Description
0	Explanation The devices specified were successfully scanned. Non-standard record zeros or records with invalid count fields, as determined by zDMF, were not detected.
4	Explanation Completed with warning message(s). User Response Investigate and understand the reasons for the warning messages before attempting a zDMF migration of the volumes.
8	Explanation Corrective action is necessary for one or more of the volumes before a successful migration can be performed using zDMF.
12	Explanation A severe error prevented completion of the volume scan. User Response Correct the error and rerun GZDSCAN.
16	Explanation OPEN failed for SYSPRINT. User Response Correct the SYSPRINT JCL and rerun GZDSCAN.

Table 11. GZDUKEY. General purpose register 15 on completion of GZDUKEY contains both the reason code in bits 0-15 and the return code in bits 16-31.
Code	Description
0	Explanation Successful execution. System Action GZDUKEY completed normally.
200	Explanation BLDL error. System Action GZDUKEY completed in error. Problem Determination The reason code in bits 0-15 is the return code from the BLDL macro request. System Programmer Response Evaluate the return code from BLDL and respond accordingly. If further assistance is needed, contact the technical support.
204	Explanation The GZDKEYS load module has multiple text records, or its format is invalid. System Action GZDUKEY completed in error. System Programmer Response Contact the technical support for assistance.
208	Explanation TTR conversion error. The TTR returned by the BLDL macro is not valid for the GZDKEY data set. System Action GZDUKEY completed in error. Problem Determination The reason code in bits 0-15 is the non-zero return code from IECPCNVT. System Programmer Response: Contact the technical support for assistance.
212	Explanation Unsuccessful I/O operation (Read). System Action GZDUKEY completed in error. Problem Determination The first eight bits of the reason code are copied from the ECB used for the EXCP request. Refer to a description of the IOBECBCC field in the DFSMS/MVS documentation to interpret this value. System Programmer Response Contact the technical support for assistance.
216	Explanation Unsuccessful I/O operation (Write). System Action GZDUKEY completed in error. Problem Determination The first eight bits of the reason code are copied from the ECB used for the EXCP request. Refer to a description of the IOBECBCC field in the DFSMS/MVS documentation to interpret this value. System Programmer Response Contact the technical support for assistance.
220	Explanation GETMAIN error. System Action GZDUKEY completed in error. Problem Determination The reason code in bits 0-15 is the return code from the GETMAIN macro request. System Programmer Response Evaluate the return code from GETMAIN and respond accordingly. If further assistance is needed, contact the technical support.
224	Explanation RDJFCB error. System Action GZDUKEY completed in error. Problem Determination The reason code in bits 0-15 is the return code from the RDJFCB macro request. System Programmer Response Evaluate the return code from RDJFCB and respond accordingly. If further assistance is needed, contact the technical support.
228	Explanation Bad buffer address. Problem Determination The I/O buffer address which was passed by the caller to GZDUKEY was zero. Probable programming error. System Action GZDUKEY completed in error. System Programmer Response Contact the technical support for assistance.
232	Explanation Invalid function code. System Action GZDUKEY completed in error. Problem Determination The requested function was not "Read," "Update" or "Read with reserve." Probable programming error. System Programmer Response Contact the technical support for assistance.

Table 12. GZDUQTY. General purpose register 15 on completion of GZDUQTY contains both the reason code in bits 0-15 and the return code in bits 16-31.
Code	Description
0	Explanation Successful execution. System Action GZDUQTY completed normally.
300	Explanation BLDL error. System Action GZDUQTY completed in error. Problem Determination The reason code in bits 0-15 is the return code from the BLDL macro request. System Programmer Response Evaluate the return code from BLDL and respond accordingly. If further assistance is needed, contact the technical support.
304	Explanation The GZDKEYS load module has multiple text records, or its format is invalid. System Action GZDUQTY completed in error. System Programmer Response Contact the technical support for assistance.
308	Explanation TTR conversion error. The TTR returned by the BLDL macro is not valid for the GZDKEY data set. System Action GZDUQTY completed in error. Problem Determination The reason code in bits 0-15 is the non-zero return code from IECPCNVT. System Programmer Response: Contact the technical support for assistance.
312	Explanation Unsuccessful I/O operation (Read). System Action GZDUQTY completed in error. Problem Determination The first eight bits of the reason code are copied from the ECB used for the EXCP request. Refer to a description of the IOBECBCC field in the DFSMS/MVS documentation to interpret this value. System Programmer Response Contact the technical support for assistance.
316	Explanation Unsuccessful I/O operation (Write). System Action GZDUQTY completed in error. Problem Determination The first eight bits of the reason code are copied from the ECB used for the EXCP request. Refer to a description of the IOBECBCC field in the DFSMS/MVS documentation to interpret this value. System Programmer Response Contact the technical support for assistance.
320	Explanation GETMAIN error. System Action GZDUQTY completed in error. Problem Determination The reason code in bits 0-15 is the return code from the GETMAIN macro request. System Programmer Response Evaluate the return code from GETMAIN and respond accordingly. If further assistance is needed, contact the technical support.
324	Explanation RDJFCB error. System Action GZDUQTY completed in error. Problem Determination The reason code in bits 0-15 is the return code from the RDJFCB macro request. System Programmer Response Evaluate the return code from RDJFCB and respond accordingly. If further assistance is needed, contact the technical support.
328	Explanation Express information error. System Action GZDUQTY completed in error. System Programmer Response Contact the technical support for assistance.

Table 13. GZDVTOC
Code	Description
0	Explanation Normal completion.
4	Explanation One or more devices in the configuration: Had VTOCs that could not be opened Contain information which is in conflict with the physical device characteristics reported by the storage controller.
8	Explanation The IOERROR flag returned this code for two possible reasons: An I/O error occurred, in which case the I/O error message will be displayed on the output line for the relevant volume. An allocation error occurred, in which case the messages returned by the allocation process will be displayed - beginning on the line of the failing volume.