CarsSummaryProcessStep/CorrectiveApplySummaryProcessStep is not allowed
search cancel

CarsSummaryProcessStep/CorrectiveApplySummaryProcessStep is not allowed

book

Article ID: 73556

calendar_today

Updated On:

Products

Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction

Applying CAR1802 for CA Common Services with CA CSM fails with CarsSummaryProcessStep is not allowed and without using CAR1802 CorrectiveApplySummaryProcessStep is not allowed.

Environment

Release: MSMNGR00200-6.0-Chorus Software Manager
Component:

Resolution

This is because RO96371 had the incorrect DISTLIB AEG1SHSC specified for ESMSH. This results in the apply of RO99859 which is included in CAR1802 to fail as follows:
‚ÄčGIM40501E ** THE DISTLIB VALUE (AAW0ZFS1) SPECIFIED FOR SHELLSCR ESMSH IN SYSMOD RO99859 DOES NOT MATCH THE DISTLIB 
VALUE (AEG1SHSC) IN THE SHELLSCR ENTRY FOR ESMSH. 
GIM22601I APPLY PROCESSING FAILED FOR SYSMOD RO99859. 

 
Apply RO99859 without CAR1802 would also fail with the GIM4050E and so with CA CSM the failure would be CorrectiveApplySummaryProcessStep is not allowed while with CAR1802 it would be CarsSummaryProcessStep is not allowed.
  
 To correct this specific GIM4050E/CarsSummaryProcessStep/CorrectiveApplySummaryProcessStep, apply RO96371 first by itself then perform the HOLDDATA action for RO99859 to re-assign DISTLIB from AEG1SHSC to AAW0ZFS1 and then apply RO99859 followed by the CA RS upgrade. 
 
Note that the GIM40501E will cause the CarsSummaryProcessStep/CorrectiveApplySummaryProcessStep failure for any product/release/PTF. This example is specific to CA Common Services/r14.1/RO99859.