Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Running Different Levels of IPCS z/OS MVS IPCS User's Guide SA23-1384-00 |
|
The version and release level of IPCS must match the level of the system that produced the dump. You must use the z/OS MVS™ libraries of IPCS code, for example, to analyze a dump or trace produced by an z/OS MVS system. With z/OS® Release
2, enhancements are added that make it more important that the user
confirm that the level of IPCS being used matches the level of the
system that generated dumps and traces. If there is a mismatch between
the IPCS level and the level of the dumping program, IPCS will issue
an appropriate message when IPCS dump initialization is performed.
Also with z/OS Release 2,
IPCS issues messages to indicate whether the level of IPCS matches
the level of the dumping program and the level of the system being
dumped. If all are at the same level, one of the following messages
will be issued:
With z/OS with
FMID JBB778H, an additional indicator is added to identify an MVS release. IPCS has been updated
to display this indicator as a part of the product name as shown below:
With the exception of SADUMP, z/OS dumping
programs are part of the system itself and cannot be matched with
the wrong system level. SADUMP is intended to be used to process a
system of a matching level. However, if there is a mismatch between
the level of the dumped system and the SADUMP level, message BLS18224I
identifies the nature of the mismatch.
In all cases, IPCS will attempt to process the dump. Although IPCS and the dump or trace must have matching levels, you can run IPCS on different levels of the system. See z/OS MVS IPCS Customization for requirements for running IPCS on different levels of z/OS. |
Copyright IBM Corporation 1990, 2014
|