Installing CA View release 12.2 and the BRM5APP job fails on RC=12 with GIM30206E and GIM35901I unresolved HOLD reason errors.

Products

• Deliver
• View

Issue/Introduction

We are attempting to install the CA View release 12.2 base product but the SMP/E APPLY job is failing with a RC=12 due to receiving errors similar to the following:

GIM30206E ** APPLY PROCESSING FAILED FOR SYSMOD CBRMC20. HOLD REASON IDS WERE NOT RESOLVED.

GIM35901I ERROR HOLD AC87514 WAS NOT RESOLVED. UNRESOLVED HOLD REASON REPORT FOR APPLY CHECK PROCESSING

ERROR CBRMC20 HIPER AC87514 CBRMC20 RO87340 MISSING

ERROR AC87514 UNRESOLVED CBRMC20

What causes these errors and how can we resolve them in order to install the product? 

Environment

z/OS

Resolution

The cause of the problem/errors is that, there is reference to HIPER PTF (RO87340) in the HOLDDATA that is downloaded from Support Online, but, the PTF is not in the pax installation file. The PTF was published after the pax file was created. As a result, the base install is failing because of HOLDDATA that references a HIPER PTF that was published after the release went GA. 

When this scenario presents itself, customers have two options for getting the SMP/E APPLY (And ACCEPT) to run successfully... 

Option 1 : 

As per the comments in the SMP/E APPLY jobs JCL, in this case BRM5APP, the JCL should be modified to include the BYPASS(HOLDSYSTEM,HOLDERROR(reason id)) parameter. An example of what the BYPASS statement should look like in your particular case (regarding the errors on PTF RO87340 - reason ID=AC87514) would look like the following: 

BYPASS(HOLDSYSTEM,HOLDERROR(AC87514)). 

** NOTE ** 

- Add the above HOLDERROR parameter to BOTH the APPLY JCL (BRM5APP) as well as the ACCEPT (BRM6ACC) JCL. 

- The addition of this parameter may cause the APPLY and ACCEPT jobs to receive a RC=04 and a "BYPASSED HOLD REASON REPORT" will be produced. But the jobs will run to "successful completion". 

- Since the HOLD statements are purposefully and specifically in the HOLDDATA to draw your attention to the fact that you need to apply a HIPER PTF, you will want to make sure that you DOWNLOAD and APPLY the referenced PTF before implementing the product into a production environment! 

 

 

The "BYPASSED HOLD REASON REPORT" will look similar to the following: 

******************** 

BYPASSED HOLD REASON REPORT FOR APPLY PROCESSING 

 

TYPE REASON ID FMID SYSMOD ++HOLD DATA 

------ --------- ------- ------- ------------------------------------------- 

ERROR AC87514 CBRMC20 CBRMC20 ++HOLD(CBRMC20) ERROR FMID(CBRMC20) 

REASON(AC87514) DATE(16007) CLASS(HIPER) 

COMMENT( 

PROBLEM VIEW-1972: MISSING DDS IN JOB MODE RECORDS, POSSIBLE CORRUPT 

DATABASE 

SMRTDATA(CHGDT(160107) FIX(RO87340) 

SYMP(DAL) 

)). 

 

SUMMARY OF BYPASSED AND UNRESOLVED HOLD REASON REPORT FOR APPLY PROCESSING 

 

NOTE: SEE THE HOLDDATA REPORT OF UNRESOLVED HOLD REASON IDS TO DETERMINE HOLDS CAUSING SYSMOD TERMINATIONS. 

SEE THE HOLDDATA REPORT OF BYPASSED HOLD REASON IDS TO DETERMINE HOLDS THAT WERE BYPASSED. 

 

TYPE REASON ID REPORT SYSMODS AFFECTED 

------ --------- ---------- ----------------- 

ERROR AC87514 BYPASSED CBRMC20 

******************** 

 

Option 2 : 

The actual HOLDDATA file created by the job that downloads the HOLD data from CA Support Online, in this case job BRM1HOLD, can be manually edited and the statements associated to the missing PTF can be removed. The statements to be removed are as follows: 

 

++HOLD(CBRMC20) ERROR FMID(CBRMC20) 

REASON(AC87514) DATE(16007) CLASS(HIPER) 

COMMENT( 

PROBLEM VIEW-1972: MISSING DDS IN JOB MODE RECORDS, POSSIBLE CORRUPT 

DATABASE 

SMRTDATA(CHGDT(160107) FIX(RO87340) 

SYMP(DAL) 

)). 

 

** NOTE ** 

 

IMPORTANT - since the HOLD statements are purposefully and specifically in the HOLDDATA file to draw your attention to the fact that you need to apply a HIPER PTF, you will want to make sure that you DOWNLOAD and APPLY the referenced PTF before implementing the product into a production environment!