IAM WTO Messages

DD='ddname' I/O ERROR CODE=X'decb iobecb csw cccchhhhrr'

Explanation: This message is provided by the IAM processor for Compatible format files, when a file access fails with an I/O error. The message contains the following diagnostic information: DECB- displays the two error bytes of the BDAM DECB(+1). Possible codes are:
8000- Block not found on track
4000- Block length was incorrect
0800- Media failure - Data or Equipment check
0400- Physical End of File marker
0200- Unidentified error
0010- Requested block not within file extents
IOBECB- displays the first four bytes of the IOB.
CSW- displays the channel status word.
cccchhhhrr- displays the cylinder, head and record head number the error was detected on. The head and record number may not be accurate. IBM's message IEA000I/IOS000I, if present, contains the real track address.

Return Codes: A Return Code of 12, X'0C', and a reason code of X'04' for a read I/O error, or X'10' for an output I/O error, is stored in the RPL. The SYNAD exit will be invoked, if so specified by the program.

System Action: If an IBM IEA000I/IOS000I message appears on the JCL LOG, a hardware error has occurred. The IBM message gives the sense information (like data check, equipment check). Examine the error information provided in the IBM message to determine the cause of the error. The format of this information is documented in the IBM data management SRL for the operating system in use. The file in question is unreadable in its present state and must be reestablished. This may be the result of a hardware error and if possible the new file should be allocated to a different physical location or volume.

For other I/O errors, those not accompanied by a hardware failure error message, determine the cause of the error. It is recommended that an IAMRECVR DIAGNOSE function be executed on the problem file, to see if there are any problems with the file integrity. Some common reasons for these types of I/O errors include:

—File has been improperly moved or restored to a device type different than it was originally loaded on. Frequently, this will fail with block not found I/O error, with a DECB error code of x'8000'.

—Multi-volume file has been improperly moved, or improperly cataloged. Frequently, this will result in an I/O error of block not within extent, DECB error code of x'0010'.

—Storage overlay of IAM I/O control blocks. When this type of error occurs, most jobs and application programs do successfully process the IAM file, as does IAMRECVR. The failure is typically limited to one or a few jobs. A SYSUDUMP will be needed to determine the cause of this type of error.

The utility IAMRECVR may be used to recover a file that is no longer usable due to I/O or logical error conditions. This utility can be used to off load records from those portions of the file that have not been physically damaged. The user program should make a decision on the action to take when this occurs, for example, to continue processing without this file or to terminate processing until this file is made available. The appropriate action will depend entirely on the application and the user program's evaluation of the diagnostic information that is returned. If further assistance is needed, Contact BMC. 

REPLY RETRY WAIT OR CANCEL FOR ENQ WAIT ON 'dsname'

Explanation: The IAM file is not available to this job because some other job is currently accessing the file. This WTOR will only be issued when the IAM Global Option VSAMTWO=YES is specified, and is only applicable to Compatible Format files. A load process is always protected against concurrent access (read or update) or from another load. The Share Options specified when the file was defined determine which types of access can concurrently share the file.

System Action: The operator reply determines the course of action IAM will take. The following responses are allowed:
RETRY: IAM retries the ENQUEUE for the data set. If the file is still unavailable, the message will be re-issued.
WAIT: IAM waits for the data set to become available. Caution: The job could time out.
CANCEL: IAM fails the OPEN request with a return code indicating the file is not currently available for processing. The ACBERFLG field will be set to x'A8'.

DD='ddname' FILE FULL DUE TO INSUFFICIENT CORE

Explanation: This message is displayed by IAM when it finds an insert has failed because of insufficient storage to expand the overflow index. The record that was to be added was not placed in the file. Space may still be available at other locations within the file. Consequently, subsequent inserts may or may not fail depending on where in the file they are placed. Additionally, changes in the storage available within a region may allow a subsequent GETMAIN to succeed.

This message is displayed a maximum of 10 times per execution.

Return Codes: A return code of eight (8) and a reason code of 28 (x'1C') is stored in the feedback field of the RPL. This error code indicates a VSAM file full logical error. The logical error exit, LERAD, will be invoked, if so specified in the program.

System Action: This message indicates that there is an insufficient above the line storage region available for IAM to expand the overflow index size. Reorganizing the file may help to reduce the storage required. For Compatible format files, the definition of the file's OVERFLOW parameters as well as the OCOREO% and OCOREX% parameters should be reviewed. Increasing the OCOREO% value to acquire a larger overflow index area when the file is Opened may correct the problem. The job step region size or, for CICS users, the MVS IEFUSI exit, may also need adjustment so more storage will be available for use by this particular task.

DD='ddname' OPEN ERROR - DATA SET IN USE BY JOB jobn

Explanation: IAM was unable to open the specified file because it was already opened by another job. For Enhanced Format files, if IAM is able to determine which JOB or user has the file, it will be identified in the message.

Return Codes: A reason code of 168(x'A8') is stored in the ACB error flags field (ACBERFLG) and the OPEN is failed with a return code of 8.

System Action: Rerun the job when the indicated job has terminated or closed the IAM file that was in use.

DD='ddname' OPEN ERROR - MORE THAN 2 OPENS FOR UPDATE IN TASK

Explanation: This message is displayed by IAM, for Compatible format files only, when it finds a task has issued multiple Opens for update against the same data set.

Return Codes: A reason code of x'F8' is stored in the ACB error flags and the OPEN is failed with a return code of 8.

System Action: Convert the file to an Enhanced Format file, which supports multiple ACB's within the same address space. Or, change the program to make sure that the same file is never opened for update more than once within the processing task without first closing it.

DD='ddname' I/O ERROR CODE=X'decb iobecb csw cccchhhhrr'

Explanation: This message is displayed for Compatible Format file when a file OPEN fails with an I/O error. The format is the same as the IAMW01 message, please refer to that message for an explanation of the error codes. 

Return Codes: The ACB error flag is set to a value of x'B8', and the open is failed with a return code of 8.

System Action: Refer to message IAMW01 for potential causes and corrective action.

DD='ddname' SHORT ON STORAGE IN REGION, REQ:

Explanation: This message is displayed by IAM when a file OPEN fails because storage is not available for data buffers, the index or control information. Typically this message is issued due to insufficient storage above the 16 megabyte line (31-bit addressable storage), although it can also be issued for shortage of storage below the 16 megabyte line. Below the line storage may have become depleted due to insufficient region specified for above-the-line storage. The amount of storage requested in kilobytes is provided in the message.

The message can also occur if there was insufficient storage available in the Index Space when a z/OS data space is being used, in which case REGION is replaced by DSPACE, or from 64-bit virtual in which case 64BIT is indicated in place of REGION.

Return Codes: Reason code of x'88' is stored in the ACB error flags, and the open is failed with a return code of 8.

System Action: This message can occur for any number of reasons, and be corrected in various ways depending on the base cause of the problem. Frequently the problem is that the number of records in Independent or Extended Overflow result has significantly increased, causing a high demand for virtual storage for the index to the Overflow area. That problem can most easily be resolved by reorganizing the file. Please refer to the IAM-Storage-Usage on Storage Tuning for complete information on IAM's storage usage, and how that usage can be controlled.

