New Features

The following updates were made to nwmip after the 12.2 GA release:
The following updates were made to
CA NetMaster NM for TCP/IP
after the 12.2 GA release:
Use this link to view the PTF numbers for each new feature in this article. The PTFs in this link are updated programmatically so you always have access to the current New Feature PTFs.
2
SmartTrace Supports Limiting Size of Traced Packets (LU02699, LU02700, and LU02701)
The SmartTrace feature in CA NetMaster NM for TCP/IP has been enhanced to allow you to save space by limiting the size of collected packets.
The size limits are made possible by two new Packet Analyzer parameters in SOLVE SSI:
  • The parameter PATPSZLIM  (Default Packet Size Limit) sets the default size for the packet size limit in a trace definition. Its value range is 192 to 1920.
  • The parameter PAMTPSZLIM (Maximum Packet Size Limit) sets the maximum size you can specify as the packet size limit. Its value range is 384 to 1920.
The default value for each new parameter is 1920. No action is required to accept the default values.
In CA NetMaster NM for TCP/IP, the default packet size limit defined in SOLVE SSI is displayed in a new
Packet Size Limit
field in two locations:
  • SmartTrace: Tracing Options
    parameter group: You can edit the value here to change the default packet size limit for all traces controlled by the parameter group.
  • SmartTrace:
    [
    Trace type
    ]
    Trace Details
    panel: You can edit the value here to change the default packet size limit for a specific trace.
Values must fall within the ranges defined by the new SOLVE SSI parameters.
A z/OSMF Configuration Workflow is now Available for NetMaster Products (LU02872)
Systems Programmers, Security Administrators, and anyone responsible for managing the configuration of z/OS systems can now use a z/OS Management Facility (z/OSMF) workflow to configure NetMaster products. A z/OSMF workflow allows you to configure a software product instance with less effort and in less time. And, less mainframe expertise is needed. The workflow guides you through the configuration process and automates product configuration. This approach significantly reduces the time that is required to perform configuration tasks. For more information on using a z/OSMF workflow to configure NetMaster products, refer to the Configure CA NetMaster Products Using a z/OSMF Workflow installation topic in the CA NetMaster Shared Content Library.
Additional Certificate Attributes Display for IKE Tunnel Endpoints (LU01517, LU01518, and LU01519)
NetMaster now displays additional certificate attributes for Internet Key Exchange (IKE) tunnel endpoints. On z/OS v2r5 and later, the NetMaster /IPSEC.K display now includes:
  • Local & Remote certificate expiration date
  • Local & Remote certificate serial number
  • Local & Remote subject distinguished name
  • Local & Remote issuer distinguished name
When replacing certificates, Network Administrators and Network Security staff can use these attributes to more easily identify which certificate an IKE tunnel uses for authentication.
Support for the IBM Function Registry for z/OS is now Available (LU02255, LU02256, LU02257, and LU02369)
Broadcom mainframe products that use Continuous Delivery (CD) can now use the CA Common Services for z/OS (CCS) Feature Registration Service (FRS). Through CAIRIM, FRS allows products to register with the IBM Function Registry for z/OS. The IBM Function Registry for z/OS provides a simple way for customers to gather information about their NetMaster installations. Registry information includes the release and maintenance level, available features, and status, use count and the LMP key for each feature. To enable the registry, apply feature PTFs LU02255, LU02256, LU02257, and LU02369. Ensure that you have version 15.0 of
CA Common Services
for z/OS, and that maintenance PTF LU01130 has been applied. For more details on using the registry, refer to the View z/OS Function Registry Data topic.
Use of Application Transparent Transport Layer Security and Keyrings is now Supported by the CA NetMaster API Service (LU01020)
The CA NetMaster API Service Portal installation now supports the use of the AT-TLS protocol for secure HTTPS connectivity. AT-TLS is beneficial because it encrypts and decrypts data based on a Policy Agent that can manage settings for multiple applications. This is more efficient than defining and managing individual certificates for multiple applications. In addition, SAF keyrings can now be used by the CA NetMaster API Service. Keyrings enable you to define and administer multiple certificates from a single point, making it easier to secure your z/OS environment. Refer to the CA NetMaster API Service Configuration File topic for sample configuration files using AT-TLS and for a list of SAF Keyring properties.
Support for Version 2 of the SMC-D Protocol is Now Available (LU00870 and LU00889)
CA NetMaster NM for TCP/IP now supports version two of the IBM Shared Memory Communications - Direct Memory Access (SMC-D) protocol.  Support for version two provides NetMaster users with more detailed information when viewing SmartTraces, connection lists, and device link lists. Specifically, the following panels display additional SMC-D detail:
  • The
    Connection Detail
    panel (type
    SD
    next to a connection list item) 
  • The
    SMC-CLC
    section of the
    SmartTrace Expanded Packet Display
    panel
  • SMC-D type interface details, accessed from the
    Device Links List
    (/DEVLINKS DL) panel
