Question & Answer
Why does command BBOC START_SRVR fail with "The registration with the Liberty profile server was not successful. The return code is 12, and the reason code 16."? I am attempting to start z/OS Connect Enterprise Edition (EE) V2.0.1 for the first time with UI38699. I am not sure what more I should do and need assistance getting my z/OS Connect EE server started.
I have the updated z/OS File System (zFS) as well as the LOADLIB populated from wlp/clients/zos. I have also restarted the CICS region with the updated LOADLIB code. As far as I know, I should have all the updated code.
With the WebSphere Liberty Profile (WLP) started, I enter my BBOC START_SRVR command:
BBOC START_SRVR RGN=ZCONNREG DGN=ZPET NDN=ZCONNECT SVN=CICS SVC=* MNC=1 MXC=10 TXN=N SEC=N REU=Y
The registration with the Liberty profile server consistently fails with the RC 12 and RSN 16.
The BBOATRUE module in my LOADLIB shows compile dates of 2/22/2016. Response to the F WSANGEL,VERSION command is CWWKB0053I ANGEL VERSION 3
z/OS Connect messages.log showed message:
CWWKB0104I: Authorized service group SAFCRED is not available.
User found the cause to be the security configuration for the client server access to BBG.AUTHMOD.BBGZSCFM was lost. After adding it back the RC12 RSN16 no longer occurred and the WOLA registration in CICS was successful.
See Configuring the Liberty Angel process and z/OS authorized services in the z/OS Connect Enterprise Edition documentation for more details on the security requirements.
Since you are not getting the complete message that contains the message ID, I would like to recommend that you take a look at the solution to the dW Answers post: Error: Could not open WOLA message catalog wola_cics_messages.cat.
CICS/TS CICSTS CICS TS CICS Transaction Server;zCEE
21 September 2016