IAML0051 - IAML0075 IAMOPCOM MESSAGES

IAML0051

IAMOPCOM WAITING

Explanation: IAMOPCOM, the operator communications task for IAMRLS, is waiting for work.

System Action: None

IAML0052

IAMOPCOM SHUTTING DOWN

Explanation: IAMOPCOM has ended operator communications and is shutting down.

System Action: None

IAML0053

IAMOPCOM MODIFY RECEIVED

Explanation: IAMOPCOM has received a modify command.

System Action: None

IAML0054

IAMOPCOM RECEIVED INVALID COMMAND

Explanation: IAMOPCOM has received an invalid command.

System Action: Check the spelling and syntax of the command entered.

IAML0055

IAMOPCOM RECEIVED INVALID MODIFY

Explanation: IAMOPCOM has received an invalid modify command.

System Action: Check the spelling and syntax of the modify command entered.

IAML0056

IAML0057

JSWITCH COMMAND COULD NOT BE PROCESSED

Explanation: The JSWITCH command was entered to switch the journal data sets but IAMRLS is using the SYSTEM LOGGER for the journal so the switch could not be processed.

System Action: None

IAML0058

IAMOPCOM LOAD OF IAMBSTAE FAILED, ESTAE NOT ACTIVE

Explanation: IAMOPCOM was unable to load the IAMBSTAE module.

System Action: Check the contents of the IAM load library to ensure all of the distributed modules are present.

IAML0059

IAMOPCOM ESTAE ACTIVATION FAILED

Explanation: IAMOPCOM was unable to activate it's ESTAE routine.

System Action: Contact BMC for help in diagnosing the cause of this problem.

IAML0060

IAMOPCOM COMMAND INVALID, MISMATCHED QUOTES

Explanation: On an APPLY or RESTORE command, the data set name entered contains mismatched quotes.

System Action: Re-enter the command correctly.

IAML0061

IAMOPCOM COMMAND INVALID, MISMATCHED PARENTHESIS

Explanation: On an APPLY or RESTORE command, the data set name entered contains mismatched parenthesis.

System Action: Re-enter the command correctly.

IAML0062

MESSAGES COMMAND INVALID

Explanation: An invalid MESSAGES command was entered.

System Action: Check the syntax of the command and re-enter it correctly.

IAML0063

DISPLAY COMMAND INVALID

Explanation: An invalid DISPLAY command was entered.

System Action: Check the syntax of the command and re-enter it correctly.

IAML0064

SELECT TABLE DATASET LIST

Explanation: This is the header message for the list of SELECT TABLE data sets displayed as a result of the DISPLAY,SELECTTB command.

System Action: None

IAML0065

DSN: dsname or
NO MATCHING DATASETS FOUND

Explanation: This message is written once for every data set in the Select Table that matches the selection criteria or once if no data sets are found.

System Action: None

IAML0066

EXCLUDE TABLE DATASET LIST

Explanation: This is the header message for the list of EXCLUDE TABLE data sets displayed as a result of the DISPLAY,EXCLUDETB command.

System Action: None

IAML0067

DSN: dsname or
NO MATCHING DATASETS FOUND

Explanation: This message is written once for every data set in the Exclude Table that matches the selection criteria or once if no data sets are found.

System Action: None

IAML0068

NO SELECT TABLE DATASET LIST PRESENT

Explanation: A DISPLAY,SELECTTB command was entered and no Select Table exists.

System Action: None

IAML0069

NO EXCLUDE TABLE DATASET LIST PRESENT

Explanation: A DISPLAY,EXCLUDETB command was entered and no Exclude Table exists.

System Action: None

IAML0070

RELEASELOCKS COMMAND INVALID

Explanation: An invalid RELEASELOCKS command was entered.

System Action: Check the syntax of the command and re-enter it correctly.

IAML0071

CLOSEFILE COMMAND INVALID

Explanation: An invalid CLOSEFILE command was entered.

System Action: Check the syntax of the command and re-enter it correctly.

IAML0072

GETMAIN FAILED ON CLOSEFILE COMMAND

Explanation: The GETMAIN for an OCQ needed for the CLOSEFILE command failed, the close is not done.

System Action: Check the region size of the IAMRLS address space.

IAML0073

CLOSE COMMAND FAILED, O/C TASK NOT ACTIVE.

Explanation: The OPEN CLOSE TASK was not active and the close command could not be processed.

System Action: The QUIESCE,FORCE command may have been entered, if so, all files will have been closed. If not then call BMC for further assistance in diagnosing this problem.

IAML0074

RETAINED LOCKS PRESENT, QUIESCE,FORCE REQUIRED TO OVERRIDE

Explanation: IAMRLS will not shut down while there are record locks that have been retained due to transaction or job step abend that have not yet been recovered.

System Action: Make sure all recovery action has been processed. If you decide not to have the recovery performed, you can either issue the release retained locks commands, or do the QUIESCE with the FORCE operand.

IAML0075

ECHO OF WHATEVER OPERATOR COMMAND IS ENTERED

Explanation: This message is issued in confirmation that the IAM/RLS or IAM/PLEX address space has received the indicated operator command.

System Action: None. This is an informational message only.

IAML0076

EXTRA I/O TASK ATTACHED

Explanation: An extra I/O subtask was attached to handle an increase in workload.

System Action: None

IAML0077

 I/O TASK ATTACHED

Explanation: This message is issued once for every I/O subtask attached during initialization, till the MINIOTASK is reached.

System Action: None

IAML0078

IAMOPCOM APPLY COMMAND INVALID, NO DSN WAS PROVIDED

Explanation: An APPLY command was issued to IAMRLS but no DSN was provided to use as input for command.

System Action: Reissue the command with a valid DSN.

IAML0086

RLSLOGDD ALLOCATION FAILED, LOGGING DISABLED

Explanation: The RLSLOGDD DD statement was not present in the JCL used to start the IAMRLS address space and IAMRLS was not able to dynamically allocate it. Logging is disabled.

System Action: If you want logging active, stop IAMRLS and add the RLSLOGDD DD and restart IAMRLS.

IAML0087

RLSLOGDD DEALLOCATED BY LOGSWITCH COMMAND

Explanation: The RLSLOGDD has been deallocated due to the issuance of the LOGSWITCH command.

System Action: None

IAML0088

RLSLOGDD REALLOCATED BY LOGSWITCH COMMAND

Explanation: The RLSLOGDD has been reallocated due to the issuance of the LOGSWITCH command.

System Action: None

IAML0089

RLSLOGDD SWITCH COMPLETED

Explanation: The switch of the RLSLOGDD to a new sysout data set has been completed.

System Action: None

IAML0090

RLSLOGDD DEALLOCATION FAILED, LOGSWITCH TERMINATED

Explanation: The RLSLOGDD could not be deallocated, the LOGSWITCH command has been terminated.

System Action: The JOURNAL subtask should have printed out the DYNAMIC ALLOCATION messages indicating the reason for the failure.

IAML0091

IAMBDSNT PROCESSING COMPLETED

Explanation: The processing of the SELECT and EXCLUDE lists is complete.

System Action: None

IAML0092

RLSLOGDD ALLOCATION FAILED, LOGGING DISABLED

Explanation: The RLSLOGDD could not be reallocated, logging to the RLSLOGDD is disabled.

System Action: Examine the log for messages indicating the reason for the allocation failure. call BMC if you cannot correct the error situation.

IAML0093

RLSLOGDD LOGSWITCH COMPLETE

Explanation: The LOGSWITCH command has completed successfully.

System Action: None

IAML0094

RLSLOGDD ALLOCATED TO SYSOUT BY IAMLOGER

Explanation: The RLSLOGDD has been dynamically allocated during IAMRLS initialization due to the lack of the RLSLOGDD DD statement in the RLS proc.

System Action: None

IAML0095

RLSLOGDD DYNALLOC ERROR, RC= ,RSN=

Explanation: The dynamic allocation error codes describing the reason for the dynamic allocation failure.

System Action: Take corrective action if possible, otherwise call BMC if you cannot correct the situation.

IAML0096

RLSLOGDD ALLOCATED VIA JCL, CANNOT SWITCH

Explanation: The LOGSWITCH command cannot switch the RLSLOGDD if it was allocated via a DD statement in the RLS PROC.

System Action: None

IAML0100

TRACE DWA GETMAIN FAILURE - TRACE REQUEST FAILED

Explanation: The trace processor was unable to obtain storage for its work area.

System Action: Check the region size of the IAMRLS address space and increase if needed.

IAML0101

TRACE SUBTASK NOT ACTIVE - TRACE REQUEST FAILED

Explanation: The TRACE subtask is not active, tracing cannot be activated.

System Action: Check the RLSLOGDD and JESLOG to determine why the TRACE subtask was not started. Call BMC for help in diagnosing this problem.

IAML0102

TRACE REQUEST COMPLETED SUCCESSFULLY

Explanation: A TRACE request has completed successfully.

System Action: None

IAML0103

TRACE REQUEST FAILED

Explanation: A TRACE request has failed.

System Action: Call BMC for help in diagnosing the problem.

IAML0104

INVALID TRACE KEYWORD - TRACE REQUEST FAILED

Explanation: An invalid keyword was entered on a TRACE request.

System Action: Check the syntax of the command entered and re-enter it correctly.

IAML0105

TRACE ID REQUIRED. ENTER ID= OR CANCEL

Explanation: A trace ID is required on a TRACE request.

System Action: Enter a trace ID or CANCEL in response to the WTOR.

IAML0106

TRACE JOB AND/OR DSN REQUIRED. ENTER JOB=, DSN= OR CANCEL

Explanation: A jobname and/or a data set name is required for a TRACE request.

System Action: Enter a JOB=jobname or DSN=dsname or CANCEL in response to the WTOR.

IAML0108

TRACE TYPE REQUIRED. ENTERE TR= OR CANCEL

Explanation: The type of TRACE records to record is required on a TRACE request.

System Action: Enter one or more of the record types in response to the WTOR, for example:
TR=(IOS,IOE,BFR,EXCP,XTND,PC)

IAML0109

TRACE REQUEST MUST BE START, STOP, LIST OR CANCEL

Explanation: One of the above keywords must be present in the TRACE request.

System Action: Re-enter the TRACE request specifying either START, STOP, LIST, or CANCEL.

IAML0110

TRACE_ID=xxxxxxxx

Explanation: Output from a TRACE request showing the TRACE ID.

System Action: None

IAML0111

TYPE=IOS,IOE,BFR,EXCP,XTND,PC

Explanation: Output from a TRACE request showing the TRACE TYPES.

System Action: None

IAML0112

DSN=dsname

Explanation: Output from a TRACE request showing the DSNAME being traced.

System Action: None

IAML0113

JOBNAME=jobname

Explanation: Output from a TRACE request showing the JOBNAME being traced.

System Action: None

IAML0114

STEPNAME=stepname

Explanation: Output from a TRACE request showing the STEPNAME.

System Action: None

IAML0115

OUTDD=ddname

Explanation: Output from a TRACE request showing the OUTPUT DD.

System Action: None

IAML0116

TRACE_ID ALREADY ACTIVE. TRACE REQUEST FAILED

Explanation: A TRACE request with the same TRACE ID was already active, the current request is terminated.

System Action: If this is a new request use a different TRACE ID, if you want to change the old request, STOP it first then restart it with the new options.

IAML0117

SPECIFIED TRACE_ID NOT FOUND. TRACE NOT DEACTIVATED

Explanation: A TRACE,STOP command was issued but an active TRACE with the ID requested was not active.

System Action: None

IAML0118

NO ACTIVE TRACE REQUESTS FOUND

Explanation: No active trace requests were found to list on the TRACE,LIST command.

System Action: None

IAML0119

TRE GETMAIN FAILURE. TRACE REQUEST FAILED

Explanation: A GETMAIN for a trace element failed causing the trace request to be failed.

System Action: Check the region size of the IAMRLS address space. Contact BMC for assistance in diagnosing this problem.

IAML0120

TRACE OUTPUT OPEN FAILURE. TRACE REQUEST FAILED

Explanation: The TRACE processor could not open the requested trace output file.

System Action: Make sure the file is allocated and has sufficient space

IAML0121