For additional details, refer to the online (3270 interface) help.
A New REST API is Available for CA NetMaster NM for TCP/IP (SO12879, SO15811, and SO15812)
The CA NetMaster API Service is now available to NetMaster customers. The CA NM API Service is a NetMaster suite microservice that leverages the Open Mainframe Project Zowe™ Spring Boot REST API SDK. The API provides NetMaster customers with an open and standard interface to network management data collected by NetMaster. The initial release provides access to connectivity data from CA NetMaster NM for TCP/IP.  By providing an easier way to access and customize the display of mainframe connectivity data, the API expands the troubleshooting and response capabilities of network administrators and information security personnel.
  • The API can be used in a standalone way to quickly summarize and report on connectivity information.
  • The API enables the CA NetMaster Web Portal, a new web interface that is also available in this release. See the next note for more information.
  • The API can be used to retrieve NetMaster data and display that data in an existing third-party data portal.
Information for installing and using the API is included in the CA NetMaster NM for TCP/IP documentation:
A New Web Interface is Available for CA NetMaster NM for TCP/IP (SO16068 and LU00880)
The CA NetMaster Web Portal (NM Web Portal or Web Portal) is now available to NetMaster customers. The NM Web Portal provides a single point from which to access critical NetMaster tools and services. Its initial release features the Security view. The Security view gives information security and network management staff a single-pane reference from which to view mainframe connectivity information. The CA NM Web Portal uses the CA NetMaster API Service to retrieve data in a highly secure and flexible manner. Through future release 12.2 PTFs, the CA NetMaster Web Portal will offer all of the tools and services that are currently provided through Mainframe Team Center - Network Management (MTC-NM). And, ultimately, the CA NM Web Portal will replace MTC-NM. Until the Web Portal replaces MTC-NM, both applications will be available. Information for installing and using the CA NM Web Portal is included in the CA NetMaster NM for TCP/IP documentation:
The TCP Listener Detail View Now Includes Additional Information (SO15836 and SO15837)
In order to provide NetMaster users with a comprehensive view of TCP Listener activity, the TCP Listener detail view (SD) now displays the entire set of information that is available from IBM's EZBNMIFR interface. The additional information includes DVIPA options, Shared Memory Communication (SMC) configuration and values, Share Port information, additional status flags such as SDquiesce and ConnFlood, and values associated with the Workload Manager (WLM). For descriptions of the additional fields, refer to the online (3270) help.
New Link Failure Alerting Options are Available (SO15626)
The $AM Alerts parameter group now includes a new option,
Link Failure Alerts
. It provides organizations with additional alert management options in response to inactive region links. Previously, if a failed link was reactivated, the alert closed automatically
only
if the failure was part of a normal shut-down. Any other alerts related to linked region failures had to be closed manually, following reactivation of the link. With the new
Link Failure Alerts
option, all alerts can be set to automatically close following reactivation of the link.  There are three alerting options:
  • ON (default) - Severity 3 alerts that are raised as part of a normal shut-down automatically close when the region link reactivates. Severity 1 alerts that are raised for non-intentional shut-downs do not automatically close.
  • OFF - Alerts are not raised when region links become inactive.
  • AUTO - Severity 3 and severity 1 alerts are both automatically closed when the region link is reactivated.
