Page 1
NESiGate-CO
NetEx/IP Offload Channel-to-IP Gateway
Release 2.10
Reference Manual
MAN-REF-COSW 2.10-19
Page 2
Revision Record
Revision Description
01 (April 2001) Initial manual release by Network Executive Software.
02 (July 2001) Added messages and NRBSTAT Session error codes
03 (Oct 2001) Incorporate NetEx/IP Release 6.2.5.
04 (Jan 2002) Updated for Red Hat 7.2 distribution and miscellaneous corrections and addi-
tions.
05 (Apr 2002)
• Added documentation for new initialization parameters.
• Added documentation for additional NetEx operator commands.
06 (xxx 2002) Added documentation for Hitachi IBM-compatible configuration require-
ments.
07 (Oct 2002) Added documentation for NG_CO service
08 (Dec 2002) Removed Integration section to NESiGate Software Installation Guide
09 (Jun 2005) Added Software RAID to installation
10 (Aug 2005) Updated for release 2.7.2
11 (Jan 2006) Updated for release 2.7.4
12 (Jan 2006) Updated for release 2.7.5
13 (Feb 2006) Updated for release 2.7.6
14 (Oct 2006) Updated for release 2.8
15 (Nov 2006) Updated for release 2.8.1
16 (Feb 2007) Updated for release 2.8.2
17 (Apr 2007) Updated for release 2.8.3; Major command security redefinitions
18 (Feb 2008) Updated for release 2.9.1
19 (Feb 2010) Update for release 2.10
© 2008-2010 Network Executive Software, Inc. Reproduction is prohibited without prior permission of
Network Executive Software. Printed in USA. All rights reserved.
The U.S. Department of Commerce restricts the distribution of technical information contained in this
document when exported outside the U.S. Therefore, careful attention should be given to compliance
with all applicable U.S. Export Laws if any part of this document is to be exported.
Page ii MAN-REF-COSW 2.10-19
Page 3
Table of Contents
Table of Contents .....................................................................................................................................iii
Copyrights and Trademarks ...................................................................................................................v
Notice to the Customer..........................................................................................................................vi
NESiGate Modification Policy..........................................................................................................vi
Introduction................................................................................................................................................1
Customization.............................................................................................................................................3
Overview................................................................................................................................................3
Device addressing ..............................................................................................................................3
Device Number ..............................................................................................................................3
GNA Address..................................................................................................................................4
IP Address......................................................................................................................................4
Using a Web Browser to Configure NESiGate......................................................................................5
Define the Channel Boards(s) ............................................................................................................5
Define the Devices.............................................................................................................................5
Configure NetEx/IP............................................................................................................................5
GNA to IP Mapping...........................................................................................................................6
Reboot NESiGate...............................................................................................................................7
Web Browser Interface...............................................................................................................................9
Overview................................................................................................................................................9
Browser Considerations .....................................................................................................................9
Initial Screen ......................................................................................................................................9
Common Command Frame................................................................................................................9
Common Webpage Navigation..........................................................................................................9
NESiGate Board/Channel Commands .............................................................................................10
Show Channel Config ..................................................................................................................12
Show Channel Info.......................................................................................................................13
Channel Display Stats ..................................................................................................................13
Channel Define Interface..............................................................................................................15
Remove Channel Interface...........................................................................................................16
NETEX Webpage.............................................................................................................................17
MAN-REF-COSW 2.10-19 Page iii
Page 4
Modify NetEx Startup Parms.......................................................................................................18
NetEx Eat/Gen Test......................................................................................................................18
Appendix A: Configuration Worksheet ...................................................................................................19
Appendix B: NetEx Default Parameters...................................................................................................21
Appendix C: NetEx/IP Messages.............................................................................................................29
Viewing NetEx/IP Messages............................................................................................................29
Using the Web Browser Interface ................................................................................................29
Using the Command Line Interface..............................................................................................29
Messages:.........................................................................................................................................30
Appendix D. NRB Status Error Codes.....................................................................................................37
General Errors ......................................................................................................................................37
Session Errors.......................................................................................................................................38
Appendix E: NESiGate Sense Bytes........................................................................................................41
NESiGate ESCON............................................................................................................................41
Page iv MAN-REF-COSW 2.10-19
Page 5
Copyrights and Trademarks
This document contains references to the trademarks of the following corporations.
Corporation Trademarks
International Business Machines ESCON®
Unisys Corporation SBCON
Red Hat, Inc. RedHat®
Note: RedHat® is a registered trademark of Red Hat, Inc. This product is not a product of Red Hat,
Inc. and is not endorsed by Red Hat, Inc. This is a product of Network Executive Software and we have
no relationship with Red Hat, Inc.
Additional trademark references:
MAN-REF-COSW 2.10-19 Page v
Page 6
Notice to the Customer
Comments about this manual may be submitted via mailto:pubs@ netex.com or by visiting our website:
www.netex.com
Information on Network Executive Software’s general software support policy (e.g., alternate contact
methods, support severity level descriptions, and service status definitions) may be found at
http://www.netex.com/support/software-support-policy
Details on Network Executive Software’s warranty and support policies specific to NESiGate may be
found at http://www.netex.com/support/nesigate-warranty-and-support-policy
NESiGate Modification Policy
NESiGate is an appliance that contains proprietary software and firmware. Modifications to the software, firmware, or hardware platform that are not specifically authorized by NESi are prohibited.
Examples of prohibited activities include (but are not limited to) the following items:
• Installing other software on NESiGate
• Modifying the file system through means other than NESiGate’s defined User Interfaces (in-
cluding adding, deleting, or moving files and/or directories, adding or deleting user accounts or
changing permission levels, ownership, or other attributes of files and/or directories)
• Starting or stopping system services through means other than NESiGate’s defined User Inter-
faces
• Adding or removing hardware components
. Always include the complete title of the document with your comments.
.
.
Any unauthorized modifications to NESiGate may affect its operation and/or obstruct NESi’s ability to
diagnose problems and provide corrections. Any work resulting from unauthorized modifications shall
be paid by the customer at NESi’s then-current support rates and may result in the immediate termination of warranty/support coverage.
Page vi MAN-REF-COSW 2. 10 -19
Page 7
MAN-REF-COSW 2.10-19 Page vii
Page 8
Introduction
The purpose of this manual is to provide an overview of the procedures used to integrate and customize
the NetEx/IP components onto a NESiGate channel offload platform, and to provide a description of the
command and web browser interfaces.
This manual is divided into the following sections:
1) Software Installation: Installation of NESiGate software on the hardware platform is covered in
the NESiGate Common Reference Manual. Refer to that guide, then return to this manual to complete the configuration of NESiGate as a Channel Offload (CO) type device
2) Customization: this section is targeted to the end-user who is responsible for customizing the NE-
SiGate appliance for use as a NetEx/IP channel offload device. It is assumed the NESiGate already
has the appropriate level of the system software installed. To complete the customization, the reader must be familiar with channel device and network addressing concepts.
3) Web Browser Interface: this section is targeted to the end-user who is responsible for customizing
the NESiGate appliance for use as a NetEx/IP channel offload device, and who is responsible for
configuring and controlling operational aspects of the device.
MAN-REF-COSW 2.10-19 Introduction Page 1
Page 9
Page 2 Introduction MAN-REF-COSW 2.10-19
Page 10
Customization
Overview
The purpose of this section is to provide an overview of the procedures used to complete the customization of the NESiGate Offload channel-to-IP NetEx/IP gateway for use with NetEx/IP offload products.
This section is targeted to the end-user responsible for customizing a NESiGate appliance for use as a
NetEx/IP offload channel device. It is assumed the NESiGate already has the appropriate level of the
system software installed. To complete the customization, the reader must be familiar with channel device and network addressing concepts.
The customization process consists of these major steps:
1. Configure NESiGate
2. Configure NetEx/IP
3. Update DNS or local ‘hosts’ file (optional)
4. Reboot NESiGate
Device addressing
Prior to performing the Device and IP customization tasks, it would be beneficial to review NESiGate
device and network addressing concepts.
There are three important addressing elements involved in delivering NetEx/IP channel data that is not
IP-aware, and transferring it over an IP network to the correct destination:
• Device Number
• GNA Address
• IP Address
Device Number
The Device Number on the host and Device Index on the NESiGate channel board are numeric representations of the same unique "device". On the Host operating system, a "Device Number" is mapped
as a Unit Address on a Logical Control Unit (a physical control unit may consist of from 1-16 logical
control units). The Physical Control Unit may be connected to a Port on an ESCON Director. Multiple
inbound Host channels may be connected to the ESCON Director and provide connectivity to the device
from multiple partitions (LPARs) across multiple hosts.
MAN-REF-COSW 2.10-19 Customization Page 3
Page 11
Similarly, on the NESiGate ESCON board, a "Device Index" is defined as a Unit Address on a Logical
Control Unit (up to 16 may exist). The Physical Control Unit may be connected to a Port on an ESCON
Director, which may provide connectivity to multiple LPARs across multiple hosts.
Since both the Device Number and Device Index represent the same unique device (from different perspectives), the same addressing components must be specified exactly the same in both definitions.
Failure to do so will prevent the NESiGate devices from functioning properly.
When defining devices on the ESCON channel board, the following items are specified: Device Unit
Address, Logical Control Unit, the Director port to which the host channel is connected, and Partition-id
(LPAR). The Device Index values are not specified by the user. They are automatically generated
when the channel configuration is defined.
A maximum of 64 devices are supported on each ESCON interface.
Refer to the “Channel Define Interface” button on page 15 for a description of defining the channel de-
vices.
Conflicts and illogical configurations may be accepted as input (to the web or CLI), however that does
NOT mean they will work (i.e. overlapping subchannel addresses, incorrect CUs, etc.). The channel
configuration in the NESiGate must match the (gen'ed) configuration in the host.
GNA Address
The GNA address represents a NetEx/IP network address that is associated with a given device. It is
specified in the NetEx/IP Network Configuration Table (NCT). It is also specified during the customization of the NESiGate Channel Driver. At that time, an association is established between a particular
GNA address and a Device Index.
IP Address
The IP address represents a NetEx/IP network node address. There is no channel device awareness inherent in an IP address. However, during the NESiGate configuration, IP host names are defined, each
having a format based on its GNA address. This enables NESiGate to perform a direct mapping between GNA and IP addresses. This mapping is transparent to the NetEx/IP running on the host, as well
as to all NetEx/IP applications.
Page 4 Customization MAN-REF-COSW 2.10-19
Page 12
Using a Web Browser to Configure NESiGate
The NESiGate Web Browser Interface should be used to configure and manage NESiGate. Before configuring the NG-CO specific items, the common System and Network configuration should be completed. See the “NESiGate Common Reference Manual” (NG-SW) manual for details.
Refer to the "Web Browser Interface" section on page 9 for a complete description of the commands
used in this section.
Define the Channel Boards(s)
The channel board(s) are automatically configured by the NESiGate initialization software. Normally,
no re-configuration of the board configuration is required.
Define the Devices
This step is required. If this step is not performed, the ESCON devices will respond as the correct device without regard to LPAR or ESCON director port affinity. If this does not match the real configuration, incorrect results will occur.
Select the Board/Channel link located on the navigation menu. This will open the page that is titled:
NESiGate CO Board/Channel.
Using the device configuration data from a completed worksheet provided in “Appendix A: Configuration Worksheet” on page 19, use the "Channel Define Interface" button to define the devices. Refer to
page 17 for a description of this command.
Repeat this step as many times as necessary until all required channel interfaces are defined.
Configure NetEx/IP
There are three steps to configure NetEx/IP for NESiGate:
• create and download an NCT
• make a pamfile for this NESiGate
• modify default parameters for this NESiGate
NCT
The NCT can be created on any network-attached host and placed in a file named ‘<nesigate>.nct’
where <nesigate> is the configured hostname of the NESiGate being configured.
Refer to the “Configuration Manager and NetEx Alternate Path Retry (APR) User Guide” [MANCNET-CONF-MGR] manual for a description of the NCT parameters.
MAN-REF-COSW 2.10-19 Customization Page 5
Page 13
The NCT can then be uploaded to the NESiGate by using the web browser interface, on the Product
webpage under the “Send/Receive” section or via the Uploads webpage.
Typical steps for NCT modification are:
1. From the NESiGate, Downloads webpage, copy the NCT from the NESiGate to your work-
station
2. On your workstation, edit the NCT to make modifications (i.e. adding another host)
3. From the NESiGate, Uploads webpage, copy the modified NCT back to the NESiGate
4. From the NESiGate, Netex webpage, run the build PAM for this NESiGate hostname
5. Insure the GNA to IP mapping or DNS accommodates the new modifications.
6. Reboot the NESiGate
PAM
The pamfile is an internal file built from the NCT by the Configuration Manager. It contains a configuration image of the NCT relative to a particular host.
To build a PAM, use the web browser interface, on the Netex webpage under the “(buildPam) for Ne-
tex Host” section and select the hostname for which you are creating the pamfile.
NETEX parameters
Netex has a set of default initialization parameters. Refer to “Appendix B: NetEx Default Parameters ”
on page 21 for a description of the parameters contained in ntx_default.
Two parameters MUST be changed in order to make Netex functional (“local” and “device1”) for your
site and one may be changed in order to improve performance on some networks (“segsize”). See
“Modify NetEx Startup Parms” on page 18 for details.
GNA to IP Mapping
NetEx/IP Offload performs dynamic mapping of GNA addresses to IP addresses. Dynamic mapping is
performed at NetEx/IP initialization time for all hosts defined in the NCT. If DNS is configured, a DNS
lookup is done for a hostname entry in the following format:
NTX0000UUSS
where UU is the network address and SS is the subaddress. (Note: the "NTX" DNS entry
names must all be upper case).
These addresses comprise the Netex toGNA address, as defined in the NetEx/IP NCT by the
NETADDR (UU) and SMGDREF (SS) parameters. If the DNS lookup is successful, an entry is dynamically created in the NetEx/IP mapping table that maps the toGNA and toIP addresse s. Subsequent
searches of the table for any outgoing and incoming messages will find this new entry, thus avoiding
additional DNS lookups.
If a host is not defined in the NCT, or if a DNS entry does not exist for the host, you can configure the
GNA to IP mapping on the “GNA Host Mapping” webpage.
Page 6 Customization MAN-REF-COSW 2.10-19
Page 14
Reboot NESiGate
After the configuration changes have been made, the NESiGate unit must be rebooted to make the
changes effective:
• Vary the devices offline to the host operating system.
• Navigate to the “System Config” webpage of the NESiGate
• In the “Misc Command” drop down menu, select “REBOOT”
• Click the <Misc Commands> button
• After NESiGate is back up vary the devices online to the host operating system
MAN-REF-COSW 2.10-19 Customization Page 7
Page 15
Page 8 Customization MAN-REF-COSW 2.10-19
Page 16
Web Browser Interface
Overview
NESiGate provides a web-enabled configuration facility. Connecting NESiGate to an intranet infrastructure enables usage of a web browser to configure and manage the NESiGate CO. Refer to the common
NESiGate Installation Manual for descriptions of all the common web pages.
Browser Considerations
The browser can be hosted on any system, as long as that system has network connectivity to the NESiGate. However, the browser must be configured to refresh pages on each page reference.
Initial Screen
When the browser first connects to NESiGate, a password entry window will be displayed. Enter the
ngadmin userid you have been assigned and its password to gain access to the NesiGate. Default userids and passwords are described in the common NESiGate Installation Manual.
The initial screen displayed when the password has been accepted includes a “Welcome” screen with
general information on the right.
Common Command Frame
In the top, left frame is a dropdown navigation list of the available command pages, and some common
display commands, as well as commonly used miscellaneous commands. Command page specific functions are below this area. Help for each selected page can be accessed by clicking on the HELP button in
the top left frame.
Common Webpage Navigation
These navigation links will bring you to the webpage for re-configuring and displaying common information. Refer to the “NESiGate Installation Manual” for a description of these commands.
MAN-REF-COSW 2.10-19 Web Browser Interface Page 9
Page 17
NESiGate Board/Channel Commands
This webpage is used to define, display and monitor the channel interface and devices with respect to
the NESiGate CO.
Conflicts and illogical configurations may be accepted as input (to the web or CLI), however that does
NOT mean they will work (i.e. overlapping subchannel addresses, incorrect CUs, etc.). The channel
configuration in the NESiGate must match the (gen'ed) configuration in the host.
Figure 1. Channel/Board Webpage
The following are general definitions of components on this page.
IFname
name given to a channel interface for displays, other commands
board
name of the channel board on which this interface is being defined.
UADD
OS-gened Unit Address.
StartGNA:
first HCM network address (UUSS). UU matches NCT netaddr & smgdref is within
SS,SS+num devices.
Number of devices
number of GNA addresses (subchannels) for this interface (4 is recommended for NGCA;
at least 2 per concurrent session is required for NG-CO)
NOTE: up to 64 active devices per board and 128 active devices per NESiGate are supported.
Page 10 Web Browser Interface MAN-REF-COSW 2.10-19
Page 18
CU (escon only)
OS-genned Control Unit Address (must be 0 for Unisys)
CHlink (escon only)
Escon director host-side port#; or for direct connect:
1 (IBM), 2 (Unisys old SBCON), 77 (Unisys SCIOP/SIOP SBCON)
LPAR (escon only)
Logical Partition # (IBM)
MAN-REF-COSW 2.10-19 Web Browser Interface Page 11
Page 19
Show Channel Config
This shows the currently defined and currently loaded ESCON subchannel ranges and their index values.
Prior to selecting this button, provide the following data on the selection screen:
IFname the name of the channel interface to display.
If IFname is not specified, all defined channel interfaces are displayed.
Show Channel Config [ x3650 - Thu Jun 3 15:49:50 ]
id type bus slot
-------- ------------------ --- --- board1 ESCON 2 1
id board type prot sgna num in sUnt sdi bfsz opt minor
l_index dtTo wmTo mxData
-------- -------- ---- ---- -------- --- -- ---- --- ------ --- ----- ----
--- ---- ---- ----- if5e00 board1 MSG HCM 00005e00 4 0 -1 1 65535 0 1
1 30 0 65535
--- Boards Config File ---
### Auto-configured on 2010Jun03-150841 ###
#
board1 pcibus 2 pcidev 1 escon cfgd
--- Interface Config File ---
### channel config file - created: 2010 May 11 at 09:08:14
if5e00 board board1 type MSG prot HCM sgna 5E00 num 4 in 00 mxdt 65535 bfsz
65535 uadd 0 cu 1 chlink E6 lpar 1 sdevinx 1
--- Escon Config File ---
; ESCON configuration : created on 2010 May 11 at 09:08:14
; indexNN=uadd,emulation,controlunit,channellink,lpar,tag
slot=197121
index1=0,HCM,1,E6,1,nesiCLI
index2=1,HCM,1,E6,1,nesiCLI
index3=2,HCM,1,E6,1,nesiCLI
index4=3,HCM,1,E6,1,nesiCLI
Figure 2. Output from ‘Show Channel Config’
Page 12 Web Browser Interface MAN-REF-COSW 2.10-19
Page 20
Show Channel Info
This displays detailed channel interface information. Prior to selecting this button, provide the following
data on the selection screen:
IFname The name of the channel interface to display. If not specified, all defined chan-
nel interfaces are displayed.
Device# Limit the display of the channel interface to a particular device. For an ESCON
channel interface running in “configured” mode, this parameter is the Device
Index. For an ESCON channel interface running in “non-configured” mode,,
this parameter is an offset from the UADD specification. If the UADD parameter is not used, this parameter is an offset from the low-order byte of the startGNA address.
Show Info [ x3650 - Thu Jun 3 15:51:07 ]
id minor state db type prot startGna #Su sUnt sdi TxMsgs
RxMsgs
-------- ----- -------- -- ---- ---- -------- --- ---- --- -------- ------
- if5e00 1 STARTED 0 MSG HCM 00005e00 4 -1 1 0
0
id sub unit devi initStat accWSize currWMsg
------------ --- ---- ---- -------- -------- ------- if5e00:1 0 -1 1 0 0 0
Figure 3. Output from ‘Show Channel Config’
Channel Display Stats
This displays statistics for a particular channel interface. Prior to selecting this button, provide the following data on the selection screen:
IFname The name of the channel interface to display. If not specified, all defined chan-
nel interfaces are displayed.
Device# Limit the display of the channel statistics to a particular device. For an ESCON
channel interface running in “configured” mode, this parameter is the Device
Index. For an ESCON channel interface running in “non-configured” mode,
this parameter is an offset from the UADD specification. If the UADD parameter is not used, this parameter is an offset from the low-order byte of the startGNA address.
MAN-REF-COSW 2.10-19 Web Browser Interface Page 13
Page 21
Show Stats [ x3650 - Thu Jun 3 15:52:48 ]
id txpacks txbytes rxpacks rxbytes txMiscEr
------------ -------- ------------ -------- ------------ -------if5e00:1 0 0 0 0 0
rxMiscEr haltIO streamTo sysReset selReset cmdRej intvReq
-------- -------- -------- -------- -------- -------- ------- 0 0 0 0 0 0 0
busOutCk equipCk dataCk overRun delayTx delayRx dataTo WO
-------- -------- -------- -------- -------- -------- -------- - 0 0 0 0 0 0 0 0
Figure 4. Output from ‘Show Channel Stats
Where:
id : id for display only – minor number
txpacks : # messages sent to the channel
txbytes : # data bytes sent to the channel
rxpacks : # messages read from the channel
rxbytes : # data bytes read from the channel
txMiscEr : # transmit to the channel errors
rxMiscEr : # receive from the channel errors
haltIO : halt I/O count
streamTo : I/O streaming timeout count
sysReset : system reset count
cmdRej : command reject count
intvReq : intervention required count
busOutCk : bus out check count
equipCk : equipment check count
dataCk : data check count
overRun : overrun count
delayTx : # stream delayed messages destined for the channel
delayRx : # stream delayed messages coming from the channel
dataTo : data timeout count
this parameter is an offset from the UADD specification. If the UADD parameter is not used,
this parameter is an offset from the low-order byte of the startGNA address.
Page 14 Web Browser Interface MAN-REF-COSW 2.10-19
Page 22
Channel Define Interface
This defines a channel interface, which consists of a range of devices for use by a particular NetEx/IP.
Note: a channel board must be installed before defining any channel interfaces.
Prior to selecting this button, provide the following data on the selection screen:
IFname a name by which the interface will be identified.
On board the name of the board on which this interface is being defined. Auto-
Define uses ‘board1’ and ‘board2’
StartGna the GNA address of the first device in the form ‘UUSS’, where ‘UU’ is
the NETADDR for this ADAPTER definition in the NCT. ‘SS’ must be
the same as the first device address lower byte. The SMGDREF definition for this ADAPTER definition in the NCT must be in the range
‘SS’ to ‘SS’ + Number of devices.
Number of devices the number of devices being defined for this interface (4 is normally
sufficient). The maximum number of devices that can be defined per
interface definition is 16.
UADD the unit address of the device.
For ESCON devices only
CU the control unit number. Up to sixteen control units can be specified, ranging
from 0-F. A unique Control Unit should be defined for each concurrent host, or
host partition, running NetEx/IP. Note: CU 0 must be used if connection is to a
Unisys system.
CHlink - the ESCON director port number to which the channel is connected that is used
for communicating to the ESCON board. If the ESCON interface is connected
directly to the channel without going through an ESCON Director, a port number of 1 (or 01) should be specified if connection is to an IBM or Hitachi IBMcompatible system; a port number of 2 (or 02) should be specified if connection
is to a Unisys system.
If the ESCON interface is connected from an IBM system through an ESCON
Director, but the port-to-port connection is defined as Dedicated in the channel
subsystem (HCD or IOCP), and the port-to-port connection is also defined as
Dedicated on the ESCON Director, then a port number of 1 (or 01) must be
specified. This configuration is treated the same as a point-to-point nonswitched connection.
LPAR - the partition number of the host driving this interface if the channel is defined
as SHARED. If the system is running in BASIC mode, or if the system is running in LPAR mode but the channels are defined as either RECONFIGURABLE or DEDICATED, then the value specified for LPAR must be zero.
On an IBM system that supports logical channel subsystems, NESiGate is con-
figured the same way as on systems that do not support logical channel subsystem. The partition number (referred to as the MIF ID) is used as the LPAR
number. It is still a number in the range of x0-xF regardless of the logical
channel subsystem number.
MAN-REF-COSW 2.10-19 Web Browser Interface Page 15
Page 23
Caution: It is extremely important that the values specified for UADD, CU, CHlink, and LPAR
exactly match the values specified in the host system’s device configuration. Failure to do so
will make the devices unusable.
The total number of devices supported on each ESCON interface board is 64. Use this selection button
multiple times until all required device interfaces are defined.
It is possible to define more than 64 devices to satisfy specific configuration requirements (e.g., extra
devices that are only used when needed on backup systems), but care must be taken so that no more than
64 devices are active at any point in time. “Over-configuring” the ESCON interfaces with many devices
being used concurrently will have a negative impact on performance.
Remove Channel Interface
This removes a defined channel interface. Prior to selecting this button, provide the following data on
the selection screen:
IFname the name of the channel interface to stop.
Page 16 Web Browser Interface MAN-REF-COSW 2.10-19
Page 24
NETEX Webpage
This screen is used to issue commands configure and monitor the embedded Netex/IP stack.
Figure 5. NetEx Webpage
.
Netex Show Commands
Perform the specified showNtx, showNCT or showPAM command.
Display the current Netex log file, the loaded NCT or PAM file.
Netex Show Detailed Commands
Display all or specific host, session, transport or network.
buildPam
Build a PAM for the specified host. the host must match the local (host) in the Netex Default
file.
Set Netex Parm
MAN-REF-COSW 2.10-19 Web Browser Interface Page 17
Page 25
Change current running parameter values via ntxoper. settable parms and valid values are documented in the NG manual.
These values are set immediately, however a restart or a reboot will reset these values to those
in the Netex Default file.
Configure Netex Default
Change default values for Netex startup (ntx_default).
These values do not take effect until a restart or a reboot, however they are perisstent (every re-
boot/restart will reapply these values).
Also, the entire file or changed parms can be displayed, or the entire file may be reset to original
settings to restart the configuration from the beginning.
Modify NetEx Startup Parms
Certain NetEx parameters must agree with NCT-configured values for proper initialization. These can
be changed by using the buttons in the “Configure Netex Default” section. Select the parameter to
change in the first dropdown menu, enter the desired value in the window next to it, select “configure
default value” in the second dropdown and click <defaultcmd>. All the initial values can be restored
by selecting “reset all defaults” and clicking on the <defaultcmd> button.
Local Host – must agree with the hostname used for buildPAM
Local GNA (device 1) - must agree with the netaddr/smgdref of the local ADAPTER in the NCT.
Segment Size – may be adjusted from the default value (32768) for better performance in your configu-
ration.
Multihost – must be on if multiple channel-attached hosts will be offering the same Netex service(s),
e.g.BFXJS, but only the host corresponding to the name in the connect request may satisfy the connect.
NetEx Eat/Gen Test
To verify connectivity or measure Netex-to-Netex performance a pair of utility programs can be initiated from NESiGate CO or LO. Required parameters are:
Remote Host – Netex name of the remote Netex host.
DataMode – NRBDMODE for the data to be sent
Bytes/block – size of the data blocks to be sent in bytes
Blocks/loop - number of SWRITEs to do
Loops – number of times to run the test before ending. Each loop connects a new session.
Page 18 Web Browser Interface MAN-REF-COSW 2.10-19
Page 26
Appendix A: Configuration Worksheet
This worksheet can be used to record the necessary NESiGate configuration information. (Minimum
recommended configuration is listed here.)
The corresponding web configuration panel is identified in parentheses.
HOST & IP Information
(System Configuration)
Example
Site Configuration
Host & domain name netfin3.myworld.com
Time Zone US/Central
NTP Server 10.1.3.1
SNMP SysLocation myworld Comp Rm 3rd Fl
SNMP SysContact [email protected]
SNMP Community netexsw
SNMP Trap Server 10.1.2.75
DNS Server 10.1.3.1
DNS Domain myworld.com
DNS Search myworld.com
IP Network Information
(Network Configuration)
IP address (data)/netmask 11.1.2.27/255.255.255.0
IP address (management) 10.1.2.27/255.255.255.0
Default gateway 10.1.2.50
IP address of name server 10.1.3.1
Example
Site Configuration
Static Routes:
Network – mask – gateway 10.1.7.0 255.255.255.0
10.1.7.50
NESiGate GNA to IP Mapping
For either DNS Entries or the GNA Host
IP Mapping
Example
NTX0000A110
Site Configuration
10.1.2.25
MAN-REF-COSW 2.10-19 Appendix A Page 19
Page 27
OS device information
(Used for OS Definitions)
Example
Site Configuration
Device number (or name) 5200
Number of devices 14
Director port (device director port) F3
Control unit number (or name) 1
Unit address 0
LPAR number 0
Channel board Information
(Used for NESiGate board definitions)
Board name Board1
Example
NESiGate Channel Information
(Used for NESiGate device definition)
IFname
Example
IBM5200
Type (must be emsg)
Board (name of channel board)
Board1
UADD (unit address)
EMSG
0
Site Configuration
Site Configuration
StartGNA (starting GNA address)
Number of devices
Input device (n/a for NG-CO)
Max Data
For ESCON devices only:
CU (control unit)
CHlink (channel director port)
LPAR
EA00
14
0
65535
1
EA
0
Page 20 Appendix A MAN-REF-COSW 2.10-19
Page 28
Appendix B: NetEx Default Parameters
This section contains a description of the default parameters used by NetEx. Only a few of these can be
changed via the user interfaces. Refer to the web pages to see which parameters can be altered. All others will require direction from NESi Support personnel.
Note: “local” and “device1” must be correct or Netex will not initialize.
NetEx/IP Parameter Default Description
local LOCAL Local host name. This is the same name that
is defined in the HOST statement in the NCT
and during the MAKEPAM phase of building
the PAM file.
logerrors default The two allowed values are –
DEFAULT – this value logs adapter and
communications errors that are uncommon.
Some of these errors are normal but normally
occur only once every few hours.
ALL – this value logs all adapter and communication errors.
mbxname *not changable This is the name of the pipe used to move
NRB and DATA requests from user space
into NetEx/IP space.
pamfile *not changable This is the name of the PAM file NetEx/IP
uses to load the initial NCT. This name
should match the name specified in the Configuration Manager MAKEPAM command.
ntxlogname
msgsyslog
*not changable This is the name of the NetEx/IP log file.
Messages associated with the operation of
NESiGate NetEx/IP are logged in this file.
3 This parameter indicates where Netex mes-
sages are recorded.
0: record messages in both ntxlog AND mes-
sages.log (same as 3)
1: record messages in ntxlog ONLY
2: record messages in messages.log ONLY
3: record messages in both ntxlog AND mes-
sages.log (same as 0)
MAN-REF-COSW 2.10-19 Appendix B Page 21
Page 29
NetEx/IP Parameter Default Description
trapcmd
nesigate_trap This is the name of the current trap command
being used.
cctable *not changable This is the default name of a user customized
code conversion table. If not specified, NetEx/IP defaults to the built-in table.
ackcredit 2 This is the number of buffers that NetEx/IP
sends without returning an explicit ack.
Note: More buffers may be in the process of
being sent. Increasing this value has little
effect on system load and may decrease NetEx/IP throughput.
bufcnt 500 This is the number of “segment” sized buffers
available for all input and output.
Note: This parameter should be increased to
the maximum amount of data expected to be
in transit (being sent but not yet acknowledged) divided by “segment”.
connto 25 This is the initial value for CONNECT
TIMEOUT
datato 300 This is the initial value for DATA TIMEOUT.
In a heavily loaded system or during transfer
to tape, this value should be increased to
about 1000.
deadto 60 This is the initial value for DEAD TIMEOUT
debugreq 0 This parameter enables or disables the tracing
of user requests arriving at the NetEx/IP pro-
tocol stack. A value of 0 turns tracing off;
any other value turns tracing on.
debugret 0 This parameter enables or disables the tracing
of user responses being returned from the Ne-
tEx/IP protocol stack. A value of 0 turns trac-
ing off; any other value turns tracing on.
debugmsg 0 This parameter enables or disables the tracing
of HYPERchannel messages between Ne-
tEx/IP and the network. A value of 0 turns
tracing off; any other value turns tracing on.
debugdata 0 This is the maximum number of data bytes to
trace for any associated data block.
defblkin 32768 This is the default value for NRBBLKIN, if
the value zero is specified.
Page 22 Appendix B MAN-REF-COSW 2.10-19
Page 30
NetEx/IP Parameter Default Description
defblkout 32768 This is the default value for NRBBLKOUT, if
the value zero is specified.
defmsecsonewaydelay 0 This is the propagation delay of the network,
expressed in milliseconds, and is used if there
is no delay value specified in the PAM for this
network path. For Type 2 protocol connec-
tions, this value represents a fixed propagation
delay that never changes. For Type 4 protocol
connections, this value represents a starting
point that is used for internal bandwidth ca-
pacity calculations. However, the delay is
continuously measured during each session,
and if it changes, the updated value is used for
subsequent internal bandwidth capacity calcu-
lations.
dreadqueue 6 This is the number of reads that NetEx/IP has
outstanding to the DRIVER. This value may
need to be increased, if many very small
transfers are needed.
highresmsecs 10 This is the value of the internal high resolu-
tion timer. It is used for internal rate throt-
tling, and should not be changed.
idleto 6 This is the initial value for IDLE TIME. In
networks with many errors or contention, it
may help to drop this value to 2 or 3.
maxblkin 65400 This is the maximum NRBBLKIN value in
bytes.
maxblkout 65400 This is the maximum NRBBLKOUT value in
bytes.
maxkbitspersec 0 This is the maximum rate at which NetEx/IP
will deliver data to the network for each net-
work connection. If zero is specified, data
will be delivered with no internal throttling.
This value is only used for connections to
hosts that do not have a ‘rate’ value specified
in the PAM. This value is specified in Kbits
per second. For example, a value of 50 means
50Kbs; a value of 50000 means 50Mbs (i.e.
50,000 Kbs).
maxmbxxfer 32768 This is the maximum block which can be sent
across the STREAMS pipe facility.
MAN-REF-COSW 2.10-19 Appendix B Page 23
Page 31
NetEx/IP Parameter Default Description
mbufin 5 This is the number of input blocks that Ne-
tEx/IP will allow to be outstanding for each
user. This may have to be increased for long
telecommunications delays.
mbufout 5 This is the number of output blocks that Ne-
tEx/IP will allow to be outstanding for each
user. This may have to be increased for long
telecommunications delays.
msglvl 6 This is the value that controls the verbosity of
the message displays. A value must be speci-
fied as one of the following:
immediate
important
interesting
moderate
monitor
debug
blither
A value of ‘important’ (or less) must be speci-
fied to enable NetEx/IP session establishment
messages to be recorded in the ‘ntxlog’ file.
multihost ON When set ON, allows Netex to distinguish
between SOFFERs of the same application
name from multiple locally attached hosts
(LAN or channel). Set to OFF if there is only
one attached host or if all SOFFERs will have
unique names.
numlogs 5 This value defines the maximum number of
‘ntxlog’ files that are saved by the ‘swlog’
command.
prefprot 2 Defines the default preferred protocol type to
use when connecting to hosts that support
multiple NetEx/IP protocol types.
rcvratesecs 6 This is the time interval (in seconds) after
which the receive rate for a network connec-
tion is recalculated. The receive rate refers to
the rate at which the application is receiving
data from NetEx.
sndratesecs
3 actual send rate calculation interval
smqmax
25 max number of waiting incoming connects for
session manager
Page 24 Appendix B MAN-REF-COSW 2.10-19
Page 32
NetEx/IP Parameter Default Description
segsize 32768 This is the maximum size of a single trans-
mission data block over the network.
smax 110 This is the maximum number of users active
at any one time. If this value is changed, the
file specified by “mbxname” above should be
deleted.
timer 2 This is the initial value for the watchdog ti-
mer.
The following parameters are only applicable to protocol type 4 connections:
defstartkbitspersec 0 This is the starting throughput rate at which
NetEx/IP will attempt to deliver data to the
network for each network connection. If zero
is specified, data will be delivered with no
internal throttling. This value is only used for
connections to hosts that do not have a ‘rate’
value specified in the PAM or NRB.
This value is specified in Kbits per second.
For example, a value of 50 means 50Kbs; a
value of 50000 means 50Mbs (i.e. 50,000
Kbs).
ratedelaydecp 250 (25.0%) This is the percentage factor used to decrease
the sending rate of a network connection if the
round-trip delay increases. This recalculation
is performed after the expiration of each in-
terval specified by the ‘rtdelayincsecs’ pa-
rameter. The value specified represents a per-
centage multiplied by a factor of 10.
rateequivph 975 (97.5%) This is the upper bound of the send and re-
ceive equivalence adjustment (see ‘rate-
equivps’). The value specified represents a
percentage multiplied by a factor of 10.
rateequivpl 500 (50.0%) This is the lower bound of the send and re-
ceive equivalence adjustment (see ‘rate-
equivps’). The value specified represents a
percentage multiplied by a factor of 10.
MAN-REF-COSW 2.10-19 Appendix B Page 25
Page 33
NetEx/IP Parameter Default Description
rateequivps 850 (85.0%) This is the percentage factor used to deter-
mine equivalence of the send and receive rates
for each network connection. These rates are
assumed to be equal if they fall within this
percentage of each other. This is the initial
value used for each network connection, and
can be dynamically adjusted based on activity
and performance of the network. The value
specified represents a percentage multiplied
by a factor of 10.
rcvdataqhbytes 5000000 This is the high threshold value (in bytes) for
the size of the receiving NetEx DataQue for
each network connection. If the size of the
Data Queue exceeds this value, subsequent
blocks received on the network that are great-
er than the highest received LRN are NAK'ed
and discarded. Subsequent blocks will con-
tinue to be discarded until the size of the Da-
taQue is reduced to the value specified by
‘rcvdataqlbytes’.
rcvdataqlbytes 3000000 This is the low threshold value (in bytes) for
the size of the receiving NetEx DataQue for
each network connection. See the ‘rcvda-
taqhbytes’ parameter for the description of
how this value is used.
rtdelayincsecs 60 This is the interval (in seconds) used by the
sending side of a network connection after
which a check is made for an increase in the
round trip delay.
sndratedecsecs 18 This is the interval (in seconds) used by the
sending side of a network connection after
which a check is made for a rate decrease (i.e.
the receive rate is less than ‘rateequivps’ of
the send rate). If an adjustment is required,
the sending rate is decreased by the current
value of ‘sndrateps’.
sndrateincsecs 60 This is the interval (in seconds) used by the
sending side of a network connection after
which an attempt is made to increase the
sending rate, as long as a decrease in the send-
ing rate has not occurred during the interval.
sndrateupsecs
20 target send rate update interval
Page 26 Appendix B MAN-REF-COSW 2.10-19
Page 34
NetEx/IP Parameter Default Description
sndrateph 500 (50.0%) This is the high bound of the ‘sndrateps’ ad-
justment for each network connection. The
value specified represents a percentage multi-
plied by a factor of 10.
sndratepl 10 (1.0%) This is the low bound of the ‘sndrateps’ ad-
justment for each network connection. The
value specified represents a percentage multi-
plied by a factor of 10.
sndrateps 100 (10.0%) This is the percentage factor used to increase
or decrease the send rate for each network
connection. The send rate may be increased
after the expiration of the interval specified by
‘sndrateincsecs’. The send rate may be de-
creased after the expiration of the interval
specified by ‘sndratedecsecs’. The value spe-
cified represents a percentage multiplied by a
factor of 10.
startratep 750 (75.0%) This is the percentage factor used to calculate
the initial send rate of each network connec-
tion. This value is applied against the maxi-
mum rate for the connection, as specified in
the PAM, NRB, or by the ‘defstartkbitsper-
sec’ parameter. During the course of the con-
nection, the actual send rate may be adjusted,
based on network activity. The value speci-
fied represents a percentage multiplied by a
factor of 10.
Resume common parameters:
iprecv 250000 This is the size of the IP receive buffer.
ipsend 250000 This is the size of the IP send buffer.
ip1intrf 1
ipchksum
1
device1 UDP-6950-ddnnuuss This is the name of the NetEx/IP device. The
“ddnn” must be specified as either ‘0000’ or
‘0101’; “uuss” represents the unit number and
subaddress portions of the GNA address of
this device. The “uu” value must be the same
as the “netaddr” value specified on the
ADAPTER statement for this host in the
NCT, and the “ss” value must be the same as
the “smgdref” value specified on the same
ADAPTER statement.
MAN-REF-COSW 2.10-19 Appendix B Page 27
Page 35
NetEx/IP Parameter Default Description
device2 This is the name of a second NetEx/IP device,
and is only used if there is a second NIC card.
device3 This is the name of a third NetEx/IP device,
and is only used if there is a third NIC card.
device4 This is the name of fourth NetEx/IP device,
and is only used if there is a fourth NIC card.
Page 28 Appendix B MAN-REF-COSW 2.10-19
Page 36
Appendix C: NetEx/IP Messages
This section contains a description of the messages issued by NetEx/IP. These messages are displayed
in the ‘ntxlog’ file if the value of the ‘msglvl’ parameter is set to ‘important’ (or less).
Each message is prefixed with a date and timestamp of the following format:
Sun Jan 27 01:03:52 2008
Viewing NetEx/IP Messages
NetEx/IP messages are recorded in the ‘ntxlog’ file. There are two ways to view this file:
1) Using the NetEx/IP Web Browser Interface
2) Using the Command Line Interface (CLI)
Using the Web Browser Interface
To view the ‘ntxlog’ file using the Web Browser Interface, follow the instructions contained in the
“Web Browser Interface” section on page 9, and select the “ShowNtxLog” command. The recording of
NetEx/IP session messages in the ‘ntxlog’ file requires the ‘msglvl’ parameter to be set to ‘important’
(or less). This can be set by issuing the following command after NetEx/IP is initialized:
set msglvl important
This command should be entered following the procedures in the “Modify NetEx Startup Parms” section on page 18.
After this command is issued, select the “ShowNtxLog” command to view the log.
Using the Command Line Interface
Use ‘telnet’ or ‘ssh’ to access NESiGate, and login using the ngadmin userid you have been assigned.
Default userids and passwords are described in the common NESiGate Installation Manual.
Enter the ‘ShowProductLogAll’ or ‘ShowProductLogTail’ command to view the product logs, as described in the NESiGate installation manual. These commands display all product logs, including
ntxlog.
MAN-REF-COSW 2.10-19 Appendix C Page 29
Page 37
Messages:
ISOFFR nref n uname : offering pname at hname, t secs
Description: An OFFER has been issued by the NetEx/IP application that is running under the user
name ‘uname’.
n identifies the internal NetEx/IP session reference number
uname identifies the user name under which the NetEx/IP application is running.
pname identifies the NetEx/IP OFFER name of the application.
hname identifies the name of the host on which the OFFER occurred (local host)
t identifies the OFFER timeout value specified by the application.
User Response:
None.
ISCONN nref n uname : connecting to pname at hname,
path from aa to bb
Description: A CONNECT has been issued by the NetEx/IP application that is running under the user
name ‘uname’.
n identifies the internal NetEx/IP session reference number
uname identifies the user name under which the NetEx/IP application is running.
pname identifies the NetEx/IP name of the remote application (remote OFFER name).
hname identifies the name of the host being connected to (remote host).
aa identifies the local unit portion of the network path address
bb identifies the remote unit portion of the network path address
User Response:
None.
Page 30 Appendix C MAN-REF-COSW 2.10-19
Page 38
ISCONF nref n uname : pname confirming to nref m at hname
Description: An OFFER has been completed (connected to) by a remote NetEx/IP application, and the
subsequent CONFIRM has been issued.
n identifies the internal NetEx/IP session reference number of the local application.
uname identifies the user name under which the NetEx/IP application is running.
pname identifies the NetEx/IP OFFER name of the application.
m identifies the internal NetEx/IP session reference number of the remote application
hname identifies the name of the host on which the OFFER occurred (local host)
User Response:
None.
ISCLOS nref n uname : closing
Description: A CLOSE has been issued by the NetEx/IP application that is running under the user
name ‘uname’.
n identifies the internal NetEx/IP session reference number of the local application.
uname identifies the user name under which the NetEx/IP application is running.
User Response:
None.
ISDISC nref n uname : disconnecting
Description: A DISCONNECT has been issued by the NetEx/IP application that is running under the
user name ‘uname’.
n identifies the internal NetEx/IP session reference number of the local application.
uname identifies the user name under which the NetEx/IP application is running.
User Response:
None.
MAN-REF-COSW 2.10-19 Appendix C Page 31
Page 39
FINISHSESSION nref n : nrbreq = rr, nrbstat = ssss, nrbind = i
Description: A NetEx connection is terminated, due to the reason indicated in the message.
n identifies the internal NetEx/IP session reference number of the local application.
rr identifies the NetEx/IP request type.
ssss identifies the reason for the session failure. Ref er to “Appendix D. NRB Status Error
Codes” on page 37 for a description of the possible status codes.
i identifies the status of the connection
6 session is disconnected
User Response:
None.
NEXTPAM nref n : new path from aa to bb
Description: An APR (alternate path retry) operation has occurred for the indicated session connection.
n identifies the internal NetEx/IP session reference number
aa identifies the local unit portion of the new network path address
bb identifies the remote unit portion of the new network path address
User Response:
None.
Page 32 Appendix C MAN-REF-COSW 2.10-19
Page 40
NETEX: network protocol error n
Description: A netex network protocol error has been detected. The specific error is identified by “n”
1 Attempt to reroute non-offering side
2 Attempt to confirm to offerer
3 Actual data shorter than specified in protocol
4 D-read failed
5 Not a NETEX message
6 Checksum error
9 Awaiting the second part of a two-part message after the first part was already received.
We received a new one-part message instead.
10 Received the second part of a two-part message prior to receiving the first part.
11 Awaiting the second part of a two-part message after the first part was already received.
We received the first part of a different two-part message instead.
12 Two-part message error—no P-data or O-data
13 Invalid network unique id
14 Bad status creating TUB NDB
User Response:
None. Netex reports the invalid message and continues. This situation can sometimes occur when
messages are dropped on busy networks.
MAN-REF-COSW 2.10-19 Appendix C Page 33
Page 41
NETEX: transport protocol error n
Description: A netex transport protocol error has been detected. The specific error is identified by “n”
1 -- base field too small
2 -- protocol level is not greater than or equal to 2
3 -- invalid message type
4 -- connect attempt to unlicensed PROT_4
5 -- tdb->tdblrn > tub->tubrplrn
6 -- ‘disc’ sub-field in ‘x’ msg type, ‘type’
7 -- invalid sub-field type ‘x’, ‘type’
8 -- sub-field ‘x’ too small = ‘y’, ‘type’, ‘size’
9 -- sub-field ‘x’ length ‘y’ overlaps total transport length ‘z’, ‘type’, ‘size’, ‘length’
10 -- New path has smaller segsize
User Response:
None. Netex reports the invalid message and continues.
Message received with no read active
Description: A Netex message was received on the network, but there was no Netex ‘read’ request active at the time. Message is dropped.
User Response:
None. Netex reports the condition and continues.
Repeated occurences of this message could indicate the Netex ‘DREADQUEUE’ parameter might
need to be increased.
Page 34 Appendix C MAN-REF-COSW 2.10-19
Page 42
emsg(xx,yyyy): unknown netex request 0xn
Description: An unknown Netex request was received by the NESiGate-CO application.
xx,yyy -- identifies the NESiGate-CO process
0xn -- n identifies the unknown request type
User Response:
None. Netex reports the condition and continues.
emsg(xx,yyyy): abort ind received, disconnecting
Description: An abort indicator was received by the NESiGate-CO application.
xx,yyy - identifies the NESiGate-CO process
User Response:
None. Netex reports the condition and continues.
chnlMailHandler(stream nnnnnnnn(xx)): system reset, subch=nn
Description: A system reset was received on the channel
xx, - identifies the NESiGate-CO channel interface name
nn - identifies the NESiGate-CO subchannel device
User Response:
None. Netex reports the condition and continues.
MAN-REF-COSW 2.10-19 Appendix C Page 35
Page 43
chnlMailHandler(stream nnnnnnnn(xx)): selective reset, subch=nn
Description: A selective reset was received on the channel
xx, - identifies the NESiGate-CO channel interface name
nn - identifies the NESiGate-CO subchannel device
User Response:
None. Netex reports the condition and continues.
chnlMailHandler(stream nnnnnnnn(xx)): data timeout, subch=nn
Description: A data timeout has occurred on the indicated subchannel device. Data is discarded and
the Netex session is aborted.
xx, - identifies the NESiGate-CO channel interface name
nn - identifies the NESiGate-CO subchannel device
User Response:
None. Netex reports the condition and continues.
chnlGenAbortInd(stream nnnnnnnn(xx)): putnext message nnnnnnnn
Description:
xx, -- identifies the NESiGate-CO channel interface name
nnnnnnn -
User Response:
None. Netex reports the condition and continues.
Page 36 Appendix C MAN-REF-COSW 2.10-19
Page 44
Appendix D. NRB Status Error Codes
General Errors
The following errors are general NETEX errors.
0001 A read type operation completed normally within NETEX, but the Pdata buffer provided
by the user was not large enough to hold the data. NRBLEN and NRBUBIT reflect the
amount of data the other party intended to send. However, the amount of data moved to
the user’s program was only the amount of addressable units specified in NRBBUFL.
NRBIND specifies the type of data sent to the user. Requests affected: OFFER, READ.
The status of the connection is not affected.
0002 NRBBUFL and NRBBUFA do not specify a block of storage that fits entirely within the
user’s addressable memory. The operation is suppressed. All requests are affected. The
status of the connection is unaffected.
0003 On a write type operation, the unused bit count (NRBUBIT) specifies a larger number of
bits than are in the machine’s word (addressable unit size). The operation is suppressed;
the status of the connection is not affected.
0004 The request code (NRBREQ) is not valid. The operation is ignored, and the status of the
connection specified by NRBNREF is not affected
0005 The buffer size specified (in NRBBUFL for read and NRBLEN for write) exceeds an im-
plementation defined NETEX maximum. The operation is suppressed. The status of the
connection is not affected.
0011 A read-type operation completed normally within NETEX, but the Odata buffer provided
by the user was not large enough to hold the data. NRBPROTL reflects the amount of data
the other party intended to send; however, the amount of data moved to the user’s program
was only the amount of addressable units originally specified in NRBPROTL. NRBIND
specifies the type of data sent to the user. Requests affected: OFFER, READ. The status
of the connection is not affected
0012 NRBPROTL and NRBPROTA do not specify a block of storage that fits entirely within the
user’s addressable memory. The operation is suppressed. All requests are affected. The
status of the connection is unaffected.
0021 A read-type operation completed normally within NETEX, but BOTH the Odata and Pdata
buffers were too small to hold the incoming data. NRBLEN/NRBUBIT and NRBPROTL
reflect the amount of data the other party intended to send; however, the amount of data
moved to the user’s program was only the amount of addressable units originally specified
in NRBLEN and NRBPROTL. NRBIND specifies the type of data sent to the user. Request affected: OFFER, READ. The status of the connection is not affected.
0100* The user interface detected that the NRBNREF in the NRB does not refer to a connection
currently in use by the application program. Probable cause is a bad CONNECT, OFFER,
or ASSIGN or failure to handle an incoming Disconnect.
MAN-REF-COSW 2.10-19 Appendix D Page 37
Page 45
0310 The user has attempted to re-use an NRB before a previous request issued with that NRB
has completed. The request will be rejected. When the original request issued with that
NRB completes, then the NRB will be once more updated with the status of that request.
0500* NETEX is not currently running on the local computer. Intervention by the local co mputer
operator will be required to start NETEX. This code is issued by the NETEX user interface
when it is determined that NETEX is unavailable.
0503* An OFFER, CONNECT, or ASSIGN request has resulted in the number of connections
outstanding for the caller exceeding an implementation defined maximum. The new connection request is rejected.
0505* NETEX is currently being drained in preparation for a NETEX shutdown. No new OF-
FER, CONNECT, or ASSIGN requests will be accepted. The request is rejected. The status of already existing connections is not affected.
0512* The NETEX program is aborting execution due either to internal NETEX software prob-
lems or cancellation by the computer operator. No further traffic with NETEX will be possible. This error will be issued to complete a request that was issued when NETEX was
running normally.
Session Errors
The following status codes are Session level errors that are returned in the NRBSTAT field, indicating
the completion status of a NetEx/IP request.
All errors that result in the loss of the connection and a Disconnect Indication in NRBIND are indicated
by an asterisk (*) following the error code number.
3005 During a WRITE operation, the length of the buffer as specified by NRBLEN exceeds the
maximum buffer size found in NRBBLKO. The WRITE operation is rejected. The connection remains outstanding.
3006 The length of PDATA sent on a CONNECT, CONFIRM, or DISCONNECT is greater than
the maximum allowed. The request is rejected.
3008 During a WRITE, NRBLEN exceeds segment size.
3100 The Sref specified by NRBNREF is not in use or is not owned by this applications program.
The request is rejected. The status of other connections owned by this application remain
unchanged.
3101 On an SWRITE request for intra-host communications, a DATAMODE was specified that is
not supported for internal communications.
3103 The quantity of Odata provided exceeds an implementation defined maxim. The request is
rejected.
3300 An SREAD or SOFFER request timed-out before a response was received on the network. If
the timed request is an SREAD, the status of the connection was not affected. If an SOFFER
timed out, then the connection will not have taken place.
Page 38 Appendix D MAN-REF-COSW 2.10-19
Page 46
3301 SCONNECT, SOFFER, or SCONFIRM has been issued for a connection that is already fully
established. The request is rejected. The status of the connections remains unchanged.
3302 A connect indication was received by a preceding SOFFER, and a request other than SCON-
FIRM or SDISCONNECT was issued. The request is rejected. NETEX will continue to wait
for the confirm or disconnect request.
3303 An SCONNECT request was previously issued, then a request other than an SREAD or
SDISCONNECT was issued. The request is rejected. NETEX will continue to wait for the
SREAD or SDISCONNECT request.
3304 The number of SWRITE requests outstanding against a single connection exceeds an imple-
mentation defined maximum (usually one). The SWRITE request is rejected. The status of
the connection and the previous SWRITE requests remains unchanged.
3305 The number of SREAD requests outstanding against a single connection exceeds an imple-
mentation defined maximum (usually one). The SREAD request is rejected. The status of
the connection and the previous SREAD requests remains unchanged.
3306 A SWRITE has been issued to a session connection that is in the process of servicing a re-
mote caller or NETEX initiated Disconnect. A Disconnect Indication is pending from NE-
TEX.
3307 A SREAD request has been issued to a session connection that is in the process of servicing a
remote caller or NETEX initiated Disconnect. A Disconnect Indication is pending from NE-
TEX.
3308 A write type request (SWRITE or another SCLOSE) has been issued against a connection
that has accepted a previous SCLOSE.
3402* The remote application has failed to issue an SREAD request for a period of elapsed time
(READTO) specified by the installation systems programmer on the remote host. The con-
nection is terminated. A Disconnect Indication will be found in NRBIND.
3403* The remote application exited without issuing an explicit Disconnect back to the local appli-
cation. The connection is terminated. A Disconnect Indication will be found in NRBIND
3422 HALTSREF was issued by operator.
3500* A connect message was repeatedly sent to the remote host in response to a previous TCON-
NECT request, but no response was received for a period of elapsed time (CONTO) specified
by the installation systems programmer. Probable cause is the absence of the NETEX soft-
ware on the remote host. The SCONNECT terminates with a Disconnect Indication in
NRBIND.
3501* The PNAME specified is not OFFERed on the HOST specified during the SCONNECT. The
SCONNECT terminates with a Disconnect Indication in NRBIND.
3502* The PNAME specified was not OFFERed on the HOST specified during the SCONNECT.
However, a session that was previously established by OFFERing the requested PNAME is
now in progress on the remote machine. If the remote application elects to re-OFFER the
connection in the future the service might be available at that time. (In other words, the re-
mote application is “busy.”)
3503* The number of user session connections permitted by NETEX has been exceeded. Session
service can not be offered at this time. The SCONNECT or SOFFER is rejected.
MAN-REF-COSW 2.10-19 Appendix D Page 39
Page 47
3504* Session service is not directly available to applications programs. This service can only be
made available by the installation systems programmer.
3505* NETEX is currently being “drained” by the computer operator. No new requests for Session
services (SCONNECT and SOFFER) are being accepted.
3506* The HOST specified in an SCONNECT request does not exist anywhere on the network gen-
erated by the installation systems programmer. The SDISCONNECT terminates with a Dis-
connect Indication in NRBIND.
3507* The HOST specified exists on the installation generated network configuration, but the local
computer operator has specified that no session level connections take place with that particu-
lar host. The SCONNECT terminates with a Disconnect Indication in NRBIND.
3508* The HOST specified exists on the installation generated network configuration, but no com-
munications path exists between the local host and the specified remote host. The SCON-
NECT terminates with a Disconnect Indication in NRBIND.
3509* The specified value of NRBBLKO exceeds an installation or implementation defined maxi-
mum. The connection request is rejected.
3510* The specified value of NRBBLKI exceeds an installation or implementation defined maxi-
mum. The connection request is rejected.
3511* The Class of Service request is not currently implemented.
3522* NETEX was drained while this outstanding OFFER was not complete.
3523* NETEX was DRAINed when a connect was received. This error is returned by the Session
Manager to the connector.
3550* The local host specified on an SOFFER or SCONNECT does not exist in the NETEX Ad-
ministrator’s NCT. The request is rejected at the Administrator.
3552* The local host specified on an SOFFER or SCONNECT request in not in the NETEX Admin-
istrator’s domain. The request is rejected.
3553* The Physical Address Map (PAM) sent along with an OFFER or CONNECT request to the
Administrator does not match any PAM that the Administrator can generate. The request is
rejected.
Page 40 Appendix D MAN-REF-COSW 2.10-19
Page 48
Appendix E: NESiGate Sense Bytes
NESiGate ESCON
Table 1. NESiGate ESCON Sense Bytes defines the sense bytes that are returned from the NESiGate
ESCON interface board.
Sense Bytes
0
X’80’ – Command Reject
X’10’ – Equipment Check
Table 1. NESiGate ESCON Sense Bytes
Subchannel not started error – only two byes of sense are returned X’8200’
On NESiGate offload (CO type) boxes, connect completion and write completion errors are returned as
follows:
Sense Byte
0
X’80’ – Command Reject .. X’03’ X’00’ “nrbstat” “nrbind” “nrbnref”
Table 2 NESiGate Offload (CO) Sense Bytes
See Appendix D. NRB Status Error Codes on Page 37 for details on “nrbstat” codes.
……
…… X’80’ – Data Timeout
X’10’ – Waitmsg Timeout
..
10 11 12 - 13 14 - 17 18 – 21
8
…..
….. X’2A’ – Data Timeout
X’2B’ – Waitmsg Timeout
31
MAN-REF-COSW 2.10-19 Appendix E Page 41
Page 49
Page 42 Appendix E MAN-REF-COSW 2.10-19
Loading...