After upgrading ACF2 from r15 to r16 the user defined fields in the CICS MINILID are at different locations, what has changed to cause this?
Article ID: 12510
Updated On:
Products
Issue/Introduction
After upgrading ACF2 from r15 to r16 the user defined fields in the CICS MINILID are at different locations, what has changed to cause this?
Environment
Component: ACF2MS
Resolution
The r16 ACF2 CICS MLAREC dsect is X'10' larger than the r15 MLAREC desct due to the r16 two new 8 byte fields MLATODA2 and MLAPSWA2, for PASSWORD SET TOD (AES256) and PASSWORD IN AES256 FORMAT fields respectively. Since the CICS MLID(dsect MLACICS) is located AFTER the ACF2 MLID(MLAREC), a user program that is checking specific offsets within the MINILID for the user defined fields in the CICS MLID(dsect MLACICS) will find that the fields are offset by X'10'. When a user program does MINILID mapping, sites should use the appropriate dsect field MLAUOFF located in the MLAREC dsect to find the start of their user MLID definition rather than using hard-coded offsets.
Feedback