Refer to the online help for more detail.
EXPORT and IMPORT Commands are Now Available from the TCP/IP: Application Name Definitions Panel (/IPAPPLS) (SO15217)
On mainframe networks, business application name definitions are often shared across multiple LPARs, and have a common shared workload. To promote consistency and standardization, it is advantageous for multiple systems (in a SYSPLEX for example) to share a common set of application name definitions. To more easily facilitate the sharing of business application name definitions across multiple LPARs, the necessary EXPORT and IMPORT facilities are now available as primary commands on the
TCP/IP : Application Name Definitions
panel (/IPAPPLS). For more detail on the use of the EXPORT and IMPORT commands, refer to the online (F1) help and to the Setting Up the Packet Analyzer topic.
A NetMaster zFS Mount Point is no Longer Required for Unix System Services (USS) Commands (SO15227 and SO15228)
Previously, NetMaster installations required the availability of a zFS mount point for USS support (specified in /PARMS ZFS). In NetMaster installations, this location was provided in the CC2DZFS dataset. If the mount point was incorrect, or CC2DZFS was unavailable for any reason, users would receive error messages. With this change, users no longer must ensure that the mount point is correctly specified and that CC2DZFS is available. Now, the installation process dynamically creates the location path in the /tmp directory, the /PARMS USS default location. The /tmp directory contains a Unix socket and a link entry for the NM129 file, and automatically enables communication between the region and USS. Creating the mount point is no longer necessary to enable USS commands.
If you are using a web-enabled product such as MTC-NM, you must create and verify this mount point. Refer to the Prepare to Start Your Products installation article for more detail.
An Enhanced Security Level Event Detector (TCPSECE) is now Available (SO15088)
The new
TCP Security Protocol Enhanced
event detector (TCPSECE) is now available for NetMaster customers. TCPSECE
does not
replace the original
TCP Security Protocol/Cipher usage
event detector (TCPSECLV). However, because TCPSECE provides greater functionality and flexibility, it is preferable to use for for developing new event detectors. The original TCPSECLV detector monitored connections from all sources for a specific protocol. TCPSECE provides additional criteria that enable an organization to considerably narrow event detection, as needed for its environment. For example, an organization that operates in a single "mixed" environment, where internal jobs run alongside external jobs, can now specify port numbers and host addresses to exclude the monitoring of internal jobs. This added capability provides your organization with greater monitoring precision and more meaningful alerts. Specifically, the new TCPSECE event detector includes the following enhancements:
  • When you specify a protocol in the
    Protocol Name
    field, the event detector can monitor either for the entered protocol plus any lower versions (e.g., TLSv1.2), or for only the specified protocol (e.g., TLSv1.2e). This change enables greater granularity in event detection and alerting.
  • None
    (unsecured) is now a choice in the list of available protocols (Protocol Names). This option enables Network Security Administrators to focus specifically on unsecured connections.
  • The
    Cipher
    field was split into two fields -
    Cipher Code
    , and
    Cipher Suite
    . The addition of Cipher Code allows you to enter either the precise Internet Assigned Numbers Authority (IANA) hexadecimal equivalent to your cipher suite, or the cipher suite itself. Entering a cipher code is useful in cases where the manufacturer name for the cipher suite does not precisely match the standard name. Entering the cipher code ensures that the event detector does not miss any events and that you do not miss any alerts due to a non-standard cipher suite name.
  • Five optional fields -
    Task Name
    ,
    Local Host Address
    ,
    Local Port Number
    ,
    Remote Host Address
    , and
    Remote Port Number
    - were added to the available criteria. A Network Security Administrator can now narrow alerting down to only the information necessary to establish and enforce security policies.
