Review changes applicable to JES2 exits
Description
In z/OS V2R2, exit changes might be necessary, depending on which exits you are using and which JES2 data areas those exits are referencing.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | z/OS JES2. |
|---|---|
| When change was introduced: | General migration action not tied to a specific release. |
| Applies to migration from: | z/OS V2R1 and z/OS V1R13. |
| Timing: | Before the first IPL of z/OS V2R2. |
| Is the migration action required? | Yes, if you have any affected JES2 exits. |
| Target system hardware requirements: | None. |
| 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
See the "JES2 z/OS V2R1 migration details" section of z/OS MVS Setting Up a Sysplex. This section details the changed information which you might need to accommodate. Generally, assembly errors in JES2 exits indicate that you were affected by a JES2 data area change.
Reference information
For more information, see z/OS MVS Setting Up a Sysplex.