Audit log messages (CBKxx8500-8999)

The messages described in this section are written to the CICS BAC audit log by the CICS® request server, or by the batch request utility if it services a command directly because the target CICS region is not available. Expressions such as "written by CICS BAC" , or similar, are used generically in the message explanations to mean either one of these two components. The DD name for the audit log is CBKLOG.

The CICS region and the batch request utility job step dynamically allocate the audit log, based on the audit log attributes in the CICS region properties. You can define, view, or alter the audit log attributes using the workstation administration client, opening the Region Properties window and selecting the Miscellaneous options tab.

CBKxx8501I
date time Start: CICS=applid
By={STARTUP|CICSSVR|BATCH} jobname stepname procname jobnumber sysid
By=CICSSPI jobname userid termid transid
Explanation:

CICS BAC is performing one of the following actions:

By=STARTUP
CICS BAC is starting in a CICS region. The CICS BAC startup procedure identifies the CICS region by jobname, stepname, procname, and jobnumber, and it also displays the MVS™ sysid.
By=CICSSVR
The CICS BAC request server is processing a batch utility request. The CICS BAC request server identifies the batch request utility by its jobname, stepname, procname, and jobnumber, and it also displays the MVS sysid.
BY=BATCH
The CICS BAC batch request utility is servicing a command, or set of commands, itself because CICS BAC is not active in the target CICS region. The CICS BAC batch request utility identifies itself by its jobname, stepname, procname, jobnumber, and it also displays the MVS sysid.
BY=CICSSPI
The CICS BAC state monitor within the CICS region has detected a change to a CICS resource. The CICS BAC state monitor identifies the the task responsible for the change by its userid, termid, and transid.

In all the above cases, the CICS BAC component displays the date and time of the request.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8503I
seqnum LIST {START|END} listname O=openstatus E=enablestatus DSN={PRIMARY|ALTERNATE}
Explanation:

CICS BAC has started processing, or has finished processing, a CICS BAC application list. listname shows the name of the application list being processed, and openstatus, enablestatus, and DSN show the values specified by the command.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8504I
seqnum GROUP {START|END} groupname O=openstatus E=enablestatus DSN={PRIMARY|ALTERNATE}
Explanation:

CICS BAC has started processing, or has finished processing, a CICS BAC application group. groupname shows the name of the application group being processed, and openstatus, enablestatus, and DSN show the values specified by the command.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8505I
seqnum FILE {BEFORE|REQUESTED|AFTER} filename O=openstatus E=enablestatusA=addstatus U=updatestatus D=deletestatus R=readstatus B=browsestatus T=processtransids P=processprograms disp dsn
Explanation:

CICS BAC is processing a file state change request. A CBKxx8505I message can be written up to three times for each request, depending on the specific processing that takes place:

BEFORE
CICS BAC writes a BEFORE record for each request.
REQUESTED|AFTER
If the request is serviced successfully, CICS BAC follows the before state record by a REQUESTED record and an AFTER record. If CICS BAC does not write a REQUESTED or AFTER record to the log, it writes other records to explain why the request was not serviced

A file record in a CICS BAC control file can specify transactions and programs that are to be processed when a file request is being processed by a batch request utility command. If the file record does specify transactions and programs to be processed, the audit log can contain transaction ID and program name audit log records between the BEFORE and AFTER file audit log records, depending on the state changes requested.

seqnum is the command sequence number relative to one if the request is performed by the CICS BAC batch request utility. For all other cases, such as a CICS SPI request, seqnum is zero.

The various status fields (openstatus, enablestatus, and so on) contain various values depending on the type of record written (BEFORE, REQUESTED, or AFTER), and where the request is serviced (CICS BAC request server or CICS BAC batch request utility).

For BEFORE and AFTER log records, a question mark (?) status value means that CICS BAC does not know the status of the file at the time of the request. For example, if a batch request utility command is used to process a file newly defined to CICS BAC while the CICS region that owns the file is not active, CICS BAC is not able to determine the current status of the file. BEFORE and AFTER log records do not contain the processtransids or processprograms status indicators.

For REQUESTED log records, a blank status value means that the resource state change request did not attempt to change that particular state value.

The variables in the message text can have the following values:

Variable
Possible values (and meanings)
openstatus
O (open) or C (closed)
enablestatus
E (enabled), D (disabled), or U (unenabled)
addstatus
Y (addable) or N (not addable)
updatestatus
Y (updatable) or N (not updatable)
deletestatus
Y (deletable) or N (not deletable)
readstatus
Y (readable) or N (not readable)
browsestatus
Y (browsable) or N (not browsable)
processtransids
Y (associated transaction IDs are processed) or
N (associated transaction IDs are not processed)
(REQUESTED records only)
processprograms
Y (associated programs are processed) or
N (associated programs are not processed)
(REQUESTED records only)
disp
SHR, OLD, or blank (the disposition of the file)
dsn
The name of the data set associated with the file, or blank
System action:

None

User response:

None

Destination:

Audit log

CBKxx8506I
seqnum TDQUEUE {BEFORE|REQUESTED|AFTER} tdqname O=openstatus E=enablestatus T=processtransids P=processprograms
Explanation:

CICS BAC is processing a transient data queue state change request. A CBKxx8506I message can be written up to three times for each request, depending on the specific processing that takes place.

BEFORE
CICS BAC writes a BEFORE record for each request.
REQUESTED|AFTER
If the request is serviced successfully, CICS BAC follows the before state record by a REQUESTED record and an AFTER record. If CICS BAC does not write a REQUESTED or AFTER record to the log, it writes other records to explain why the request was not serviced

seqnum is the command sequence number relative to one if the request is performed by the CICS BAC batch request utility. For all other cases, such as a CICS SPI request, seqnum is zero.

The status fields openstatus and enablestatus contain various values depending on the type of record written (BEFORE, REQUESTED, or AFTER), and where the request is serviced (CICS BAC request server or CICS BAC batch request utility).

For BEFORE and AFTER log records, a question mark (?) status value means that CICS BAC does not know the status of the transient data queue at the time of the request. For example, if a batch request utility command is used to process a transient data queue newly defined to CICS BAC while the CICS region that owns the transient data queue is not active, CICS BAC is not able to determine the current status of the queue. BEFORE and AFTER log records do not contain the processtransids or processprograms status indicators.

For REQUESTED log records, a blank status value means that the resource state change request did not attempt to change that particular state value

The variables in the message text can have the following values:

Variable
Possible values (and meanings)
openstatus
O (open) or C (closed)
enablestatus
E (enabled), D (disabled), or U (unenabled)
processtransids
Y (associated transaction IDs are processed) or
N (associated transaction IDs are not processed)
(REQUESTED records only)
processprograms
Y (associated programs are processed) or
N (associated programs are not processed)
(REQUESTED records only)
System action:

None

User response:

None

Destination:

Audit log

CBKxx8507I
seqnum TRANSID {BEFORE|REQUESTED|AFTER} transid E=enablestatus
Explanation:

CICS BAC is processing a transaction ID state change request. A CBKxx8507I message can be written up to three times for each request, depending on the specific processing that takes place.

BEFORE
CICS BAC writes a BEFORE record for each request.
REQUESTED|AFTER
If the request is serviced successfully, CICS BAC follows the before state record by a REQUESTED record and an AFTER record. If CICS BAC does not write a REQUESTED or AFTER record to the log, it writes other records to explain why the request was not serviced

seqnum is the command sequence number relative to one if the request is performed by the CICS BAC batch request utility. For all other cases, such as a CICS SPI request, seqnum is zero.

The enablestatus field contains various values depending on the type of record written (BEFORE, REQUESTED, or AFTER), and where the request is serviced (CICS BAC request server or CICS BAC request utility).

For BEFORE log records, a question mark (?) status value means that CICS BAC does not know the status of the transaction ID at the time of the request. For example, if a batch request utility command is used to process a transaction ID newly defined to CICS BAC while the CICS region that owns the transaction ID is not active, CICS BAC is not able to determine the current status of the transaction ID.

Where the status is known, the value can be an E (enabled) or D (disabled).

System action:

None

User response:

None

Destination:

Audit log

CBKxx8508I
seqnum PROGRAM {BEFORE|REQUESTED|AFTER} program E=enablestatus
Explanation:

CICS BAC is processing a program state change request. A CBKxx8508I message can be written up to three times for each request, depending on the specific processing that takes place.

BEFORE
CICS BAC writes a BEFORE record for each request.
REQUESTED|AFTER
If the request is serviced successfully, CICS BAC follows the before state record by a REQUESTED record and an AFTER record. If CICS BAC does not write a REQUESTED or AFTER record to the log, it writes other records to explain why the request was not serviced

seqnum is the command sequence number relative to one if the request is performed by the CICS BAC batch request utility. For all other cases, such as a CICS SPI request, seqnum is zero.

For all types of record (BEFORE, REQUESTED, and AFTER) the enablestatus variable can be either E or D indicating that the program is either enabled or disabled. For BEFORE record types only, an enable status shown as a question mark (?) means that CICS BAC does not know the status of the program at the time of the request. For example, if a batch request utility command is used to process a program newly defined to CICS BAC while the CICS region that owns the program is not active, CICS BAC is not able to determine the current status of the transaction ID.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8511I
seqnum resourcetype resourcename State not changed due to CICSSTARTMODE=UPDATE requested
Explanation:

CICS BAC is being started in the CICS region with CICSSTARTMODE parameter specified with a value of UPDATE.

With a start mode of UPDATE, CICS BAC does not set the state of any CICS resources. It does, however, update the resource records defined in the CICS BAC control file with the current state of the resource specified by resourcetype and resourcename.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8512I
seqnum resourcetype resourcename State not changed because requested state is unknown.
Explanation:

During CICS BAC startup processing in a CICS region, CICS BAC has read a resource record where the last requested status of the resource is unknown. CICS BAC is unable to set the state of the resource.

This situation can occur if you add a resource object record to a CICS BAC region control file while the CICS region is not available. In this situation, CICS BAC is unable to determine the last state of the object.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8513I
seqnum resourcetype resourcename already at requested state. No state changes necessary
Explanation:

CICS BAC has received a request to change the state of a resource, but the resource is already at the requested state. CICS BAC leaves the state of the resource unchanged.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8514I
seqnum FILE filename Can't change DSN. File permanently allocated. Req DSN=datasetname
Explanation:

The CICS BAC request server is processing a batch request utility command that specifies, either by the NEWDSN or DSN parameter, a change of data set name for file filename. However, filename is defined in the CICS region startup JCL and allocated to the CICS job my MVS, thus CICS BAC cannot change the data set name. You can change the name of a data set only when CICS files are dynamically allocated by CICS, and not when they are allocated by MVS during job step initiation.

This condition can also occur during CICS BAC startup processing if a request to change the data set name was processed directly in the CICS region control file, by the batch request utility, while the target CICS region was not available. The name change request is then detected during the next execution of CICS BAC startup processing. At this point, the CICS BAC startup processor can find that the name change is not allowed, and reject the request, as described above for the CICS BAC request server.

System action:

If this occurs as a result of a batch request utility command, the batch request utility job step terminates. If it occurs during CICS BAC startup processing, the data set name is not changed, and startup processing continues.

User response:

If this occurs as a result of a batch request utility command, correct the command and rerun the job step.

Destination:

Audit log

CBKxx8515I
seqnum resourcetype resourcename not processed. Object not defined to CICS.
Explanation:

CICS BAC is processing a batch request utility command that specifies a resource (resourcetype and resourcename) that is not defined to CICS.

CICS BAC also writes this audit log message if, during CICS BAC startup processing, it finds that the control file contains a resource that is not defined in the CICS region.

System action:

If CICS BAC writes this log record as a result of processing a batch request utility command, the batch request utility job step terminates with return code 12.

If CICS BAC writes this log record during CICS BAC startup processing, startup processing continues.

User response:

If CICS BAC writes this audit log message as a result of a batch request utility command, correct the command and rerun the job step.

Destination:

Audit log

CBKxx8516E
seqnum resourcetype resourcename Invalid attributes on control file: O=openstatus E=enablestatus A=addstatus U=updatestatus D=deletestatus R=readstatus B=browsestatus DISP=disposition.
Explanation:

During CICS BAC startup processing in the CICS region, one or more invalid status values have been detected in the control file record for the resource named by resourcename. openstatus, enablestatus, addstatus, updatestatus , deletestatus, readstatus, browsestatus, and disposition give the hexadecimal value(s) of the status field(s) in error. A blank status field value means the value is not in error, or it is not relevant for the type of resource being processed. For example, the only relevant status field for programs and transaction ID's is enablestatus.

System action:

CICS BAC does not change the status of the object. Startup processing continues.

User response:

Contact technical support.

Destination:

Audit log

CBKxx8517I
seqnum FILE filename Forcing {PRIMARY|ALTERNATE} DSN: eibresp eibresp2 enablestatus datasetname
Explanation:

CICS BAC has detected that there is no data set name for a file it is about to open. Because of the NODSN parameter value specified when CICS BAC was started in the CICS region, CICS BAC sets the data set name for the file to either the primary or alternate data set name specified in the CICS BAC control file record for the file. eibresp and eibresp2 give the resulting EIBRESP and EIBESP2 values in hexadecimal format for the EXEC CICS SET FILE command that set the data set name. enablestatus is the hexadecimal representation of the value used for the ENABLE parameter when the EXEC CICS SET FILE command was issued. The meaning of the numeric values can be found in Appendix A of the CICS System Programming Reference. . datasetname is the data set name that CICS BAC set for the file.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8520I
seqnum resourcetype resourcename Record did not exist on control file but has been added.
Explanation:

CICS BAC has processed a batch request utility command that specifies a resource (resourcetype and resourcename) that is not defined in the CICS region control file. You have specified in the CICS region properties that unknown objects of this type are to be added to the control file.

System action:

CICS BAC adds a record for the object resourcetype and resourcename to the CICS region control file.

User response:

None

Destination:

Audit log

CBKxx8521I
seqnum resourcetype resourcename Record did not exist on control file. Record not added.
Explanation:

CICS BAC has processed a batch request utility command that specifies a resource (resourcetype and resourcename) that is not defined in the CICS region control file. You have specified in the CICS region properties that unknown objects of this type are to be processed but not added to the control file. CICS BAC has processed the command, but has not added a record for the resource to the control file.

