Customize
NetMaster NM for TCP/IP

After you have performed the common customization tasks for
NetMaster NM for TCP/IP
, perform the following unique customization tasks for the product:
nwmscl122
Required roles: systems programmer
Update and Review the Unique Fast Customization Parameters for
NetMaster NM for TCP/IP
When you performed the common customization tasks for
NetMaster NM for TCP/IP
, you updated and reviewed the common fast customization parameters for all
NetMaster
products. Next, update and review the unique fast customization parameters for
NetMaster NM for TCP/IP
, as follows:
Implement the TCP/IP Sockets Interface Parameters
This procedure enables TCP/IP support. Access to sockets interfaces requires UNIX System Services authorization, which should have been done via the section Prepare IBM Communications Server (TCP/IP and FTM Only).
  1. Enter
    U
    next to the TCP/IP Sockets Interface parameter group.
    The first SOCKETS - TCP/IP Sockets Interface panel appears.
  2. Tab to the
    TCP/IP Interface Type
    field, and enter the required value.
    Only one type of TCP/IP software can be configured as the sockets interface in each region.
  3. Specify an
    Inbound Connections Port
    The Inbound Connections Port field contains a default port number. The port number must be unique for each system. If another region on this system is already using that number, update the field.
  4. Specify the
    Retry Interval
  5. Press F8.
    The second panel for this parameter group appears.
  6. Enter the
    TCP/IP Job Name
    or the
    TCPIP.DATA.DSN name
    .
  7. Enter the
    Work Data Set Name
  8. Press F6 (Action) to set the specified values and start the interface.
  9. Press F3 (File) to save your settings.
  10. Press F3 (Exit).
    The System Parameters panel appears.
Meet Prerequisites for Using Web Interfaces
The WebCenter component was deprecated in April of 2020. Mainframe Team Center for Network Management (MTC-NM), which is documented in this space, is the official replacement for WebCenter. For details, refer to the associated Product Update
If you are using
Mainframe Team Center - Network Management
, instruct all users to take the following actions:
  • Clear the cache of their web browser to prevent them from getting a mix of old and new web files.
  • Disable the pop-up blocker, or define
    Mainframe Team Center - Network Management
    as an allowed website.
Specify Web Interface Parameters
To specify web interface parameters, use the WEBCENTER - Web Interface Controls parameter group in the 3270 interface.
This parameter group, originally designed for WebCenter,  now applies exclusively to
Mainframe Team Center - Network Management
, and the Access WebCenter field now indicates
WebCenter Disabled
.
Follow these steps:
  1. Enter
    U
    next to the WebCenter Web Interface parameter group.
    The
    WEBCENTER - WebCenter Web Interface Controls
    panel appears.
  2. Tab to the
    Web Interface Port
    input field, and enter a unique value.
  3. Complete the fields on the panel.
    For more information, press F1 (Help).
  4. When you have completed all the fields, press F6 (Action) to set the specified values.
    The web interface parameters are implemented.
    Save the location of the generated Access URL. You use this URL to access your product region using WebCenter.
  5. Press F3 (File) to save your settings.
    The Fast Setup panel appears with the Reviewed column marked
    Yes
    for the WebCenter web interface parameters.
  6. Press F3 (Exit).
    You return to the System Parameters panel, and the parameters are implemented.
Update Additional Parameter Groups for
NetMaster NM for TCP/IP
Update the following additional parameter groups for the product, if applicable:
Enable Metrics Feed to
DX Application Performance Management
Perform this task only if you have a
Cross-Enterprise APM
license and you want to feed data to
DX Application Performance Management
from this product region.
The APMEPAGENT parameter group configures the metrics feed to
DX Application Performance Management
.
For information about how to configure
DX Application Performance Management
, see
DX Application Performance Management
.
Follow these steps:
  1. Enter
    U
    next to the APMEPAGENT parameter group.
    The APMEPAGENT -
    DX Application Performance Management
    EPAgent panel appears.
  2. Complete the fields as required:
    • Set the Enable EPAgent Client? field to
      YES
      .
    • Set the IP Addr/Host Name that identifies your Environment Performance Agent.
    For information about the fields, press F1 (Help).
  3. Press F6 (Action) to action the entries.
    The region starts to feed metrics.
  4. Press F3 (File) to save your settings.
    The Complete Setup panel appears.
Implement External Applications Access
Perform this task only if you have installed
NetSpy
and you want to be able to start a
NetSpy
session from your product region.
Follow these steps:
  1. Enter
    U
    next to the $RM EXTAPPLS parameter group.
    The EXTAPPLS - External Applications Access panel appears.
  2. Under NetSpy Application Specifications, enter the NetSpy ACB Name.
    For information about the remaining fields, press F1 (Help).
  3. Press F6 (Action) to action the entries.
  4. Press F3 (File) to save your settings.
    The Complete Setup panel appears.
Implement Links to
NetSpy
Perform this task only if you have installed
NetSpy
and you want to make its data available to your product region.
Follow these steps:
  1. Enter
    U
    next to the $ES NETSPYLINKS parameter group.
    The NETSPYLINKS - Links to NetSpy Applications panel appears.
  2. Enter the ACB name of the
    NetSpy
    X-communication (NSYXNAME). This name is used for the following communications:
    • NetSpy-to-NetSpy communication
    • NetSpy-to-NetMaster communication
    For information about the fields, press F1 (Help).
  3. Press F6 (Action) to action the entries.
  4. Press F3 (File) to save your settings.
    The Complete Setup panel appears.
  5. Press F3 (Exit).
    The System Parameters panel appears.
