Explanation
- aa
- The module identifier.
- return-code
- The return code
- reason-code
- The reason code
- sfi
- The subfunction (SFI) field information. If present, it is documented under the specific return-code reason-code.
For the explanations of a return code and reason code, find the heading for the return code in the following text and then scan for the associated reason code.
If you are using Library Server, to find the explanations of a return code and reason code quickly, enter the following search argument:
IDC3009I return-code reason-codeIEC331I 004-33, XXXXXXXX, YYYYYYYY, OPN VSM ACB, ZZZZZZZZIDC3009I 4 33IDC3009I rcreturn-codeFor example, for the general description of return code 4, enter IDC3009I rc4.
If the search takes you to a description of the reason code "x", it means the reason code you received is one of a group of reason codes that have a common description. Most of these reason codes represent internal logic errors, and they will indicate that you should contact the IBM® Support Center.
System action
The system ends processing associated with the error return code.
Operator response
None, unless indicated for specific return and reason codes
System programmer response
If the error recurs and the program is not in error, look at the messages in the job log for more information. Search problem-reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Some return and reason code combinations might also produce an SVC dump. This dump should also be provided with any other documentation supplied to the IBM Support Center.
Descriptions of the return codes and reason codes follow.
RETURN CODE 4 Explanation: The system encountered an error while performing open/close processing for a catalog.| Reason Code | Description |
|---|---|
| x | Explanation: An internal error
has occurred during Catalog processing. Programmer Response: Contact the IBM Service Center. An SVC dump may have been produced for this error. |
| 2 | Explanation: An error occurred
while opening a new catalog that is being defined, or the master catalog. Programmer Response: Check for open/close problem determination messages in the job stream output. |
| 6 | Explanation: A request has
referenced a catalog while catalog management is processing, or after
catalog management has processed, an access method services DELETE
command for the specific catalog. Programmer Response: The catalog needed for the request has been deleted. If needed, the catalog must be redefined before attempting the request again. |
| 8 | Explanation: An incorrect
access method control block (ACB) was supplied to catalog management
for a catalog to be used during a catalog request. Programmer Response: Contact your programming support personnel. |
| 23 | Explanation: While performing
a GETMAIN from the requested subpool, the VSAM volume data set (VVDS)
manager protocol module returned an error. Programmer Response: Increase the size of the CSA or run the job again when more CSA is available. |
| 25 | Explanation: Unable to get
CSA storage (subpool 241). Programmer Response: Increase the size of CSA or run the job when more CSA is available. |
| 26 | Explanation: Unable to get
storage for scheduler workarea (subpool 252). Programmer Response: Increase the REGION size. |
| 27 | Explanation: Unable to get
CSA for catalog (subpool 241). Programmer Response: Increase the size of CSA or run the job when more CSA is available. |
| 30 | Explanation: Unable to get
in subpool 252. Programmer Response: Increase the REGION size. |
| 31 | Explanation: The VVDS manager encountered an error processing a VSAM volume record (VVR) request. |
| 32 | Explanation: The system was
unable to complete verification that the required volume is mounted. Programmer Response: Ensure that the unit is available for mounting and that the correct volume is mounted. |
| 34 | Explanation: An attempt to
open a catalog could not find the VVR record for the catalog. Programmer Response: It is possible that the catalog name is still defined in the master catalog but does not physically exist on the expected volume. This is usually a result of re-initializing the volume without doing an EXPORT DISCONNECT of any user catalogs on the volume. |
| 60 | Explanation: Unable to get
storage in subpool 252 (for EOV) or in subpool 253 (for CLOSE). Programmer Response: Increase the REGION size. |
| 83 | Explanation: The catalog has
been deleted, and CAXWA is still on the chain until all jobs allocated
to it end or logoff. Programmer Response: Do not use the catalog, or a new catalog with the same name, until all jobs allocated to the old catalog end or logoff. |
| 84 | Explanation: CAXWA count of
active users has reached 32767, the maximum allowed. Programmer Response: Do not use the catalog until one of the current jobs allocated to it ends or logs off. |
| 85 | Explanation: Unable to get
CSA for the catalog ACB or for the PCTT (subpool 241) Programmer Response: Increase the size of the CSA or run the job when more CSA is available. |
| 86 | Explanation: An error occurred
while opening the catalog. Programmer Response: See associated message IEC161I and/or IEC331I for information about the OPEN error. The catalog might be damaged. Run the DIAGNOSE or EXAMINE command to analyze the catalog. |
| 102 | Explanation: An invalid catalog
ACB address was passed in the catalog parameter list. Programmer Response: Point the ACB pointer passed in the parameter list to the valid ACB of a user catalog. |
| 104 | Explanation: A necessary catalog
could not be dynamically allocated in the catalog address space, and
the catalog parameter list indicated dynamic allocation in the callers
address space was not allowed. Programmer Response: Check for allocation problem determination messages in the job stream output. Follow the programmer response for these messages. |
| 106 | Explanation: A necessary catalog
could not be dynamically allocated in the catalog address space, and
the catalog parameter list indicated dynamic allocation in the callers
address space was not allowed. Programmer Response: Check for allocation problem determination messages in the job stream output. Follow the programmer response for these messages. |
| 108 | Explanation: A necessary catalog
could not be dynamically allocated in the catalog address space, and
the catalog parameter list indicated dynamic allocation in the callers
address space was not allowed. Programmer Response: Check for allocation problem determination messages in the job stream output. Follow the programmer response for these messages. |
| 114 | Explanation: A catalog needed
for the request could not be allocated to the catalog address space,
and the caller did not request it be allocated to the callers address
space. Programmer Response: When a catalog cannot be dynamically allocated to the catalog address space, it must be allocated to the user address space before the catalog request is issued. |
| 116 | Explanation: The CAS unallocation lock was not available. Programmer Response: Contact the IBM Support Center. |
| 118 | Explanation: The catalog needed
for this request has been deleted. Programmer Response: Redefine the deleted catalog and reissue the request. |
| 120 | Explanation: The master catalog
connector record was not found for the named catalog. Programmer Response: Enter the access method services LISTCAT command to display the entries in the master catalog. If the user catalog is not listed, enter the access method services IMPORT CONNECT command to connect the catalog. If the user catalog data set name is listed, ensure that the entry is for a user catalog. |
| 122 | Explanation: The master catalog
connector record was not found for the named catalog. Programmer Response: Enter the access method services LISTCAT command to display the entries in the master catalog. If the user catalog is not listed, enter the access method services IMPORT CONNECT command to connect the catalog. If the user catalog data set name is listed, ensure that the entry is for a user catalog. |
| 124 | Explanation: An error occurred while
opening the catalog. Programmer Response: See associated messages IEC161I and IEC331I, or both, for more information about the OPEN error. |
 132 |
