Description: z/OS® V2R1
Communications Server includes the following enhancements for application,
middleware, and workload enablement:
- API to locate SYSLOGD configuration file - Syslog daemon
(syslogd) processing is enhanced to provide the syslogd configuration
file location and related information. The ability to find syslogd
information helps other programs that need to use the information
that is written to syslogd.
- Real-time application-controlled TCP/IP trace NMI - The
real-time application-controlled TCP/IP trace network management interface
(NMI) is a callable NMI that provides the following information to
network management applications based on filters that are set by the
application:
- Real-time packet trace information
- Real-time data trace information
Each application that uses the NMI can set its own filters
and options to obtain the required data, and the application can request
the trace data at any time.
In contrast, the existing real-time
TCP/IP network monitoring NMI provides similar trace data based on
the global packet trace and data trace settings for the TCP/IP stack.
The application has to wait for a token to retrieve the trace data.
To
provide access to this NMI and to the information that the NMI provides,
you must define new security product resource profiles in the SERVAUTH
class. You can use the DISPLAY TCPIP,,TRACE command to display information
about the applications that are using this NMI and the resources that
are currently being used by the NMI.
- FTP client security user exits - You can control FTP client
commands that are sent to the server or monitor the replies that are
received from the server by using the following two client user exits:
- FTP command user exit – EZAFCCMD. Use the EZAFCCMD user exit to
inspect an FTP command, modify the arguments of an FTP command, reject
an FTP command, or end the FTP client address space before the command
is sent to the server.
- FTP reply user exit – EZAFCREP. Use the EZAFCREP user exit to
inspect the FTP server reply or to end the FTP client address space
after the FTP client receives each line of reply that is received
from the server.
- Simplify FTP transfer of data sets between z/OS systems - z/OS FTP supports getting the attributes of
an MVS™ data set on the z/OS FTP server using the new FTP
command XDSS.
z/OS FTP also
introduces two new FTP subcommands, MVSPut and MVSGet. The MVSPut
subcommand transfers an MVS data
set from a z/OS FTP client
to a z/OS FTP server without
the client user needing to know the attributes of the client data
set. Likewise, the MVSGet subcommand transfers an MVS data set from a z/OS FTP server to a z/OS FTP client without the client user needing
to know the attributes of the server data set. In both cases FTP extracts
the attributes of the source data set, and applies them to the target
host FTP configuration before the transfer.
- Enable DHCP clients on OSA interfaces - You can define
and activate an OSA-Express QDIO interface without specifying an IP
address. Applications that implement a DHCP client, such as IBM® Rational® Developer for System
z® Unit Test feature (RDz-UT), can communicate with DHCP servers to
dynamically obtain an IP address.
- NMI and SMF enhancements for TCP/IP applications - Two
new SMF 119 event records:
- The SMF 119, subtype 71 record contains FTP daemon configuration
data. This record is created during the FTP daemon initialization
when it listens on the listening port successfully for the first time.
A new FTP.DATA statement SMFDCFG is added to control whether to write
this SMF record to the SMF data set.
- The SMF 119, subtype 24 record provides the TN3270 server initial
profile configuration information, as well as information about replacement
of the profile caused by VARY TCPIP,Telnet,OBEYFILE processing. This
record is written to the MVS SMF
data sets.
You can obtain FTP daemon configuration data by using the
following NMIs:
- The TCP/IP callable NMI, EZBNMIFR, by specifying the new request
type, GetFTPDaemonConfig.
- The real-time TCP/IP network monitoring NMI, SYSTCPSM. The SMF
type 119, subtype 71 record for FTP daemon configuration data is available
to this NMI.
TN3270 server profile configuration data can be obtained
through the following NMIs:
- The TCP/IP callable NMI, EZBNMIFR by specifying the new request
type, GetTnProfile.
- The real-time TCP/IP network monitoring NMI, SYSTCPSM. The SMF
type 119, subytpe 24 record for TN3270 server profile configuration
data is available to this NMI.
The new GetTnProfile request for the TCP/IP Callable NMI,
EZBNMIFR, provides complete profile information. Network management
applications can use a combination of the GetTnProfile request and
the new SMF 119 event records that are created during the VARY TCPIP,Telnet,OBEYFILE
command processing to monitor replacements of the Telnet profile settings.
When change was introduced: z/OS V2R1
Reference information: See the following topics in
z/OS V2R1.0 Communications Server: New Function Summary for
detailed descriptions that include any applicable restrictions, dependencies,
and steps on using the functions:
- API to locate SYSLOGD configuration file
- Real-time application-controlled TCP/IP trace NMI
- FTP client security user exits
- Simplify FTP transfer of data sets between z/OS systems
- Enable DHCP clients on OSA interfaces
- NMI and SMF enhancements for TCP/IP applications