Discover System Resources
You can discover your system resources using Express Setup.
Express Setup discovers resources and stores their definitions in a system image. Express Setup starts after initial customization has completed.
Express Setup relies on SNMP, name lookup, and Netstat. Ensure that these facilities are configured correctly for the stack that you previously configured.
Express Setup uses SNMP to discover the IP nodes. If you have any special SNMP requirements for IP nodes, define them using the Maintain SNMP Installation Details option on the TCP/IP Administration Menu. The shortcut is /IPADMIN.S. The special requirements can include nonstandard community names or a requirement to use a specific SNMP version.
Follow these steps:
  1. Exit from the System Parameters panel if you have
    not
    already done so.
    The Confirm Express Setup panel appears.
  2. Select IP Express Setup.
  3. Specify the values in the System Image and Version fields. These values default to the local z/OS system name and the next available version number.
  4. (Optional) Configure the $RMEXPR6 control member:
    1. Copy
      dsnpref
      .NMC2.CC2DEXEC($RMEXPR6) into
      dsnpref.rname.
      TESTEXEC.
    2. Update the
      dsnpref.rname.
      TESTEXEC($RMEXPR6) specifications. (For example, comment out the resources you do not need to discover.)
    3. Rename $RMEXPR6, and use this name in the Control Member field.
    For an overview of what resources Express Setup builds when using the default $RMRXPR6 control member, see the online help.
  5. Set Load Image? to
    YES
    .
    This system image is loaded after the discovery has completed.
  6. Set the Create Application Name Definitions? field to
    YES
    .
    When the value is YES, application name definitions are created automatically for important discovered address spaces. You can implement extra application names manually later. For more information, refer to the Implementing topics in the
    NetMaster NM for TCP/IP
    documentation. If you are migrating, set this field to NO and migrate your application name definitions.
  7. Press F6 (Action).
    The Express Setup Status panel appears. This panel reports the progress of the resource discovery and the number of resources successfully discovered.
    Your site configuration determines the duration of this process.
To access Express Setup after your first logon, enter
/RADMIN.AD.I
at the command prompt.
For information about reviewing and administering the resources that Express Setup discovers, refer to the Implementing topics in the
NetMaster NM for TCP/IP
documentation.
Set Up the System Image to Load on Restart
This procedure ensures that a system image is loaded when the region initializes.
Follow these steps:
  1. Enter
    /PARMS
    at the command prompt.
    The Parameter Groups panel appears.
  2. Enter
    U
    next to the $RM AUTOIDS parameter group.
    The AUTOIDS - Automation Identifiers panel appears.
  3. Enter a question mark (
    ?
    ) in the System Image Name field.
    The System Image List panel appears.
  4. Select the System Image and Version you specified during Express Setup.
  5. Press F6 (Action) if the system image is not already loaded.
    F6 (Action) replaces the currently loaded system image. If you do not want to load the system image now, skip this step.
  6. Press F3 (File).
    The system image loads each time the product region starts.
Review Region Status
After you complete the initial product customization, review the status of your region to verify that it is ready for use.
Follow these steps:
  1. Enter /IPTEST at the command prompt.
    A summary of region configuration details appears.
  2. Ensure that the information that appears is as expected based on the customization that you have performed in this section.
    Red text indicates an error, and yellow text indicates a warning.
  3. Address any errors or warnings by reviewing the customization steps that you previously performed to ensure that you have
    not
    missed any steps.
 For more information about how to perform a self-test, see the Administrating topics in the
NetMaster NM for TCP/IP
documentation.
Use Express Setup
Express Setup defines a collection of resources, which is a static snapshot at the time of discovery. The collection is not updated dynamically even if a new resource appears a minute later. To capture new resources, update the collection. Add new resources to the collection (or system image) manually.
Review your monitoring environment over time. Add local knowledge to the monitoring setup. Modify the discovered resources so that you are monitoring only things that are critical to your business. Modify the monitoring of a resource from the IP resource monitor (/IPMON) using the UM line command.
Aim to get your region to satisfy the following objectives:
  • Everything that is monitored is useful so that each alert must be taken notice of and each status change is significant.
  • Only the things you want are monitored, but in depth.
  • The automated actions are targeted and valuable.
Monitoring everything wastes system resources and is distracting -- inconsequential alerts can distract you while causing you to miss the important ones. Removing unnecessary monitoring also reduces the processing that the region has to do.
Express Setup is a process that you run during your first logon to a new region. The process uses rules to discover the IP resources that are present at the time it runs, such as:
  • Address spaces
  • IP nodes within a specified number of hops
  • Defined Open Systems Adapter (OSA)
  • Virtual IP address (VIPA)
  • Enterprise Extender (EE) devices
If requested, Express Setup also defines simple business applications.
What Express Setup discovers can only be a starting point for your monitoring environment. Express Setup does not know your business or your wider network.
Everything Express Setup discovers is placed in a system image. You can have multiple system images, each containing a particular collection of resources. System images are given unique names -- generally the system ID and a version number (for example, SYS1-0001). A region can have only one system image active at a time.
You can rerun Express Setup but only if a major reconfiguration has occurred since the last time it was run. Rerunning Express Setup creates another system image, which has to be reconfigured from scratch. The changes that you made to the existing system image are not propagated to the new image.
For more information, see Implementing.