For more details, refer to the Use zERT Data to Verify That Incoming Connections Adhere to Security Policy topic and the online help.
Although possible, Broadcom does not recommended simultaneous use of TCPSECE and TCPSECLV event detectors. Doing so could result in unexpected alerts. For example, if a TCPSECLV detector has the same criteria as a TCPSECE detector, you will receive two alerts for any matching event.
Connection Detail Panels Updated to Display All Available Fields (SO15249 and SO15250)
The TCP/IP Connection Detail Panels, which are accessed which are via the
SD
action on a connection list, have been updated to display additional fields provided by the IBM EZBNMIFR interface. These fields provide organizations with additional useful information to use in diagnosing and resolving connectivity issues, and appear for all connections except for those with a status of LISTENER or UDP. The new fields are:
Ancillary Queue
,
ATTLS Session Id
,
Auto Delay Ack?
,
Bulkdata Interface
,
Delay Ack?
,
Receive Right Sizing
,
Receive Window
,
Send Right Sizing
,
Send Window
,
SMC-D Cached?
,
SMC-D Reason
,
SMC-D Status
,
SMC-R Cached?
,
SMC-R Reason
,
SMC-R Status
,
SMC Local Buffer
,
SMC Local Link
,
SMC Remote Buffer
,
SMC Remote Link
,
Time Stamp
,
Time Stamp Age
, and
Trusted Partner
. For descriptions of the individual fields, refer to the online help in the 3270 interface.
Trace Duration Can Now be Specified as a SmartTrace Option (SO14612).
When defining SmartTrace details, you can now specify a maximum active time-frame in seconds in the new
Trace Duration
field. Trace Duration enhances SmartTrace precision by allowing you to set an upper time limit on how long the trace is active. You do not have to set the limit solely based on the number of packets (Trace Limit). Trace Duration allows for more efficient diagnosis and resolution of network issues by allowing you to restrict the amount of information in a trace. The Trace Duration option also enables greater precision and efficiency in cases where automation has been defined to activate SmartTrace in response to a network event. In such a case, you can use the Trace Duration value to ensure that automatically initiated traces do not exceed the Trace Duration value. If you specify both a Trace Limit and a Trace Duration, the trace ends when it reaches the first of the two limiting values, either the maximum number of packets or the maximum time-frame.
Round Trip Time (RTT) and Round Trip Time Variance (RTTV) are Now Available as Connection Event Detector Criteria (SO14697).
When defining Connection type event detectors (CONNECT), you can now specify two additional criteria for alerting and actions:
  • RTT Over
    - The
    RTT Over
    field tells the Connection Event Detector to trigger an alert or initiate an action when the round-trip time for the connection event is greater than the RTT value that you enter.
  • RTTV Over
    - The
    RTTV Over
    field tells the Connection Event Detector to trigger an alert or initiate an action when the round-trip time variance for the connection event is greater than the RTTV value that you enter.
This enhancement provides you with an additional level of precision in troubleshooting and resolving network connectivity issues.
New Ability to Search by and Display Round Trip Time (RTT) and Round Trip Time Variance (RTTV) for Connection Events (SO14384)
To help you better understand network performance, the
Search Connection Events
and the
All Connection Events
panels (/IPHIST.B) now include round-trip time (RTT) and round trip time variance (RTTV).
  • When you select
    List All Connection Events
    ,
    RTT
    and
    RTTV
    appear as column headings in the table display.
  • When you select
    Search Connection Events
    ,
    RTT
    and
    RTTV
    are available as search criteria. When you specify RTT and RTTV values as search criteria, the search results display any connections with a value greater than the value(s) specified.
New Ability to Monitor IP Growth and Traffic by Application (SO14247 and SO14248)
The IP Growth Tracker was enhanced with the ability to track IP growth by application (/IPGTA). With this feature, you can now monitor the growth of business applications that are defined in /IPAPPLS. Network administrators now have another tool to assess their current network based on historical data, as well as to plan for network growth.
New Option to Override the Default Directory used by NetMaster in Unix System Services (USS) (SO14011 and SO14010)
The
$NM USS
parameter group has been updated with a new field,
zFS Path for Sockets
. The zFS Path for Sockets entry sets the Unix path name for Unix sockets that are used for inter-process communication. The path that is specified must be accessible by the uid of the region. Specifying the path overrides the default
/tmp
path, and allows a user to customize their environment, as desired.
The updated path goes into effect at the next initialization.
New Continuous Delivery Numbering Standard
PTFs SO13476 and SO13477 establish a new Continuous Delivery numbering standard for the NetMaster 12.2 GA pax. It applies to all generally available NetMaster products and follows the ISO standard of the form
vv.rr.mm
where:
  • vv indicates the version (major) level of the deliverable
  • rr indicates the release (minor) level of the deliverable
  • mm indicates the level set number
