CICS BAC startup messages in CICS region (CBKxx4000 --4999)

The following messages are issued by the CICS BAC component running in the CICS® region.

CBKxx4001I
applid CICS Batch Application Control for z/OS Startup in progress via PLTPI entry.
Explanation:

The CICS component of CICS BAC is starting in CICS region applid during PLTPI processing of CBKCMNDS during CICS initialization.

System action:

CICS BAC is started in the CICS region.

User response:

None.

Destination:

Console

CBKxx4002I
applid CICS Batch Application Control for z/OS (5697-I94) version starting.
Explanation:

The CICS component of CICS BAC is beginning startup processing. The CICS BAC version number is shown as version in region applid.

System action:

None.

User response:

None.

Destination:

Console

CBKxx4003I
applid CICS Batch Application Control for z/OS started: TSQname(queuename) term/user(termid/userid).
Explanation:

The CICS component of CICS BAC has been successfully started in CICS region applid. The temporary storage control queue name is given by queuename. The termid/userid message variable is set as follows:

System action:

None.

User response:

None.

Destination:

Console

CBKxx4004E
applid Unable to process command. CICS Batch Application Control for z/OS is not active in this CICS region.
Explanation:

You have issued the CICS BAC command processor (KBKM) transaction with a command other than START, when CICS BAC is not active in CICS region applid. The only command that you can specify on KBKM when CICS BAC is not active is the START command.

System action:

The command is not processed.

User response:

Start CICS BAC and reenter the command as necessary.

Destination:

Console

CBKxx4005I
applid Dump request complete. Dumpcode: dumpcode.
Explanation:

You have issued the KBKM DUMP command requesting a CICS BAC dump. The dump has completed successfully in region applid, with the dump code identified by dumpcode.

System action:

None.

User response:

None.

Destination:

Console

CBKxx4006W
applid CICS Batch Application Control for z/OS is already started in this region.
Explanation:

A request to start the CICS BAC CICS component has been received, but CICS BAC is already active in CICS region applid.

System action:

The START request terminates.

User response:

None.

Destination:

Console

CBKxx4007W
applid CICS Batch Application Control for z/OS (5697-I94) is already shut down in this region.
Explanation:

You have issued a request to shut down CICS BAC in CICS region applid, but CICS BAC is not active in the region applid.

System action:

The SHUTDOWN request is rejected.

User response:

None.

Destination:

Console

CBKxx4008E
applid Input data is too long. Maximum 71 characters allowed.
Explanation:

You have issued in CICS region applid the CICS BAC KBKM command processor with an input string that is longer than seventy-one characters.

System action:

The request is rejected.

User response:

Correct the input string and retry the KBKM transaction.

Destination:

Console

CBKxx4010I
applid CICS Batch Application Control for z/OS SHUTDOWN via PLTSD started.
Explanation:

CICS BAC is shutting down in CICS region applid during CICS PLTSD processing. The CICS BAC command processor program, which performs shutdown, is driven by an entry in the PLTSD table.

System action:

Shutdown processing begins.

User response:

None.

Destination:

Console

CBKxx4011I
applid CICS Batch Application Control for z/OS SHUTDOWN requested by user userid from terminal termid.
Explanation:

You have issued the KBKM command processor transaction to shut down CICS BAC in CICS region applid. The command processor transaction KBKM was issued by user userid at terminal termid.

System action:

Shutdown processing continues.

User response:

None.

Destination:

Console

CBKxx4014E
applid CICS Batch Application Control for z/OS will not run on this version of CICS. START terminated.
Explanation:

You have tried to start CICS BAC in CICS region applid that is running a version of CICS not supported by CICS BAC.

System action:

The START request terminates.

User response:

Ensure that you are attempting to start CICS BAC in a CICS region that is running a supported version of CICS. If you are, contact technical support.

Destination:

Console

CBKxx4015E
applid Program ID error: Program(progname) code1(code1) code2(code2).
Explanation:

The CICS component of CICS BAC in region applid has received a CICS PGMIDERR error during its startup processing. The name of the program that resulted in the PGMIDERR is program and code1 and code2 are the EIBRESP and EIBRESP2 values respectively, returned with the PGMIDERR.

System action:

The START request is terminated.

User response:

This can be caused by a missing or incorrect program definition. It can also be caused by the module being missing. Determine the cause of the problem, correct it, and retry the CICS BAC START command.

Destination:

Console