TRACE OUTPUT DCB GETMAIN FAILURE. TRACE REQUEST FAILED

Explanation: The GETMAIN for the trace output DCB failed. The TRACE request is failed.

System Action: Check the region size of the IAMRLS address space, Contact BMC for assistance in diagnosing this problem.

IAML0122

OUTPUT DD FOR TRACE_ID xxxxxxxx IS ddname

Explanation: Output from a TRACE request showing the OUTPUT DD.

System Action: None

IAML0123

IAM ADDRESS SPACE TRACE REQUEST:

Explanation: Output header line for a trace request.

System Action: None

IAML0124

TRACE_ID xxxxxxxx DEACTIVATED

Explanation: The trace id in the message has been deactivated.

System Action: None

IAML0125

TRACE_ID xxxxxxxx QUEUED

Explanation: A trace request has been queued and will become active when the requested selection criteria have been met.

System Action: None

IAML0126

TRACE_ID xxxxxxxx ALREADY ACTIVE

Explanation: An active trace request is already active with the trace id requested on a new trace request.

System Action: If this is indeed a new request, choose a new trace id.

IAML0127

INVALID TRACE KEYWORD IN PARMLIB - TRACE REQUEST FAILED

Explanation: An invalid trace keyword was detected, the trace request fails.

System Action: Correct the trace keyword in error.

IAML0128

INVALID DSN SPECIFIED - TRACE REQUEST FAILED

Explanation: An invalid data set name was specified on a trace request, the trace request is failed.

System Action: Re-enter the trace request with a valid data set name.

IAML0129

DATASET ALLOCATION FAILED

Explanation: Allocation of the output data set for a trace request failed.

System Action: Make sure the output data set exists and is available for use.

IAML0130

LOG OF USER TRACE REQUEST

Explanation: Log entry of the trace request as entered by the user.

System Action: None

IAML0150

dsname OPENED DD=ddname J=jobname S=stepname I=jobid

Explanation: DSNAME X.Y.Z DDNAME DDDDDDDD under JOBNAME JJJJJJJ and STEPNAME SSSSSSS using PROGRAM PPPPPPPP was successfully opened by IAMRLS.

System Action: None

IAML0151

dsname OPEN FAILED DD=ddname J=jobname S=stepname I=jobid

Explanation: The indicated data set was not successfully opened by IAMRLS.

System Action: None

IAML0152

dsname DYNALOC FAILED RC=nnnn DD=ddname J=jobname S=stepname I=jobid

Explanation: The indicated data set could not be dynamically allocated by IAMRLS.

System Action: None

IAML0153

dsname CLOSED DD=ddname J=jobname S=stepname I=jobid

Explanation: The indicated data set was successfully closed by IAMRLS.

System Action: None

IAML0154

dsname CLOSE FAILED DD=ddname J=jobname S=stepname I=jobid

Explanation: DSNAME X.Y.Z DDNAME DDDDDDDD under JOBNAME JJJJJJJ and STEPNAME SSSSSS using PROGRAM PPPPPPPP was not successfully closed by IAMRLS.

System Action: None

IAML0155

dsname DYNDEAL FAILED RC=nnnnnnnn DD=ddname J=jobname

Explanation: IAMRLS attempted to deallocate the indicated data set, but encountered a failure.

System Action: Determine cause of the problem from the return codes. Contact BMC support if further assistance is needed.

IAML0156

dsname CLOSE COMMANDS ISSUED DUE TO IAMRLS REQUEST

Explanation: In response to an operator command the indicated data set has been closed.

System Action: None

IAML0157

dsname OPEN REQUESTED BY RLSID=rlsid CPUID=xxxxxxxx

Explanation: The indicated data set has been opened for processing by the indicated IAMPLEX region.

System Action: None.

IAML0158

dsname CLOSE REQUESTED BY RLSID=rlsid CPUID=xxxxxxxx

Explanation: The indicated data set has been closed due to a request from the indicated IAMPLEX region.

System Action: None

IAML0167

IAMBROC-IAMBSTAE LOAD FAILED - ESTAE NOT ACTIVE

Explanation: The remote open/close task that is responsible for sending those requests to a remote IAM/PLEX instance encountered a non-zero return code when attempting to load the IAMBSTAE load module. The task will continue to operate however will not have ESATE protection for recovery should the task experience an abend condition.

System Action: Notify BMC technical support for assistance.

IAML0168

IAMBROC-ESTAE ACTIVATION FAILED

Explanation: The remote open/close task that is responsible for sending those requests to a remote IAM/PLEX instance encountered a non-zero return code when attempting to activate an ESTAE environment. The task will continue to operate, however, it will not have ESATE protection for recovery should the task experience an abend condition.

System Action: Notify BMC technical support for assistance.

IAML0169

IAMBROC-SCHEDULE FAILED RC=xxxxxxxx J=jobname S=stepname I=jobid

Explanation: The request to schedule an SRB in the address space identified by the indicated job step failed with the indicated return code, displayed as hex digits. This SRB was intended to resume processing within that job step on completion of the open or close request being handled by IAM/PLEX.

System Action: If the indicated job step is no longer active, then no action is necessary. If the indicated job step is active, obtain a dump of this IAM/PLEX address space and the batch job indicated then notify BMC technical support for assistance. The job will most likely have to be canceled and restarted.

IAML0170

IAMBQP - PAUSE/RELEASE ERROR - XXXXXXXX - RC=XXXXXXXX

Explanation: An I/O subtask received an error during PAUSE or RELEASE processing.

System Action: None

IAML0173

RLSID=rlsid IS NO LONGER CONNECTED TO GROUP=rlsgroup

Explanation: The IAM/PLEX instance identified by the indicated RLSID is no longer connected to the indicated RLSGROUP. Message is issued during termination processing of the indicated IAM/PLEX instance.

System Action: None.

IAML0174

REMOTE NAME TOKEN AREA DELETED FOR RLSID=NNNN

Explanation: The IAM/PLEX instance identified by the indicated RLSID has deleted its name token area. Message is issued during termination processing of the indicated IAM/PLEX instance.

System Action: None.

IAML0175

RLS SYSPLEX GROUP INFORMATION FOR RLSID=CCCC

Explanation: This message appears in response to a DISPLAY,GROUP command issued on an IAM/PLEX instance identified by the indicated RLSID. It will be followed by subsequent IAML0176 messages.

System Action: None.

IAML0176

RLSID=rlsid,CPUID=cccccccc,STATUS=[ACTIVE¦CREATED¦QUIESCED¦FAILED¦NOT-DEF]

Explanation: This message appears in response to a DISPLAY,GROUP command issued on an IAM/PLEX instance identified by the indicated RLSID on the preceding IAML0175 message. This message displays the known IAM/PLEX instances by RLSID and CPUID that are associated with the same RLSGROUP indicated by the IAML0175 message, along with the current status.

System Action: None.

IAML0177

IAML0178

IAML0179

IAML0180

IAML0181

IAML0182

IAML0183

IAMBROC RESPONSE RECEIVED FROM TARGET RLSID=rlsid CPUID=ccccccccExplanation: An IAM/PLEX remote open/close task has received a response from a prior request to a target address space.

System Action: None. This message is only displayed when the MESSAGES=ALL parameter has been specified.

IAML0184

IAMBROC XCF FAILURE DURING cccc REQUEST/RESPONSE, TARGET RLSID=rlsidExplanation: An error was encountered either sending or receiving a message from XCF. There should be a message preceding this message with more details.

System Action: Search for preceding message for details on the failure, and take the associated action.

IAML0185

IAMBROC function IXCMSGO FAILURE RC=xx REAS=xxxxxxxx TARGET=rlsid CPUID=cupid

Explanation: The transmission of the indicated request type that was destined for the indicated target IAM/PLEX address space failed with the indicated return and reason code.

System Action: Check the return code and reason code to determine the cause of the error. If it is an environmental factor, correct the problem. Take a dump of the IAM/PLEX address space that issued the message with the IAMPLEX operator command of DUMP. Then contact BMC support for assistance if needed.

IAML0186

IAMBROC TERM RLSID=rlsid NOT CURRENTLY ACTIVE

Explanation: A router IAM/PLEX instance received a job step termination request which needed to be sent to the indicated TARGET IAM/PLEX instance, however, the Target IAM/PLEX address space was not active.

System Action: No action is necessary if the indicated IAM/PLEX region is not active. If it is active, enter a DISPLAY,GROUP command and dump the IAM/PLEX address space, then Contact BMC support with t requested information.

IAML0187

IAMRLS ROUTER ENTRY NOT FOUND AFTER function RLSID=rlsid...

Explanation: The Target IAM/PLEX did not find the indicated Router IAM/PLEX instance. Because of which, it was unable to return a response back to the originating system.

System Action: If the Target system is still running and the job did not abend, the job will need to be canceled.

IAML0188

IAMBOC function XCF RESPONSE SENT TO ROUTER

Explanation: The Target IAM/PLEX instance has responded to the Router IAM/PLEX upon completion of the indicated function.

System Action: None. This is an informational message only.

IAML0189

IAMBOC EXTERNAL function status RLSID=rlsid CPUID=cupid MSGID=msgid JOB=jobname

Explanation: This message is displayed by the TARGET IAM/PLEX address space indicating the processing of an open or close request from an external ROUTER IAM/PLEX instance.

System Action: None. This is an informational message that is only displayed when the MESSAGES=ALL parameter is set.

IAML0190

dsname OPEN-type DD=ddname J=jobname S=stepname I=job#####

Explanation: Message issued by IAM/PLEX ROUTER on completion of an open request on a TARGET system. The “type” will be either “I” for input only, or “U” for update. The rest of the information provided is based on the job that had requested the open.

System Action: None. This is an informational message followed by an IAML0191 message.

IAML0191

dsname OPENED ON RLSID=rlsid CPUID=xxxxxxxx

Explanation: Message issued by IAM/PLEX ROUTER on completion of an open request on a TARGET system. This message will follow the IAML0190 message, and provide information on the TARGET IAM/PLEX instance that actually did the open.

System Action: None. This is an informational message followed by an IAML0191 message.

IAML0192

dsname CLOSED DD=ddname J=jobname S=stepname I=job#####

Explanation: Message issued by IAM/PLEX ROUTER on completion of a close request on a TARGET system. The rest of the information provided is based on the job that had requested the open.

System Action: None. This is an nformational only message followed by an IAML0191 message.

IAML0193

Dsname CLOSED ON RLSID=rlsid CPUID=xxxxxxxx

Explanation: Message issued by IAM/PLEX ROUTER on completion of a close request on a TARGET system. This message will follow the IAML0192 message, and provide information on the TARGET IAM/PLEX instance that actually did the close.

System Action: None. This is an informational message followed by an IAML0191 message.

IAML0194

IAML0195

IAML0196

dataset name NO OID DD=ddname J=jobname S=stepname I=jobidExplanation: Record lock manager was unable to create an owner identifier block.

System Action: Contact BMC for support

IAML0200

INSUFFICIENT STORAGE FOR ADDITIONAL RECORD LOCKS

Explanation: IAMBRLOK was unable to obtain more storage for lock tables. The I/O that requested the record lock is failed.

System Action: Make sure IAMRLS has sufficient storage in the area being used for the record locks.

IAML0201

INSUFFICIENT STORAGE FOR ADDITIONAL OWNER ELEMENTS

Explanation: IAMBRLOK was unable to obtain more storage for owner elements. The I/O that requested the record lock is failed.

System Action: Make sure IAMRLS has sufficient region size in the startup JCL.

IAML0202

INSUFFICIENT STORAGE FOR DEADLOCK DETECTION
INSUFFICIENT SERIALIZATION WORK AREAS

Explanation: IAMBRLOK was unable to obtain more storage for the indicated area. For dead lock detection, processing continues, however, a dead lock situation is possible. For other reasons, request is failed with a logical error of x’28’

System Action: Make sure IAMRLS has sufficient region size in the startup JCL. Contact BMC for support after dumping the region.

IAML0203

RECORD LEVEL LOCKING ALREADY INITIALIZED

Explanation: A call has been made to IAMBRLOK to perform initialization and IAMBRLOK has detected that initialization has already been done.