With this implementation, there are corresponding changes to the user interface:
  • The Level in status messages changes from the GA pax release year and month, i.e.,
    1904
    , to
    00
    .
  • The
    Product Component Software Levels
    panel (/LEVELS) now includes a
    Level Set
    column with a value of
    00
    .
  • The
    System Services Release
    on the
    System Profile
    panel ($$SYSPRO) displays with the level set value
    00
    rather than the GA pax release number
    1904
    .
  • N11414
    status messages and the
    N00503
    and
    NS1001
    initialization  messages all display with the level set value
    00
    rather than the GA pax release number
    1904
    .  See the CA NetMaster Messages documentation.
  • OPS/MVS SSM messages display with the level set value
    00
    rather than the GA pax release number
    1904
    .
The EXPORT Command is Now Available from Automation Services Reporting Lists
PTF SO13457 enables the EXPORT command on search result lists generated from the
Automation Services: Reporting
panel, specifically the 
Browse
options (/ASADMIN.R.B). The EXPORT command sends search results to a sequential (flat) file that can then be imported (IMPORT) into a different RAMDB, using the /RAMUTIL panel.
The syntax of the command is
EXPORT
dataset name
, and this data set must already exist as a sequential file with a record length of at least 80 characters. For a video demonstration of this feature, click the following link: Feature Demo Video: EventView and ResourceView - Search and Export Enhancements
$$SYSPRO USAGE Now Tracks MTC - Network Management Web URLs
PTF SO13220 enhances the $$SYSPRO function usage reporting feature with the inclusion of MTC - Network Management web URL tracking. The additional usage data provided by this update, in addition to expanding overall usage reporting, enables you to differentiate between the use of the mainframe interface and the web interface for various functions. Refer to the earlier "New Function Usage Reporting Parameter" release note for an overview of this functionality.
SmartTrace Now Offers the Ability to Merge Saved Traces
PTFs SO12840 and SO12842 add trace merging functionality to the SmartTrace feature in CA NetMaster NM for TCP/IP. Trace merging allows you to diagnose network issues from the perspective of both the originating and receiving systems, without having to switch back and forth between multiple systems and packet lists. The new trace merging enables you to more easily locate and troubleshoot cross-system issues. To use the merge feature, enter
M
for two traces on a multi-system Saved Traces List. The Merged Packet List displays a time-ordered, color-coded view of the packets from the traces. For usage details, refer to the Merge Traces article. For a video demonstration of this feature, click the following link: Feature Demo Video: Merge Saved Traces
CTRACE Now Supports Data Tracing
PTFs SO12583 and SO12584 update the Component Trace (/CTRACE) option to support data tracing. This key enhancement enables you, when AT-TLS is in use and the
CtraceClearText
parameter is set to
On
, to perform a data trace and review application data flows in clear text. In CA NetMaster NM for TCP/IP, data traces are stored as packet traces with an emulated IP and protocol header. The new
Trace Type
field for the emulated packets displays a value of
Data
in the Formatted Packet Display. For more details, refer to the "Using CTRACE" articles in this documentation.
New Ability to Restore Alerts at Region Start-up
PTF SO12615 introduces the capability to restore open alerts when you restart a region. Typically, when you restart a region, any open alerts in the Alert Monitor panel are lost. To help you avoid lost alert information, a new control,
Restore Alerts at Restart?
, was added to the $AM ALERTHIST parameter group. When set to YES (the default is NO), open alerts are restored automatically at region restarts; the alerts then reappear in the Alert Monitor, rather than the Alert History.
New Ability to View X.509 Certificate Details Via SmartTrace
PTFs SO11535 and SO11536 update the NetMaster SmartTrace packet tracing functionality with the ability to view X.509 certificate details in TLS handshake records. This feature provides you with the benefit of being able to verify that the certificates you expect to be in use, actually are in use. The functionality is available when you select an appropriate packet from the Packet List panel.
Packet decoding works within standard constraints. If a certificate is larger than 1950 characters, SmartTrace decodes the packet and displays details for as much of the certificate as possible. Similarly, certificates that span more than one packet display details only in the first packet.
/IPAPPLS - New Write zERT Records Option
PTFs SO11462 and SO11463 update CA NetMaster NM for TCP/IP with the new Write zERT Records option. In previous releases, zERT records were written according to the setting of the Write TERM Records option - either WRITE, NOWRITE, or DEFAULT. Now, when adding or updating a TCP/IP application on the /IPAPPLS - Maintain Application Name Definitions panel, Write zERT Records appears as a separate processing option. The Write zERT Records option allows you to specify whether zERT records are written to SMF, independent of any processing selections. This capability allows for greater granularity in reporting and analyzing TCP/IP SMF records. To activate this feature, update CA NetMaster NM for TCP/IP with the specified PTFs, and restart both the SOLVE Subsystem Interface (SSI)
and
the applicable region.
The Write zERT Records option initially defaults to the value of the Write TERM Records option, namely, how it worked before the update. The default setting ensures minimal disruption to your current processes.
New OSA-E7S Support
PTF SO10322 updates CA NetMaster NM for TCP/IP with support for OSA-E7S monitoring. Use the OSA Configuration command (CF) to display information that is related to OSA 7 hardware. For more information related to the displayed configuration attributes, refer to the IBM osaexp7.mib file. You can find this file as a download on the "OSA-Express Direct SNMP MIB" article on the IBM Support site.
When the OSA Configuration command (CF) is run, the last five fields of the output under
Details for port N
>
Receive Counters
do not display. The display error is not a NetMaster issue. When the CF command runs, the IBM OSA SNMP subagent IOBSNMP task reports an IOB010E error message. The problem is being investigated by IBM.
New Function Usage Reporting Parameter
PTFs SO10730 and SO10850 update
CA NetMaster NM for TCP/IP
with the ability to monitor function usage. More specifically, the parameter displays how many times a function has been accessed over a specified time period by product users. The new $NM FUNCTIONUSE parameter group enables you to turn the feature on or off, and to set the data retention period for the reporting. The $$SYSPRO USAGE command and its variants provide the function reports by user, over a rolling time-frame. Reports are stored solely on your system, with the intent of allowing you to better understand how NetMaster is used within your environment. If desired, reports can be shared with the NetMaster development team, who will use the information to troubleshoot issues and better understand customer use patterns; in turn, this will ultimately allow for better prioritization of future development. This feature is enabled by default, and can be disabled by changing the
Monitor Function Use?
setting to
NO
. Refer to the Monitor NetMaster Function Usage topic for more detail. In addition, the HOLDDATA section of the PTF reiterates the information here, and provides instructions on how to ensure that the Customizer INIFILE is regenerated, if used.
New Multi-system Trace Functionality
PTF SO10524 updates /SMART options L, LA, and LS to support multiple Link Name selections. The  resulting lists include traces from all of the selected regions. Refer to the Using Smart Trace topic for more details.
Support for Generic Hosts and Non-standard Port Usage
PTFs SO10212 and SO10213 update the SNMP Host Details Definition (/IPADMIN.S) in CA NetMaster Network Management for TCP/IP with the following features:
  • Support for generic hosts for SNMPv3 with user-specified keys
  • Support for non-standard port usage when a site is not using port 161
