CICS BAC communication server messages (CBKxx1000-1499)

The following messages are issued by the CICS BAC communication server:

CBKxx1001I
CICS Batch Application Control for z/OS communication server initialization starting.
Explanation:

The CICS® BAC communication server has begun its initialization process.

System action:

None.

User response:

None.

Destination:

Console

CBKxx1005I
cbkid CICS Batch Application Control for z/OS communication server initialization complete: MAB=address
Explanation:

The CICS BAC communication server has successfully completed its initialization process.

System action:

The communication server waits for command requests from the operator and for requests from a workstation administration client.

User response:

None.

Destination:

Console

CBKxx1015E
cbkid Empty or no control file table located. Communication server abending with abend code U1120.
Explanation:

An error has occurred while attempting to locate the control file table. Either it does not exist or the data set member does not contain any control file definitions.

System action:

The CICS BAC communication server abends with a U1120 abend code.

User response:

Add or update the PDS member that defines the control file table, then restart the communication server.

Destination:

Console

CBKxx1030E
Error detected in input parameter from parmloc. Processing terminating.
Explanation:

The communication server has detected an error in an input parameter. In the message text, parmloc specifies the location from which the parameter was read, and which can be one of the following values:

This message is preceded by a message giving the details of the parameter error.

System action:

The communication server terminates.

User response:

Correct the parameter error and restart the communication server.

Destination:

Console

CBKxx1050E
cbkid A server with this ID is already active. Initialization terminates.
Explanation:

Another communication server with the ID of cbkid is already active in another address space. A communication server ID cannot be active on more than one MVS image at a time.

System action:

The communication server address space that is trying to start with a duplicate ID terminates.

User response:

Check to see if the communication server which is already active is the same as the one being started. If so, use the one that is already active. If not, change the ID parameter for the communication server being started to give it a unique ID.

Destination:

Console

CBKxx1090E
Unable to load CICS EXCI module. CICS SDHEXCI load library may not be available: code1(retcode) code2(rsncode)
Explanation:

During startup processing, the communication server has attempted to load one of the required CICS EXCI modules to ensure the server has access to the load library. The load request has failed with the errors indicated by retcode and rsncode, which contain the contents of R15 and R1, respectively, as returned by the failed load attempt.

System action:

The communication server terminates.

User response:

Ensure the CICS SDFHEXCI load library is available to the communication server by placing it in the system linklist or in the communication server STEPLIB concatenation.

Destination:

Console

CBKxx1098I
cbkid CICS Batch Application Control for z/OS server shutdown processing starting.
Explanation:

The communication server cbkid has received a command to shut down. It has begun the process of shutting down its address space.

System action:

The communication server terminates.

User response:

None.

Destination:

Console

CBKxx1099I
cbkid CICS Batch Application Control for z/OS server shutdown complete.
Explanation:

The communication server cbkid has completed its process of shutting down.

System action:

The communication server terminates.

User response:

None

Destination:

Console

CBKxx1150W
ddname member member not found.
Explanation:

The member member cannot be found in the ddname data set. This member provides the communication parameter values, and without this member the communication server uses all default values.

System action:

Parameter processing continues without the indicated member.

User response:

If the parameters are specified elsewhere, or if the default parameter values are sufficient, no action is needed. Otherwise, add the indicated member to the data set, specifying the needed parameter values.

Destination:

Console

CBKxx1157W
Server startup will continue. Server parameters with errors will be ignored.
Explanation:

The communication server has accepted your reply GO to message CBKxx1156R. The communication server ignores the parameters with errors and continue its initialization process.

System action:

The communication server continues to initialize.

User response:

None.

Destination:

Console

CBKxx1200I
cbkid The following startup parameters are in effect for this CICS BAC communication server:
Explanation:

The communication server cbkid has received a DISPLAYPARMS command. After displaying this message, the server issues one or more CBKxx1201I messages, where each message text contains the current parameter value for a communication server parameter. Note that the communication server also issues this message automatically during startup processing to display the parameters that are in effect.

System action:

None.

User response:

None.

Destination:

Console

CBKxx1201I
cbkid loc parm
Explanation:

The communication server cbkid displays each parameter and its value pair parm immediately after it has displayed message CBKxx1200I. Each communication server parameter and its value is displayed in a separate CBKxx1201I message. The source loc from which the communication server obtained the parameter can be one of the following:

System action:

None.

User response:

None.

Destination:

Console

CBKxx1209I
cbkid End of CICS BAC communication server startup parameter list.
Explanation:

The communication server cbkid has finished displaying parameter and value pairs in response to a DISPLAYPARMS command (or during server initialization) and DISPLAYPARMS command processing is now complete.

System action:

The DISPLAYPARMS command is complete.

User response:

None.

Destination:

Console

CBKxx1300I
cbkid CICS Region=region, DSN=dsname.
Explanation:

The communication server cbkid has received a DISPLAYCFT command and responds with one CBKxx1300I message for each entry in its control file table, CBKCFTBL. Each message indicates the CICS region region and its CICS BAC control file data set name dsname .

System action:

None.

User response:

None.

Destination:

Console

CBKxx1301I
cbkid End of CICS control file data set name list.
Explanation:

The communication server cbkid has displayed, in one or more CBKxx1300I messages, all the entries in its control file table (CBKCFTBL) in response to a DISPLAYCFT command. The server has completed DISPLAYCFT command processing.

System action:

The DISPLAYCFT command is complete.

User response:

None.

Destination:

Console

CBKxx1401I
cbkid CICS control file table construction starting.
Explanation:

A CICS BAC component is initializing and is beginning the process of building its internal control file table using the statements in the CBKCFTBL parmlib member. It uses the entries in this member to associate a CICS region with its VSAM control file. The CICS BAC component can be the communication server, the batch request utility, or the file maintenance utility. If the message is issued by the communication server, cbkid identifies the server, but in the case of the batch request utility or the file maintenance utility, it is the job name under which the utility is executing.

System action:

None.

User response:

None.

Destination:

Console (if issued by the communication server) or the job log (if issued by one of the utilities).

CBKxx1404I
cbkid CBKPARMS member CBKCFTBL not found. Logical PARMLIB search will be attempted.
Explanation:

A CICS BAC component cannot find a control file table, CBKCFTBL, as a member of its CBKPARMS PDS. Either the member CBKCFTBL is not in the CBKPARMS PDS, or the CBKPARMS DD statement is missing from the component startup procedure.

The CICS BAC component can be the communication server, the batch request utility, or the file maintenance utility. If the message is issued by the communication server, cbkid identifies the server, but in the case of the batch request utility or the file maintenance utility, it is the job name under which the utility is executing.

System action:

The CICS BAC component attempts to locate a CBKCFTBL member in the MVS logical parmlib concatenation.

User response:

None.

Destination:

Console (if issued by the communication server) or the job log (if issued by one of the utilities).

CBKxx1405E
cbkid PARMLIB member CBKCFTBL not found.
Explanation:

The CICS BAC component cannot find a control file table member, CBKCFTBL, in the MVS logical parmlib concatenation. CICS BAC has already failed to find CBKCFTBL in its own CBKPARMS PDS, and because it must have a CBKCFTBL to function correctly, the CICS BAC component cannot continue its initialization. If the message is issued by the communication server, cbkid identifies the server, but in the case of the batch request utility or the file maintenance utility, it is the job name under which the utility is executing.

System action:

The CICS BAC component terminates.

User response:

Add a CBKCFTBL member to CICS BAC CBKPARMS PDS or to the MVS logical parmlib concatenation then restart the CICS BAC component.

Destination:

Console (if issued by the communication server) or the job log (if issued by one of the utilities).

CBKxx1406E
cbkid ddname member CBKCFTBL is empty.
Explanation:

A CICS BAC component has found a CBKCFTBL member located in either the CBKPARMS PDS or the MVS logical parmlib concatenation, but the member does not contain any control file table entries. ddname indicates where the empty CBKCFTBL member has been found-showing a value of CBKPARMS or PARMLIB, as appropriate.

Provide a CBKCFTBL that contains at least one valid CICS APPLID and data set name pair for the CICS BAC component to initialize successfully. See The control file table for information about the CBKCFTBL member and its definitions. If the message is issued by the communication server, cbkid identifies the server, but in the case of the batch request utility or the file maintenance utility, it is the job name under which the utility is executing.

System action:

The CICS BAC component terminates.

User response:

Update the indicated CBKCFTBL member to contain one or more valid control file entries, then restart the CICS BAC component.

Destination:

Console (if issued by the communication server) or the job log (if issued by one of the utilities).

CBKxx1409I
cbkid CICS control file table successfully built from ddname member. Number of entries: num.
Explanation:

A CICS BAC component has located the CICS control file table in the ddname DDNAME. From that CBKCFTBL table it has successfully built its own internal control file table that contains num entries. If the message is issued by the communication server, cbkid identifies the server, but in the case of the batch request utility or the file maintenance utility, it is the job name under which the utility is executing.

System action:

None.

User response:

None.

Destination:

Console (if issued by the communication server) or the job log (if issued by one of the utilities).

CBKxx1450E
cbkid DYNALLOC error detected: code1(code1) code2(code2) DSN(dsname) DDN(ddname).
Explanation:

The communication server cbkid has attempted to allocate dynamically the data set dsname with DD name ddname and an error has occurred. The server has received return code code1 and reason code code2.

System action:

The data set is not allocated.

User response:

Check for additional messages relating to this error, which should provide more information regarding the source of the problem. Take the corrective action indicated by these other messages. For information about the return and reason codes, see the z/OS® MVS Programming: Authorized Assembler Services Guide.

Destination:

Console