System Action: call BMC for help in diagnosing this problem.

IAML0204

INSUFFICIENT STORAGE FOR LOCK HASH TABLE

Explanation: IAMBRLOK was unable to obtain more storage for a lock hash table.

System Action: Make sure IAMRLS has sufficient region size in the startup JCL.

IAML0205

INSUFFICIENT STORAGE FOR RECORD LOCKS

Explanation: IAMBRLOK was unable to obtain storage for record locks during initialization. The startup of IAM/PLEX instance will be failed.

System Action: Either increase storage via REGION or if locks are to be in 64-bit storage increase the MEMLIMIT parameter for more storage. Alternatively, reduce the value for MAXLCKS. Then restart the failing IAM/PLEX instance.

IAML0206

INSUFFICIENT STORAGE FOR LOCK OWNER TABLE

Explanation: IAMBRLOK was unable to obtain more storage for lock owner tables. The IAM/PLEX or IAM/RLS startup has failed.

System Action: Make sure IAMRLS has sufficient region size in the startup JCL.

IAML0207

INSUFFICIENT STORAGE FOR LOCK OWNER POOL

Explanation: IAMBRLOK was unable to obtain storage for a lock owner pool. The IAM/PLEX or IAM/RLS startup has failed.

System Action: Make sure IAMRLS has sufficient region size in the startup JCL.

IAML0208

INSUFFICIENT STORAGE FOR DEADLOCK DETECTION

Explanation: IAMBRLOK was unable to obtain storage for deadlock detection tables. The IAM/PLEX or IAM/RLS startup has failed.

System Action: Make sure IAMRLS has sufficient region size in the startup JCL.

IAML0209

INSUFFICIENT STORAGE FOR LOCK WORK AREA

Explanation: IAMBRLOK was unable to obtain storage for a lock work area. If this occurs during initialization of the IAM/RLS or IAM/PLEX instance, the startup will be failed. If this occurs during regular processing, the request being process will be failed.

System Action: Make sure IAMRLS has sufficient region size in the startup JCL.

IAML0210

DEADLOCK CONDITION DETECTED, I/O REQUEST FAILED FOR J=jobname S=stepname DD=ddname

Explanation: A deadlock condition was detected for DD=ddname J=JOBNAME S=STEPNAME. The I/O request is failed.

System Action: Wait for the other user of the resource to end and resubmit the job.

IAML0211

LOCKS HAVE BEEN RETAINED FOR JOB ASID=xxxx J=jobname S=stepname I=jobid

Explanation: In response to a DISPLAY,RETAINEDLOCKS, this message indicates for what job steps record locks were retained due to an abend.

System Action: None. This is an informational message only.

IAML0212

RL DSN=dsname ASID=xxxx J=jobid S=stepname I=jobid

Explanation: In response to a DISPLAY,RETAINEDLOCKS,DSN. This message indicates the data set name, and associated job step for which record locks have been retained. A group of these messages is preceded by message IAML0211.

System Action: None. This is an informational message only.

IAML0213

NO LOCKS RETAINED

Explanation: In response to a DISPLAY,RETAINEDLOCKS command, this message indicates that there are no retained locks.

System Action: None. This is an informational message only.

IAML0214

RETAINED LOCKS FOUND, SEE RLSLOGDD

Explanation: In response to a DISPLAY,RETAINEDLOCKS command. The list of retained locks is displayed in the RLSLOGDD.

System Action: None. This is an informational message only.

IAML0215

Dsname LOCKED ASID=xxxx J=jobname S=stepname I=jobid

Explanation: In response to a DISPLAY,CONTENTION command, indicates that the specified job has record locks held for the identified data set.

System Action: None. This is an informational message only.

IAML0216

MAXLOCK CONDITION DETECTED, I/O REQUEST FAILED FOR DD=12345678 J=12345678 S=12345678

Explanation: The batch job indicated in the message attempted to exceed concurrently holding more record locks than specified by the IAM/RLS or IAM/PLEX startup parameter value for MAXLOCKS. This results in failing this and any subsequent I/O requests that require record locks unless locks are released. The reason for this action is to prevent IAM/RLS or IAM/PLEX address space failures due to storage shortages that can be caused by holding an excessive number of record locks at one time.

System Action: This batch job step needs to be revised to either (1) use the AUTOSYNCPOINT function, (2) incorporate calls to the IAM batch Syncpoint routine to release locks, or (3) set some of the files being processed to a non-recoverable state by turning off before image journaling.

IAML0217

NO RECORD LOCK CONTENTION FOUND

Explanation: In response to a DISPLAY,CONTENTION command, indicates that no record lock contention was detected, meaning that no I/O requests are waiting for record lock.

System Action: None. This is an informational message only.

IAML0218

RECORD LOCK CONTENTION FOUND, SEE RLSLOGDD

Explanation: In response to a DISPLAY,CONTENTION command, indicates that record lock contention exists. This means that some I/O requests are waiting for a record lock. Additional details on what is waiting can be found in messages in the RLSLOGDD.

System Action: Review the RLSLOGDD for more information on the lock contention.

IAML0219

LOCK CONTENTION FOUND FOR FOLLOWING KEY:

Explanation: In response to a DISPLAY,CONTENTION command, indicates the specified records that are experiencing contention.

System Action: None. This is an informational message only.

IAML0220

UNABLE TO OBTAIN 64-BIT STORAGE FOR LOCKS RC= xx REASON=xxxxxxxx
REQUESTED x,xxx,xxx MEGABYTES OF 64-BIT STORAGE

Explanation: During initialization of an IAM/PLEX or IAM/RLS address space, IAM was not able to obtain the required amount of 64-bit virtual storage to use for the record locking structures. The IAM/PLEX or IAM/RLS address space will terminate due to this problem.

System Action: Make sure to provide an adequate MEMLIMIT value on the EXEC card of the PROC or in the system SMFPRMxx so that IAM can obtain the necessary storage. Alternatively the amount of storage requested can be reduced by lowering the MAXLOCKS parameter however that may result in subsequent failures if the number of concurrently held record locks requires more storage and is unable to obtain it at that time.

IAML0222

BRLOK SYNCPOINT

Explanation: A SYNCPOINT request was issued by the indicated job or CICS transaction.

System Action: None, this message is informational only and will only be displayed when the MESSAGES=ALL parameter has been set.

IAML0223

IAMBRLOK ENTERED FOR CICS SYNCPOINT/TX END

Explanation: A SYNCPOINT request was issued by a CICS transaction.

System Action: None, this message is informational only and will only be displayed when the MESSAGES=ALL parameter has been set.

IAML0224

IAMBRLOK FOUND MATCHING CICS TX OID

Explanation: Indicates that IAMBRLOK found an entry for the CICS transaction that had issued a SYNCPOINT and will perform the syncpoint processing.

System Action: None, this message is informational only and will only be displayed when the MESSAGES=ALL parameter has been set.

IAML0225

IAMBRLOK ENTERED FOR JOB STEP TERMINATION

Explanation: IAMBRLOK was entered to perform cleanup of locks for a job step termination.

System Action: None, this message is informational only and will only be displayed when the MESSAGES=ALL parameter has been set.

IAML0226

IAMBRLOK JOB STEP END RELEASING LOCKS

Explanation: IAMBRLOK has released record locks during a job step end.

System Action: None, this message is informational only and will only be displayed when the MESSAGES=ALL parameter has been set.

IAML0227

IAMBRLOK JOB ABENDED, RETAINING LOCKS

Explanation: IAMBRLOK has retained record locks after a job abend.

System Action: Insure that a backout recovery is performed for this file, then release the locks if not already done so by IAMRLS.

IAML0228

IAMBRLOK BATCH SYNCPOINT RELEASING LOCKS

Explanation: IAMBRLOK has been called from the batch syncpoint exit to release locks following a syncpoint exit call from the batch program.

System Action: None, this message is informational only and will only be displayed when the MESSAGES=ALL parameter has been set.

IAML0229

IAMBRLOK ENTERED FOR BATCH SYNCPOINT

Explanation:  IAM RLS lock manager has been called to release locks from a job issuing batch syncpoints.

System Action: None, this message is informational only and will only be displayed when the MESSAGES=ALL parameter has been set.

IAML0230

IAML0230

IAML0232

RECORD LOCKS RETAINED ASID=xxxx J=jobname S=stepname I=jobid

Explanation: Record locks held by the specified job were retained due to an abend or because of address space failure.

System Action: Make sure that a file recovery is performed, which will release the retained locks.

IAML0233

QUEUED DYNAMIC BACKOUT REQUEST ASID=xxxx J=jobname S=stepname I=jobid

Explanation: IAM RLS posted the dynamic job backout task to perform a backout on the indicated job step due to an abend or address space failure.

System Action: Verify from subsequent messages that the backout was performed and that it released the retained locks.

IAML0234

IAML0240

RELEASE RETAINED LOCKS REQUESTED ASID=xxxx J=jobname S=stepname I=jobid

Explanation: A RELEASELOCKS command has been issued for the indicated job. Any information not provided on the command will be printed as asterisks.

System Action: None. This is an informational message only.

IAML0241

IAML0242

IAML0243

REQUESTED JOB NOT FOUND ASID=xxxx J=jobname S=stepname I=jobid

Explanation: The job specified on a RELEASELOCKS command could not be found.

System Action: Issue either a DISPLAY,RETAINEDLOCKS or DISPLAY,CONTENTION to get a list of job(s) which currently have locks, and supply more job identification on the RELEASELOCKS command.

IAML0244

NONE RELEASED, MORE THAN 1 MATCH ASID=xxxx J=jobname S=stepname I=jobid

Explanation: In response to a RELEASELOCKS command, IAM RLS found more than one matching job. No record locks were released

System Action: Reissue the RELEASELOCKS command with more specific job identification, as can be found on the preceding IAML0241 messages.

IAML0245

IAML0246

TERMINATING JOB OID NOT FOUND ASID=xxxx J=jobname S=stepname I=jobid

Explanation: A job termination request was given to the IAM/RLS or IAM/PLEX address however IAM had no record of the job.

System Action: None.

IAML0247

IXCMSGO FAILED, RC=xx REAS=xxxxxxxx RLS=rlsid J=jobname S=stepname I=jobid

Explanation: A TARGET IAM/PLEX instance processed termination for a job, however the attempt to respond to the ROUTER IAM/PLEX instance failed with the indicated return and reason codes.

System Action: If unable to correct the problem from the provided information, contact BMC support for assistance.

IAML0250

IAMBREST INITIALIZATION FAILURE. BATCH BACKOUT NOT AVAILABLE

Explanation: The automatic batch backout was either unable to obtain storage or encountered an invalid environment during initialization and is unable to process.

System Action: Contact BMC support for assistance.

IAML0251

BACKOUT REQUESTED ASID=xxxx J=xxxxxxxx S=xxxxxxxx I=xxxxxxxx

Explanation: The automated job backout process has started processing a backout for the failed job that is indicated in the message.

System Action: None.

IAML0252

BACKOUT COMPLETE ASID=xxxx J=xxxxxxxx S=xxxxxxxx I=xxxxxxxx

Explanation: The automated job backout has completed processing for the indicated failed job.

System Action: None.

IAML0253

IAML0254

J=xxxxxxxx S=xxxxxxxx I=xxxxxxxx (JOURNAL I/O TRACE MSG)

IAML0255

IAMBREST DATASPACE INIT FAILURE. BACKOUT WITHOUT DATASPACE

Explanation: IAMBREST requested Data Space storage, however that request failed. IAMBREST continues processing without the use of Data Space storage.

System Action: Notify BMC technical support of problem.

IAML0256

IAMBREST REQUIRED JOURNAL DATASET ALLOCATION FAILURE. BACKOUT NOT PERFORMED

Explanation: IAMBREST could not allocated a required journal data set.

System Action: Make sure all journal data sets are properly cataloged and available. If so, then Contact BMC support for assistance.

IAML0257

BACKOUT FAILED ASID=xxxx J=jobname S=stepname I=jobid

Explanation: The dynamic job backout processing has failed.

System Action: Contact BMC support. Attempt to perform backout manually with the IAMJREST utility.

IAML0258

