Verify your IFAPRDxx Product ID is correct for z/OS Version 2
Description
Because z/OS has changed from Version 1 (V1) to Version 2 (V2), the IFAPRDxx parmlib member Product ID should reflect the new program number for z/OS. The Version, Release, and Modification values also found in IFAPRDxx should be specified as "*", so those values do not have to change; only the Product ID is affected by this change.
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: | z/OS V2R1. |
Applies to migration from: | z/OS V1R13. |
Timing: | Before the first IPL of z/OS V2R2. |
Is the migration action required? | Yes. |
Target system hardware requirements: | None. |
Target system software requirements: | None. |
Other system (coexistence or fallback) requirements: | If you are sharing the IFAPRDxx parmlib member between z/OS V1 and V2 systems, keep the V1 Product ID statements (for 5694-A01). You can have both the V1 Product ID and the V2 Product ID statements in the same IFAPRDxx parmlib member. After you have completed your migration to z/OS V2, you can remove the V1 Product ID statement from your IFAPRDxx parmlib member. |
Restrictions: | None. |
System impacts: | Failure to update IFAPRDxx with the correct
Product ID statement for z/OS V2 will result in various initialization
failures. An example of one of these failures is the following:
|
Related IBM Health Checker for z/OS check: | None. |
Steps to take
Follow these steps:
- If you use ServerPac, the customized IFAPRDxx parmlib member has been shipped to you in CPAC.PARMLIB. Verify that you are either using that parmlib member, or have copied its contents to a parmlib member you are using.
- If you are using CBPDO, use provided job ZOSREG in the RIMLIB,
to place a customized IFAPRD00 member into your parmlib. Note: Customers must ensure that the policy in IFAPRDxx enables only the version/release at which they are licensed. Use of and enablement of z/OS features is subject to the z/OS license terms and conditions and must be done with the knowledge of your asset manager according to the terms and conditions for z/OS. For additional license terms and conditions, see the "Usage Restriction" section in the z/OS Licensed Program Specifications.
Reference information
For more information,
see the following references:
- z/OS MVS Initialization and Tuning Reference
- z/OS Planning for Installation
- z/OS Program Directory, see the z/OS installation related information website.