Default language.

Running the Exception SYSMOD report

Enhanced HOLDDATA is updated daily. Therefore, you are likely to receive updates between the APPLY and ACCEPT steps, or to encounter ++HOLDs on the ACCEPT step that were not identified at the time of the APPLY step.

By reviewing the Exception SYSMOD report before the ACCEPT step, you can identify any outstanding PE or HIPER conditions.

Important

PE and HIPER conditions that existed before BMC adopted Enhanced HOLDDATA are converted, and they list the APAR number for reference.

See the following sections:

Related topic

Obtaining-Enhanced-HOLDDATA

To run the Exception SYSMOD report

  1. Create a job by copying the following JCL sample.

    Tip

    You can copy the JCL from the SampleReport.txt file in the ftp://ftp.bmc.com/bmc/holddata directory.

    //JOB_NAME JOB (ACCOUNT),'USER COMMENT',
    //             class="JOB_CLASS",MSGCLASS=MSG_CLASS,
    //             REGION=0M,NOTIFY=&SYSUID
    //******************************************************
    //* USE THIS SAMPLE BATCH JOB TO EXECUTE THE
    //* SMP/E REPORT ERRSYSMODS.
    //* MODIFY JOB CARD, DATA SET NAMES, AND ZONE FOR YOUR SITE.
    //******************************************************
    //REPORT  EXEC PGM=GIMSMP
    //SMPCSI   DD DISP=SHR,DSN=your.smpe.global.csi  <=== your global csi
    //SMPPTS   DD DISP=SHR,DSN=your.smpe.smppts      <=== your PTS
    //SMPLOG   DD SYSOUT=*
    //SMPOUT   DD SYSOUT=*
    //SMPRPT   DD SYSOUT=*
    //SMPLIST  DD SYSOUT=*
    //SYSPRINT DD SYSOUT=*
    //SMPCNTL  DD *  
    SET BDY(GLOBAL).
    REPORT ERRSYSMODS
           ZONES(your_zone).
    /*
  2. Run the job.


Important

To complete any product installation, ensure that all critical service is installed for the products by reviewing the Exception SYSMOD report. Some PE or HIPER conditions might not have a PTF that resolves the problem. Analyze the symptoms or contact BMC Support to determine whether you want to bypass the specific ERROR HOLDs and continue the installation.

Sample Exception SYSMOD report

The Exception SYSMOD report provides the following information:

  • Affected FMID
  • APAR that describes the HIPER or PE condition
  • SYSMOD that resolves the condition, when availableIf the resolving SYSMOD has been applied, the report will not include the condition.
  • Whether the resolving SYSMOD has been received
  • Class of the hold
  • Hold symptoms

Sample Exception SYSMOD report

PAGE 0001 - NOW SET TO GLOBAL ZONE          DATE 12/13/08 TIME 19:13:26 GIMS
EXCEPTION SYSMOD REPORT FOR ZONE MV3913C

HOLD    SYSMOD  APAR    ---RESOLVING SYSMOD----  HOLD    HOLD
FMID    NAME    NUMBER  NAME    STATUS RECEIVED  CLASS   SYMPTOMS
--------------------------------------------------------------------------------------
BBDDZ82 BBDDZ82 BAD9998 ***NONE                  HIPER   IPL - E37 failure
BBIIS25 BPI9594 BAI8761 BPI9999 GOOD   YES       PE      PRV - see BAI8761 for details
BBGSC74 BPG5406 BAG3490 ***NONE                  PE      IPL - fails with E37 abend
        BPG5465 BAG3490 ***NONE                  PE      IPL - fails with E37 abend
BBGCO75 BPG5407 BAG9999 BPG9999 GOOD   NO        PE      DAL - Perf reports invalid
        BPG5466 BAG9999 BPG9999 GOOD   NO        PE      DAL - Pref reports invalid   

EXCEPTION SYSMOD REPORT SUMMARY
ZONE     FMID        TOTAL APARS     TOTAL RESOLVING
                    AGAINST FMID   SYSMODS AGAINST FMID
--------------------------------------------------------------------------------------
MV3913C  BBDDZ82            1                0
BBIIS25                     1                1
BBGSC74                     1                0
BBGCO75                     1

The following table describes the BMC hold symptoms.

Hold symptoms

Symptom

Keyword

Description

DAL

DATALOSS

Indicates destruction or contamination of data

FUL

FUNCTIONLOSS

Causes a major loss of function

IPL

SYSTEMOUTAGE

Causes a re-IPL, reboot, recycle, or restart on one or more systems or subsystems

PRF

PERFORMANCE

Causes severe impact to system performance or throughput

PRV

PERVASIVE

Identifies a problem that might affect many users

SYSPLXDS

SYSPLEXDS

Identifies HIPER fixes that are needed to support and implement sysplex data sharing

XSYS

XSYSTEM

Identifies HIPER fixes that provide cross-system, migration, compatibility, or toleration support

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*