Information about some parameters.

Document ID : KB000054001
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

  1. How can the customer find the explanation of the following parameters?

    AOMCMDPF, AOMSUPCH, NSPDEBUG, NSPTRACE, RXDEBUG, SMFIDS, SMFTRACE, SSLDEBUG, SSLPSMAX, SSLTRACE, SYSPGCHK, TNDEBUG, TNGDEBUG and TNGTRACE.
  2. Explanation of each parameter above?

  3. Were the following parameters superseded?

    AOMCMDCH, CMDSTACK, EDITMAXK, LOCKMAX, MAIFILE, MAIFPREF, MAPFILE, MAXPANEL, MAXRUT2, MSRETAIN, M2RETRY, NCLCSAVE, NCLMAXK, NCLPEND, NCLPRSHR, NCLUMAX, NCLXUSER, NMIQLIM, OMLUMAX, PANLPPD, PRIACBNM, RECONN, ROFPAREN, ROFPREFX, RTA480, SYSUDB, TCMDMAX, TPEND, UNSPVPSZ and VTAMAUTH

Solution:

  1. To find an explanation of the parameters listed, you can go to Command Entry and run the command, for example:

    SH SYSPARMS=AOMCMDPF

    This will display:
      ==========================================================================================         CSNM26 (11.36.58)-------- NetMaster : Command Entry  --------Line 4 of 8         SH  SYSPARMS=AOMCMDPF           N22201 SYSPARM   VALUE               SOURCE         NAME/USER    LINKNAME           N22202  AOMCMDPF                     CUSTOMIZER      OPSYSIDS============================================================================================
    ...which shows that this is set via the '$RM OPSYSIDS' Parameter Group in the Customizer. Then if you go to the Customizer ('/PARMS' command), and look at the '$RM OPSYSIDS' Parameter Group, and look for the 'AOM SSI Command Prefix String', and press the PF1 Key, you will see that this is the:

    =====================================================================================
    AOM SSI Command Prefix String - Specifies the character string used as the command prefix when sending commands
    to the region interface from the system console.
    =====================================================================================
    ...and if you then select 'Fields', you will see more information on this parameter:
    =====================================================================================
    AOM SSI Command Prefix String specifies the prefix string to use when sending commands to the region interface from the system console. It provides a shorter method of entering the MODIFY system command from the console. A blank field indicates that you do not want to use a command prefix string.
    Limits: Blank or 1 to 8 characters
    The following characters are valid:
    Alphanumeric: Uppercase A through Z, 0 through 9 National: @ $ #
    Special: ' , . / ( ) * & + - ? < | ! ; % _ > ? : "
    Example: If the string is NM>, you can enter NM>SH USER instead of F so_task_name,SH USER to send a command to the region.
    Important! When selecting a command prefix, ensure that the prefix satisfies the following conditions:

    • It is not a system command (or an abbreviation of a command).

    • It does not conflict with existing prefixes.

    • It is not a subset or a superset of an existing prefix.

    • It does not clash with WTOR reply commands.

      Note: You can view the currently allocated prefixes by issuing an MVS DISPLAY OPDATA command.
      =============================================================================

      This can be done for all the unknown parameters that you wish to know about. When a SYSPARM operand is set by Customizer, it cannot be updated using OCS, Command Entry, or NCL.
      It must be updated using the Customizer to ensure synchronization. Synchronization checks can be bypassed using 'SYSPARMS SYSPGCHK=NO', but this is not recommended except in an emergency, because there is no synchronization with the Customizer.
      +--------------------------------------------------------------+           
      | SYSPARM | Customized Parameter Group | Customizer Parameter|
      |==========+===========================+=======================|
      | SMFIDS | $NM SMF Interface |SMF Record Identifier |
      +----------+---------------------------+-----------------------|
      | SSLDEBUG | CA Engineering SYSPARM setting. |
      +----------+---------------------------------------------------|
      | SSLPSMAX | CA Engineering SYSPARM setting. |
      +----------+---------------------------------------------------|
      | SSLTRACE | CA Engineering SYSPARM setting. |
      +----------+---------------------------------------------------|
      | SYSPGCHK | CA Engineering SYSPARM setting. |
      +--------------------------------------------------------------+
      The SYSPARM 'SMFIDS' is in the Customizer under the $NM SMF Interface Parameter Group, and the specific parameter is 'SMF Record Identifier'.

      The other SYSPARMS, 'SSLDEBUG', 'SSLPSMAX', 'SSLTRACE' and 'SYSPGCHK' are all set at the default value and are not changeable by customers. These sysparms are for internal use by CA Engineering Teams, and can be set or changed by them only, and are specifically used in diagnosing errors and problems within the NetMaster code.

      The difference between SMFID and SMFIDS?
      SMFID and SMFIDS are indeed two separate SYSPARMS and are explained in the online help for the $NM SMF (SMF Interface) Parameter Group, as follows:
      SMF Record Identifier
      SMF Record Identifier (subtype)
      SMF Record Identifier specifies the ID to use when this region creates the following SMF records:

    • ServiceView

    • ResourceView

    • EventView

    • User CPU time accounting

    • User

      These records are written without setting the subtypes flag in the SMF record header.
      The value should not have been used by other third-party products. A value of 0 disables record creation.
      Valid values: 0, 128 to 255

      SMF Record Identifier (subtype) specifies the ID of the SMF record to use when this region creates the following subtypes:
      01 - Audit Record
      These records are written with the subtypes flag set in the SMF record header and use the dynamic, structured format of the record.
      The value should not have been used by other third-party products. A value of 0 disables record creation.
      Valid values: 0, 128 to 255

  2. See the answer to (1.) above.

  3. Yes.