DD='ddname' OPEN ERROR - FILE ALLOCATED BUT NOT LOADED

Explanation: This message is displayed by IAM when a task has issued an OPEN against an IAM file but the data set (referenced by 'ddname') for input or update processing, but the file had never been loaded as an IAM file, or an attempted load failed.

Return Codes: Reason code of x'A0' is stored in the ACB error flags, and the open request is failed with a return code of 8.

System Action: The file must be successfully loaded with data before it can be used for input or update processing.

DD='ddname ' OPEN ERROR - NOT AN IAM/VSAM FILE OR CREATE FAILED

Explanation: This message is displayed by IAM when a task has issued a VSAM OPEN for the data set (referenced by 'ddname') but the file did not contain a valid IAM file descriptor block. The data set may be the result of a load that failed, may have a misspelled data set name, or perhaps the file was damaged.

Return Codes: Reason code of x'BC' is stored in the ACB error flags, and the Open is failed with a return code of 8.

System Action: First, determine if the file being opened is supposed to be an IAM or a VSAM file. If it is supposed to be an IAM file, review the output from the job which created the file for errors.

DD='ddname' DYNCORE DISABLED DUE TO INSUFFICIENT STORAGE

Explanation: This message is displayed by IAM when a user requested storage for IAM's Dynamic Table option and the virtual storage is not available. Processing continues as if the request for Dynamic Tabling had not been requested.

Return Codes: No error codes or return codes are set.

System Action: The user should increase the region size or decrease the value requested for DYNCORE.

DD='ddname' DATA COMPRESS ERROR xxxxxxxx xxxxxxxxxxxxxx xxxxxxxxxxxxxxExplanation: During a file access of a data compressed IAM file, IAM decompression failed. The first four bytes are the internal RDW, the remaining data is the key.

Return Codes: A logical error code of x'2C' is set in the RPL. If present and active, the program's logical error exit (LERAD) is invoked, otherwise the request is failed with a return code of 8. If the user has placed a //IAMDEBUG DD DUMMY DD card in the JCL, then the task is abended with an abend code of U0185.

System Action: Run an IAMRECVR DIAGNOSE function to validate that the file is still valid. If the DIAGNOSE did not find any errors, then the cause is most likely a storage overlay. If the application did not produce a dump, rerun the job with a //IAMDEBUG DD DUMMY DD card to get a dump. If errors were found by DIAGNOSE, then a file recovery is necessary, either with IAMRECVR or other procedures that have been established. Contact BMC for assistance.

DD='ddname' FILE FULL, REORGANIZATION REQUIRED

Explanation: 

IAM

  was unable to add a record into a file, or unable to accept a larger size updated record. For compatible format files, the Independent Overflow area has been filled. For Enhanced format files, 

IAM

 was not able to obtain additional DASD space to expand the size of the file. A message indicating some type of X37 abend may 
precede this message.Return Codes: A reason code of 28(x'1C') is stored in the RPL error flags field (RPLERRCD) and the PUT is failed with a return code of 8. This VSAM logical error code signifies a file full error condition. If the application has provided a logical error exit (LERAD), the exit will be invoked.

System Action: Reorganize the file. It may be necessary to increase the space allocation for the file, and / or to move the file to a different volumes. For Enhanced Format files, it may be possible to free up some DASD space that is allocated to other data sets, and retry the request without doing a file reorganization.

IAM MEDIA MANAGER EXTEND ERROR - RC=xxxxxxxx RSN=xxxxxxxx

Explanation: An IAM Linear Data set while being loaded and likely used for Pervasive Encryption purposes, tried to take another DASD extent after using all the space in the current DASD extents and was unsuccessful.

System Action: Check on the SMS Storage Class volumes and make sure there is sufficient space for an additional secondary space extent.

DD=’ddname’ REQUEST FAILED - IAM ADDRESS SPACE QUIESCING OR INACTIVE
DD=’ddname’ REQUEST FAILED - IAMRLS FILE CLOSED BY OPERATOR REQUEST

Explanation: IAM was unable to complete an I/O request for the indicated file that was being processed by an IAMRLS or IAMPLEX address space due to the condition indicated by the message.

Return Codes: For the first message text, the I/O request will receive a logical error code of x’B9’ decimal 185. For the second message test the I/O request will receive a logical error code of x’BD’ decimal 189.

System Action: The application should close the affected IAM file. When the IAMRLS or IAMPLEX region has been reactivated or when it is okay for the application to OPEN the file again, it may then do so.

DD='ddname' OPEN ERROR - IAM DOES NOT CURRENTLY SUPPORT LSR

Explanation: For Compatible Format files only, this message is displayed by IAM when a task has issued an open for a data set with the Local Shared Resources processing option (MACRF=LSR) specified in the ACB, and a UPAD exit active in the exit list (EXLIST) specified for the ACB. Typically, this will occur for a Compatible Format file opened by CICS, without indicating that the file is not to be in any LSR pool in the CICS FCT. The OPEN fails.

Return Codes: Reason code of x'E4' is stored in the ACB error flag field and the open is failed with a return code of 8.

System Action: Either convert the file to an IAM Enhanced Format file, which will support the LSR application, or if the error occurred under CICS, change the CICS FCT table to specify LSRPOOL=NONE.

DD='ddname' ADD FAILED - MORE THAN 1 ACB CONCURRENTLY UPDATING FILE.

Explanation: IAM does not support concurrent file update. This message will be displayed when IAM detects an inconsistency between an Overflow block, and the index entries for that block in virtual storage. Generally such inconsistencies should only occur if another job had updated the data set since it was last OPENed by the failing application. IAM expects proper procedures to be used to prevent concurrent update as it will eventually result in damage to the file. This message is displayed a maximum of 10 times per execution.

Return Codes: A return code of eight (8) and a reason code of x'1C' (file full) is stored in the feedback field of the RPL. The logical error exit (LERAD) will be invoked, if so specified in the program.

System Action: In a multi-processor environment IAM files must be protected, by a global enqueue facility or manual scheduling, from concurrent update by tasks running on different processors. Within a single processor multiple tasks will be prevented from concurrently opening a file for update by the proper use of SHAREOPTIONS. IAM defaults to a cross region SHAREOPTION 1, multiple read access users or one update user. The use of SHAREOPTIONS 3 and 4 disable IAM's enqueue protection for a file as does the IAMOVRID parameter UPDATENQ=NONE. Use these facilities with great care. Within a single task for Compatible Format files, use of multiple ACBs against an IAM file will defeat IAM's enqueue protection for that file. To preserve the integrity of your IAM files any application program that accesses an IAM Compatible Format file with multiple ACBs must be changed to ensure only one ACB is used to access the file for update or convert the file to the IAM Enhanced File format. (For further assistance contact BMC support).

DD='ddname' USER NOT AUTHORIZED FOR UPDATE

Explanation: For Enhanced Format files, IAM issued a RACROUTE to verify that the user had authority to access the data set for the desired mode and received a return code indicating that the user is not authorized for the requested function.

Return Codes: A reason code of x'98' is stored in the ACB error flags field, and the open request is failed with a return code of 8.

System Action: Correct the error and rerun the job. Error could be caused by an incorrect data set name on the DD card, or this is a legitimate error.

