Question & Answer
Question
An SMP/E APPLY job failed with the following errors when trying to apply RMM maintenance: [
APPLY GROUPEXTEND
SOURCEID(PUT*,HIPER, ESO0206)
BYPASS(HOLDSYSTEM, HOLDUSER).
GIM38201E ** THERE IS A MODID ERROR FOR MOD ENTRY EDGMLCS IN SYSMOD UA23768.
GIM31901I SYSMOD UA23768 DOES NOT SPECIFY UA19462 ON THE PRE OR SUP OPERAND.
UA19462 IS THE RMID FOR MOD EDGMLCS THAT IS CURRENTLY INSTALLED.
GIM38201E ** THERE IS A MODID ERROR FOR MOD ENTRY EDGMTSO IN SYSMOD UA23768.
GIM31901I SYSMOD UA23768 DOES NOT SPECIFY UA20874 ON THE PRE OR SUP OPERAND.
UA20874 IS THE RMID FOR MOD EDGMTSO THAT IS CURRENTLY INSTALLED.
GIM38201E ** THERE IS A MODID ERROR FOR MOD ENTRY EDGVRECH IN SYSMOD UA23768.
GIM31901I SYSMOD UA23768 DOES NOT SPECIFY UA20529 ON THE PRE OR SUP OPERAND.
UA20529 IS THE RMID FOR MOD EDGVRECH THAT IS CURRENTLY INSTALLED.
GIM22601I APPLY PROCESSING FAILED FOR SYSMOD UA23768.
GIM30209E ** APPLY PROCESSING FAILED FOR SYSMOD UA90234. REQUIRED SYSMODS FAILED
OR WERE MISSING.
GIM35911I COREQUISITE SYSMOD UA90233 FAILED.
GIM30209E ** APPLY PROCESSING FAILED FOR SYSMOD UA90239. REQUIRED SYSMODS FAILED
OR WERE MISSING.
GIM35907I PREREQUISITE SYSMOD UA90233 FAILED.
GIM30202E ** APPLY PROCESSING FAILED FOR SYSMOD UA90233. ALL SYSMODS THAT WOULD
HAVE SUPERSEDED UA90233 HAVE FAILED.
GIM35942I SYSMOD UA23768, WHICH WOULD HAVE SUPERSEDED SYSMOD UA90233, FAILED.
GIM20501I APPLY PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 08.
]Cause
The SMP/E messages indicate that an error exists in the relationship between an element in the indicated SYSMODs (PTFs) being installed and elements in other SYSMODs that are already installed or that are being installed concurrently. After a check of all the PRE and SUP statements of all of the affected PTFs, all were found to be in order.
The problem was caused a week earlier when a previous APPLY job was cancelled because the spool filled up and locked the system. Certain parts for the PTFs in question got installed before the spool filling up during the earlier APPLY job. During the second APPLY the following week, PTFs containing the same parts as the parts that got missed when the spool filled up were hit by PTFs at a higher level resulting in the MODID errors being seen. A LIST of the modules affected shows that the RMIDs were not updated. The mod output showed that the RMID was not the PTF number of the last PTF applied.
Answer
Perform an APPLY REDO of all of the PTFs affected by the spool filling up. Then, redo all of the applies that were done since the time that the spool filled up. Afterward, a listing of all SYSMODs will show no PTFs are in ERRor status.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG90","label":"z\/OS"},"Component":"5695DF186 - DFSMS\/MVS RMM","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB56","label":"Z HW"}}]
Was this topic helpful?
Document Information
Modified date:
03 September 2021
UID
isg3T1010412