System action:

The command is processed.

User response:

None

Destination:

Audit log

CBKxx8522I
seqnum resourcetype resourcename Record did not exist on control file. Command not processed.
Explanation:

CICS BAC has processed a batch request utility command that specifies a resource ( resourcetype resourcename) that is not defined in the CICS region control file. You have specified in the CICS region properties that unknown objects of this type are not to be processed.

System action:

CICS BAC does not add a record for the resource to the control file. Further action taken depends on the CICS BAC region properties for the CICS region. The command can be ignored, in which case processing continues with the next command. Alternatively, the batch request utility job step can terminate.

User response:

Correct the problem and resubmit the batch request utility job step.

Destination:

Audit log

CBKxx8528I
seqnum FILE filename File must be temporarily set to CLOSED/DISABLED to set to final requested state.
Explanation:

During its startup processing in the CICS region, CICS BAC has determined that a file must be closed and disabled before it can set the file to its last requested state. This is because the file is currently open and enabled, or open and disabled, or closed and enabled. Even though the last requested state might be open and enabled, or closed and enabled, it must still be set to closed and disabled first for the change to be made. For example, if CICS BAC needs to change one or more of the file access attributes (such as READ, UPDATE, and ADD), CICS requires that a file must be closed and disabled before these attributes can be changed. Note that this message can occur only during CICS BAC startup processing.

System action:

Processing continues. The file will be temporarily set to CLOSED DISABLED before setting to its last requested state.

User response:

None

Destination:

Audit log

CBKxx8529I
seqnum SET FILE(X'filename'), OPENSTATUS(openstatus), ENABLESTATUS(enablestatus)
Explanation:

CICS BAC displays the EXEC CICS SET FILE command issued by CICS BAC startup processing if a file must be temporarily closed or disabled to set it to its last requested state. filename provides the hexadecimal representation of the file name used for the SET FILE command. openstatus and enablestatus provide the OPENSTATUS and ENABLESTATUS values used for the SET FILE command. The meaning of the two numeric values can be found in Appendix A in the CICS System Programming Reference. For additional information on the circumstances that result in this message being displayed, see message CBKxx8528I.

System action:

Processing continues.

User response:

None

Destination:

Audit log

CBKxx8530I
seqnum resourcetype resourcename Objects of this type not allowed for this region. Object not processed.
Explanation:

CICS BAC has processed a batch request utility command that specifies a resource type that is not allowed for this region by the CICS BAC region properties defined in the CICS region control file.

System action:

CICS BAC action depends on the CICS BAC region properties for the CICS region. The command can be ignored, in which case processing continues with the next command. Alternatively, the batch request utility job step can terminate.

User response:

Correct the problem and resubmit the batch request utility job step.

Destination:

Audit log

CBKxx8532I
seqnum tdqname Open/close and enable/disable cannot be set for indirect transient data queue.
Explanation:

CICS BAC is attempting to process a batch request utility command that specifies one of the following actions for an indirect transient data queue.

You cannot use CICS BAC to open, close, enable, or disable indirect transient data queues.

System action:

Processing continues and CICS BAC processes any transaction IDs or programs associated with the transient data queue.

User response:

None

Destination:

Audit log

CBKxx8533I
seqnum tdqname Open/close cannot be set for intrapartition transient data queue.
Explanation:

CICS BAC is attempting to process a batch request utility command to open or close an intrapartition transient data queue. You cannot use CICS BAC to open or close intrapartition transient data queues.

System action:

Processing continues and CICS BAC processes any transaction IDs or programs associated with the transient data queue.

User response:

None

Destination:

Audit log

CBKxx8534I
seqnum tdqname Open/close cannot be set for remote transient data queue.
Explanation:

CICS BAC is attempting to process a batch request utility command to open or close a remote transient data queue. You cannot use CICS BAC to open or close a remote transient data queues.

System action:

Processing continues and CICS BAC processes any transaction IDs or programs associated with the transient data queue.

User response:

None

Destination:

Audit log

CBKxx8535I
seqnum {LINK|START|RUNCEMT} {transid | program} Requests of this type not allowed for this region. Request not processed.
Explanation:

CICS BAC has received a command that is not allowed in this CICS region. The message includes either the transid or the program message variable, depending on the type of command, as follows:

System action:

CICS BAC rejects the command. Further action taken depends on the CICS BAC region properties for the CICS region. The command can be ignored, in which case processing continues with the next command. Alternatively, the batch request utility job step can terminate.

User response:

Correct the problem and resubmit the batch request utility job step.

Destination:

Audit log

CBKxx8536I
seqnum filename State changes cannot be performed for a remote file. Processing continues.
Explanation:

CICS BAC is attempting to process a batch request utility command to change the state of a remote file. You cannot use CICS BAC to change the state of remote files.

System action:

Processing continues and CICS BAC processes any transaction IDs or programs associated with the named file.