BACKOUT COMPLETE - JOURNAL RECORDS USED - XXXXXXXX ASID=XXXX

Explanation: Dynamic Job Backout has performed a backout using the indicated number of journal records.

System Action: None.

IAML0261

IAMBREST CAN NOT LOCATE CURRENT JOURNAL - BACKOUT NOT PERFORMED

Explanation: Current journal data set can not be determined.

System Action: Restore ends with RC=8.

IAML0262

IAMBREST CANNOT POSITION TO STARTING JOURNAL FOR BACKOUT - BACKOUT NOT PERFORME

Explanation: Cannot determine staring journal based on timestamps for journal activation and job/step start.

System Action: Restore ends with RC=8.

IAML0263

IAMBREST INTERNAL DSN ENTRY NOT FOUND - BACKOUT NOT PERFORMED

Explanation: Current journal DSN not found in list of available journals for this execution of IAMRLS

System Action: Restore ends with RC=8.

IAML0264

IAMBREST COULD NOT DETERMINE DSN FOR ALLOCTION: dataset.name

Explanation: Invalid DSN was passed for Dynamic Allocation.

System Action: Restore ends with RC=8.

IAML0265

IAMBREST ALLOCATION FAILED FOR DSN: dataset.name RC=xxxxxx REAS=xx

Explanation: Dynamic Allocation Error.

System Action: See Return Code (RC=) and Reason Code (REAS=) and take appropriate action.

IAML0266

DJB TRACE ACTIVE - DDNAME=ddname

Explanation: Dynamic Job backout trace is active for DDNAME=ddname

System Action: None

IAML0267

DJB TRACE ACTIVATION FAILED

Explanation: Dynamic Job Backout trace activation failed.

System Action: None

IAML0275

IAMRLS STORAGE SHORTAGE OBTAINING IOQ OR OCQ CELL

Explanation: IAM/PLEX or IAM/RLS was unable to obtain additional storage for the control block used to manage an I/O or open/close request.

System Action: Attempt to take a dump of the IAM/PLEX or IAM/RLS address space with the
F iamplex,DUMP operator command, then notify BMC technical support for assistance.

IAML0276

I/O REQUEST SENT TO TARGET=rlsid CPUID=cpuid MSGID=xxxxxxxx

Explanation: The IAM/PLEX instance acting as a router has sent an I/O request to the target IAM/PLEX.

System Action: None, informational only. Message will only appear when the MESSAGES=ALL parameter has been specified.

IAML0277

I/O RESPONSE RECEIVED FROM TARGET=xxxx CPUID=xxxxxxxx MSGID=xxxxxxxx

Explanation: The IAM/PLEX router has received a response for an I/O request from the target IAM/PLEX.

System Action: None. This is an informational message that will only appear when the MESSAGES=ALL parameter has been specified.

IAML0278

I/O ERROR RESPONSE FROM TARGET=rlsid CPUID=cupid MSGID=xxxxxxxx

Explanation: The IAM/PLEX router has received a response for an I/O request from the target IAM/PLEX that indicates an error was encountered with IAM/PLEX processing.

System Action: Obtain a dump of the IAM/PLEX target and router address spaces, and notify BMC technical support.

IAML0279

I/O ERROR - TARGET TERMINATED - TARGET=rlsid CPUID=cupid

Explanation: A router IAM/PLEX address space had been posted by recovery for an I/O request sent to the indicated target.

System Action: If the indicated target IAM/PLEX instance is operational, notify BMC technical support.

IAML0280

I/O EXPECTED RESPONSE - TARGET=rlsid CPUID=cupid

Explanation: A router IAM/PLEX address space received an invalid response from the target IAM/PLEX address space for the I/O request.

System Action: Take a dump of both the router and target IAM/PLEX address spaces as soon as possible, and Contact BMC support for assistance.

IAML0281

IAMBIO REQ xxxxx xxxx/xxxxxxxx MSGID=xxxxxxxx LEN=xxxxxxxx

Explanation: The target IAM/PLEX address space has received the indicated I/O request from the router IAM/PLEX address space and is beginning processing of that request.

System Action: None. Informational message that is only issued when the MESSAGES=ALL parameter is set.

IAML0282

IAMBIO RESP xxxxx xxxx/xxxxxxxx MSGID=xxxxxxxx FDBK=xxxxxxxx

Explanation: The target IAM/PLEX address space has completed processing the indicated I/O request and is sending the response back to the router.

System Action: None. Informational message that is only issued when the MESSAGES=ALL parameter is set.

IAML0283

IAMBPC07 IOQ=xxxxxxxx OBTAINED FOR REMOTE I/O OCQ=xxxxxxxx

Explanation: The router IAM/PLEX has received an I/O request destined for another IAM/PLEX address space, and has obtained the internal control block necessary for the request.

System Action: None. Informational message that is only issued when the MESSAGES=ALL parameter is set.

IAML0284

IAMBPC07 IOQ=xxxxxxxx REQUEUED AFTER REMOTE I/O OCQ=xxxxxxxx'

Explanation: The router IAM/PLEX has received a response from the target IAM/PLEX address space for an I/O request and is releasing the internal control block necessary for the request.

System Action: None. Informational message that is only issued when the MESSAGES=ALL parameter is set.

IAML0285

IAMBPC02 SYNCPOINT REQUEST IOQ=xxxxxxxx

Explanation: The router IAM/PLEX has received a syncpoint request.

System Action: None. Informational message that is only issued when the MESSAGES=ALL parameter is set.

IAML0286

IAMBPC03 TRACE MESSAGES

Explanation: Trace messages issued from IAMBPC03 when MESSAGES=ALL is specified and IAMBMON is in use.

System Action: None.

IAML0287

IAMBPC02 SYNCPOINT Release Fail

Explanation: Release of task to perform SYNCPOINT request failed.

System Action: Contact BMC for support.

IAML0300

RECORD LOCK RECOVERY INITIALIZING

Explanation: Message occurs during startup of an IAMRLS or IAMPLEX address space to indicate that the Record Lock Recovery function is being initialized. Subsequent messages will be provided on the initialization process and the status of the Record Lock Recovery when the initialization has been completed.

System Action: None. This is an informational message only.

IAML0301

RECORD LOCK RECOVERY ACTIVE, CHECKPOINT EVERY XXX MINUTES

Explanation: The message indicates that the Record Lock Recovery function has successfully been initialized and is currently active. The check point frequency is indicated.

System Action: None. This is an informational message only.

IAML0302

INSUFFICIENT STORAGE LOCK RECOVERY WORK AREA

Explanation: The Record Lock Recovery function was not able to obtain sufficient virtual storage to initialize.

System Action: Increase the amount of above the line region available using the REGION parameter on the EXEC card and restart the region. A REGION=0M value is recommended for the IAMRLS or IAMPLEX address space. The IAMRLS or IAMPLEX region will continue without using the Record Lock Recovery function.

IAML0303

IAML0304

IAML0305

UNABLE TO ESTABLISH CHEKCPOINT EXIT, STIMERM FAILED WITH RC=XX

Explanation: The request to establish an timed exit to take the periodic check point for the Record Lock Recovery function failed with the indicated return code. Codes are documented in the IBM z/OS assembler macro space. The Record Lock Recovery process is disabled.

System Action: Contact BMC for support. The IAMRLS or IAMPLEX address space will need to be recycled to restart Record Lock Recovery processing.

IAML0306

RECORD LOCK RECOVERY CHECKPOINT COMPLETE
LOGGER BLOCK: XXXXXXXX XXXXXXXX or
JOURNAL TTTR: XXXXXXXX

Explanation: Informational message that appears periodically when MESSAGES=ALL has been specified that indicates a Record Lock Recovery checkpoint has occurred.

System Action: No action required, this is an informational only message.

IAML0307

FORMATTING RECORD LOCK RECOVERY DATASET

Explanation: During IAMRLS or IAMPLEX region startup, the Record Lock Recovery journal data set is being pre-formatted. This occurs either when it is found to be unloaded or when the LOCKSTART=COLD parameter was specified. Upon completion, the Record Lock Recovery function will be activated.

System Action: None. This is an informational message only.

IAML0308

FORMATTED nnn,nnn,nnn OWNER RECORDS AND nnn,nnn,nnn LOCK RECORDS

Explanation: During IAMRLS or IAMPLEX region startup, it was found that either the record lock recovery data set was not preformatted, or LOCKSTART=COLD was specified. This has resulted in Record Lock Recovery formatting out the journal file it will use to track the lock ownership on recoverable data sets.

System Action: None. This is an informational message only.

IAML0310

ACTIVE LOCK OWNER RECORDS PROCESSED = nnn,nnn,nnn

Explanation: During IAMRLS or IAMPLEX region startup, the indicated number of lock owners were reestablished.

System Action: None. This is an informational message only.

IAML0311

ACTIVE RECORD LOCK RECORDS PROCESSED= nnn,nnn,nnn

Explanation: During IAMRLS or IAMPLEX region startup, the indicated number of record lock were processed and reestablished from the Record Lock journal information.

System Action: None. This is an informational message only.

IAML0312

LOCK RECORDS DROPPED, MISSING OWNER = nnn,nnn,nnn

Explanation: During IAMRLS or IAMPLEX region startup, the indicated number of record locks could not be reestablished due to the absence of the corresponding lock owner information, that is, job name, step name, job id, and so on. The most likely reason is that the some of the data blocks may not have been physically written out to the record lock journal.

System Action: If the record lock recovery also reads the IAMRLS / IAMPLEX journal then this message is informational only. However, if no journal recovery is performed and the value is not zero, notify  BMC support.

IAML0313

RECORD LOCKS RECOVERED AND RETAINED = nnn,nnn,nnn

Explanation: Indicates the number of record locks that have been recovered from the record lock recovery data set.

System Action: Use the display retained locks command to find out what jobs and CICS regions need recovery to be performed to release the recovered locks.

IAML0314

RECORD LOCKS RECORDED AT SHUTDOWN, NO JOURNAL RECOVERY

Explanation: The record lock recovery function determined that the lock recovery data set was properly closed when the IAMRLS or IAMPLEX region last terminated. Therefore, it will have the proper status of the record locks, and lock recovery does not need to read the IAMRLS or IAMPLEX journal files to update the status of the recovered locks.

System Action: None. This is an informational message only.

IAML0315

RECORD LOCK RECOVERY INDICATES FAILED STATUS, WILL RE-INITIALZIE DATASET

Explanation: The record lock recovery encountered some problem resulting in the shut down of the record lock recovery function. For that reason the current data in the lock recovery data set is not current, so the data set will be initialized.

System Action: No action required. If you Contact BMC for support, please go through the RLSLOGDD and job log for any messages that will indicate the original failure that caused record lock recovery to terminate.

IAML0316

IXGBRWSE nnnnn FAILED, RC=XX REAS=XXXXXXXX

Explanation: The record lock recovery function encountered a failure while processing the system logger journal data set. The nnnnn is replaced with the function attempted. The request failed with the indicated return code and reason code.

System Action: Record lock recovery will stop processing the system logger, and use whatever locks have already been recovered. One can use the display retained locks to determine what locks have been recovered and are actively holding records. Contact BMC for technical support.

IAML0317

UNABLE TO OBTAIN STORAGE TO READ JOURNAL RECORDS

Explanation: Record lock recovery was unable to obtain sufficient storage to read records from the journal data set.

System Action: Record lock recovery will continue without performing the recovery of record locks based on the data written to the record lock data set only. If this occurs, please take a dump and Contact BMC and FTP the dump to BMC’s site.

IAML0318

LOCK RECOVERY JOURNAL RECORDS READ = nnn,nnn,nnn

Explanation: Indicates the total number of journal records read from the time of the last syncpoint until the failure to restore the record locks as they were at the time of the failure.

System Action: None. This is an informational message only.

IAML0319

LOCK RECOVERY JOURNAL RECORDS USED = nnn,nnn,nnn

Explanation: Indicates the number of journal records that were actually used to update the record locks.

System Action: None. This is an informational message only.

IAML0320

LOCK RECOVERY JOURNAL ADDED LOCKS = nnn,nnn,nnn

Explanation: Indicates the number of additional record locks acquired based on the before image records from the journal.

System Action: None. This is an informational message only.