IAM MEDIA MANAGER CONNECT|DISCONNT ERROR- RC=xxxxxxxx RSN=xxxxxxxx

Explanation: An IAM Media Manager Connect or Disconnect call could not open or close the IAM Linear Data Set being Loaded. IAM Linear data sets are primarily used for Pervasive Encryption purposes.

System Action: Make sure the DD statement for the file being loaded points at a valid IAM non-loaded Linear Data Set.

DD='ddname' OPEN ERROR -- error description

Explanation: The file load process has detected an invalid, unsupported, or inconsistent parameter for the indicated file attribute. The particular attribute that is invalid is indicated in the error description text. The possibilities are:

• LRECL Specification - Must be at least as long as key offset (RKP) plus the key length, and no larger than 32,755.
• Key Length Specification - Must be greater than 1, and less than 250.
• Blocking Factor Specification - Must be between 1 and 15.
• Blocksize Specification - Must exceed the maximum record length by at least five bytes, and be at least 300 bytes.
• RKP Specification - Must be less than 4092 bytes.
• Independent Overflow Specification - For compatible format files, cannot be a value that will cause the Overflow area to exceed 64,000 blocks.
• Integrated Overflow Specification - Must be between 0 and 99.
• Prime Extension Specification - For Compatible Format files, cannot exceed 32,767.
• Delete Processing Request - Should not occur with the IAM/ VSAM Interface.
• Data Control Area (DCA) Validation - Should not occur with the IAM/ VSAM Interface.
• Block size Calculation - The IAM internal block size calculation resulted in a value that cannot be used on the device that contains the IAM file.
• IAM File cannot be a DFSMS Striped data set. – IAM files cannot have multiple stripes, and Compatible format files cannot be SMS Extended format.
• DSNTYPE Invalid for Compatible – Compatible format IAM files cannot use Large Format data sets.
• DSNTYPE=LARGE Requires ZOS 1.7 – Large Format data sets require a minimum operating system level of z/OS 1.7.
• ACBSTRNO > 1 – The program specified a string number greater than one on a file load, which is not allowed for problem state programs. A reason code of 160 (x’A0’) is stored in the ACB error flags field.
• Not licensed for RRDS support – May occur during an attempted load an RRDS file when the version of the IAM product being used has not been licensed for the optional RRDS feature.
• RRDS Initialization Failed – Should be accompanied by additional error message, such as an IAMW36. Please refer to other messages for additional details.
• LOAD ERROR -- EXCEEDED 255 EXTENTS - The write (or put) request is failed with a Logical Error code of x'1C', file full logical error, and the request will receive a return code of 8. If the error occurred during CLOSE, then the CLOSE will fail with a return code of 4, and the ACB error flags set to x'90'. The file is left marked in an unloaded state.

Return Codes: Unless otherwise noted above, a reason code of 192(X'C0') is stored in the ACB error flags field (ACBERFLG) and the open is failed with a return code of 8.

System Action: Correct the invalid specification, and rerun. This error may occur when using VIF if the IAM file was allocated through some means other than an IDCAMS DEFINE and the user failed to correctly provide file specifications through a CREATE Override Control Statement. Additionally, conflicts between the file itself and the user program's internal file definition must be resolved.

DD='ddname' REORG RECOMMENDED: > REQUESTED OVERFLOW nnn,nnn,nnn

Explanation: A file reorganization is recommended because the number of records in overflow exceeded the amount specified via the Overflow (O=) override when the file was defined or loaded. The current number of records in the overflow area is included in the message.

Return Codes: None.

System Action: Presumably, the override was provided to indicate when the file should be reorganized. IAM will continue to add records to extended overflow, provided that IAM is able to obtain sufficient DASD space to do so.

DD='ddname' REORG RECOMMENDED: OVERFLOW INDEX > nnn,nnn MEG

Explanation: A file reorganization is being recommended because the estimated amount of storage required for the overflow index has exceeded the value specified in the IAM Global Option for the IAMW22LIM operand, which defaults to 64 megabytes. The current estimated amount of storage in megabytes is provided in the message. The value is an estimate only, the actual amount used may be different.

Return Codes: None.

System Action: The performance on the indicated file may be adversely affected due to the size of the overflow area. In particular, it may take several minutes to open the file, and sequential processing may be detrimentally affected. It is therefore recommended that the file be reorganized at the earliest convenient time to prevent further performance deterioration. The file can be quickly reorganized with FDRREORG®, or if that product is not available, then use IDCAMS REPRO.

DD='ddname' OPEN ERROR – AN ABEND OCCURRED DURING OPEN

Explanation: While IAM was opening a file an ABEND occurred. The ABEND is identified by a preceding IAMW73 error message, which contains the PSW and registers. Open processing for this file is terminated.

Return Codes: The OPEN fails with a return code of 8 and a reason code of 188(X'BC') in the ACBERFLG field of the ACB being opened.

System Action: Contact BMC . Please have all of the available error messages available, along with any dumps to diagnose the problem.

DD=’ddname’ INVALID COMPRESSION DICTIONARY BLOCK: nnn,nnn,nnn

Explanation: IAM was attempting to open a data set with an internal customized hardware compression dictionary. IAM encountered an invalid or corrupted block that should have had a portion of the hardware compression dictionary. The invalid block number is displayed in the message.

Return Codes: The OPEN fails with a return code of 8 and a reason code of 188(X’BC’) in the ACBERFLG of the ACB being opened.

System Action: Attempt a data set recovery, by either using IAMRECVR, or restoring the data set from a backup. Before overwriting the corrupted data set, back it up and notify BMC of the error. Also run IAMRECVR with two print statements: a PRINT IDPINQ and a PRINT FBLK=nnnnn,MAXBLKS=1 where the FBLK value is the block identified by the IAMW25 message. Email that output to BMC technical support.

DD=’ddname’ EXTEND CVAF READ (or WRITE) FAILED R15=xx STATUS=ddd

Explanation: While IAM was expanding the size of a DFSMS Extended Format IAM data set, the attempt to update the LSTAR in the VTOC failed. Refer to DFSMSdfp Diagnosis Reference for information on the return code and status value.

Return Codes: If an IAMDEBUG DD DUMMY dd card is in the affected job step, then the job step will abend with a U0184, otherwise IAM will continue processing the data set.

System Action: Contact BMC with the error codes. If problem is repeatable, add in an IAMDEBUG DD DUMMY and a SYSABEND dd card to the job to get a dump at the time the error is detected.

DD=’ddname’ OPEN ERROR: error description

Explanation: While attempting to open an SMS Extended Format or a Sequential Large Format IAM data set, IAM encountered the error as described in the text of the message. This message will be followed by an IAMW06 message.

Return Codes: Reason code of x'80' is stored in the ACB error field and the open request is failed with a return code of 8.

System Action: If unable to correct the indicate problem, rerun the job with an //IAMDEBUG DD DUMMY card and an //SYSABEND DD SYSOUT=* card in the failing job step to produce a dump, and Contact BMC for assistance.