CBKxx4016E
applid CICS Batch Application Control for z/OS START request terminated due to subtask initialization failure. See job log for more information.
Explanation:

An unrecoverable error has occurred in the CICS BAC request server subtask during CICS BAC region startup processing in CICS region applid.

System action:

The START request terminates.

User response:

Check the CICS region job log for additional messages describing the error. Correct the problem and retry the START request. If you cannot correct the problem, contact technical support.

Destination:

Console

CBKxx4017E
applid Error detected during CICS BAC startup. See job log for error information. CICS BAC start request terminated.
Explanation:

An unrecoverable error has occurred during CICS BAC startup processing in CICS region applid. CICS BAC writes additional error messages to the CICS job log.

System action:

The START request is terminated.

User response:

Correct the problem and retry the START request. If you cannot correct the problem, contact technical support.

Destination:

Console

CBKxx4019I
applid CICS Batch Application Control for z/OS SHUTDOWN complete.
Explanation:

CICS BAC has successfully shut down in CICS region applid .

System action:

None.

User response:

None.

Destination:

Console

CBKxx4030I
applid The following CICS BAC parameters will be used for this CICS region.
Explanation:

The CICS component of CICS BAC is starting in region applid and during its startup processing, CICS BAC displays the parameters that it will use in CICS region applid. CBKxx4030I is followed by several instances of message CBKxx4031I to display the parameters.

System action:

CICS BAC startup processing continues.

User response:

None.

Destination:

Console

CBKxx4031I
applid location parmameter=value
Explanation:

CICS BAC displays one CBKxx4031I message for each CICS BAC region startup parameter in region applid . location can be either CICS or Default. If location is CICS, you specified the parameter as part of the command input string. If location is Default, you did not specify the parameter explicitly as part of the command input string, and CICS BAC is using the default value. parameter is the parameter name and value is the value that CICS BAC is to use.

System action:

CICS BAC startup continues in the CICS region.

User response:

None.

Destination:

Console

CBKxx4032I
applid End of CICS BAC CICS region startup parameter list.
Explanation:

CICS BAC has finished listing its startup parameters for CICS region applid.

System action:

CICS BAC startup continues in the CICS region.

User response:

None.

Destination:

Console

CBKxx4060E
applid Error rewriting region properties record during startup: DDN=ddname RESP=eibresp RESP2=eibresp2.
Explanation:

An error has occurred during CICS BAC startup processing in CICS region applid when CICS BAC was rewriting the CICS region properties record to the CICS BAC control file . The CICS BAC control file name is ddname. The error codes eibresp and eibresp2 are the EIBRESP and EIBRESP2 values returned by CICS in response to the rewrite request.

System action:

If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, the START request terminates. If you are using PLTPI processing to start CICS BAC, CBKxx4060E is followed by message CBKxx4080R. See the explanation of message CBKxx4080R for more information.

User response:

If you are using PLTPI processing to start CICS BAC, reply to message CBKxx4080R. If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, correct the problem and retry the START request. If you cannot resolve the problem, contact technical support.

Destination:

Console

CBKxx4070E
applid Error closing control file during startup. CICS BAC start request terminated. DDN=ddname RESP=eibresp RESP2=eibresp2.
Explanation:

An error has occurred during CICS BAC startup processing in CICS region applid when CICS BAC was closing its control file. The CICS BAC control file name is ddname. The error codes eibresp and eibresp2 are the EIBRESP and EIBRESP2 values returned by CICS in response to the close request.

System action:

If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, the START request terminates. If you are using PLTPI processing to start CICS BAC, CBKxx4070E is followed by message CBKxx4080R. See the explanation of message CBKxx4080R for more information.

User response:

If you are using PLTPI processing to start CICS BAC, reply to message CBKxx4080R. If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, correct the problem and retry the START request. If you cannot resolve the problem, contact technical support.

Destination:

Console

CBKxx4071E
applid Error opening control file during startup. CICS BAC start request terminated. DDN=ddname RESP=eibresp RESP2=eibresp2.
Explanation:

An error has occurred during CICS BAC startup processing in CICS region applid when CICS BAC was opening its control file for the region. The CICS BAC control file name is ddname. The error codes eibresp and eibresp2 are the EIBRESP and EIBRESP2 values returned by CICS in response to the open request.

System action:

If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, the START request terminates. If you are using PLTPI processing to start CICS BAC, CBKxx4071E is followed by message CBKxx4080R. See the explanation of message CBKxx4080R for more information.