Documentation
All CA (Broadcom) documentation is now located on the new Tech Docs Portal, which is structured in the same way as the former documentation repository, or DocOps. In addition to being able to search for and navigate to your product, Tech Docs provides a single point of access to all archival/legacy documentation, through the
Legacy Bookshelves and PDFs
button at the bottom of the window.
IP Filters Display Updated to Include SORT Functionality for the Matched and MisMatched Columns
PTF SO09442 updates the
IP Filters
display (/IPSEC.F) with SORT functionality for the
Matched
and
MisMatched
columns.
TLS v1.3 Protocol Support
With z/OS V2R4, the IBM Communications Server TCP/IP stack was updated to support TLS protocol v1.3. PTFs SO09966, SO09967, and SO09968 update NetMaster NM for TCP/IP with TLS v1.3 support for /SECURE displays and Connection information output.
New IPEVENT Burst Limit and Maximum Record Limit Parameters for the IPLOG
PTFs S010120 and S010121 update NetMaster NM for TCP/IP with two new IPEVENT parameters for the IPLOG: Burst Limit and Maximum Record Limit. The burst limit parameter prevents an excessive number of events from overwhelming the IPLOG. The maximum record limit sets an upper limit on the size of the IPLOG.
  • If incoming events exceed the burst limit value before the cache is emptied, IP logging stops, and no further events are processed until the cache is emptied and the burst has finished.
  • If the IPLOG reaches its maximum record count, IP logging stops and resumes after the archive process has removed records from the IPLOG, which prevents unnecessary CPU utilization due to IPLOG resizing.
