Warm Starting with multiple JES2 levels in a MAS
JES2 supports up to three consecutive releases of JES2 running in the same MAS. JES2 enforces this rule and ships service to down level releases to allow them to exist with the newer releases. Failure to apply this maintenance or trying to go outside the supported release will result in a $HASP710 message being issued to indicate the problem. $HASP710 indicates active members in the MAS are incompatible with the initializing member. See the z/OS JES2 Messages information for more information.
JES2 also supports a more liberal migration policy.
This migration policy covers going from one release of JES2 to a new
release with a warm start. IBM® guarantees that this migration
policy will span a minimum of 5 releases of
the operating systems. That is, the data generated by the JES2 provided
with release x of the operating system is compatible with the data
generated by the release of JES2 provided with release x-5 and release
x+5 of the operating system. This may include a release that cannot
coexist in a MAS. The requirements for migration are documented in
the z/OS V2R2 Migration for each release. Failure to abide by the migration requirements
can result in a $HASP446 message being issued. For more information
about $HASP446 see z/OS JES2 Messages.
Note: IBM supports
data compatibility for only supported releases. Data compatibility
is not guaranteed with unsupported releases.