Base install of Netmaster 12.1 in CSM is successful but shows SYSMODs in error
Article ID: 38937
Updated On:
Products
Issue/Introduction
Introduction:
When installing through CSM, the SMP/E installation of Netmaster 12.1 package at level 1507 ends correctly but shows this warning in CSM:
There are SYSMODs in error installed in this SMP/E Environment.
Review SMPRPT output to see which SYSMODs are in error and if there are resolvers available.
We recommend that you apply the latest available maintenance that resolves these errors.
The corresponding SMP/E EXCEPTION SYSMOD REPORT (that also appears when using SMP/E batchjobs for the install) shows
PAGE 0001 - NOW SET TO GLOBAL ZONE DATE 03/05/16 TIME 06:30:05 SMP/E 36.68 SMPRPT OUTPUT
EXCEPTION SYSMOD REPORT FOR ZONE CAIDLIB
HOLD SYSMOD APAR ---RESOLVING SYSMOD---- HOLD HOLD
FMID NAME NUMBER NAME STATUS RECEIVED CLASS SYMPTOMS
------------------------------------------------------------------------------------------------------------------------ CC2D760 CC2D760 TR87510 RO87510 GOOD NO
PAGE 0002 - NOW SET TO GLOBAL ZONE DATE 03/05/16 TIME 06:30:05 SMP/E 36.68 SMPRPT OUTPUT
EXCEPTION SYSMOD REPORT FOR ZONE CAITGT
HOLD SYSMOD APAR ---RESOLVING SYSMOD---- HOLD HOLD
FMID NAME NUMBER NAME STATUS RECEIVED CLASS SYMPTOMS
------------------------------------------------------------------------------------------------------------------------
CC2D760 CC2D760 TR87510 RO87510 GOOD NO
Question:
Is this a problem or working as designed? Do I need to take any action?
Answer:
The base install ran correctly – nothing needs to be redone.
This warning was added to the Netmaster 12.1 installation package at level 1507 to raise awareness regarding the need to apply PTF RO87510, which is a hiper fix to correct a potential system hang.
CA recommends applying all maintenance after installing the base product, but this is not always done. The message is to ensure that at least RO87510 is applied.
Additional Information:
PTF RO87510 has a HOLDDATA that needs to be reviewed once it is applied in order to ensure that any custom code conforms to changes made in the distributed code.
Below is the HOLDDATA from the PTF.
Review STEP1. If this does not apply, you can ignore the further steps.
1. Review the member list of the TESTEXEC library for all product
regions. If any of the following AOM screening table exits are
present, check the next step.
$RMAOMCXCOMMAND PROCESSING GENERAL EXIT
$RMAOMMX MESSAGE PROCESSING GENERAL EXIT
$RMAOMNX MESSAGE NORMALISATION EXIT
2. Check the custom screening table exits listed in 1. above for the
GDB verb followed by any of the following: ADD PUT UPDATE DELETE.
If present, the function must be replaced as outlined in step 3.
3. Communication between message screening and region that used the AOM
GDB can be replaced by the EVENT verb or a mirrored Vartable.
For examples of how to use EVENT, please refer to $REAOMMS for the
screening table, and $REAC33Z for the region.
To use a mirrored VARTABLE, refer to the section "Mirrored Vartables"
in Chapter 5 of the Network Control Language Programmer Guide, the
&VARTABLE verb in Chapter 2 of the Network Control Language Reference
Guide, and the LOOKUP verb in $RMAOMMS.
If you have any questions regarding required code changes, please contact CA support.
Environment
Component:
Feedback
