IBM z System z/OS (H21x) FAQs

H210IPZ/TNP210 7.4 (NetEx/IP & TNP) Frequently Asked Questions

Refer to the IBM z System z/OS Support Table for the supported releases of H210IPZ and TNP210. Typically the latest release is the highest numbered version.

Refer to the IBM z System z/OS Support Table for the supported releases of zOS.

Refer to the FAQ on limitations with ordinary address spaces for REUSASID restrictions.

Yes. A software license is required for each LPAR in which H210IPZ is used, and a key is required for each H210IPZ license. TNP support can also be purchased and enabled with a key.

The format of the key has changed beginning with Release 7.1, so a new key may be needed prior to deploying this release. Keys from H210IPZ or H210IP releases earlier than Release 7.1 are not compatible with this release, and will not work. Similarly, a Release 7.4 key is not downward compatible with earlier releases of H210IPZ or H210IP. If upgrading from 7.1 or later, a new key is not needed.

Issue the 'D M=CPU' command on the LPAR where Netex will be running and send the output to support@netex.com, along with your company, contact info, and the product name (i.e. H210IPZ Release 7.4) to request the license key.

The LICCODES file may contain multiple keys. If H210IPZ is installed on multiple LPARs on the same system, and if the PRODCONF and LICCODES files are shared across these multiple LPARs, then keys for all of these instances of H210IPZ can be placed in the same LICCODES file. Each instance of H210IPZ will use the first key found that contains its fingerprint.

If there are multiple keys for the same LPAR, H210IPZ will use the first key found for the LPAR on which H210IPZ is being started, as it sequentially reads the keys from the file. This makes it important to add new H210IPZ keys for an existing LPAR to the front of the file. For example, if a new key is installed that provides a license date extension, or adds a new feature to H210IPZ, adding this new key to the file before the old key ensures the new key will be used rather than the old key.

The LICCODES file may also contain keys in the old format (i.e. pre-7.1 keys), which means the same LICCODES file can be shared for both Release 7.4 as well as with prior releases. If NESi’s eFT213 product is installed, it can also share the same PRODCONF and LICCODES files with H210IPZ.

H210IPZ/TNP210 is distributed by download. Refer to the Release Announcement for instructions for obtaining a distribution.

Issuing the 'D L' NetEx/IP operator command will display the release level and service level.

You may be using very old JCL when running the Configuration Manager. Please follow the instructions in the Install Reference Manual, and use the JCL provided in the H210IPZ distribution.

You may be using very old JCL when running the Configuration Manager. Please follow the instructions in the Install Reference Manual, and use the JCL provided in the H210IPZ distribution.

The order in which paths are generated is related to the order in which ADAPTER statements are specified in the NCT. Paths are generated in the following order: For each Local Host ADAPTER (proceeding from last to first), paths are generated to each Remote Host ADAPTER (proceeding from first to last). For example:

    HOSTA   HOST     TYPE=Linux    MODEL=Fedora
            ADAPTER  MODEL=N130    NETADDR=02 TO=eth0
            ADAPTER  MODEL=N130    NETADDR=03 T0=eth0
    HOSTB   HOST     TYPE=Linux    MODEL=Fedora
            ADAPTER  MODEL=N130    NETADDR=12 T0=eth0
            ADAPTER  MODEL=N130    NETADDR=13 T0=eth0

Paths will be generated in the following order:

        Path 1: 03->12
        Path 2: 03->13
        Path 3: 02->12
        Path 4: 02->13

TNP serves as a NetEx/IP "proxy", for use by NetEx/IP Requester products. Requesters are available on platforms for which there is no host-based NetEx/IP. Examples of Requester platforms are HP Integrity NonStop, HP Integrity OpenVMS, and Bull.

Requesters use a TCP/IP connection to communicate with H210IPZ TNP. TNP uses an intrahost NetEx/IP connection to provide the NetEx/IP services on behalf of the Requester. Prior to H210IPZ TNP, Requesters would use a NESiGate-LO appliance to provide the NetEx/IP services. H210IPZ with TNP eliminates the need for NESiGate-LO.

No. The support provided in Rel 7.4 that allows NetEx/IP to run in a reusable address space requires the Rel 7.4 versions of NXMUIF00 and NXMTERM0 to be used.

When using the TNP feature, a HOST statement should be defined in the NCT that represents the NetEx/IP Requester (which resides on HP Integrity NonStop, Integrity OpenVMS or Bull). The NETADDR specified for the Requester Host should be the same as the OSA NETADDR on the local z/OS host. For example:

***  Local HOST ZOST*ZOST     HOST     TYPE=IBM      MODEL=Z9                  PROTOCOL=2    PROTOCOL=4**        OSA Interface         ADAPTER  MODEL=N220    NETADDR=01                  CHANADDR=0100 T0=UDP_ETH5                  NUMADDRS=4    SMGDREF=00***  Requester host on HP Integrity NonStop (uses OSA as NetEx/IP intrahost**  path to HP NonStop Requester)*TNPNSTOP HOST     TYPE=IBM      MODEL=Z9                  PROTOCOL=2*        OSA Interface         ADAPTER  MODEL=N220    NETADDR=01                  CHANADDR=0100 T0=UDP_ETH5                  NUMADDRS=4    SMGDREF=00