User response:

None

Destination:

Audit log

CBKxx8538E
seqnum filename RLS file state change(s) not allowed based on CICS BAC control file setting. Processing terminated.
Explanation:

CICS BAC has received a request from the CICS BAC batch request utility to change the state of a file defined as using record level sharing (RLS). The RLS option for this file is set to terminate or abend such requests.

System action:

Processing is terminated for the batch request utility job step. The job step is either terminated immediately or abended depending on the settings for the target file.

User response:

Determine whether or not this action is appropriate for your environment. Change the associated CICS BAC settings if a different CICS BAC action is required.

Destination:

Audit log

CBKxx8539I
seqnum filename RLS file in quiescing state. Waiting two seconds for state to stabilize.
Explanation:

CICS BAC is attempting to change the quiesce status for the data set associated with filename. The data set is currently in the quiescing transient state. CICS BAC must wait for the state to change from quiescing to some other state before it can process the request. After two seconds, CICS BAC checks the data set state again. It continues to do this until the data set state is no longer quiescing, or it has waited thirty times (approximately one minute).

System action:

If the data set state changes to something other than quiescing, CICS BAC continues to process the batch request utility request. If after waiting for two seconds thirty times, the data set quiesce state is still quiescing, the batch request utility job step is terminated with a condition code of twelve.

User response:

If the batch request utility job step is terminated because the data set quiesce state remained quiescing for too long, determine why the data set is in that state. If necessary, ensure that the state has changed from quiescing and rerun the batch request utility job step.

Destination:

Audit log

CBKxx8540I
seqnum {LINK|START|RUNCEMT} {transid | program} CICS region not active. {LINK|START|RUNCEMT} request ignored. Processing continues.
Explanation:

The CICS BAC batch request utility is trying to process a LINK, START, or RUNCEMT command at a time when it is processing requests directly because CICS BAC is not active in the target CICS region, or because the CICS region is not running. Because it cannot pass the command to the target CICS region, it cannot process commands of the type LINK, START, and RUNCEMT.

System action:

The command is ignored and because the NOTACTIVE parameter specifies CONTINUE, batch request utility processing continues with the next command.

User response:

None

Destination:

Audit log

CBKxx8541I
seqnum {LINK|START|RUNCEMT} {transid | program} CICS region not active. Job step will be terminated: RC=12
Explanation:

The CICS BAC batch request utility is trying to process a LINK, START, or RUNCEMT command at a time when it is processing requests directly because CICS BAC is not active in the target CICS region, or because the CICS region is not running. Because it cannot pass the command to the target CICS region, CICS BAC cannot process commands of the type LINK, START, and RUNCEMT.

System action:

The command is ignored and because the NOTACTIVE parameter specifies TERMINATE, the batch request utility terminates.

User response:

None

Destination:

Audit log

CBKxx8542E
seqnum filename OPEN requested for migrated RLS data set or RLS not supported. Processing terminated.
Explanation:

CICS BAC is attempting to process a file that is defined to CICS as using record level sharing (RLS). Either the data set associated with the file has been migrated, or RLS processing in the CICS region is not allowed (by the CICS SIT RLS parameter).

System action:

If the request is for CICS BAC startup processing, the file state is not changed and processing continues with the next object. If the request originated from the CICS BAC batch request utility, the batch request utility job step is immediately terminated with a condition code of twelve.

User response:

Call technical support if the cause of this problem cannot be determined and corrected.

Destination:

Audit log

CBKxx8543E
seqnum filename Data set exceeded quiescing state time limit. Processing terminated.
Explanation:

CICS BAC has exceeded its time limit for waiting for a data set to change from the quiescing state. See message CBKxx8539I for more information. This message is issued only when the file is defined in CICS as using record level sharing.

System action:

If the request is for CICS BAC startup processing, the file's state is not changed and processing continues with the next object. If the request originated from the CICS BAC batch request utility, the batch request utility job step is immediately terminated with a condition code of twelve.

User response:

If you cannot determine the cause of this problem and correct it, call technical support.

Destination:

Audit log

CBKxx8550I
seqnum resourcetype resourcename EXCLUDED: Action={Terminate|Abend} {AC|CC}=code
Explanation:

The target resource of a CICS BAC batch request utility command is defined as excluded in the CICS region control file. The resource type is resourcetype and resource name is resourcename.

System action:

If the resource is defined as EXCLUDE and TERMINATE, or EXCLUDE and ABEND, CICS BAC either terminates with termination code (CC) or abends with the abend code (AC) as defined.

User response:

None

Destination:

Audit log

CBKxx8551I
seqnum resourcetype resourcename set as excluded in CICS BAC control file.
Explanation:

During startup processing in the CICS region, CICS BAC has detected a resource that is defined as excluded in the CICS region control file. The resource type and resource name are resourcetype and resourcename.

System action:

The state of the resource is not changed, even if the CICS BAC control file contains a requested state different from the current state of the resource.

User response:

None

Destination:

Audit log

CBKxx8560I
seqnum resourcetype {BEFORE|REQUESTED|AFTER} filename RLS data set detected: Quiesce state={Q|U} DSN=dataset
Explanation:

CICS BAC has detected that a batch request utility command is attempting to open or close a file that is defined to CICS as RLSACCESS(YES). In order to process the command, CICS BAC might have to change the quiesce state of the data set associated with the file. The data set name associated with the file is dataset. The various quiesce states, given as Q (for quiesce) or U (for unquiese), are indicated by the message as follows:

System action:

None

User response:

None

Destination:

Audit log

CBKxx8561I
seqnum resourcetype filename Data set already at requested quiesce state: dataset
Explanation:

CICS BAC has determined that a data set dataset associated with a target file filename is defined as RLSACCESS(YES) and is currently at the quiesce state necessary for CICS BAC to perform the open or close request against the target file.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8562E
seqnum FILE filename RLS {INQUIRE|SET} error detected: EIBRESP=eibresp EIBRESP2=eibresp2
Explanation:

While processing an RLS data set, a failure has occurred in CICS BAC on an EXEC CICS INQUIRE DSNAME or an EXEC CICS SET DSNAME command. The CICS EIBRESP eibresp and EIBRESP2 eibresp2 values indicate the cause of the error. For an explanation of these CICS SPI error codes, see the System Programming Reference.

System action:

Processing for the command terminates and CICS BAC does not process any further commands from the batch request utility. The batch request utility job step is terminated with return code 12.

User response:

Contact technical support if you cannot determine the reason for the failure and correct it.

Destination:

Audit log

CBKxx8570I
seqnum {LINK|START|RUNCEMT} {transid | program} termid starting
Explanation:

The CICS BAC request server is about to process a LINK, START, or RUNCEMT command. The message includes the transid, program, or termid message variable, depending on the type of command, as follows:

System action:

None

User response:

None

Destination:

Audit log

CBKxx8579I
seqnum {LINK|START|RUNCEMT} {transid | program} termid EIBRESP=eibresp EIBRESP2=eibresp2 CC=12
Explanation:

The CICS BAC request server is processing a LINK, START, or RUNCEMT command and CICS has returned an error. The message includes the transid, program, or termid message variables, depending on the type of command, as follows:

For LINK and RUNCEMT commands, eibresp and eibresp2 are the EIB response codes returned from the EXEC CICS LINK command. For START commands, eibresp and eibresp2 are the EIB response codes returned from the EXEC CICS START command.

System action:

The batch request utility job step terminates with return code 12

User response:

Correct the problem and rerun the batch request utility job step.

Destination:

Audit log

CBKxx8580I
seqnum SET FILE(X'filename'), OPENSTATUS(openstatus), ENABLESTATUS(enablestatus), DISPOSITION(disposition),
Explanation:

When CICS BAC issues an EXEC CICS SET FILE command during startup processing or while processing a batch request utility job step command, it writes this message to the CICS BAC audit log to document the command and the parameters used. filename is the hexadecimal representation of the name of the file for which the EXEC CICS SET FILE command is being issued. openstatus, enablestatus, and disposition are the values in decimal form for the parameters used with the command. The meaning of these values are given in Appendix A in the CICS System Programming Reference. This message is followed by message CBKxx8581I and, optionally, message CBKxx8582I to provide the remainder of the EXEC CICS SET FILE command parameter values.

System action:

Processing continues.

User response:

None

Destination:

Audit log

CBKxx8581I
seqnum ADD(addstatus), UPDATE(updatestatus), DELETE(deletestatus), READ(readstatus), BROWSE(browsestatus),
Explanation:

When CICS BAC issues an EXEC CICS SET FILE command during startup processing or while processing a batch request utility job step command, it writes this message following message CBKxx8580I to the CICS BAC audit log to document the command and the parameters used. addstatus, updatestatus, deletestatus, readstatus, and browsestatus are the values in decimal form for the parameters used with the command. The meaning of these values are given in Appendix A in the CICS System Programming Reference. This message can be followed by message CBKxx8582I.

System action:

Processing continues.

User response:

None

Destination:

Audit log

CBKxx8582I
seqnum DSNAME(X'datasetname')
Explanation:

When CICS BAC issues an EXEC CICS SET FILE command during startup processing or while processing a batch request utility job step command, and the command contains the DSNAME parameter, it writes this message following message CBKxx8581I to the CICS BAC audit log to document the data set name used with the command.datasetname contains the hexadecimal representation of the DSNAME parameter value.

System action:

Processing continues.

User response:

None

Destination:

Audit log

CBKxx8583I
seqnum SET DSNAME(X'datasetname')
Explanation:

CICS BAC writes this message CBKxx8583I to the CICS BAC audit log when CICS BAC issues an EXEC CICS SET DSNAME command to change the quiesce state of a data set associated with a file being processed by CICS BAC. This can occur during CICS BAC startup processing in the CICS region, or when CICS BAC is processing a CICS BAC batch request utility command in the CICS region.datasetname contains the hexadecimal representation of the DSNAME parameter value. This message is followed by message CBKxx8584I.

System action:

Processing continues.

User response:

None

Destination:

Audit log

CBKxx8584I
seqnum QUIESCESTATE(quiescestate)
Explanation:

This message CBKxx8584I follows message CBKxx8583I on the CICS BAC audit log when CICS BAC issues an EXEC CICS SET DSNAME command to change the quiesce state of a data set associated with a file being processed by CICS BAC. This can occur during CICS BAC startup processing in the CICS region, or when CICS BAC is processing a CICS BAC batch request utility command in the CICS region. quiescestate is the value in decimal form for the QUIESCESTATE parameter used with the command. The meaning of this value is given in Appendix A in the CICS System Programming Reference.

System action:

Processing continues.

User response:

None

Destination:

Audit log

CBKxx8585I
seqnum SET TDQUEUE(X'tdqname'), OPENSTATUS(openstatus), ENABLESTATUS(enablestatus)
Explanation:

CICS BAC writes message CBKxx8585I to the CICS BAC audit log when CICS BAC issues an EXEC CICS SET TDQUEUE command to change the state of a transient data queue. This can occur during CICS BAC startup processing in the CICS region, or when CICS BAC is processing a CICS BAC batch request utility command in the CICS region. tdqname contains the hexadecimal representation of the transient data queue name being processed. openstatus and enablestatus are the values in decimal form for the OPENSTATUS and ENABLESTATUS parameters, respectively, used with the command. The meaning of these values are given in Appendix A in the CICS System Programming Reference.

System action:

Processing continues.

User response:

None

Destination:

Audit log

CBKxx8586I
seqnum SET PROGRAM(X'programname'), STATUS(enablestatus)
Explanation:

CICS BAC writes message CBKxx8586I to the CICS BAC audit log when CICS BAC issues an EXEC CICS SET PROGRAM command to change the state of a program. This can occur during CICS BAC startup processing in the CICS region, or when CICS BAC is processing a CICS BAC batch request utility command in the CICS region. programname contains the hexadecimal representation of the program name being processed. enablestatus is the value in decimal form for the STATUS parameter used with the command. The meaning of this value is given in Appendix A in the CICS System Programming Reference.

System action:

Processing continues.

User response:

None

Destination:

Audit log

CBKxx8587I
seqnum SET TRANSACTION(X'transid'), STATUS(enablestatus)
Explanation:

CICS BAC writes message CBKxx8587I to the CICS BAC audit log when CICS BAC issues an EXEC CICS SET transaction command to change the state of a transaction ID. This can occur during CICS BAC startup processing in the CICS region, or when CICS BAC is processing a CICS BAC batch request utility command in the CICS region. transid contains the hexadecimal representation of the transaction ID being processed. enablestatus is the value in decimal form for the STATUS parameter used with the command. The meaning of this value is given in Appendix A in the CICS System Programming Reference.

System action:

Processing continues.

User response:

None

Destination:

Audit log

CBKxx8599I
date time Start: CICS=applid
By={STARTUP|CICSSVR|BATCH} jobname stepname procname jobnumber sysid
By={CICSSPI|LINKAPI} jobname userid termid transid
{CC=completioncode | AC=abendcode}
Explanation:

CICS BAC is performing one of the following actions:

By=STARTUP
CICS BAC is starting in a CICS region. The CICS BAC startup procedure identifies the CICS region by jobname, stepname, procname, and jobnumber, and it also displays the MVS sysid.
By=CICSSVR
The CICS BAC request server is processing a batch utility request. The CICS BAC request server identifies the batch request utility by its jobname, stepname, procname, and jobnumber, and it also displays the MVS sysid.
BY=BATCH
The CICS BAC batch request utility is servicing a command, or set of commands, itself because CICS BAC is not active in the target CICS region. The CICS BAC batch request utility identifies itself by its jobname, stepname, procname, jobnumber, and it also displays the MVS sysid. The CICS BAC batch request utility also includes the final completioncode (or the abendcode in the case of an abend).
BY=CICSSPI
The CICS BAC state monitor within the CICS region has detected a change to a CICS resource. The CICS BAC state monitor identifies the the task responsible for the change by its userid, termid, and transid. The CICS BAC state monitor also includes the final completioncode.
BY=LINKXPI
The CICS BAC request server is being driven by a CICS application program through the CICS BAC callable API. The CICS BAC request server identifies the task responsible for the request by its userid, termid, and transid. The CICS BAC request server also includes the final completioncode .

