A fullword field that contains the SMS reason code explaining the failure. The system returns a reason code in this field only when an error code beginning with X'97xx' is returned in the S99ERROR field of the request block.
IGD messages accompany the SMS reason code depending on the allocation message processing options in the S99EOPTS field of the request block. (See Processing options (S99EOPTS).) The SMS reason code also corresponds to an IGD system message that further describes the error. For example, if the reason code is X'4379' (decimal 17273), the IGD message that contains the decimal equivalent, IGD17273I, describes the error.
The system returns a reason code in S99ERSN when a failure occurs during SMS processing. For any reason code returned in S99ERSN that is not described in the following list and that does not convert to a recognizable IGD system message, search the decimal code under SMS reason codes in z/OS DFSMSdfp Diagnosis. If you still cannot locate the reason code, have the system programmer locate the logrec data set entry associated with the error and report the failure to the IBM® support center.
System Programmer Action: Examine message IGD300I and the symptom dump to determine why the abend occurred.
Application Programmer Action: If specific volumes are not required, remove the explicit volume specification and reissue the request. If the explicitly specified volumes are required, contact the system programmer for assistance.
System Programmer Action: Make sure that all of the volumes are SMS-managed and are defined to the same storage group. Also, make sure the volumes have the properties that this storage group requires; or modify the storage class routine to select a non-guaranteed space storage class. Then have the application programmer reissue the request.
Application Programmer Action: If the data set is supposed to be SMS-managed, get help from the system programmer to determine why a storage class was not derived for the data set.
System Programmer Action: Use the logrec data set to obtain information about the error that occurred. Refer to z/OS DFSMSdfp Diagnosis for an explanation of the reason code and return code.
System Programmer Action: Use the logrec data set and SYS1.DUMPnn to determine why the installation exit failed.
Application Programmer Action: Either obtain authorization to use the storage class or the management class or use a storage or management class that you are already authorized to use. Reissue the request.
System Programmer Action: Make sure the ACS routines will derive a data class with a DSNTYPE attribute that is supported with the current level of operating system.
Application Programmer Action: If a scratch volume is derived from an SMS tape library, specify a volume of SCRTCH. If the tape volume is private, either eject the volume from the SMS tape library and access it outside the library, or contact the system programmer so that the status of the volume can be changed from scratch to private using IDCAMS or ISMF, and access it within the library.
Application Programmer Action: Add the PATH keyword, or remove the DSNTYPE of PIPE.
Application Programmer Action: Process OPEN/MVS requests only on systems that have OPEN/MVS installed.
Application Programmer Action: No action is required.
System Programmer Action: Locate the logrec data set entry for this error and determine the return code and the reason code for the catalog locate error under message IDC3009I.
System Programmer Action: Make sure all referenced ICF catalogs are connected to the system master catalog.
Application Programmer Action: If the volume serial numbers are specified incorrectly, then correct the specification. If the numbers are correct, then contact the tape librarian to ensure that all the tape volumes reside in the same library. When one of the two actions has been taken, reissue the request.
Application Programmer Action: If the volume serial numbers are specified incorrectly, then correct the specification. If the numbers are correct, then contact the tape librarian to eject the tape volumes from the system-managed tape library and access them on non-system managed tape drives.
Application Programmer Action: No action is required.
Application Programmer Action: Ensure that the data set name was specified correctly, and that the data set is cataloged in the appropriate catalog. Contact the system programmer to check if the alias entries point to the catalog. Reissue the request.
Application Programmer Action: Submit a batch job to locate the z/OS UNIX file to determine the return and reason codes returned in the corresponding IGD04900I message.
Application Programmer Action: Add a path name to the requested allocation.
Application Programmer Action: Specify volumes that are within a single storage group, or remove volume specification and allow SMS to select volumes. Reissue the request.
Application Programmer Action: Specify volumes that are defined to SMS and are within a single storage group, or remove volume specification and allow SMS to select volumes. Reissue the request.
Application Programmer Action: Specify volumes that are defined to SMS and within a single storage group, or remove volume specification and allow SMS to select volumes. Reissue the request.
System Programmer Action: Submit a batch job to roll the generation data set into the generation data group, and use the return and reason codes from any corresponding IGD messages when contacting the IBM support center to determine the cause of the catalog failure.
Application Programmer Action: Contact the system programmer to make the necessary modifications. Then delete the data set after the modifications have been completed.
System Programmer Action: Either modify the configuration to include the volume, or make sure the volume is online.
Application Programmer Action: Add a path name for the requested allocation.
Application Programmer Action: Submit a batch job to delete the z/OS UNIX file to determine the return and reason codes returned in the corresponding IGD07901I message.
Application Programmer Action: Correct the disposition for the z/OS UNIX file.
Application Programmer Action: Change or remove the RECORG value or RECFM keyword on the dynamic allocation request; then reissue the request.
Application Programmer Action: Correct the RECORG or DSNTYPE value on the dynamic allocation request; then reissue the request.
Application Programmer Action: Change the disposition of the referencing data set to OLD, MOD, or NEW. If the disposition was set correctly, contact the system programmer.
System Programmer Action: Locate the correct logrec data set entry for the error and report the failure to the IBM support center.
Application Programmer Action: Change the disposition of the referenced data set to OLD, MOD, or NEW. If the disposition was set correctly, contact the system programmer.
System Programmer Action: Locate the correct logrec data set entry for the error and report the failure to the IBM support center.
Application Programmer Action: Do not attempt to reference an SMS-managed data set from a non-SMS-managed data set.
Application Programmer Action: Correct the specified data set name. If data set name is valid, catalog the data set before attempting to reference it. Reissue the request.
Application Programmer Action: Correct the specified data set name. If data set name is valid, catalog the data set before using it to reference an SMS-managed data set. Reissue the request.
Application Programmer Action: Reference a data set that is in a valid storage class, and reissue the request, or contact the system programmer to have the same storage class assigned to the referencing data set as the referenced data set.
System Programmer Action: Contact your storage administrator, and supply the reason code.
Application Programmer Action: Correct the VOL=REF so that the data set referenced is not a GDS base, or remove the VOL=REF.
Application Programmer Action: Use a different data set name, and reissue the request. Contact the system programmer to resolve the duplicate data set names on the volume.
System Programmer Action: Reorganize the VTOC or VTOC index on the indicated volume.
System Programmer Action: Use the record in the logrec data set, the return code, and the diagnostic information to determine the error. Use z/OS DFSMSdfp Diagnosis to determine the meaning of the DADSM historic return code and the diagnostic information.
Application Programmer Action: Reduce the average block length specified, and reissue the request.
Application Programmer Action: If the data set name was incorrectly specified, correct the name and reissue the request. Otherwise, contact the system programmer.
System Programmer Action: Use z/OS DFSMSdfp Diagnosis to determine the meaning of the DADSM historic return code and the DADSM diagnostic information from the corresponding logrec data set entry. If the return code and the diagnostic information indicate that the user is unauthorized to create the data set, then alter the user's RACF profile to grant authorization. Otherwise, remove the automatic data set protection characteristic from the user's profile.
Application Programmer Action: Specify a non-zero value in tracks or cylinders for space, or specify a valid data class with space, and reissue the request.
Application Programmer Action: Either reduce the directory space or increase the primary space, and reissue the request. If there is little or no space available to allocate the data set, contact the system programmer.
System Programmer Action: If volumes are fragmented, run DEFRAG or run DFSMShsm space management to create space for new data sets. If space is not available to be freed, add volumes to the storage group, or add an overflow storage group to the list of storage groups selected.
System Programmer Action: Determine the reason for the rejection. Modification of the installation exit may be required.
System Programmer Action: Determine the reason for the rejection. Modification of the installation exit may be required.
Application Programmer Action: Specify a value for space, or specify a data class with non-zero space information, and reissue the request.
Application Programmer Action: Decrease the primary space to less than 65535 tracks and reissue the request.
Application Programmer Action: If the data set is not SMS managed, correct the volume specification and reissue the request. If it is a cataloged data set, and the catalog indicates that the data set resides on the volume, contact the system programmer.
System Programmer Action: Locate the logrec data set entry associated with the error to verify that the volume list passed to DADSM is correct.
Application Programmer Action: Either delete the existing data set, or change the new name to a name other than the indicated data set.
Application Programmer Action: You can delete the data set by specifying the PURGE option on IEHPROGM SCRATCH or IDCAMS DELETE.
System Programmer Action: Locate the logrec data set entry associated with the error to determine the DADSM historic return code and the DADSM diagnostic information. If the error cannot be corrected, contact the IBM support center.
Application Programmer Action: Retry the request later.
Application Programmer Action: If the user has access to the data set, contact the system programmer for assistance.
System Programmer Action: Locate the logrec data set entry associated with the error and contact the IBM support center.
Application Programmer Action: No action required.
System Programmer Action: If the data set was intended to be an extended format data set, the volumes in the storage group may not support extended format allocations.
System Programmer Action: Determine why the extended sequential format requirement could not be met and ensure the storage groups and their volumes have the correct requirements for allocating an extended sequential format data set. Locate the logrec data set entry to determine if there are any other messages associated with this error.
System Programmer Action: If this is acceptable, ignore the reason code. If not, determine why the extended sequential format requirement could not be met and ensure the storage groups and their volumes have the correct requirements for allocating an extended sequential format data set.
Application Programmer Action: Correct the volume list for the data set or remove the volume list and let the system select the volumes. Reissue the request.
Application Programmer Action: Ensure the data set to be allocated is physical sequential, and reissue the request.
Application Programmer Action: Ensure the data set to be allocated will be an SMS-managed data set, and reissue the request.
Application Programmer Action: Determine why the data set was not allocated as a VSAM extended format data set, and make the changes necessary to reissue the request. If necessary, contact the system programmer for assistance.
Application Programmer Action: Examine the return code and reason code in the accompanying message IGD17100I, as described in SMS reason code (S99ERSN).
Application Programmer Action: Allocate the data set using a different name and reissue the request.
Application Programmer Action: Examine the return code and reason code in accompanying message IGD17102I in z/OS MVS System Messages, Vol 8 (IEF-IGD).
Application Programmer Action: Correct the data set name in the VOL=REF reference, and reissue the request.
Application Programmer Action: If the new expiration date is unacceptable, contact the system programmer to take a corrective action, if any.
Application Programmer Action: Specify a valid data set name of a non-VSAM data set or a VSAM cluster name on the LIKE parameter, and reissue the request.
Application Programmer Action: If the data set should not be compressed, contact the system programmer for assistance.
System Programmer Action: Determine if compression services are available. If they are, locate the logrec data set entry associated with the error and contact the IBM support center. Otherwise, bring up compression services.
System Programmer Action: Determine if the data set characteristics met the criteria for compression. If so, locate the logrec data set entry associated with the error and contact the IBM support center. Otherwise, have the application programmer change the characteristics for the data set to ensure it will be eligible for compression.
Application Programmer Action: If possible, change the characteristics for the data set to ensure it will be eligible for compression, and reissue the request.
Application Programmer Action: The multi-volume temporary data set will be allocated as a non-extended format data set. The reason code can be ignored.
Application Programmer Action: If the construct is explicitly specified, make sure the specification is correct and reissue the request. Otherwise, contact the system programmer.
System Programmer Action: If the construct was supplied by the ACS routines, the ACS routines may have to be modified.
System Programmer Action: If a volume list was explicitly specified, then correct the volume list and reissue the request. If you did not explicitly specify the volume list, then locate the logrec data set entry associated with the error and contact the IBM support center.
Application Programmer Action: Specify volumes within the same storage group, or remove the volumes, and reissue the request. If necessary, contact the system programmer for assistance.
Application Programmer Action: Reissue the request, specifying less space than before. If this error message still occurs, contact the system programmer.
System Programmer Action: Determine which storage class and storage group were used for the request, and check the amount of available space on all volumes in the storage group. Then either force the selection of another storage class, or make more space available on the volumes within the selected storage group. If necessary, add more volumes to the selected storage group, add an overflow storage group to the selected storage group list, or move data off volumes using DFSMShsm.
System Programmer Action: Determine which storage class and storage group were used for the request, and check the amount of available space on all volumes in the storage group. Then either force the selection of another storage class, or make more space available on the volumes within the selected storage group. If necessary, add more volumes to the selected storage group, add an overflow storage group to the selected storage group list, or move data off volumes using DFSMShsm.
Application Programmer Action: Specify a valid space value or contact the system programmer to have the ACS routines assign a data class that has the space specified, and then reissue the request.
Application Programmer Action: Have the system programmer free more space on the specified volume, specify another volume, or remove the volume, and reissue the request.
Application Programmer Action: Specify another volume, remove the volume, or get a non-guaranteed space storage class derived for the data set, then reissue the request. If the problem persists, contact the system programmer.
System Programmer Action: Make sure the volume is online, enabled, and has adequate space for the data set; and make sure the status of the storage group containing the volume is either enabled, quiesced, or quiesced new. Then have the application programmer reissue the request.
Application Programmer Action: Reduce the number of volumes specified, and reissue the request.
Application Programmer Action: Ensure that no more than one volume is specified for a temporary VSAM data set when you reissue the request.
System Programmer Action: Correct the storage group ACS routines.
Application Programmer Action: Specify another volume or remove the volume and let the system select the volume when the request is resubmitted. If not successful, contact the system programmer for assistance.
System Programmer Action: Determine which storage group contains the volume, and which storage classes map to that storage group. Ensure that the volume is online to MVS and enabled to SMS. Then force the selection of one of those storage classes when the request is resubmitted.
System Programmer Action: Determine whether the volume or the storage group needs to be enabled; you can enable either by using the VARY SMS command. Then try to allocate the data set again.
Application Programmer Action: Make sure the allocation request specifies a volume serial number or a valid volume reference; then reissue the request.
Application Programmer Action: Reduce the volume count and reissue the request, or contact the system programmer for assistance.
System Programmer Action: Add volume to the storage group, or ensure the storage group selected has a sufficient number of available online volumes.
Otherwise, refer to the logrec data set entry associated with this error to determine if there are any messages that could describe this error further.
Application Programmer Action: Specify volumes that belong to an eligible storage group, and reissue the request.
Application Programmer Action: Make sure no more than 59 volumes are allocated to the data set when the request is resubmitted.
System Programmer Action: Locate the logrec data set entry associated with this error and determine if there are any other SMS messages that were logged with this failure.
System Programmer Action: If the volume is offline, then have the operator vary it online. If the volume is disabled, then either enable it, or deny the delete or rename request.
System Programmer Action: Use AMS ALTER to assign a storage class for the data set and attempt to delete it again.
Application Programmer Action: Define all volumes on which the data set resides to the same storage group, and reissue the delete or rename request. If the catalog entry is bad, execute IDCAMS ALTER to remove volumes for the non-SMS-managed volumes, and delete the data set.
Application Programmer Action: If the volume list is incorrect, correct the volume list for the data set and reissue the delete or rename request. Otherwise, contact the system programmer for the corrective action.
Application Programmer Action: Specify a smaller track or cylinder space quantity.
Application Programmer Action: Specify non-SMS-managed volumes and reissue the request.
System Programmer Action: Locate the logrec data set entry associated with this error and determine the cause of the error using the logged messages, and then take the appropriate actions to correct the error.
Application Programmer Action: This reason code is returned for informational purposes; therefore, no action is required.
Application Programmer Action: A retention period or expiration date need not be specified for temporary data sets.
System Programmer Action: If the volumes in the catalog are in error, correct them by changing the volumes to '*'.
System Programmer Action: Locate the logrec data set entry associated with the error to determine why the locate request failed. Then catalog the data set, and reissue the request.
System Programmer Action: Disable the VIO storage group to the selected system, or change the unit name in the VIO storage group to match a unit defined to the system.
Application Programmer Action: Specify another data set in the LIKE reference, and reissue the request.
Application Programmer Action: Remove the LIKE reference and specify a data class that meets the required criteria. Then reissue the request.
Application Programmer Action: Specify a data set that resides on a direct access volume and reissue the request.
Application Programmer Action: Correct the reference or remove the LIKE parameter. Then reissue the request.
Application Programmer Action: Specify the directory blocks quantity by one of the specified means, and reissue the request.
Application Programmer Action: Specify a RECORG or have one assigned through the data class ACS routines. If this is not successful, contact the system programmer.
System Programmer Action: If the AMP=AMORG parameter is required but a RECORG cannot be provided at allocation, force this data set to be non-SMS-managed. This may require modification of ACS routines. Otherwise, provide the RECORG value by assigning a data class.
Application Programmer Action: Change the LIKE reference to a data set that has not been migrated or remove the LIKE reference and specify a data class that meets the required criteria. Reissue the request.
Application Programmer Action: Add the PATH keyword, or remove the DSNTYPE of PIPE. Then reissue the request.
Application Programmer Action: Add the PATH keyword. Then reissue the request.
Application Programmer Action: Set the DSNTYPE to PIPE, or remove the PATH keyword.
Application Programmer Action: If you explicitly specified the construct, make sure your specification is correct and reissue the request. Otherwise, if the construct was supplied by the ACS routines, contact the system programmer.
System Programmer Action: Change the ACS routines so that a valid construct is assigned.
Application Programmer Action: Change the request so that all volumes specified are in the same storage group or remove all the specified volumes and have the system select the volumes; then reissue the request.
Application Programmer Action: Reissue the request, specifying less space than before. If you still get this error message, contact the system programmer.
System Programmer Action: Determine which storage class and storage group were used for the request, and check the amount of available space on all volumes in the storage group. Then either force the selection of another storage class, or make more space available on the volumes within the selected storage group.
System Programmer Action: Determine the status of all storage groups and volumes used for this request. You may need to enable some storage groups or bring some volumes online to MVS and enabled to SMS.
System Programmer Action: If DADSM could not find enough space, put additional volumes online in one of the eligible storage groups, or run DFSMShsm space management cycle to provide more space on the volumes, and have the application programmer reissue the request. Otherwise, refer to the logrec data set entry associated with this error to determine if there are any messages that could describe this error further.
Application Programmer Action: No action is required.