We added a new auth byte (LIDUFLGW) to be used for CICS regions. When the CICS region started, it got an ACFAE189 UNABLE TO LOCATE CFDE FOR LID FIELD CICSTEST IN ACF2 FDR. What's causing the message?

Products

• ACF2
• ACF2 - DB2 Option
• ACF2 for zVM
• ACF2 - z/OS
• ACF2 - MISC
• PanApt
• PanAudit

Issue/Introduction

Question:  

We added a new auth byte (LIDUFLGW) to be used for CICS regions. When the CICS region started, it got an ACFAE189 UNABLE TO LOCATE CFDE FOR LID FIELD CICSTEST IN ACF2 FDR. What's causing the message?

Answer: 

The @MLID macro specifies a set of logonid record field names. CA ACF2 uses 

these logonid record fields to create a minilogonid record, also called an 

MLID or mini-LID. The MLID is used in the same fashion as the ACMCB; each MLID 

contains the minimum number of logonid record fields that CA ACF2 needs to 

validate access requests and still provide full CA ACF2 security controls.

 

If you add fields to the CICS @MLID, you must update the MLACICS DSECT in 

CAI.CAIMAC to reflect the new fields.

 

The @MUSASS defined for a CICS region in the ACFFDR specifies an @MLID. The new 

LIDUFLG6 field must be included in the @MLID definition for the CICS region.  It 

may be necessary to define a new @MLID that specifies (LIDUFLGW,MLACAUTH) and 

then specify that @MLID in the @MUSASS for this region.

 

Environment

Release:
Component: ACF2MS

Resolution

-