Reconnect subsystems
Description
If you use subsystems, you need to make them usable with the new system.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | Multiple. |
|---|---|
| When change was introduced: | General migration action that is 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 use CICS®, DB2®, IMS™, or NCP on your new system. |
| 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
Ensure that any required target system PTFs are installed before you use the subsystem with the new z/OS system. This work includes any required SVCs, system modifications, parmlib setup, and proclib setup. Follow the instructions for the subsystem that you need to reconnect.
Tip: The required IBM PTFs for z/OS V2R2 are identified with
the FIXCAT IBM.TargetSystem-RequiredService.z/OS.V2R2
Reference information
None.