IBM Support

CICS BAC 1.1.1 fails to start in region with CBKCM9001E 00000088 001B0001

Question & Answer


Question

Why is CICS Batch Application Control for z/OS (CICS BAC) V1.1.1 returning message CBKCM9001E Internal error: code1(00000088) code2(001B0001) data( ), and failing to start in one specific CICS Transaction Server for z/OS (CICS TS) region?

I have CICS TS sytem initialization table (SIT) INITPARM=(CBKCMNDS='CICSSTARTMODE(UPDATE),NODSN(PRIMARY) specified and PTF UI19084 for the CICS BAC CICS TS 5.2 toleration APAR PI17232 applied.

This is identical to regions that work. The IBM Knowledge Center documentation does not include an explanation for the error codes. I verified regions are using the same load library. Right now I cannot run batch commands to manage resources in this region.

Answer

It has something to do with not having the CBAC message table defined correctly in this region. The 001B and 0001 in "R0" are the halfword RESP and RESP2 values from an INQUIRE PROGRAM command.

CBAC supports two languages... ENU and JPN.

During startup, it does an EXEC CICS ASSIGN LANGINUSE to get the current language in use. From the results, it forms the program name to be used for the message table. It should be either CBKMTENU or CBKMTJPN.

Next, it does an EXEC CICS INQUIRE PROGRAM for the message table program name previously "formed". If it gets a PGMIDERR, and the program name was not CBKMTENU, it will try again using CBKMTENU instead of what was previously used. If CBKMTENU gets a PGMIDERR on the first or second INQUIRE command, it will return message CBKCM9001E with the internal error code1 00000088 and code2 001B0001.

So, my guess is that in this particular region, you do not have the CBKMTENU program defined (assuming the language is not Japanese) possibly due to the CBKGROUP not being completed installed.

If that does not resolve the problem, the easiest thing to do would be to start CBAC using transaction ID with CEDF or CEDX on the transaction. It gets to the ASSIGN LANGINUSE and INQUIRE PROGRAM commands pretty quickly. Make note of what those commands return and let me know.

The section entitled Host component NLS in CICS Batch Application Control for z/OS V1.1.1 documentation describes where CICS BAC determines the NLS language.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSWHM2","label":"CICS Batch Application Control for z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"Startup","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICSBAC CICS BAC;CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
31 August 2015

UID

dwa1208040