User response:

If you are using PLTPI processing to start CICS BAC, reply to message CBKxx4080R. If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, correct the problem and retry the START request. If you cannot resolve the problem, contact technical support.

Destination:

Console

CBKxx4072E
applid Error checking control file state during startup. CICS BAC start request terminated. DDN=ddname RESP=eibresp RESP2=eibresp2.
Explanation:

An error has occurred during CICS BAC startup processing in CICS region applid when CICS BAC was checking the state of its control file. The CICS BAC control file name is ddname. The error codes eibresp and eibresp2 are the EIBRESP and EIBRESP2 values returned by CICS in response to the inquire request.

System action:

If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, the START request terminates. If you are using PLTPI processing to start CICS BAC, CBKxx4072E is followed by message CBKxx4080R. See the explanation of message CBKxx4080R for more information.

User response:

If you are using PLTPI processing to start CICS BAC, reply to message CBKxx4080R. If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, correct the problem and retry the START request. If you cannot resolve the problem, contact technical support.

Destination:

Console

CBKxx4073E
applid Invalid control file state after open. CICS BAC start request terminated. DDN=ddname state name=state-name state value=state-value.
Explanation:

An error has occurred during CICS BAC startup processing in CICS region applid when CICS BAC was checking its control file attributes. The CICS BAC control file name is ddname. state-name is the name of the attribute that is not correct; state-value is the current value of the state for the control file. See Appendix A of the CICS System Programming Reference for possible values of state-value.

System action:

If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, the START request terminates. If you are using PLTPI processing to start CICS BAC, CBKxx4073E is followed by message CBKxx4080R. See the explanation of message CBKxx4080R for more information.

User response:

If you are using PLTPI processing to start CICS BAC, reply to message CBKxx4080R. If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, correct the problem and retry the START request. If you cannot resolve the problem, contact technical support.

Destination:

Console

CBKxx4074E
applid object-type object record not found during startup processing. CICS BAC start request terminated.
Explanation:

CICS BAC cannot find one of the required records in its control file during CICS BAC startup processing in CICS region applid. The message variable object-type can be one of the following values:

System action:

If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, the START request terminates. If you are using PLTPI processing to start CICS BAC, CBKxx4074E is followed by message CBKxx4080R. See the explanation of message CBKxx4080R for more information.

User response:

If you are using PLTPI processing to start CICS BAC, reply to message CBKxx4080R. If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, correct the problem and retry the START request. Note this problem can occur because you have not initialized the CICS BAC control file. If this is the case, run the CICS BAC control file initialization program to initialize the file and then retry the START request. If you cannot resolve the problem, contact technical support.

Destination:

Console

CBKxx4075E
applid Error reading object-type object record during startup processing. CICS BAC start request terminated. DDN=ddname RESP=eibresp RESP2=eibresp2.
Explanation:

CICS BAC has encountered an error while was reading one of the required records from its control file during CICS BAC startup processing in CICS region applid. The message variable object-type can be one of the following values:

The error codes eibresp and eibresp2 are the EIBRESP and EIBRESP2 values returned by CICS in response to the READ request. The CICS BAC control file name is ddname. eibresp and eibresp2 give the EIBRESP and EIBRESP2 values from the read request.

System action:

If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, the START request terminates. If you are using PLTPI processing to start CICS BAC, CBKxx4075E is followed by message CBKxx4080R. See the explanation of message CBKxx4080R for more information.

User response:

If you are using PLTPI processing to start CICS BAC, reply to message CBKxx4080R. This error can be caused by a corrupt CICS BAC control file. If you cannot find the cause of the problem, contact technical support.

Destination:

Console

CBKxx4076W
applidUnable to change DSN for JCL allocated file ddname. Current DSN=current-dsn Requested DSN=requested-dsn
Explanation:

During startup processing in CICS region applid, CICS BAC has determined that it should change the data set name associated with a CICS file. However, the data set is permanently allocated to the region because it is defined in the CICS region startup JCL. The data set associated with a file cannot be changed if the file is defined in the JCL. The name of the file being processed is ddname. current-dsn and requested-dsn are the current and requested data set name for the file.

System action:

The data set name for the file is not changed. Startup processing continues.

User response:

Determine whether or not the data set specified by current-dsn should be allocated to the CICS file. If not, make the change by some means other than through a CICS BAC command.

Destination:

Console

