Description: A user modification is a change constructed
by a user to modify an existing function, add to an existing function,
or add a user-defined function. Common types of
user modifications are:
- User-written and vendor-written exit routines.
- User-written and vendor-written SVCs.
- User-written and vendor-written termination routines.
- Modifications of IBM® source
code.
- Unit information modules (UIMs) for non-IBM hardware.
- User-written and vendor-written modules that are listed in a NUCLSTxx parmlib
member.
- Updates to default modules to set site defaults differently than
the IBM-supplied defaults, such as for the following element and features:
- XL C/C++
- DFSORT.
Consider using ICEPRMxx parmlib members,
introduced in z/OS® V1R10, to
eliminate the assembler language installation option modules.
- HLASM.
- ISPF (specifically, the ISPF configuration table).
- Language Environment®. Consider using the CEEROPT module, which can be
used to specify runtime options for CICS®, IMS™ LRR, and other LRR users. Beginning
in z/OS V2R1, for other assembler language runtime option modules,
you must migrate to use the CEEPRMxx parmlib member. See Convert to CEEPRMxx to set system-level default runtime options for
more information about CEEPRMxx.
- SDSF. See Use dynamic statements for ISFPARMS to avoid reassembly for further information.
If you made any user modifications, you have to determine which
ones need to be reworked and which ones just need to be reinstalled.
| Element or feature: |
Multiple. |
| When change was introduced: |
General migration action not tied to a specific
release. |
| Applies to migration from: |
z/OS V1R13 and z/OS V1R12. |
| Timing: |
Before the first IPL of z/OS V2R1 |
| Is the migration action required? |
Yes, if you made any user modifications. |
| 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: Use the z/OS SMP/E
Planning and Migration Assistant to help determine which user modifications
need to be reworked and which just have to be reinstalled. The Top
or New Intermediate Product Migration Changes Report uses data found
on your system, combined with IBM-supplied information from the Software
Information Base, to show you the current levels of products available
as well as product migration and functional changes using a comparison
of FMIDs. You can use this report to determine the product migration
impacts by reviewing the
"changed" FMIDs. This can help you assess
how many user modifications have to be reworked if you issued the
LIST SYSMOD USERMOD FORFMID (listing the
"changed" FMIDs) command.
All other user modifications can be reinstalled without having to
be reworked.
Note: IBM recommends
using exit routines for any user modifications where possible, and
installing the exit routines with SMP/E. By using SMP/E, it is easier
to bring forward modifications to the z/OS release you are installing.
Reference information: See the following information.