Update automation and procedures for changed and deleted messages
Description
Every release, many messages change and some are deleted. If you use automation programs to handle messages, or you have operator or other procedures that deal with messages, you should update the programs or procedures.
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 automation programs or other procedures to handle messages. |
| 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
Review the lists of changed and deleted messages in z/OS Summary of Message and Interface Changes. Update programs that automate on these messages and make other necessary accommodations.
Also, see the following migration actions, which
have more details about particular message changes:
- Update automation for changed DFSORT messages
- Update automation that handles messages IEE302I, IEE303I, IEE1302I, IEE1303I, and IOS566I
- IP Services: Update automation to monitor resolver address space initialization completion messages
- IP Services: Update automation on D TCPIP,tnproc,<Telnet>,CONN for the expanded EN TY column in message EZZ6064I
Reference information
For a list of new, changed, and deleted messages, see z/OS Summary of Message and Interface Changes.