Gallagher & Robertson Pthru Terminal Gateway, G3270, Qsim, V78sim Emulator, Ggate, Gsftp Gateway, Gweb Web Browser, Gspool Print Spooler, GUFT File Transfer, Gproxy Network Management User Manual

HOST LINKS
PTHRU
G&R
Terminal
Gateway
to the
Bull Primary
Network
http://www.gar.no/hostlinks/
TM
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.5
© Gallagher & Robertson as 1990-2010
All Rights Reserved
GALLAGHER & ROBERTSON AS, Kongens gate 23, N- 0153 Oslo, Norway
Tel: +47 23357800 • Fax: +47 23357801
www: http://www.gar.no/
e-mail: [email protected]
Contents
Contents
Host Links Pthru ................................................................................ 1
Installation.................................................................................................................. 1
Host Links Product Overview .................................................................................... 1
Terminal environment..................................................................................... 1
Server environment ......................................................................................... 2
Scope of the product................................................................................................... 3
Functionality............................................................................................................... 3
Network connections.................................................................................................. 3
Integration .................................................................................................................. 4
Run-time licenses ....................................................................................................... 5
Pthru service messages ....................................................................... 7
Using DSA ................................................................................................................. 7
Using TNVIP ................................................................................................ 12
Pthru Function keys ......................................................................... 13
Printing .............................................................................................. 15
Hard copy ................................................................................................................. 15
Host print output....................................................................................................... 15
Gspool ........................................................................................................... 15
Emulator print ............................................................................................... 16
File transfer ....................................................................................... 17
Unified File Transfer ................................................................................................ 17
Kermit and MML ..................................................................................................... 17
Gallagher& Robertson
Pthru
i
Contents
Commands......................................................................................... 19
Command overview ................................................................................................. 19
Command interface .................................................................................................. 19
Commands in detail.................................................................................................. 20
Command shell ($*$!)................................................................................... 20
Change context ($*$#) .................................................................................. 20
Call the directory manager ($*$$)................................................................. 21
Send a break to the host application ($*$B).................................................. 21
Disconnect from host application ($*$D) ..................................................... 22
Execute UNIX/Linux command ($*$E)........................................................ 22
Call the Host Links Help facility ($*$H) ...................................................... 23
Quit, leave the gateway ($*$Q)..................................................................... 23
Set parameter ($*$S)..................................................................................... 23
National character sets ..................................................................... 25
Internal character set ................................................................................................ 25
Using 8-bit terminals..................................................................................... 25
Using 7-bit terminals..................................................................................... 25
Mainframe character set ........................................................................................... 25
National 7-bit character sets.......................................................................... 25
8-bit character sets......................................................................................... 25
Startup/Configuration...................................................................... 27
Terminal types.......................................................................................................... 27
User terminal................................................................................................. 27
Mainframe terminal....................................................................................... 27
Command line .......................................................................................................... 28
Configuration file (<product>.cfg)........................................................................... 28
Using Ggate.............................................................................................................. 29
Using TNVIP............................................................................................................ 30
Pthru parameters....................................................................................................... 31
Host Links user profiles............................................................................................ 32
Profiles file structure ..................................................................................... 32
Line handler parameters ........................................................................................... 33
Line parameters for DSA .............................................................................. 33
Line parameters for TCP/IP .......................................................................... 33
Terminal line parameters............................................................................... 34
ii
Pthru
Gallagher & Robertson
Contents
Troubleshooting ................................................................................ 35
Product trace files..................................................................................................... 35
Line handler trace files ............................................................................................. 35
When connecting through Ggate .............................................................................. 36
The TTY line handler ............................................................................................... 36
Appendix: Host Links Manuals....................................................... 37
Appendix: Host Links DSA Utilities ............................................... 39
Gconame ....................................................................................................... 39
Gerror............................................................................................................ 40
Glnode........................................................................................................... 40
Gmacfix......................................................................................................... 40
Gping............................................................................................................. 40
Grnode........................................................................................................... 41
Gtrace............................................................................................................ 41
Gtsupd ........................................................................................................... 41
Appendix: Host Links Trace ........................................................... 43
Trace activation ........................................................................................................ 43
Trace types ............................................................................................................... 43
Structure ................................................................................................................... 44
Tracing Ggate ........................................................................................................... 45
Examples - G&R products........................................................................................ 45
CPI-C and Gweb trace files...................................................................................... 47
Appendix: Error codes ..................................................................... 49
OSI/DSA error codes................................................................................................ 49
Windows Sockets error Codes.................................................................................. 61
Gallagher& Robertson
Pthru
iii
Contents
iv
Pthru
Gallagher & Robertson
Pthru
Host Links Pthru
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.
Host Links Product Overview
Terminal environment
Host links products that run on UNIX or Linux servers with a terminal driven
user interface include emulators and concentrators, as well as various utilities.
•
G3270
provides synchronous IBM3270 functionality. G3270 emulates
IBM LU type 2, including base and extended colour together with
extended highlighting.
•
Qsim
provides synchronous Questar terminal functionality. Qsim
simulates all Questar models, including the DKU7007, DKU7107,
DKU7105 and DKU7211 (Mono, four colour A/B and seven
colour modes are supported). It also simulates the VIP7760 and the
VIP7700.
•
V78sim
provides Bull VIP78xx (BDS) functionality. V78sim emulates all
models of the VIP7800 family; the actual reference is the BDS7.
All visual attributes including colour are supported.
•
Pthru
provides transparent VIP7800 visibility to Bull mainframes for
users with asynchronous VIP7800 terminals or emulators. The
terminals are used in text or forms mode.
Gallagher& Robertson
Pthru
1
Pthru
Server environment
Host Links products that run on UNIX, Linux or Windows servers.
2
• Ggate
is a transparent gateway to the Bull native network. It avoids all
need for Front-ends (MainWay/Datanet) or other gateways. It can
be used to connect G&R/Glink (for Windows or Java) emulators
or any of the emulators, concentrators, network printer emulators
and file transfer clients/servers in the Host Links product set. It
also supports third party clients using the TNVIP, TN3270,
TN3270E and standard asynchronous Telnet protocols.
• Gweb
provides a web browser interface to any host application that is
otherwise accessible using the Host Links Qsim, V78sim, or
G3270 emulations.
• Gspool
is designed to run as an unattended process and accept transparent
print output from any type of host application (GCOS8, GCOS7,
GCOS6, IBM) that normally sends print data to network printers
(ROPs), or to a remote spooling system (DPF8-DS). On the
Gspool system the print may be directed to a physical printer or to
the local spooling system. Gspool operates in different modes,
Connect mode, Terminal Writer mode, DPF8 mode, SNM mode,
IBM mode, TN3270 mode and TN3270E mode.
• GUFT
is a G&R implementation of the Bull UFT file transfer protocols. It
enables transfer of data files between Host Links and GCOS systems
over a DSA network.
• Gproxy
is a network management program used for supervision,
management, load balancing and license sharing of G&R Host
Links applications. Gproxy can be set up as a freestanding
monitor program and/or report generator in a small network, or
play a bigger role in a larger network.
• Gsftp
is a transparent gateway between two different File Transfer protocols: FTP (RFC 959) and SFTP (the SSH File Transfer Protocol).
The purpose is to present a seamless integration between the two
protocols, with automatic conversion.
Pthru
Gallagher & Robertson
Pthru
Scope of the product
Functionality
G&R/Pthru provides transparent VIP7800 visibility to Bull mainframes for users
with asynchronous VIP7800 terminals or emulators connected to a UNIX or
Linux system. The terminals are used in text or forms mode. Pthru transforms the
system into what appears to the mainframe as a synchronous VIP7800 terminal
cluster. Pthru is not available for Windows. PC users with our G&R/Glink
terminal emulator can also connect to Bull mainframes using Pthru, but it is more
efficient for a Glink user to connect via G&R/Ggate. Glink users can also
connect to Bull mainframes as VIP77xx, DKUxxxx or IBMxxxx terminal types,
and Pthru will select the appropriate emulation mode in Glink when started, but
again, these connections can be made more efficiently using G&R/Ggate.
Network connections
DSA connections can be made in the traditional way using OSI-transport, which
is a requirement when connecting via old-style Datanets. The Bull systems can
be accessed over an X.25 WAN or Ethernet LAN through a Datanet or MainWay
front-end. Alternatively access can be direct to GCOS6 using a LAN adapter or
direct to GCOS7 using ISL. Access can be by an FDDI LAN direct to GCOS7
using FCP7 or direct to GCOS8 using FCP8 (both support OSI-transport).
DSA connections can also be made over a TCP/IP network, using the Internet
standard RFC1006 transport protocol to replace OSI-transport. MainWay frontends with an ONP (Open Network Processor) have RFC1006 support in the
standard product, allowing DSA sessions over TCP/IP into the MainWay.
RFC1006 can also be installed in the FCP7 and FCP8 cards to support DSA
connections direct to the mainframes without passing through the front-end. The
GNSP of newer GCOS8 systems and the Open System personality of GCOS7
Diane systems both support RFC1006 connections.
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. If
you must use OSI-transport for the mainframe connection, using Ggate will limit
the need for OSI-stacks to the Ggate platforms.
Gallagher& Robertson
Pthru
3
Pthru
The Host Links Installation and Configuration manuals cover the OSI stack
installation and setup for the supported UNIX and Windows server systems.
Bull systems can be accessed using Telnet, TNVIP, TN3270 or TN3270E to
connect to a Bull front-end. However, Ggate with RFC1006 increases throughput
as compared to these gateways. Ggate also gives a real, fully functional DSA
session over the TCP/IP network, as compared to the limited terminal session
offered by TNVIP, TN3270 or Telnet. Third-party clients with only
Telnet/TN3270/TNVIP protocol can connect via Ggate, which supports these
protocols on the client side.
Integration
Pthru allows you to execute local UNIX/Linux commands or the command shell,
and you can switch to other Host Links products, all while keeping one or
more mainframe sessions alive. This includes the Interactive Help System that
has all the information available in this manual. System administrators may
easily customize the menus provided.
In order to provide a command interface to the Pthru program itself, to the Host
Links facilities and to UNIX/Linux services a command syntax is implemented
in the familiar form of $*$command. However, when running a host
application it may be difficult to issue these commands, so the -F12 parameter
may be used to make F12 a command key, and issue the $*$ prompt in the
status line. Users with VIP7800 terminals will find this convenient. For users
with G&R/Glink a background script is provided to monitor the LF (GREY -)
key, and give an interface.
4
Pthru
Gallagher & Robertson
Pthru
Run-time licenses
In order to run Pthru, the following license keys must be present in your
/usr/gar/config/licenses file:
basic
For the base G&R run-time system
pthru
For Pthru
The licenses file identifies the G&R distributor, the owner of the license and the
licensed products. The license key for a product will normally state how many
simultaneous sessions the product is licensed for. If a limitation is specified in
the license, only the licensed number of sessions can be active at any time.
Gallagher& Robertson
Pthru
5
Pthru
6
Pthru
Gallagher & Robertson
Pthru
Pthru service messages
A connect command (F12 C when using the -F12 parameter) causes Pthru to
make a connection request using the parameters set in the configuration file.
However you may do your own connect by entering a connect command string;
Using DSA
The line handler accepts service messages for connect $*$CN, disconnect
$*$DIS, break $*$BRK (attention, and possibly purge undelivered data,
depending on configuration of the mainframe, and/or application), the two
attention signals $*$A1 (attention type 1), $*$A2 (attention type 2),
identification query $*$ID and lower case support $*$LC ON/off from the
communications product using the handler. You can type them and transmit
when using a Host Links emulator or Glink/Ggate. Unknown service messages
(messages beginning with $*$ but where the 2-3 following characters are not
recognized) will cause an error message.
Interpretation of service messages within the message text can be disabled
(-DSD OFF as an emulation parameter or CFIX 2875 in Glink) so that they
are transmitted as data to the mainframe. The emulators all have command keys
for issuing service messages that may be used instead of typing $*$ if
interpretation is disabled.
User applications using one of our communications APIs from the GlAPI
library must send service 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.
Gallagher& Robertson
Pthru
7
Pthru
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. explicitly by parameter setting from command line and/or
the configuration file)
Using the traditional G&R positional $*$CN format:
GCOS8 connect to 'appl' (application)
$*$CN appl,node[,str,password,person,project,billing]
GCOS7 connect to 'appl' (application)
$*$CN userid,project,billing,appl,password,node[,,str]
Using the Terminal-Manager keyword connect format:
$*$CN -scid NODE -dmb APPL –ext . . .
The following key words can be used:
-dmb, -ext, -scid, -lmb, -str, -usr, -ba, -pj, -pw, -mdmp
A GCOS8 connect normally requires only application and node, but you may
need to specify a GRTS ID or LID depending on Datanet configuration. This is
supplied as -str. You will need password, person, project if the target
site has the ‘Secure Workstation Environment’, or is using the IDCHECK
package developed by Bull Norway for securing networks.
8
Pthru
Gallagher & Robertson
Pthru
A GCOS7 connect normally requires you to set all of the documented parameters. The string (-str) is used by GCOS7 to set application options. These
are:
IOF:
![NS] [NM] [NEW]
$station-name
*environment
e.g. –str “!NM NEW”
e.g. –str “!NM NEW $STA1”
e.g. –str “!NM NEW $STA1 *ENV1”
Note that when using multiple space-separated options they must be enclosed
in quotes.
NS
NM
NEW
station name
environment
No Startup, user specific information suppressed
No Mail, user messages suppressed
New session, previous interrupted session lost
station for JOR and SYSOUT
IOF user context for session
TDS
?<option>[%string OR <length><system-header]
e.g.
–str ?B40D25
-str ?A%JIM
option
A: system messages and edited mode
B: system messages and unedited mode
C: no system messages and edited mode
D: no system messages and unedited mode.
8 alphanumeric characters to be input to the first TPR of the
LOGON transaction
service message header in the form of an alphanumeric
prefix or a control code
string
header
Note that you can set the default values for the connect commands with parameters in the configuration file, but that if no default is configured then the last
value used for this particular field becomes the default. So if you make an error
in one of the parameters you need not specify the others in your next connect.
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.
Gallagher& Robertson
Pthru
9
Pthru
Connecting to GCOS8 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. In the connect ($*$CN) the first parameter
(mailbox name) can be specified as follows:
$*$CN XXXXXX YYYY,node
XXXXX the TP8 mailbox
YYYY
the extension for your LID
When the remote mailbox string contains 8 characters you must follow the
mailbox string with the mailbox extension string without a space separator.
Alternatively the remote mailbox is configurable as default application (-DA)
and in the same way the extension is configurable as default extension (-DX).
The disconnect command
$*$DIS
force disconnection (normally done by application).
10
Pthru
Gallagher & Robertson
Pthru
The break commands
$*$BRK
sends attention type 1, against turn if necessary. The host, and/or application
session may be configured to purge undelivered data when a break is sent.
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.
The identification inquiry
$*$ID
returns the local DSA session control name, the local mailbox name and the
terminal type used e.g.
$$DSA: Your ID is: SC:EN3D MB:D24701
Gallagher& Robertson
Pthru
TM:DKU7107
11
Pthru
Using TNVIP
The TNVIP handler (-li tcp –am tnvip) handles $*$CN, $*$BRK and
$*$DIS, but the connect format is different.
The only information required is the IP address in symbolic or numeric format
and the port number if it is not the standard Telnet port e.g.
$*$CN hostname:portnumber
12
Pthru
Gallagher & Robertson
Pthru
Pthru Function keys
The function keys on the synchronous and asynchronous versions of the
VIP7800 family are defined as sending a control sequence to the host. This
sequence is sent transparently through Pthru, and will be interpreted by the host
application, as for directly connected terminals. Consult the VIP7800 or
G&R/Glink reference manual for the control sequences generated, and the
possibilities for modifying them, or other keyboard sequences.
Despite the wish for transparency, there is still a need to give commands to the
UNIX/Linux operating system. A command interface is implemented using the
$*$ syntax familiar from dialogue with the Datanet. If the -F12 parameter is
used F12 will act as a prompt for the $*$ command sequence. Pressing F12
again causes the F12 sequence to be transmitted. Pressing any other F-KEY will
cancel the prompt. Otherwise the commands may be entered as documented in
the commands section on page 19.
Gallagher& Robertson
Pthru
13
Pthru
14
Pthru
Gallagher & Robertson
Pthru
Printing
Hard copy
Host Links has a generic hard copy function in the video interface, but this is
not available in the Pthru product because all presentation is being done by the
VIP7800 terminal or by G&R/Glink on the PC.
Host print output
Gspool
As a print output station the Host Links mainframe print spooler
G&R/Gspool is recommended. Gspool is designed to run as an unattended
process and accept transparent print output from any type of mainframe
application (GCOS8, GCOS7, GCOS6, IBM) that normally sends print data to
network printers. On the Gspool system the print may be directed to a physical
printer or to a file for spooling.
For all IBM print Gspool supports unformatted and formatted print (LU type 1
and 3) and SNA Character String (SCS) codes directed to an IBM3287 printer.
In IBM mode Gspool supports printers configured in a Bull front-end with the
OSF SNA gateway (Janus). The front-end has the Gspool node and mailbox
name configured as the location of the printer. Gspool waits for the connect
request from the front-end.
In TN3270 mode Gspool supports printers via a TN3270/SNA gateway as
specified in RFC1646. In TN3270E mode Gspool supports TN3270E print as
specified in RFC1647 via a TN3270E/SNA gateway. It can be configured as a
generic printer or associated printer through the use of TCP line handler
parameters -LU and -AP. Microsoft’s MS SNA Server (MS Windows NT),
Bull’s TN3270E server in MainWay and Bull’s SNA/20 (AIX 4.1) are examples
of SNA gateways that support RFC1647.
Gallagher& Robertson
Pthru
15
Pthru
In SNM mode Gspool supports network printers configured in the SNM (GCOS6
Secondary network manager). When started with the 'no connect' option (-CN
off), Gspool will wait for the connect request from SNM.
In GCOS8 or GCOS7 mode Gspool supports network printers configured in TP,
TDS or Twriter. For Twriter Gspool waits for the connect from GCOS7.
In DPF8-DS mode (-DPF8) Gspool supports the ‘DPF8-Distributed SYSOUT’
(‘DPF8-DS’) product on GCOS8. In this mode Gspool starts two TCP/IP line
handlers and waits for remote connect requests from DPF8-DS.
For more information about Gspool see the Gspool manual.
Emulator print
For occasional print output to the user terminal the emulators handle print from
the mainframe. The print may be sent within the terminal session, or the
mainframe may send to a separate print session that is associated with the
terminal session using the merged print feature.
If the mainframe addresses the printer on the terminal using VIP7800 print
control sequences embedded in the data, then these are passed transparently to
the terminal, and will cause the print to be done on the attached printer.
If the mainframe addresses a separate print session, but you want this print
session to be associated with the attached printer on your terminal, then you must
configure the attached printer session in your dsa.cfg, and use the -PCO parameter. Please refer to the Gline manual for details of configuring a separate
printer session.
16
Pthru
Gallagher & Robertson
Pthru
File transfer
Unified File Transfer
Host Links has an implementation of the Bull Unified File Transfer (UFT)
facility for transferring large quantities of data between the GCOS and local file
systems. G&R/Guft is available both as a server and a client. The server version
accepts incoming file transfer requests initiated from TSS or IOF on the Bull
mainframes. You can use the client version to initiate transfers from your UNIX
or Linux workstation.
Kermit and MML
While in interactive dialog with GCOS you can use the G&R implementation of
the GCOS 'Kermit' (FTRAN, GKRM or other Kermit versions).
On GCOS8, use the TSS command FTRA PC7800, or start the GKRM system.
On GCOS7, use the MICROFIT command FTRAN MICROSYS, but you must
log in through the MICROFIT system. In both cases the emulator recognizes
the FTRA start-up.
If you have an ordinary terminal, or if you set parameter -GK ON, then the
emulator will ask direction and mode, then start G&R/Gkerm (the Host
Links Kermit, which is FTRA compatible). The file will be transferred between
the mainframe and the local file system.
If your terminal is a PC with G&R/Glink, then the default action is to enter
pass-through-mode and allow Glink to deal with the FTRA. The Glink
Kermit window pops up, and you will be allowed to select direction and
ASCII/Binary. The file will be transferred direct between the mainframe and
your PC. In case of error, pass-through-mode can be terminated by transmit of a
null block and the FTRA can then be terminated with a break (LF B).
Gallagher& Robertson
Pthru
17
Pthru
18
Pthru
Gallagher & Robertson
Pthru
Commands
Command overview
You can type the following commands immediately after a $*$ sequence to
perform a Pthru command function. You can type the $*$ or obtain it as a
prompt from F12. For Glink users a user-friendly interface for sending these
commands while using a host application is provided by the Glink script
PTHRU.SCR, which if executing in the background will be activated by the LF
(GRAY -) key, to give a pop-up menu of commands available.
1(9)set count for command
! start the command shell (on gateway, UNIX)
# change context (1-9)
(followed by count)
$ directory administrator
B send break to the host
C connect to host
D disconnect from host
E execute command
(followed by the command)
H call help facility
Q exit Pthru concentrator
S set Pthru parameter
Command interface
Pthru examines all messages from the terminal that begin with $*$ to see if they
are Pthru commands, but if not they will be delivered to the Gline interface
rather than rejected as they may be Gline commands. Typing a $*$ command
sequence may be impossible while running a host application so Pthru allows
F12 to be configured as a prompt key (-F12 parameter), and the status line is
used to collect the command. For Glink users a background script is available
that collects commands locally through pop-up menus, and transmits them without affecting the host screen image.
Gallagher& Robertson
Pthru
19
Pthru
During execution of commands that use the terminal the screen image has to be
saved and restored on return to Pthru. For Glink users the image is saved on the
PC to save network traffic. For terminal users the image is saved in the
UNIX/Linux file system:
/usr/gar/pthru_sv/$logname/pthru.cxn
the n in .cxn is the context number where Pthru is running. Directory
pthru_sv should exist, and the users should have directory create permission.
Commands in detail
Command shell ($*$!)
If you are working within the Host Links systems and are an advanced user,
a UNIX/Linux specialist or the system administrator you might find it
convenient to start a command line shell in order to work with UNIX/Linux
commands for a period, without losing your Host Links context. Thus you
can maintain several host connections or other activities while you temporarily
work at command level.
F12 !XMIT
--> start a command line shell
This may be inhibited in your profiles file (NOEXEC).
Change context ($*$#)
The Host Links multi-context feature is a set of utilities for allowing user
friendly access to the UNIX/Linux multitasking capability such that a user may
have several facilities in use at the same time and jump between them as desired
without terminating or restarting. For example, you can start several copies of
Pthru, each of them logged on to different host applications and then switch
between these applications as desired.
Each facility started by the Host Links multi-context feature is defined as an
active context. If you have installed this software, then the $*$# command
allows you to jump directly to another active context.
A context number (1-9) is assigned to each active context. You set the desired
context number by using a repetition count:
20
Pthru
Gallagher & Robertson
Pthru
$*$#
$*$# 1
$*$# 9
-->
-->
-->
switch to context menu
switch to context 1
switch to context 9
or with -F12 parameter:
F12 #
F12 # 1
F12 # 9
-->
-->
-->
switch to context menu
switch to context 1
switch to context 9
Call the directory manager ($*$$)
The G&R/Gdir file manager is a fully compatible interactive menu driven
replacement for standard file commands in UNIX/Linux. It provides facilities for
navigating in the directory structure and for creating and releasing files.
It also has a facility for activating the alphanumeric keyboard with user-oriented
functions that can then be executed with a single keystroke. These functions may
contain any command, and the name of the file or directory being pointed to with
the cursor in the file display is available as a parameter to the commands.
The file manager is integrated with a configurable editor and print system, so the
file pointed at may be read in to an editor or printed.
For a detailed explanation, enter the manager and type LF H.
G&R/Gdir is bundled with all Host Links products. G&R/Gdir may be
inhibited in your profiles file (NODOLLAR).
Send a break to the host application ($*$B)
Several of the host systems you may access have situations where they keep the
initiative in a dialogue, and if you want to regain it you are required to transmit a
break signal. Please do not confuse this function with the BREAK key on your
asynchronous terminal.
Because the host has the initiative, your keyboard may be locked for normal
typing, unless inhibited with -LK off. However if running Glink script
PTHRU.SCR you may send a break to the host with LF B, which will normally
cause the host to give you the initiative.
Gallagher& Robertson
Pthru
21
Pthru
You may of course unlock the keyboard manually. You can then use the
command $*$B by typing normally or using F12 for the $*$ prompt. You can
send a break by typing:
$*$BRK <TRANSMIT>
Disconnect from host application ($*$D)
Disconnect from a mainframe application by entering the log-off sequence
required by the host and transmitting. The mainframe will close the current
session and a 'Disconnected' message will appear on your screen.
If this log-off procedure for some reason fails, you can send a session disconnect
request to the mainframe by entering the Pthru command $*$D by typing
normally or F12 prompt. Normally you will then receive a disconnect
confirmation message. You may also type manually:
$*$DIS <TRANSMIT>
Execute UNIX/Linux command ($*$E)
This command allows you to execute a UNIX/Linux command without exiting
from Host Links. The following variations are available:
$*$E
command
$*$E
*command
$*$E
**command
$*$E ***command
$*$E ****command
-->
-->
-->
-->
-->
show command, execute, wait for CR
cursor to 1/24, execute, don't wait
same as the above
execute command, no refresh
execute command, refresh screen
All save and restore the screen except the 3 asterisk mode, which does not
restore afterwards; so data written by the application to the screen is still there
when Pthru regains control. Use four asterisks when starting Host Links or
other full screen products that begin by blanking or otherwise initializing the
screen.
This may be inhibited in your profiles file (NOEXEC).
22
Pthru
Gallagher & Robertson
Pthru
Call the Host Links Help facility ($*$H)
This calls the G&R/Gmenu facility, which is an independent system that
executes outside of the products. The menu facility navigates in a series of
menus and/or information pages, and most Host Links products have a set of
help menus that may be consulted using the system. Your own applications may
also use it. Menus and information pages may be added or changed by the user or
system administrator.
The G&R Gmail reference manual describes how to maintain the menus and
information pages. G&R/Gmenu is bundled with all Host Links products.
Quit, leave the gateway ($*$Q)
This command is used to terminate Pthru. The host log-off sequence should be
sent and a disconnect confirmation received before entering this command. However, if you leave Pthru with an active session, the network software will do an
abnormal disconnect to close it.
Set parameter ($*$S)
You can set parameters when you start Pthru, or afterwards by using the $*$S
syntax, typed manually, or from the F12 prompt. The following format should
be used:
-XX parameter1 -YY parameter2
If a parameter is for the line handler module the -LI argument should precede
the actual parameter:
-LI DSA -XX parameter
For an overview of the parameters available see the Pthru configuration menu.
This may be inhibited in your profiles file (NOPARAM).
Gallagher& Robertson
Pthru
23
Pthru
24
Pthru
Gallagher & Robertson
Pthru
National character sets
Internal character set
When you use the Pthru the gateway machine will not involve itself in national
character transliteration. Characters will be sent to the host exactly as they are
received from the VIP7800 terminal or emulator.
Using 8-bit terminals
Only the VIP8800 is regarded as an 8-bit terminal by the mainframes.
Using 7-bit terminals
The VIP7800 models are all regarded as 7-bit by the mainframes.
Mainframe character set
National 7-bit character sets
The mainframe to which you connect may use a national 7-bit set. If you use a
national 7-bit VIP7800 terminal or character set within Glink then both
representations of national characters use the same 7-bit equivalents (square and
curly brackets etc.).
8-bit character sets
All of the GCOS mainframes (GCOS6, GCOS7, GCOS8) have 8-bit capability
in the sense that characters can be stored as 8-bit bytes, but the communications
software involved often undermines this capability. The front-end software or the
mainframe terminal-handling package may not recognize the terminal as having
an 8-bit capability, and may cut off the top bit.
Gallagher& Robertson
Pthru
25
Pthru
The standard VIP terminal types are defined as 7-bit. There is an encoding
(SI/SO) for 8-bit, but this is not supported by the mainframes. There is a
VIP8800 terminal type that is defined as 8-bit, and this must be used when
connecting to 8-bit mainframes. The communications software may support it.
G&R native 8-bit connections
The G&R DSA/DIWS interfaces, and G&R/Ggate provide an 8-bit connection to
GCOS mainframes.
If your mainframe is a GCOS7 system it only supports 8-bit ASCII sessions for
VIP8800. If your GCOS7 system is a Diane, then you can use the 8-bit terminal
types and associated 8bit printer type specially defined for G&R to Diane
communication. These were defined for GCOS 7 TS 9910 and need the
following co-requisite patches:
Q1606.02, Q1607.03, Q1608.04, Q1609.02
Additionally the definition of the new models must be appended in the H_TERM
sub-file of the SYS.HSLLIB library as follows:
DEFLIKE EXTYPE=VIP9800,LIKE=HDS7,DSAMODEL=20A3,CSETTYPE=9
DEFLIKE EXTYPE=PRT9220,LIKE=PRT1220,DSAMODEL=20A4,CSETTYPE=9
26
Pthru
Gallagher & Robertson
Pthru
Startup/Configuration
Terminal types
User terminal
The type of terminal being used to run Pthru is taken from the Host Links
configuration of the user. The Host Links terminal type is taken from the
UNIX/Linux TERM variable. If the TERM variable cannot be set correctly, the
Host Links terminal type can be overridden using the VIDEO directive in the
Host Links PROFILES file, see below. Pthru supports only two terminal types,
real VIP7800 asynchronous terminals (or standard emulations of it) and
G&R/Glink. Choosing a TERM name that starts with VIP indicates a real
VIP7800 terminal and restricts the command set that Pthru uses to control it.
Choosing a TERM name that starts with GLINK allows Pthru to use the extended
command set supported by G&R/Glink.
Mainframe terminal
The default mainframe terminal type is set to VIP7804. This can be changed
using the -TM parameter to the line handler, see the section entitled Line handler
parameters. Users with a real VIP terminal must choose the appropriate VIP as
the mainframe terminal type. Glink users can choose any VIP7800 terminal type
as necessary for the mainframe application.
For Glink only, you can specify the mainframe terminal type as a VIP77xx,
DKUxxxx or IBMxxxx assuming the mainframe connection supports the
terminal type. This will cause Pthru to switch Glink into the appropriate
emulation mode.
Gallagher& Robertson
Pthru
27
Pthru
Command line
An example command line:
pthru –F12 -LI DSA -HM DPS7
Parameters for the G&R emulators and gateways are divided into two categories,
parameters for the product itself and parameters for the line handler. Parameters
for the product must precede the -LI argument that signals that the rest of the
parameters are for the line handler module.
The -USER and -HOST parameters may later be used to switch between
product and line parameters. Parameters may be pre-configured on:
/usr/gar/config/$LOGNAME/<product>.cfg
The user ($LOGNAME) directory may be replaced with default to give a
configuration for users with no private directory.
Configuration file (<product>.cfg)
The configuration file is grouped into sections.
Default
Parameters apply to all users
User user(.accnt.mode)
Parameters apply to this user only
Terminal terminal-name
Parameters apply to this terminal only
TermUser terminal user
Parameters apply to this combination only
ContextUser ctx user
Parameters apply to user in this context
The 'User' identifier may be in the standard star format, or the .accnt.mode
part can be omitted altogether. Comment lines are denoted by an asterisk or hash
(*, #) in column 1, and may appear anywhere in the file. A section header must
appear before the first parameter, but sections may be in any order. Both section
headers and parameters can be indented for clarity. The file is processed
sequentially and subsequent parameters will override any previous parameters of
the same type.
28
Pthru
Gallagher & Robertson
Pthru
Parameters for the product must be preceded by -USER if any line parameters
have been delivered previously, e.g. in the Default section. Line parameters
must always be preceded by -LI XXX.
In the following there are line parameters in the Default section, so the
parameters in the user sections must be preceded with -USER, and the user's line
parameters must be preceded with -LI XXX again.
e.g. /usr/gar/config/default/pthru.cfg
Default
-LI DSA -D? OURGCOS6
User Peter
-LI DSA -HM DPS7 -DA IOF -DN P7 -D? SECRET
-DP DEVELOP
User Mary
-USER -F12-HOST -DA TSS -DN PROD8 -HM DPS8
A user with a private configuration file would only have directives associated
with his/her sessions. For a user with a private file the default file is not read or
used.
Line parameters that are associated with the host rather than with the user can be
configured in the dsa.cfg file. See section entitled Line handler parameters.
Using Ggate
The G&R emulators and gateways support the G&R/Ggate protocol and may
access the Bull or IBM mainframe through a G&R/Ggate system. In this case
there is no need for a DSA stack on the system running the emulator. The
emulator can use the Ggate protocol on top of TCP/IP to communicate with
Ggate, and Ggate will run the DSA or DIWS line handlers on top of the
transport software on its own system. In this case the emulator startup commands
would use:
(DSA)
(DIWS)
-LI DSA:gars.gar.no
-LI DIWS:192.150.211.4
Note that both the symbolic and numeric IP-address formats are supported. See
the Ggate manual for more information about Ggate.
Gallagher& Robertson
Pthru
29
Pthru
Using TNVIP
The G&R Bull emulators and gateways can connect over a TCP/IP network
using the TNVIP protocol to reach a TNVIP server in the MainWay, the GNSP
of newer GCOS8 systems, the Open Systems personality of GCOS7 Diane
systems or the Bull TNVIP server on AIX.
-li tcp -am tnvip
The TNVIP server on AIX uses a non-standard port, normally 7323, and requires
parameter -rp 7323, or the port can be specified in the default node parameter
together with the IP address of the server.
-li tcp –am tnvip -dn 192.150.211.4:7323
You can use the numeric IP-address directly or you can use a symbolic name to
identify the host. In the latter case this symbolic name must be registered in your
hosts file or with your name server. You can enter the port number directly or
use a symbolic name for it. In the latter case this symbolic name must be
registered in your services file.
The MainWay TNVIP server normally uses the default port (23), but may need
the -res parameter to deliver a mailbox name to the server. This is used to
select a specific terminal configuration.
We have implemented the TNVIP client protocol in the interest of completing
our connectivity offer. Please note however that DSA over RFC1006 is
supported by all MainWay front-ends with an ONP (Open Network Processor),
by the GNSP front-end of newer GCOS8 systems, and by the Open Systems
personality of the GCOS7 Diane systems. If used when communicating with
G&R products DSA over RFC1006 will increase throughput as compared to
using TNVIP. It will also give a real, fully functional DSA session over the
TCP/IP network, as compared to the limited terminal session offered by TNVIP.
30
Pthru
Gallagher & Robertson
Pthru
Pthru parameters
This is an overview of the parameters for normal usage.
Parameter
Description
-AI
rgb kiu
Information message attributes. Default green. Use
either a combination of rgb for a colour or one of kiu
for blink, inverse, underline.
-AW
rgb kiu
Attribute for warning messages, default red.
-CN
on/OFF
Connect automatically to host application (defined by
line handler parameters) at startup.
-DBG
on/OFF
Turns on an internal trace.
-DQ
on/OFF
Disconnect causes Pthru to quit, normal disconnect
gives a return code of zero, abnormal disconnect gives
a return code equal to the return code from the line.
Pthru also quits on failing connection attempts with a
nonzero return code.
-E8
on/OFF
Exchange eight bit bytes with the terminal and the
mainframe line handler. The default is to ignore the top
bit.
-EC
on/OFF
As for -E8.
-F12
on/OFF
Treat F12 as command prompt. F12 F12 transmits
F12. F12 followed by any F-KEY cancels the prompt.
-LK
ON/off
Lock keyboard on transmit and unlock on 'turn'.
-MSG
ON/off
Display Pthru and line handler messages.
-PT
ON/off
Map transparent print addressing in the VIP header to
in-line print start- and stop-sequences.
-PW
10
Wait time in seconds before Pthru will deliver accumulated print for spooling. A value of zero stops
automatic spooling.
Gallagher& Robertson
Pthru
31
Pthru
Host Links user profiles
Pthru uses the Host Links terminal type to differentiate between real VIP7800
terminals and G&R/GLINK. The correct terminal type is also needed for other
Host Links products and utilities. You should set the TERM environment variable
to inform Host Links of your terminal type. Any TERM variable starting with
VIP will select the handler for the VIP7801 (BDS 7) terminal, and VIPUNIX
tells the handler that the terminal is in ‘Character Attribute Mode’. A TERM
starting with GLINK will enable the G&R/Glink extensions. GLINKVIP leaves
Glink in VIP78 mode when executing other UNIX/Linux products. This is the
recommended way of running UNIX/Linux with Glink. If the TERM variable
cannot be set correctly it may be overridden with the VIDEO directive in the
PROFILES file.
Profiles file structure
/usr/gar/config/default/profiles
/usr/gar/config/$LOGNAME/profiles
/usr/gar/config/system/profiles
These files are read in the sequence given above. Suggested commands should
be given in config/default/profiles, user specific commands in
config/$LOGNAME/profiles and config/system/profiles to
override all other settings.
All files are organized in sections, which may apply either to all terminals
(Default), a group of users (User), specific terminals (Terminal), a combination
(Termuser), or specific terminal types (Termtype). Each section is prefaced with
a header line:
DEFAULT
USER
person.project.mode
TERMINAL
terminal_name
TERMUSER
terminal_name person.project.mode
TERMTYPE
terminal_type
Commands may be put into any section to specify the Host Links environment for a user or terminal.
32
Pthru
Gallagher & Robertson
Pthru
Line handler parameters
All line handler parameters are described in the G&R/Gline manual.
Line parameters for DSA
-LI DSA/DIWS
Use Bull DSA or DIWS
-LL line length
For applications that send large blocks
-HM DPS8/DPS7/CXI/DPS6
DPS8 is the default
-MN mailbox name
Local mailbox name of terminal
-TM VIP7804
Terminal type for connect letter
-DA application
Default application TSS, TDS, IOF, etc.
-DN node
Session control name of the host gateway.
-D? password
User password for host or IDCHECK.
Example: pthru -li dsa -tm vip7814 -da tss -dn ph13
Line parameters for TCP/IP
-LI TCP
Use TCP/IP
-AM Telnet/TNVIP
Telnet is default. TNVIP for TNVIP server
-HO hostname
Remote host name. Numeric/symbolic
IP-address
-RES mailboxname
Resource name for TNVIP
-RP remote_port
Non-standard remote port for connection
-TM VIP7804
Terminal type, must be a synchronous type.
Example: pthru -li tcp -tm vip7814 -am tnvip
Gallagher& Robertson
Pthru
33
Pthru
Terminal line parameters
Only a restricted set of parameters may be used on the terminal side. They are
introduced with the -TERM parameter.
34
-D_ on/OFF
Data trace in Host Links debug structure
-EB on/OFF
Add ETB to send data when enclosure =
e_message. Automatically turned on for
DKU terminal modes (Glink only)
-EX on/OFF
Add ETX to send data when enclosure >
e_message. Automatically turned on for
DKU and 3270 terminal modes (Glink
only).
-NX on/OFF
Disable IXON/IOFF. Automatically turned
on for DKU and 3270 terminal modes
(Glink only).
-S_ on/off
Session trace of internal events and low
level data.
-ST XXXXX
stty options.
Pthru
Gallagher & Robertson
Pthru
Troubleshooting
If you experience any kind of problem when using an emulator or gateway to
access your host application, the product trace file and/or the line handler trace
file will provide useful documentation of the problem, for your own use, to the
G&R distributor or to G&R if it turns out to be caused by an error in the product.
See the appendix Host Link Trace for a full discussion of how to generate
G&R/Host Links trace files.
Product trace files
/usr/gar/debug/XXX/YYY.dbg
XXX = user name
YYY = product identifier g32, g52, qsi, v78, pth
This traces details from internal processing. Enable it by adding -DBG to the
start-up command or the <product>.cfg configuration file:
-USER
-DBG ON
Line handler trace files
/usr/gar/debug/XXX/YYY-gli.dbg
XXX = user name
YYY = product identifier g32, g52, qsi, v78, pth
This traces details of line handler operation. Enable it by adding one or both of –
D_ and –S_ to the start-up command or the <product>.cfg configuration
file:
-LI ZZZ
-S_ -D_
(ZZZ =line handler identification, i.e. DSA, DIWS, TCP or X25)
Gallagher& Robertson
Pthru
35
Pthru
When connecting through Ggate
/usr/gar/debug/ZZZZ/ggaNN-PPPP.dbg
(ZZZZ = DSA node name, e.g. EN06 or PH13)
(NN =Instance number, starting at 01)
(PPPP =IP-address of the client system, running the emulator)
When any G&R or customer application based on GlAPI connects through Ggate
to the host application, the line handler trace will be generated on the Ggate
system, with the name and location showed in the table above. In this case the
product start-up command or <product>.cfg file would look like this:
-LI YYY:PPPP
-S_ -D_
(YYY =line handler identification, i.e. DSA or DIWS)
(PPPP =IP-address of the system running Ggate)
The TTY line handler
You can obtain a line trace of the terminal side of Pthru by using -TERM to
introduce parameters for the terminal side:
-TERM
-S_ -D_
36
Pthru
Gallagher & Robertson
Pthru
Appendix: Host Links
Manuals
Below you find a complete list of all available Host Links manuals:
Installation
Host Links Servers
Installation and Configuration on UNIX/Linux
Host Links Emulators
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
Gsftp
Gateway between FTP and SFTP
Emulations
Gspool
Network Printer Emulation
GUFT
Unified File Transfer
G3270
Emulating IBM 3270 Terminals
G5250
Emulating IBM 5250 Terminals
Pthru
Gateway to the Bull Primary Network
Qsim
Emulating Questar DKU7107-7211 & VIP7700-7760
V78sim
Emulating VIP7801 & VIP7814
Gweb
Web Browser Front-end for DKU, VIP7700-7760,
VIP7800, IBM3270 and IBM5250 Emulations
Gallagher& Robertson
Pthru
37
Pthru
38
Pthru
Gallagher & Robertson
Pthru
Appendix: Host Links DSA
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.
Gconame
Lists the parameters generated from a given CONAME. The utility works for
both CONAME and RESOURCE e.g.:
gconame tnviptm
Checking 'dsa.cfg' for coname 'tnviptm'
Coname: tnviptm, type TM, parameters:
-DA misfld
-S_
-D_
-CODE 0000
-CODE 1000
-CODE 1800
-TEXT Remote SCID?:
-CODE 4700
-TEXT Remote application?:
-CODE 1400
-CODE 1600
-TEXT Password?:
Gallagher& Robertson
Pthru
39
Pthru
Gerror
Shows the text message associated with a DSA reason code. Only the most
common codes are supported i.e. the ones related to network, transport and session communication layers. Errors generated by the OSI-stack on the Host Links
platform are not covered by this utility; please refer to the documentation from
the vendor of the stack e.g.:
gerror 0109
Reporting component: Session control (01) 0109, Dialog
protocol error or negotiation failed (wrong logical record).
For a detailed description of all reason codes, please consult the Bull manual
OSI/DSA Network System Messages and Return codes (39A2 26DM).
Glnode
List and verify the communications parameters of the local node e.g.:
glnode
Local node name : GRDL
Local session control id : GRDL
DSA200 address (area:tsm): 54:60 (36:3C)
Gmacfix
When you connect to FCP cards on Bull mainframes via an Ethernet port on the
LAN-Extender the mainframe address is given in Ethernet (LLC) format. If you
connect to an FDDI adapter you must convert the MAC address to SMT. e.g.:
gmacfix 080038000fab
MAC address 080038000fab = 10001c00f0d5
Gping
Connects to a remote system using the Gline parameters set on the command line.
If successful it returns ‘connected to application’, otherwise it shows the error
code returned e.g.:
gping -li dsa -dn b7dl -da iof -du jim -pw mydogsname
Gping - $$DSA: Connected to application
40
Pthru
Gallagher & Robertson
Pthru
Grnode
Return the parameters (in dsa.cfg) and the state of a remote node e.g.:
grnode b6dl
Checking ‘dsa.cfg’ for node ‘b6dl’
Session control id : B6DL
DSA200 address (area:tsm) : 1:5 (1:5)
Inactivity interval : 0
Route 0
Load balance percentage : 0
TP class : 2
TP expedited : 0
TPDU size : 0
Network address : 130405
Gtrace
Same as gping but writes the DSA communication trace on the user’s terminal
(applicable to UNIX versions) e.g.:
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.
Gtsupd
Update the state of a transport route. Transport routes can be set automatically in
a disabled state if a backup route is configured. When such a state change occurs
the route will be set back to the enabled state after a configurable timer has
expired. The default is 15 minutes. You can reset the state of such a route with
gtsupd ts-name enbl/used/down/locked e.g.:
gtsupd gars_rfc enbl
TS-entry ‘gars_rfc’, new state = enbl
Gallagher& Robertson
Pthru
41
Pthru
42
Pthru
Gallagher & Robertson
Pthru
Appendix: 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.
Windows
server
gspool -id gs1 –dbg –ps \\SERVER\LEXMARK
-li dsa -da tptst -d_ on
UNIX
Linux
gspool -id gs1 -dbg-pc lp -li dsa
-da tptst -d_ on
Most G&R products include a facility for setting product or line parameters
dynamically. It is therefore generally possible to turn on debug or trace without
modifying the command line or configuration of a production system.
Trace types
All Host Links products accept a parameter –dbg, which starts an application
level trace of internal events. This is useful when investigating malfunctions or
looking closely at product behaviour.
All Gline line handlers accept a parameter -d_ to turn on a data trace. It records
data and enclosure level being exchanged with the line handler. It is useful when
documenting product malfunction e.g. an emulation error, because it records
exactly what the host sends and what the G&R application replies. It can be used
to simulate a customer situation, reproduce a problem and to verify that a
correction fixes the documented problem.
Gallagher& Robertson
Pthru
43
Pthru
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.
Structure
The Host Links file structure includes a debug directory to collect the trace and
debug files in one location where the permissions can be adjusted as required for
security. By default only the Host Links administrator can access the directory.
The debug directory is created by the initialization procedure and located (by
default) in:
Windows
server
\gar\debug
UNIX
Linux
/usr/gar/debug
If the application is a client type of application, a debug sub-directory with the
same name as the user (UNIX username or PC login name) is created and all
debug files are located there. This includes the line level trace except in the
special case where the client application connects via Ggate and the line level
trace is written on the Ggate system using the Ggate DSA node name as a debug
sub-directory.
If the application is a server type of application, then a sub-directory will be
created using the DSA node name on behalf of which the server application is
executing. If the server does not use DSA the default local session control name
is still used if there is a dsa.cfg file. If there is no dsa.cfg file then the
system’s UNIX or Windows communications node name is used. You can find
this name using the command uname –n on UNIX systems, or the Network
section of the control panel on Windows systems. This covers situations where
several instances of a server are executing on the same system and accepting
incoming calls to different DSA node names, or where several Host Links
systems using the same server product share a file system.
44
Pthru
Gallagher & Robertson
Pthru
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 .dbg for a terminal session or –dbp for a printer session.
The following is a trace file name for Ggate session sequence number 5
executing on Host Links system GRDL initiated from a Glink client on IPaddress jim.gar.no:
gga05-jim.gar.no.dbg
This file, and possibly also a Glink debug file and a Glink communication trace
file activated by the /J command line parameter will be needed by the support
engineer investigating any problem.
To enable a line handler trace through Ggate the product’s start-up command or
configuration file would look like this:
-LI YYY:ZZZZ -S_ -D_
(YYY =line handler identification, i.e. DSA or DIWS)
(ZZZZ =IP-address of the system running Ggate)
Examples - G&R products
Examples of directory and file names in the debug structure are:
/usr/gar/debug/jim
Debug directory for user ‘jim’
qsm.dbg
Qsim emulator debug file
Gallagher& Robertson
Pthru
-dbg
45
Pthru
46
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.dbg
GUFT client host line trace
-li dsa -s_
/usr/gar/debug/en01
Debug directory for node ‘en01’
guf.def
GUFT server debug file
-dbg
guf-gli.def
GUFT server host line trace
-li dsa -s_
gli-gli.dsa
DSA listener host line trace
-s_
gli-gli.diw
DIWS listener host line trace
-s_
gsp.def
Gspool (default -id) debug
file
-dbg
gsp-gli.def
Gspool (default -id) host
trace
-li dsa -s_
gga01-mike.gar.no.dbg
Ggate line trace, first Glink
-s_
gga02-mike.gar.no.dbg
Ggate line trace second
Glink
-s_
/usr/gar/debug/en02
Debug directory for node ‘en02’
gsp.abc
Gspool (-id abc) debug
file
-dbg
gsp-gli.abc
Gspool (-id abc) host
trace
-li dsa -s_
gspc-gli.def
Gspool DPF8 command
trace
-li tcp -s_
gspd-gli.def
Gspool DPS8 data trace
-li tcp -s_
Pthru
Gallagher & Robertson
Pthru
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. CPI-C applications use the ‘client’ style of debug and create a
debug directory with the UNIX username or PC login name used by the process
that started them.
The application level debug (-dbg) and line trace (-s_ and -d_) are set in the
cpic.cfg file. The line trace goes to the debug directory, with the name built
up as follows:
<product_id><session_id>-<process_id>.<debug_type>
product_id
Value
Comment
cpi
CPI-C API
cp3
CPI-C 3270
cp7
CPI-C 7800
cpd
CPI-C DKU
gw3
Gweb3270
gw7
Gweb7800
gwd
Gwebdku
session_id
(nn)
If multi-session application, 1-63
process_id
n (n n n...)
Varies by platform
debug_type
dgb
Application level debug
gli
Line trace
Gallagher& Robertson
Pthru
47
Pthru
Example:
\gar\debug\system
48
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.gli
Gweb7800 host line trace
-li dsa -s_
Pthru
Gallagher & Robertson
Pthru
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.
code Description
00xx General Errors
0001
0002
0003
0004
0005
0006
0007
0008
0009
000A
000B
000C
000D
000E
000F
0010
0011
0012
0013
Open Failure in LC - Reject for unknown reason
Open Failure in LC - Acceptor customer node inoperable
Open Failure in LC - Acceptor customer node saturated.
Open Failure in LC - Acceptor mailbox unknown.
Open Failure in LC - Acceptor mailbox inoperable.
Open Failure in LC - Acceptor mailbox saturated.
Open Failure in LC - Acceptor application program saturated
Connection refused. Transport protocol error or negotiation failed.
Open Failure in LC - Dialog protocol error or negotiation failed
Open Failure in LC - Presentation protocol error or negotiation failed
Open Failure in LC / Connection refused lack of system resources
Open Failure in LC / Connection refused from GCOS7 duplicate
user
Open Failure in LC, Duplicate implicit LID / Q class not started
Open Failure in LC, Duplicate GRTS Id / lack of memory resources
Open Failure in LC, No Logical line declared for DACQ / 7
connection refused
Open Failure in LC, GCOS 8 GW Missing translation / Incorrect
device length in ILCRL.
Open Failure in LC, DAC connection not initialized / Too many jobs
executing
Open Failure in LC, No binary transfer / impossible to start the IOF
job
Open Failure in LC, connection is not negotiated in FD mode /
impossible to start the IOF job
Gallagher& Robertson
Pthru
49
Pthru
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
0056
0057
50
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.
Connection refused - Unknown pre-negotiated message path
Connection refused - Security validation failed.
Connection refused - Unknown acceptor mailbox extension.
Connection refused - Inoperable acceptor mailbox extension.
Connection refused - Invalid Message group number.
Disconnection - no more memory space.
Connection refused - Unknown node.
Connection refused - inaccessible node or Host down.
Connection refused - saturated site.
Connection refused - inoperable mailbox.
(X.25) Packet too long. Problem with packet size. / Connection
block already used.
Syntax Error - option not known (received on close VC).
(X.25) No response to call request packet - timer expired.
(X.25) Timer expired for reset or clear indication.
Disconnection - transport protocol error (MUX).
Presentation Control Protocol Error
The application has not the turn
Message group closed
(X.25) Facility code not allowed. / Connection refused - unknown
node
Connection refused - path not available.
Connection refused - Duplicate USER ID / Facility parameter not
allowed
(X.25) Invalid calling address.
(X.25) Invalid facility length.
(X.25) No logical channel available.
DNSC: (X.25) Invalid call packet length.
Normal disconnection (GCOS3/8)
Error or Event on LC initiated by GW
Error or Event on LC initiated by GW.
Error or Event on LC initiated by GW. TCall
Error or Event on LC initiated by GW. DIA in LOCK State
Error or Event on LC initiated by GW. DIA error
Error or Event on LC initiated by GW. GW has no known
explanation.
Error or Event on LC initiated by GW. Reject mailbox permanent
Pthru
Gallagher & Robertson
Pthru
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
0087
0090
0092
0093
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. Wrong letter or wrong record
Error or Event on LC initiated by GW. Forbidden letter received
Error or Event on LC initiated by GW. Forbidden letter received
Error or Event on LC initiated by GW. No buffer for secondary letter
Error or Event on LC initiated by GW. No buffer for fragmented
letter
Error or Event on LC initiated by GW. Disconnect on end of phase
record
Error or event on LC initiated by GW. No buffer for control letter.
Error or event on LC initiated by GW. Mailbox in closing phase
Error or event on LC initiated by GW. Flow control error.
Error or event on LC initiated by GW. CH locked by operator.
Error or event on LC initiated by GW. Disconnect with a normal
TMG F2 exchange.
Error or event on LC initiated by GW. Teletel rerouting error from
DACQ
Error or event on LC initiated by GW. Teletel routing error from
DACQ
Error or event on LC initiated by GW. Teletel rerouting error from
TM
Error or event on LC initiated by GW. Teletel rerouting error from
TM
Syntax error - text too long.
Syntax error - illegal object in a GA command.
Syntax error - unknown node Id.
Syntax error - illegal command for this object.
Syntax error - illegal date.
(X.25) No route available for X.25 switching.
No more network routes available for switching.
(X.25) Hop count reached for X.25 switching.
(X.25) Flow control negotiation error.
(X.25) Frame level disconnection.
(X.25) Frame level connection.
(X.25) Frame level reset.
Frame level not set.
(X.25) X.25 Echo service in use.
(X.25) Incorrect password for PAD connection.
Gallagher& Robertson
Pthru
51
Pthru
0094
0096
009C
009D
009E
009F
00B2
00B6
00C0
00D7
00DE
00E1
00E6
(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.
Use of invalid password through PAD
Unknown mailbox selection for PAD connection using the PAD
password.
(X.25) Normal disconnection.
(X.25) TS image (of type DSA or DIWS) in LOCK state.
(X.25) NS RMT or NR SW in LOCK state.
Connection refused. Mailbox is not in ENBL state.
QOS not available permanently.
01xx Session Control
0100
0101
0102
0103
0104
0105
0106
0107
0108
0109
010A
010B
010C
010D
010E
010F
0110
0111
0112
0113
0115
0117
0118
0119
011A
011E
52
Logical connection accepted or normal termination
Rejection for unknown reason or abnormal termination
Acceptor node inoperable.
Acceptor node saturated. When a node has no available resources
Acceptor mailbox unknown.
Acceptor mailbox inoperable.
DNS: Acceptor mailbox saturated.
DNS: Acceptor application program saturated.
Transport protocol error or negotiation failed (DSA 200 only).
Dialog protocol error or negotiation failed. (Wrong logical record).
Time-out on session initiation / unknown LID
Acceptor mailbox extension unknown.
Acceptor mailbox extension inoperable.
Invalid Session Number.
Unknown node.
System error. System generation error or insufficient memory space
Application abnormal termination. Subsequent to an abnormal
occurrence in the dialogue
Normal terminate rejected.
Protocol not supported.
Session control service purged by user.
Disconnection Time-out on message group initiation.
Incorrect Access Right for MB
Incorrect Access Right for the Application
Pre-negotiated Message Path Descriptor unknown
Security validation failed
Incorrect object status
Pthru
Gallagher & Robertson
Pthru
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
015B
015C
015D
0160
0161
Not enough memory space available.
Node unknown.
The channel object (CH) is in LOCK state
Saturation - no plug available
Object status = LOCK
Connection block (TSCNX) already used
Disconnection already running
The connection block (TSCNX) is disconnected (or not connected)
Change Credit value < 0
Ineffective Change Credit ( delta = 0 )
No more deferred letters
"Reinitialization" Request
"Reinitialization" in progress
"Reinitialization" in progress, letters are dropped
Close virtual circuit. Either no mapping exists between PA/NR or
CL and VC/NS
Null connection object index.
Undefined function at Sysgen time.
Letter too large with respect to the negotiated size.
The received letter is longer than the size which was
Disconnection of the session control user
Interface error on EOR (End-Of-Record) processing.
Presentation control protocol error.
You do not have the turn.
Message group closed.
Session is closed.
Request refused, no system buffers available.
Incorrect addressing record.
No presentation record in the ILCAL or ILCRL
Negotiation failed on session mode
Negotiation failed on resynchronization.
Negotiation failed on END to END ACK
No presentation record in the connection letter
Negotiation failed on session mode
Negotiation failed on letter size (in the Logical Connection record).
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.
Gallagher& Robertson
Pthru
53
Pthru
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
0191
0192
0193
0194
0195
0196
0197
0198
54
Negotiation failure.
Record header length error.
Protocol error.
Protocol error reception of control letter.
Type or length error on interrupt letter.
Protocol error on reception of data letter.
Dialog protocol error.
Unknown event.
Protocol error on data transfer.
Invalid status for a disconnection request.
Invalid status for a recover
Invalid status for a suspend/resume request.
Negotiation failure.
Unknown command.
Error in presentation protocol
Letter header length error in
ILCAL is not DSA 200 protocol.
Error in session record.
Normal disconnection, without complementary reason code.
Letter is not in ASCII or EBCD.
Connection protocol letter header
Letter header protocol error.
Record header protocol error.
Record header length error.
Mbx record header length error.
Error on buffer transfer.
DSA 200 record header protocol
DSA 300 record header protocol
Unsupported connection options.
Character error in ASCII string.
No segmented record size.
Invalid mailbox object index.
Mapping error for a remote connection.
No more buffers.
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.
Pthru
Gallagher & Robertson
Pthru
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
01EA
01EB
01EC
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.
Invalid transfer state.
Suspend protocol running.
Suspend protocol running.
Recover protocol running.
Forbidden function in write request. ($WRITE)
Conflicting parameters for segmented record. (SWBREC)
Protocol conflict - suspend/recover.
Protocol not supported - letter/end-to-end ACK. (SWBLET)
Multi-record letter in progress.
Interrupt request forbidden.
Send control record request forbidden. (SCTROL)
Forbidden for TWA session - turn is here. (SREAD)
Termination forbidden - suspend or recover in progress. (STERM)
No space available for downstream connection request. (SMECNX)
No space available for upstream connection request. (SMUCNX)
No space available for upstream SCF connection. (SMRCNX)
No space available for session context. ($SCTX)
Enclosure or data length error for a write request. ($WRITE)
Enclosure or data length error for a write segment record request.
(SWBREC)
Enclosure error for 'give turn' request. (SGVTRN)
Interrupt request is not demand turn, attention/data attention, or
purge record.
Input status for a send control letter is not permitted.
Write request without turn.
Write segmented record request without turn.
Write segmented letter request without turn.
Send control letter request without turn.
Disconnection request without turn.
02xx Presentation Control
0201
0202
0203
0204
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.
Gallagher& Robertson
Pthru
55
Pthru
0205
0206
0207
0230
0231
0232
0233
0234
0235
0236
0237
Character subset error. TM cannot support the proposed character
subset.
Incorrect record encoding.
Incorrect parameter encoding.
Data presentation control error. The presentation control proposed
for this session cannot be used
Device type is incompatible with the configuration.
TM control protocol is incorrect.
Device-sharing attributes are invalid.
Initiator or acceptor configuration is not correct.
Logical device index error.
Number of logical devices is incompatible with the configuration.
TM protocol record not supported.
03xx Terminal Management
0300
0301
0302
0303
0304
0305
0306
0307
030A
0310
031E
0320
0321
0322
0323
0324
0325
0326
0327
0328
0329
032A
032B
032C
56
Sysgen error WARNING. There is no mapped object; some objects
will be spare.
Operator requested session abort or logged.
Idle time run out after secondary network failure.
Idle time run out for no traffic.
Form not found.
Operator requested suspension.
Destructive attention send on the session.
Unknown TX addressed in this session. TM is unable to a the
session.
Protocol error. A record was received which did not comply with
current standards
Insufficient resources. The receiver cannot act on the request
because of a temporary
Incorrect value for Retry or Wait parameters on UP LL command.
Function not supported.
Parameter error. This can result
Resource not available. The
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.
Resource not configured.
Symbol set not loaded.
Pthru
Gallagher & Robertson
Pthru
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
0383
0384
038C
0390
0391
0392
03C0
Read partition state error.
Page overflow.
Subsidiary device temporarily not available.
Intervention required at subsidiary device.
Request not executable because of subsidiary device.
TM cannot accept a new connection.
Object status incorrect.
The TM configuration is not correct.
Unknown TX addressed on this session.
Data presentation protocol error.
Device type is incompatible with the configuration, or is not
supported.
TM control protocol incorrect.
Device shareability attributes are invalid.
Initiator or acceptor configuration is not correct.
Logical device index error.
Number of logical devices incompatible with the configuration.
Disconnection of TM after reinitialization of the network.
File not found. (Welcome and Broadcast Messages)
Site not found. (Welcome and Broadcast Messages)
NASF error. (Welcome and Broadcast Messages)
No-session timeout. Device disconnected.
No-input timeout. Device disconnected.
No-output timeout. Device disconnected.
Timeout due to no backup session being initiated.
Timeout due to no backup session being established.
Connection refused because of late activation of back up session.
Disconnection of current session to switch to backup session.
AUTOCN parameter not declared.
Mixed ETB in data sent by VIP screen and cassette
Data header sent by the terminal incorrect.
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
PAD connection refused.
Flow control error.
Gallagher& Robertson
Pthru
57
Pthru
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
1741
1742
1744
1745
1747
1749
174F
1755
58
Logical channel number not zero in restart packet.
Illegal packet length or use of D-bit forbidden.
Illegal header.
Illegal Logical Channel Number.
Invalid packet type for the automaton state. Protocol error
Incorrect packet type.
Inconsistent network parameters in the generation file.
No more space.
DSAC network layer object not usable.
USED/ENBL transition. Transport station is locked.
USED/ENBL transition. This is a back-up NR.
USED/ENBL transition. Dynamic close due to load.
USED/ENBL transition. Transfer time-out has elapsed.
USED/ENBL transition. This is a back-up NR.
USED/ENBL transition. Transport station is idle.
USED/ENBL transition. NR object is locked.
ENBL/LOCK transition. NR HDLC has no more memory space.
Remote station is inaccessible via the configured network. Check
Incorrect PAD password.
Virtual circuit already in use. LCN (Logical Channel Number) too
high.
Invalid virtual circuit.
Packet too short. Protocol error for the equipment directly connected
to the Bull Datanet.
Incompatibility between the generation parameters of two
communicating systems on window or packet size.
Packet size in communicating systems not the same.
Timer runs out while waiting for call confirmation.
Timer runs out while waiting for clear confirmation.
Timer has run out while waiting a reset confirm.
Call setup or call clearing problem.
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.
End of time-out on call confirm.
Incorrect packet length. Protocol error for the equipment directly
connected to the Bull Datanet.
Flow control, window, packet size or reset error.
Pthru
Gallagher & Robertson
Pthru
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
17CC
17CE
17CF
17D0
17D4
17D7
17DD
17DE
17DF
17E0
17E1
17E2
Frame disconnection.
Frame connection.
Frame reset.
No more network routes available for X.25 switching.
Maximum of 15 switches have been used,
Flow control negotiation error.
Frame level disconnection.
Frame level connection.
Frame level reset.
Frame level not established.
No more logical paths available for the PAD.
Echo service busy.
Incorrect PAD password.
All the PAD virtual circuits are used
X.25 initialization not possible.
LCN not null in restart packet
Incompatible header (receive error: all VC of concerned NS
LCN greater than NBVC in NS directive
Incorrect packet type
Invalid facility.
Normal disconnection.
X.25 Echo in use.
No more logical channels available.
No more PAD connections allowed.
TS SX25 or NU X25 object locked.
Buffer capacity overflow.
Normal disconnection.
Unknown calling SNPA (Sub-Network Point of Attachment).
Internet problem.
Call collision on VC
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.
Gallagher& Robertson
Pthru
59
Pthru
17E3
17E4
17E5
17E6
17E7
17E9
17EB
17EE
17FF
No object mapped above.
NR not locked (MP NR -ADD/-SUB) or virtual circuit already open.
NR is last in list and the TS is not locked.
No object mapped above (UP NR -PRIO). NR not mapped on TS.
Upward mapped object not locked
Mix of datagram and connection network
Class inconsistent with NR.
Incompatible generations. NR object without mapping.
Wrong parameter in administrative CALL
18xx Transport Layer
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
180A
180B
180C
1817
181F
1821
1824
182E
182F
1831
1832
1833
1834
1835
183A
183C
1840
60
Normal disconnection initiated by the correspondent
Local saturation at connection request time.
Failed negotiation at connection time.
Duplicate connection. Two or more requests have been issued for the
same connection.
Redundant request.
Retransmission Time-out at transport level.
Survey time-out at transport level.
Transport protocol error.
Session Control specified is not available (inaccessible).
Requested Session Control Id unknown by remote transport.
Termination because of disconnection by administration.
Session Control/Transport interface error.
Connection request on non-sharable VC in case of ISO Transport.
ISO: header or parameter length is invalid.
Station in shut-down state.
No memory space at connection time.
Session Control inaccessible by configured session routes. ISO:
Session entity not attached to TSAP.
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.
ISO: Remote transport entity congestion at connect request time.
Server in terminating state. TC has been re-assigned on another NC.
Pthru
Gallagher & Robertson
Pthru
18A1
18B0
18EF
An additional NC has been assigned to a TC.
NC has been re-assigned on another VC.
Disconnection at Transport level caused by reception of RESTART
DSA during the transfer phase.
Windows Sockets error Codes
Below is a list of Windows Sockets return codes and the corresponding
description.
Hex
code
2714
Windows Sockets Access
Error name
WSAEINTR
2719
271E
WSAEBADF
WSAEFAULT
2726
WSAEINVAL
2728
WSAEMFILE
2733
WSAEWOULDBLOCK
2734
WSAEINPROGRESS
2735
WSAEALREADY
2736
2737
2738
WSAENOTSOCK
WSAEDESTADDRREQ
WSAEMSGSIZE
2739
WSAEPROTOTYPE
273A
WSAENOPROTOOPT
273B
WSAEPROTONOSUPPORT
Gallagher& Robertson
Description
Pthru
The (blocking) call was cancelled
via WSACancelBlockingCall()
The socket descriptor is not valid.
An invalid argument was supplied
to the Windows Sockets API.
An invalid call was made to the
Windows Sockets API.
No more file descriptors are
available.
The socket is marked as nonblocking and no connections are
present to be accepted.
A blocking Windows Sockets call
is in progress.
The asynchronous routine being
cancelled has already completed.
The descriptor is not a socket.
A destination address is required.
The datagram was too large to fit
into the specified buffer and was
truncated.
The specified protocol is the wrong
type for this socket.
The option is unknown or
unsupported.
The specified protocol is not
supported.
61
Pthru
62
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
2749
274A
274B
274C
WSAEISCONN
WSAENOTCONN
WSAESHUTDOWN
WSAETOOMANYREFS
WSAETIMEDOUT
274D
WSAECONNREFUSED
274E
WSAELOOP
274F
2750
2751
WSAENAMETOOLONG
WSAEHOSTDOWN
WSAEHOSTUNREACH
The specified socket type is not
supported in this address family.
The referenced socket is not a type
that supports connection-oriented
service.
The specified address family is not
supported by this protocol.
The specified address is already in
use.
The specified address is not
available from the local machine.
The Windows Sockets
implementation has detected that
the network subsystem has failed.
The network address can't be
reached from this host. There is
probably a problem in the way you
have set up TCP/IP routing for your
PC (most likely you have not
defined a default router).
The connection must be reset
because the Windows Sockets
implementation dropped it.
The connection has been closed.
Not enough buffers available, or
too many connections.
The socket is already connected.
The socket is not connected.
The socket has been shutdown.
Attempt to connect timed out
without establishing a connection.
The attempt to connect was
forcefully rejected. The service on
the other side is not available.
Too many symbolic links were
encountered in translating the path
name.
The host machine is out of service.
The host machine is unreachable.
Pthru
Gallagher & Robertson
Pthru
2752
2753
2754
2755
2756
2757
276B
WSAENOTEMPTY
WSAEPROCLIM
WSAEUSERS
WSAEDQUOT
WSAESTALE
WSAEREMOTE
WSASYSNOTREADY
276C
WSAVERNOTSUPPORTED
276D
WSANOTINITIALISED
2AF9
WSAHOST_NOT_FOUND
2AFA
WSATRY_AGAIN
2AFB
WSANO_RECOVERY
2AFC
WSANO_DATA
Gallagher& Robertson
Pthru
Indicates that the underlying
network subsystem is not ready for
network communication.
The version of Windows Sockets
API support requested is not
provided by this particular
Windows Sockets implementation.
A successful WSAStartup() must
occur before using this API.
Authoritative answer host not
found.
Non-authoritative answer host not
found, or SERVERFAIL.
Non-recoverable errors,
FORMERR, REFUSED, NOTIMP.
Valid name, no data record of
requested type.
63