Effective with Release 7.1, SMP/E is no longer used for the installation process. An installation script, contained within a single batch job, is used to allocate and load the distribution libraries, and perform the installation. The H210IPZ downloaded installation file consists of the installation job, along with the H210IPZ distribution libraries, in TSO TRANSMIT format.

Yes, all of the documented z/OS rules are followed when determining which stack to use.

Yes. Refer to the H210IPZ Installation Manual for examples.

The following initialization statements are legacy, and are no longer used:

TRANLIM, TRANMAX, SET NAVGAG ON, ADMTM, ATNIDX

They are not needed effective with the Release 7.1 NTXINIT initialization file.

Yes. Toleration support for reusable address spaces was added to Release 7.2 with patch 5215 and carried forward into Release 7.3 and 7.4. When running NetEx/IP on z/OS V1R12 (or later) systems, and REUSASID(YES) is specified in IEASYSxx, Release 7.4, Release 7.3, or Release 7.2 (with patch 5215) MUST be installed.

Failure to use the correct level of NetEx/IP when reusable address spaces are in use will result in S0D3 abends in other applications and/or system components.

Yes. The support that allows Netex to run in a reusable address space was added in Release 7.4.

Yes. When NetEx/IP terminates, the address space in which it was running becomes unavailable, as indicated by message IEF352I ADDRESS SPACE UNAVAILABLE being issued. This means that the address space in which NetEx/IP was running can no longer be used until after the next IPL. From an operational standpoint, if you frequently start and stop NetEx/IP on a regular basis, you should consider increasing the RSVNONR value in the z/OS IEASYSxx initialization parameter. Refer to the MAXUSER, RSVSTRT, and RSVNONR parameters in the z/OS Initialization and Tuning Reference Manual.

It is NESi's recommendation to always run Netex in a reusable address space.

An SB0A-5C abend means that ALLOWUSERKEYCSA(NO) is specified in the z/OS DIAGxx parmlib member, and NetEx/IP is attempting to run in program key 8. When ALLOWUSERKEYCSA(NO) is specified, NetEx/IP must be installed to run in a non-key8 program key. Review Step #18 in the installation instructions contained in the NetEx/IP Installation Manual.

There were several new initialization statements introduced in H210IPZ. They should be added to a customer's current initialization file before migrating to H210IPZ. As reference, a copy of the NTXINIT file is contained in the H210IPZ distribution. It can be found in 'hlq.NTXSAMP(NTXPARM)'. The new initialization statements are listed below. Refer to the H210IPZ Installation Manual for a description of these statements.

  • OSAA and OSA1IF - should be specified if an OSA interface is used to provide NetEx/IP network connectivity
  • MFCP - should be specified as 0
  • FUBS - should be specified as OFF
  • FMSML - specified as ON will force multiline WTOs for remote operator displays, which will truncate the display if any lines are greater than 70 characters
  • SNDGRNM - specified as OFF will cause the real host name (not group name) to be sent on connects
  • PAGE4K, PAGE8K, and PAGE16K - should be set to the same value that is currently specified for PAGE1K
  • USERPK and USERSK - use as/if needed to specify program keys (USERPK) and storage keys(USERSK) when using non-key8 Netex programs (this is not normally the case). Refer to the Installation manual for more information.

H211 1.x (BFX) Frequently Asked Questions

Refer to the Support Table for the currently supported versions of H211; typically the highest release number is the latest version.

No, H211 does not require a key.

eFT213 5.4.5 & 5.4.6 (eFT/USER-Access) Frequently Asked Questions

Yes, this product requires a license key to operate. If you are upgrading from a release prior to 5.4.4 you will need a new key. To request a key, send an e-mail to support@netex.com. The following information must be copied exactly and included in your request:

  1. Customer site name
  2. CPU serial number for the z/OS system. This information is found by executing the z/OS command “D M=CPU”.
  3. LPAR name.
  4. eFT product designator and version (e.g., eFT213 5.4.6 for IBM z/OS).

Start the eFT/USER-Access Client application and issue the eFT command 'show local' to display your currently running version.

Yes, beginning with Release 5.4.5, eFT213 uses Dynamic Allocation to allocate datasets, and Dynamic Allocation supports the use of volser system symbols.

eFT213 5.4.4 (eFT/USER-Access) Frequently Asked Questions

Yes, this product requires a license key to operate. If you are upgrading to 5.4.4 you will need a new key. To request a key, send an e-mail to support@netex.com. The following information must be copied exactly and included in your request:

  1. Customer site name
  2. CPU serial number for the z/OS system. This information is found by executing the z/OS command “D M=CPU”.
  3. LPAR name.
  4. eFT product designator and version (e.g., eFT213 5.4.4 for IBM z/OS).

Run the eFT/USER-Access Client application and issue the eFT command 'show local' to display your currently running version.

No, eFT213 uses Dynamic Allocation to allocate datasets, and Dynamic Allocation does not support the use of volser system symbols.

Recent News about HyperIP

2016 NetExIP-HyperIP Security Enhancement Update

NetEx/IP® and HyperIP® Today Network Executive Software, Inc. (NESi) brings high performance file transfer technology to the industry-standard IP environment with its NetEx/IP and HyperIP software products. NetEx/IP is many times faster than TCP over long distances, which makes it the ideal solution for moving massive amounts of mission- or time-critical data a…[MORE+]