DD=’ddname’ INELIGIBLE FOR BACKUPCOMPRESSED, OPTION IGNORED’
VERIFY FAILED, CONTINUING DUE TO NOVERIFY OVERRIDE
IARV64 RC=xxxxxxxx REAS=xxxxxxxx OPEN CONTINUES
UNABLE TO OBTAIN 64 BIT STORAGE, CACHE64 IGNORED
RACROUTE RC4 NO SECURITY DECISION, OPEN CONTINUES
MMPCPGM RC=xxxxxxxx REAS=xxxxxxxx OPEN FAILED

Explanation: This is a warning message indicating that an error was detected during open processing and was resolved as indicated. Some of these messages are the result to appropriate conditions not being available for an IAM Global Option or Override specification to be used. The RACROUTE RC4 message comes out when the SAFRC4 IAM Global Option is enabled, and indicates that the RACF was not available, and no other security software handled the request.

System Action: IAM continues file open processing without use of the indicated function. For the RACROUTE RC4 message, if you are using ACF/2 for security, see the ACF Security topic in Activating the IAM VSAM Interface section of the IAM Space to make sure that it is properly set up for IAM.

DD=ddname CONNECT RC=xx FDBK=xxxxxxxx xxxxxxxx MM FAILED
DD=ddname DISCONN RC=xx FDBK=xxxxxxxx xxxxxxxx MM FAILED

Explanation: IAM encountered an error connecting to or disconnecting from Media Manager to process the IAM file. The return code and feedback codes are provided for diagnosis.

System Action: Contact technical support with the message and codes, and any additional messages that may have appeared. In most circumstances, further processing of the file can not be continued in the current job / program.

DD='ddname' OPEN ERROR -- FILE IN USE BY JOB jobname

Explanation: While attempting to load an IAM file, it was determined that the IAM file is currently in use by some other job or an attempt was made to simultaneously load multiple IAM files to the same data set. IAM attempts to determine the name of the job using the data set, and will display the first job found that has the data set open in this message. If the owning job is not found, then *UNKNOWN is displayed.

Return Codes: A reason code of 192(x'C0') is stored in the ACB error flags field (ACBERFLG) and the open request is failed with a return code of 8.

System Action: An IAM load must be executed without any other job accessing the file at the same time. Wait until the file is closed by the other users, then rerun the file load.

IAM TOKEN AREA LOC ERROR- RC=xxxxxxxx

Explanation: At the start of an IAM file load, the IAM Load program looks for a Token Area that IAM VIF Open routines have placed in storage. A likely cause of this problem is that the load job has a STEPLIB or JOBLIB with an IAM library at a different IAM level than what any of the IAM VIFs have been started with.

System Action: Restart the load job with a level of IAM that has been IAM VIF started. The level of IAM must be at least 9.4/00.

DD=ddname OPEN ERROR – JOURNALING INITLIZATION FAILED

Explanation: An error has occurred while attempting to open an IAM file that requested the use of the IAM  Journaling exit. IAM was unable to complete initialization for journal processing. This message will be preceded by IAMJxx messages indicating the reason for the failure.

Return Codes: A reason code of 188 (x’BC’) is stored in the ACB error flags field (ACBERFLG) and the open request is failed with a return code of 8.

System Action: Review the accompanying IAMJxx messages for the corrective action that is required.

IAM MEDIA MANAGER CONNECT CISZ nnnnn NE TO DEFINE BLKSZ nnnnn

Explanation: The IAM Linear file that is being loaded has a different CI Size than the Block Size requested when the File was Defined. Somehow the file was updated, most likely by non-IAM means in between the File Define and the File Load.

System Action: Redefine the IAM file with a valid IAM Linear File B= value (or let it default) and try the File Load again.

DD=ddname TCBTOKEN JSTCB FAILED, RC=xx
DSPSERVE CREATE FAILED, RC=xx REAS=xxxxxxxx
ALESERV ADD FAILED, RC=xx
EXCEEDED MAXIMUM OF 16 DATA SPACES
RRN BITMAP OVERFLOWED WORK FILE DATASPACE

Explanation: One of the above errors occurred while loading an IAM RRDS data set. The requester will fail with an error code indicating insufficient virtual storage.

Return Codes: For a PUT or WRITE I/O request, it will fail with a return code of 8, and a logical error code of 40(x’28’). If the error occurred during OPEN processing, the OPEN will fail with a return code of 8 and an error code in ACBERFLG of 192(x’C0’).

System Action: Contact BMC support for assistance.

DD=ddname I/O ERROR ecbx,cswxxxxx,ccw,rd,rbnxxxx,sense ]

Explanation: This message is displayed when an I/O error has occurred processing an Enhanced Format IAM file, or during a load of an IAM file. This message may also be accompanied by an IEA000I/IOS000I error message. The message contains the following information separated by commas:

ECB - displays the first 2 bytes of the ECB as posted. Possible values of the first byte include:

41 - I/O terminated with error. CSW and / or Sense bytes are useful.
42 - Block is not within DASD extents for data set.
47 – DFSMS Extended Format block-id mismatch
4E – Attempted write of a block of all hex zeros.

The second byte may contain additional status information relevant for z/HPF architecture channel programs.

CSW - contains the 4 bytes in hex of the status bytes from the CSW. Possible values of the first two bytes for CCW type of I/O are:

0C00 - Normal Status
0E40 - Unit Check and/or Wrong length record
0D40 - End of file

The type of channel program, either CCW (standard I/O) or TCW for z/HPF I/O
Indicates either RD for read I/O, or WR for write I/O

The relative block number if known, in hex

SENSE - contains the first two sense bytes from the IAM internal IOB, or if extended sense byte data is present will contain total of 32 bytes continued on the next line. Possible values include of the first 2 bytes are:
8000 - Command reject, the device or control unit did not recognize the command
4000 - Device requires operator Intervention
1000 - Equipment check
0800 - Data check
0040 - Invalid Track Format
0020 - End of cylinder
0008 - Block not found

For file loads, the job step will be abended with a U0233 abend code.

System Action: If an IBM IEA000I/IOS000I message appears on the JCL LOG, a hardware error has occurred. The IBM message gives the sense information (like, data check, equipment check). Examine the error information provided in the IBM message to determine the cause of the error. The format of this information is documented in the IBM data management SRL for the operating system in use. The file in question is unreadable in its present state and must be reestablished. This may be the result of a hardware error and if possible the new file should be allocated to a different physical location or volume.

For other I/O errors, those not accompanied by a hardware failure error message, determine the cause of the error. It is recommended that an IAMRECVR DIAGNOSE function be executed on the problem file, to see if there are any problems with the file integrity. Some common reasons for these types of I/O errors include:

—File has been improperly moved or restored to a device type different than it was originally loaded on. Frequently, this will fail with block not found I/O error, with a SENSE error code of x'0008'.

—Multi-volume file has been improperly moved, or improperly cataloged. Frequently, this will result in an I/O error of block not within extent, ECB error code of x'42'.

—Storage overlay of IAM I/O control blocks. When this type of error occurs, most jobs and application programs do successfully process the IAM file, as does IAMRECVR. The failure is typically limited to one or a few jobs. A SYSUDUMP will be needed to determine the cause of this type of error.

The utility IAMRECVR may be used to recover a file that is no longer usable due to I/O or logical error conditions. This utility can be used to off load records from those portions of the file that have not been physically damaged. The user program should make a decision on the action to take when this occurs, for example, to continue processing without this file or to terminate processing until this file is made available. The appropriate action will depend entirely on the application and the user program's evaluation of the diagnostic information that is returned. If further assistance is needed, contact BMC .