IAML0321

LOCK RECOVERY JOURNAL RELEASED LOCKS= nnn,nnn,nnn

Explanation: Indicates the number of record locks released based on the syncpoint and job step end records read from the journal.

System Action: None. This is an informational message only.

IAML0322

LOCK RECOVERY JOURNAL ADDED OWNERS = nnn,nnn,nnn

Explanation: Indicates the number of new lock owners acquired based on the data read from the journal.

System Action: None. This is an informational message only.

IAML0323

LOCK RECOVERY JOURNAL RELEASED OWNER = nnn,nnn,nnn

Explanation: Indicates the number of lock owners removed based on the job step end or transaction end data read from the journal.

System Action: None. This is an informational message only.

IAML0324

IAML0325

IAML0326

LOCK RECOVERY PROCESSING JOURNAL DSN= dataset name

Explanation: This message indicates which journal data set is being used to find any update to record locks.

System Action: None. This is an informational message only.

IAML0327

IAML0328

TOTAL RECORD LOCKS RETAINED = nnn,nnn,nnn

Explanation: Indicates the total number of record locks reestablished as a result of the record lock recovery function.

System Action: None. This is an informational message only.

IAML0330

WARNING: IAMRLS LOCK QUEUE RECOVERY INVOKED, IAMRLS MAY BE NOT FUNCTIONING PROPERLY

Explanation: This message is issued when IAMRLS has detected that there may be a problem an internal queue of requests waiting for the Record Lock Manager Lock. A recovery routine has been invoked to analyze the queue in further detail for any errors, and update or rebuild the queue to resolve the problem. Message is displayed as a non-deletable message until the recovery process completes. This message is an alert that if the applications using data sets under this IAMRLS address space, that there may be a serious issue that could potentially result in an outage of IAMRLS services.

System Action: This is a warning message that indicates a potential problem under IAMRLS. A subsequent IAML0344 or IAML0345 should follow within a few seconds. Check that online systems and batch work utilizing IAMRLS are still functioning. There may be a brief delay as the queue will be locked during the recovery attempt. If problems are discovered in the queue, messages will be written in the RLSLOGDD message file. Examine the RLSLOGDD for the potential error messages. Please check for any system dump data sets that the recovery process may have generated which should be forwarded to BMC for problem diagnosis.

IAML0331

IAML0332

IAML0333

IAML0334

IAML0335

INVALID ENTRY POINTER FOUND ON Q: xxxxxxxx_xxxxxxxx HAS BEEN REMOVED FROM QUEUE

Explanation: Informational error message that the recovery process encountered an entry on the queue that was not valid, so it has removed that entry from the queue. A system dump has been requested by IAMRLS. The 64-bit address of the entry is included in the message and is important diagnostic information.

System Action: Please forward the dump to BMC for diagnosis. While no action is immediately required, be alert for the possibility of an I/O request with no response from the IAMRLS address space due to removal of this invalid queue entry.

IAML0336

INVALID ECB: XXXXXXXX FOR ENTRY: xxxxxxxx_xxxxxxxx HAS BEEN REMOVED FROM QUEUE

Explanation: Informational error message that the recovery process determined that the queue entry at the specified 64_bit address had an was waiting on an ECB that was determined to be invalid, for some reason such as the address was not a valid virtual storage address at the time of the recovery process. A system dump has been requested by IAMRLS for diagnosis by BMC.

System Action: Please forward the dump to BMC for diagnosis. While no action is immediately required, be alert for the possibility of an I/O request with no response from the IAMRLS address space due to removal of this invalid queue entry.

IAML0337

INVALID PRB: xxxxxxxx FOR ENTRY: xxxxxxxx_xxxxxxxx HAS BEEN REMOVED FROM QUEUE

Explanation: Informational error message that the recovery process determined that the queue entry at the specified 64_bit address that the PRB address pointed to by the waiting ECB does not match a task that was found waiting for this ECB, which implies that the task will not be dispatched when the ECB is posted. A system dump has been requested by IAMRLS for diagnosis by BMC.

System Action: Please forward the dump to BMC for diagnosis. While no action is immediately required, be alert for the possibility of an I/O request with no response from the IAMRLS address space due to removal of this invalid queue entry.

IAML0338

UNKNOWN WAITER FOR LOCK QUEUE: xxxxxxxx_xxxxxxxx FOR TWA: XXXXXXXX NOT PUT ON QUEUE

Explanation: Informational error message that the recovery process determined that the queue entry at the specified 64_bit address is not a valid structure to be waiting on this lock. The address in the message for the TWA corresponds to the IAMRLS task processing the request. A system dump has been requested by IAMRLS for diagnosis by BMC.

System Action: Please forward the dump to BMC for diagnosis. While no action is immediately required, be alert for the possibility of an I/O request with no response from the IAMRLS address space due to removal of this invalid queue entry.

IAML0339

ENTRY NOT FOUND ON TASK SCAN: xxxxxxxx_xxxxxxxx NOT PUT ON QUEUE

Explanation: The entry at the indicated address was on the queue as waiting for the resource, however, it was not found from a scan of the TCB’s as being a resource that was actively being waited on. A system dump has been requested by IAMRLS for diagnosis by BMC.

System Action: Please forward the dump to BMC for diagnosis. While no action is immediately required, be alert for the possibility of an I/O request with no response from the IAMRLS address space due to removal of this invalid queue entry.

IAML0340

UNDETERMINED ERROR FOR ENTRY: xxxxxxxx_xxxxxxxx NOT PUT ON QUEUE

Explanation: The IAMRLS recovery process has found a request at the specified address is in error for an undetermined reason. The request was removed form the queue, and IAMRLS has requested a system dump for diagnosis.

System Action: Please forward the dump to BMC for diagnosis. While no action is immediately required, be alert for the possibility of an I/O request with no response from the IAMRLS address space due to removal of this invalid queue entry.

IAML0341

LOCK QUEUE RECOVERY CALL FAILED, FLAG INDICATED WAS ALREADY BUSY. LOGIC FAILURE.

Explanation: The flag indicating that the lock recovery process was active was set. Possibly it had previously tried to run but did not complete for some unexpected reason. This recovery invocation call is terminated.

System Action: If there is no other indication of a problem with IAMRLS, then no action is necessary. If there is a problem, such as a hang, take a dump of IAMRLS with the F IAMRLS,DUMP command and forward the dump to BMC for diagnosis. If that doesn’t work then cancel IAMRLS with a dump if IAMRLS is no longer functional. It may be necessary to use the FORCE command after the cancel to get the IAMRLS address space out of the system. Then IAMRLS can be restarted if it was canceled.

IAML0342

LOCK QUEUE RECOVERY CALL FAILED DUE TO NOT BEING ABLE TO ACQUIRE SERIALIZATION.

Explanation: The lock recovery process was unable to acquire serialization after multiple attempts. The serialization is needed to prevent any changes to the lock queue while the recovery process is executing. This recovery invocation call is terminated.

System Action: If there is no other indication of a problem with IAMRLS, then no action is necessary. If there is a problem, such as a hang, take a dump of IAMRLS with the F IAMRLS,DUMP command and forward the dump to BMC for diagnosis. If that does not work, then cancel IAMRLS with a dump if IAMRLS is no longer functional. It may be necessary to use the FORCE command after the cancel to get the IAMRLS address space out of the system. Then IAMRLS can be restarted if it was canceled.

IAML0343

FIRST ENTRY IN LOCK QUEUE CHANGED DURING THE RECOVERY, CHANGING TO RECOVERY VALUE

Explanation: The lock recovery process discovered that the top of the queue has changed. Due to the serialization that should not have happened.

System Action: IAMRLS will take a dump, and then proceed with the lock recovery process removing the unexpected entry on the queue, as it was not properly changed. Please forward the dump to BMC for diagnosis.

IAML0344

LOCK QUEUE RECOVERY COMPLETED, CHECK RLSLOGDD FOR ERROR MESSAGES. PROCESSING RESUMED.

Explanation: Record lock recovery has completed, with some error messages. The error messages have been written to the RLSLOGDD output file. IAMRLS has also requested a dump of its address space.

System Action: Please forward the dump and the error messages from the RLSLOGDD to BMC for problem diagnosis.

IAML0345

LOCK QUEUE RECOVERY COMPLETED WITH NO ERROR MESSAGES, PROCESSING RESUMED.

Explanation: The IAMRLS queue recovery process has completed. The queue has been revised as necessary. No additional messages have been written out to the RLSLOGDD data set.

System Action: No action is necessary, unless there are still problems with the IAMRLS address space. If there are still problems, take a dump with the F IAMRLS,DUMP command and forward the dump to BMC for diagnosis.

IAML0346

IAMRLS RLMLRLM Q RECOVERY FAILED DUE TO WORK TABLE OVERFLOW, IAMRLS MY BE IN TROUBLE

Explanation: The table that IAMRLS has acquired to contain recovery information so the queue can be rebuilt if necessary has been filled up. This is unexpected because there should have been sufficient space to handle all of the entries.

System Action: Please forward the dump to BMC for diagnosis. While no action is immediately required, this may be an indication that there are some problems within the IAMRLS address that may require action.

IAML0347

IAMRLS RUNNING REOCRD LOCK MANAGER LOCK QUEUESCAN, BRIEF DELAY IN LOCK PROCESSING

Explanation: This message will appear if the installation has enabled the periodic health check process for the queue recovery indicating a scan has been started to validate the queue.

System Action: None. This is an informational message only.

IAML0348

IAMRLS RECORD LOCK MANAGER LOCK QUEUE HEALTH CHECK FOUND NO PROBLEMS

Explanation: This message is issued upon the completion of a scan done on a periodic basis indicating that no problems were found with the queue.

System Action: None. This is an informational message only.

IAML0386

IAML0387

IAML0388

IAML0389

RECORD LOCK RECOVERY ERROR, EXPECTED LOCK SYNONYM POINTER IS 0

Explanation: An unexpected problem occurred in the record lock structure as it was being recreated by the record lock recovery process while processing the journal records.

System Action: Record lock recovery will deactivate itself. The record locks it has reestablished may not reflect the actual record lock circumstance at the time that the region was originally not available. Take a dump of the region using the F iamrls,DUMP command. If you need the record lock recovery, backup the record lock data set then recycle the IAM RLS or IAM PLEX region with LOKSTART=COLD. Contact BMC for support.

IAML0390

JOURNALING NOT ACTIVE, REQUIRED FOR RECORD LOCKING TO FUNCTION

Explanation: Record lock recovery did not find any active journaling, to either DASD files or to the system logger. Journaling is necessary for the functioning of record lock recovery to determine the status of record locks since the last record lock recovery syncpoint. Record lock recovery has already set up the status for records locks it found in the record lock data set, but that may not be the true lock status when the region became unavailable.

System Action: The record lock recovery function will not be active. If the above error can be resolved, then the record lock recovery data set should be restored to it’s contents prior to this startup, and it should be recycled.

IAML0391

RECORD LOCK RECOVERY CHECKPOINT ABENDED

Explanation: The record lock recovery code has abended. There should be preceding messages indicating the abend code. Depending on the circumstance, and what recovery can be done, it may have to disable record lock recovery until the region is restarted.

System Action: Please retain any dumps that have been taken and Contact BMC for support.

IAML0392

IAML0393

IAML0394

RECORD LOCK RECOVERY INVALID LOCK OWNER
LOCK DSN= dataset name

Explanation: The lock record had a reference to a non-existent or invalid owner record.

System Action: The lock is not re-established. Record lock recovery startup processing will continue. When the region is initialized, take a dump of the region and make a backup copy of the record lock control data set, then Contact BMC for support.

IAML0395

IAML0396

IAML0397

RECORD LOCK RECOVERY PROCESSING FAILED

Explanation: Record Lock Recovery function encountered a problem which should be described by prior error message(s), and will be now flagged as not active.

System Action: Record Lock Recovery function will be disabled. Take a dump of the IAM RLS or IAM PLEX region that encountered this error, and make a backup copy of the record lock recovery data set. If possible, correct the cause of the problem then recycle the IAM RLS or IAM PLEX region. It might be necessary to restart the region with LOCKSTART=COLD. Contact BMC for support.

