IBM Support

II03777: GRAPHIC SUBSYSTEM INFORMATIONAL APAR - NPM V1R5 V1R5M1 V1R6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • ****************************************************************
    *    LAST UPDATE:  93/03/03                              CMC   *
    ****************************************************************
    DIAGNOSTIC CHECKLIST:
      - SEE NPM DIAGNOSIS, LY20-0381,
        UNDER 'GRAPHIC SUBSYSTEM CHECKLIST'
      - ADDITIONAL ITEMS:
        > IS THE SYS1.GDDMLOAD DATASET EITHER
          A.  A PART OF THE MVS LINKLIST
                     OR
          B.  CONCATENATED TO THE STEPLIB IN THE TSO
              STARTUP PROCEDURE?
       >  'GARBLED' SCREENS EXPERIENCED?  THEN
          ADD "ADMMDFT IOSYNCH=YES" TO THE GDDM ADMDEFS DATASET.
       >  WAS THE OLD IGX00041 REMOVED FROM SYS1.LPALIB?  IF
          THE NPM GRAPHICS SVC MODULE IGX00041 WAS LINKED INTO
          SYS1.LPALIB, SMP/E WILL NOT REMOVE THIS MODULE DURING
          THE INSTALLATION OF NPM R4 OR NPM R4.1.  IF YOU DO
          NOT, THE TARGET SYSTEM WILL USE THE PREVIOUS RELEASE
          OF THIS MODULE INSTEAD OF NPM R4 OR NPM R4.1'S IGX00041
          MODULE IN SFNMLPA1.
    BASIC REQUIRED DOCUMENTATION:
      - SEE NPM DIAGNOSIS, LY20-0381
        UNDER 'DOCUMENTING NPM GRAPHIC SUBSYSTEM PROBLEMS'.
    
    BASIC GRAPHIC SUBSYSTEM REQUIREMENTS FOR ALL NPM RELEASES:
     1. SUPPORTED VERSIONS OF GRAPHICAL DATA DISPLAY MANAGER (GDDM)
        SUPPORTED VERSIONS OF PRESENTATION GRAPHICS FEATURE (PGF)
     2. MVS NPM, TSO and the GRAPHIC SUBSYSTEM MUST BE INSTALLED
        ON THE SAME OPERATING SYSTEM.
     3. THE FOLLOWING GRAPHIC TERMINAL CAPABILITIES:
        A. QUERY CAPABILITY
        B. PROGRAMMED SYMBOL SETS
        C. EXTENDED COLOR
        D. EXTENDED HIGHLIGHT SUPPORT
        E. AT LEAST A 32 LINE DISPLAY. (D/T3270 MOD3 OR MOD4 OR
           D/T3279 MOD S3G ARE EXAMPLES.)
        REFER TO GRAPHIC DATA DISPLAY INSTALLATION AND SYSTEM
        MANAGEMENT FOR DISPLAY REQUIREMENTS.
    ****************************************************************
     THIS APAR CONTAINS INFORMATION ON THE NPM GRAPHIC SUBSYSTEM
     INSTALLATION.
    *
    1. WAS THE FNMMISC JCL RUN TO LINK-EDIT THE NPM GRAPHIC
       SUBSYSTEM TO THE GDDM SUBROUTINES?  (SYS1.GDDMLOAD
       CONTAINS THE GDDM SUBROUTINES.)  FNMMISC JCL IS
       IN THE SFNMJCL1 DATASET.
       (NOTE: UNRESOLVED WEAK EXTERNAL REFERENCES
        ARE TO BE EXPECTED, MSGIEW0132, CC=08 )
        ********
        Please Note: FNMMISC pulls object modules from
        AFNMMOD1, so any NPM graphics maintenance must
        be ACCEPTED prior to running FNMMISC.
    
    2. IF THE GRAPHICS MONITOR IS TO BE USED, WAS FNMIGX41 COPIED
       TO SYS1.LPALIB, OR TO SFNMLPA1, AS IGX00041?
          AFTER THE COPY WAS AN IPL WITH CLPA PERFORMED?
    
    3.  IS SYS1.GDDMLOAD EITHER:
        A.  PART OF THE MVS LINKLIST OR
        B.  CONCATENATED TO THE STEPLIB IN THE TSO LOGON PROCEDURE?
    
    4.  IS THE FNMGMON SAMPLE TSO CLIST BEING USED TO INVOKE
        THE NPM GRAPHICS SUBSYSTEM?  FNMGMON IS IN THE SFNMJCL1
        DATASET.
    
    5.  TO REQUEST MONITOR DATA FROM NPM THESE REQUIREMENTS
        MUST BE MET:
    
        A.  THE MODULE IGX00041 MUST BE INSTALLED INTO AN
            LPALIB AND A CLPA MUST HAVE BEEN DONE.
    
        B.  THE NGRAPHS STATEMENT IN THE FNMINIT MEMBER
            MUST SPECIFY A VALUE OF MAXMON GREATER THAN ZERO.
            EXAMPLE:
                 NGRAPHS MAXMON=4    THIS ALOWS UP TO FOUR
                                     SIMULTANEOUS REQUESTS.
    
        C.  EACH TSO USER THAT WILL BE USING THE GRAPHICS
            MONITOR MUST BE DEFINED TO NPM IN AN NPM
            OPERATOR STATEMENT.
            EXAMPLE:
                 OPERATOR NAME=USERID1,PASSWD=USERID1,
                          PROFILE=GRAPHICS,EXTERNAL=YES
    
            THE NAME PARAMETER MUST BE THE SAME AS THE TSO
            USERID.  IF THE USER IS ALSO ALLOWED TO LOGON TO
            NPM, THEN THIS OPERATOR ID MAY ALSO BE USED.
    
            A PASSWORD MUST ALWAYS BE SPECIFIED
            (EVEN WITH SECURITY=RACF).
    
            THE FIRST PROFILE NAME (OR ONLY) IS USED FOR
            FOR GRAPHICS MONITOR REQUESTS.
    
            THE EXTERNAL=YES ALLOWS NPM OPERATORS TO SEND
            MESSAGES TO TSO USERS.  THESE MESSAGES WILL
            APPEAR ON THE TSO TERMINAL. SEE OPTION 3.7
            ON THE NPM ONLINE SCREEN.
    
        D.  THE PROFILE DEFINED ON THE NPM OPERATOR STATEMENT
            MUST BE DEFINED TO ALLOW GRAPHICS MONITOR REQUESTS.
            THE PROFILE STATEMENT IS DEFINED IN THE FNMPROF
            MEMBER OF THE FNMPARM DATASET.
            EXAMPLE:
                 PROFILE NAME=GRAPHICS,GRPHMON=YES,...
    
            THE GRPHMON=YES ALLOWS GRAPHICS MONITOR REQUESTS
            TO BE PROCESSED.
    
        E.  WERE COLLECTION COMMANDS EXECUTED?  IN ORDER
            FOR THE GRAPHICS MONITOR TO MONITOR DATA, THERE
            MUST BE NETWORK AND/OR SESSION COLLECTION
            COMMANDS ISSUED.
    
    6.  NOTES:
    
        A.  VARIOUS 'DATA SET IN USE' MESSAGES WHILE RUNNING
            GRAPHICS, (I.E. MSGIKJ56335I, MSGIKJ56225I, ETC.)
            WHEN RUNNING THE NPM GRAPHICS SUBSYSTEM, THE
            USE OF ANY VSAM IDCAMS FUNCTION (REPRO, VERIFY,
            ETC.) IN THE NPM START-UP PROC WILL CAUSE
            AN EXCLUSIVE ENQUEUE ON THE VSAM DATASETS. IT
            IS RECOMMENDED THE JOB STREAMS FOR IDCAMS
            AND NPM START-UP BE RUN SEPARATELY.
    
        B.  AFTER APPLYING A NEW RELEASE OF GDDM
            OR APPLYING MAINTENANCE TO GDDM, RERUN
            THE FNMMISC JCL TO PICK UP CHANGES TO
            GDDM.
    
        C.  MODULE FNMMODE (NPM V1R2) HAS BEEN REPLACED
            BY MODULE FNMGRAPH (NPM V1R3).
    
        D. INCORROUT- IF GARBLED SCREENS ARE EXPERIENCED THIS
           CAN BE CORRECTED BY ADDING THE FOLLOWING TO THE GDDM
           ADMDEFS DATA SET:
           ADMMDFT IOSYNCH=YES
    
        E. WHILE SOME UNRESOLVED EXTERNAL REFERENCES CAN BE
           EXPECTED WHEN EXECUTING FNMMISC (AS REFERENCED IN THE
           PROGRAM DIRECTORY), YOU SHOULD NOT RECEIVE UNRESOLVED
           EXTERNAL REFERENCES FOR CHRNIT, CHAREA, CHHMAR, CHUMAR,
           CHAATT, CHLATT, CHXSET, CHXPUT ETC. THESE ARE PGF
           (PRESENTATION GRAPHICS FEATURE) MACROS AND THIS INDICATES
           THAT THE PGF FEATURE IS EITHER NOT INSTALLED OR NOT
           ACCESSABLE TO FNMMISC. PGF IS REQUIRED FOR NPM GRAPHICS
           AND FAILURE TO INCLUDE IT WILL RESULT IN AN ABEND0C1
           WHEN ATTEMPTING TO START GRAPHICS.
    
    ADDITIONAL SYMPTOMS:
      1. MSGADM0313 INVALID RECORD attempting to bring up NPM
         graphics. NPM.V1R5M0.SFNMGPL0 had multiple extents.
    
    REFERENCES:
         NPM MVS PROGRAM DIRECTORY
         NPM INSTALLATION AND CUSTOMIZATION GUIDE, SH20-6361
         NPM GRAPHIC SUBSYSTEM USER'S GUIDE, SH20-6362
         NPM PREVENTIVE SERVICE PLANNING (PSP BUCKET)
    
    NPM DOCUMENTATION APARS OF INTEREST:
      OY20543 - ADMGGMAP DD DATASET STATEMENT
      OY12627 - NPM V1R3 HARDWARE REQUIREMENTS
    
    NOTE: IF NPM GRAPHICS MONITOR IS NOT BEING USED, MAXMON=0 MUST
          BE SET ON THE NGRAPHS INITIALIZATION STATEMENT. FAILURE
          TO DO SO WILL RESULT IN MSGFNM656E RC68. AN ABENDS016D
          RC8 WILL BE GENERATED INDICATING AN UNSUPPORTED EXTENDED
          SVC WAS SPECIFIED. SEE INSTALLATION AND CUSTOMIZATION
          SH20-6361 UNDER 'NGRAPHS' STATEMENT.
          (ABEND016D ABEND16D MS/FNM656E)
          ( AB/S016D AB/S16D )
    KEYWORDS:
    566533301 NPM GRAPHICS SUBSYSTEM GRAPHIC R150 R154 R160
    NPMINFO TPINFO ABEND806 ABEND0C1 FNMGMON FNMMISC JCL
    VTAM NPMGRAPH TSO CLIST INSTALL INSTALLATION INFO
    GDDM FNMMISC FNMMODE IEW0132 MSGIEW0132 CC 08 ADMASEHP
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • INFOV2LIB
    REPINNED ANSWR PR91/07/23 'ADDED INFO' RALFS/LG
    REPINNED ANSWR RP93/03/02 'ADDED NPMV1R6 INFO' RAL/CMC
    

APAR Information

  • APAR number

    II03777

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1989-03-01

  • Closed date

    1989-03-03

  • Last modified date

    1995-12-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
13 December 2020