Handle changes to length of field EEPLEVENTSPECIFICINFO in control block IXLYEEPL

Description: In z/OS V1R13 the length of the field EEPLEVENTSPECIFICINFO in the XES Event Exit Parameter List (IXLYEEPL) is being increased by 8 bytes to include additional information for users to take advantage of the new function provided by greater-than 32 connectors. This additional information is mapped by EEPLSTRSTATECHANGEINFO. The following fields have been added to the EEPLSTRSTATECHANGEINFO mapping:

EEPLSSCSTRFACILITYUSERLIMIT
EEPLSSCSTRLOCKNUMUSERS

A program can determine if these fields are valid; therefore, you can use the longer length for EEPLEVENTSPECIFICINFO if the flag EEPLSSCUSERLIMITINFOVALID is set. This change was rolled back to earlier releases in the service stream through APAR OA34061.

Element or feature:

BCP

When change was introduced:

z/OS V2R1. z/OS V1R13 and z/OS V1R12 both with APAR OA34061.

Applies to migration from:

z/OS V1R12 without APAR OA34061 applied.

Timing:

Before the first IPL of z/OS V2R1.

Is the migration action required?

Yes, if any of your programs have relied on the length of the EEPLEVENTSPECIFICINFO field in IXLYEEPL.

Target system hardware requirements:

CFLEVEL 17 support for greater than 32 connectors for list or lock structures.

Target system software requirements:

None.

Other system (coexistence or fallback) requirements:

None.

Restrictions:

None.

System impacts:

None.

Related IBM Health Checker for z/OS check:

None.

Steps to take: Consider any program that makes use of the length field EEPLEVENTSPECIFICINFO in IXLYEEPL. If you rely on the length of field EEPLEVENTSPECIFICINFO, for example if its length is used to define local data areas in a module and if the length that the compiler uses will be the updated larger length, all modules using the length of the field need to be recompiled.

Reference information: z/OS V2R1 MVS Data Areas Volume 2 (DDRCOM -IEFALCXT)