Migration Considerations

When migrating from CA Spool Release 11, Release 11.5, or Release 11.6 to Release 11.7 consider the following:

The file queue has not been restructured.
CA Spool Release 11.7 can be warm started on your existing CA Spool Release 11, Release 11.5, or Release 11.6 spool and checkpoint configuration. In addition, should it become necessary to fall back from CA Spool Release 11.7 to CA Spool Release 11, Release 11.5, or Release 11.6 you can do this by simply warm starting the CA Spool Release 11.7 checkpoint and spool configuration on your CA Spool Release 11, Release 11.5, or Release 11.6 system.
CA Spool Release 11.7 members may coexist with CA Spool Release 11, Release 11.5, or Release 11.6 members in the same EMAS/MAS complex.
If CA Spool Release 11.7 and CA Spool Release 11.5 have to be started on the same MVS system, or as a member in the same EMAS/MAS complex with Release 11.5, we recommend that you install the CA Spool Release 11.5 fixes RO17296 and RO22958.
If CA Spool Release 11.7 and CA Spool Release 11 have to be started on the same MVS system, or as a member in the same EMAS/MAS complex with Release 11, we recommend that you install the CA Spool Release 11 fixes RO18777 and RO22970.

If you have files under control of any previous release, which must now be used with Release 11.7, do the following:

When migrating from any previous CA Spool release to Release 11.7 consider that:

Any application programs using pre-V8.0 interface routines (AESFPRIV) must be re-linked with the Release 11.7 interface routines.
All user exits have been renumbered in CA Spool Release 11.7. Source updates to exits in IEBUPDTE format must use these new numbers, so be sure to check the sequence numbers before applying the updates.