IAM Journal Exit WTO Messages

IAMDD ddname: INITQ BROKEN, JOURNAL PROCESSING TERMINATED.

Explanation: An error occurred during the IAM Journal Exit initialization processing. This error can occur when multiple concurrent I/O requests are active and are requiring service from the IAM Journal Exit while it is attempting to allocate and open the log data set.

System Action: I/O requests will continue to be serviced to the IAM data set, however journaling is no longer being done by IAM for the indicated IAM  data set. Contact BMC for assistance.

IAMDD ddname: ALLOCATION OF LOG FILE FAILED, JOURNAL PROCESSING TERMINATED.

Explanation: The dynamic allocation of the log file for the specified IAM data set has failed.

System Action: I/O requests will continue to be serviced for the indicated IAM data set, however, journaling is not being done. If you are having difficulty determining why the LOG data set is not able to be allocated, Contact BMC for assistance.

IAMDD ddname: GETMAIN1 FAILED, JOURNAL PROCESSING TERMINATED.

Explanation: There is insufficient below the 16 megabyte line storage available in the region for IAM to acquire the storage required to handle the requested journaling. The amount of storage being requested that resulted in this failure is generally less than 2K. The OPEN of the indicated IAM data set will be failed.

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: Generally increasing the REGION parameter for the job step should correct this problem. If it does not, then contact BMC for assistance. This problem can be circumvented by turning journaling off for this file, through the use of the IAM overrides. (i.e., JRNAD=NONE).

IAMDD ddname: OPEN OF LOG FILE FAILED, JOURNAL PROCESSING TERMINATED.

Explanation: The OPEN of the log file has failed. There should be some IBM messages indicating the cause of the failure.

System Action: I/O requests will continue to be serviced for the indicated IAM data set, however, journaling is not being done. Correct the error condition based on the information available.

IAMDD ddname: BUFFER GETMAIN FAILED, JOURNAL PROCESSING TERMINATED.

Explanation: There is insufficient storage available to obtain the necessary I/O buffers for the IAM journal processing. For systems that are at a high enough level of DFSMS, the buffers are requested above the 16 megabyte line, otherwise the storage is requested from below the 16 megabyte line.

System Action: I/O requests will continue to be serviced for the indicated IAM data set, however journaling is not being done. The journal exit requests storage for five (5) buffers, so multiply the block size of the data set by 5 to determine storage requirements, and adjust your region parameter as necessary.

IAMDD ddname: SYNAD MESSAGE GOES HERE.......................

Explanation: An I/O error has occurred on the IAM Log data set. Review the I/O error cause from the message displayed.

System Action: I/O requests will continue to be serviced for the indicated IAM data set, however journaling is not being done. Correct the problem causing the I/O error.

IAMDD ddname: LOCATE FAILED FOR THE LOG FILE, JOURNAL PROCESSING TERMINATED.

Explanation: In an attempt to prevent allocation and open errors, the 

IAM

 Journal exit program will verify that the required log file is in the catalog. If it is not found in the catalog, then the OPEN request for the 

IAM

 data set will also fail.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: The OPEN request for the IAM file is failed. Either correct the error condition, or disable IAM journaling for this file and job step through the ACCESS override keyword JRNAD=NONE.

IAMDD ddname: OBTAIN FAILED FOR THE LOG FILE, JOURNAL PROCESSING TERMINATED.

Explanation: The IAM journal exit will attempt to make sure that the required log data set is allocated on the volume indicated by the catalog prior to attempting an allocation and open of this critical file. If the required log data set is not found, then the OPEN for the IAM data set will be failed.

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: Make sure that the required log data set is properly allocated and cataloged. Specifying the IAM ACCESS override JRNAD=NONE can be used to turn off journaling until the cause of the error is found.

IAMDD ddname: DCB ATTRIBUTES OF LOG FILE ARE INCOMPATIBLE, JOURNAL PROCESSING TERMINATED.

Explanation: The IAM journal exit will make sure that the attributes (RECFM, LRECL, and BLKSIZE) are appropriate as needed by the file being logged. If they do not meet the required criteria, the OPEN of the IAM data set will fail.

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 documentation on the IAM journaling exit to make sure that the DCB attributes selected for the LOG data set are appropriate, and change them as necessary. It is best to let IAM determine the DCB attributes, by just allocating the DASD space required for the LOG data set without specifying any DCB attributes.

IAMDD ddname: SAVEAREA GETMAIN FAILED, JOURNAL PROCESSING TERMINATED.

Explanation: There is insufficient virtual storage available for the IAM Journal Exit. The OPEN of the IAM data set will be failed. The amount of storage being requested is generally less than 1K, and it can reside in either above or below the 16 megabyte line.

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: Increase the REGION parameter of the job step that is failing with this error.