Explanation: A zero UCB pointer was found
in an internal catalog control block of an ICFCATALOG. Programmer Response: Send in the 4-134 dump produced to the IBM support center. Issue the MODIFY command F CATALOG,ALLOCATE(catalog name) for the catalog in error and reissue the failing request. If that still does not resolve the issue, contact the IBM support center. |
| 134 |
Explanation: A zero UCB pointer was found
in an internal catalog control block of an ICFCATALOG. Programmer Response: Send in the 4-134 dump produced to the IBM support center. Issue the MODIFY command F CATALOG,ALLOCATE(catalog name) for the catalog in error and reissue the failing request. If that still does not resolve the issue, contact the IBM support center. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: An entry was
not found on LOCATE REQUEST. Programmer Response: Ensure that the proper entry was specified. |
| 2 | Explanation: The catalog cluster
record was not found. Programmer Response: Call your programming support personnel. |
| 6 | Explanation: No record was
found from record management. Programmer Response: Ensure that the entry name is spelled correctly. In the instance of an improper DELETE command entry type, either remove the type specification or correct it. Check also that the proper catalog is being searched for the name you specified. |
| 8 | Explanation: A request to
place a record by key into a catalog resulted in a duplicate key error
from VSAM. Programmer Response: Ensure that the entry name is spelled correctly and that the proper catalog is being used. |
| 12 | Explanation: An incorrect
entry type occurred for locate on the entry named. The data set was
not found in a catalog. Programmer Response: Ensure that the proper data set name was specified in the job control language DD statement. |
| 14 | Explanation: A generation
data group (GDG) entry type for locate did not find the specified
entry in a catalog. Programmer Response: Ensure that the proper data set name was specified in the job control language DD statement. |
| 16 | Explanation: A GDG entry was
found to be deleted from a catalog. Programmer Response: Ensure that the proper data set name was specified in the job control language DD statement. |
| 18 | Explanation: A GDG type of
locate request specified an incorrect generation number. Programmer Response: Ensure that the proper data set name was specified in the job control language DD statement. |
| 20 | Explanation: The volume entry
being removed from an catalog entry during ALTER REMOVEVOLUMES processing
cannot be found in the catalog record or the volume being removed
is a PRIME volume. Programmer Response: Verify that the volume serial numbers specified actually exist in the catalog entry for the data set being altered and is not a PRIME volume. |
| 38 | Explanation: A duplicate entry
name or high level index name was found in the target catalog during
a define command. See section on Multi Level Alias Facility in your
"Managing Catalogs" manual. Programmer Response: In the DEFINE command, specify a name that does not already exist in the target catalog. In the case of a DEFINE ALIAS, make sure there are no data sets that currently exist with that same high-level qualifier. |
| 40 | Explanation: A DEFINE GDG
command was not issued prior to the DEFINE NONVSAM command with GDG
entry name. Programmer Response: Ensure that the GDG base is defined prior to defining the non-VSAM with a GDG entry name. |
| 42 | Explanation: The catalog record
for the requested entry could not be found. Programmer Response: Ensure that the entry name specified on the access method services command is in the catalog specified. |
| 44 | Explanation: A request to
place a record by key into an ICF catalog resulted in a duplicate
key error from VSAM. Programmer Response: If the spelling and catalog being used are correct, run the DIAGNOSE command to analyze the catalog. |
| 46 | Explanation: A base record
was not found upon deletion of a cluster, AIX® or GDG in an ICF catalog. Programmer Response: Run the DIAGNOSE command to analyze the catalog. The ICF catalog may have to be restored or rebuilt. |
| 50 | Explanation: A record was
not found during LISTCAT ALL processing. Programmer Response: The requested record may have been moved during concurrent catalog updating. Ignore the error or run the job again. |
| 52 | Explanation: A duplicate data
component name was found. Programmer Response: Ensure that all data component names are unique and run the job again. |
| 54 | Explanation: A duplicate index
component name was found. Programmer Response: Ensure that all index component names are unique and run the job again. |
| 56 |
Explanation: An IDCAMS ALTER REMOVEVOLUMES
command was issued against a Guaranteed Space candidate volume. Programmer Response: Ensure that the volume or volumes are not Guaranteed Space candidate volumes and then run the job again. |
| Reason Code | Description |
|---|---|
| x | Explanation: A record being
processed contained inconsistent or incorrect data for the type of
entry. Programmer Response: Run the DIAGNOSE command to check for a damaged catalog record. A SYS1.DUMP may have been produced for this error. |
| 0 | Explanation: An incorrect
record type is found when trying to find a subrecord to be moved. Programmer Response: Run the DIAGNOSE command to check for a damaged catalog record. |
| 10 | Explanation: An incorrect
VSAM volume record was read from the VSAM volume data set and was
detected while modifying the catalog's VSAM volume record. Programmer Response: Perform the following steps:
|
| 12 | Explanation: The record type
for a data set was found to be incorrect during reset of a reusable
data set. Programmer Response: Ensure that the target of a reset is a VSAM data set. Call your programming support personnel. |
| 14 | Explanation: On a disconnect
request, the connector record was missing or incorrect. Programmer Response: Run the DIAGNOSE command to determine if the user catalog connector record is damaged and take the recommended action. |
| 20 | Explanation: The volume cell
in the VVDS catalog record could not be found. Programmer Response: Run the DIAGNOSE command to determine if the VVDS catalog record is damaged and take the recommended action. |
| 42 | Explanation: A VVDS record
contained inconsistent data. Programmer Response: Run the DIAGNOSE command to check for a damaged VVDS record. |
| 50 | Explanation: VVR or NVR exceeds its maximum size. |
| Reason Code | Description |
|---|---|
| x | Explanation: A required component
was not found within a catalog record. Programmer Response: Run the DIAGNOSE command to check for a damaged catalog record. A SYS1.DUMP may have been produced for this error. |
| Reason Code | Description |
|---|---|
| x | Explanation: A required cell
was not found in a catalog record during processing. Programmer Response: Run the access method services DIAGNOSE command to check for a damaged catalog record. A SYS1.DUMP may have been created. |
| Reason Code | Description |
|---|---|
| x | Explanation: An attempt was
made to issue an ALTER command to remove SMS volumes. Programmer Response: Do not attempt the incorrect ALTER command. Correct the commands and rerun the job. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: A system request
to alter the backup-while-open (BWO) options specified an inconsistent
or unsupported state. Programmer Response: This is most likely an invalid catalog parameter list. Contact the IBM Support Center. |
| 2 | Explanation: An attempt to
alter a data set's storage class name or management class name has
fail because DFSMShsm was
not active. The system found incorrect data for an alter of a backup
while the backup was open. Programmer Response: Verify DFSMShsm is operational and retry the request. |
| 4-10 | Explanation: An ALTER for
a migrated data set was issued, but the call to DFSMShsm failed. The reason-code code
is from DFSMShsm. Programmer Response: Refer to DFSMShsm message ARC0073I in z/OS MVS System Messages, Vol 2 (ARC-ASA) for an explanation of the reason code and take the appropriate action. |
| 12 | Explanation: An attempt to
alter a data set's security information was rejected. Security information
is no longer supported in catalogs. Programmer Response: Remove the security-related parameters (READPW, UPDATEPW, MASTERPW, CONTROLPW, ATTEMPTS, CODE, AUTHORIZATION) and retry the alter request. |
| 14 | Explanation: An ALTER command failed
to rename a data set into a generation data group, because the data
set has ACCOUNT information associated with it. Programmer Response: Copy the data set to a new NonVSAM data set to remove the ACCOUNT information. Then rename the new data set into the generation data group. |
| 16 | Explanation: An ALTER of a VSAM data
set with an indirect volume serial is not supported. Programmer Response: Ensure that the data set is not a VSAM dataset with an indirect volume serial, and rerun the ALTER. |
| 98 | Explanation: An ALTER for
a migrated data set was issued, but the call to DFSMShsm failed. The reason-code code
is from DFSMShsm. Programmer Response: Refer to DFSMShsm message ARC0073I in z/OS MVS System Messages, Vol 2 (ARC-ASA) for an explanation of the reason code and take the appropriate action. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: The
catalog cannot be extended for one of the following reasons:
Programmer Response: Scratch unneeded data sets from the volume. Delete all unnecessary entries from the catalog. The catalog may need to be reallocated and rebuilt if these steps do not resolve the space shortage. |
| Reason Code | Description |
|---|---|
| x | Explanation: An invalid structure
was passed as input to a catalog request. Programmer Response: Contact the IBM Support Center. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: An I/O error
occurred while attempting to read information from the catalog. Programmer Response: Messages IEC331I, IEC332I, and IEC333I have been printed to aid in determining the cause of the error and where the error occurred. If a hardware error is not causing the problem, restore or rebuild the catalog. |
| Reason Code | Description |
|---|---|
| x | Explanation: A VS record management
error occurred while processing a catalog request. Programmer Response: Contact the IBM Support Center. An SVC dump will be created for this error. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: An I/O error
processing the catalog occurred while processing an access method
services command that requires modifying the catalog. Programmer Response: Messages IEC331I, IEC332I, and IEC333I have been printed to aid in determining the cause of the error and where the error occurred. If a hardware error is not causing the problem, restore or rebuild the catalog. |
| 4 | Explanation: An I/O error
occurred during catalog OPEN. Programmer Response: Messages IEC331I, IEC332I, and IEC333I have been printed to aid in determining the cause of the error and where the error occurred. If a hardware error is not causing the problem, restore or rebuild the catalog. |
| 6 | Explanation: One or more entries
were not deleted due to an I/O related error during DELETE processing. Programmer Response: Messages IEC331I, IEC332I, and IEC333I have been printed to aid in determining the cause of the error and where the error occurred. If a hardware error is not causing the problem, restore or rebuild the catalog. |
| 26 | Explanation: An I/O error
occurred while writing the catalog's self-describing records. Programmer Response: Contact the IBM Support Center. |
| 28 | Explanation: A close error
occurred after the writing of the catalog's self-describing records. Programmer Response: Contact the IBM Support Center. |
| 30 | Explanation: An I/O error
occurred writing records to the catalog. Programmer Response: Contact the IBM Support Center. |
| Reason Code | Description |
|---|---|
| x | Explanation: An internal logic
error has occurred. Programmer Response: Contact the IBM Support Center. An SVC dump may be created for this error, depending on the specific reason code. |
| 6 | Explanation: Attempt to define
an alias that relates to a volume category. Programmer Response: This is an incorrect function. Possible user error. |
| 18 | Explanation: The required
library name was not specified for a define library request. Programmer Response: Supply a library name and rerun the job. |
| 20 | Explanation: Required library
ID was not specified for a define library request. Programmer Response: Supply a library ID and rerun the job. |
| 22 | Explanation: The library logical
type specified is incorrect for a define library record request. Programmer Response: Supply a valid library logic type and rerun the job. |
| 34 | Explanation: Incorrect name
was specified for a define volume category request. Programmer Response: The volume category's name must begin with SYS1.VOLCAT.V. |
| 40 | Explanation: Incorrect checkpoint
indicator was specified for a define volume request. Programmer Response: Supply a valid checkpoint indicator and rerun the job. |
| 42 | Explanation: Incorrect volume
location was specified for a define volume request. Programmer Response: Supply a valid volume location and rerun the job. |
| 44 | Explanation: Required library
name not specified for a define volume request with a volume location
of library specified. Programmer Response: Supply a library name and rerun the job. |
| 46 | Explanation: Incorrect volume
use attribute specified for a define volume request. Programmer Response: Supply a valid use attribute and rerun the job. |
| 48 | Explanation: Required volume
name not specified for a define volume request. Programmer Response: Supply a volume name and rerun the job. |
| 50 | Explanation: Incorrect date
format specified. Programmer Response: Re-specify the date in the following format: YYYY-MM-DD. |
| 56 | Explanation: Attempt to alter
the number of scratch volume message thresholds for an incorrect media
type. Programmer Response: Supply a valid media type and rerun the job. |
| 58 | Explanation: Attempt to alter
the number of scratch volumes for an incorrect media type. Programmer Response: Supply a valid media type and rerun the job. |
| 62 | Explanation: No general volume
category was found. Programmer Response: Define SYS1.VOLCAT.VGENERAL then rerun the job. |
| 66 | Explanation: An attempt
was made to create a volume or library record into a non-volume catalog. Programmer Response: Ensure the high-level qualifier of the volume or library record matches the high-level qualifier of the volume catalog. |
| 68 | Explanation: Non-volume category
was specified for a request associated with volume or library record. Programmer Response: Insure SYS1.VOLCAT.VGENERAL is a volume category for library requests. For volume entry requests, check all catalogs with volume category naming convention to be volume categories. |
| 70 | Explanation: A duplicate entry
name was found during define library or volume request. Programmer Response: Remove the duplicate entry and rerun the job. |
| 72 | Explanation: General volume
category had been deleted or disconnected. Programmer Response: Redefine or reconnect general volume category. |
| 98 | Explanation: Incorrect library
name specified for a define library request. The library name cannot
begin with ‘V’. Programmer Response: Supply a valid library name and rerun the job. |
| 154 | Explanation: Attempting to
delete a library record which is not empty, or scratch volumes is
not equal to zero. Programmer Response: Verify the library record tried to delete. If the library record is empty and the scratch volumes count equal to zero then contact the IBM Support Center |
| 158 | Explanation: Attempting to
delete a volume record that has not reached its expiration date. Programmer Response: Verify the expiration date. ALTER command may be used to alter the expiration date. |
| 168 | Explanation: Attempting to
delete a record without specifying the correct type in catalog parameter
list. Programmer Response: Specify the type and rerun the job. |
| Reason Code | Description |
|---|---|
| x | Explanation:
The length of the catalog work area specified is either zero or too
small. Programmer Response: If using the CSI, use the value returned in CSIREQLN for the workarea length and try again. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: An incorrect
record type was found in the access method services ALTER command. Programmer Response: Determine if the correct name was specified in the command or if the proper fields are requested to be modified for the entry type. |
| 4 | Explanation: A data set name
was not found on the VTOC. Programmer Response: Ensure that the proper versions of the volume and catalog are being processed and that the volume is synchronized with the catalog, or ensure that the VVR/NVR entry type in the VVDS matches its corresponding format 1 DSCB record type from the VTOC. |
| 12 | Explanation: A locate request
to catalog management requires dynamic access to a catalog. Programmer Response: If this error causes a job to end, ensure that the master catalog references the proper catalogs and that they are available to the system when the job stream is processed. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: An error was
encountered while attempting to recall a data set with a volume serial
of MIGRAT. The catalog entry indicated that the data set was migrated,
but DFSMShsm determined that the data set was not migrated. Programmer Response: Review the DFSMShsm message or messages and take the appropriate action. |
| 4 | Explanation: An error was
encountered while attempting to recall a data set with a volume serial
of MIGRAT (the catalog entry indicated that the data set was migrated). Programmer Response: Review the DFSMShsm message or messages and take the appropriate action. |
| 8 | Explanation: An error was
encountered while attempting to delete a data set with a volume serial
of MIGRAT (the catalog entry indicated that the data set was migrated). Programmer Response: Review the DFSMShsm message or messages and take the appropriate action. Check if an attempt to delete a data set in an alternate catalog occurred, while a duplicately named migrated data set exists in a catalog that can be found in the standard search order (via the master catalog). If so, recall the migrated data set and reissue the delete. |
| 12 | Explanation: The catalog installation
exit module issued a locate request, and catalog indicated that the
request was not successful. Programmer Response: Review the DFSMShsm message or messages and take the appropriate action. |
| 16 | Explanation: The catalog installation
exit module was processing a JES3 converter/interpreter (C/I) request
for a data set with a volume serial of MIGRAT (the catalog entry indicated
that the data set was migrated). The exit module determined that
DFSMShsm was not ready to process the JES3 C/I request because of
one of the following reasons:
Programmer Response: Review the DFSMShsm message or messages and take the appropriate action. The DFSMShsm message was issued through a TPUT request to the user ID specified on the job that requested this function. In other words, the message was not routed to the job log. |
| 24 | Explanation: The catalog installation
exit module was processing a JES3 (C/I) request for a data set, and
determined that the request was from an unauthorized user. Programmer Response: Review the DFSMShsm message or messages and take the appropriate action. The DFSMShsm message was issued through a TPUT request to the user ID specified on the job that requested this function. In other words, the message was not routed to the job log. |
| 48 | Explanation: The referenced
data set is in an incomplete status. Programmer Response: Recall the data set and then issue your request again. |
| 50 | Explanation: DFSMShsm generates
this reason code when the installation is using the DFSMShsm patch
to prevent interactive TSO users from being placed in a wait state
while a data set is recalled. This code is generated to cause the
locate to fail instead of placing the TSO session in a wait state
and may be ignored. The recall for the data set has been scheduled
and the function causing the recall should be tried again later. Programmer Response: Submit the requested function again. |
| 52 | Explanation: For TSO HSM RECALL requents,
the RECALL request has been converted to a background request when
the attention key is used and message ARC1020I is replied to with
'Y'. Programmer Response: Information only. No action is required. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: The user provided
work area is too small. Programmer Response: Run the job again with a work area length that is at least equal to the required length. |
| 2 | Explanation: The format 1
work area is too small. Programmer Response: Run the job again with a work area length that is at least equal to the required length. |
| 8 | Explanation: The volume list is too small to include the storage management subsystem workarea. |
For details about how to address the errors indicated by the following reason codes, see z/OS DFSMSdfp Diagnosis z/OS DFSMSdfp Diagnosis, Chapter 6 DADSM/CVAF Diagnostic Aids, and refer to the section entitled "DADSM return and diagnostic codes".
| Reason Code | Description |
|---|---|
| 2 | Explanation: A DADSM RENAME error occurred on branch entry. |
| 4 | Explanation: A DADSM ALLOCATE error occurred on branch entry. |
| 6 | Explanation: A DADSM SCRATCH error occurred on branch entry. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: The delete catalog
work area is too small. Programmer Response: Check the work area length. If it is correct, contact the IBM Support Center. If the length is not correct, run the job again with a valid length. |
| 4 | Explanation: The caller's
work area is too small. Programmer Response: If this is a Catalog Search Interface (CSI) request, you need to increase the size of the work area. Otherwise, this may be a logic error or limitation in the component making the request. |
| 6 | Explanation: An access method
services DELETE command to delete an entire generation data group,
with the FORCE parameter, encountered a work area too small to contain
names of entries deleted. However, the entire GDG was successfully
deleted. The following then occurs:
Programmer Response: Run the job again with a larger work area. |
| 8 | Explanation: The caller's
work area is too small. Programmer Response: If this is a Catalog Search Interface (CSI) request, you need to increase the size of the work area. Otherwise, this may be a logic error or limitation in the component making the request. |
| 12 | Explanation: The amount of
data that the system will return may overflow the workarea. Programmer Response: Either divide the catalog into smaller catalogs or convert to the ICF catalog format. |
| 14 | Explanation: The amount of
data returned by the system cannot be contained in a 2-byte length
field. Programmer Response: None. This is a design limitation. If you are using the CSI (Catalog Search Interface), you must request that fullword lengths be used for all lengths. |
| Reason Code | Description |
|---|---|
| 1 | Explanation: UCBPIN PIN returned
an unexpected return code. Programmer Response: Contact the IBM Service Center. An SVC dump might have been produced for this error. |
| 2 | Explanation: UCBPIN UNPIN returned an
unexpected return code. Programmer Response: Contact the IBM Service Center. An SVC dump might have been produced for this error. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: VSAM has detected
an internal error while processing a catalog index. Programmer Response: Rerun the request. If the error continues, see z/OS DFSMSdfp Diagnosis, Chapter 20 VSAM Diagnostic Aids, section entitled “Recovering from Index Damage” for further instruction. |
| Reason Code | Description |
|---|---|
| x | Explanation: An internal logic
error has occurred. Programmer Response: Contact the IBM Support Center. |
| 6 | Explanation: An ALTER of a
non-VSAM entry is not allowed for the fields being modified. Programmer Response: Ensure that the proper entry name was specified on the access method services ALTER command and that only fields that exist for a non-VSAM entry are requested to be changed. |
| 8 | Explanation: An ALTER of the
catalog name is not allowed. Programmer Response: Ensure that the catalog name was not used by mistake. Catalog names can only be changed by DELETE and then re-DEFINE catalog commands. |
| 10 | Explanation: Erase option
delete, but file name is for incorrect catalog. Programmer Response: Do not use a DD name on the catalog parameter in the access method services DELETE command if erase processing is to be performed. |
| 14 | Explanation: A data set is
update inhibited. Programmer Response: Do not open a data set for reset processing that is inhibited for update processing. |
| 16 | Explanation: A data set is
not reusable. Programmer Response: Do not open a non-empty data set for reset processing that is not reusable. |
| 18 | Explanation: It is only valid
to change the attributes or owner id fields of a GDG base entry by
the access method services ALTER command. Programmer Response: Do not attempt the incorrect ALTER commands. Correct the commands and rerun the job. |
| 24 | Explanation: It is not valid
to attempt to change the name of a user catalog or alias entry through
the use of the access method services ALTER Command. Programmer Response: Do not attempt the incorrect ALTER commands. Correct the commands and rerun the job. |
| 26 | Explanation: It is not valid
to attempt to change the name of a non-VSAM entry that is a GDG base
or member through the use of the access method services ALTER command. Programmer Response: Do not attempt the incorrect ALTER commands. Correct the commands and rerun the job. |
| 28 | Explanation: It is not valid
to attempt to delete a GDG base entry that contains non-VSAM entries. Programmer Response: Delete the members of the GDG base explicitly. Alternatively, the GDG base and its members may be deleted with the use of the FORCE parameter in the DELETE command. |
| 29 | Explanation: RBA too large for data set. |
| 30 | Explanation: It is not valid
to delete the master catalog with the FORCE parameter. Programmer Response: The master catalog cannot be deleted. Submit the job again. |
| 36 | Explanation: The ALTER REMOVEVOLUMES
volume cleanup function contains incorrect coded parameters. Programmer Response: Only the master catalog name, password, and file parameters may be coded for the ALTER REMOVEVOLUMES function. |
| 40 | Explanation: An incorrect
catalog management function, ALTER of a VVDS name, occurred. Programmer Response: Do not attempt the incorrect ALTER commands. Correct the commands. Run the job again. |
| 42 | Explanation: The maximum number
of extensions was exceeded. Programmer Response: Redefine the catalog with a RECORDSIZE specifying a maximum of 32400. |
| 54 | Explanation: An incorrect
reset of a non-reusable data set was detected. Programmer Response: Do not open a non-empty data set for reset processing that is not reusable. |
| 56 | Explanation: The data set
update is inhibited. Programmer Response: Do not open a data set for reset processing that is inhibited for update processing. |
| 60 | Explanation: A define no-allocate
or RECATALOG was not APF authorized. Programmer Response: Probable user error. Ensure that access method services is APF authorized. |
| 64 | Explanation: A DEFINE of a
SYS1.VVDS.Vvolser cannot request space in records. Programmer Response: Change records to tracks or cylinders. Run the DEFINE command again. |
| 70 | Explanation: An ALTER LOCK of the master catalog is not allowed. |
| 72 | Explanation: An incorrect catalog management function alter of a non-VSAM data set name that is cataloged with an indirect volser occurred. |
| 74 | Explanation: An alter newname
of a tape data set is incorrect. Programmer Response: Do not attempt the incorrect ALTER commands. Correct the commands. Run the job again. |
| 76 | Explanation: An alter of non-VSAM
data set that contains the extended format cell is not allowed. Programmer Response: None |
| 78 | Explanation: The conversion of SMS to non-SMS managed cannot be done for a data set that contains the extended format cell. |
| 80 | Explanation: Define data set with extended format information is not valid for a non-SMS data set. |
| 90 | Explanation: Re-cataloging a temporary VSAM data set is not allowed. |
| 94 | Explanation: The conversion of SMS to non-SMS managed cannot be done for a data set that contains attributes extension information. |
| 96 | Explanation: Define data set with attributes extension information is not valid for a non-SMS data set. |
| 98 | Explanation: A define of non-extended
data set that contains compress information is not allowed. Programmer Response: None |
| 102 | Explanation: The request is against an SMS-managed data set, but the specified data set is not SMS managed. |
| 104 | Explanation: The user is not authorized to issue ALTER no VVDS update. |
| 108 | Explanation: The specified SMS construct cannot be altered. |
| 112 | Explanation: A VSAM data set cannot be converted to an SMS managed data set because not all of its components' names resolve to the same catalog. |
| 118 | Explanation: A SMS storage class construct cannot be blanks. |
| 120 | Explanation: The ALTER NEWNAME is not allowed for non-VSAM data set with an alias when the new name resolves to a different catalog than the current one. |
| 122 | Explanation: The ALTER NEWNAME is not allowed for VSAM data set when the new name resolves to a different catalog than the current one. |
| 124 | Explanation: A VSAM data set cannot be converted to SMS managed because not all of the volumes belong to the same storage group. |
| 126 | Explanation: A VSAM data set cannot be converted to SMS managed because not all of its associated names in the sphere resolve to the same catalog. |
| 128 | Explanation: An SMS storage class construct cannot have a length of zero. |
| 130 | Explanation: Altering a non-SMS managed VSAM data set to an SMS managed one (or vice versa) is a stand-alone function. No other ALTER functions are allowed. |
| 132 | Explanation: Altering a non-specific volume serial to a specific one is a stand-alone function. No other ALTER functions are allowed. |
| 134 | Explanation: The user is not authorized to alter a non-specific volume or the user attempted to alter a non-SMS managed data set to include non-specific volser. |
| 136 | Explanation: An incorrect component was supplied for ALTER non-specific volume. |
| 140 | Explanation: An ALTER GDG limit of 0 is not allowed. |
| 142 | Explanation: An ALTER fails due to unsuccessful DADSM UPDATE function. |
| 144 | Explanation: A Record unit of allocation not valid for linear data sets. |
| 146 | Explanation: The ALTER NONVSAM RECATALOG function and the caller pass SMS information for conversion, but the caller is not authorized to use this function. |
| 148 | Explanation: Alter request
is not valid for stand-alone function such as alter of backup while
open (BWO) data set. Programmer Response: Ensure that the field requested to be altered is valid for stand-alone function. |
| 152 | Explanation: An attempt has
been made to define a PDSE as a member of a GDG base. PDSEs may not
be a member of a GDG base Programmer Response: Be sure that the IGDSMS00 parmlib member has DSNTYPE default of PDS. |
| 156 | Explanation: The alter backup
while open (BWO) request is not for valid component or record. Programmer Response: Ensure that the BWO alter request is for cluster, data, non-VSAM, or GDS only. |
| 158 | Explanation: The alter backup
while open (BWO) indicator is incorrect for non-SMS managed data sets Programmer Response: Ensure that the data set is SMS-managed. |
| 160 | Explanation: An attempt was
made to alter a non-SMS managed non-VSAM data set to a name in the
format of a GDS (for example, the name ends with GnnnnVnn). Programmer Response: Change the name of the new data set to be a non-GDS format name. |
| 162 | Explanation: An attempt was made to alter a non-SMS managed GDS to a non-GDS name. |
| 166 | Explanation: An alter volume
or device type on OAM entries is not allowed. Programmer Response: None |
| 168 | Explanation: An attempt was
made to alter an SMS-managed non-VSAM data set to a GDS name (for
example, the name ends with GnnnnVnn), but there is no GDG base associated
with the new name. Programmer Response: Change the name of the new data set to one that has an existing GDG base definition. |
| 170 | Explanation: When defining
an OAM data set, a generation data set low level qualifier (that is,
G0000V00) or an increment of a GDG number (that is, +1) is invalid. Programmer Response: Use a name other than the GDS low level qualifier or a GDG increment number. Rerun the define request. |
| 172 | Explanation: REUSE was specified for a non-cluster component or a component that had an AIX Associated with it. |
| 174 | Explanation: ALTER REUSE was specified for a cluster that has an AIX defined over it. |
| 175 | Explanation: A DEFINE of a striped data set specified REUSE, which is invalid. |
| 176 | Explanation: ALTER REUSE was specified for a cluster that contains a KEYRANGE. |
| 178 | Explanation: ALTER-REUSE-ON
and ALTER-REUSE-OFF are mutually exclusive. They cannot be active
at the same time. Programmer Response: Only one ALTER-REUSE bit should be set at a time. |
| 184 | Explanation: Attempted to ALTER the DDM file class attribute for other than a CLUSTER or NONVSAM entry. |
| 186 | Explanation: Attempted to ALTER the pointer to the last active record for other than CLUSTER or NONVSAM entry. |
| 188 | Explanation: Attempted to ALTER DFM attributes for a non-SMS data set. |
| 190 | Explanation: Attempted to ALTER DFM attributes for other than a CLUSTER entry. |
| 192 | Explanation: Attempted to ALTER DFM attributes for other than a CLUSTER or NONVSAM entry. |
| 194 | Explanation: A specific request
to locate an OAM data set was made and a data set was found, but it
is not an OAM data set name. Programmer Response: Verify that the name of the data set desired is an OAM data set. |
| 196 | Explanation: A specific request
to locate an OAM data set was made and a data set was found, but it
is not an OAM data set name. Programmer Response: Verify that the name of the data set desired is an OAM data set. |
| 200 | Explanation: The ALTER ADDVOL
function cannot be used to cause the number of volumes of a SMS-managed
data set to exceed the maximum of 59 volumes. Programmer Response: The maximum allowable volumes for a SMS-managed data set is 59. If this error was issued incorrectly, contact the IBM Support Center. |
| 202 | Explanation: A request to
re-catalog a temporary non-VSAM data set is not valid. Programmer Response: Correct the request. If the error recurs, contact the IBM Support Center. |
| 204 | Explanation: HSM-INCOMPLETE-ON
and HSM-INCOMPLETE-OFF are mutually exclusive. They cannot be active
at the same time. Programmer Response: Only one HSM-INCOMPLETE bit should be set at a time. |
| 216 | Explanation: Define of ACCOUNT
information is invalid for non-SMS-managed data sets. Programmer Response: Ensure that the data set is SMS- managed and then rerun the request. |
| 218 | Explanation: Alter of ACCOUNT
information is invalid for non-SMS-managed data sets. Programmer Response: Ensure that the data set is SMS-managed and then rerun the request. |
| 222 | Explanation: Extended attribute
(AX) cell and ACCOUNT information are mutually exclusive for define
or alter request. Programmer Response: Ensure that the AX cell and ACCOUNT information are not both specified during define or alter of the data set. |
| 226 | Explanation: Multivolume DEFINE
RECATALOG of a data set with an indirect volser is not supported. Programmer Response: Ensure that the VOLUME parameter for the DEFINE RECATALOG has only one indirect volume serial specified before attempting the DEFINED RECATALOG. |
| 228 |
Explanation: An alter of
a non-EA SMS-managed VSAM LDS to Extended Addressable is not allowed.
Only valid data set type is a non-SMS managed VSAM LDS. Programmer Response: Ensure that the data set on the ALTER EXTENDEDADDRESSABLE command is a non-SMS managed VSAM LDS and re-issue the request. If the problem persists, contact the IBM support center with the job output and/or dump. |
| Reason Code | Description |
|---|---|
| x | Explanation: An internal logic
error has occurred, or an error has been detected in the structure
or contents of a VVDS. Programmer Response: Run a DIAGNOSE and print the VVDS associated with the problem. These errors will usually be accompanied by additional console messages which contain SFI information necessary to diagnose the problem. Contact the IBM Support Center. |
| 2 | Explanation: New catalog name
added. This is a normal return code returned during the adding of
a new VVR. The associated catalog name of the VVR was new to the VVDS
and was added to the VVCR/VVCN record. Programmer Response: None |
| 4 | Explanation: VVDS Manager
parameter list had incorrect information. This attention error code
does not effect the operation of the request. Programmer Response: Contact the IBM Support Center. |
| 5 | Explanation: The VVDS required
for LISTCAT could not be accessed. The missing data in the LISTCAT
output will contain Xs. The volume might be offline, but a mount request
is not automatically issued for a LISTCAT operation. If
present, the sfi value is FOR volser,
where volser is the volume serial of the VVDS on
which the error was detected. Programmer Response: Ignore the return code or ensure the volume is online and available for the LISTCAT operation. |
| 6 | Explanation: A requested VVR
or NVR was not found in the VVDS specified. If present
in this message, the sfi value is FOR volser,
where volser is the volume serial of the VVDS on
which the error was detected. The sfi value
in message IEC331I contains characters 5 through twelve of the requested
VVR name. Programmer Response: Ensure that the volume serial numbers provided in VOLUMES parameters and DD statements are correct. If all the commands are specified correctly, this condition may indicate an error in the catalog or VVDS. Run the DIAGNOSE command to determine if any catalog records are in error. |
| 7 | Explanation: One or more of
the 3 required VVRs for a catalog was not found. sfi in
message IEC331I contains the first 8 characters of the catalog name
whose VVR(s) was missing. Programmer Response: Run DIAGNOSE command against the VVDS and correct any problem detected. |
| 8 | Explanation: A DEFINE command
for a VVDS has failed because a VVDS already exists on the volume.
No SFI data. Programmer Response: If the existing VVDS is to be replaced, delete it before defining the new VVDS. |
| 9 | Explanation: A dynamic allocation
will require a TIOT slot, but a search finds none available. No SFI
data. Programmer Response: Contact the IBM Support Center. |
| 10 | Explanation: Bad return code
from dynamic allocation issued from DFSMS/MVS. SFI contains the SVC 99 reason
code. Programmer Response: Ensure that the VVDS name or the volume serial number provided is correct. If an access method services command was being processed, ensure that all required FILE parameters are supplied. Ensure that the volume will be mounted and available by providing a DD statement for the volume. |
| 11 | Explanation: The caller of
the VVDS manager passed a volume serial number in the parameter list
and a UCB address. The UCB's volume serial does not match the parameter
list volume serial. The SFI contains the UCB volume serial while
the parameter list volume serial is in the second field in the SFI
data. Programmer Response: Contact the IBM Support Center. |
| 12 | Explanation: An attempt to
allocate space on a DASD volume has failed. SFI contains the historical
return code from DADSM allocate. Programmer Response: Ensure that there is enough space for the VVDS data set being defined. The data set will require a minimum of three to four tracks. If space was available when the error occurred, contact the IBM Support Center. |
| 13 | Explanation: The VSAM volume
data set (VVDS) request contained an invalid volume serial number
(VOLSER). The invalid VOLSER might be available with the structured
field introducers (SFI) information. Programmer Response: Rerun the request with a valid VOLSER. |
| 14 | Explanation: A request to
delete a VVDS has failed because the VVDS still contained VVRs. SFI
contains the RBA of the first CI that contains a VVR. Programmer Response: If the VVDS is to be deleted, first delete the VSAM data sets on the volume and then run the DELETE command again. Or, if the VVDS is to be recovered, run the DELETE command again with the RECOVERY parameter. |
| 16 | Explanation: No storage was
available for the VVDS manager work area. There may be no SFI data
because the working storage for the VVDS manager could not be obtained.
Otherwise, SFI will contain the register 15 return code from the
GETMAIN request. Programmer Response: Contact the IBM Support Center. |
| 17 | Explanation: No storage was
available for VVDS manager buffers. SFI contains ‘xxxxzzzz’
where xxxx is the amount of storage being requested
and zzzz is the register 15 return code from the
GETMAIN request. Programmer Response: Increase available LSQA storage. This error can sometimes be avoided by decreasing the region size. |
| 18 | Explanation: An I/O error
has been detected while accessing a VVDS record. This reason code
results in message IEC161I being issued, which provides more information
about the error. An SVC dump may also have been created, depending
on the type of error that occurred. Programmer Response: A DIAGNOSE should be run against the VVDS indicated in message IEC161I. If an SVC dump was produced, contact the IBM Support Center. |
| 25 | Explanation: An OBTAIN was
issued to read the F1 DSCB for an existing VVDS and OBTAIN returned
with an error. SFI contains the register 15 return code from OBTAIN. Programmer Response: A failure to obtain a DSCB for a VVR may indicate either a damaged VVDS or the existence of an orphan VVR. In either case, enter the DIAGNOSE command to check the integrity of the VVDS. Correct any errors found as a result of using the DIAGNOSE command. |
| 26 | Explanation: An OBTAIN was
issued to read the F1 DSCB for a new VVDS and OBTAIN returned with
an error. SFI contains the register 15 return code from OBTAIN. Programmer Response: A failure to obtain a DSCB for a VVR may indicate either a damaged VVDS or the existence of an orphan VVR. In either case, enter the DIAGNOSE command to check the integrity of the VVDS. Correct any errors found as a result of using the DIAGNOSE command. |
| 28 | Explanation: A call to VSAM
end of volume to extent the VVDS has failed. SFI contains register
15 return code from end of volume. Programmer Response: There is probably insufficient space on the volume or in the VTOC to extend the VVDS, in which case no more VSAM data sets can be defined on that volume until space is made available to extend the VVDS. If sufficient space is available at the time this error occurs, contact the IBM Support Center. |
| 30 | Explanation: While updating
the VVDS, it was found to be full and needed to extend, but was already
at the maximum number of extents (123). There is no SFI data. Programmer Response: The volume must be recovered from backup after creating a larger VVDS, or unneeded data sets on the volume must be deleted to release space in the VVDS. |
| 32 | Explanation: The
VVDS is full (maximum 1048575 CIs). There is no SFI data. Programmer Response: If a VSAM data set was being defined, use an alternate volume. If a VVDS was being defined, decrease the primary space allocation. |
| 36 | Explanation: A request to
write a VVR could not be processed because the VVR was larger than
the max size of a valid VVR. SFI contains the VVR length. Programmer Response: Run a DIAGNOSE and print the VVDS associated with the problem. These errors will usually be accompanied by additional console messages which contain SFI information necessary to diagnose the problem. Contact the IBM Support Center. |
| 38 | Explanation: A DELETE command
with the NOSCRATCH parameter has been issued for a catalog. The VVR
for the catalog was not deleted because the catalog has data on the
volume. SFI contains the RBA of the first CI that has a VVR owned
by the catalog. Programmer Response: Ensure that the correct catalog is being used and that the VVDS is correctly specified. |
| 40 | Explanation: A call to scratch
the F1 DSCB from a volume has failed. SFI contains the return code
from the scratch. Programmer Response: It is possible that a user other than the one issuing the delete has an outstanding ENQ on the VVDS. If this is the case, the ENQ should be removed. |
| 80 | Explanation: An internal VVDS
logic error has occurred. If the SFI information contains “IORUNING”,
the job associated with the catalog request may have been terminated
abnormally (for example, operator CANCEL, TSO attention ) and this
does not represent an internal logic error. Programmer Response: If the SFI information contains “IORUNING”, check console and job logs for the associated job to see if it was abnormally terminated. You should run a DIAGNOSE against VVDS on the volume indicated to check for any possible damage. If the SFI information is not “IORUNING”, you should contact IBM Service. |
| 82 | Explanation: The system discovered,
during synchronization processing of the VTOC and VVR extents, that
the number of extents indicated for the data set in the VTOC is more
than the number indicated in the VVR. Programmer Response: Print the VVDS and VTOC. Contact the IBM Support Center. |
| 84 | Explanation: The system discovered,
during synchronization processing of the VTOC and VVR extents, that
the number of extents indicated for the data set in the VVR is more
than the number indicated in the VTOC. Programmer Response: Print the VVDS and VTOC. Contact the IBM Support Center. |
| 85 | Explanation: During synchronization
processing of the VTOC and VVR extents, the VVDS manager was unable
to read the DSCBS. Programmer Response: Print the VVDS and VTOC. Contact the IBM Support Center. |
| 86 | Explanation: The VVR for the
VVDS number of extents field is not valid; it has more than 123 extents
in it. SFI contains the VVR's extent number. Programmer Response: Print the VVDS. Contact the IBM Support Center. |
| 87 | Explanation: During
open processing of a VSAM data set, the system discovered that there
were fewer extents in the VTOC than were described in the VVDS for
the component, or that the extent ranges did not match between the
VVDS and VTOC. System Action: The data set will not be permitted to open. Message IEC331I is issued to detail which volume and component is incorrect. Programmer Response: Use LISTCAT and LISTVTOC to determine the details of the mismatch. The data set must be recreated to correct the error. |
| 88 | Explanation: A VVR or NVR
with the correct component name was found, but the catalog name did
not match. On a delete request, the BCS record will be deleted, but
the VVR or NVR and the format 1 DSCB will not be scratched. There
is no SFI data. Programmer Response: No action is required because this code is for information only. |
| 89 | Explanation: During
open processing of a VSAM data set, the system discovered that there
were extra extents in the VTOC that are not described in the VVR. System Action: Message IEC331I is issued to detail which volume and component of the data set has extra extents on the volume. Open processing continues. In most cases, on the next extend of the data set the extra extents will be recognized and incorporated into the data set extents. |
| 92 | Explanation: A request to
allocate dynamically the VVDS has failed. SFI contains the dynamic
allocation error reason code returned in the SVC 99 request block,
or text stating why the allocation routine failed. Programmer Response: Determine why the dynamic allocation reason code was returned. |
| 94 | Explanation: A VSAM OPEN request to open
the VVDS failed. SFI contains ‘xxrrrrrr’, where rrrrrr=register 15
from the OPEN and xx is ACBERFLG. Programmer Response: Determine why the OPEN reason code was returned. |
| 96 | Explanation: A record read
from the VVDS was found to be invalid. System Action: Message IEC331I will be issued in the job log and will contain the RBA and volume serial of the invalid record. An SVC dump will be created for the problem. Programmer Response: A DIAGNOSE of the VVDS should be performed and any errors related to the VVDS corrected. If no errors are detected, contact IBM Service and provide the SVC dump for analysis. |
| 100 | Explanation: A F1 DSCB with
a SYS1.VVDS.Vxxxxxx was found and it is not a VSAM data set. A VVDS
cannot be created or opened for this volume. Programmer Response: Determine the source of the non-VSAM data set and have it renamed or removed. |
| 126 | Explanation: VVDS detected a potential
problem with VVDS internal structure. When attempting to correct problem
a free control interval (CI) could not be found, which was required
for the repair operation. An SVC dump should have occurred. Programmer Response: Run a DIAGNOSE and print the VVDS associated with the problem. Contact IBM Service and provide the SVC dump plus the DIAGNOSE and print of the problem VVDS. |
| 128 | Explanation: A VVDS request (add, insert,
or delete) took very long to complete. Programmer Response: Please provide any dumps to IBM support. |
| Reason Code | Description |
|---|---|
| x | Explanation: The reason codes
associated with this error are from one of the following:
|
| Reason Code | Description |
|---|---|
| 2 | Explanation: The system attempted
to verify alter authority to the master catalog (update authority
for an ALTER NEWNAME), but the user did not have the required authority. Programmer Response: Ensure the user has the proper authority to the master catalog. For some types of requests, only the proper data set authority is required, and the master catalog is only checked if they do not have necessary data set authority. Granting the authority to the data set may eliminate this error. |
| 4 | Explanation: A non-system
caller has specified request special authority level checking in the
catalog parameter list. Programmer Response: Contact the IBM Support Center if the user written programs are not calling catalog management. |
| 6 | Explanation: The user did
not have the required access authority to the specified entry. Programmer Response: Ensure the user has the proper RACF® authorization for the function being requested. |
| 8 | Explanation: The return code
from the RACHECK REQUEST=AUTH was other than 0, 4, or 8. Programmer Response: Determine the reason for the unexpected RACF return code. |
| 14 | Explanation: An implicit alter
of a GDG was denied because the user did not have the proper authority
to the GDG base and the catalog. Programmer Response: Ensure the user has the proper authority for the GDG base. |
| 16 | Explanation: The caller is not authorized for the requested SMS Management Class, SMS Storage Class, or both. |
| 28 | Explanation: An unauthorized
caller attempted to define an SMS data set. Programmer Response: Ensure the caller is APF authorized, or system key or system state. |
| 30 | Explanation: The caller was not authorized to the catalog when defining an SMS data set into the master catalog. |
| 32 | Explanation: The return code
from the RACHECK REQUEST=AUTH was other than 0, 4, or 8 when attempting
to verify access to a facility class. Programmer Response: Determine the reason for the unexpected RACF return code. |
| 34 | Explanation: An internal logic
error has occurred. Programmer Response: Contact the IBM Support Center. |
| 36 | Explanation: The caller is not authorized. When no profile exists for functions that require RACF authorization, the caller must be at least APF authorized. |
| 40 | Explanation: RACF options do not permit use or cataloging of uncataloged non-SMS managed data sets. |
| 42 | Explanation: Caller is not
authorized to use the specified volume. Programmer Response: Acquire authority to the specified volume and resubmit the job. |
| 44 | Explanation: Caller is not authorized to update catalog for DEFINE ATL request |
| Reason Code | Description |
|---|---|
| 2 | Explanation: The allocation
quantity requested for the dataset resulted in an amount greater than
16,777,215 CYL on the primary space quantity. Programmer Response: Reduce the primary space quantity and rerun the request. |
| 4 | Explanation: The allocation
quantity requested for the dataset resulted in an amount greater than
16,777,215 CYL on the secondary space quantity. Programmer Response: Reduce the secondary space quantity and rerun the request. |
| 6 | Explanation: The striped data set was
allocated with a primary space allocation of more than 16777215 tracks.
The maximum primary allocation in tracks that can be specified on
the define is 16777215. Programmer Response: Reduce the primary space allocation and rerun the request. |
| 8 | Explanation: The striped data set was
allocated with a secondary space allocation of more than 16777215
tracks. The maximum secondary allocation in tracks that can be specified
on the define is 16777215. Programmer Response: Reduce the secondary space allocation and rerun the request. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: Probable system
error. An incorrect entry type for an extract operation was detected. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 4 | Explanation: An incorrect
entry type (cluster or non-VSAM) was detected. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 6 | Explanation: An incorrect
cluster entry for ALTER of data set attributes was detected. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 8 | Explanation: An incorrect
cluster or index entry for ALTER of buffer size was detected. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 10 | Explanation: An incorrect
entry type (CLUSTER) to ALTER the FREESPACE or WRITECHECK parameters
was detected. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 12 | Explanation: An incorrect
entry type (CLUSTER) to ALTER volumes was detected. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 14 | Explanation: Probable system
error. An incorrect catalog parameter list was supplied in an attempt
to add a volume. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 16 | Explanation: An
attempt was made to alter an SMS-managed data set to add or delete
volumes from the data set; however, one or more of the volume specifications
were specific volume serial numbers. Programmer Response: Only nonspecific volume serial numbers can be added to or removed from SMS-managed data sets. Correct the specification in the ALTER command and retry it. |
| 20 | Explanation: The upgrade set
association in the base cluster data record does not point to an upgrade
set record. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 22 | Explanation: The data association
in the cluster record does not point to a data record. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 26 | Explanation: ALTER of EXCEPTIONEXIT
was specified, but the entry is not a data or index component. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 28 | Explanation: ALTER of average
RECORDSIZE was specified, but the entry is not a data or index component. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 30 | Explanation: ALTER of expiration
date was specified but the entry is not a cluster, alternate index,
or path. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 32 | Explanation: ALTER of last back-up date was specified, but the component is not a cluster, non VSAM, or GDS. |
| 34 | Explanation: ALTER of last back-up date was specified, but the data set is non-SMS managed and does not have a last back-up date. |
| 36 | Explanation: An alias entry
may only be defined for non-VSAM or user catalog entries. Programmer Response: Do not attempt an incorrect DEFINE operation. |
| 38 | Explanation: A LOCATE or ALTER
was specified for a GDG base, and entry is not a GDG. Programmer Response: GDGs must have qualified names. Ensure that all levels of qualification are specified for GDG. Submit the job again. |
| 40 | Explanation: An input base
record to catalog upgrade management is not an alternate index, cluster
or data type entry. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP 11 option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 42 | Explanation: An input base
record to catalog reusable processing is not a data type entry. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog entry is still valid, by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP 11 option. Contact the IBM Support Center. Otherwise, correct the error. Run the job again. |
| 44 | Explanation: An incorrect
entry type was encountered in a DELETE operation, other than the expected
alias entry. Programmer Response: Ensure that the proper entry name was specified and that the catalog reflects the expected structure. It may be necessary to rebuild the catalog. |
| 46 | Explanation: An incorrect
entry type was encountered in a DELETE operation, other than the expected
VVR type. Programmer Response: Ensure that the proper entry name was specified. |
| 48 | Explanation: An entry type other than the expected NVR type was encountered in a DELETE operation. |
| 50 | Explanation: An incorrect
entry type, other than the expected BCS type, was encountered in a
delete operation. Programmer Response: Ensure that the correct entry type was specified. |
| 52 | Explanation: ALTER of SMS constructs was specified, but the component is not a cluster, non-VSAM, or GDS. |
| 54 | Explanation: Define an Extended
Format UCAT is not allowed. Programmer Response: Define the UCAT as a non-Extended Format data set. |
| 56 | Explanation: ALTER of FILEID
or CCSID is not allowed with other DFM attributes. Programmer Response: Ensure that no other DFM attributes are being altered in the same request. Run the job again. |
| 58 | Explanation: ALTER of CCSID
is not allowed for non-SMS managed data set, or the data component
of a catalog. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 60 | Explanation: ALTER of FILEDATA is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 62 | Explanation: An attempt has
been made to alter DFM attributes for a non-SMS managed data set.
Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 64 | Explanation: ALTER of 'DFM/NFSS
ACCESS AUTH' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 66 | Explanation: ALTER of 'DFM/NFSS
ACCESS TIME' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 70 | Explanation: ALTER of 'DFM/NFSS
USERID' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 72 | Explanation: ALTER of 'DFM/NFSS
GROUPID' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 74 | Explanation: ALTER of 'DFM/NFSS
LAST SIZE CHANGE' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 76 | Explanation: ALTER of 'DFM/NFSS
MODIFIED TIME' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 78 | Explanation: ALTER of 'DFM/NFSS
ATTR CHNG TIME' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 80 | Explanation: ALTER of 'DFM/NFSS
BINARY FILE SIZE' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 82 | Explanation: ALTER of 'DFM/NFSS
LOGICAL RECORD COUNT' field is not allowed for non-SMS managed data
set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. |
| 84 | Explanation: ALTER of 'DFM/NFSS
CHARS NO PADDING' field is not allowed for non=SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 86 | Explanation: ALTER of 'DFM/NFSS
TEXT TIMESTAMP' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 88 | Explanation: ALTER of 'DFM/NFSS
ATTRIBUTE EXTENSION FLAGS' is not allowed for non-SMS managed data
set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 90 | Explanation: ALTER of 'DFM/NFSS
EXTENSION AREA' field is not allowed for non-SMS managed data set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM or non-VSAM data set. Correct the error. Run the job again. |
| 92 | Explanation: ALTER of the
RLS SMS flag is not allowed for a data set that is not capable of
being used by RLS. Data sets that are Linear, non-SMS managed, keyrange
or temporary are not eligible for RLS access. Programmer Response: Ensure that the entry being altered is eligible for RLS processing. Correct the error. Run the job again. |
| 94 | Explanation: ALTER of the
RLS recovery timestamp (local) is not allowed for a data set that
is not capable of being used by RLS. Data sets that are Linear, non-SMS
managed, keyrange or temporary are not eligible for RLS access. Programmer Response: Ensure that the entry being altered is eligible for RLS processing. Correct the error. Run the job again. |
| 96 | Explanation: ALTER of the
RLS recovery timestamp (GMT) is not allowed for a data set that is
not capable of being used by RLS. Data sets that are Linear, non-SMS
managed, keyrange or temporary are not eligible for RLS access. Programmer Response: Ensure that the entry being altered is eligible for RLS processing. Correct the error. Run the job again. |
| 98 | Explanation: ALTER of the
RLS flags is not allowed for a data set that is not capable of being
used by RLS. Data sets that are Linear, non-SMS managed, keyrange
or temporary are not eligible for RLS access. Programmer Response: Ensure that the entry being altered is eligible for RLS processing. Correct the error. Run the job again. |
| 100 | Explanation: ALTER of the
BWO flag is not allowed for non-SMS managed data set or a linear data
set. Programmer Response: Ensure that the entry being altered is an SMS managed VSAM data set that is not LINEAR. Correct the error. Run the job again. |
| 102 | Explanation: ALTER of 'ACCOUNT
INFORMATION' is specified but the entry type is not Data, NonVSAM,
or GDS. Programmer Response: Ensure that the name of the entry specified in the command is correct. Ensure that the catalog is still valid by performing a LISTCAT run. If the reason code indicates a system error, list the catalog using the PRINT command with the DUMP11 option. Contact the IBM Support Center. Otherwise, correct the error and run the job again. |
| 104 | Explanation: Invalid entry type for alter of extended addressability data set. |
| 106 | Explanation: ALTER of the
LOGSTREAMID parameter is not allowed for a data set that is not capable
of being used by RLS. Data sets that are Linear, non-SMS managed,
keyrange or temporary are not eligible for RLS access. Programmer Response: Ensure that the entry being altered is eligible for RLS processing. Correct the error. Run the job again. |
| 108 | Explanation: ALTER of the
LOG parameter is not allowed for a data set that is not capable of
being used by RLS. Data sets that are Linear, non-SMS managed, are
keyrange or temporary are not eligible for RLS access. Programmer Response: Ensure that the entry being altered is eligible for RLS processing. Correct the error. Run the job again. |
| 110 | Explanation: ALTER of the
FRLOG parameter is not allowed for a data set that is not capable
of being used by RLS. Data sets that are Linear, non-SMS managed,
are keyrange or temporary are not eligible for RLS access. Programmer Response: Ensure that the entry being altered is eligible for RLS processing. Correct the error. Run the job again. |
| 112 | Explanation: An IDCAMS SHCDS
command with either the CFRESET or CFRESETDS keywords was issued against
a data set not capable of being used by RLS. Data sets that are Linear,
non-SMS managed, are keyrange or temporary are not eligible for RLS
access. Programmer Response: Ensure that the entry being altered is eligible for RLS processing. Correct the error. Run the job again. |
| Reason Code | Description |
|---|---|
| x | Explanation: An attempt to
extend a striped data set to a new volume encountered an internal
logic error when locating the volume information in the catalog to
be updated. Programmer Response: Contact the IBM Support Center. |
| Reason Code | Description |
|---|---|
| x | Explanation: An internal logic
error has occurred. Programmer Response: Contact the IBM Support Center. |
| 6 | Explanation: The association
of a true name record in an ICF catalog is incorrect. Programmer Response: Use access method services to define the associated base of the true name record. |
| 8 | Explanation: The association of a true name record is not in the IEASYMxx member, or the SYMBOLICRELATE function did not provide a symbolic item. Programmer Response: Check the IEASYMxx to ensure that the item has a symbolic item, or the SYMBOLICRELATE function does not provide a symbolic item. |
| Reason Code | Description |
|---|---|
| x | Explanation: The reason code listed is the return code from the DADSM function, which may have been a RENAME or a SCRATCH request. |
| Reason Code | Description |
|---|---|
| x | Explanation: The returned
DADSM Historic Return Code was other than 0, 4, 8, or 12. The reason
code shown is the DADSM return code. See z/OS DFSMSdfp Diagnosis for
an explanation of the DADSM return and diagnostic codes. Programmer Response: The return code is returned by DADSM. |
| 22, 24 | Explanation: An attempt to allocate an SMS-managed
data set using the Best Fit interface was able to allocate space on
all supplied volumes, but the amount of space allocated was not the
total amount required. If the data set being allocated was not SMS-managed
then reason code 20 indicates requested space was not available; The
primary allocation amount must be able to be allocated within 5 extents.
For a non SMS-managed VSAM data set the primary allocation amount
must be available on each volume if the data set is a multivolume
data set. Programmer Response: The storage group did not contain sufficient space to allocate the data set. If this was a non SMS-managed data set being allocated, the volume(s) did not have sufficient space for the primary allocation amount. |
| 26 | Explanation: An attempt to
allocate an SMS-managed data set using the Best Fit interface resulted
in more than 255 extents for the data set. VSAM data sets are limited
to a maximum of 255 extents. Programmer Response: This is most likely a result of significant fragmentation on the volumes selected. Volume reorganization should be performed, or additional volumes added to the storage group with sufficient contiguous space to allow to the allocate to complete. |
| 28 | Explanation: The volume does
not contain enough track-managed space to allocate the BCS, VVDS or
page data set. Programmer Response: Try the request with a different volume. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: An internal logic
error has occurred processing a GDS record. Programmer Response: Contact the IBM Support Center. |
| Reason Code | Description |
|---|---|
| 4 | Explanation: Unable to mount
user volumes. Programmer Response: Ensure that proper volumes are implicitly or explicitly allocated by the JCL. |
| 8 | Explanation: An error occurred
while attempting to mount the user volume. Examples of possible errors
include insufficient virtual storage for workareas or a time-stamp
mismatch problem. Programmer Response: Verify that the volume and the volume information (time stamps) contained in the catalog are at the same level. If the problem is due to insufficient virtual storage, specify a larger region parameter. Run the job again. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: The volume cell
for a base clusters data or index component was not found. A DEFINE
alternate index command was being processed. Programmer Response: Run access method services DIAGNOSE command for additional information. The base cluster may have to be deleted with the NOSCRATCH option and redefined with the RECATALOG option. |
| 2 | Explanation: The relate cell
was not found in the base cluster sphere record while a moved subrecord
update was in progress. Programmer Response: Run access method services DIAGNOSE command against the catalog and then determine the action to be taken. Delete with the NOSCRATCH parameter. Define with the RECATALOG parameter. |
| 4 | Explanation: An association
cell was not found for a path or alias record while a subrecord move
update was in progress. Programmer Response: Run access method services DIAGNOSE command against the catalog and then determine the action to be taken. Delete with the NOSCRATCH parameter. Define with the RECATALOG parameter. |
| 10 | Explanation: The SMS cell
was not found in the VVDS entry for a data set, even though the data
set is SMS-managed. Programmer Response: Run access method services DIAGNOSE command against the catalog and then determine the action to be taken. The data set may need to be copied to a new SMS data set and the failing data set deleted. |
| 12 | Explanation: The SMS cell
was not found in the BCS entry for a data set, even though the data
set is SMS-managed. Programmer Response: Run access method services DIAGNOSE command against the catalog and then determine the action to be taken. The catalog may be repaired by doing a DELETE NOSCRATCH, followed by DEFINE RECATALOG. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: Access method
services ALTER name change of a unique object was specified, but no
volumes containing any part of the data set were mounted. Programmer Response: Ensure that JCL statements cause the proper volumes and units to be allocated. Also, ensure that all DDNAMES specified match the access method services dname parameter when specified. Determine a minimum unit count and have sufficient units available for job processing. Ensure that volumes are allocatable by the use of dynamic allocation. |
| 2 | Explanation: The volume was
not mounted when expected. Programmer Response: Ensure that JCL statements cause the proper volumes and units to be allocated. Also, ensure that all DDNAMES specified match the access method services dname parameter when specified. Determine a minimum unit count and have sufficient units available for job processing. Ensure that volumes are allocatable by the use of dynamic allocation. |
| 8 | Explanation: A scan of the
task I/O table (TIOT) failed to find a needed JCL DD statement. Programmer Response: Ensure that you have all needed JCL DD statements and that all JCL statements cause the proper volumes and units to be allocated. Also, ensure that all DDNAMES specified match the access method services dname parameter when specified. Determine a minimum unit count and have sufficient units available for job processing. Ensure that volumes are allocatable by the use of dynamic allocation. For a non-VSAM data set, ensure the number of volumes on the DD statement match the number of volumes where the data set resides. |
| 10 | Explanation: A scan of the
task I/O table (TIOT) failed to find the user specified JCL ddname
statement. Programmer Response: Ensure that JCL statements cause the proper volumes and units to be allocated. Also, ensure that all DDNAMES specified match the access method services dname parameter when specified. Determine a minimum unit count and have sufficient units available for job processing. Ensure that volumes are allocatable by the use of dynamic allocation. |
| 12 | Explanation: A scan of the
task I/O table (TIOT) failed to find the user specified JCL ddname
statement. Programmer Response: Ensure that JCL statements cause the proper volumes and units to be allocated. Also, ensure that all dynamis specified match the access method services dname parameter when specified. Determine a minimum unit count and have sufficient units available for job processing. Ensure that volumes are allocatable by the use of dynamic allocation. |
| Reason Code | Description |
|---|---|
| x | Explanation: An internal logic
error occurred while processing a subrecord. Programmer Response: Contact the IBM Support Center. |
| Reason Code | Description |
|---|---|
| x | Explanation: An internal logic
error occurred. Programmer Response: Contact the IBM Support Center. |
| 0 | Explanation: The related object
is reusable. Programmer Response: Correct the DEFINE command so that the entry named in the RELATE parameter is proper for the type of object being defined. |
| 2 | Explanation: The related object
is a relative-record data set or a linear data set. Programmer Response: Correct the DEFINE command so that the entry named in the RELATE parameter is proper for the type of object being defined. |
| 4 | Explanation: The related object
does not exist. Programmer Response: Correct the DEFINE command so that the entry named in the RELATE parameter is proper for the type of object being defined. |
| 6 | Explanation: An alternate
index or path is not allowed to be built over a catalog. Programmer Response: Correct the DEFINE command so that the entry named in the RELATE parameter is proper for the type of object being defined. |
| 8 | Explanation: The names of
an alternate index or path and a related object are identical. Programmer Response: Correct the DEFINE command so that the entry named in the RELATE parameter is proper for the type of object being defined. |
| 10 | Explanation: There is no pointer
to a related object of an alternate index or path. Programmer Response: Correct the DEFINE command so that the entry named in the RELATE parameter is proper for the type of object being defined. |
| 12 | Explanation: An alternate
index is not to be built over a base cluster, or the related path
object is not a cluster or an alternate index. Programmer Response: Correct the DEFINE command so that the entry named in the RELATE parameter is proper for the type of object being defined. |
| 14 | Explanation: A DEFINE PATH
command specified a PATHENTRY name of a PAGESPACE object. Programmer Response: Correct the path entry name. Run the DEFINE PATH command again. |
| 16 | Explanation: A DEFINE PATH
command has specified a PATHENTRY name for a VVDS. Programmer Response: Correct the path entry name. Run the DEFINE PATH command again. |
| 20 | Explanation: The related object
for a DEFINE ALTERNATEINDEX is a VVDS. Programmer Response: Correct the related name. Run the DEFINE AIX command again. |
| 28 | Explanation: The related name
specified for a DEFINE ALIAS command is for a record type other than
NONVSAM or USERCATALOG. Programmer Response: Ensure that the related name is correct and that a DEFINE ALIAS command is desired. If the above is true refer to access method services DIAGNOSE command to obtain additional information. |
| 30 | Explanation: The version number of the
related generation data set name does not match the version number
in the base GDG. The DEFINE ALIAS will fail. Programmer Response: Correct the version number in the GnnnnVnn part of the generation data set name. Run the DEFINE ALIAS command again. |
| 36 | Explanation: An AIX (alternate index) data set specified non-Extended-Format
on the define, but the base cluster is an Extended-Format data set. Programmer Response: Check the definition of the base cluster to ensure that it is also non-Extended-Format. |
| 38 | Explanation: An AIX (alternate index) data set specified Extended-Format
on the define, but the base cluster is not an Extended-Format data
set. Programmer Response: Check the definition of the base cluster to ensure that it is also Extended-Format. The data class attribute is the source for requesting Extended-Format, so verify that the proper data class was used |
| 40 | Explanation: The related object is a variable relative-record data set. |
| 42 | Explanation: The
data set type in the RELATE parameter for a DEFINE ALTERNATEINDEX
command is an extended addressability ESDS. Programmer Response: Change the type of the related data set to a non-extended addressability ESDS. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: An unexpired
purge date exists. An attempt to delete an entry failed because its
expiration date has not been reached, and the DELETE command did not
specify the PURGE option. Programmer Response: Specify the PURGE option if desired. Run the DELETE command again. |
| 2 | Explanation: There are conflicting
date formats. An attempt to retrieve a date in the new format (YYYYDDD)
failed because the request used the old format (YYDD) by passing the
old format field dictionary name DSETEXDT or DSETCRDT. The date cannot
be passed correctly in the old format. Programmer Response: Submit the job again using the new format field dictionary name DSCRDT2 (creation date) or DSEXDT2 (expiration date). |
| 4 | Explanation: An unexpired
new format purge date exists. An attempt to delete an entry failed
because its expiration date has not been reached, and the DELETE command
did not specify the PURGE option. This expiration date is stored in
the new format (YYYYDDD) and it is beyond the year 1999. Programmer Response: Specify the PURGE option if desired. Run the DELETE command again. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: No related PATHENTRY
name was found on the path catalog record. Programmer Response: Ensure that the PATHENTRY name is correct. If it is, refer to access method services, DIAGNOSE command, to obtain additional information. |
| 2 | Explanation: An internal logic
error occurred. Programmer Response: Contact the IBM Support Center. |
| 4 | Explanation: Something other
than a CLUSTER or alternate index type object specified the RECATALOG
parameter. Programmer Response: Ensure that the object being recataloged is a cluster or alternate index. |
| 6 | Explanation: Either the primary
VSAM volume record (VVR) points to another catalog, or the primary
VVR or non-VSAM volume record (NVR) for the object being recataloged
was not found on the first volume serial number specified. The primary
VVR or NVR contains the data set information needed to recatalog the
object. Possible causes
of this error are:
Programmer Response: If no VVR exists, then re-issue the DEFINE command, without the RECATALOG parameter, for the ICF catalog. If the VVR exists but points to a different catalog, specify the correct catalog and re-issue the DEFINE command with the RECATALOG parameter. If the original values for parameters NAME, INDEXED, LINEAR, NONINDEXED, NUMBERED, and VOLUMES were not specified, specify the original values and re-issue the DEFINE command with the RECATALOG parameter. |
| 8 | Explanation: The RECATALOG parameter is incorrect on the DEFINE command for an ICF catalog. |
| 10 | Explanation: The catalog associated
with this data set does not match the catalog name found in the VVR. Programmer Response: You can only recatalog pagespace, swapspace, or SYS1 data sets to a different catalog than the one specified in the VVR. If the data set you are recataloging is one of those types, or if you are getting this error in response to a REPRO MERGECAT command, contact the IBM support center. If your data sets is not one of those types, print the VVR to determine which catalog the data set should be associated with. |
| 12 | Explanation: The VVR for the data set being recataloged indicated it was for a LINEAR data set, but the DEFINE RECATALOG command did not specify the LINEAR keyword. |
| 14 | Explanation: The DEFINE RECATALOG command specified the LINEAR keyword, but the VVR for the data set did not indicate it was a LINEAR data set. |
| 16 | Explanation: NVR for the object being recataloged was not found on the volume serial numbers specified. |
| 18 | Explanation: Something other than the expected NVR was retrieved. |
| 20 | Explanation: A DEFINE NONVSAM
RECATALOG request was issued on a volume that does not have the UCBSMS
indicator on. Programmer Response: This could result from an IDCAMS DEFINE NONVSAM RECATALOG request or an IDCAMS REPRO request that would cause the DEFINE RECATALOG to be issued. A DEFINE NONVSAM RECATALOG request is valid only for SMS NONVSAM data sets. Therefore, the volume specified must have the UCBSMS indicator set to on. Check to see if the volume was removed from the active configuration or if the volume was set to non-SMS status. Correct the error and run the job again. |
| 22 | Explanation: The VVR/NVR catalog name does not match the name of the catalog currently oriented to. |
| 24 | Explanation: The DEFINE RECATALOG
command detected that a volume for a data component is missing from
the volume list. Programmer Response: Ensure that any missing volumes are supplied when issuing the DEFINE RECATALOG command. |
| 26 | Explanation: The DEFINE RECATALOG
command detected that the last volume for a data component is missing
from the volume list. Programmer Response: Ensure that any missing volumes are supplied when issuing the DEFINE RECATALOG command. |
| 28 | Explanation: The DEFINE RECATALOG
command detected that the last volume of a stripe for a data component
of a striped VSAM data set is missing from the volume list. Programmer Response: Ensure that any missing volumes are supplied when issuing the DEFINE RECATALOG command. |
| 30 | Explanation: The DEFINE RECATALOG
command detected that a volume for an index component is missing from
the volume list. Programmer Response: Ensure that any missing volumes are supplied when issuing the DEFINE RECATALOG command. |
| 32 | Explanation: The DEFINE RECATALOG
command detected that the last volume for an index component is missing
from the volume list. Programmer Response: Ensure that any missing volumes are supplied when issuing the DEFINE RECATALOG command. |
| 34 | Explanation: The DEFINE RECATALOG
command detected that the last volume of a stripe for an index component
of a striped VSAM data set is missing from the volume list. Programmer Response: Ensure that any missing volumes are supplied when issuing the DEFINE RECATALOG command. |
| 36 | Explanation: An indirect volume
serial was used in the DEFINE RECATALOG for a VSAM non-LDS data set. Programmer Response: Ensure that the data set is a VSAM linear data set and marked zFS. |
| 38 | Explanation: DEFINE RECATALOG
using an indirect VOLSER was attempted for a VSAM indexed data set. Programmer Response: Ensure that the data set is a VSAM linear data set and is marked zFS. |
| 40 | Explanation: DEFINE RECATALOG
using an indirect VOLSER entry was not marked zFS or was a non-LDS
data set. Programmer Response: Ensure that the data set is a VSAM linear data set and marked zFS. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: An attempt was
made to delete the Master Catalog. Programmer Response: Determine if the correct catalog is specified. If so, run the job again with a different master catalog. |
| 4 | Explanation: The system was
unable to determine if the catalog is empty. Programmer Response: Specify FORCE, RECOVERY, or run DIAGNOSE and recommended action. |
| 6 | Explanation: An incorrect
DELETE TRUENAME request was specified. The associated base object
exists. Programmer Response: User error. |
| 8 | Explanation: A pagespace record
was damaged. It could not be determined if pagespace was active. Programmer Response: Run DIAGNOSE and take the recommended action. |
| 10 | Explanation: The generation
data set was not found in the GDG. Programmer Response: Run LISTCAT to determine the generation data sets in the GDG. Run the delete job again with the correct generation/version number. |
| 12 | Explanation: A required FILE
parameter was not specified on the DELETE VVR command. Programmer Response: Specify FILE parameter. Run the job again. |
| 14 | Explanation: No DD was found
to match the supplied DD name on the DELETE VVR request. Programmer Response: Check FILE parameter. Run the job again with the correct DD name. |
| 16 | Explanation: DELETE VVR request
for a VVR with an associated catalog. Programmer Response: User error. |
| 18 | Explanation: The usercatalog
parameter is missing. Programmer Response: Specify the file parameter. Run the job again. |
| 20 | Explanation: DELETE NVR request
for a NVR with an associated catalog. Programmer Response: This is probably a user error. |
| 22 | Explanation: No DD was found
to match the DD name on the DELETE NVR request. Programmer Response: User error. Respecify the DDname in the FILE parameter. Run the job again. |
| 24 | Explanation: The request is
to delete an SMS data set only, but the data set is non-SMS managed. Programmer Response: This is probably a user error. |
| 26 | Explanation: A required FILE
parameter was not specified on the DELETE NVR command. Programmer Response: This is probably a user error. |
| 30 | Explanation: DELETE VVR resulted
in an attempt to delete a DSCB that has an associated VVR with a catalog
name other than the one specified. Nothing was deleted. Programmer Response: This is probably a user error. |
| 32 | Explanation: For DELETE VVR/NVR,
the VVR/NVR was not found, but a DSCB was found. The DSCB was deleted. Programmer Response: This is an informational message. No action is required. |
| 34 | Explanation: DELETE VVR resulted
in an attempt to delete a non-VSAM DSCB. Nothing was deleted. Programmer Response: User error. DELETE VVR cannot be used to delete non-VSAM data sets. |
| 36 | Explanation: DELETE VVR resulted
in an attempt to delete a DSCB whose name resolves to an associated
keyrange VVR. Nothing was deleted. Programmer Response: User error. Use DELETE CLUSTER. |
| 38 | Explanation: For DELETE VVR,
both the VVR and DSCB were not found. Nothing was deleted. Programmer Response: Informational message. Neither the VVR nor the DSCB were found. The object name may be misspelled. If so, run the job again with the correct object name specified. |
| 40 | Explanation: For DELETE VVR,
the DSCB was not found. Programmer Response: Informational message. The VVR was found, but the associated DSCB was not found. The VVR is deleted. |
| 42 | Explanation: An NVR was retrieved
during a DELETE VVR request. Programmer Response: User error. Specify DELETE NVR and run the job again. |
| 44 | Explanation: A VVR was retrieved
during a DELETE NVR request. Programmer Response: User error. Specify DELETE VVR and run the job again. |
| 46 | Explanation: DELETE VVR failed
to specify the system master catalog name in the catalog parameter. Programmer Response: User error. Rerun the failing DELETE VVR job specifying the system master catalog name in the catalog parameter. |
| 48 | Explanation: DELETE CLUSTER
failed because the data set is using RLS resources. Programmer Response: This data set must be deleted on a DFSMS/MVS 1.3 or higher system to ensure the RLS resources are freed. |
| 50 | Explanation: DELETE failed
because SMSVSAM Server was not available. Programmer Response: Retry the operation when the SMSVSAM Server is available. |
| 52 | Explanation: The SMSVSAM Server
encountered an internal error performing the delete operation. Diagnostic
data will be written to Logrec, and a system dump may have been taken. Programmer Response: Refer the problem to IBM programming support center. |
| 54 | Explanation: DELETE failed
because the data set is being renamed but it has not completed. Programmer Response: Rename the data set with the IDCAMS ALTER command and then delete it. |
| 56 | Explanation: A DELETE USERCATALOG
or EXPORT DISCONNECT command issued against a user catalog failed
because the catalog contains one or more user catalog connector extension
records, which are not allowed in a pre-z/OS V1R13 system. Programmer Response: In order to delete user catalog connector records, issue EXPORT DISCONNECT for the user catalog on a system at the z/OS® V1R13 level or higher. |
| Reason Code | Description |
|---|---|
| 4 | Explanation: The correct volume
was not mounted for OBTAIN. Programmer Response: Check the JCL and file parameters, and ensure that the required volume is mounted. |
| 8 | Explanation: OBTAIN did not
find requested format-1 DSCB on specified volume. Programmer Response: Ensure that the correct volume is mounted. |
| 12 | Explanation: OBTAIN encountered
an I/O error in the volume's VTOC. Programmer Response: Check for a possible hardware error. |
| x | Explanation: The reason code
is the OBTAIN return code. Programmer Response: Determine the meaning of the obtain return code. Correct the error. Run the job again. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: The key specified
for spanned record exceeds the control interval size. Programmer Response: Correct the erroneous parameter (KEYS or RECORDSIZE). Run the job again. |
| 4 | Explanation: The maximum logical
record size for spanned records exceeds the control area size. Programmer Response: Correct the erroneous parameter (KEYS or RECORDSIZE). Run the job again. |
| 6 | Explanation: The alternate
index key position plus the key length for the base cluster is larger
than the control interval size minus 10 for spanned records. Programmer Response: Correct the erroneous parameter (KEYS or RECORDSIZE). Run the job again. |
| 8 | Explanation: The alternate
index key position plus the key length for the base cluster is larger
than the record size. Programmer Response: Correct the erroneous parameter (KEYS or RECORDSIZE). Run the job again. |
| Reason Code | Description |
|---|---|
| x | Explanation: The reason code
is the same as returned by the DADSM RENAME function in the status
byte of the RENAME volume list. Programmer Response: Determine the meaning of the RENAME return code, as documented in the "Status Codes from RENAME" section in z/OS DFSMSdfp Diagnosis. Correct the error. Run the job again. |
| Reason Code | Description |
|---|---|
| 10 | Explanation: The data set
name is indicated as a NEWNAME in an ALTER NEWNAME request that has
not completed. Programmer Response: Determine if the ALTER NEWNAME request has completed. If so, run the request again to get the correct information. |
| Reason Code | Description |
|---|---|
| x | Explanation: The reason code
is the DADSM SCRATCH function status code. Programmer Response: Determine the meaning of the SCRATCH status code. See z/OS DFSMSdfp Diagnosis for these status codes and take the appropriate corrective action before rerunning the job that failed. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: At least one
user catalog connector extension record was found when locating the
association entries of a user catalog on a pre-V1R13 system. You can
only use user catalog extension records on a z/OS V1R13 or later system. The system might
not return all the association entries in the usercatalog. Programmer Response: Retry the operation on V1R13 or higher systems to retrieve all the association entries of a user catalog. |
| Reason Code | Description |
|---|---|
| 0 | Programmer Response: The message indicates that the caller's AMS release level or maintenance level is different from the CATALOG level that is being called. Ensure that IDCAMS and CATALOG are at the same level. |
| Reason Code | Description |
|---|---|
| 4 | Explanation: The data set
to which an ALTER RENAME command is directed is RACF indicated. However, there is no RACF profile. Programmer Response: Make the data set RACF-protected or remove the RACF indicator. |
| 8 | Explanation: An ALTER RENAME
command has been issued for a RACF-protected data set. This failed
because as a result of the new name, the data set cannot be defined
to the security subsystem. Programmer Response: Use a new name acceptable to the security subsystem. |
| Reason Code | Description |
|---|---|
| 4 | Explanation: An internal logic
error occurred. Programmer Response: Probable system error. Contact the IBM Support Center. However, if a user program is interfacing directly with catalog management, the FPL contains improper data. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: As a result of
an IMPORT or DEFINE command, VSAM has attempted to establish a RACF profile for a cluster/alternate
index, data, or index object. This failed because a profile with the
same name already exists. Programmer Response: Either:
|
| Reason Code | Description |
|---|---|
| 24 | Explanation: An incorrect
association was returned during upgrade retrieval. Programmer Response: An IDCAMS DIAGNOSE should be run against the catalog and any errors identified corrected. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: As the result
of a DEFINE, IMPORT, or IMPORTRA command, VSAM attempted to define
a RACF profile for the object.
The profile could not be established because the user does not have
sufficient authority for the specified data set characteristics. Programmer Response: Check the installation security subsystem guidelines for defining a data set in the security subsystem. Modify the data set characteristics accordingly. |
| 12 | Explanation: As a result of
a DEFINE, IMPORT or IMPORTRA command, VSAM attempted to define a RACF profile for the object. RACF was incapable of building
the profile. Programmer Response: RACF was inactive and could not process the profile build request. To activate RACF, contact the system security administrator. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: invalid field name passed. Programmer Response: Contact the IBM Support Center. |
| 2 | Explanation: The storage management
subsystem field in the BCS is inconsistent with that field in the
VVDS entries. Programmer Response: Contact the IBM Support Center. |
| 32 | Explanation: Invalid filter key was provided.
This return code may also indicate an invalid data set name was encountered
in the catalog being searched. Programmer Response: Correct filter key, run IDCAMS DIAGNOSE on the catalog being searched to determine if there are any entries in error. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: An incorrect
relative block address (RBA) return code was returned from VSAM record
management. Programmer Response: This is a system error indicating that the catalog may need to be restored. Use of the access method services list catalog (LISTCAT) or DIAGNOSE commands may help identify the incorrect entry. It may be necessary to contact the IBM Support Center. |
| 34 | Explanation: DASDCALC returns
either an incorrect physical block size or an incorrect index into
the physical block size table. Programmer Response: The possible cause of this error is a CI size that is not compatible with the physical device. Correct the CI size and rerun the job. |
| 36 | Explanation: VSAM record management
has returned an invalid CI error on an access to a catalog record.
This error generally occurs because an invalid CIDF or RDF is detected
within a catalog CI. One possible cause is damage as a result of
a hardware failure. An IEC331I message will be issued and the SFI
information will contain additional information about the VSAM error. Programmer Response: Run an access method services DIAGNOSE command, and EXAMINE DATATEST against the catalog. The catalog may need to be recovered. |
| Reason Code | Description |
|---|---|
| ACS reason code = catalog reason code + 1000 | Explanation: Catalog management
can only support ACS services reason codes from 1000 to 1255. The
ACS services return and reason codes are documented in the z/OS DFSMSdfp Diagnosis. Programmer Response: For the ACS reason code referenced in the appropriate SMS SUB-System Message Manual. Refer to the Storage Management Subsystem Reason Codes, Sub-Sections Subsystem Interface Reason Codes and ACS Service Reason Codes in the z/OS DFSMSdfp Diagnosis for a complete description of the reason codes. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: An integrity
check of the user catalog parameter list (CPL), the FPL, or the FVT,
failed. Programmer Response: Contact the IBM Support Center unless a user-written program is interfacing directly with catalog management. |
| 2 | Explanation: A storage validity
check failed on a user FPL or on the user work area referenced from
the CPL. Programmer Response: Contact the IBM Support Center unless a user-written program is interfacing directly with catalog management. |
| 6 | Explanation: A CPL field that
references the work area is zero. Programmer Response: Contact the IBM Support Center unless a user-written program is interfacing directly with catalog management. |
| Reason Code | Description |
|---|---|
| 4 | Explanation: Only the old name catalog entry remains to be deleted, but the VTOC still has the DSCB with the old name. |
| 6 | Explanation: Only the old name catalog entry remains to be deleted, but the VVDS still has the NVR with the old name. |
| 8 | Explanation: The DSCB has been renamed, but no DSCB with either the old name or the new name can be found. |
| 10 | Explanation: The data set DSCB cannot be located. |
| 12 | Explanation: The NVR has been renamed, but the NVR with the new name cannot be located. |
| 14 | Explanation: There should be an NVR with the old name, but that NVR cannot be located. |
| 16 | Explanation: The DSCB has been renamed without error, but the NVR cannot be renamed because there is already an NVR with that name. |
| 18 | Explanation: The data set name specified in NEWNAME is involved in another ALTER NEWNAME request that is not yet complete. |
| Reason Code | Description |
|---|---|
| x | Explanation: An expected field
value was not supplied or an internal logic error occurred. This
is probably a logic error in the caller of catalog management. Programmer Response: Contact the IBM Support Center. |
| 0 | Explanation: Expected component not found. |
| 10 | Explanation: A UCB address
passed to the Catalog Address Space was found to be invalid during
an attempt to capture the UCB in the Catalog Space. Programmer Response: Attempt to rerun the failing request. If it continues to fail, create an SVC dump by using the MODIFY CATALOG,DUMPON command and contact the IBM Support Center. |
| 20 | Explanation: There is no pointer
to the catalog work area in the catalog parameter list, and the DEFINE
function is unable to return the names generated for a component.
Programmer Response: Contact the IBM Support Center unless a user-written program is interfacing directly with catalog management. |
| 48 | Explanation: The AMDSB information
has not been found in the VVR, or VSAM CLOSE passed invalid AMDSB
data to update the VVR. In the latter case, message IEC251I will
be issued. not found. Programmer Response: Run the DIAGNOSE command to check for a damaged catalog record. Contact the IBM Support center if message IEC251I was issued. |
| 122 | Explanation: Define master catalog or user catalog with extended format information or attributes extension information is not valid. |
| 124 | Explanation: Backout while open specification not valid for non-VSAM data set. |
| 126 | Explanation: Backout while open specification not valid for ALTER of non-SMS data set. |
| 128 | Explanation: An internal logic
error has occurred. Programmer Response: Contact the IBM Support Center. |
| 130 | Explanation: An internal logic
error has occurred. Programmer Response: Contact the IBM Support Center. |
| 132 | Explanation: Record Level Sharing attributes not valid for non-VSAM data set. |
| 134 | Explanation: Record Level Sharing attributes not valid for non-SMS data set. |
| Reason Code | Description |
|---|---|
| x | Explanation: An internal logic
error has occurred. Programmer Response: Contact the IBM Support Center. |
| 20 | Explanation: The key length
is required and has not been provided. Programmer Response: Ensure that a valid key length is specified for the data set. |
| 22 | Explanation: A unique data
set needs a DD statement for a rename, or the DD statement is missing. Programmer Response: Supply a dname job control statement. |
| 32 | Explanation: An alias name
was not provided on a DEFINE command. Programmer Response: Correct the DEFINE command. Run the job again. |
| 34 | Explanation: GDG limit or
attribute data were not provided on a DEFINE command. Programmer Response: Correct the DEFINE command. Run the job again. |
| 40 | Explanation: A required DD
statement is missing for a mountable unit. The system is unable to
mount the volume required for DELETE NONVSAM SCRATCH processing. Programmer Response: Use file parameter on DELETE and allocate a mountable unit to the job through a DD statement. Specify DEFER mount. |
| 42 | Explanation: An error occurred
from IDA0192V while attempting to mount a volume required for DELETE
NONVSAM SCRATCH processing. Programmer Response: Ensure that the mountable unit was allocated for DELETE processing. |
| 46 | Explanation: No storage class information was passed for an SMS managed data set. |
| Reason Code | Description |
|---|---|
| x | Explanation: Volume status code from DADSM. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: The index component
was found for relative record data set or entry-sequenced data set.
This is a system error. Programmer Response: If the reason code indicates a system error, contact the IBM Support Center. Otherwise, follow the programmer response indicated by the reason code. |
| 4 | Explanation: The key range
is incorrect for catalog define, or the key ranges are not specified
in ascending sequence in the DEFINE of a VSAM key sequenced data set. Programmer Response: Correct the DEFINE command. |
| 6 | Explanation: Key ranges were
found on both data and cluster catalog FVT. This is a system error. Programmer Response: If the reason code indicates a system error, contact the IBM Support Center. Otherwise, follow the programmer response indicated by the reason code. |
| 8 | Explanation: The work area
is too small. This is a system error. Programmer Response: If the reason code indicates a system error, contact the IBM Support Center. Otherwise, follow the programmer response indicated by the reason code. |
| 10 | Explanation: Space parameters
were found on both cluster and data catalog FVT. This is a system
error. Programmer Response: If the reason code indicates a system error, contact the IBM Support Center. Otherwise, follow the programmer response indicated by the reason code. |
| 20 | Explanation: The key lengths
for data and index are not equal. This is a system error. Programmer Response: If the reason code indicates a system error, contact the IBM Support Center. Otherwise, follow the programmer response indicated by the reason code. |
| 28 | Explanation: There are an
unequal number of volume serial numbers and file sequence numbers
in list entries. Programmer Response: Correct the input. Run the job again. |
| 30 | Explanation: More device type
entries exist than volume serial numbers. Programmer Response: Correct the input. Run the job again. |
| 34 | Explanation: An incorrect
space request type on DEFINE was detected. This is a system error. Programmer Response: If the reason code indicates a system error, contact the IBM Support Center. Otherwise, follow the programmer response indicated by the reason code. |
| 44 | Explanation: A relative-record
data set has a maximum record length that is not equal to the average
record length. Programmer Response: Correct the input. Run the job again. |
| 60 | Explanation: The logical record
size for an ICF catalog has been exceeded. The DEFINE ALIAS has caused
the updated catalog record to exceed the catalog's logical record
size. Programmer Response: Redefine the catalog record size to increase the logical record size to a value up to the 32,400 byte maximum. Run the DEFINE of the alias again. If the catalog record size is already 32,400, no more aliases may be defined for this catalog. A new catalog will need to be created for subsequent aliases, or existing aliases will need to be deleted from the current catalog. |
| 62 | Explanation: The maximum average
logical record size is less than 4086 bytes for an ICF catalog define. Programmer Response: Increase the maximum average logical record size. Run the DEFINE command again. |
| 64 | Explanation: An incorrect
group code for field management was detected. Programmer Response: This is a system programming error. |
| 66 | Explanation: The component
key length exceeds the limit. Programmer Response: Run the DIAGNOSE command to check for a damaged catalog record. |
| 72 | Explanation: Duplicate volumes
exist in the volume list of a non-keyrange data set. Programmer Response: For a DEFINE, remove the duplicate volume from the volume list and rerun the DEFINE. For an ALTER ADDVOLUMES, a volume being added might already exist as a primary or candidate volume for the data set; therefore, remove the volume from the ADDVOLUMES list and rerun the ALTER. |
| 74 | Explanation: The define of
a VVDS had the INDEX option specified. A VVDS is an entry sequenced
data set. Programmer Response: Remove the INDEX option. Run the define operation again. |
| 78 | Explanation: The request to
field management was not valid. Programmer Response: Check the CPL for calling field management. |
| 80 | Explanation: The size of the
generation data set subrecord exceeds the maximum spanned record size
of the ICF catalog. Programmer Response: Do one of the following:
|
| 82 | Explanation: Key ranges are
not allowed on a DEFINE of an ICF catalog. Programmer Response: Remove the KEYRANGES parameter. Run the DEFINE command again. |
| 84 | Explanation: The REUSE parameter
was specified with UNIQUE or KEY ranges. Programmer Response: Remove one of the conflicting parameters. Run the DEFINE command again. |
| 90 | Explanation: More than one
volume serial number is specified for the DEFINE request of a non-VSAM
data set, and one of the volume serial numbers is an
indirect volser ****** or a symbolic volser &xxxxx. Programmer Response: If the indirect or the symbolic volser feature (a non-VSAM data set defined with a volser of ******) is wanted, remove the other volsers from the DEFINE request. |
| 92 | Explanation: A format 2 work
area is incorrect for this catalog request. Programmer Response: Run the job again with a format 1 work area. |
| 94 | Explanation: DEFINE NONVSAM no BCS for a non-SMS managed data set cannot be requested. |
| 96 | Explanation: DEFINE NONVSAM no NVR for a non-SMS managed data set cannot be requested. |
| 98 | Explanation: The new record length will exceed the maximum VVR or NVR size. |
| 100 | Explanation: The number of volumes passed exceeds the number of UCB addresses. |
| 102 | Explanation: The Volser in the UCB does not match the volser in the volume list. |
| 104 | Explanation: An incorrect number of device types were passed for the ALTER non-specific volume request. |
| 106 | Explanation: An incorrect number of volumes were passed for the ALTER non-specific volume request. |
| 110 | Explanation: Either
of the following problems occurred:
Programmer Response: Define the data set with a smaller space allocation request. |
| 112 | Explanation: An incorrect
high-allocated RBA was found during a define of a data component.
The high-allocated RBA was less than the high-used RBA. Programmer Response: Reduce the amount of space specified for the data component of the cluster. Enter the DEFINE command again. |
| 116 | Explanation: A request was
made to compress a data set that is not an Extended Format data set. Programmer Response: Contact the IBM Support Center. |
| 120 | Explanation: Compressible
request is allowed for KSDS data set only. Programmer Response: Change the job to define the data set as a non-compressible data set. |
| 122 | Explanation: Catalog G1000Vxx
will cause the GDG to exceed the limit of 10,999. Programmer Response: Clean up the GDG in error then catalog G1000Vxx. |
| 124 | Explanation: Invalid data
set type for extended addressability. Programmer Response: Clean up the GDG in error then catalog G1000Vxx. |
| Reason Code | Description |
|---|---|
| x | Explanation: Return code from OBTAIN. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: An incorrect
first character, non-alphabetic, was detected. The alternate index
or path name is incorrect. Programmer Response: Correct the entry name. |
| 6 | Explanation: The data and
index names are not allowed for a catalog. Programmer Response: Avoid the use of names at the INDEX and DATA level of DEFINE MASTERCATALOG and DEFINE USERCATALOG. |
| 8 | Explanation: A syntax error
was encountered in examining a GDG name. Programmer Response: Correct the name. Run the job again. |
| 10 | Explanation: A reserved high-level
qualifier name was specified on an ICF define operation. CATINDEX
is a reserved high-level qualifier. Programmer Response: Change the name to use a different high-level qualifier. Run the define operation again. |
| 12 | Explanation: The data name specified for an SMS VSAM data set does not orient to the same user catalog that the cluster did. |
| 14 | Explanation: The data set name to be
added to the catalog does not meet the syntax requirements for a valid
cataloged data set name. For information about valid cataloged data
set names, see z/OS DFSMS Using Data Sets. Programmer Response: Correct the data set name so that it meets the requirements for a valid cataloged data set name. |
| 16 | Explanation: The index name does not resolve to the same catalog as the cluster name did. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: An incorrect storage class name length was detected. |
| 4 | Explanation: An incorrect data class name length was detected. |
| 6 | Explanation: An incorrect management class name length was detected. |
| Reason Code | Description |
|---|---|
| 0 | Programmer Response: If the catalog and all of its entries are to be deleted specify the FORCE parameter on the access method services DELETE CATALOG command. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: A GETMAIN failure
occurred. There is insufficient virtual storage available. Programmer Response: Increase the region size available to the step. |
| 10 | Explanation: A GETMAIN failure
occurred. There is insufficient virtual storage available for the
catalog communication area. Programmer Response: Increase the region size available to the step. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: One of the following
has occurred:
Programmer Response: Specify a device type or device name that is acceptable to the system. |
| 4 | Explanation: An incorrect
device name was specified on a define of a non-VSAM entry. Programmer Response: Specify a device type or device name that is acceptable to the system. |
| Reason Code | Description |
|---|---|
| x | Explanation: The return code from a failed DADSM RENAME. |
| 2 | Explanation: A duplicate name
was detected on a volume during a define of a data set. Programmer Response: Select another data set name, scratch the original data set from the volume, or ensure that there are as many volumes as key ranges for the define of a unique key sequenced data set (KSDS). |
| Reason Code | Description |
|---|---|
| 0 | Programmer Response: Delete any unneeded data sets or data spaces from the volume to make additional DSCBs available, or re-create the volume with a larger VTOC. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: The open-for-output
indicator was found on in the catalog while a partial release request
was being processed. Partial release processing cannot occur if there
are other users opened to the data set. Programmer Response: Run an IDCAMS verify against the data set to reset the open-for-output indicator and re-run the partial release request. |
| 4 | Explanation: The data set is not an extended format VSAM cluster. Partial release processing is supported only for extended format VSAM clusters. |
| 6 | Explanation: The data set
name passed to a VSAM partial release request was not a VSAM cluster
data component. Programmer Response: Ensure the name being passed is the VSAM cluster data component and re-run the partial release request. |
| 8 | Explanation: A DADSM partial
release request failed. Programmer Response: Examine the job and system log for related messages explaining the DADSM failure. |
| 10 | Explanation: An attempt was made to perform partial release processing against a data set defined with guaranteed space. Guaranteed space data sets are not supported for partial release processing. |
| 12 | Explanation: An attempt to
release excess space has been made for this data set, but the data
set is not eligible for partial release processing. The data set is
a multi-volume data set that was created through space constraint
relief processing and the high use RBA for the data set is not in
the range of an extent on the last volume of the data set. System Action: The request to release the space is ignored. |
| 14 | Explanation: Rounding
for multi-cylinder unit (MCU) boundary prevented partial release of
space. System Action: The request to release the space is ignored. |
| 18 | Explanation: The primary volume RBAs
are out of order for this multivolume partial release request. Correct,
and rerun. Programmer Response: Run IDCAMS DEFINE RECATALOG with the volumes in RBA order. |
| Reason Code | Description |
|---|---|
| x | Explanation: Internal
logic error. Programmer Response: Contact the IBM Support center. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: A rename is not allowed for an open data set. The backout has been done successfully. |
| 2 | Explanation: The data set is currently open to another user. |
| 4 | Explanation: The data or index
component (or both) is in use, and the data set cannot be deleted. Programmer Response: Run the command again. To ensure proper completion, specify a disposition parameter of OLD, not SHR. |
| 6 | Explanation: The attempted
DELETE or ALTER of a PAGESPACE, or attempted DELETE CATALOG FORCE
that implicitly deletes a PAGESPACE, cannot be allowed. The pagespace
is currently in use on this or another system sharing the volume that
contains the pagespace. Programmer Response: If a PAGESPACE is to be deleted or altered, it must not be in use by any system that shares the volume on which it is located. |
| 8 | Explanation: The data set
is in use by another job; this reason code usually means that a Backup-While-Open
(BWO) dump of the data set is in progress. Programmer Response: Run the requested function again after verifying the data set is not currently being dumped. |
| 10 | Explanation: An attempt has
been made to alter one of the attributes LOG, LOGSTREAMID, or BWO
for a data set that is currently open. System Action: The request is terminated. Programmer Response: Reissue the ALTER request when the target data set is not open. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: Lock verification
failed. Programmer Response: An unauthorized caller attempted to access a locked catalog. To access a locked catalog, a user must have read authority to the profile IGG.CATLOCK of class type FACILITY. Obtain the correct authorization. Run the job again. |
| 2 | Explanation: Access was denied
for one of the following reasons:
Programmer Response: Either define the profile IGG.CATLOCK, activate RACF, or supply an MVS router exit. |
| 4 | Explanation: The caller was
not authorized for DEFINE LOCK. Programmer Response: To use the DEFINE LOCK command, a caller must have read authority to the profile IGG.CATLOCK of class type FACILITY. Obtain the correct authorization. Run the job again. |
| 6 | Explanation: The caller was
not authorized for ALTER LOCK. Programmer Response: A caller attempted to issue either the ALTER LOCK command for an unlocked catalog, or the ALTER UNLOCK command for a locked catalog for which the caller was unauthorized. To use the ALTER LOCK and ALTER UNLOCK commands, a caller must have read authority to the profile IGG.CATLOCK of class type FACILITY. Obtain the correct authorization. Run the job again. |
| Reason Code | Description |
|---|---|
| 6 | Explanation: The catalog is
temporarily unavailable. Programmer Response: Try the request again at a later time. If a COPY or IMPORT operation has failed, do a DELETE RECOVERY and import a backup copy of the catalog. As a volume error code: Catalog unavailable for the remainder of processing which establishes volumes as candidates for future extension. This occurs during define of VSAM data sets only when another error is encountered during candidate processing. This code appears as a volume error code for the volumes that are not processed due to the other error code which will appear in the access method services jobstream output. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: The function was ALTER BCS only. |
| 2 | Explanation: The function was DIRECTED CATALOG. |
| 4 | Explanation: The function was DEFINE NONVSAM with no BCS. |
| 6 | Explanation: The function was DEFINE NONVSAM with no NVR. |
| 8 | Explanation: The function was DELETE NVR with no BCS check. |
| 10 | Explanation: The function was DELETE NOSCRATCH. |
| 12 | Explanation: The function was DELETE GDG FORCE. |
| 14 | Explanation: The function was ALTER UNCONVERT from SMS managed VSAM data set back to non-SMS managed. |
| 16 | Explanation: The user is not
authorized to alter the storage class or management class of an SMS-managed
data set. Programmer Response: Insure that the user
has read access authority to |
| 18 |
Explanation: The user is
not authorized to perform a ATL define, alter, or delete request. Programmer Response: Insure that the user has read access authority to 'STGADMIN.IGG.LIBRARY'. |
| Reason Code | Description |
|---|---|
| 0 | Programmer Response: Reduce the maximum logical record length or define the data set as spanned. |
| Reason Code | Description |
|---|---|
| 8 | Explanation: MLA was unavailable
for the request. Programmer Response: Enter the F CATALOG, MLA(REFRESH) or F CATALOG, RESTART command to re-enable the MLA. |
| 10 | Explanation: MLA detected a damaged master catalog record. A snap dump was taken to aid in resolution of the problem, and MLA facility in-storage tables were invalidated. |
| 14 | Explanation: MLA detected a damaged master catalog record. A snap dump was taken to aid in resolution of the problem, and MLA facility in-storage tables were invalidated. |
| 18 | Explanation: MLA detected a damaged master catalog record. A snap dump was taken to aid in resolution of the problem, and MLA facility in-storage tables were invalidated. |
| 20 | Explanation: MLA detected a damaged master catalog record. A snap dump was taken to aid in resolution of the problem, and MLA facility in-storage tables were invalidated. |
| 28 | Explanation: An error occurred during a generic search of the alias table for the input data set name. |
| 30 | Explanation: MLA was unable to obtain sufficient memory to hold its in-storage tables. |
| 34 | Explanation: MLA was unable to obtain sufficient memory to rebuild its in-storage tables. |
| 40 | Explanation: The system number
of qualification was not between 1 and 4. The search order of the
multi-level alias facility is undefined. All requests requiring the
multi-level alias facility will fail until the situation is rectified. Programmer Response: Use the MODIFY CATALOG,ALIASLEVEL operator command to send a valid level of qualification. |
| 42 | Explanation: MLA detected a damaged master catalog record. A snap dump was taken to aid in resolution of the problem, and MLA facility in-storage tables were invalidated. |
| 44 | Explanation: MLA detected a damaged master catalog record. A snap dump was taken to aid in resolution of the problem, and MLA facility in-storage tables were invalidated. |
| 46 | Explanation: An error occurred during a generic search of the alias table for the input data set name. |
| 50 | Explanation: The MLA tables are incorrect. The generic request cannot be fulfilled. |
| Reason Code | Description |
|---|---|
| 0 | Programmer Response: Reduce the control interval size of the data component. |
RETURN CODE 198 Explanation: An attempt has been made to use an unsupported feature.
RETURN CODE 200 Explanation: The specified or defaulted control interval size of the index component is greater than the maximum block size of the index device.
| Reason Code | Description |
|---|---|
| 0 | Programmer Response: Reduce the control interval size of the index component or use a different device with a larger maximum block size. |
RETURN CODE 202 Explanation: Storage management subsystem call error.
| Reason Code | Description |
|---|---|
| 0 | Explanation: An error was
detected during a call to SMS. Programmer Response: Print the OBR record to get the appropriate error messages. |
| 2 | Explanation: An error was detected during a call to determine whether all volumes belong to the same storage group. |
| 4 | Explanation: An incorrect definition was passed to the SMS. |
| 6 | Explanation: Insufficient space was provided for that definition to the SMS subsystem. |
| 8 | Explanation: An attempt was
made to alter the expiration date of an SMS-managed data set that
was defined with a management class whose maximum number of retention
days was specified as zero. Programmer Response: Redefine the data set with a management class with no retention limit or with a specified retention value equal to or exceeding the date specified in the ALTER command. |
| Reason Code | Description |
|---|---|
| 0 | Programmer Response: Reduce the key length, change the key position, or increase the logical record length. |
| Reason Code | Description |
|---|---|
| 0 | Programmer Response: Increase the buffer size specified through the BUFFERSPACE parameter of the DEFINE command. |
| 4 | Programmer Response: Increase the buffer size specified through the BUFFERSPACE parameter of the ALTER command. |
| Reason Code | Description |
|---|---|
| x | Explanation: Return code from Subsystem call. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: The control interval
and the control area calculations are unsolvable with specified parameters. Programmer
Response: Determine which of the specifications may have caused
the problem. The following are the possible specifications:
|
| 4 | Explanation: Specified and
default values result in only one control interval per control area
for a key-sequenced data set. Programmer Response: Correct the input. Run the job again. |
| 6 | Explanation: Using the specified
or default values, the maximum index control interval size for the
device would be exceeded for nonunique objects. Programmer Response: Increase the data control interval size or decrease the data control area size. |
| 8 | Explanation: Using the specified
or default values, the maximum index control interval size for the
device would be exceeded for unique objects. Programmer Response: Increase the data control interval size or decrease the data control area size. |
| 10 | Explanation: The buffer space
is too small for a nonunique object. Programmer Response: Correct the buffer size. Run the job again. |
| 12 | Explanation: The specified and default value result in only one control interval per control area for a variable relative-record data set. |
| Reason Code | Description |
|---|---|
| x | Explanation: Return code from Subsystem call. |
| Reason Code | Description |
|---|---|
| ACS reason code = catalog reason code + decimal 256 | Explanation: Adding decimal
256 to the catalog reason code will give the correct ASC reason code.
The ACS services return and reason codes are documented in the z/OS DFSMSdfp Diagnosis
Programmer Response To ACS reason code add decimal 256 to obtain the correct error code for reference in the appropriate SMS SUB-System Message Manual. Refer to the Storage Management Subsystem Reason Codes, Sub-Sections Subsystem Interface Reason Codes and ACS Service Reason Codes in the z/OS DFSMSdfp Diagnosis & for a complete description of the reason codes. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: The maximum number
of volume extent (group occurrence) pointers have been processed. Programmer Response: Determine why the excessive values are being supplied. |
| 2 | Explanation: More than 255
volume extent (group occurrence) pointers exist in a record, or more
than 125 alternate indexes exist in the upgrade set. System Action: The additional values are not added to the entry. Programmer Response: Determine why the excessive values are being supplied. |
| Reason Code | Description |
|---|---|
| 4 | Explanation: To OPEN a catalog,
the caller must be running in key 0 - 7, must be in supervisor state,
or must be APF authorized. To do CLOSE or EOV processing for a catalog the caller must be running in key 0 - 7, must be in supervisor state, or must be APF authorized. To process the CONVERTV function, the caller must be APF authorized. Scheduler type locate (non-generic) is restricted. To issue LOCATE SVC, the caller must be running in key 0 - 7, must be in supervisor state, or must be APF authorized. Programmer Response: Respond to the particular error accordingly. If there is no fix for the problem, contact the IBM Support Center. |
| Reason Code | Description |
|---|---|
| x | An internal logic error has occurred. Programmer Response: Contact the IBM Support Center. |
| 2 | ECS workarea storage is not available. |
| 3 | Coupling Facility connection error. If received with message IEC377I, fields aaaa and bbbb contain the return and reason codes from IXLCONN. |
| 4 | An ECS request was made but the system is not ECS-active. |
| 9 | Coupling Facility disconnection error. If received with message IEC377I, fields aaaa and bbbb contain the return and reason codes from IXLDISC. |
| 13 | ECS activation was requested for a catalog with the NOECSHARING attribute. |
| 26 | Returned on a non-ECS system when an attempt is made to access a catalog that is ECS-active on another system. |
| 28 | Catalog is temporarily in use by a non-ECS system. |
| 29 | ECS-activation of a catalog is requested but the catalog does not have cross-system share options or is not on a shared volume. |
| 47 | A Coupling Facility error has occurred. Programmer Response: Consult the Coupling Facility messages that appear in the system log and correct the associated problem. Then reactivate ECS. |
| 48 | An attempt was made to add a catalog
to the Coupling Facility structure for Enhanced Catalog Sharing use,
but the structure is full. Programmer Response: Increase the size of the ECS structure definition in the CFRM policy. |
| 58 | An attempt was made to connect to the ECS structure but Catalog has detected that the system is running as a VM guest. ECS cannot be activated. |
| 65 | Connecting to the CF cache is not allowed at
this time until the structure is finished with the rebuild. Programmer Response: Wait for the rebuild to finish. If the CF cache is not automatically reconnected after the rebuild, issue F CATALOG,ECSHR(CONNECT) to connect. |
| Reason Code | Description |
|---|---|
| x | Explanation: The reason code
represents the catalog management return code encountered while performing
SMF processing. The catalog management return codes correspond to
the return codes listed for this message. Programmer Response: Examine the reason code returned. Run the job again after performing the required corrective measures. |
RETURN CODE 236 Explanation: An
error occurred while changing a catalog’s state across the sysplex
via the modify command, IDCAMS, or IGGQUIES interface. The following
reasons may be corrected by the installation. Codes not shown indicate
an internal system error.| Reason Code | Description |
|---|---|
| x | Explanation: An internal logic
error has occurred. Programmer Response: Contact the IBM Support Center. |
| 24 | Explanation: The request to change a catalog’s state failed. |
| 26 | Explanation: The request to change a catalog’s state timed out. |
| 28 | Explanation: Either the specified catalog cannot be found, or the catalog is not RLS-eligible to be RLSQUIESCE or RLSENABLE. |
| 30 | Explanation: The catalog
is still open somewhere in the sysplex. Programmer Response: Use D GRS,RES=(SYSVSAM,catname*) to determine which system or job still has the catalog open. |
| 32 | Explanation: The catalog
is either locked or suspended already. Programmer Response: Use F CATALOG,ALLOCATED or IDCAMS LISTCAT to determine the current state of the catalog. |
| Reason Code | Description |
|---|---|
| x |
Explanation: An internal
logic error has occurred. Programmer Response: Contact the IBM Support Center. |
| 0 | Programmer Response: Use the access method services IMPORT CONNECT command to put an entry for the user catalog into the master catalog. |
| 6 |
Explanation: SMSVSAM address
space is not available. Programmer Response: Issue D SMS,SMSVSAM to examine whether SMSVSAM is active. |
| Reason Code | Description |
|---|---|
| 0 | Explanation: An ALTER of expiration date was specified, but no DD statement was supplied. |
| 4 | Explanation: The DEVTYPE function
failed during DEFINE processing. Programmer Response: Provide the required parameter, ensure that the DD statement name is correctly spelled, or that the DD statement is present for the step. Also, ensure that the volumes can be allocated by dynamic allocation. If these are correct, contact the IBM Support Center. |
| 8 | Explanation: An incorrect
device type was encountered during DEFINE processing. Programmer Response: Provide the required parameter, ensure that the DD statement name is correctly spelled, or that the DD statement is present for the step. Also, ensure that the volumes can be allocated by dynamic allocation. If these are correct, contact the IBM Support Center. |
| 14 | Explanation: A delete of a
unique object was specified, but no DD statement was supplied. Programmer Response: Provide the required parameter, ensure that the DD statement name is correctly spelled, or that the DD statement is present for the step. Also, ensure that the volumes can be allocated by dynamic allocation. If these are correct, contact the IBM Support Center. |
| 16 | Explanation: A delete of a
non-VSAM object with the scratch option was specified, but no DD statement
was supplied. Programmer Response: Provide the required parameter, ensure that the DD statement name is correctly spelled, or that the DD statement is present for the step. Also, ensure that the volumes can be allocated by dynamic allocation. If these are correct, contact the IBM Support Center. |
| 18 | Explanation: A delete of a
VSAM object with the erase option was specified, but no DD statement
was supplied. Programmer Response: Provide the required parameter, ensure that the DD statement name is correctly spelled, or that the DD statement is present for the step. Also, ensure that the volumes can be allocated by dynamic allocation. If these are correct, contact the IBM Support Center. |
| 22 | Explanation: There was no
DDname match found in the TIOT. Programmer Response: Provide the required parameter, ensure that the DD statement name is correctly spelled, or that the DD statement is present for the step. Also, ensure that the volumes can be allocated by dynamic allocation. If these are correct, contact the IBM Support Center. |
| 34 | Explanation: The system was
unable to determine the DD statement name for a CRA. Programmer Response: Provide the required parameter, ensure that the DD statement name is correctly spelled, or that the DD statement is present for the step. Also, ensure that the volumes can be allocated by dynamic allocation. If these are correct, contact the IBM Support Center. |
| 36 | Explanation: Either a required
DD statement is missing or, if the user is dynamically allocating
the data set, the limit to the number of data sets that can be dynamically
allocated has been exceeded. Programmer Response: Provide the required parameter, ensure that the DD statement name is correctly spelled, or that the DD statement is present for the step. Also, ensure that the volumes can be allocated by dynamic allocation. Check the DYNAMNBR parameter in the user's LOGON procedure to determine if the limit on the number of data sets that can be dynamically allocated was exceeded. If these are correct, contact the IBM Support Center. |
| Reason Code | Description |
|---|---|
| x | Explanation: An internal error has occurred. System Action: An SVC dump may be produced for the error, depending on the reason code. Processing of the catalog request is terminated. Programmer Response: Determine if an SVC dump was created for this failure, and contact the IBM Support Center for assistance. |
| 26 | Explanation: An overlay in the Access
Control Block (ACB) or CAXWA for an ICFCATALOG has been detected.
A dump will be taken and the Catalog Address Space will be restarted
internally to invalidate the affected control blocks. Programmer Response: Please provide any dumps to IBM support. Prepare to re-IPL the system(s) that got the 246-26 dumps to rebuild the ACBs as soon as possible. |
| 28 | Explanation: A broken CAXWA chain has
been detected. A dump will be taken and a IEC366E WTO message will
be issued. An IPL is recommended at the earliest convenience to avoid
any fatal errors because of the broken CAXWA chain. Catalog address
space is not restarted. Programmer Response: Please provide any 246-28 dumps to IBM support to make sure the overlay has been corrected. |
| Reason Code | Description |
|---|---|
| 2 | Explanation: The opening of a catalog failed during catalog reorientation. |
| 4 | Explanation: The allocation of a catalog unit failed. |
Programmer response
See the programmer response for the specific return code and reason code. Inspect other messages concerning the DADSM subcomponent or open or close processing to aid in solving the problem. If necessary, contact the IBM Support Center.
Source
DFSMSdfp
Module
IGG0CLaa