HOST LINKS GLINE G&R Line Handlers and Configuration http://www.gar.
Microsoft, Windows, MS, MS-DOS are registered trademarks of Microsoft Corp. IBM and PC are registered trademarks of IBM Corp. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. Any other product names are trademarks of their respective owners. Version 6.1 © Gallagher & Robertson as 1990-2004 All Rights Reserved GALLAGHER & ROBERTSON AS, Kongens gate 23, N- 0153 Oslo, Norway Tel: +47 23357800 • Fax: +47 23357801 www: http://www.gar.
G&R Contents Installation........................................................................................... 1 Scope of the product ........................................................................... 3 Overview.............................................................................................. 5 G&R product architecture .......................................................................................... 5 Architecture diagram..................................................
G&R Connection errors.......................................................................................... 30 Parameters for DSA/DIWS handler .............................................................. 31 DSA and DIWS parameters in detail....................................................... 36 The TCP/IP handler.................................................................................................. 47 Making connections using TCP .........................................................
G&R The dsa.cfg configuration file................................................................................... 74 Overview....................................................................................................... 74 Configuration file directives ......................................................................... 76 SC - Session control ................................................................................ 76 RSC - Remote Session Control ..................................
G&R Appendix: Host Links Manuals..................................................... 107 Appendix: DSA test utilities........................................................... 109 Gerror.......................................................................................................... 109 Glnode......................................................................................................... 109 Gmacfix.........................................................................................
G&R Installation The G&R emulations and gateways are independent programs, but part of the G&R Host Links product set available on all major UNIX/Linux platforms. Many of the products are also available for Windows servers. For details on platforms supported, software delivery and installation refer to the Host Links Installation and Configuration manual. VTnnn, xterm, ...
G&R 2 Gline Line Handlers and Configuration
G&R Scope of the product G&R/Gline comprises a set of communications line handlers with a standard interface used by the G&R Host Links product set. The Gline line handlers standardize handling of any kind of communications line. This reduces application complexity, and makes applications portable across network environments. Applications are written using one of the communications libraries supporting the standard communications interface, GlAPI (Gline Application Programming Interface).
G&R 4 Gline Line Handlers and Configuration
G&R Overview G&R product architecture The G&R products are built in a modular way, and designed to take advantage of the multitasking capability of the Windows and UNIX/Linux platforms. Thus a single instance of a product will in general consist of two or three quite separate processes: • A video handler: which maps all updates of the internal screen image into the control sequences required to update the specific screen being used.
G&R Architecture diagram Clients for terminal users (V78sim, Qsim, G3270, G5250 Pthru) on UNIX and Linux only. Protocol dependent Communication Facilities Line Handler DIWS Product GWEB Video Handler CGI WEB SRV DSA V78sim Glink VIP Qsim X.
G&R Handler/product relationships Any product using the Gline API to communicate with the line handler can be run using any line handler. This is one of the strengths of the architecture. There are restrictions enforced by the external environment. For example the Questar DKU emulation Qsim can normally only be used over a link that the Bull primary network regards as synchronous. In practice this means it can only be run over a DSA/DIWS or TNVIP link.
G&R The G&R/Ggate product off-loads the DSA session protocol into gateways. By running Ggate on the system(s) with the mainframe connections the emulator platforms need only the very small and efficient Ggate protocol layer to connect over TCP/IP to a Ggate gateway with full native Bull network functionality. Ggate can make the mainframe connection using OSI-transport or RFC1006.
G&R Enclosures and ‘turn’ The interface between a Host Links product and the line handler is global throughout the G&R product range, and for all user applications using one of the GlAPI programmatic interfaces for communication. The functions for receiving and sending data include an indication of the ‘enclosure’ level for the data received, or to be sent. Enclosures are very important in the more advanced line handlers, particularly the Bull DSA handler.
G&R Whereas a simple handler might have no session protocol unit size restriction it might have a transport size restriction, or a network packet size restriction (e.g. TCP/IP packet size) that would cause fragmentation of the application record for transmission purposes. Depending on the interface between the handler and the lower level protocol this might cause the receiver to see a series of data blocks with enclosure ‘none’.
G&R Host Links Trace If you experience any kind of problem when using a Host Links application, the application trace file and/or the line handler trace file will provide useful documentation of the problem. Trace activation The Host Links products automatically create sub-directories in the debug directory when debug is activated: at product level using the -dbg parameter, or at line level using the -d_ or -s_ parameters to the line module.
G&R All Gline line handlers accept a parameter -s_ to turn on a session trace. It records the raw data being exchanged between the line module and the underlying transport layer (e.g. OSI Transport, or TCP socket), as well as internal events and protocol states. It is useful when investigating protocol failures such as unsuccessful connect attempts or abnormal disconnections.
G&R Tracing Ggate When Glink, a Host Links client or a customer application based on GlAPI connects through Ggate to the application, the line handler trace is generated on the Ggate system, with the name and location shown in the table: Windows server UNIX Linux \gar\debug\NODE\ggaNN-PPPP.dbg /usr/gar/debug/NODE/ggaNN-PPPP.dbg NODE is the local DSA node name used by the Ggate system. The trace file name consists of the prefix ggaNN- followed by the IP-address of the client, suffixed by .
G&R 14 qsm-gli.dbg Qsim host line trace -li dsa -s_ pth-glit.dbg Pthru terminal line trace -term -s_ pth-glih.dbg Pthru -host line trace -li dsa -s_ g32.dbg G3270 emulator debug file -dbg g32-gli.dbg G3270 host line trace -s_ /usr/gar/debug/mike Debug directory for user ‘mike’ v78.dbg V78sim emulator debug file -dbg v78-gli.dbg V78sim host line trace -li dsa -s_ guf.dbg GUFT client debug file -dbg guf-gli.
G&R gspd-gli.def Gspool DPS8 data trace -li tcp -s_ gsp._00 Gspool started on demand debug -dbg gsp-gli._00 Gspool started on demand trace -li dsa -s_ CPI-C and Gweb trace files Gweb uses the CPI-C libraries so the Gweb debug structure is exactly the same as for CPI-C, except that Gweb inserts its own product identifier into the file name structure.
G&R Example: \gar\debug\system 16 debug directory for user "system" cpi-16.dbg CPI-C single session debug -dbg cpi-16.gli CPI-C single session line trace -li dsa -s_ cpi2-123.dbg CPI-C session 2 application debug -dbg gw7-20172.
G&R Line handlers The DSA/DIWS handler You start this handler when you specify -li dsa or -li diws as the line handler for a Host Links product. If you connect via Ggate it creates a new line handler process or thread for you, and the new process/thread runs gl_dsa on your behalf.
G&R • Increased speed since the unneeded level of protocol translation is bypassed • Simpler DNS and/or mainframe configuration, as it’s likely that DSA session is already configured whereas DIWS is not • The DIWS protocol mode can still be used if you have historic reasons to do so. It implements DSA presentation over OSI session, interfacing to the OSI transport stack according to the Bull DSA/ISO workstation specification.
G&R Transport stacks The DSA/DIWS handler interfaces to a transport stack. The transport stack traditionally used by Bull front-ends and mainframes was the OSI-transport stack, and the Host Links products needed a corresponding OSI-transport stack in order to connect. This is no longer the case. Bull supports the Internet standard RFC1006 protocol layer, allowing native DSA sessions to be established over TCP/IP networks.
G&R OSI-transport The Host Links product set does not include an OSI-transport stack as a part of the standard delivery. If one is needed it must be ordered. We do not offer an OSI-transport stack for Linux; RFC1006 is the only choice. For most UNIX platforms an OSI-transport stack is available from the UNIX supplier. The great majority of the OSI stacks for UNIX systems come with a programmatic interface to the OSI-transport layer following the TLI, XTI or ISODE API standards, all of which we support.
G&R Accepting connections Products and applications receiving connections must configure a local node name using the -ln option, causing the line handler to accept incoming calls. The local mailbox name should then also be specified using the -mn option. Because a line handler can deal with only one incoming connection, a system accepting multiple simultaneous connections to a single node name must use a listener, described below.
G&R Listener parameter overview 22 Option value Explanation -prot DSA DIWS Session protocol to be used. Default DSA -dbg Enable data and event tracing. Write information to the debug file gli-gli.
G&R Using the Windows listener For Windows servers the nl_dsa line module server (listener) must be started before any Host Links product can use the DSA/DIWS line handler, see the section describing use of the DSA/DIWS handler on Windows servers on page 18.
G&R Mailbox pools for incoming connects Contrast this functionality with ‘Starting applications on demand’ described below. You can start multiple instances of products accepting connects to the same mailbox name on the same DSA node (SCID). Each instance should use a different mailbox extension.
G&R You can also accept multiple simultaneous incoming connects to GUFT servers with the same Host Links node name and mailbox name. The nl_dsa listener handles the implementation; so this must be started. A configuration file controls the mapping from the DSA mailbox name (-mn) and, optionally, extension (-mx) to the command line for the application to be started. There is one file for each DSA node name (SCID) for which connections are being accepted.
G&R The file above allows an unlimited number of simultaneous connections to mailboxes printer1, printer2 and printer3. For each connection to one of the mailboxes a new instance of the corresponding Gspool is started, regardless of how many were already executing. Connections to mailbox filtran each start a new instance of GUFTSRV. Only one instance of userapp is allowed to start, new connections to userapp are refused until the first instance terminates.
G&R Two-way-simultaneous sessions do not have a ‘turn’ concept, but the DSA session records indicate the enclosure level specified by the sender. Thus data blocks may be delivered with enclosure ‘end of group’ indicating ‘turn’. GCOS8 DACQ applications using interactive dialog will generally indicate ‘turn’ at the end of their output even if they are configured as two-way simultaneous. GCOS6 command mode does not indicate 'turn'.
G&R The connect command 3 different $*$CN formats can be used: Using a predefined CONAME from dsa.cfg to connect: $*$CN coname If the name given is not a predefined CONAME, it is assumed to be the application name and the connect will be carried out using the parameters set for the DSA session (i.e.
G&R If you set all connect parameters in the configuration file you can connect from most of the Host Links products using a single key connect command, or by transmitting $*$CN. Connecting to CXI applications You must use -HM CXI if you log in to GCOS8 via CXI. When you log in the endpoint (at least for TP8) is: node/mailbox/mailbox extension When you define a LID in TP8 one of the parameters is mailbox extension, usually set to be equal to the LID.
G&R The default configuration for break is: GCOS8 GCOS7 DNS Attention and purge Attention only Attention only For DSA300 applications (CXI applications such as TP8) an option 'data attention' may be negotiated. For these applications a data attention is used instead of attention when transmitting a break. $*$A1 sends attention type 1 as for break, but never purges undelivered data. $*$A2 sends attention type 2, no purge.
G&R Transport disconnect ‘Transport disconnect received’ errors after a connection attempt typically mean that you have a physical problem with the link or a network configuration problem. Look up the error code displayed in the XTI/OSI documentation. If you are using the Bull OSI-stack on an AIX platform use the pmaderror command to get the error code explained. Check with trace tools on the UNIX side if any packets leave the UNIX system.
G&R Parameter Description -AW on/OFF Delay initial turn from host (in the session accept) until real data is received on the session. -BRK AT/ATPGLT Can be used to override the defaults for purge handling on break. AT gives no purge, ATPGLT gives purge. See section entitled DSA/DIWS service messages. -CM xxxx Connection mode to be used when connection is initiated. Defaults to offer all modes.
G&R Parameter Description -DU xxxxxx -USR -USERID Default userid -DX xxxx -EXT Default application mailbox extension 4 characters.
G&R Parameter Description -MN xxxxxxxx -LMB Local mailbox name -MX xxxx Local mailbox extension. -NA xxx yyy zzz Send statistics to Gproxy network administration stations (up to 4 IP addresses may be given) -NB on/OFF Enable broadcasting for any/all Gproxy stations -PCO xxxxxx Associated printer session connection name -PCN on/OFF Associated printer session auto-connect -PTS ON/off Associated printer session turn simulation -PL nnn Page/screen length of terminal in lines (max.
G&R Parameter Description HDS7 7800 8-bit 72-line ASCII terminal -CS ASCII TWS2255V VIP7700 VIP7760 Early sync text/forms terminals. Replaced by VIP7800 and DKU DKU7001 DKU7002 Async, treated as TTY DKU7102 Async, but with forms and attributes DKU7007 DKU7107 Sync, text/forms DKU7007D DKU7107D Sync, text/forms, supporting local forms DKU7211 DKU7211D Colour model, without/with local forms DKU9107 8-bit PLW DKU for GCOS7 Diane. -CS EBCDIC DKU722X PRT722X Printers for DKU.
G&R DSA and DIWS parameters in detail -LI DSA and -LI DSA:GATEWAY Also -LI DIWS and -LI DIWS:GATEWAY These parameters start the DSA/DIWS line handler and select the protocol. If the colon and a gateway name are included, the handler is started on the Ggate gateway with the symbolic name or IP address GATEWAY. It also signals that the parameters following are for the line handler. The first group of line handler parameters MUST be preceded by a -LI parameter.
G&R -BT 1/2/3 This parameter changes the default for the break signal. The default for DSA200 is ‘Attention 1’ (-BT 1), with ‘Attention 2’ (-BT 2) used in special circumstances. The default for DSA300 is ‘data attention’ (-BT 3). Data attention is normally negotiated when needed by the mainframe, and this parameter is not necessary. -CM xxxx qsim -li dsa -cm TWAI This parameter sets a connection mode to be suggested to the other party when the connection is initiated.
G&R -CO xxxxxx qsim -li dsa -co b8dcacce This parameter sets a symbolic connection name. The line handler parameters are set in dsa.cfg for the CONAME. The line handler processes the -CO parameter by first resetting all line handler parameters to their default value, canceling any parameters set before -CO, and then expanding the CONAME. Any parameters after the -CO override the parameters set by the expansion, if allowed in dsa.cfg.
G&R This parameter enables the line handler’s data trace. Data sent and received to the client application is written to a file in the Host Links debug directory. If the -PCO parameter is included an additional trace file is written for the printer session. The trace file generated when this parameter is set, can be used as input to various debug tools used by G&R support in order to reproduce e.g. emulations problems. See section entitled Host Links trace.
G&R -DU, -USR, -USERID xxxxxx qsim -li dsa -du mmluser This parameter defines the default userid for the mainframe. -DX, -EXT xxxx qsim -li dsa -hm cxi -dx gr01 This parameter defines the default mailbox extension for the mainframe. The mailbox extension is used when connecting to CXI (GCOS8) subsystems such as TP8 (CXI requires that -HM CXI be set), and will normally contain the LID (Logical ID). The mailbox extension can be up to 4 characters long.
G&R Making connect parameters fixed value The following parameters stop the user from changing connection parameters that are set in the configuration file. -FA on/OFF qsim -li dsa -da tss -fa on This restricts connections to the default application name (-DA appl). It must be entered after the -DA parameter. -FM on/OFF qsim -li dsa -mn jim -fm on This locks the mailbox name (-MN mbxname). It must be entered after the -MN parameter.
G&R mode Explanation DPS6 Used when communicating with GCOS6 systems through SNM. DN Host type Datanet. Used when connecting to DNS applications. ROUTER Host type GCOS6 NTM. HostLink Used when communicating with another Host Links system. Gmailer and GUFT can make such connections. IBM Used when communicating with IBM hosts through the Janus/OSF gateway in the Datanet. -IE ON/off v78sim -li dsa -ie OFF This controls insertion of ETX/CR at the end of messages.
G&R -LT XXXX gspool -li dsa -lt grdw This defines a non-standard local node name for outgoing connections. XXXX must match an SC record in dsa.cfg. -MN, -LMB xxxxxx qsim -li dsa -mn mike This sets the local mailbox name. It can be up to 12 characters long. Characters 9-12 become the extension and can be set separately with -MX. By default the handler assigns unique mailbox names based on the program’s process id (pid) in the form Dnnnnn.
G&R This enables broadcasting of network administration information to systems running Gproxy. Broadcasts allow multiple, but unspecified, systems running Gproxy to monitor G&R products. This is especially important for servers such as Ggate, GwebS and GlinkJS for which Gproxy can load-balance and license-share. -PCO xxxxxx qsim -li dsa -co tp8_app -pco printsess This associates a CONAME for a printer with the terminal session.
G&R -SX on/OFF qsim -li dsa -sx on This selects Scandinavian transliteration tables for conversion between EBCDIC and ASCII. The -SX parameter transliterates EBCDIC #@$ to ASCII [\]. It is seldom used, even in Scandinavia. -S_ on/OFF Windows Server gspool -id gs1 -ps \\SERVER\LEXMARK -li dsa -da tptst -s_ on UNIX Linux gspool -id gs1 -pc lp -li dsa -da tptst -s_ on This enables the session trace in the line handler.
G&R -UD, -UR, -STR, -STRG xxxxxx qsim -li dsa -hm dps8 -ur glid qsim -li dsa -hm dps7 -ur !NEW This defines the default user record for the mainframe to which you are connecting. It can be 2-32 characters long, and is normally used to deliver the GRTS id (GRID) for connection to DAC programs on GCOS8, or the Logical id (LID) when connecting to TDS or DMIV-TP by DACQ.
G&R The TCP/IP handler You start this handler (gl_tcp) when you specify -li tcp as the line handler for a Host Links product. When you connect from one G&R product (or GlAPI application) to another the TCP/IP handler uses a ‘raw’ mode; the application data is simply packed in TCP packets and transmitted with no higher-level protocol involved.
G&R Service messages The TCP handler accepts service messages for connect ($*$CN), disconnect ($*$DIS) and break ($*$BRK) from the communications product using the handler. You can type them and transmit when using an emulator or concentrator. User applications using one of our communications APIs from the GlAPI library must send the $*$CN, $*$DIS and $*$BRK messages themselves when the Gline API is used, but they will be sent automatically by CMALLC, CMDEAL and CMSERR when one of our CPI-C APIs is used.
G&R The disconnect and break commands All systems accept: $*$DIS force disconnection (normally done by application). $*$BRK interrupt application, against turn if necessary.
G&R Parameter Description -HO hostname:port Numeric/symbolic IP-address, optional port -HW n Enable ‘delayed enclosure’.
G&R -AM XXXXXX This is used to select a mode of operation. The following modes are available: -AM mode Description RAW In this mode all data is passed to the application with an end of data marker. CRTERM In this mode all data buffers are marked with a ‘more data’ marker until a Carriage Return (CR) is found. When CR is received the data passed to the application is marked with an end of data marker.
G&R TN3270 and TN3270E Gweb, G3270 and Gspool use these modes. In TN3270 mode Gweb, G3270 and Gspool can select LU name. Gspool supports TN3270 print as specified in RFC1646 and used in the SNA gateway from Open Connect Systems. In TN3270E mode G3270 supports the ATTN and SYSREQ keys as well as selection of a specific LU name. Gspool can be configured as a generic printer or associated printer through the use of TCP line handler parameters -LU and -AP.
G&R -DN ipaddress:port v78sim -li tcp -dn 192.150.211.4:9998 This selects the server to which you connect. You can use its numeric IPaddress or you can use its symbolic name. In the latter case it must be registered in your hosts file or with your name server. You can append a colon and a numeric port number or use a symbolic name. In the latter case this symbolic name must be registered in your services file. -D_ on/OFF Windows Server gspool -id gs1 -ps \\SERVER\LEXMARK -li tcp -am tnvip -d_ on -ho some.
G&R -LP local port myglineapp -li tcp -lp 9999 This parameter selects the local port for incoming connections, and enables accept of incoming connections. You can use the port number or a symbolic name. In the latter case this symbolic name must be registered in your services file. The default is to not accept incoming connections. It defaults to raw mode. -LU LUname This is used in TN3270 mode to ask for a specific LU name on the host side. -NU on/OFF v78sim -li tcp -nu on This enables Telnet CRNUL mode.
G&R -S_ on/OFF Windows Server gspool -id gs1 -ps \\SERVER\LEXMARK -li tcp -am tnvip -s_ on -ho some.gcos.system UNIX gspool -id gs1 -pc lp -li tcp -am tnvip -s_ on -ho some.gcos.system Linux This enables the line handler’s session trace. It documents session, transport and internal events along with inbound and outbound data sent and received through the underlying socket interface. -TM terminal_type This selects terminal type for Telnet negotiation performed in application-mode TN3270, TN5250 or TNVIP.
G&R The default value in application mode TN5250 is IBM-3179-2. G5250 -li tcp -tm ibm-3179-2 For TNVIP the terminal types listed in RFC-1921 are VIP7700 VIP7760 DKU7005 DKU7007D DKU7105 DKU7107D DKU7211 DKU7211D VIP7804 VIP7804V VIP7814 HDS7 VIP8800 DKU terminal types ending in D imply local form support. Local forms are not supported in our UNIX/Linux based DKU emulations (they are supported in Glink).
G&R The X.25 handler You start the X.25 handler (gl_x25) when you specify -li x25 as the line handler for a Host Links product. It is only available for the UNIX/Linux version of Host Links, and only on some of the platforms. Making connections using X25 Accepting a connect The X25 handler by default does not accept connections because the ‘outgoing only’ parameter (-OO) is by default ON. If it is set OFF products and applications receiving connections can use the handler.
G&R User applications using one of our communications APIs from the GlAPI library must send the $*$CN, $*$DIS and $*$BRK messages themselves when using the Gline API, but they will be sent automatically by CMALLC, CMDEAL and CMSERR when one of our CPI-C APIs is used. The PAD service messages can only be used from the Gline API. The connect command $*$CN remoteaddress,userdata The only information required is the X.25 number to be called in numeric format, and the user data if needed in hexadecimal.
G&R Parameters for the X.25 handler The following parameters apply to this handler (defaults in uppercase): Parameter Description -LI X25 Start gl_x25 -AC on/OFF Accept reverse charges -CR on/OFF Insert CR at end of message -D_ on/OFF Write Gline data trace to Host Links debug -DS xxxxxx/NONE Default Remote address. -DU hxhxhx/NONE Default Remote User data -EB on/OFF Use EBCDIC on line -LU hxhxhx/NONE Local User data -HW n Enable ‘delayed enclosure’.
G&R 60 Parameter Description -XS nnn/NONE Facility code: Transmit packet length override -XW nnn/NONE Facility code: Transmit window size override Gline Line Handlers and Configuration
G&R The Asynchronous (TTY) handler You start the TTY handler (gl_tty) when you specify -li tty as the line handler for a Host Links product. It is only available for the UNIX/Linux version of Host Links. Making connections using TTY Accepting a connect The TTY handler accepts connects in the sense that it sees the status of the line change if the other side (e.g. a modem) takes up the correct signals, and reports this as an incoming connect to the Host Links product.
G&R Service messages The TTY handler accepts service messages for connect ($*$CN), disconnect ($*$DIS) and break ($*$BRK) from the communications product using the handler. User applications using one of our communications APIs from the GlAPI library must send the $*$CN, $*$DIS and $*$BRK messages themselves when the Gline API is used, but they will be sent automatically by CMALLC, CMDEAL and CMSERR when one of our CPI-C APIs is used.
G&R Parameters for the TTY handler The following parameters apply to this handler (defaults in uppercase): Parameter Description -LI TTY Start gl_tty. -BM on/OFF Block mode. ETX/EOT used as end of record mark. -CR on/OFF CR mode. CR used as end of record mark. -D_ on/OFF Write Gline data trace to Host Links debug directory. -DN XXXXX Device name. Name of async port.
G&R 64 Gline Line Handlers and Configuration
G&R DSA Configuration Step-By-Step Guide Configuration check list Before you start to configure the mainframe and Host Links system you must obtain the configuration parameters you will need. If you already have a functional network, you do not need to change the configuration of the mainframe. Obtain the parameters from the network administrator.
G&R The Host Links system • The DSA node name (SCID, session control ID) for the Host Links system If DSA session is to be used for DSA200 connections: • The local DSA area address (the TSN, e.g.
G&R RSYS NAME = GRDL, PF = ‘STID/ISO/SID3’, RSC = GRDL; RSC NAME = GRDL, ADDR = DSA, SCID = 54:060, SVR=NCC1; Or as follows for a DIWS Host Links system: RSYS NAME = GRIL, PF = ‘STID/ISO/SID3’, RSC = GRIL; RSC NAME = GRIL, ADDR = DSA, SCID = 54:060, SVR=NCC1,PRTC=SID; Front-end configuration If the connections go through a FEP, the FEP must have both the mainframe and Host Links systems configured.
G&R SRISO RSCA RTSEL RNSAP ROUTE LLAN LLAN -RNSAP_NAME NSGRDLI -NAME GRDL -TYPE D6SC -RNSAP_NAME NSGRDLI -T_SEL -HEX 4002454C3344 -TU_SIZE 1024 -CLASS 4 -WINDOW 1 -MIN_CRED 1 -NO_CHECKSUM -NAME NSGRDLI -OWNER ISOT -NSAP NSEN3CI -NAME RTGRDLI -PROTOCOL CLNP -SUBLAYER LACS –NULL -LOCAL_SAP LPTP30 -REMOTE_SAP GRDLSAP -L_USER LPTP30 -R_USER LN3DSAP -FRAME 1497 -L_USER LPTP30 -R_USER GRDLSAP -FRAME 1497 and in >sid>lanc-f REMSAP GRDLSAP,,X’20’/X’0000C0E9A8E6’ Another Host Links system If you want to communi
G&R Configuring the Host Links system Configuring the transport stack DSA is a session level protocol that runs over a transport stack. Traditionally DSA ran over the OSI-transport stack and a LAN or WAN network. Today the vast majority of networks are built of commodity products using the TCP/IP communications stack.
G&R Configuring Host Links It is assumed here that the Host Links software, and OSI-transport, if used, is already installed on the target platform. For a detailed description of the installation process, see the Host Links Installation and Configuration manuals for UNIX and Windows. The dsa.cfg file You must configure the local Host Links system as well as the remote host systems you will access.
G&R The listener The listener is used for distribution of incoming connections from the remote host(s) to the Host Links applications. The listener must be used if several Host Links applications will receive incoming connects using the same local DSA session control name (TSAP). The listener should be started automatically whenever the Host Links system is restarted. If the receiving applications are started before the connections arrive then no listener configuration is necessary.
G&R Establish the physical connections X25 connections For a public X25 connection simply connect the appropriate cables to the X25 DCEs. Most DCEs have LEDs that indicate the state of the link. In most cases the link will be opened when the Host Links platform is started (i.e. before any connections take place).
G&R Host Links tools If you are using OSI-transport there are usually internal debug and trace tools supplied with the communication stack. Check the documentation from the stack supplier, and see the platform-specific hints given in the Host Links installation and configuration manuals for UNIX and Windows. There are several Host Links utilities and debug tracing routines you can use.
G&R The dsa.cfg configuration file Overview One or more local session control entities (SC) must be defined. These are looked up using the value of the -ln line module option and contain the DSA session control name and number of the local UNIX/Linux or Windows server system, to be used by applications accepting incoming connects. The SC is also used to identify the calling Host Links node on outgoing connections. Remote session control entities (RSC) must be defined.
G&R Access to undefined connection names may be configured to be either an error or to be ignored (COSTRICT). Arbitrary options or groups of options may be restricted to clients passing a security filter (-FILTER). The security filters referred to above are lists of IP addresses, IP network numbers, names of local hosts or names of applications. Each element in the list may either be permitted or denied access. There is no limit on the number of objects that may be defined.
G&R Configuration file directives In the syntax used below UPPERCASE is used for the fixed keywords and lowercase for the variable parameters. Brackets [...] are used around optional keywords. The vertical line | is used to separate alternatives. Symbolic names you define may be from 1 to 12 characters long and if they contain spaces the name must be enclosed in quotes. The order of the directives in the file is irrelevant except for the PARAMS and POOL cases mentioned below.
G&R -UNAME is optional. It’s the system’s UNIX/Linux or Windows server communications node name. NB! it is not the DSA node name. This name can be displayed using the command uname –n on UNIX/Linux systems, and displayed in the Network section of the control panel on Windows server systems. When looking for an SC the software first looks for one with a matching UNAME, but if none is found it looks for one without a UNAME.
G&R -TS points to a TS (Transport Station) directive somewhere else in the file. If you omit the option the default TS is used. rsc is2b rsc en3e -addr 54:62 rsc is2b -ii 15 -ts fep1_wan To set up backup routes you just specify multiple -ts routes: rsc -ts route1 route2 route3 These are then tried in order until a connection succeeds or the end of the list is reached.
G&R -CLASS is required and must be set to 0 for RFC1006 connections, 2 for WAN/X.25 connections and 4 for LAN connections. -NS is also required and for some stacks is a symbolic pointer into the transport configuration, but in others is the real network address. It (or the real address it points to) must be set to the X.25 address of the transport station for WAN/X.25 connections, the MAC or FDDI address of the transport station for LAN connections or the IP name or address for RFC1006 connections.
G&R Deriving -NS for FDDI hosts All Ethernet MAC addresses are in ‘LLC’ format. All FDDI addresses are in ‘SMT’ format. In SMT format you will see the address in the MSB (most significant bit) form. You will however normally, for instance in the case where you connect via an Ethernet port of a LAN Extender, see the LLC format only. If you connect to an FDDI adapter directly or by an FDDI port of a LAN Extender, you must convert the MAC address to SMT.
G&R For Marben on Windows servers: Specify either WAN or LAN. For SUN Specify a local network layer address as configured in the local OSI stack. For Bull: Specify the X.25 or MAC address of the local OSI-transport interface you will be using. Alternatively give the value ‘rfc’ in order to signal the use of RFC1006, and select the Bull-supplied RFC1006 (NetShare). On AIX it is also legal to give a value of the form pvc-xxxx to signal the use of the X.25 PVC named xxxx.
G&R CONAME - Connection Name CONAME name [-DESC desc] [-FILTER filter] [-PARAMS params] [-POOL pool] [-TYPE TERM | PRINT] [Gline parameter list] Defines a connection name. e.g. coname tssprod -desc “TSS production” -filter block_remote -scid is40 -dmb tss * Gline parameter list for all users The CONAME parameters if used must be on the same line as the CONAME keyword. The optional list of Gline parameters must be on a single new line 82 -DESC adds a verbal description of the CONAME.
G&R Gline parameters Gline parameters can be added to the CONAME directly, or via PARAMS or POOL directives. By default Gline parameters can be overridden by the client, but this can be inhibited using the ‘+’ character as a prefix to the parameter in the directives in dsa.cfg. The client can be requested to ask for a parameter interactively using the ‘*’ character for the parameter.
G&R coname tssprod -desc “TSS production system” -params tssprod -scid is40 -dmb tss * Gline parameter list for all users params tssprod -filter john -usr john -pw calvin * parameters for John only params tssprod -filter sue -usr sue -pw hobbes * parameters for Sue only POOL - Parameter Pool POOL name [-FILTER filter] Gline parameter list [Gline parameter list] Defines a pool of connection parameters. There may be multiple POOL directives with the same name.
G&R filter permit filter permit bergen tcp 192.150.212.[00-10] lillehammer tcp 192.150.213.4 * macro for group * single user Macro facility A simple macro facility eases configuration of parameters for large numbers of sessions. It expands numeric ranges only. Multiple macros on the same line must have the same range. You may use up to 8 macros on each line. e.g.
G&R RESTRICT - Parameter Restrictions RESTRICT [-FILTER filter] Gline parameter list [Gline parameter list] Defines Gline parameters that should be restricted from general use. If a filter is specified then only those that are permitted by it are subject to the restrictions. While this may seem backwards at first glance it was done this way so that all the directives can be read the same way, namely that the directive is visible only if the filter specified returns the client as permitted.
G&R running Qsim, V78sim etc. will match filter lines with LOCAL specified. Local clients are the Host Links products on the system that owns the /usr/gar (UNIX/Linux) or \gar (Windows) directory, or on other systems that mount it over the network. Clients coming in through Ggate will match filter lines with TCP specified. Any client will match filter lines with APPL specified. TCP expression: The expression is IPaddress[/bits].
G&R USER expression: The expression is the user name that is supplied by the client in the ‘logon packet’ (in the -us parameter). The user name is normally the user account name in the local client network. The asterisk (*) matches anything. Glink clients need version 6.1.4 or later. For Host Link applications, release 5.3 or later is required. NODE expression: The expression is the unique workstation (‘node’) name supplied by the client in the ‘logon packet’ (in the -st parameter).
G&R restrict -filter internal # addresses passing the filter cannot choose -dn * # the default node to which they connect -da * # the application mailbox to which they connect -ln * # or to listen for incoming connects filter internal deny tcp 192.150.211.0/24 deny tcp 193.71.16.
G&R Sample dsa.cfg for RFC1006 GC8F GC7F FCP8 FCP7 FDDI Bull hosts and FEP G&R Host Links nodes ONP 1 HL0 2 LAN HL01 Brief description of the configuration HL01 - is a Host Links node with a LAN connection to a MainWay (ONP1). The ONP adapter in the MainWay supports RFC1006 and acts as a network switch that passes on the DSA session records to GC8F and GC7F. The MainWay sees HL01 as both a DSA and a DIWS node.
G&R The Host Links node ‘HL01’ Windows Server UNIX/Linux \gar\config\dsa.cfg /usr/gar/config/dsa.cfg # Local Host Links DSA node HL01 # sc hl01 -addr 49:001 # local G&R RFC1006 transport provider (IP=202.1.1.1) tp rfc -who gar # # Remote DPS7000, DSA node GC7F thru LAN connected ONP1 # rsc gc7f -addr 49:007 -ts onp1 # # Remote DPS9000, DSA node GC8F thru LAN connected ONP1 # rsc gc8f -addr 49:008 -ts onp1 # transport station route (Mainway) ts onp1 -class 0 -ns 202.1.1.
G&R The DPS9000 node ‘GC8F’ Osi.cfg STACK I_NOERRFLAG NETSHARE TCIVMO NAME=IVMO8 TPUSIZE=1024 NRSC NAME=HL01 NRTS=HL01TS NRTS NAME=HL01TS TYPE=INET IP_ADDR=202.1.2.1/102 NRSC NAME=HL02 NRTS=HL02TS NRTS NAME=HL02TS TYPE=INET IP_ADDR=202.1.2.2/102 Routes.
G&R The MainWay & & LOCAL MAINWAY NODE 'ONP1', ADDR=49:005 & SC ONP1 LOC -ADDR 49:005 -ISOPLG TS ONP1 LOC -ADDR 49:005 -NET 492008003811008D -CNX 900 & & & SC SR TS NR PL & & & SC SR TS NR PL & & & SC & SR TS & NR LL CT & DPS7000, SC RMT GC7F GC7F GC7F GC7F GC7F GC7F RMT ISO DIWS LAN1 CSM1 RMT ISO DIWS LAN1 CSM1 ADDR=49:007 -ADDR 49:007 -SR GC7F -NAT DSA -TS GC7F -NR GC7F -PL GC7F -CB ETH1 -ETHAD 080038100FE7 DPS9000, SC RMT GC8F GC8F GC8F GC8F GC8F GC8F -SERV CONS ADDR=49:008 -ADDR 49:008 -SR GC8
G&R Sample dsa.cfg for OSI Transport This sample configuration is meant to cover many of the most used configuration scenarios and will hopefully be useful when setting up new configurations or modifying existing ones. It shows various types of Bull mainframe systems and some G&R Host Links nodes. Both LAN and WAN configurations are included in addition to a simple example of an FDDI link.
G&R Brief description of the configuration For simplicity all GCOS6 hosts are referred to as DPS6s, all GCOS7 hosts as DPS7s and all GCOS8 hosts as DPS8s except for the ones with FCP8 adapters, which are referred to as DPS9000s: GRDL - is a Host Links node with both LAN and WAN connection. It is configured to reach a DPS7 over LAN (ISL) and a DPS8 over WAN (through the FEP). It can be seen as both a DSA and a DIWS node by the mainframes.
G&R The configuration files The Host Links node ‘GRDL’ Windows Server UNIX/Linux \gar\config\dsa.cfg /usr/gar/config/dsa.cfg # dsa.cfg: Configuration for G&R Host Links node GRDL # Local node. DSA/DIWS type, LAN access and WAN access.
G&R rsc b8dc -ts dn01_lan ts dn01_lan -class 4 -ns 080038200557 -tp gril_lan # A DPS8 system, B8DF, direct FDDI access to FCP8 rsc b8df -ts b8df_fddi # # # ts NB! the FDDI MAC address (10001c08082a) must be specified in SMT format.
G&R The Host Links node ‘GRIW’ Windows NT/2000 UNIX \gar\config\dsa.cfg /usr/gar/config/dsa.cfg # dsa.cfg: Configuration for G&R Host Links node GRIW # Local node. DIWS type, WAN access only.
G&R TERM TERM RTERM TERM -NAME SNM150 -MODE USER -NTD NTDVIP -TYPE DKU7107 -EL 150 -NAME ROP150 -MODE IMPLO -NTD NTDVIP -TYPE TTU8125 -EL 150 -NAME PRX150 -CM DSA -AD1 GRDL -AD2 ROPGRDL -GN ROP150 -NAME SNM151 -MODE USER -NTD NTDVIP -TYPE VIP7804 -EL 151,152,153,154,155,156,157,158,159 -- LRNs from clm_user * Remote nodes RTSEL -- -DEFAULT -CLASS 4 -TU_SIZE 1024 -- if no matching RTSEL * G&R Host Links node GRDL, LAN access, DSA type SRISO RSCA RTSEL -RNSAP_NAME NSGRDLI -NAME GRDL -TYPE D6SC -RNSAP_
G&R * various local SAPs * LCLSAP LXPT18,,X’F8’/X’080038363E18’ LCLSAP LDDS18,,X’14’/X’080038363E18’ LCLSAP LTNV18,,X’28’/X’080038363E18’ LCLSAP LPTP18,,X’20’/X’080038363E18’ * * GRDL SAP and MAC address * REMSAP GRDLSAP,,X’20’/X’02608C200441’ * * GRIL ditto * REMSAP GRILSAP,,X’20’/X’02608c2d8023’ * * local physical line * PLIN PHY18,CSMA,X’1800’,0 LCLSAP LMAC18,,X’080038363E18’ The DPS7 node ‘B7DL’ COMM COMM SYS ‘Sample DPS7 config (extract)’ ‘B7DL DPS7000 local definitions’ NAME=B7DL PF=LSYS SCID=1:4 I
G&R routes.wdf: # # Local session control for ‘B8DF, channel fe4 (in routes.wdf) # create_node_route_list gril -nrl fe4 loadscen: # # FCP8 MAC (LLC) Ethernet address (in loadscen file) # sti W3NX00T20010 macadr 080038101054 The Datanet node ‘DN01’ &*********************************************************** & G&R Host Links DSA node ‘GRDW’.
G&R SC B8DC RMT SR B8DC CXI CH B8DC CXI -ADDR 1:2 -SR CXIA -CH B8DC -CT DIA1 -T1 6000 -T2 2400 -CNX 1000 &*************************************************** & DPS7000 with channel access &*************************************************** SC B7DC RMT -ADDR 1:3 -BRK AT -SR B7DC SR B7DC GC64 -CH B7DC CH B7DC GC64 -T3 3000 -RCH 8 -CNX 200 -CT PSI1 CT PSI1 PSI -PHAD X’0C00’ -MXCH 16 &*************************************************** & Local LAN connection &************************************************
G&R A shared dsa.cfg for all the Host Links nodes In some situations it makes sense to build and maintain one dsa.cfg file for all the Host Links nodes in the network. If two or more Host Links systems share a dsa.cfg file in a shared file system you must use the -UNAME directive to assign parameter values to the correct Host Links system. The -UNAME parameter can also be useful if you prefer to maintain a single copy of the dsa.
G&R # The Dps8 system (DNET/ROUT and CXI), accessed over X25 in DN01 rsc b8dt -addr 1:1 -ts dn01_wan rsc b8dc -ts dn01_wan # The DN, used for WAN access to Dps7 and Dps8 ts dn01_wan -class 2 -ns 130399 -tp wan # Host Links systems rsc grdw -addr 54:58 -ts grdw_wan ts grdw_wan -class 2 -ns 130366 -tp wan rsc griw -ts griw_wan ts griw_wan -class 2 -ns 130367 -tp wan # Remote systems accessed over LAN # Various G&R Host Links systems rsc grdl -addr 54:60 -ts grdl_lan ts grdl_lan -class 4 -ns 02608c200441 -tp
G&R Gline Line Handlers and Configuration 105
G&R 106 Gline Line Handlers and Configuration
G&R Appendix: Host Links Manuals Below you find a complete list of all available Host Links manuals: Installation Host Links Installation and Configuration on UNIX/Linux Host Links Installation and Configuration on Windows Line handling Gline Line Handler and DSA/OSI Configuration Ggate Transparent Gateway Gproxy Network Manager & SNMP Proxy Agent G&R SSL Using SSL for security in G&R products GlAPI Application Programming Interfaces Emulations Gspool Network Printer Emulation GUFT Unified
G&R 108 Gline Line Handlers and Configuration
G&R Appendix: DSA test utilities The Gline package includes a set of Gline communication utilities. These are used when testing and debugging connection problems. The utilities are delivered as part of the Gline package and can be used without any additional configuration. The nodes to be tested must of course be configured in the dsa.cfg file. Gerror Show the text message associated with a DSA reason code. Only the most common codes are supported i.e.
G&R Gmacfix When connecting to the FCP cards on the Bull mainframes via an Ethernet port on the LAN-Extender the address on the host side is given in the Ethernet (LLC) format. If you connect to an FDDI adapter directly or by an FDDI port of a LAN Extender, you must convert the MAC address to SMT. This utility can be used to convert the address format. Typically Bull LLC MAC addresses start with 080038 and the FDDI address starts with 10001C.
G&R Gtrace Same as gping but writes the DSA/DIWS communication trace on the user’s terminal (applicable to UNIX versions) Example: gtrace -li dsa -dn ln40 -da snm151 D6:Application event @ 14:17:17.6003. tokenitem = 00 D6:Application event @ 14:17:17.6082. tokenitem = 00 D6:Connect request called, node = LN40 D6:OurBufferSizes. ApplMaxXmit = 511, ApplMaxRecv = 500 Rec:4000 0002 s:2 Rec:506B 0010 s:16 etc etc Gtrace - line trace ending. Gtrace - $$DSA: Connected to application.
G&R 112 Gline Line Handlers and Configuration
G&R Appendix: Error Codes OSI/DSA error codes Below is a list of OSI/DSA error codes and the corresponding description. These are the same descriptions that the G&R/Gerror utility will display when given the DSA code as a parameter.
G&R 0013 0014 0016 0017 0018 0019 001A 001B 001C 001D 001F 0020 0021 0022 0023 0024 0030 0031 0033 0039 003C 003E 003F 0040 0041 0042 0044 0045 0047 004F 0050 0051 0052 0053 0054 0055 114 Open Failure in LC, connection is not negotiated in FD mode / impossible to start the IOF job Disconnection - Timeout resulting from absence of traffic. Option missing for an RBF mailbox. Connection refused - Incorrect access right for MB. Connection refused - Incorrect access rights for the application.
G&R 0056 0057 0058 0059 005A 005B 005C 005D 005E 005F 0060 0061 0062 0064 0065 0066 0067 0068 0069 006A 006B 006C 006D 0078 0079 007F 0081 0082 0083 0085 0086 Error or Event on LC initiated by GW. GW has no known explanation. Error or Event on LC initiated by GW. Reject mailbox permanent Error or Event on LC initiated by GW. No more input lines in DACQ Time-out on GCOS 3/8 gateway. Error or Event on LC initiated by GW. Disconnect from terminal without reason Error or Event on LC initiated by GW.
G&R 0087 0090 0092 0093 0094 0096 009C 009D 009E 009F 00B2 00B6 00C0 00D7 00DE 00E1 00E6 (X.25) Frame level reset. Frame level not set. (X.25) X.25 Echo service in use. (X.25) Incorrect password for PAD connection. (X.25) No more PAD connections allowed. (X.25) TS SX25 or NU X25 objects locked. (X.25) Invalid packet header. X.25 protocol error. (X.25) Incompatible header. X.25 protocol error. (X.25) Logical Channel Number too high. (X.25) Incorrect packet type.
G&R 0117 0118 0119 011A 011E 011F 0120 0121 0122 0123 0124 0125 0126 0127 0128 0129 012B 012C 012D 012E 012F 0130 0131 0132 0133 0134 013C 013E 013F 0140 0151 0152 0153 0154 0156 0157 0158 0159 015A Incorrect Access Right for MB Incorrect Access Right for the Application Pre-negotiated Message Path Descriptor unknown Security validation failed Incorrect object status Not enough memory space available. Node unknown.
G&R 015B 015C 015D 0160 0161 0162 0163 0164 0165 0166 0167 0168 0169 016A 016B 016C 016D 016E 016F 0170 0171 0172 0173 0174 0175 0176 0177 0178 0179 017A 017B 017C 017D 017E 017F 0180 0181 0182 0190 118 Negotiation failed on resynchronization (in the Logical Connection record). Negotiation failed on end-to-end ACK (Logical Connection record). No support of the "letter" interface because Multirecord is not negotiated. Incorrect TSPACNX table. Protocol error on letter reception. Negotiation failure.
G&R 0191 0192 0193 0194 0195 0196 0197 0198 0199 019A 019B 019C 019D 019E 019F 01A0 01A1 01A2 01A3 01A4 01A5 01A6 01A7 01A8 01A9 01AA 01AB 01AC 01C0 01C1 01C2 01C3 01E0 01E1 01E2 01E3 01E4 01E8 01E9 Byte count is greater than GP. Byte count is greater than GP. Byte count is greater than GP. Byte count is greater than GP. Byte count is greater than GP. Byte count is greater than GP. Byte count is greater than GP. No more buffers. Byte count is greater than GP. Byte count is greater than GP.
G&R 01EA 01EB 01EC Write segmented letter request without turn. Send control letter request without turn. Disconnection request without turn. 02xx Presentation Control 0201 0202 0203 0204 0205 0206 0207 0230 0231 0232 0233 0234 0235 0236 0237 Protocol level not supported Application designation protocol error. Character encoding error. TM cannot support the proposed encoding. Character set error. TM cannot support the proposed character set. Character subset error.
G&R 0323 0324 0325 0326 0327 0328 0329 032A 032B 032C 032D 032E 0330 0331 0332 0340 0341 0342 0343 0344 0345 0346 0347 0348 0349 034A 0350 0360 0361 0362 0370 0371 0372 0373 0374 0375 0376 0380 0381 0382 Intervention required (on principal device). Request not executable. EOI required. Presentation space altered, request executed. Presentation space altered, request not executed. Presentation space integrity lost. Device busy. The device is busy and cannot execute the request. Device disconnected.
G&R 0383 0384 038C 0390 0391 0392 03C0 Desynchronization in the exchange of data. KDS block count error. Remote terminal is not connected Unknown mailbox. No call packet to return. No "Possibility" command to return Protocol error Slave device disconnection. 17xx Network Layer 1701 1702 1706 1707 1708 1709 1710 1711 1712 1713 1714 1717 1718 1719 171A 171B 171C 171E 171F 1721 1723 1724 1725 1726 1727 1729 1731 1732 1733 1740 122 PAD connection refused. Flow control error.
G&R 1741 1742 1744 1745 1747 1749 174F 1755 1760 1770 1771 1781 1782 1783 1785 1786 1787 1790 1791 1792 1793 1794 1795 179B 179D 179E 179F 17A0 17B0 17B1 17B2 17B3 17B4 17B5 17B6 17B8 17B9 17CB Open failure on virtual circuit. No flow control on this NS. Incorrect facility. Protocol error for the equipment directly connected to the Bull Datanet. Unknown subscriber. End of time-out on reset confirm. Invalid facility length. Protocol error for the equipment directly No logical channel available.
G&R 17CC 17CE 17CF 17D0 17D4 17D7 17DD 17DE 17DF 17E0 17E1 17E2 17E3 17E4 17E5 17E6 17E7 17E9 17EB 17EE 17FF Incompatible generations (NR object without mapping). Invalid status NR locked. Lack of space. Unknown subscriber. TSCNX already used for another connection. SCF internal error. Transport station locked. Proper NS locked. Invalid status NR locked. Lack of space. Forbidden parameter or invalid value. Invalid transition. Upward-mapped object (TS) not locked. No object mapped above.
G&R 1824 182E 182F 1831 1832 1833 1834 1835 183A 183C 1840 18A1 18B0 18EF Collision between Close NC and Open TC. Remote station not configured. Resource saturation. ISO: No route for the called NSAP. ISO: Received NSAP addresses are wrong. Segmentation violation. ISO:QOS priority not available temporarily, due to a local condition (for example, lack of resources). ISO:QOS priority permanently unavailable locally (for example, due to an error in the system generation). ISO: Remote reason not specified.
G&R 2735 WSAEALREADY 2736 2737 2738 WSAENOTSOCK WSAEDESTADDRREQ WSAEMSGSIZE 2739 WSAEPROTOTYPE 273A WSAENOPROTOOPT 273B WSAEPROTONOSUPPORT 273C WSAESOCKTNOSUPPORT 273D WSAEOPNOTSUPP 273E 273F WSAEPFNOSUPPORT WSAEAFNOSUPPORT 2740 WSAEADDRINUSE 2741 WSAEADDRNOTAVAIL 2742 WSAENETDOWN 2743 WSAENETUNREACH 2744 WSAENETRESET 2745 2746 2747 WSAECONNABORTED WSAECONNRESET WSAENOBUFS 2748 WSAEISCONN 126 The asynchronous routine being cancelled has already completed.
G&R 2749 274A 274B 274C WSAENOTCONN WSAESHUTDOWN WSAETOOMANYREFS WSAETIMEDOUT 274D WSAECONNREFUSED 274E WSAELOOP 274F 2750 2751 2752 2753 2754 2755 2756 2757 276B WSAENAMETOOLONG WSAEHOSTDOWN WSAEHOSTUNREACH WSAENOTEMPTY WSAEPROCLIM WSAEUSERS WSAEDQUOT WSAESTALE WSAEREMOTE WSASYSNOTREADY 276C WSAVERNOTSUPPORTED 276D WSANOTINITIALISED 2AF9 WSAHOST_NOT_FOUND 2AFA WSATRY_AGAIN 2AFB WSANO_RECOVERY 2AFC WSANO_DATA Gline Line Handlers and Configuration The socket is not connected.
