SMP/E HOLDERROR Processing
Note: This is publication is now archived. For reference only.
Published 07 January 2003
View online
Authors: Jouko Jantti
Abstract
SMP/E HOLDERROR processing is a practical method that can be used to determine SYSMODs in error. With this process you execute the APPLY CHECK BYPASS HOLDERROR command against SYSMODs you have already received. The output from the SMP/E command is then searched for an SMP/E message (GIM35934) that identifies a SYSMOD in error. Another method for determining the SYSMODs in error is to examine the SMP/E CAUSER report. However, the SMP/E CAUSER report contains information about which piece of service held up the other service from going to the system, normally due to a PE chain, and many times, one or two PTFs in error can keep many other PTFs from processing. This technique provides an easy way to find the end of chains. Even though this hint is an extract from an IMS IBM Redbooks publication, it is not only IMS specific topic, and it may apply also to other SMP/E users.
Contents
Executing APPLY CHECK BYPASS(HOLDSYS,HOLDERROR)
The primary SMP/E command used for this process is APPLY CHECK BYPASS(HOLDSYS,HOLDERROR). The following example contains the SMP/E commands that can be used to generate the SMP/E listing:
//SMPEIN DD *
SET BOUNDARY (IMSTZ71) .
APPLY CHECK GROUPEXTEND
BYPASS(HOLDSYSTEM,HOLDERROR).
/*
Reviewing the SMP/E reports
The following is an example listing of the output from an execution of the SMP/E APPLY CHECK BYPASS(HOLDSYS,HOLDERROR) command:
APPLY CHECK GROUPEXTEND /* APPLY FOR THIS FMID */
BYPASS(HOLDSYS,HOLDERROR).
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD UQ51605 WERE NOT SATISFIED, BUT
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35966I SYSTEM HOLD DOC ORIGINATED BY SYSMOD UQ51605 WAS BYPASSED.
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD UQ51639 WERE NOT SATISFIED, BUT
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35966I SYSTEM HOLD DOC ORIGINATED BY SYSMOD UQ51639 WAS BYPASSED.
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD UQ53718 WERE NOT SATISFIED, BUT
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35966I SYSTEM HOLD DOC ORIGINATED BY SYSMOD UQ53718 WAS BYPASSED.
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD UQ54647 WERE NOT SATISFIED, BUT
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35966I SYSTEM HOLD DOC ORIGINATED BY SYSMOD UQ54647 WAS BYPASSED.
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD MOD UQ54647 WAS BYPASSED.
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35966I SYSTEM HOLD DOC ORIGINATED BY SYSMOD UQ54648 WAS BYPASSED.
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD UQ54962 WERE NOT SATISFIED, BUT
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35966I SYSTEM HOLD DEP ORIGINATED BY SYSMOD UQ54962 WAS BYPASSED.
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD UQ55863 WERE NOT SATISFIED, BUT
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35934 ERROR HOLD DQ54672 WAS BYPASSED.
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD UQ57027 WERE NOT SATISFIED, BUT
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35966I SYSTEM HOLD DOC ORIGINATED BY SYSMOD UQ57027 WAS BYPASSED.
GIM35966I SYSTEM HOLD ACTION ORIGINATED BY SYSMOD UQ57027 WAS BYPASSED.
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD UQ58403 WERE NOT SATISFIED, BUT
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35966I SYSTEM HOLD DOC ORIGINATED BY SYSMOD UQ58403 WAS BYPASSED.
GIM42001W THE FOLLOWING CONDITIONS FOR SYSMOD UQ61481 WERE NOT SATISFIED, BUT
WAS SPECIFIED. PROCESSING CONTINUES.
GIM35966I SYSTEM HOLD DEP ORIGINATED BY SYSMOD UQ61481 WAS BYPASSED.
GIM35966I SYSTEM HOLD ACTION ORIGINATED BY SYSMOD UQ61481 WAS BYPASSED.
GIM20501I APPLY PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 04.
The report was generated after the IMS Version 7 SMP/E environment was established. While reviewing the listing, a FIND GIM35934 command was performed. That command found the following in the listing:
- GIM35934 ERROR HOLD DQ54672 WAS BYPASSED
(highlighted in the listing)
Resolving the HOLDERRORs
Once the unresolved hold errors are identified, you need to do one of the following:
- Process corrective PTF — If there is a PTF fix, it should be processed.
- Do not install the PTF in error (or PE PTF) into the system.
- Ask the IBM support center for recommendations.
- Apply APAR — If there is an APAR fix available and if you cannot tolerate the error, then obtain and apply the APAR.
- Obtain a fixtest — If there is a fixtest available and if you cannot tolerate the error, then obtain and apply the fixtest.
- BYPASS the error — If the component involved in the PE is not implemented on this system, the hold error can safely be bypassed.
Important: Be sure to analyze all SMP/E messages.
Special Notices
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.