IAML0398

RECORD LOCK RECOVERY INITIALIZATION FAILED

Explanation: Record Lock Recovery failed prior to reaching full activation. Prior messages should indicate the reason for the error.

System Action: Record Lock Recovery function will be disabled. Take a dump of the IAM RLS or IAM PLEX region that encountered this error, and make a backup copy of the record lock recovery data set. Correct the cause of the problem, then restart the region. It may be necessary to restart with LOCKSTART=COLD specified. Contact BMC for support.

IAML0399

RECORD LOCK RECOVERY NOT ACTIVE

Explanation: The Record Lock Recovery function has encountered some error that has resulted in the function being disabled.

System Action: Correct the problem which should be identified in prior messages, then recycle the IAM RLS or IAM PLEX region to reactivate Record Lock Recovery. If necessary Contact BMC for support.

IAML0400

IAMJRESM GETMAIN FOR WORKAREA FAILED.

Explanation: The IAMJRESM resource manager could not obtain storage for its work area. Step end records will not be written for jobs using the replication logs, the IAMJUTIL utility can be used to process backouts without the step end records.

System Action: The resource manager returns without writing a step end record.

IAML0401

IAMJRESM CSA GETMAIN OR LOCK OBTAIN FAILURE.

Explanation: The IAMJRESM resource manager could not get the local lock or could not GETMAIN extended CSA for the cell pool required to process step end records. Step end records will not be written for jobs using the replication logs, the IAMJUTIL utility can be used to process backouts without the step end records.

System Action: The resource manager returns without writing a step end record.

IAML0402

IAMJRESM UNABLE TO OBTAIN CELL FOR STEP END

Explanation: All cells in the cell pool are in use and the pool could not be expanded due to storage limitations. Step end records will not be written for jobs using the replication logs, the IAMJUTIL utility can be used to process backouts without the step end records.

System Action: The resource manager returns without writing a step end record.

IAML0403

CONNECT FAILED TO LOGSTREAM:cccc.cccc.cccc RC=xx RSNCD=xx

Explanation: The IAMJRESM resource manager was unable to connect to the specified log stream to write the step end record. Step end records will not be written for jobs using the replication logs, the IAMJUTIL utility can be used to process backouts without the step end records.

System Action: The resource manager returns without writing a step end record.

IAML0404

IAMJRESM DISCONNECTED FROM LOGSTREAM:cccc.ccccccc

Explanation: The IAMJRESM resource manager has disconnected from the specified log stream.

System Action: No action is necessary, informational only.

IAML0405

IXGWRITE IN IAMJRESM FAILED, RC= RSNCD=

Explanation: The IAMJRESM resource manager issued the IXGWRITE macro to write the step end record to the replication log stream. The write failed with the return code and reason code specified. Step end records may be missing for jobs using the replication logs, the IAMJUTIL utility can be used to process backouts without the step end records.

System Action: The resource manager returns without writing a step end record.

IAML0406

IAMDD cccccccc: GETMAIN FAILED, REPLICATION PROCESSING TERMINATED.

Explanation: The IAMJREPL journal exit was unable to obtain storage for its work area to process the replication log records for the specified ddname. Replication processing for this file is terminated.

System Action: Determine why the address space cannot get main a work area, possibly raise the region size for this job. Updates to this file will not be duplicated on the mirror system.

IAML0407

IAMDD cccccccc: SAVEAREA GETMAIN FAILED, REPLICATION PROCESSING TERMINATED

Explanation: The IAMJREPL journal exit was unable to obtain storage for a save area to process the replication log records for the specified ddname. Replication processing for this file is terminated.

System Action: Determine why the address space cannot get main a save area, possibly raise the region size for this job. Updates to this file will not be duplicated on the mirror system.

IAML0408

IAMJREPL CONNECTED TO LOGSTREAM: ccccc.ccccc

Explanation: The IAMJREPL journal exit connected to the specified log stream to process the replication log records.

System Action: None. This is an informational message only.

IAML0409

IAMJREPL DISCONNECTED FROM LOGSTREAM: ccccc.ccccc

Explanation: The IAMJREPL journal exit disconnected from the specified log stream during close processing.

System Action: None. This is an informational message only.

IAML0410

IAML0411

IAML0412

IAML0413

IAML0414

IXGWRITE OF INIT RECORD FAILED, RC=xx RSNCD=xx

Explanation: The IAMJREPL exit issued a write to the logstream for the initial record for a job and the write failed.

System Action: The return and reason codes are documented in the MVS Authorized Assembler Services References space. There may be problems with the log stream or underlying structures in the couping facility. The replication logs may not contain the information needed for replication on the target system.

IAML0415

IXGWRITE OF CLOSE RECORD FAILED, RC=xx RSNCD=xx

Explanation: The IAMJREPL exit issued a write to the logstream for the close record for a job and the write failed.

System Action: The return and reason codes are documented in the MVS Authorized Assembler Services References space. There may be problems with the log stream or underlying structures in the couping facility. The replication logs may not contain the information needed for replication on the target system.

IAML0416

IXGWRITE IN IAMJREPL FAILED, RC=xx RSNCD=xx

Explanation: The IAMJREPL exit issued a write to the logstream for a record update for a job and the write failed.

System Action: The return and reason codes are documented in the MVS Authorized Assembler Services References space. There may be problems with the log stream or underlying structures in the couping facility. The replication logs may not contain the information needed for replication on the target system. If you see RC=8 with RSNCD=860 you may need to adjust your Logstream LOWOFFLOAD and HIGHOFFLOAD settings.

IAML0417

IXGWRITE FAILED, RC=xx RSNCD=xx

Explanation: The IAMJREPL exit issued a write to the logstream to flush the buffers during a close call which failed.

System Action: The return and reason codes are documented in the MVS Authorized Assembler Services References space. There may be problems with the log stream or underlying structures in the couping facility. The replication logs may not contain the information needed for replication on the target system.

IAML0418

IAML0419

IAML0420

IAML0421

IAML0422

IAML0423

IAML0424

IAML0430

IAMDD : GETMAIN FAILED, REPLICATION PROCESSING TERMINATED.

Explanation: The journal exit for IAMLOGVR replication processing could not obtain storage for a workarea during open. Replication processing for the DDNAME mentioned in the message is terminated and the open is failed with an error code of x'BC' in the ACBERFLG field.

System Action: Determine why the job could not get enough storage for a workarea.

IAML0431

IAMDD : SAVEAREA GETMAIN FAILED, REPLICATION PROCESSING TERMINATED.

Explanation: The journal exit for IAMLOGVR replication processing could not obtain storage for a savearea needed to process a replication journal request. Replication processing is terminated for this DDNAME and the open is failed with an error code of X'BC' in the ACBERFLG field.

System Action: Determine why the job could not get enough storage for a savearea.

IAML0432

IAML0433

IAMLOGVR ADDRESS SPACE NOT ACTIVE, REPLICATION PROCESSING IS TERMINATED.

Explanation: The IAMLOGVR address space is not active. Replication processing is terminated and the open is failed with an error code of X'BC' in the ACBERFLG field.

System Action: Start the IAMLOGVR address space before trying to use the replication logging.

IAML0434

IAML0435

IAML0436

IAML0437

IAMLOGVR PC RETURNED NON ZERO RETURN CODE, RC=

Explanation: IAMJREPL uses a PC routine that is returning an error condition which should not happen. This error was on the write start record during OPEN. The open is failed with an error code of x'BC' in the ACBERFLG field.

System Action: Contact BMC for assistance.

IAML0438

IAMLOGVR PC RETURNED NON ZERO RETURN CODE, RC=

Explanation: IAMJREPL uses a PC routine that is returning an error condition which should not happen. This error was on the write close record during CLOSE.

System Action: Contact BMC for assistance.

IAML0439

IAMLOGVR PC RETURNED NON ZERO RETURN CODE, RC=

Explanation: IAMJREPL uses a PC routine that is returning an error condition which should not happen. This error occurred during the write of a change record.

System Action: Contact BMC for assistance.

IAML0440

IAMLOGVR PC RETURNED NON ZERO RETURN CODE, RC=

Explanation: IAMJREPL uses a PC routine that is returning an error condition which should not happen. This error occurred during the flush of buffers during close.

System Action: Contact BMC for assistance.

IAML0441

IAMJRES1 GETMAIN FOR WORKAREA FAILED

Explanation: IAMJRES1 is a resource manager established at open time to handle the writing of the end of job record and could not get main the storage needed for it's workarea. The end of job records cannot be written.

System Action: Contact BMC for assistance.

IAML0442

IAMJRES1 CSA GETMAIN OR LOCK OBTAIN FAILURE

Explanation: IAMJRES1 has to get the local lock to get main CSA storage to establish an anchor table to be able to write the end of job records to the replication log. If the local lock cannot be obtained or the CSA storage allocated then the end of job records cannot be written.

System Action: Contact BMC for assistance.

IAML0443

IAMJRES1 UNABLE TO OBTAIN CELL FOR STEP END

Explanation: IAMJRES1 was unable to allocate a cell in the anchor table to be able to store the information needed to write the end of job records to the replication log.

System Action: Contact BMC for assistance.

IAML0444

IAMJRES1 UNABLE TO LOCATE THE LOGVR TOKEN AREA

Explanation: IAMJRES1 was unable to locate the LOGVR token area created by the IAMLOGVR address space.

System Action: Check to make sure the IAMLOGVR was started and came up without error. If not started, Contact BMC for assistance.

IAML0445

IAMLOGVR PC RETURNED NON-ZERO RETURN CODE, RC=

Explanation: IAMLOGVR PC returned a non-zero return code to the resource manager while trying to write the end of job record.

System Action: Contact BMC for assistance.

IAML0446

IAMLGWTR CONNECT FAILED TO LOGSTREAM:cccc.cccc.cccc RC=xx RSNCD=xx

Explanation: IAMLOGVR subtask IAMLGWTR was unable to connect to the specified logstream. Replication records will not be written to this logstream until the error is corrected.

System Action: Examine the return and reason code for the IXGCONN macro. Contact BMC for assistance.

IAML0447

IAMLGWTR CONNECTED TO LOGSTREAM:cccc.cccc.cccc

Explanation: IAMLOGVR subtask IAMLGWTR connected to the specified logstream to process replication log records.

System Action: None. This is an informational message only.

IAML0448

IAMLGWTR DISCONNECTED FROM LOGSTREAM:cccc.cccc.cccc

Explanation: IAMLOGVR subtask IAMLGWTR disconnected from the specified logstream.

System Action: None. This is an informational message only.

IAML0449

IAMLGWTR WRITE FAILED FOR LOGSTREAM:ccccc.cccccc.cccc RC= RSNCD=

Explanation: IAMLOGVR subtask IAMLGWTR issued an IXGWRITE to the specified logstream and failed with the return code and reason code specified.

System Action: Examine the return and reason code for the IXGWRITE macro. Contact BMC for assistance.

IAML0450

IAMLOGVR ADDRESS SPACE ALREADY ACTIVE

Explanation: IAMLOGVR deteted an address space running under the same name.

System Action: None required.

IAML0451

GETMAIN OR LOCK OBTAIN FAILURE

Explanation: IAMLOGVR could not obtain the local lock needed for a CSA GETMAIN or there was not enough CSA to satisfy the CSA GETMAIN request.

System Action: Contact BMC for help in diagnosing this problem.

IAML0452

IAMLOGVR NAME TOKEN AREA CREATE FAILED

Explanation: IAMLOGVR could not create a name token area used to anchor the PC routines and workareas.

System Action: Contact BMC for help in diagnosing this problem.

IAML0453

LOAD OF SERVICE MODULE cccccccc FAILED

Explanation: IAMLOGVR could not LOAD the module named in the message.

System Action: Contact BMC for help in diagnosing this problem.

IAML0454

 IAMLOGVR TASK WORK AREA GETMAIN FAILED.

Explanation: IAMLOGVR could not obtain storage for the task workareas.

System Action: Contact BMC for help in diagnosing this problem.

IAML0455

ATTACH PROCESSOR FAILED, CANNOT CONTINUE

Explanation: IAMLOGVR could not attach a subtask to process a Logstream.

System Action: Contact BMC for help in diagnosing this problem.