By default these parameters are set to their maximum values of 10,000 (burst) and 4,000,000 (records). These values can be modified from the IPEVENT parameter group. Reducing the default maximums helps to protect the IPLOG from being overwhelmed by an excessive burst of records, or a large overall number of event records. Accordingly, the new IPEVENT parameters help to reduce high CPU utilization and other problems.
/IPCON EXPORT Command Support for Connections Lists
PTF SO09807 adds support for the EXPORT command from the TCP/IP:Connections (/IPCON) connections list command line. The EXPORT command uses Printer Services to print the contents of the current Telnet, FTP, or Connection List screen. The screen information is written in comma-delimited format. NetMaster processes the print request in the background, and when the request is completed, NetMaster a writes a Printer Services message to the Activity Log.
New System Field on the Event Status Panel
PTF SO08877 enhances the Event Status panel with a new
System
field that allows you to select from a list of systems when viewing Ruleset Status, Active Timers, or EventView Variables. This enables you to quickly view event information without having to log in to each individual system.
EventView is an option only for the CA NetMaster File Transfer Management and CA NetMaster Network Automation products. Customers who use either of these products with CA NetMaster Network Management for TCP/IP can use EventView functions such as Timer Rules.
New zIIP Usage Health Checks
PTFs SO09323 and SO09324 update CA NetMaster Network Management for TCP/IP with two new health checks that report on zIIP utilization: NM_ZIIP and NM_ZIIPSSI.
  • NM_ZIIP reports on product region usage of zIIP processors.
  • NM_ZIIPSSI reports on SOLVESSI usage of zIIP processors.
Parameter Updates for zIIP Utilization
In conjunction with the new zIIP health checks, the following CA NetMaster parameters now have a default setting of BEST, which tells the system to use zIIP processors when they are available:
  • XM Product Region JCL parameter
  • PAEXMODE Packet Analyzer parameter for use with the SOLVE SSI (for CA NetMaster Network Management for TCP/IP only)
Updates to SmartTrace Packet List to Support Absolute Time Display
PTF SO08461 updates CA NetMaster NM for TCP/IP SmartTrace to show the actual time of the packet capture on the 3270 SmartTrace:
Packet List
panel. Use PFKey F4 to toggle between absolute and relative time.
Event Detector Enhancements
PTF SO08206 provides updates for
CA NetMaster NM for TCP/IP
Event Detectors. The following enhancements have been made:
  • The CONNECT detector has been updated to add extra criteria: Buffered In Over, Buffered Out Over, Retransmits Over, and DupACKs Over.
  • The LISTENER detector has been updated to use IBM program EZBNMIFR instead of SNMP.
  • The $IP IPTIMING Customizer parameter group has been updated to allow a minimum polling time of one minute instead of five for the CONNECT and LISTENER detectors. This is possible because both detectors now use the EZBNMIFR program.
  • The TCPSECLV detector has been updated to issue one alert per remote address.
  • Various Event Detector-related help panels have been updated to present content in a consistent manner.