CBKxx4078E
applid Incorrect record length for object-type object record. CICS BAC start request terminated. Record length=reclen.
Explanation:

During CICS BACstartup processing in CICS region applid, CICS BAC has read from its control file a required record that has an incorrect record length. The message variable object-type can be one of the following values:

The CICS BAC control file name is ddname, and reclen is the length of the object record that CICS BAC read.

System action:

If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, the START request terminates. If you are using PLTPI processing to start CICS BAC, CBKxx4078E is followed by message CBKxx4080R. See the explanation of message CBKxx4080R for more information.

User response:

If you are using PLTPI processing to start CICS BAC, reply to message CBKxx4080R. This error can indicate a corrupt CICS BAC control file. Contact technical support.

Destination:

Console

CBKxx4079E
applid Incorrect control file version record detected: region=cics-version file=file-version DSN=dsn
Explanation:

During CICS BACstartup processing in CICS region applid, CICS BAC has detected an incompatibility between the version of the product and the CICS BAC control file. cics-version is the version of the CICS BAC product running in the CICS region. file-version specifies the version of the CICS BAC control file. dsn is the data set name of the CICS BAC control file.

System action:

If you are using the CICS BAC command processor transaction, KBKM, to start CICS BAC, the START request terminates. If you are using PLTPI processing to start CICS BAC, CBKxx4079E is followed by message CBKxx4080R. See the explanation of message CBKxx4080R for more information.

User response:

If you are using PLTPI processing to start CICS BAC, reply to message CBKxx4080R. If you cannot determine the cause of the incompatibility, contact technical support.

Destination:

Console

CBKxx4080R
applid Reply GO to continue without CICS BAC or CANCEL to cancel the CICS region.
Explanation:

CICS BAC is waiting in region applid for a reply of GO or CANCEL, because of an unrecoverable error detected during CICS BAC startup during CICS PLTPI processing. The error is reported by an earlier error message. If you reply GO, CICS region startup processing continues, but CICS BAC is not started in the region. If you reply CANCEL, the CICS region abends.

System action:

The CICS BAC startup processing waits for an operator reply to the WTOR.

User response:

This message is preceded by one or more CICS BAC messages that describe the error condition. Reply to message CBKxx4080R with a GO or CANCEL. If you cannot determine and resolve the cause of the problem, contact technical support.

Destination:

Console

CBKxx4081W
applid Region startup will continue without CICS BAC support.
Explanation:

The CICS BAC startup processor has received a GO reply to message CBKxx4080R or message CBKxx4086R.

System action:

CICS startup processing continues, but CICS BAC is not active in the region.

User response:

None.

Destination:

Console

CBKxx4082E
applid Region will be abended with abend code abend-code.
Explanation:

The CICS BAC startup processor has received a CANCEL reply to message CBKxx4080R or message CBKxx4086R.

System action:

CICS BAC abnormally terminates CICS region applid with abend code abend-code.

User response:

If you cannot determine and correct the cause of the problem, contact technical support.

Destination:

Console

CBKxx4083E
applid Error detected during CICS BAC startup processing. Startup terminated. Check system console for additional messages.
Explanation:

CICS BAC has been started in CICS region applid by the CICS BAC command processor transaction, KBKM. An unrecoverable error has occurred in the startup processor, causing startup processing to be terminated.

System action:

CICS BAC startup processing in the CICS region terminates.

User response:

Check the system console or CICS job log for additional messages describing the error condition. If you cannot determine and correct the cause of the problem, contact technical support.

Destination:

3270 terminal that issued the START command

CBKxx4084W
applid Unable to obtain CICS BAC region control file enqueue. Startup terminated.
Explanation:

CICS BAC has been started in CICS region applid by the CICS BAC command processor transaction, KBKM. However, CICS BAC cannot obtain a systems-level enqueue on its region control file. CICS BAC requires this to ensure that it has exclusive control of the CICS BAC region control file. CICS BAC has tried to obtain the enqueue thirty times, at one second intervals, and has now abandoned the attempt.

System action:

CICS BAC terminates the START request.

User response:

The enqueue can be held by either a batch request utility job step, or a communication server address space. If you cannot determine and correct the cause of the condition, contact technical support.

Destination:

3270 terminal that issued the START command

CBKxx4085W
applid Unable to obtain CICS BAC region control file enqueue.
Explanation:

CICS BAC has been started in CICS region applid during PLTPI processing. However, CICS BAC cannot obtain a systems-level enqueue on its region control file. CICS BAC requires this to ensure that it has exclusive control of the CICS BAC region control file. CICS BAC has tried to obtain the enqueue thirty times, at one second intervals, and follows CBKxx4085W with message CBKxx4086R.

System action:

CICS BAC prompts for an operator response to the error with message xx4086R.

User response:

See message CBKxx4086R

Destination:

Console

CBKxx4086R
applid Reply RETRY, GO to continue without CICS BAC, or CANCEL to cancel the CICS region.
Explanation:

CICS BAC has issued message CBKxx4085W and now wants a reply to this RETRY, GO, or CANCEL prompt.

System action:

The CICS region waits for an operator reply.

User response:

Reply RETRY if you want CICS BAC to continue trying to obtain the enqueue. Reply GO if you want the CICS region to continue startup processing without CICS BAC. Reply CANCEL to terminate the CICS region.

Destination:

Console

CBKxx4087I
applid Response was RETRY. CICS BAC will try to obtain enqueue again.
Explanation:

CICS BAC has received an operator reply of RETRY to message CBKxx4086R.

System action:

CICS BAC makes thirty more attempts to obtain its control file enqueue, at one second intervals.

User response:

None

Destination:

Console

CBKxx4088W
Incorrect final state for resourcetype resourcename: resourcestate. CICS BAC startup processing continuing.
Explanation:

CICS BAC has attempted to set a resource state during startup processing in the CICS region. The resource type and state are given by resourcetype resourcename. Immediately after setting the resource state, CICS BAC performs an inquiry of the resource state to determine whether or not the resource is at the requested state. As a result, CICS BAC has found that the resource is not at the state requested by CICS BAC for at least one state attribute. The first state discrepancy detected by CICS BAC is given by resourcestate. CICS BAC does not check to see if there is more than one discrepancy for a resource.

System action:

Startup processing continues. CICS BAC does not attempt to correct the incorrect resource state that it found.

User response:

Check the CICS BAC audit log for detailed information on what state changes CICS BAC attempted for the named resource and what the results of the request were. If the final state is not acceptable, change the resource state using some other method, for example, the CICS CEMT transaction.

Destination:

Console

CBKxx4092W
applid Error detected while processing resourcetype: resourcename errorcode1 errorcode2 errordata. See CICS BAC audit log for more information.
Explanation:

CICS BAC has detected an error during its startup processing in the CICS region. Various types of diagnostic data are provided in the message. Additional diagnostic data might also have been written to the CICS BAC audit log.

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 you cannot determine the reason for the error and correct it.

Destination:

Audit log

CBKxx4093W
applid errorcount errors detected during CICS BAC startup processing for resourcetype. See audit log for more information.
Explanation:

In CICS region applid, CICS BAC has detected one or more errors (errorcount) during CICS BAC region startup processing for resource type resourcetype.

System action:

Processing continues.

User response:

Contact technical support if you cannot determine the reason for the errors and correct them.

Destination:

Audit log

CBKxx4700I
applid CICS request handler subtask initialization starting.
Explanation:

The CICS BAC request handler subtask is being started in CICS region applid.

System action:

CICS BAC startup processing continues in the CICS region.

User response:

None.

Destination:

Console

CBKxx4701I
applid CICS request handler subtask initialization complete. Now accepting requests.
Explanation:

The CICS BAC request handler subtask has completed its initialization processing in CICS region applid and is ready to begin accepting requests from a CICS BAC batch request utility and communication server.

System action:

CICS BAC startup processing continues in the CICS region.

User response:

None.

Destination:

Console

CBKxx4702I
applid CICS request handler shutting down. Batch utility requests no longer accepted.
Explanation:

The CICS BAC request handler subtask running in CICS region applid has received a shutdown request. It no longer accepts requests from a CICS BAC batch request utility or communication server.

System action:

CICS BAC shutdown processing continues.

User response:

None.

Destination:

Console

CBKxx4707E
applid CICS request handler unable to dynamically allocate control file. Request handler terminating.
Explanation:

During startup processing in CICS region applid, the CICS BAC request handler subtask has detected an unrecoverable error when attempting dynamically to allocate the CICS BAC control file for the region. Additional messages describing the error can be displayed before this message.

System action:

CICS BAC startup processing in the CICS region terminates.

User response:

If you cannot determine and correct cause of the problem, contact technical support

Destination:

Console