IAML0456

OPTION TABLE TYPE INCORRECT, IAMLOGVR WILL TERMINATE

Explanation: IAMLOGVR loaded the option table and it does not match the level needed for this version of IAMLOGVR.

System Action: Contact BMC for help in diagnosing this problem.

IAML0457

SYSIN DD NOT FOUND IAMLOGVR WILL TERMINATE

Explanation: IAMLOGVR did not find or could not open the SYSIN DD and cannot continue.

System Action: Provide a SYSIN DD with the input for the IAMLOGVR task.

IAML0458

IAML0459

IAMLOGVR DELETED THE GLOBAL TOKEN AREA

Explanation: IAMLOGVR deletes its GLOBAL TOKEN area during shutdown.

System Action: None. This is an informational message only.

IAML0460

IAMLOGVR COULD NOT OBTAIN WORKAREA

Explanation: IAMLOGVR could not obtain a workarea needed for subtask processing.

System Action: Contact BMC for help in diagnosing this problem.

IAML0461

IAMLOGVR ATTACH OF IAMLGWTR TASK FAILED FOR LOGSTREAM: ccccccccccccc

Explanation: IAMLOGVR tried to attach a subtask to process the logstream named in the message.

System Action: Contact BMC for help in diagnosing this problem.

IAML0462

IAMLOGVR UNABLE TO OPEN SYSIN DD

Explanation: IAMLOGVR tried to open the SYSIN DD provided and the open failed.

System Action: Check the messages in the syslog for the reason the open failed.

IAML0463

IAMLOGVR UNABLE TO READ SYSIN DD NO LOGSTREAMS AVAILABLE

Explanation: IAMLOGVR was unable to read the SYSIN DD.

System Action: Check the messages in the syslog for the reason the read failed.

IAML0464

IAMLOGVR PROCESSING MODIFY cccccccc COMMAND

Explanation: IAMLOGVR is processing the MODIFY command entered by the operator.

System Action: None. This is an informational message only.

IAML0465

IAMLOGVR RECEIVED INVALID MODIFY

Explanation: IAMLOGVR did not find a valid modify command.

System Action: Correct the modify command and reissue.

IAML0466

IAMLOGVR ESTAE ENTERED FOR ABEND Sxxx
PSW AT TIME OF ERROR:
PSW FOR IAMLOGVR RB:
FAILING PROGRAM:
GPR 00-03:
GPR 04-07:
GPR 08-11:
GPR 12-15:
AR 00-03:
AR 04-07:
AR 08-11:
AR 12-15:

Explanation: IAMLOGVR's ESTAE detected and error and will print the programs status information at the time of the error.

System Action: Contact BMC for assistance.

IAML0467

LOGSTREAM:cccccccc.cccccccc ALREADY ACTIVE COMMAND IGNORED

Explanation: IAMLOGVR Found the LOGSTREAM in the ADDSTREAM command is already active, the command is ignored.

System Action: Check to make sure the correct logstream is entered.

IAML0468

LOGSTREAM:cccccccc.cccccccc NOT ACTIVE, COMMAND IGNORED

Explanation: IAMLOGVR Did not find the LOGSTREAM entered in the REMOVE command to be active, the command is ignored.

System Action: Check to make sure the correct logstream is entered.

IAML0469

NO ROOM IN TABLE FOR NEW LOGSTREAM

Explanation: IAMLOGVR Could not find room in the logstream table for a new Logstream.

System Action: Contact BMC for assistance.

IAML0470

CHECKBUFF FOUND NO BUFFERS

Explanation: The CHECKBUFF command did not find any buffer areas.

System Action: None. This is an informational message only.

IAML0471

CHECKBUFF FOUND nnnnnnnn TOTAL BUFFERS ALLOCATED, nnnnnnnn ON AVAILABLE QUEUE

Explanation: The CHECKBUFF command found the number of buffers listed.

System Action: None. This is an informational message only.

IAML0472

ALLOCATION OF MORE BUFFERS FAILED

Explanation: The MOREBUFF command could not allocate more buffers.

System Action: Check the MEMLIMIT for the IAMLOGVR address space.

IAML0473

LGWTR POSTED FOR ERROR QUEUE PROCESSING

Explanation: An IXGWRITE failed and the buffer was placed on an error queue. The message indicates that the SRB Listen exit posted the log writer task to process the error queue after the logstream offload task completed.

System Action: None. This is an informational message only.

IAML0502

GETMAINn FAILED, JOURNAL PROCESSING TERMINATED

Explanation: A getmain for the journal work area failed during journal processing initialization, journal processing is terminated.

System Action: If journal processing is desired, make sure the IAMRLS address space has a big enough region size to satisfy its storage needs and restart the address space.

IAML0504

BUFFER GETMAIN FAILED, JOURNAL PROCESSING TERMINATED

Explanation: A getmain for the journal output buffers failed during journal processing initialization, journal processing is terminated.

System Action: If journal processing is desired, make sure the IAMRLS address space has a big enough region size to satisfy it's storage needs and restart the address space.

IAML0506

SYNAD MESSAGE

Explanation: The SYNAD exit was entered during I/O to a journal file.

System Action: Call BMC for help in diagnosing this problem.

IAML0507

LOCATE FAILED FOR JOURNAL DSN dsname

Explanation: A locate failed for the specified journal data set during the initialization process for journaling.

System Action: Make sure the data set names provided in the startup parameters are correct and that the data sets are properly cataloged.

IAML0508

OBTAIN FAILED FOR JOURNAL DSN dsname

Explanation: An obtain failed for the specified journal data set during the initialization process for journaling.

System Action: Make sure the data set names provided in the startup parameters are correct and that the data sets exist on the volumes to which they are cataloged.

IAML0510

IAMBJRNL CLOSED DSN - DDD.DDD.DDD

Explanation: A journal data set has been closed.

System Action: None. This is an informational message only.

IAML0511

IAMBJRNL USING DSN - dsname

Explanation: The journal processor has selected the specified data set for journal use.

System Action: None. This is an informational message only.

IAML0512

JOURNALING HAS BEEN DISABLED

Explanation: Journaling has been disabled for IAMRLS processing either due to an initialization error or because no journal data sets have been provided and SYSLOGGER has not been selected.

System Action: If journaling is desired, fix the initialization error or specify journal data sets or SYSLOGGER in the IAMRLS startup parameters.

IAML0513

CONNECT FAILED TO LOGSTREAM: logstreamid

Explanation: IAMBJNRP was unable to connect to the specified journal logstream.

System Action: Make sure the system coupling facility policies have been defined correctly and the SYSTEM LOGGER is available on your CPU.

IAML0514

INIT OF JOURNAL FILES FAILED

Explanation: IAMBJRNP was unable to complete initialization of the journal files.

System Action: Make sure the data set names provided in the IAMRLS parmlib member for journal data sets is correct, and that they exist on DASD and have available space.

IAML0515

IAMBJRNL THE NEXT JOURNAL FILE IS NOT EMPTY, JOURNAL FILE SWITCH HAS FAILED.

Explanation: A JSWITCH command was entered to force a journal switch or a journal data set has filled causing an automatic switch, but the next journal data set is not empty.

System Action: This will be followed by message IAML0534 requesting you ready the next journal data set and respond "U" or reply "Q" to terminate the IAMRLS address space.

IAML0516

IAMBJRNL DSN - dsname DEALLOCATED

Explanation: A journal data set was de-allocated.

System Action: The data in the indicated journal should be copied to another data set on tape or DASD, and the indicated journal data set should then be emptied.

IAML0517

IAMBJRNL DEALLOCATION FAILED FOR DSN- dsname

Explanation: The de-allocation of a journal data set failed.

System Action: Call BMC for help in diagnosing this problem.

IAML0518

IAMBJRNL DSN - dsname ALLOCATED

Explanation: A Journal data set has been allocated for use.

System Action: None. This is an informational message only.

IAML0519

IAMBJRNL ALLOCATION FAILED FOR DSN- dsname

Explanation: The allocation of a journal data set has failed.

System Action: IAMRLS should switch to the next journal data set if possible. call BMC for help in diagnosing this problem.

IAML0520

IAMBJRNP CONNECTED TO LOGSTREAM: logstream

Explanation: The name of the System Logger Logstream that IAMRLS connected to for journal processing is displayed.

System Action: None. This is an informational message only.

IAML0521

IAMBJRNL DYNALLOC ERROR, RC= S99ERROR= S99INFO=

Explanation: IAMBJRNL received an error during dynamic allocation or deallocation or a journal data set.

System Action: None required.

IAML0524

IAMDD ddname: SPANNED RECORD TOO BIG, JOURNAL PROCESSING TERMINATED.

Explanation: Journaling was attempted on a spanned record file, but the record was larger then 32,756 which is the maximum size allowed.

System Action: Turn off journaling for this file, it is not allowed with such a large record size.

IAML0525

IAMDD ddname: SHUTDOWN IN PROGRESS OR JOURNAL PROCESSING TERMINATED

Explanation: The journal exit tried to journal a request for IAMDD ddname and was unsuccessful due to IAMRLS shutting down or the IAMRLS journal processing was terminated.

System Action: Check the RLSLOGDD and JESLOG for other messages indicating why journal processing has been terminated or why IAMRLS is shutting down. Call BMC for help in diagnosing this problem.

IAML0526

IAMDD ddname: GETMAIN1 FAILED, JOURNAL PROCESSING TERMINATED

Explanation: The journal exit, IAMJRNRL, could not obtain storage for a journal work area for IAMDD ddname.

System Action: Journaling for this DD is terminated. Make sure that the IAMRLS address space has enough region size specified at startup time.

IAML0527

IAMDD ddname: SAVEAREA GETMAIN FAILED, JOURNAL PROCESSING TERMINATED

Explanation: The journal exit, IAMJRNRL, could not obtain storage for a save area to schedule a journal request to the journal subtask.

System Action: Journaling for this DD is terminated. Make sure that the IAMRLS address space has enough region size specified at startup time.

IAML0528

IAMDD ddname: IXGWRITE FAILED, RC= nn ,RSNCD= nnnnn

Explanation: The journal exit has received a failing return code from the System Logger during a write operation. This message will only appear once for every 30 errors to aid so the console will not be flooded with messages.

System Action: RSNCD=00000860 indicates that an offload is needed, which should be automatically handled by the system. If it is not, one can use the IAM/PLEX command to offload the logger (F Iiamplex1,LOGGER,OFFLOAD). When the offload has completed message IAML0612 will come out and the logger processing will continue. For other codes call BMC for help in diagnosing this problem. You can use the IAMPLEX LOGGER commands to disconnect from the current logger, then define a new one, update the IAM/PLEX parameters, and start connect the new logger data set.

IAML0529

IAMDD ddname: JOURNAL UPDATE FAILED

Explanation: The journal subtasks work area could not be found to schedule a journal request for IAMDD ddname.

System Action: The journal request is not scheduled and the journal entry is lost. Contact BMC for help in diagnosing this error.

IAML0530

IAMDD ddname: JOURNAL PROCESSING TERMINATED, JOURNAL ENTRIES LOST.

• 
  
  • ====

Explanation: There is a problem with the journal buffer queue and a journal entry has not been able to be written.

System Action: Check the RLSLOGDD and JESLOG for other messages indicating the source of the journaling problem. Call BMC for help in diagnosing this error.

IAML0531

IAMDD ddname: IXGWRITES FAILING, JOURNAL PROCESSING TERMINATED

Explanation: The journal exit is receiving failing return codes from the System Logger. Journal processing is terminated.

System Action: Call BMC for help in diagnosing this problem.

IAML0533

IAMBJRNL INITIALIZATION OF JOURNAL FILES FAILED, IAMRLS WILL QUIESCE.

Explanation: The journal subtask was unable to initialize any of the journal data sets provided in the IAMRLS parmlib.

System Action: Make sure the data set names provided in the IAMRLS parmlib are correct, that the data sets exist on DASD and have available space.

IAML0534

READY DSN dsname, THEN REPLY 'U', OR REPLY 'Q' TO TERMINATE IAMRLS

Explanation: The next journal data set was not empty during a switch operation.

