II06825: NPM R6 MIGRATION PACKAGE (HINTS AND TIPS), VOLUME 1. FOR NPM V1R6 UNDER MVS OR VM (FMID HNR1160 OR VNR1160).

APAR status

• Closed as canceled.

Error description

• +----------------------------------------------------+
  | NETVIEW PERFORMANCE MONITOR V1R6 MIGRATION PACKAGE |
      +----------------------------------------------------+
  
  
       This is a pamphlet of helpful hints and tips to make the
  switch from an earlier release of NPM go smoothly. It also
  describes some of the common pitfalls other NPM customers have
  experienced during previous migrations.  Please read over before
  or during the actual migration to get the best benefits.  It is
  designed to be used by the technical systems programmer who has
  some familiarity with NPM and who is migrating to NPM release 6
  (fmid HNR1160, MVS NPM, or VNR1160, VM NPM).
  
  I.   Using FNMILOG and SYSPRINT to diagnose setup problems.
  
  1.   Before starting NPM, verify LIST=YES and CONFIG=YES are
  coded on the NPM initialization statement in FNMINIT. This will
  ensure a complete FNMILOG is created. Check NPM startup JCL to
  make sure FNMILOG and SYSPRINT DD cards exist and to find where
  these logs will be sent. FNMILOG has the word 'FNMIN000' on the
  left side of the header of every page, whereas SYSPRINT has
  'FNMONL00'. For examples of both, please see chapter 6 in NPM
  DIAGNOSIS manual (LY20-0381-04).
       FNMILOG contains a listing of each initialization deck read
  in at startup time (FNMINIT, FNMOPER, FNMPROF, etc), with each
  delimited by message FNM284I. Each deck is printed in FNMILOG
  exactly as it is coded, and each statement is numbered.
  Following this section, the FNMILOG lists all the statements
  again, but these are the 'compiled' or 'processed' versions. If
  any statement contains an error the text '*** ERROR ***' will be
  printed on the left of the compiled statement.
       Any actual error messages will be included in the FNMILOG,
  either before the 'compiled' section or after. Refer to these
  messages to resolve the error. The error message will be
  prefixed with a number followed by an ampersand '@'. The number
  references the statement which caused the error. Most errors are
  syntactical.  NPM INSTALLATION AND CUSTOMIZATION manual (SH20-
  6361-07) contains the 'Rules for Coding NPM Initialization
  Statements' in chapter 3; and Part 3: Reference, Appendix A
  'Initialization Statement Reference' gives the syntax and
  examples of each statement.
  
       +--------------------------------------------------------+
       | Warning: syntax error on NPM initialization stmt will  |
       | cause NPM's parser to take defaults for statement's    |
       | succeeding parameters. This may cause data to not be   |
       | logged to correct destinations, or certain features    |
       | to be disabled. For example:                           |
       |   NPM ALERT=YES,LOG=(SMF,NPMLOG),SESSION=(SMF),        |
       |   LANCOLL=YES,...                                      |
       | The second occurrence of this statement in FNMILOG:    |
       |   NPM ALERT=YES,LOG=NPMLOG,SESSION=SESSION,            |
       |   LANCOLL=NO,...                                       |
       | Because LOG can only have one destination (syntax      |
       | error). Notice that ALERT=YES because it was processed |
       | before the error was detected. Also note that the      |
       | session data will not be logged to SMF and that NPM's  |
       | LAN bridge collection feature will be disabled. This   |
       | error is quickly resolved by a simple examination of   |
       | NPM's FNMILOG data set. Please use it.                 |
       +--------------------------------------------------------+
  
       Following the 'compiled' statements are the virtual storage
  allocation tables (they are not as useful as the performance
  measurement tables, accessed via option 3.4 from NPM primary
  functions panel). Following this is the NPM CONFIGURATION REPORT
  which lists every resource defined to NPM by the initialization
  statements or the NCP commands (NPM obtains resource
  information from NCP RRTs). The Configuration report takes a lot
  of space and it is recommended that it be suppressed except
  during migration and NPM problem determination (code CONFIG=NO
  on NPM statement to suppress). The last part of the FNMILOG is
  the Totals By Resource Type table.
  
  2.   NPM SYSPRINT file contains NPM messages generated during
  the running of NPM, starting with any messages produced as
  FNMSTRT member is parsed. SYSPRINT also prefixes the statement
  number to the error message. This allows systems programmer to
  match the error message to the statement which caused it.
  Messages which do not have a corresponding statement number will
  have either a '@' or '*' prefixed only.
       The most important message to check is FNM025I 'NPM
  Initialization Completed', which indicates NPM started without
  any errors. If message FNM045W 'NPM Initialization completed
  with Errors' occurs, either the preceding section of SYSPRINT or
  the FNMILOG needs to be examined to determine and correct the
  error.
       Please code PRINTMBR=YES (this is the default) on any
  EXECUTE statements in FNMSTRT, or set LIST NPM EXEC field to YES
  if executing exec via option 3.8 in NPM online panels. This
  option causes NPM to print the contents of the exec in SYSPRINT
  which is very helpful when trying to determine the cause of an
  exec-generated error message.
  
  II.  NPM INFO Apars.
       NPM release 6 PSP Bucket has a comprehensive listing of
  NPM's Info Apars attached. These apars describe some of NPM's
  features in great detail. Please read these and the PSP bucket
  for late breaking information which may not be in regular NPM
  manuals. PSP bucket can be ordered from IBM software support.
  
  III. Defining NPM to VTAM and Authorizing for MVS.
  
  1.   Follow the four steps listed in section 'Defining NPM to
  VTAM' in NPM INSTALLATION manual (page 5). Steps 1, 3, and 4
  contain new release 6 specific instructions.
       NPM's authorization list needs to have 'CNM' added to it if
  NPM is running under VTAM 3.4.1 or higher, and HOSTCOLL=YES is
  coded (default is YES) on NPM initialization statement. Plus
  VTAM's startup jcl needs to have NPM's load library concatenated
  to VTAMLIB DD card so that VTAM can load ISTEXPRF, the VTAM/NPM
  session collection performance interface load module.
  Failure to do so may result in unpredictable errors such as:
     FNM930I NPM COMMAND PROCESSING TERMINATED
     FNM320I FNMONL00 ENDED, RC=00016
     FNMMAIN ENDED WITH RC=16
  or
     FNM316W 'SESSION COLLECTION DISABLED. AUTH=CNM OMITTED
             FROM VTAM APPL DEFINITION'
  or
     MSGFNM305I ' ISTEXPRF IS NOT LOADED, RC = 24 '
     MSGIST985I 'ISTEXPRF REPLACEMENT FAILED, CODE 20 '
  
  Additional information:
  Can also get above messages if NPM's load library has a smaller
  blocksize and concantenated before SYS1.VTAMLIB.  To resolve,
  either make the blocksize larger than VTAMLIB or concantenate
  NPM's load library after VTAMLIB.  (1/12/94 tld)
  .
     This new method of collecting session statistics is much
  more efficient in terms of CPU cycles and memory, plus it
  eliminates the need to code GTF=YES on the NPM SESSCOLL command
  in order to capture vtam buffer trace data in a gtf dataset. NPM
  will reset GTF=YES to GTF=NO when running under VTAM 3.4.1 or
  higher, since NPM no longer has hooks into VTAM buffer trace
  modules.
  
  2.   Release 6 PPT entry has been simplified. See Step 1 on
  page 6 of NPM INSTALLATION manual, in 'Authorizing NPM for MVS'
  section. The minimum required PPT entry is:
      PPT PGMNAME(FNMMAIN) NOSWAP KEY(6)
  Parms 'PRIV' and 'LPREF' are not required and PRIV should not be
  coded since it will cause NPM to run in Performance Group zero
  with this group's default dispatching priority. It is recommende
  that NPM run with dispatching priority just below VTAM and above
  the programs for which NPM will be performing session
  collection.
       Steps 2 and 3 on page 6 instruct reader to APF authorize
  NPM's load module and LPA libraries. Don't forget that any other
  libraries concatenated to them must also be APF authorized, as
  discussed in MVS INITIALIZATION AND TUNING manual. Also don't
  forget to APF authorize the library pointed to by FNMLLIB DD
  card in NPM's startup jcl.
  
  IV.  Session collection on TSO will fail with message FNM088W
  sense code 08060000 if the NPM application statement defining
  TSO lists more synonyms than are defined to VTAM. Make sure
  NPM's SYNCOUNT parameter on NPM TSO APPL stmt is no greater than
  the number of synonyms for TSO defined in VTAMLST.
  
  V.   The APPL stmt in FNMINIT needs to specify the name used by
  the application to open its ACB. For TSO this can be difficult
  to properly code. Please see the example in NPM Info Apar
  II05344 if NPM is not collecting session data for only a
  particular application, especially TSO.
  
  VI.  NPM's Dynamic Configuration Support (DCS).
       Starting with NPM release 5, DCS feature allows an NCP to
  be defined to NPM at any time, even redefined, without
  requiring NPM to be stopped and restarted. When NPM parses an
  NCP command, it reads the VTAMLST member and NCP RRT. NPM no
  longer creates an NPM RRT during NCP generation. NPM still comes
  with an FNMNDFGN module, whose sole function is preventing NDF
  from terminating abnormally if it encounters any NPM keywords
  (such as NPM.SPEED) in the NCP definition statements. Please see
  NPM INSTALLATION manual, 'Defining NCP Resources to NPM' section
  for details.
       The NCP statement in pre-release 5 NPM was renamed the NCP
  command and was moved to FNMSTRT. If the NCP's PUNAME is
  different from the NCP load module name (NEWNAME), both names
  must be coded on NPM's NCP command.
  
  VII. Please follow steps listed in NPM Info apar II06357 for a
  discussion on properly tuning NPM's BUFSEGS and FILEBUFs. Also
  see Chapter 10 in NPM INSTALLATION manual and Chapter 12 in NPM
  CONCEPTS AND PLANNING manual for more tuning information.
  Following these steps will reduce the likelihood of suffering an
  ABENDU0001 (out of Bufsegs) or ABENDU0019 (out of QCBs) or
  ABENDU0034 (out of TPRBs).
  
  VIII. MSGFNM667W '<file name> Not Available' will occur when
  NPM's BSAM files (FNMLOGx and FNMVLOGx) are not empty and have
  DISP=SHR specified in NPM's startup JCL. Make sure files are
  empty before starting NPM or that DISP=MOD is specified. See NPM
  info apar II03725 for more information on both suggestions.
  
  IX.  Red Books.
       IBM's International Technical Support Center's NPM manuals
  are very helpful. The following Red Books describe the new
  functions in NPM and give samples and user scenarios:
       NPM V1R4 NEW FUNCTIONS: Performance Alerts, Netview Synergy
  Interface, NTRI support.  GG24-3532.
       NPM V1R4M1 and V1R5 New Functions: X.25 support (NPSI, XI,
  NEO resources), Batch Reports, Console Support, Lan Bridge
  Support, NPM Initialization Program, and Dynamic Configuration
  Support.  GG24-3681.
       NPM V1R5M1 and V1R6 NEW FUNCTIONS: Session Alerts, Frame
  Relay (DTE and DCE) support, Ethernet support, Lan Segment
  support, Model 3746 Expansion unit (ODLC and ESCON) support,
  Enhancements to NPM Initialization Program, VTAM Session
  Collection Performance Interface, First Failure Support
  Technology.  GG24-3989.
  
  X.   NPM's Publications.
       NPM's manuals have been changed. New manual for NPM r6,
  NPM CONCEPTS and PLANNING (GH19-6906), contains a lot of
  information previously found in NPM INSTALLATION manual. NPM
  REPORTS and RECORD FORMATS manual (SC31-6147) has been enhanced
  with section 'New and Modified Record Data Sections for Release
  3 through Release 6'. Very useful in determining which sections
  may have changed from release to release.
       All NPM publications contain a vertical line on the left
  side to denote changes to the text from the last revision of the
  manual. Most NPM publications contain a 'What Is New In This
  Book' section that will describe the major changes for that
  revision level of the manual.
       The Command Reference was consolidated into the NPM
  INSTALLATION manual, in Appendix B. All the NPM initialization
  statements are listed in Appendix A and examples are included at
  the beginning. Please note that the only two statements which ca
  NOT be coded in FNMINIT are OPERATOR (which is coded in FNMOPER)
  and PROFILE (which is coded in FNMPROF).  Both sections list the
  items alphabetically.
  
  XI.  NPM Initialization Program (NIP).
       The NIP was completely re-written in release 6 and has many
  usability enhancements over the first version of NIP included in
  release 5 of NPM. The NIP allows NPM to be installed and started
  without having to manual code the initialization parameters.
  Please see NPM CONCEPTS and PLANNING, NPM INSTALLATION and
  CUSTOMIZATION, and NPM V1R5M1 and V1R6 NEW FUNCTIONS manuals for
  details.
  
  XII. Hardware and Software Requirements.
       NPM CONCEPTS and PLANNING manual, chapter 7, tables 9 and
  10, list the hardware and software required for various NPM
  functions. For instance, NPM ETHERNET performance support
  requires NCP V6R2.
       Not mentioned but needed are PDF version 3 (for NIP) and
  REXX (for NIP and LAN data collection).
  
  XIII. NPM Batch Reports Customization.
       NPM REPORTS and RECORD FORMATS manual for release 6
  includes a new chapter (chap4) detailing how to customize NPM's
   FNMREPRT reporting program.
  
   XIV. First Failure Support Technology (FFST).
        Message CSV003I 'Module EPWPINIT Not Found' is issued when
   NPM V1R6 is started if FFST V1R2 is not installed. The message
   can be safely ignored. Please contact your IBM marketing
   representative to inquire about installing FFST on your system.
   FFST will allow NPM to collect an NPM dump, needed for problem
   resolution, on the first occurrence of any NPM logic error.
   FFST is FREE for MVS/ESA customers.
  ****************************************************************
  
  Please see Info apar II06826  which contains volume 2 of the
  NPM r6 Migration Package for further hints and tips.
  
  ****************************************************************
  Keywords: NPMINFO MIGRATE MIGRATION MIG R160 INSTALL
            INSTALLATION APPLY 566533301 160 hnr1160
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• NETVIEW PERFORMANCE MONITOR R6
  

APAR Information

• 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