DD='ddname' DSPSERV CREATE FAILED, RC=xx REAS=nnnnnnnn
DD='ddname' IARV64 GETSTOR FAILED, RC=xx REAS=nnnnnnnn

Explanation: IAM attempted to create a data space or obtain 64-bit addressable storage for holding the index structure during the file load, however, the request was rejected by MVS for the indicated return code and reason code. This is an informational message only, IAM will attempt to continue processing, and utilize a dynamically allocated temporary work file on DASD. For information on the return code and reason code, review in the IBM MVS Authorized Assembler Services Reference Space, under the DSPSERV macro or the IARV64 macro depending on the format of the IAMW38 message.

Return Codes: No error codes are set for this situation.

System Action: Contact BMC support for assistance to resolve the problem if unable to do so after reviewing the return code and reason code provided. One of the common reasons for the DSPSERV error message is that, the installation exit has either disallowed the use of data spaces, or limited the size. If the size is limited, reduce the IAM Global Option value for DATASPACE, or set it to 0 to prevent the use of data spaces. A common reason for the IARV64 error message is that the MEMLIMIT for the job step is too small.

DD='ddname' ###### RECORDS ACCEPTED PRIOR TO ABEND

Explanation: IAM has determined that the task loading the specified file has abended, or hit some other type of error condition, after loading the indicated number of records. This information may be useful for determining how much to adjust the space parameters if some type of Sx37 abend has occurred. The number of records that were actually written to the file may be slightly less than indicated due to buffering. 

System Action: Correct the error condition as indicated by the abend, and rerun the job. Depending on the cause of the abend, the file may have to be deleted and redefined, for example, if a larger space requirement is necessary.

CONTROL STATEMENT BYPASSED -- 'error description'

Explanation: An error was encountered by the override processor, IAMOVRID, during the processing of user supplied Override Control statements. The error description will be from the following list:

• DDNAME NOT SPECIFIED -- The DDNAME operand was missing or misspelled. DDNAME is required to relate the override to a specific IAM file.
• MAXIMUM GLOBAL OVERRIDES EXCEEDED -- The in storage table which holds the Overrides is full. A maximum of 200 control statements may be specified.
• INSUFFICIENT STORAGE -- There was insufficient virtual storage for the IAM override processor to acquire for saving the internal format of the overrides.

System Action: Correct the Override statements as follows:

• Add a corrected DDNAME operand to the control statement and, if necessary, rerun the job.
• Reduce the number of global overrides to 200 control statements or less. If more Override statements are required, contact BMC technical support for a modification to IAMOVRID to expand the in-storage table.
• Increase the amount of region, particularly for above the line storage. The override processor needs 48K of storage for the override table. Additional storage will also be required for processing the data set being opened, so just an increase of 48K will most likely not be sufficient.

IAM MEDIA MANAGER FMTWR EX|PC ERROR - RC=xxxxxxxx RSN=xxxxxxxx IOA@=xxxxxxxx

Explanation: During an IAM Linear Data Set File Load a Media Manager Format Write operation returned with a non-zero return code and the File Load ended abnormally.

System Action: Make sure that no other address space improperly updated the same Data Set with DISP=SHR by mistake. If not, recreate the problem with a MSGID=IAMW45 SLIP trap set in order to get a dump. Then Contact BMC . Sample console command-
SLIP SET MSGID=IAMW45,ACTION=SVCD,ID=IA45,END

I/O ERROR MONITORING DSN - 'dsname' - IAM MONITOR TERMINATED

Explanation: An IAM monitor facility processor encountered an I/O error while writing monitor/trace data. Monitoring has been discontinued. Normal IAM processing continues.

System Action: If a Monitor report is needed, correct the cause of the I/O error and rerun the job.

IAM VTOC ACCESS FAILED COMP=xxxx CODE=xxxx CLUSTER=clustername

Explanation: During an IDCAMS DEFINE or RECATALOG of an IAM file, an attempt to access or update a VTOC failed. The completion code and return codes from CVAF are displayed in the message.

System Action: Refer to the IBM Space 'Common VTOC Access Facility Diagnosis Reference' for the meaning of the codes. Correct the problem and re-submit. If unable to correct the problem, contact BMC support for assistance.

IAMOVRID CONTROL STATEMENT ERROR, CLUSTER=dsname

Explanation: During an IDCAMS DEFINE of an IAM file, the IAM Override processor detected an error or invalid IAM override card.

Return Codes: The DEFINE is failed with a return code of 140 and a reason code of 36. These codes will appear on the IDC3009I message produced by IDCAMS. The DEFINE is failed on an override error to prevent IAM from defining a file with incorrect attributes.

System Action: Correct the error on the IAM Overrides, and rerun the data set. Review IAM-Overrides for proper IAM Override parameters.

IAM SHOWCAT INTERCEPT FAILED

Explanation: The IAM SHOWCAT intercept function within VIF failed.

Return Codes: The calling program will be abended with a U0283 abend code. This error would indicate that something has destroyed the IAM VSAM interface table in virtual storage.

System Action: Obtain a SYSABEND dump and call BMC support for assistance.

RECAT FAILED,DATASET NOT CATALOGED CLUSTER=clustername
DATASET NOT ON VOLUME: volserCLUSTER=clustername
OBTAIN FAILED, VOLUME: volserCLUSTER=clustername
DATASET FAILED IAM VALIDATIONCLUSTER=clustername

Explanation: An error as indicated by the reason in the message occurred during an IDCAMS DEFINE RECATALOG of an IAM data set.

Return Codes: The RECATALOG request will be failed with return codes from the failing service.

System Action: Make the corrections to the RECATALOG to correct the identified error, and rerun. If unable to determine why the request failed, contact BMC support for assistance.

PROBABLE IAM FILE HAS NOT BEEN DEFINED, DSN=dsname

Explanation: The processing program issued a SHOWCAT catalog request for a non-VSAM file that is cataloged, but does not have the IAM information (as established by DEFINE or file load) was not returned. This message is for diagnostic purposes, and will only be issued when an IAMDEBUG DD DUMMY DD card is in the job step of the program issuing the SHOWCAT macro.

Return Codes: The SHOWCAT is given a return code of 32 (x'20'), indicating that the file cannot be accessed through IAM or VSAM.

System Action: This is an unexpected error situation, and should be reported to BMC. Please have a LISTCAT ALL output from IDCAMS available when calling.

IAM NOT LICENSED FOR AIX OR RRDS SUPPORT CLUSTER=dsname

Explanation: An IDCAMS DEFINE was attempted for an alternate index, a path, or a numbered (RRDS) type of data set. While IAM does support those types of data sets, the version of IAM being used has not been licensed for those optional features.

Return Codes: The DEFINE request is failed with a return code of 22 and a reason code of 12. These codes will appear in an IDC3009I message.

System Action: If you have purchased an IAM license for those features, make sure that you are running with the version of IAM that has been licensed. If you believe that the version you are running should have the optional features license, contact BMC support. If you would like to purchase a license for these features, contact BMC .

IAM DEFINE OF NON-SUPPORTED FILE TYPE CLUSTER=dsname

