IBM Support

II07982: SECTION 1: INSTALLATION INFORMATION FOR PSP BUCKET OF NETVIEW PERFORMANCE MONITOR ( NPM ) VERSION 2 RELEASE 2.0

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • ************************
    *    UPGRADE NPM220    *
                         ************************
    
    THIS SECTION CONTAINS CHANGES TO THE NPM'S PROGRAM DIRECTORY
    AND OTHER INSTALL RELATED CONCERNS.
      FOR MVS/NPM ( SUBSET: HNR2220  PID: 5655043  SYSTEM: MVS )
    ****************************************************************
    *                  C H A N G E   S U M M A R Y                 *
    ****************************************************************
    
     DATE LAST CHANGED: 97/03/24                               CMC
    
    ****************************************************************
    * SECTION 1.  I N S T A L L A T I O N   I N F O R M A T I O N  *
    ****************************************************************
    
    
    11  97/03/24  NPM PPT
                  NPM must be correctly defined in the MVS PPT
                  and APF authorized.  Reference NPM
                  Installation and Customization, section:
                     'Authorizing NPM for MVS'
                  The following are some of the errors that may
                  result if this is not properly defined:
                    -  msgfnm328i followed by msgfnm333i rc=16.
                    -  abend55f abends55f ab/s55f abends055f
                          abend055f ab/s055f
                    -  abends0c2 in fnmxsvt0 or fnmmsvt0, ab/s0c2
                          abend0c2 ab/s00c2 abends00c2
                    -  msgfnm329t FNMMAIN IS NOT AUTHORIZED
    
    10. 96/08/15  On applying usermod FNMUXA1 to assemble and
                  link edit FNMBLVRP, the following iewl messages
                  are received:
                     MSGIEW2646W  ESD RMODE(24) CONFLICTS WITH
                                  USER-SPECIFIED RMODE(ANY) FOR
                                  SECTION FNMBLVRP
                     MSGIEW2651W  ESD AMODE(24) CONFLICTS WITH
                                  USER-SPECIFIED AMODE(31) FOR
                                  ENTRY POINT FNMBLVRP
                     MSGIEW2635I  THREE BYTE ADCON IN SECTION
                                  IN FNMBLVRP AT OFFSET 0001
                                  IN MODULE WITH RMODE=ANY
                                  CANNOT BE RELOCATED
                  and if the above messages are ignored and
                  an attempt is made to start NPM, the following
                  NPM abends will occur solidly:
                     abends0c4 pic11 in FNMMAIN
                     abends50d rc1C in FNMMAIN
                  and message IEC191I '50D-1C, invalid parameter
                  list supplied to open macro' will also be issued.
    
                  The reason for the above is if user mistakenly
                  adds 'MODE AMODE(31),RMODE(ANY) to FNMUXA1
                  SMP/E usermode to attempt to force FNMBLVRP to
                  be linked above the line.  Please see NPM
                  enhancement apar OW22077 for further details
                  on how to force NPM's LSR option to create
                  BLDVRP macro using as much extended storage
                  as possible (parm list, i/o buffers and i/o
                  related vsam control blocks).
    
    9. 96/07/15  On applying usermod FNMUXC1, the following
                  error messages are received:
                     MSGGIM30209E 'Apply processing failed for
                                   sysmod FNMUXC1.  Required
                                   sysmod failed or were missing.'
                     MSGGIM35904I 'PREREQUISITE SYSMOD FNMUXBZ
                                   MISSING'
                  To Resolve: Change the PRErequisite operand on
                  the ++VER statement to reference FNMUXB1 or
                  FNMUXB3, if one of these USERMOD's has been
                  applied.  Otherwise, remove the PRE operand
                  completely.
    
     8. 96/05/16  Page 180 step 2 of chapter 4 'Customizing the
                  FNMREPRT reporting program' in NPM REPORTS AND
                  RECORD FORMATS manual (SH19-6965-01) is
                  incorrect because it fails to mention that
                      ICONTENT=WEIGHT,
                  must be added to the COLUMN statement for
                  X25UTIL if the batch reporting interval is
                  greater than the collection interval.
                     Actually, ICONTENT=WEIGHT or ICONTENT=AVERAGE
                  needs to be added to any utilization COLUMN
                  statement which user adds (customizes), not just
                  for X25 links.
                     If ICONTENT parameter is not coded, it
                  defaults to SUM, which seems to result in
                  too low ( incorrout ) line ( link ) utilization.
    
    
    7. 96/02/26 The Program Directory specifies small
                dataset sizes for the NPM target and
                distribution datasets.  This may cause
                out-of-space abends when trying to install
                NPM.  Please increase the No. of Blocks to
                alliviate the problem.
              EXAMPLES from NPM Install on Development Test
              System:
                                      TEST SYSTEM
               DATASET NAME          NO. OF BLOCKS
                 AFNMGPL0                  424
                 AFNMJCL1                  174
                 AFNMMAC1                  119
                 AFNMMOD1                1,449
                 AFNMPNL0                  672
                 AFNMRPT1                  168
                 AFNMSRC1                  154
                 AFNMINS0                1,267
                 AFNMEUI1                1,026
                 SFNMGPL0                  424
                 SFNMJCL1                  490
                 SFNMLPA1                    7
                 SFNMMAC1                  119
                 SFNMPNL0                  672
                 SFNMRPT1                  483
                 SFNMSRC1                  336
                 SFNMINS0                1,267
                 SFNMEUI1                1,026
    
     6. 94/12/22  Program Directory Appendix C 'Service Level
                  Information' is incorrect. The following
                  PTFs are described as being 'integrated into
                  NPM v2r2':
                      UW06080 , UW06273 , UW06333
                      UW06405 , UW06418
                  Actually, none of these ptfs are in the base
                  of NPM v2r2. The correct Appendix C list is
                  'NONE' (there should be no ptfs listed in
                  this appendix).
    
     5. 96/04/02 Problem: NPM apply fails with SMP/E messages
                    MSGGIM30216I 'APPLY PROCESSING FAILED FOR
                               SYSMOD HNR2220'
    
                    also
    
                    MSGGIM30201E for each previous release of
                                 NPM being deleted (or marked
                                 deleted) by installation of
                                 the new release.
                    and
    
                    MSGGIM24001E 'ASSEMBLER PROCESSING FAILED
                               FOR FNMUEXIT IN SFNMSRC1, RC12'
    
                    and several assembler messages:
    
                    MSGIEV057 'ERROR: UNDEFINED OPCODE FOR
                               <various symbols>'
                    or
                    MSGASMA057E Undefined operation code - FNMSMFR
    
    
                   The problem is caused by SMP/E attempting
                   to assemble source module FNMUEXIT which
                   should not be assembled by SMP/E during
                   the SMP/E APPLY of HNR2220.
    
                   SMP/E is attempting to assemble FNMUEXIT
                   because an installation process of a
                   previous release of NPM created SMP/E
                   entries for FNMUEXIT that are incomplete.
                   The incomplete entries do not have an FMID
                   sub-entry filled in.  Thus, during
                   installation of HNR2220, the FNMUEXIT MOD
                   and LMOD entries prevail, triggering the
                   assembly.  The entries prevail because
                   they cannot be associated with a specific
                   release of NPM and thus are not affected
                   by the DELETE parameter of the ++VER
                   statement in the MCS for installation of
                   HNR2220.
    
                   To verify this problem, using the TSO/E
                   SMP/E dialogs, issue a Cross- Zone-Query
                   command for MOD FNMUEXIT. If the status
                   display shows blanks in the FMID column
                   then follow the resolution below:
    
                   Please run SMP/E with the following UCLIN
                   to remove the extraneous entries which are
                   present from a previous release of NPM:
    
                    //SMPCNTL DD *
                      UCLIN.
                       DEL MOD(FNMUEXIT).
                       DEL LMOD(FNMUEXIT).
                      ENDUCL.
                    //
    
    4.  94/12/15  In Section 6.1.5.2  Verify the Apply of
                  NPM:  MSGGIM23903W should be associated
                  with the linkedit message MSGIEW0461
                  or MSGIEW2454W, if BINDER.
                  MSGGIM23903W points to the linkedit
                  sequence number.  Look at the linkedit
                  output for the sequence number and there
                  you will see the IEW messages.  These
                  messages can be ignored for the unresolved
                  external references in the modules listed in
                  the program directory in this section.
                  Unresolved external reference other than
                  those listed in the program directory
                  should be investigated.
    
    3.  94/10/25   If migrating to NPM 2.2 from NPM 1.6 or
                   NPM 1.5, note that the LRECL and BLKSIZE
                   has changed for SFNMGPL0.  In NPM 1.5 and
                   1.6, LRECL=80, BLKSIZE=6000.  This has
                   changed in NPM 2.2 to LRECL=400, BLKSIZE=400.
    
    2.  94/09/19   MSGGIM44402W will occur during APPLY of NPM
                   for the following modules:
                      FNMBLVRP    BNMRPOEX    FNMU84     FNMU83
                      FNMEXCAA    FNMUEXIT    FNMRPIEX
                   These messages (GIM44402W 'No module entries
                   defined') can be ignored. See Program Directory
                   6.1.5.2 'Verify the Apply of NPM V2R2' for
                   further details.
    
    
    1.  94/03/14  If SMF exits IEFU83 or IEFU84 have been used in
                  a previous release of NPM, the NPM install job
                  will try to delete the exits.  This may cause
                  IEFU83 or IEFU84 in SYS1.LPALIB to be marked
                  as non-executable.  The linkedit will end with
                  a return code of 4.  Make sure you check the
                  linkedit with any return code above zero, to
                  ensure this wont cause a problem later.  Then
                  make sure to assemble and relink IEFU83 or
                  IEFU84 with NPM's appropriate usermod or
                  FNMEXITS after the installation of NPM.
    ****************************************************************
    * KEYWORDS: INFO NPMINFO R220 V2R2M0 R2.2 BUCKET PSPBUCKET     *
    *           INST INSTALL INSTALLATION 565504300 0566665        *
    *           NPM210 5655043                                     *
    ****************************************************************
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • npminfo
    

APAR Information

  • APAR number

    II07982

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1994-06-15

  • Closed date

    1994-07-29

  • Last modified date

    1997-03-24

  • 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:
14 December 2020