In all the above cases, the CICS BAC component displays the date and time of the request.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8600I
date time CICS BAC region startup in progress: mode={Set|Update} tran=transid term=termid user=userid
Explanation:

CICS BAC startup processing is beginning in the CICS region. The type of startup is designated by the mode value as follows:

Set
CICS BAC sets the state of all CICS resources on defined in the CICS BAC region control file to their last known states.
Update
CICS BAC does not set resource states, but it updates the resource records in the CICS BAC as necessary to reflect the state of the resources.
System action:

None

User response:

None

Destination:

Audit log

CBKxx8699I
date time CICS BAC region shutdown in progress: tran=transid term=termid user=userid
Explanation:

CICS BAC is shutting down in the CICS region. The log record includes the transaction ID, terminal ID, and user ID (transid, termid, and userid) associated with the shutdown request. If the shutdown is taking place as a result of CICS going through shutdown PLT processing, the transaction ID is CPLT, the terminal id is blank, and the user ID is the default user ID for the CICS region.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8701I
Calling pre-command user exit: exitpgmname.
Explanation:

CICS BAC is linking to the pre-command user exit program exitpgmname.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8702E
Error linking to {pre-command|post-command} user exit: exit=exitpgmname RESP=eibresp RESP2=eibresp2
Explanation:

CICS BAC has detected an error when linking to the user exit program exitpgmname . The errors reported by CICS from the EXEC CICS LINK request are EIBRESP eibresp and EIBRESP2 eibresp2.

System action:

The batch request utility job step terminates immediately with return code 12.

User response:

Contact technical support if you cannot determine the reason for the failure and correct it.

Destination:

Audit log

CBKxx8707E
{Pre-command|Post-command} GETMAIN for XPI area failed: RESP=eibresp RESP2=eibresp2 length=stglength
Explanation:

CICS BAC has detected an error when attempting to acquire storage for the commarea to be passed to the user exit program. The errors from the EXEC CICS GETMAIN request are EIBRESP eibresp and EIBRESP2 eibresp2 and the storage length requested in teh exit program is stglength.

System action:

The batch request utility job step terminates immediately with return code 12.

User response:

Contact technical support if you cannot determine the reason for the failure and correct it.

Destination:

Audit log

CBKxx8709I
Exit exitpgmname done: RC=returncode AC=abendcode CC=completioncode ET=errortext
Explanation:

CICS BAC has received a control back from the pre-command user exit program exitpgmname. returncode, abendcode, completioncode, and errortext contain the values returned by the user exit program.

System action:

The action taken depends on the value returned in returncode. Depending on the return code, processing could continue, the current command could be ignored, the job step could be terminated, or the job step could be abended.

User response:

None

Destination:

Audit log

CBKxx8711I
Calling post-command user exit: exitpgmname.
Explanation:

CICS BAC is linking to the post-command user exit program exitpgmname.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8719I
Exit exitpgmname done.
Explanation:

The post-command user exit program exitpgmname has returned control to CICS BAC.

System action:

None

User response:

None

Destination:

Audit log

CBKxx8990E
pgmname detected severe error. Diagnostic data follows. Check console for more information.
Explanation:

CICS BAC has detected a severe error during startup processing while processing a resource, such as a file or a transient data queue.

System action:

Processing terminates for the resource, and continues with the next resource on the CICS BAC control file. CBKxx8990E can be followed by one or more CBKxx8997E messages to provide additional diagnostic data.

User response:

Contact technical support if you cannot determine the reason for the error and correct it.

Destination:

Audit log

CBKxx8997E
pgmname resourcename errorcode
Explanation:

CBKxx8997E can follow message CBKxx8990E to provide additional diagnostic data when an error has been detected during CICS BAC startup processing in the CICS region.

System action:

Processing is terminated for the resource, and continues with the next resource on the CICS BAC control file. CBKxx8997E can be followed by one or more messages providing additional diagnostic data.

User response:

Contact technical support if the reason for the error cannot be determined and corrected.

Destination:

Audit log

CBKxx8998E
pgmname filename errorcode datasetname
Explanation:

CBKxx8998E can follow message CBKxx8990E to provide additional diagnostic data when an error has been detected during CICS BAC startup processing in the CICS region.

System action:

Processing is terminated for the resource, and continues with the next resource on the CICS BAC control file. CBKxx8998E can be followed by one or more messages providing additional diagnostic data.

User response:

Contact technical support if the reason for the error cannot be determined and corrected.

Destination:

Audit log

CBKxx8999E
pgmid resourcetype resourcename errorcode eibresp eibresp2 field1 field2 field3 field4 field5 field6 field7 field8
Explanation:

This message can follow message CBKxx8990E to provide additional diagnostic data when an error has been detected during CICS BAC startup processing in the CICS region.

System action:

Processing is terminated for the resource, and continues with the next resource on the CICS BAC control file.

User response:

Contact technical support if the reason for the error cannot be determined and corrected.

Destination:

Audit log