Explanation: An IDCAMS DEFINE was issued with an indication that the file should be an IAM file, but the file type cannot be converted to IAM. Examples are, VSAM RRDS (Relative Record data sets and VSAM Linear data sets.

Return Codes: The DEFINE is failed with a return code of 22, and a reason code of 8. These codes will appear in an IDC3009I message.

System Action: Correct the IDCAMS DEFINE to either change the file type to one supported by IAM, or remove the indication that the file is to be an IAM file.

IAM ALLOCATION FAILED COMP=xxxx CODE=xxxx CLUSTER=clustername
IAM MM WRITE CI FAILED, ECB=nn R15=nnnnnnnn, CLUSTER=clustername
IAM MM READ CI FAILED RETC=nnn DIAG=nnnnnnnn, CLUSTER=clustername
CONNECT RC=xx FDBK=xxxxxxxx xxxxxxxx MM ERROR, Cluster=clustername
IAM DEFINE FALIED, RC=nnn REFER TO IAMCAMS, CLUSTER=clustername
INVALID ATTRIBUTES: listed in message,CLUSTER=clustername

Explanation: An error occurred during an IDCAMS DEFINE of an IAM file. The codes displayed correspond to the return code and reason codes of the IDC3009I message from IDCAMS, and there will also be a IDC3009I message on SYSPRINT with the same codes. There may also be additional IDC or IAMW messages.

For MM Connect, Write, Read or DEFINE failure, contact technical support for assistance. For Invalid Attributes the defined data set did not meet IAM Linear data set requirements for one or more specific attribute, most likely caused due to an improper DATACLASS.

Return Codes: The DEFINE request is failed with the return code and reason code given in this message. Some of the more common return codes include:
8,38 - data set already cataloged
16,0 - SMS failed allocation request, refer to IGD messages
22,8 - IAM does not support type of VSAM file requested.
42,0 - MVS DADSM failed allocation request
56,6 - User not RACF authorized to define the file
58,0 - Obtain of VTOC entry failed
58,4 - Specified DASD volumes not online
68,20 - No space on selected volume
140,36 – Invalid IAM Override card
140,120 – SMS Compressed data set cannot be used for IAM
140,2nn – Error defining IAM Linear type data set
176,0 - No space in VTOC
184,4 - data set is allocated to another job or user
192,0 - Exceeded maximum allowable IAM record size

System Action: Refer to IAM-Catalog-Return-Codes Catalog Return Codes or IDCAMS error message IDC3009I for meaning of the codes. Correct the problem, and resubmit. It may be necessary to issue an IDCAMS DELETE command before attempting to resubmit the DEFINE.

LISTC INTERCEPT FAILED COMP=xxxx CODE=xxxx CLUSTER=UNKNOWN

Explanation: A catalog Locate or LISTC request intercepted by IAM failed and received the specified completion and return codes.

Return Codes: The request is failed with the indicated return code and reason code.

System Action: Refer to VSAM errors message IDC3009I for meaning of the codes. Correct the problem and resubmit.

LOCATE FOR AN IAM FILE FAILED CODE=(cc)xxx [DSN=......]

Explanation: Locate for an IAM file failed for one of the following reasons:

—CODE=S1xxx The IAM SHOWCAT intercept issued a locate which failed with return code xxxx on the specified data set. This form of the message will only appear when there is an IAMDEBUG DD DUMMY coded in the failing job step.

—CODE=S2xxx The IAM SHOWCAT intercept issued a locate which failed with return code xxxx. The locate was issued by CI number, so the data set name is unknown.

Return Codes: The SHOWCAT is given a return code of 32 (x'20'), indicating that the file cannot be accessed through IAM or VSAM.

System Action: Make sure that the data set is still properly cataloged. If not, an IDCAMS DEFINE RECATALOG must be done. If further assistance is required, contact BMC support.

IAM DYNALLOC FAILED 'description'

Explanation: During the processing of an IDCAMS DEFINE for an IAM file, IAM's attempted use of Dynamic Allocation failed for the specified reason. This message presents a brief English description of the error code returned by Dynamic Allocation, which is supplied in the IAMW61 error message. Both messages are printed on the system log. There will also be an IDC3009I message on SYSPRINT, with an appropriate error code.

Return Codes: The DEFINE request is failed, with a return code and reason code that matches the problem description.

System Action: Correct the error situation, as described with the matching text below, and rerun the DEFINE.

DATASET NAME IN USE BY ANOTHER JOB/USER

Explanation: The data set name has been enqueued on by another job/user. Action: Through whatever software facilities available, determine which job and/or users are enqueued on the data set, and rerun the DEFINE upon the completion of the other job/user.

System Action: Text: VOLUME NOT MOUNTED ON SPECIFIED UNIT

User Response: The specified volume was either not mounted, or was mounted but not on the unit specified by the UNIT= keyword on the IAM override control statement for this file. For non-specific volume requests, (that is, with VOL(ANYVOL) coded), there were no volumes mounted as storage for the unit name specified on IAM Override Control statement, or SYSDA.
Action: Mount the required volume, or change the volume and/or unit specification.

REQUIRED CATALOG NOT MOUNTED

Explanation: The catalog required for the definition of the IAM data set is on a volume that is not currently mounted.

System Action: Insure that the volume containing the user catalog is mounted, and rerun the DEFINE.

REQUESTED SPACE NOT AVAILABLE ON VOLUME

Explanation: The volume specified or selected did not have sufficient space to satisfy the request.

System Action: Ensure that the space requested is actually needed, and adjust if possible.

Otherwise, select a different volume, remove unneeded data sets from the volume, or run COMPAKTOR to consolidate free space.

IAM DYNALLOC FAILED COMP=nnnn CODE=nnnn CLUSTER=clustername
IAMCAMS DYNALLOC FAILED, CODE=nnnn, INFO=nnnn,CLUSTER=clustername

Explanation: The dynamic allocation requested by IAM to perform the DEFINE operation failed with the printed error codes. This message may be accompanied by an IAMW60 message.

If message states IAMCAMS then IAM DEFINE process was not able to dynamically allocate a SYSOUT data set for IDCAMS output used when defining an Encrypted / Linear type data set.

Return Codes: The DEFINE request is failed, with a return code and reason code that matches the problem description.

System Action: Refer to message IAMW60, if printed, and/or the IDC3009I error message on SYSPRINT. The error codes from Dynamic Allocation are documented in the MVS Authorized Assembler Services Guide. Correct the error condition as indicated by the error codes, and rerun the DEFINE.

IAM OPEN FAILED FOR DDNAME=ddname CLUSTER=clustername

Explanation: During DEFINE processing of an IAM file, IAM attempted to OPEN the defined file, however the OPEN failed. Additional IBM messages may appear on the system log.

Return Codes: The DEFINE request is failed with a return code of 62, reason code of 0.

System Action: Determine the cause of the OPEN failure, correct the error, and rerun the job. For a new DEFINE (as opposed to RECATALOG), DELETE and redefine the data set. 

IAM I/O ERROR: 'synad message'

Explanation: During the processing of a DEFINE command for an IAM file, an I/O error occurred when reading or writing the IAM control information.

Return Codes: The DEFINE request is failed with a return code of 62, reason code of 0. If an IAMDEBUG DD DUMMY is specified, then the program will abend with a U0310.

System Action: Using the standard SYNAD message and other messages that may appear on SYSLOG, determine the cause of I/O error and correct it. If this was not a RECATALOG operation, DELETE and DEFINE the IAM data set again. 

UNEXPECTED END OF FILE READING AN IAM FILE FOR RECATALOG REQUEST -- NOT VALID IAM DATASET

Explanation: During the processing of a DEFINE RECATALOG command for an IAM file, an end of file occurred while attempting to read the file characteristics.

Return Codes: The DEFINE request is failed with a return code of 86, reason code of 4.

System Action: The data set is empty. The recatalog request was not performed. Either the file was never an IAM file, in which case no corrective action is required, or the data set has been clobbered. To recover the data set, it can be restored from a good backup, or a recovery attempted with program 'IAMRECVR'. Recover the file, then retry the recatalog processing. 

IAM

 SCRATCH FAILED COMP=nnnn CODE=nnnn VOLSER=vvvvvv

IAM

 UNCATLG FAILED COMP=nnnn CODE=nnnn CLUSTER=clusternameExplanation: After an error attempting to catalog or initialize an IAM file being defined, an attempt to delete or uncatalog the data set failed. The codes are returned from SCRATCH or UNCATLG request, which are documented in the SYSTEM DATA ADMINISTRATION Space.

Return Codes: The return code for the DEFINE is based on the original condition that caused the error.

System Action: The data set is still on the specified volume. Refer to an immediately preceding IAMWnn message for the data set name. The data set must be manually scratched from the indicated volume and uncataloged prior to attempting to redefine the data set.

IAM REALLOC FAILED CODE=nnnn INFO=nnnn CLUSTER=clustername

Explanation: After successfully defining an IAM file, IAM had determined that the job step had DD cards which were allocated to the file, but were allocated to the wrong volume. The attempt to reallocate the file with dynamic allocation failed, with the indicated error codes.

Return Codes: The DEFINE completes with a return code of 0.

System Action: The IAM file has been successfully defined, but attempts to REPRO into the IAM file within the same step may fail. A subsequent REPRO into the IAM file can be done.

IAM SMS ALLOC FAILED RC=X'xx' REAS=X'xxxxxxxx' CLUSTER=clustername

Explanation: The define of an IAM file failed using DADSM allocation with the specified return code and reason code. Refer to the DADSM Create (ALLOCATE) Function Return Codes section of the IBM MVS/ESA DADSM/CVAF Diagnostic Aids for a description of the error codes.

Return Codes: The DEFINE request is failed with a return code of 62, reason code of 0.

System Action: Take the appropriate corrective action based on the error codes indicated, and retry the define request.

IAM UNIT NAME SEARCH FAILED, RC=xx CLUSTER=clustername

Explanation: During the define of a multivolume nonspecific allocation, an IAM call to the MVS Unit Name look up service failed as indicated in the message. The return code, if provided, is documented in the IBM MVS System Modifications Manual.

Return Codes: The DEFINE request fails with a return code of 72, reason 4.

System Action: If the condition indicated by the return code cannot be corrected, contact BMC support. As a circumvention, try a different UNIT override, or switch to specific volume allocation.

 IAM xx ELIGIBLE VOLUMES, nn VOLUMES REQUIRED CLUSTER=clustername

Explanation: During the define of a multi-volume nonspecific allocation, IAM found the indicated number of storage volumes in the specified UNIT name pool, however, more volumes then available were needed to satisfy the allocation request.

Return Codes: The DEFINE request fails with a return code of 72, reason 4.

System Action: Change the UNIT override to indicate a UNIT name that has sufficient storage volumes, or reduce the number of volumes requested.

DD='ddname' PUT ERROR -- WORK FILE DATASPACE OVERFLOW

Explanation: The size of the data space used to hold the index structure during a file load was insufficient for the file indicated by the ddname.

Return Codes: A reason code of 244(x'F4') is stored in the RPL error flags field (RPLERRCD) and the request fails with a return code of 8. The logical error exit, LERAD, if specified will be invoked. If the error is detected during close, the program is abended with a U0246 abend.

System Action: Increase the size of the data space by using the IAM CREATE override, specifying the DATASPACE keyword. As an alternative, specify a DATASPACE=0, which will force the use of a temporary work file.

TRACE DEACTIVATED - text indicating reason

Explanation: The IAM trace facility for Enhanced Format files has detected an error during activation. The possible reasons include
—The DDNAME IAMATR31 is not available
—There is insufficient storage available to obtain the trace work area.

System Action: If the IAMATR31 DD was not specified, add it to the job. If storage was not available for the trace work area, specify a larger REGION size, or a REORG of the IAM file may be required.

IAMASY ESPIE RECOVERY ENTERED FOR ABEND S0Cx

Explanation: A program check occurred under the IAM IRB while performing asynchronous processing for an I/O request with RPL OPTCD=ASY. Included in the displayed information are the PSW and registers at time of the error.

Return Codes: The specific request causing the error, if it is identified, will receive a return code of 8 with an RPL error code of 240(X'F0') stored in the RPLERRCD. IAM will internally issue an ENDREQ for that RPL to clean up any resources it may have held.

System Action: IAM will attempt to continue processing for the affected file. Contact BMC support with the full text of the message for assistance, and save any dumps that may have occurred to aid in diagnosis. 

IAM module name ESTAE ENTERED FOR ABEND Sxxx

Explanation: A abend occurred while opening or processing an IAM file. If the error occurred during open processing, IAM will attempt to free the resources acquired during the open process. Depending on the circumstance, the PSW and registers at time of the error may also be displayed.

Return Codes: The job may abend with a U0184, or the Open, Close, or I/O request will fail. An open request will fail with a return code of 8, and the ACB that has caused the error will have a reason code of 188(X’BC’) set in the ACBERFLG field. If IAM was using a Data Space for this file, it will be included in the dump. An I/O request will fail with a logical error, return code of 8, with an error code of x’B8’.

System Action: Contact BMC support with the full text of the message for assistance, and save any dumps that may have occurred to aid in diagnosis. For CICS, IAM will terminate open processing for this ACB, and will attempt to free all resources used by the failing OPEN request.

UCBLOOK MACRO FAILED R15=xxxx R0=xxxx CLUSTER=clustername

Explanation: During IAM file definition, an attempt to find the UCB on which the data set resides, or will reside, using the IBM UCBLOOK service has failed. IAM will continue, if possible, with the define request by utilizing a different UCB lookup technique.

System Action: Contact BMC support with the full text of the message for assistance.

DD=’ddname’ OPEN ERROR - DYNALLOC FAILED - CODE=xxxxxxxx

Explanation: During open of an IAM data set requiring an open of an alternate index component, the associated data set could not be allocated. The open process will fail with a return code of 8.

System Action: Look up the dynamic allocation failure code in the IBM Space on z/OS Authorized Assembler Services Guide and take appropriate corrective action. Refer Special Considerations for IAM Alternate Indexes for more information. If additional assistance is needed, Contact BMC support.

DD='ddname' OPEN ERROR - AN ABEND CONDITION OCCURRED

Explanation: While IAM was opening a file to be loaded, some type of system abend occurred. There should be additional messages indicating the exact abend condition. Open processing for this file is terminated.

Return Codes: The OPEN fails with a return code of 8 and a reason code of 192(X'C0') in the ACBERFLG field of the ACB being opened.

System Action: Correct the abend condition, and then reload the file. The most typical abend condition is an X37 abend, in which case delete and redefine the data set with more DASD space.

DD='ddname' OPEN ERROR - text indicating reason

Explanation: IAM was unable to open the specified file due to damaged control or index information on the file.

Return Codes: A reason code of 188(X'BC') is stored in the ACB error flags field (ACBERFLG) and the OPEN is failed with a return code of 8. If an IAMDEBUG DD DUMMY is in the job step, then the job will be abended with a U0184.

System Action: Do not attempt to reorganize the datas et with IDCAMS or other software. Use the IAMRECVR to recreate the file. For diagnosis, please do the following:

1. Rerun job with an //IAMDEBUG DD DUMMY card added and a //SYSUDUMP or //SYSABEND. If you have the ABENDAID, please insure that the standard IBM dump will be taken.

2. Save the damaged file, or back it up using FDR/ABR, or DFDSS.

3. Contact BMC for assistance.

MODULE 'modname' INSTALLED AT 'address' - VER nn

Explanation: The message is issued in response to a VIF status request when the module 'modname' is in place and is ready to provide IAM services to programs using ACB's to access VSAM files. The 'address' given is the virtual storage location of the named IAM VIF module. The version level number is also given for the module.

System Action: None, information message only.

THE IAM SYSTEM MODULES ARE 'status'

Explanation: This message is provided by IAMSTART when the IAM VIF modules are installed, or in response to VIF action commands when the IAM system level VSAM interface is already in place. The 'status' of the modules may be:
—ACTIVE
—REACTIVATED
—ALREADY INSTALLED

This message includes the version and release level of the VIF modules installed.

System Action: None, information message only.

THE IAM SYSTEM MODULES ARE 'status'

Explanation: This message is provided by IAMSTART in response to VIF action commands when the IAM system level VSAM interface is already in place. The status of the modules maybe:

NOT ACTIVE (the IAM system level VSAM interface is not in place),
INACTIVE (the IAM system level VSAM interface is in place but is not active).

System Action: None, information message only.

'ADDRESS' 'HEX core print'----- 'EBCDIC core print'

Explanation: This message is provided by IAMSTART when the VIF modules are first installed and is also the response to a VIF STATUS request when VIF is in place and is ready to provide IAM services to programs using ACBs. The 'ADDRESS' given is the virtual storage location of the VIF Vector Table Entry. The remainder of the line is the entry in hex and display format.

System Action: None, information message only.

IDPSTART FAILURE - REASON='number' 'reason'

Explanation: The activation of the IAM VSAM Interface failed for one of the following reasons:
01 OPERATING SYSTEM NOT MVS OR SP 1.2 OR HIGHER
02 INVALID INPUT PARAMETERS
03 UNABLE TO OBTAIN AUTHORIZATION
04 'vector table name' VECTOR TABLE IS INVALID
05 SYSLIB DD MISSING OR OPEN ERROR
06 'modname' NOT FOUND IN SYSLIB
07 'modname' MODULE LOAD ERROR
08 ERROR MODIFYING THE SVC TABLE
09 'modname' NOT FOUND
10 'modname' NOT FOUND IN THE LINKLIST
11 'modname' UNABLE TO DE-INSTALL
12 'modname' CDE OR LPDE ABOVE 16M ERROR
13 'modname' MODULE ABOVE 16M ERROR
14 GETMAIN ERROR
15 'modname' HAS SMP INSTALLED IDP MODULE
16 UNABLE TO OBTAIN DISPATCHER LOCK
17 FREEMAIN ERROR
18 UNABLE TO OBTAIN LOCAL LOCK
19 'modname' CDE NOT FOUND
20 ENQUEUE/DEQUEUE ERROR ON IAM RESOURCE
21 ENQUEUE/DEQUEUE ERROR ON SYSZSVC
22 INVALID VECTOR TABLE STATUS
23 INVALID VECTOR TABLE CDE ADDRESS
24 RC=xxxx FROM SVCUPDTE
27 'modname' and IAMVECTB ARE OUT OF SYNCH
28 VECTOR TABLE CANNOT BE STOPPED
30 PARM (PROD OR TEST) NOT SPECIFIED
31 HIGHER VERSION OF VIF ALREADY STARTED

System Action: If the problem persists call BMC support for assistance.

IAM- TRIAL VERSION FROM BMC CORP EXPIRES IN 'nnn' DAYS (PLEASE CONTACT BMC SUPPORT)

Explanation: This is a trial version of the IAM system. The number of days the trial will remain active is displayed. 

If you are a licensed IAM user, then it is possible that you have in your job a bad STEPLIB pointing to the old trial library. The library that contains the production copy will appear in the heading with a P following the version identification. For example, IAM V10.0.01/00P.

System Action: When there are 10 or fewer days before the trial to expire, this message cannot be deleted. To prevent the trial from expiring call BMC support for an extension PARM= value and use the JCL shown below to extend your trial's expiration date. The JCL to extend the trial is as follows:

 IOSCAPU MACRO FAILED COMP=xxxx CODE=yyyy

Explanation: IAM attempted to capture a UCB to initialize the IAM file being defined. The capture of the UCB failed, as indicated in the error message.

System Action: IAM terminates processing for the file being defined. The file will need to be deleted and redefined before it can be processed. The error codes are available in the MVS Authorized Assembler Services Reference Space. If assistance is needed with diagnosing the problem, Contact BMC . Attempting to define the file on a different volumes may circumvent the problem. A dump can be obtained by including an IAMDEBUG DD DUMMY statement in the JCL, which will result in a U0310 abend.

DD=xxxxxxxx REORG RECOMMENDED: > nn% RECORDS IN OVERFLOW

Explanation: It is recommended that the indicated ddnamed file be reorged because the associated data set has a greater than the indicated percentage of records in the IAM file Overflow area. This condition could cause performance degradation for sequential processing and may elongate the time to open the data set.

System Action: Reorg the IAM data set at the earliest possible time or if that is not possible or you would like to see this message less frequently use the IAM Global Option PCTTRECO to control when this message is issued.

DD=’ddname’ DYNDSPACE DSPSERV FAILED R15=xx REAS=yyyyyyyy

Explanation: IAM open processing attempted to acquire z/OS data space storage for the requested amount of Dynamic Data Space requested, which failed with the indicated return code and reason code. A return code of 08 with a REAS=xx0500xx indicates that acquiring the data space would violate the installation criteria as by the IEFUSI exit. A return code of 0C indicates an environmental error, such as inadequate resources available to fulfill the request.

System Action: IAM will continue processing the data set without use of the Dynamic Data Space. Users can contact their systems programmer to find out more information as to why they were unable to use data space storage. Return codes and reason code values are documented in the MVS Assembler Services Reference for the DSPSERV macro.

AIX Recatalog Process Messages

These messages are possible from the Alternate Index automatic recatalog process that can be invoked when opening an alternate index component that has been either renamed or copied to a new name. This process is intended to automatically update the IAM alternate index relationships with the changed names.