Facility Violations After Upgrading To CTS 5.1 From CTS 3.2

book

Article ID: 18135

calendar_today

Updated On:

Products

CA Cleanup CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Top Secret CA Top Secret - LDAP CA Top Secret - VSE

Issue/Introduction

Description:

Receiving the following ESM codes when upgrading some CICS CPSM regions to CTS 5.1 from CTS 3.2 .


+DFHUS0150 $CMPA  522                                                        
                                                                             
AN ATTEMPT TO ESTABLISH SECURITY HAS FAILED FOR USERID CPSMCMPB IN           
GROUP , NO TERMINAL,  APPLID $CMPA. UNABLE TO INITIALIZE THE                 
TRANSACTION XLST. SAF CODES ARE (X'00000008',X'00000000'). ESM CODES         
ARE (X'0000001C',X'00000000').                                               
+EYUTS0001I $CMPA TOPOLOGY DISCONNECT FOR CICSPP81 INITIATED - APPLID(CICSPP81
+EYUTS0003I $CMPA TOPOLOGY DISCONNECT FOR CICSPP81 COMPLETE - APPLID(CICSPP81)

TSSUTIL report shows a 1C-06 FACILITY security violation for the userid.

Per IBM:

PM79281/UK94164 made a change as to how CICS handles a session signons.

Many customers have been reporting the same to us after applying maintenance or upgrading releases. The same change was made to version 4 via PM67891/UK83851.

The maintenance forces a signon of the user within the CICS, which didn't occur previously. After the maintenance, users will need to be authorized to the CICS FACILITY they are signing on to.

Solution:

IBM now requires the user to have access to the CICS FACILITY.

TSS ADD(acid) FAC(facilityname) will authorize the user.

Please substitute 'acid' with the user's ACID and 'facilityname' with your CICS FACILITY name.

Environment

Release:
Component: AWAGNT