System Action: Empty data set dsname, then reply 'U' to continue journal processing, or reply 'Q' to terminate the IAMRLS address space.

IAML0535

ONLY 1 JOURNAL DATASET WAS PROVIDED, REPLY 'U' TO REUSE THE SAME DATASET, OR REPLY 'Q' TO TERMINATE IAMRLS.

Explanation: The single journal data set has been filled. IAMRLS needs operator response to start reusing the data set in order to preserve the data. All I/O requests that need to be journaled will be delayed until a response is provided.

System Action: Copy off the data from the journal data set, then reply U to continue processing. Consider adding additional journal data sets to the IAMRLS region so that delays such as this can be eliminated.

IAML0536

OFFLOAD PROCESSING FOR LOGSTREAM nnnnnnnn.nnnnnn COMPLETED, RC=xxxx, RSN=xxxx

Explanation: The requested offload process for the logstream journal has completed with the indicated return and reason codes.

System Action: None if the return code is 0. If the return code is other than 0, determine the cause of the problem. Contact BMC support if assistance is needed.

IAML0537

IAML0538

IAMJRNRL VALIDATION OF IAMRLS OCQ FAILED, JOURNALING IS TERMINATED

Explanation: The IAM/RLS Journaling Exit module obtained the address of the Job's OCQ from the ACB, but the OCQ eye-catcher validation failed.

System Action: Set a MSGID Slip trap for IAML0538 and reproduce the problem. Open a support issue and supply the dump.

IAML0551

IAMSYNC STORAGE OBTAIN FAILED, NO SYNCPOINT RECORD WRITTEN

Explanation: IAMSYNC was unable to obtain storage for a work area and will not be able to write the syncpoint record for the batch program that called it.

System Action: Make sure the batch job has sufficient region size to satisfy the storage request.

IAML0552

IAML0561

IAMASPT UNABLE TO LOAD IEANTRT, NO SYNCPOINT RECORD WRITTEN

Explanation: IAMASPT was unable to load the IBM module IEANTRT to perform name token services. Without this module IAMASPT cannot write a syncpoint record.

System Action: Make sure that IBM's common services library, SYS1.CSSLIB, is in the LINKLIST or that programs have access to it.

IAML0562

IAMASPT RECEIVED RETURN CODE nnn FROM TOKEN SERVICES, NO SYNCPOINT RECORD WRITTEN

Explanation: IAMASPT was unable to retrieve the Global Token Area for the IAMRLS address space and cannot perform SYNCPOINT services.

System Action: Check to see that IAMRLS is active, if not start it and restart the job. If it is active, call BMC for help in diagnosing this problem.

IAML0563

IAML0564

IAML0565

IAMASPT FOUND IAM RLS MARKED AS INACTIVE IN THE GLOBAL TOKEN Area, NO SYNCPOINT RECORD WRITTEN

Explanation: IAMRLS has been marked as inactive and no syncpoint services are available.

System Action: Determine why the IAMRLS address space is inactive and if possible, restart IAM RLS then restart the batch job.

IAML0566

IAMASPT FOUND IAM RLS MARKED AS QUIESCE FORCE IN THE GLOBAL TOKEN, NO SYNCPOINT RECORD WRITTEN

Explanation: A QUIESCE,FORCE condition exists in the IAMRLS address space and it is longer accepting requests.

System Action: Determine why the IAMRLS address space has been quiesced.

IAML0567

IAMASPT RECEIVED ETURN CODE nnn FROM THE RLS JOURNAL CALL, NO SYNCPOINT RECORD WRITTEN

Explanation: The syncpoint writer in RLS encountered an error.

System Action: Check this job log and the RLS job log for other error messages and Contact BMC for assistance.

IAML0571

IAMBSYNC UNABLE TO OBTAIN STORAGE; NO SYNCPOINT WRITTEN

Explanation: IAMBSYNC was unable to obtain storage for a work area, the syncpoint record could not be written.

System Action: Make sure the job has a large enough region size when started to accommodate all of the storage required.

IAML0572

IAMBSYNC FOUND JOURNAL-IN-TROUBLE FLAG ON IN THE IWA, NO SYNCPOINT WRITTEN

Explanation: The journal subtask has set a bit in the IWA indicating that initialization failed or that journaling is not active. The syncpoint record cannot be written.

System Action: Browse the RLSLOGDD and JESLOG for additional messages to determine why the journal subtask is not active.

IAML0573

IAMBSYNC FOUND AN ADDRESS OF ZERO IN THE GLOBAL TOKEN FOR THE JOURNAL'S TWA, NO SYNCPOINT WRITTEN

Explanation: There was no task work area for the journal subtask in the Global Token Area. The subtask has either failed or was not activated.

System Action: Browse the RLSLOGDD and JESLOG for additional messages to determine why the journal subtask has failed or is not active.

IAML0574

IAMBSYNC FOUND JOURNAL FULL BIT ON AFTER WAITING FOR THE JOURNAL WRITE, NO SYNCPOINT WRITTEN

Explanation: There is a problem with the journal output buffers, the syncpoint record cannot be written.

System Action: Call BMC for help in diagnosing this problem.

IAML0575

IAMBSYNC IXGWRITE FAILED; RC=nn, RSNCD=nnnn, NO SYNCPOINT RECORD WRITTEN

Explanation: IAMBSYNC attempted to write a syncpoint record to the System Logger, and the write failed with the indicated return and reason codes.

System Action: Browse the RLSLOGDD and JESLOG for additional messages that might indicate why the System Logger Connection is not working. call BMC for help in diagnosing this problem.

IAML0576

IAMBSYNC'S CALL TO RELEASE THE LOCKS HELD BY THIS JOB FAILED

Explanation: A call to release the record locks held by this job has failed.

System Action: Call BMC for help in diagnosing this problem.

IAML0577

IAMBSYNC FOUND AN INVALID OCQ IN THE PARAMETER LIST, OCQ BYPASSED

Explanation: The batch syncpoint process encountered an invalid pointer to an expected open data set. Processing will continue with the next open data set for this job, if any.

System Action: Contact BMC support.

IAML0578

IAMBSYNC IXCMSGO MESSAGE NOT ACCEPTED SYNCPOINT NOT COMPLETED

Explanation: The attempt by a router IAM/PLEX to send an request to a target IAM/PLEX for syncpoint processing has failed.

System Action: Contact BMC support.

IAML0579

IAMBSYNC IXCMSGO RESPONSE MESSAGE NOT ACCEPTED SYNCPOINT NOT COMPLETED

Explanation: The target IAM/PLEX address space failed notifying the router IAM/PLEX that it had completed syncpoint processing.

System Action: Contact BMC support.

IAML0580

IAMBSYNC'S CALL TO FIND THE OID FOR THIS JOB FAILED

Explanation: Syncpoint processing attempted to find the control information for the job that issued the syncpoint, but was unable to do so.

System Action: Contact BMC support.

IAML0581

IAMBIJNL UNABLE TO OBTAIN STORAGE, NO BATCH JOURNAL PROCESSING WILL TAKE PLACE

Explanation: The batch journal task was unable to obtain storage and no batch journal processing can happen.

System Action: Restart IAM RLS with more storage.

IAML0582

IAMBIJNL FOUND JOURNAL-IN-TROUBLE FLAG ON IN THE TWA; NO JOURNAL RECORD WRITTEN

Explanation: The batch journal task was found an unexpected flag value and cannot proceed.

System Action: Dump the IAM RLS address space and contact BMC.

IAML0583

IAMBIJNL FOUND A ZERO ADDRESS IN THE GLOBAL TOKEN FOR THE JOURNAL''S TWA, NO JOURNAL WRITTEN

Explanation: The batch journal task cannot process without a valid address for the journal task's work area.

System Action: Dump the IAM RLS address space and Contact BMC.

IAML0584

IAMBIJNL FOUND JOURNAL FULL BIT ON AFTER WAITING FOR JOURNAL WRITE, NO JOURNAL RECORD WRITTEN

Explanation: The batch journal task has encountered a journal full condition after waiting for the journal task.

System Action: Dump the IAM RLS address space and contact BMC.

IAML0585

IAMBIJNL IXGWRITE FAILED; RC=.., RSNCD=........, NO JOURNAL RECORD WRITTEN

Explanation: The batch journal task has received a non-zero return code from the system log write.

System Action: Dump the IAM RLS address space and contact BMC.

IAML0600

IAMBSYNC IXGWRITE FAILED, RC=, RSncd=, WILL WAIT FOR RETRY

Explanation: IAMBSYNC attempted to write a syncpoint record to the SYSTEM LOGGER and the write failed with the specified return and reason codes. The write will be retried after the SYSTEM LOGGER indicates the condition is resolved.

System Action: None. Should see the IAML0601 message after retry.

IAML0601

IAMBSYNC IXGWRITE REISSUED AFTER LOGGER RECOVERY.

Explanation: IAMBSYNC was notified of a SYSTEM LOGGER recovery and the failed write of the syncpoint record was reissued.

System Action: None.

IAML0602

IAMBSYNC CALLED FOR CICS SYNCPOINT

Explanation: IAMBSYNC was called for a CICS syncpoint.

System Action: None.

IAML0603

IAMBSYNC CALLED FOR EXTERNAL CICS SYNCPOINT

Explanation: IAMBSYNC was called for an external CICS syncpoint.

System Action: None.

IAML0604

IAMBJNRP DISCONNECTED FROM LOGSTREAM: logstream

Explanation: IAMBJRNL has disconnected from the logstream named.

System Action: None.

IAML0605

IXGWRITE OF INIT RECORD FAILED, RC= ,RSNCD=

Explanation: IAMBJRNL attempted to write an initialization record to the logstream and the write failed with the specified codes.

System Action: Contact BMC for support.

IAML0606

LOGGER COMMAND COULD NOT BE PROCESSED

Explanation: The LOGGER command was issued but the System Logger is not being used in this RLS or PLEX region. The command is ignored.

System Action: None.

IAML0607

LOGGER COMMAND MISSING COMMAND PARM

Explanation: The LOGGER command was issued without a DISCON, RECON, POST, or OFFL parameter. The command is ignored.

System Action: Reissue the command with the appropriate parameter.

IAML0608

OPEN FILES HAVE BEEN DETECTED, REPLY 'Y' TO FORCE SHUTDOWN, OR REPLY 'W' TO WAIT FOR FILES TO CLOSE

Explanation: A QUIESCE command was issued but there are still some open files.

System Action: Reply with 'Y' to force shutdown of the region or reply 'W' to wait for the files to close.

IAML0609

IAMZAPR COULD NOT BE LOADED

Explanation: An APPLY command was issued but module IAMZAPR could not be loaded.

System Action: Contact BMC for support.

IAML0610

IAMZAPR COULD NOT BE LOADED

Explanation: A RESTORE command was issued but module IAMZAPR could not be loaded.

System Action: Contact BMC for support.

IAML0611

NO OTHER MEMBERS HAVE CONNECTED TO THIS GROUP

Explanation: A Display Group command was issued, and no other members are connected to this RLSGROUP.

System Action: None.

IAML0612

BJRNL SRB POSTED BJRNL FOR RECOVERY AFTER WRITE ERROR

Explanation: An offload or other recovery operation has been completed by the SYSTEM LOGGER on the logstream used by this RLS and the BJRN,L task has been posted to retry any writes that may have failed during the recovery operation.

System Action: None.

IAML1000

IAML1001

IAML1002

IAML1003

IAML1004

IAML1005

IAML1006

IAML1007

IAML1008

IAML1009

IAML1010

IAML1011

IAML1012

IAML1013

IAML1014

IAML1015

IAML1016

IAML1017

IAML1020

IAML1021

IAML1022

IAML1023

IAML1024

IAML1025

IAML1026

IAML1027

IAML1029

IAML1030

IAML1031

IAML1032

IAML1033

IAML1034

IAML1035

IAML1036

IAML1037

IAML1038

IAML1039

IAML1040

IAML1041

IAML1042

IAML1043

IAML1044

IAML1045

IAML1050

IAML1051

IAML1052

IAML1053

IAML1054

IAML1055

IAML1060

IAML1061

IAML1062

IAML1063

IAML1064

IAML1065

IAML1066

IAML1067

IAML1068