Host Links Installation And Configuration - Gar.no

Transcript

| G&R HOST LINKS TM Installation and Configuration on UNIX/Linux http://www.gar.no/hostlinks/ 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.2 © Gallagher & Robertson as 1990-2005 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] G&R Contents Host Links............................................................................................ 1 Scope of the products.......................................................................... 3 Functional summary........................................................................... 5 Product architecture........................................................................... 7 Architecture diagram .................................................................................................. 8 Delivery................................................................................................ 9 General requirements....................................................................... 13 Memory usage .......................................................................................................... 13 UNIX/Linux shared memory.................................................................................... 13 PTYs......................................................................................................................... 13 Installation step by step.................................................................... 15 Preparation................................................................................................................ 16 Create user gar............................................................................................... 16 Create /usr/gar ............................................................................................... 16 Copy the software to your system ................................................................. 16 Log out, then in again as gar ......................................................................... 16 Disable old Host Links releases .................................................................... 17 Installation ................................................................................................................ 17 Run the installation script.............................................................................. 17 Review the release information..................................................................... 18 Set the path ............................................................................................................... 18 Allow rlogin mode for Host Links ........................................................................... 19 Install the network software ..................................................................................... 19 Build network configuration (dsa.cfg)...................................................................... 19 Test ........................................................................................................................... 20 Set TERM variable ................................................................................................... 20 Set Host Links profiles ............................................................................................. 21 Configure the context manager................................................................................. 21 Configure the Host Links servers ............................................................................. 22 Start at system startup ................................................................................... 22 Host Links Installation and Configuration i G&R Starting applications on demand ................................................................... 23 Build Host Links menus ........................................................................................... 24 Environment...................................................................................... 27 PATH ............................................................................................................ 27 GAR_SYSDIR .............................................................................................. 27 GAR_MODE ................................................................................................ 27 Product startup ................................................................................. 29 Configuration files.................................................................................................... 29 Command syntax...................................................................................................... 30 Product usage .................................................................................... 31 Host Links Server Administration .................................................. 33 Gmanager ................................................................................................................. 33 Additional tools ........................................................................................................ 36 Gdir ............................................................................................................... 36 Gver............................................................................................................... 36 Gdump........................................................................................................... 37 Host print in DSA networks............................................................. 38 Print to screen session .............................................................................................. 38 Pthru .............................................................................................................. 38 Qsim .............................................................................................................. 38 V78sim .......................................................................................................... 39 Print on separate session........................................................................................... 39 Gspool ...................................................................................................................... 39 Context Manager .............................................................................. 41 Multiple sessions ...................................................................................................... 41 General description................................................................................................... 41 How to start Context................................................................................................. 42 Moving between active contexts .............................................................................. 42 Context configuration files ....................................................................................... 43 Example of context.cfg............................................................................................. 45 Profiles configuration ....................................................................... 47 General ..................................................................................................................... 47 File location.............................................................................................................. 47 The DEFAULT profiles ................................................................................ 48 ii Host Links Installation and Configuration G&R The USER profiles ........................................................................................ 48 The SYSTEM profiles................................................................................... 48 File organization....................................................................................................... 49 Directive format ....................................................................................................... 50 Screen update classes ............................................................................................... 51 List of available directives........................................................................................ 52 Description of the available directives ..................................................................... 53 BWMODE – force colour off........................................................................ 53 COLOUR – change default colour settings................................................... 53 COLOURMODE – force colour on .............................................................. 54 CONFIGDIR directory – directory for user configurations .......................... 55 CURSORSIM - software simulate cursor ..................................................... 55 DIREDIT directive – configure editor for Gdir ............................................ 55 DIRUSE pathname – user command file for Gdir ........................................ 56 DOLLAR – permission to enter directory manager ...................................... 56 EDIT - permission to run editor on screen image ......................................... 56 EIGHTBIT - screen supports 8-bit characters............................................... 57 EXEC – permission to execute commands ................................................... 57 EXTENDED - 8-bit characters over 7-bit path ............................................. 57 HELPDIR directory – help base directory .................................................... 57 HOMEDIR directory – users home directory ............................................... 58 KPAM - keypad application mode................................................................ 58 KPNUM - keypad numeric mode.................................................................. 58 LANGKEY xx - configure 7-bit screen language ......................................... 59 LANGUAGE ccc – configure dialogue language ......................................... 59 LISTER directive – configure file list program ............................................ 60 MACRO - permission to define keyboard macros ........................................ 60 MENU – display program menus.................................................................. 60 MISCDIR directory – miscellaneous file directory....................................... 61 SERVERDIR directory – directory for servers ............................................. 61 SETUP - permission to run setup commands................................................ 61 SEVENBIT - screen does not support 8-bit characters ................................. 61 SHELL – permit escape to shell.................................................................... 61 SOUND – control alarm................................................................................ 62 VIDEO handler - select video handler .......................................................... 62 VIPGLINK - VIP78 handler in Glink mode ................................................. 63 VIPUNIX - VIP78 handler can assume UNIX mode.................................... 63 Video handlers .................................................................................. 65 General information.................................................................................................. 65 The VIP78 video handler.......................................................................................... 66 VIP78 handler using terminals ...................................................................... 66 VIP78 handler using Glink............................................................................ 66 Host Links Installation and Configuration iii G&R The TWS video handler............................................................................................ 67 The VT100 video handler......................................................................................... 67 The VT200 video handler......................................................................................... 68 The term video handler............................................................................................. 71 Terminfo files delivered ........................................................................................... 73 Extra setup for the X11 xterm program......................................................... 74 Extra setup for the CDE dtterm program ...................................................... 75 Extra setup for the FTP Software TN.EXE program..................................... 75 Interactive commands ...................................................................... 77 Character sets.................................................................................... 79 Limitations of the 7-bit set ....................................................................................... 79 National substitutions ............................................................................................... 79 The 8-bit standard..................................................................................................... 81 Host Links character set .................................................................. 83 Using the 8-bit set.............................................................................. 85 8-bit terminals (EIGHTBIT)..................................................................................... 85 7-bit terminals with mapping (EXTENDED)........................................................... 85 Glink ............................................................................................................. 85 The DKU7102 (TWS21xx)........................................................................... 86 7-bit terminals (LANGKEY).................................................................................... 86 Display of 8-bit characters ............................................................................ 86 Entering 8-bit characters ............................................................................... 87 8-bit terminals viewing 7-bit characters ................................................................... 87 Default national view .................................................................................... 87 Toggle to national view (CTRL/F)................................................................ 88 Data entry while viewing 7-bit...................................................................... 88 Glicense & license keys..................................................................... 89 Glicense.................................................................................................................... 89 License keys ............................................................................................................. 91 Sample dsa.cfg................................................................................... 93 Platform specific requirements ....................................................... 97 386l2 (Linux)............................................................................................................ 97 OSI software and hardware for Linux........................................................... 97 386so (Solaris).......................................................................................................... 97 iv Host Links Installation and Configuration G&R OSI software and hardware for Solaris ......................................................... 97 hpp11 (HP-UX Rel. 11)............................................................................................ 98 ppca5 (AIX 5.x)........................................................................................................ 98 rs6a4 (AIX rel. 4.x DPX20, RS6000)....................................................................... 98 spaso (Solaris 2.6 SPARC)....................................................................................... 99 Installing and configuring OSI stacks........................................... 101 Bull DPX/20 - IBM RS6000, AIX 4.1.x ................................................................ 101 Install Bull software .................................................................................... 101 X.25 setup ................................................................................................... 102 OSI transport and session setup................................................................... 103 Create a configuration ........................................................................... 104 Modify a configuration.......................................................................... 104 Loading (and generation) of the new OSI configuration ....................... 105 Troubleshooting .......................................................................................... 106 Sun Solaris 2.x OSI stack ....................................................................................... 107 X.25 setup ................................................................................................... 107 OSI over X.25 setup.................................................................................... 108 OSI over LAN setup.................................................................................... 109 dsa.cfg configuration................................................................................... 110 dsa.cfg changes for DSA over X.25 ............................................................ 110 dsa.cfg changes for DSA over LAN............................................................ 111 Troubleshooting .......................................................................................... 111 HP HP-UX OSI stack ............................................................................................. 112 Install HP software...................................................................................... 112 X.25 setup ................................................................................................... 112 Configure X.25 address ......................................................................... 113 Configure Virtual Circuits ..................................................................... 113 Configure Internet address..................................................................... 113 Verify Level 3 values ............................................................................ 113 Verify Level 2 values ............................................................................ 113 OSI transport and session setup................................................................... 114 Add CLNS over 802.3 ........................................................................... 115 Add CONS over X.25............................................................................ 116 Add destination systems. ....................................................................... 117 Edit ots_parms and ots_subnets files ..................................................... 118 ots_subnets .................................................................................................. 119 ots_dests ...................................................................................................... 120 ots_parms .................................................................................................... 121 Troubleshooting .......................................................................................... 122 Host Links Installation and Configuration v G&R Appendix: Host Links Manuals..................................................... 123 Appendix: Error Codes.................................................................. 125 OSI/DSA error codes.............................................................................................. 125 Windows Sockets error Codes................................................................................ 137 vi Host Links Installation and Configuration G&R Host Links The G&R Host Links product set is available on all major UNIX, Linux and Windows server platforms. This document is for use by those installing and configuring the UNIX/Linux versions of the product range. VTnnn, xterm, ... terminal environment Qsim V78sim G3270 Host Links platforms Gspool GUFT GlAPI Gproxy Bull/IBM Mainframes LAN Workgroup, PCs and Macs with Glink Ggate Gweb Gspool GUFT GlAPI LDSA Gproxy Powerful, multi-CPU UNIX or Windows NT Windows NT or UNIX on PC VIP7800 terminal environment Pthru Gspool GUFT GlAPI Gproxy Host Links Installation and Configuration 1 G&R 2 Host Links Installation and Configuration G&R Scope of the products The purpose of the Host Links product set is to make Bull and IBM mainframe applications accessible from the Open Systems world. It provides terminal, printer, file transfer and application-to-application connections from Windows and UNIX/Linux servers. Users of the G&R/Glink terminal emulator on their PC or Macintosh should connect through Ggate described below. UNIX/Linux terminal users can run the emulations described here. Qsim allows UNIX/Linux terminals to emulate the VIP7700, VIP7760, DKU7107 and DKU7211. All the emulations are included in one product for access to applications running on GCOS8/7/6 systems. VIP7700 and VIP7760 are included for access to the older applications, and DKU is for access to newer applications using the presentation that is standard within Bull S.A. V78sim allows UNIX/Linux terminals to emulate the VIP7800 (HDS) for access to applications running on the same range of GCOS systems using the presentation that is now standard within Bull-HN. V78sim emulates character, text and forms mode. G3270 allows UNIX/Linux terminals to emulate the IBM3270 for accessing IBM mainframes through the SNA gateway on the Bull front-end, or using Telnet/3270 to connect over TCP/IP. G3270 can also be used to access applications on Bull GCOS systems that use 3270 presentation. G5250 allows UNIX/Linux terminals to emulate the IBM5250 using Telnet/5250 to connect over TCP/IP to IBM AS/400 servers. Gweb is a Web browser interface to the G&R/emulation libraries that allows generic Web browsers to access unmodified Bull or IBM mainframe applications with the appearance of a standard Bull/IBM mainframe terminal. Ggate is a gateway between TCP/IP and the Bull primary network. It can be used by PCs and Macintoshes running the Glink emulator or by any of the Host Links products. Pthru is a gateway to the Bull primary network for either standard VIP7800 (HDS) terminals or PCs and Macintoshes running a VIP7800 emulator. Host Links Installation and Configuration 3 G&R Gspool is a network printer emulation that accepts ROP print output from Bull GCOS8/7/6 print applications and SYSOUT from Bull DPF8-DS. It also accepts IBM3287 print from the IBM mainframes via the SNA gateway in the Bull front end, or via TN3270 from a TCP/IP front end or SNA gateway. GUFT is an implementation of the Bull Unified File Transfer protocol for exchanging files with GCOS8/7/6 systems, or other UNIX, Linux or Windows systems. The GUFT server runs on the Host Links platform. It includes a GUFT client for UNIX/Linux terminal users. A GUFT client for Windows PCs is also available. With all of the above products we deliver Basic and Gline. Basic comprises a set of utilities and a menu system that is used by all the products, and which may also be used freestanding. Gline is a set of ‘line handlers’, which all the products use to make mainframe connections. Gproxy is a monitor that can be used for administration of the G&R communications products. Optionally it can be used for load balancing and license sharing over several Ggate gateways or Gweb web servers. It can also be configured to report to one or more SNMP network management systems. GlAPI (Gline Application Programming Interface) is a set of program libraries that make it possible to write your own applications using the Gline product to hide the complexity of mainframe connections. GlAPI includes both the G&R native programming interface, Gline API, and several libraries of CPI-C, which is the X/Open standard API for application-application communication. 4 Host Links Installation and Configuration G&R Functional summary The G&R Host Links products transform any Windows server or UNIX/Linux platform into a native DSA node in the Bull primary network, or into a 3270 cluster within SNA. Communication between the G&R products and the Bull systems is generally done using the Bull DSA session protocol. Communication with IBM is by TN3270/TN5250. The 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. The DSA connections can also be made over a TCP/IP network, using the Internet standard RFC1006 transport protocol to replace OSI-transport. MainWay front-ends 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 new GCOS7 Diane systems and the new GCOS8 Olympus systems have support for DSA/RFC1006 included in the mainframe. The Ggate product may be used to off-load the DSA session protocol into gateways. By running Ggate on the system(s) with the mainframe connections all other PCs, Macintoshes, Windows and UNIX/Linux machines in your network need only the very small and efficient Ggate protocol layer to connect over TCP/IP to a Ggate gateway with full primary 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. IBM systems can also be accessed using Telnet 3270 (TN3270 or TN3270E) to connect to any TN3270 SNA gateway or front-end. The MainWay gateway, the TN3270 server on the Bull DPX/20 UNIX systems, the IBM TN3270 frontend and the TN3270 server for Windows are all qualified. Host Links Installation and Configuration 5 G&R Bull systems can also be accessed using Telnet VIP (TNVIP). The TNVIP servers in the MainWay and in the Bull DPX/20 are both qualified. However, RFC1006 is supported in the MainWay front-ends with an ONP (Open Network Processor), in the FCP/7 and FCP/8 cards, and in the mainframe for both new GCOS7 Diane and GCOS8 Olympus systems. If RFC1006 is used when communicating with G&R products it 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. 6 Host Links Installation and Configuration G&R Product architecture The UNIX/Linux versions of the G&R products are built in a modular way, and designed to take advantage of the multitasking capability of the UNIX/Linux platform. Thus a single instance of a product will in general consist of three quite separate processes, communicating with each other using pipes and shared memory. In general there will be: • A video handler; which accepts user key input and transforms it into the internal standard format. It also maps all updates of the internal screen image into the control sequences required to update the specific screen being used. • A product; for example an emulator which accepts key input in the standard format and updates the internal screen image according to the presentation being emulated. An emulator will also send and receive data to the mainframe system using the standard interface that applies to all communications protocols. • A line handler; which maps the standard format for communications into the specific line protocol being used. This structure has proven itself extremely efficient and very robust. We are able to develop a video handler for a new screen type, and we know that once it works with one G&R product it will work for all. We are able to develop a new line handler and know that once it works with one product it will work with all. We are able to develop a new product using a given screen and communications protocol, and know that the product will work with all screen types we support, and with all the communications protocols we support. Ggate, Gspool and GUFT server differ slightly from the above model, as they don’t need a video handler, only a line handler. Some of the programs in the Basic product, like Gdir and Glist, also differ slightly as they don’t need a line handler, only a video handler. Host Links Installation and Configuration 7 G&R Architecture diagram Protocol dependent Communication Facilities Line Handler GWEB Video Handler CGI WEB SRV 8 DSA DIWS V78sim Glink VIP Qsim X.25 TCP G3270 GUFT VTxx DKU7102 TERMINFO TTY driver Pthru TTY Gspool Ggate TTY Print TCP socket Host Links Installation and Configuration G&R Delivery We deliver the software in a number of different ways; via e-mail, Internet FTP or tape/floppy. Theses instructions assume you have all the distribution files placed in a directory on the UNIX/Linux machine (e.g. /tmp/hlinstal). These files are only used during the installation and you may remove them when it is done. You should have received these files: install.620 Installation script. srbhl.620 Software Release Bulletin. Licenses Optional, license keys to give access to the software. Unzcccoo Unzip program, see below. pppcccoo.620 One or more ZIP archives with software, see below. The extension will vary for updates, ppp above refers to the product name: 'ppp' product name bas Basic G32 G3270 G52 G5250 gga Ggate gli Gline glp GlAPI gsp Gspool guf GUFT pth Pthru qsi Qsim v78 V78sim Gpr Gproxy Gwb Gweb Host Links Installation and Configuration prerequisite prerequisite 9 G&R You should always install the Basic and Gline products as all the other products depend on them. Basic needs a license key, which is included free with other products. Basic provides the menu structure for the products that have on-line help, as well as the help utility and other utilities. The Gline installation initializes the directory structure for communications, and also installs sample configuration files. The ccc above refers to the CPU family the product runs on. The oo above refers to the operating system family the product runs on. The platforms supported in any release are specified in the SRB (Software Release Bulletin) for the release. The 620 extensions above refer to the Host Links version number. Major releases have the first digit incremented, e.g. 500 and 600. Minor releases have the middle digit incremented, e.g. 610 or 620. Maintenance releases have the last digit incremented, e.g. 611 or 621. Beta releases have a letter appended, e.g. 620a or 620b. Temporary fixes issued between maintenance releases also have a letter appended, e.g. 621a or 622a. Some examples of complete filenames: ggaspaso.620 gsp386l2.620 gwbppca5.620 Ggate for Sun SPARC, Solaris release 2.x, release 6.2.0 Gspool for Intel x86, Linux kernel 2.x, release 6.2.0 Gweb for Bull, AIX 5L for Power V5.1, release 6.2.0 These files are packaged in ZIP format archives using Info-ZIP's compression utility. This format is also compatible with PKWARE Inc's PKZIP version 2. The installation script uses the delivered unzip program to decompress the files. From the above you should be able to pick the files you need from us. Make sure that all files end up in the same directory on your UNIX/Linux machine, and that all the file names are in lower case. These files and this directory will only be used during the installation, so you can place them in /tmp, your home directory, or whatever. Proceed as described in the installation chapter. The Info-ZIP copyright requires us to tell you: Info-ZIP's software (Zip,UnZip and related utilities) is free and can be obtained as source code or executables from Internet/WWW sites, including the Info-ZIP home page: http://www.info-zip.org/ 10 Host Links Installation and Configuration G&R Host Links Installation and Configuration 11 G&R 12 Host Links Installation and Configuration G&R General requirements For platform specific requirements please look in the section entitled ‘Platform specific requirements’ on page 97. Memory usage The exact amount of memory used by the different application will vary from platform to platform. Our measurements indicate that typical memory usage per session for Ggate and Gweb is around 250KB and 500KB respectively. Using the SSL feature will significantly increase the memory usage. The actual increase is platform specific but will typically be from 250KB to 500KB per session. For exact figures please contact G&R with information about hardware platform and operating system version. UNIX/Linux shared memory Each instance of a video handler needs one shared memory segment. Most UNIX/Linux platforms default to 50 or 100 of these. Please refer to your UNIX/Linux documentation on how to increase the number of shared memory segments. PTYs If your terminal or PC logs in to the UNIX/Linux system over TCP/IP and Telnet or Rlogin, then you may also be limited by the number of so-called PTYs (pseudo-TTYs) you can have on the system. Please refer to your UNIX/Linux documentation to see if it’s possible to configure more PTYs and how to do it. Host Links Installation and Configuration 13 G&R 14 Host Links Installation and Configuration G&R Installation step by step The default system directory for Gallagher & Robertson products is: UNIX/Linux /usr/gar During installation you are given the choice of installing on a different directory. If you have previously used the ServerX products this will be detected and you can install on the ServerX system directory (default /usr/serverx). The environment variable used to point to a different system directory is GAR_SYSDIR. For compatibility with previous releases SERVERX_SYSDIR is still supported as an alternative name for this variable, so that when you upgrade old installations there is no need to change anything. For a new installation we strongly recommend that you create a new UNIX/Linux user id and group id for Host Links. An obvious choice of names would be: username=gar groupname=gar and to let the system assign the numeric id's. Log in as, or 'su' to, this user whenever you install new releases, change configuration files or start background processes such as Gspool. Here is an outline of why this is recommended: • This user will own all files created by the installation routine, making it easy to identify files belonging to Host Links. • If you use a disk quota system, the files’ disk space will not be deducted from the quota of whoever installed them. • This user can own all daemon processes, such as the background Gspool and GUFT servers, making them easy to identify. Host Links Installation and Configuration 15 G&R • Host Links can be installed in such a way that only users belonging to the gar group can access the software. Host Links default system directory is /usr/gar. Many of the Host Links programs will look for text files, configuration files and macro files etc. in the Host Links system directory. The installation script will give you a choice to select another directory as the default system directory, but you should note that if you do that, you must define a GAR_SYSDIR environment variable that points all Host Links users to this directory. Preparation Create user gar Before installing Host Links or any of its associated software you should create a user for administration of the Host Links software. Create a new user id gar and group id gar on your UNIX/Linux system. Create /usr/gar Log in or ‘su’ to the root user, create the directory /usr/gar and make the gar user the owner of it with the ‘chown’ command. Copy the software to your system If the Host Links installation files are on a file server somewhere, copy them to a temporary directory (e.g. /tmp/hlinstal) on your system. Your file server won't recognize the new user gar until an administrator configures gar on it, so it is a good idea to copy the files to the local system before you log in as gar. Log out, then in again as gar Log out, then log in again as gar before continuing with the rest of the installation (or su to the gar user id). 16 Host Links Installation and Configuration G&R Disable old Host Links releases Stop any Host Links clients and servers that are running. Remove any old Host Links system directories from your search path. Installation Run the installation script The installation script is very careful not to overwrite configuration files that you have changed at your site. The sample files delivered will only be installed when you do the first time installation, not when you do upgrades. The same installation script is used both for new installations and for upgrades of old ones. cd to the directory that contains the delivery files (/tmp/hlinstal). Start the installation script with: sh install.620 where 620 is the Host Links version number. It will check your file system for G&R software directories (the historical directory /usr/serverx, and the standard /usr/gar) and suggest one of these as the default destination directory if it exists. If neither of these directories can be found, the install program will suggest /usr/gar as the destination directory. The destination directory will be the Host Links 'System directory'. We recommend that you enter /usr/gar as the destination directory, because the Host Links documentation often assumes this to be your System directory when describing configuration files and examples on how to start Host Links products. The script will ask you a few questions before it goes on to do the actual installation. It will show you the user id and group id you are running with and remind you that this user will own all files. Please check that you are running as user id gar and have group id gar, unless you are very sure that you want something else. Host Links Installation and Configuration 17 G&R It will offer to set permissions so that only members of the Host Links group can use the products. Let everyone use them unless you intend restricting access to the group id you are using for installation. It will ask for the directory into which you will install. The default suggested will be /usr/gar unless you have previously installed Host Links on a historical directory. If you already have a Host Links installation and choose a new directory the installation will be as for installation on a new system including the sample configuration files, and you must thereafter copy over your various configuration files from the old installation. Depending on the platform it will ask you to choose an X.400 interface. Unless you will be using the G&R/Gmail X.400 gateway Gx400 and know specifically which interface you will be using, simply accept the default. It will also ask if you are installing a Host Links system which will be shared by several platforms, for example by NFS mounting the Host Links ‘System directory’. Accept the default unless you plan to do this. If some of the product license keys are missing from the supplied licenses file, or if this file isn't supplied electronically with the software, the license key can be installed later with the Glicense program. See the section entitled Glicense for information about G&R license keys. Review the release information When all the files have been installed, the ASCII version of the SRB srbhl.620 will be found in /usr/gar/install. The installation procedure writes a log instlog.620 in the same directory, and also installs sample configuration files there so as not to overwrite files from a prior release. For a first time release, sample configuration files are installed in the correct directories. Set the path Use the system-wide /etc/profile shell script to add /usr/gar/bin to the path for all users. 18 Host Links Installation and Configuration G&R Allow rlogin mode for Host Links If you will be using the rlogin mode of the G&R TCP/IP line handler (gl_tcp) when using G&R products to reach other UNIX/Linux systems you must carry out an extra step as superuser: su cd /usr/gar/bin chown root gl_tcp chmod u+s gl_tcp Install the network software The G&R communications products for accessing the Bull primary network use the DSA session protocol. This session protocol is delivered by G&R, but requires a transport interface on the UNIX/Linux platform. If your Bull mainframe has RFC1006 support then no more communications software is required. We include RFC1006 in Gline. If your Bull mainframe does not have RFC1006 installed, or if you choose not to use it, you will need an OSI-transport stack. There is no OSI-transport stack for Linux. For UNIX, the vendor who delivers the hardware platform normally delivers the stack. It must be configured in a way that is specific for each platform. Please refer to the section entitled ‘Installing and configuring OSI stacks’ on page 101 which deals with OSI software installation on the different UNIX platforms. Build network configuration (dsa.cfg) After the installation program has been run, the file: /usr/gar/config/dsa.cfg will contain an example of a DSA configuration. This must be modified to reflect your network and the systems you will be accessing. See the sample file in the section entitled Sample dsa.cfg on page 89. Please refer to the G&R/Gline manual for more details and examples. Remember to compile dsa.cfg with the 'glcc' program every time you have modified your dsa.cfg file. Host Links Installation and Configuration 19 G&R Test Test your configuration. You will find the DSA test utilities useful e.g. Gping gping -li dsa -dn b7dl -da iof -du jim -pw mydogsname Gping - $$DSA: Connected to application For details of the test utilities please refer to the Appendix. Set TERM variable Users of the Host Links terminal handling products such as the Qsim, G3270, and V78sim emulator family, and users of the menu system, file navigator and utilities included in the basic product set must select the required video handler. The video handler must match the terminal type they are using. The most convenient way of doing this is to set the TERM variable. TERM selects the Terminfo file used by UNIX/Linux applications to control specific terminals, so Host Links generally tests only the first few characters of the TERM, so that various Terminfo files may be used. The choices are: 20 Vt1xxxx any TERM variable starting with vt1 will select the vt100 video module. Used for VT100 terminals and clones. Vt2xxxx any TERM variable starting with vt2, vt3 or vt4 will select the VT200 video handler. Used for VT200, VT300, VT400 terminals and clones. tws21x any TERM variable starting with tws21 (or dku7) will select the handler for the Bull DKU7102 terminal or clones. vipxxxx any TERM variable starting with vip will select the handler for the Bull VIP7801 (up to HDS 7) terminal or clones. glinkxxx any TERM variable starting with glink will select the VIP handler and enable the Glink extensions on entry to Host Links. Glink reverts to VTnnn on exit (see glinkvt below). glinkvip selects the VIP handler with Glink extensions, and leaves it in VIP78 mode when executing other UNIX/Linux products. This is the recommended way of running UNIX/Linux with Glink. Host Links Installation and Configuration G&R Any other TERM variable will select the generic video handler that controls stranger terminals using the Terminfo file. The UNIX/Linux administrator can set the TERM variable in the default /etc/profile or user-specific .profile (or equivalent for the UNIX/Linux shell being used). TERM=vt220; export TERM; or TERM=glinkvt; export TERM; If not set there, it can be picked up from the terminal at connect time if the Telnet terminal type response is configurable. Glink users can choose between using extended VIP78 mode always (as recommended), or only when running Host Links. We deliver improved Terminfo files for Glink users: glinkvip for users who start in VIP78 mode and remain in it, and glinkvt for users who start in VTnnn mode and switch in/out of VIP78 mode on entry/exit to/from Host Links. Note that we also deliver extra set-up programs for users of X.11 terminals, users of the dtterm product under the Common Desktop Environment and users of FTP software’s TN.EXE terminal emulator on the PC. All are described in the same section entitled Video handlers, and the sub-section Terminfo files delivered. Set Host Links profiles The profiles are used to set various parameters for customization of the Host Links environment. This will in general not be necessary unless you have special needs. For information on the files and the available parameters see the section entitled Profiles configuration on page 47. Configure the context manager If terminal users are using the Host Links emulators (Qsim, G3270, V78sim) or concentrator (Pthru) then you can allow them to start multiple simultaneous sessions from a pre-configured menu, and ‘hot-key’ between the sessions as needed. Please refer to the section entitled Context manager on page 41. Host Links Installation and Configuration 21 G&R Configure the Host Links servers Host Links servers are started by simply executing the command line, see the product manuals for command lines and parameters. You can start them manually for test purposes, but typically you should set up the system such that the command is run each time the system boots. This applies particularly to Ggate and the DSA listener, but can also be used to start up Gspool instances that will listen for incoming connections and for the GUFT server. Gspool instances which listen for DSA connections and the GUFT server are however best set up for start on demand, see the section entitled Starting applications on demand on page 23. Note that because Ggate forks a new process for each connection, it needs to be run by a user ID that has privileges to fork many processes. Typically this means running gg_tcp as root and not as the Host Links administrator user ID. The DSA listener also forks processes if configured to start programs on demand, but usually the default UNIX/Linux value for the number of forked processes is sufficient. However, if it is accepting incoming RFC1006 connections it must run as root, because access to the RFC1006 port is restricted to root. Start at system startup On AIX systems you can start the Host Links servers directly from /etc/inittab, by placing the command lines at the end of the file: gg_tcp:2:once:/usr/gar/bin/gg_tcp nl_dsa:2:once:/usr/gar/bin/nl_dsa gspool:2:once:su gar -c "/usr/gar/bin/gspool -dpf8 -id gs9 -dpfq -pc lp -li tcp” On many other systems you can create a shell script e.g. S99gar with the content below, and place it in the /etc/rc2.d directory: /usr/gar/bin/gg_tcp /usr/gar/bin/nl_dsa su gar -c "/usr/gar/bin/gspool -dpf8 -id gs9 -dpfq -pc lp -li tcp” The format and placement of these installation scripts vary from OS to OS and between versions of the same OS. Please consult your operating system manuals in order to obtain the correct method for creating startup scripts. 22 Host Links Installation and Configuration G&R Starting applications on demand Applications can be started on demand when DSA connections arrive. Currently Gspool and GUFTSRV can be started in this way, as well as user-written applications using GlAPI. The nl_dsa listener handles this, 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. It is placed in the /usr/gar/servers/.gli directory. The file is either config.dsa or config.diw for nl_dsa and nl_diws respectively. Example file /usr/gar/servers/grdl.gli/config.dsa: * Three printer mailboxes listen -mn printer1 -cmd gspool -pc listen -mn printer2 -cmd gspool -pc listen -mn printer3 -cmd gspool -pc * UFT server listen -mn filetran -cmd guftsrv * User written application listen -mn userapp -lim 1 -ext -cmd "lp -dprt1" "lp -dprt2" "lp -dprt3" userapp arg1 arg2 See the Host Links Gline manual for details of start on demand. Host Links Installation and Configuration 23 G&R Build Host Links menus The Host Links utilities in the Basic package delivered with all other Host Links packages include a menu display and navigation system, Gmenu. If you enter the command gmenu at the command line you will see the following display (here using the G&R/Glink terminal emulator as a UNIX/Linux terminal): This facility is used for navigating in user menus and executing commands. The G&R applications such as Qsim use it for navigating in help menus. In both cases it allows unlimited user extension of the help menu network, and activation of applications from the menus. In the menu above only the F4 key to start Gdir will work unless you have licensed Gmail. Press Esc (twice) to leave the menu. The help facility may be added to your own applications merely by providing for execution of a gmenu myhelpdir command from the application. In this way you may add all the functionality of the G&R/help system to your own programs, and at the same time save a lot of development resources that would otherwise be used in adding a menu capability inside the application. 24 Host Links Installation and Configuration G&R The default menu presented when you execute the command line can be found in /usr/gar/help/menu (a help directory must contain at least one menu file with name menu) and can be modified using your favorite text editor. However if you press the double quote (“) on your keyboard while viewing the menu; this default menu key starts Gedit and loads the menu ready for editing. Gedit has a line graphic edit/display of the Host Links character set, and you would see the following, except that the standard menu file loaded into Gedit would be: /usr/gar/help/menu: The line graphics were entered into the file using the line graphic capability of Gedit (LF G to start, LF SPACE to stop). The menu is activated by the command lines (>) that precede the display text. directive action when: command what happens >cr key CR is pressed a #B/gdir activate G&R video interface product >f3 key F3 is pressed e #B/pthru execute other G&R or external product >s4 key shift F4 g go to menu, relative to help directory >xQ key Q is pressed x exit menu system Host Links Installation and Configuration 25 G&R To add Qsim and Pthru to this menu add the two command lines for F1 and F2 as below, and use the line graphic capability of Gedit (LF G to start, LF SPACE to stop) to modify the drawing. as follows: On exiting from Gedit with update file (LF W) you will be returned to the menu, but now showing the two new commands available. F1 F2 the e executes Pthru with no command line options the a activates Qsim with no command line options If you exit without updating (LF Q) then the menu is untouched. Use the help (LF H) in Gedit for details on its capabilities. Please refer to the G&R/Gmail reference manual for details of Gmenu. 26 Host Links Installation and Configuration G&R Environment Some configuration may only be done using UNIX/Linux environment variables. It isn’t possible to configure these parts using the profiles or configuration files, as they actually specify where these files are and how they should be interpreted. PATH It is recommended that you add the location of the Host Links program files to your PATH. The location is /usr/gar/bin by default. The PATH update will normally be done for all users in the system-wide /etc/profile shell script, but may be set individually. Should you decide not to change the PATH then it is also possible to run any Host Links program by specifying the complete path name. GAR_SYSDIR This is not normally set. If you did not install Host Links in the default directory, /usr/gar, it has to be set to the name of the directory where you did install it. GAR_MODE This is not normally set. In some circumstances it may however be useful to specify the mode part of the user ID for a particular user in particular circumstances. It can be used in selecting special sections from Host Links profiles and configuration files. As UNIX/Linux doesn’t have log-on modes they can instead set using this environment variable. Host Links Installation and Configuration 27 G&R 28 Host Links Installation and Configuration G&R Product startup Configuration files Configuration files from earlier releases are not overwritten, the sample files are left in the /usr/gar/install directory. After running the installation program for the first time on a system sample configuration files for the various products can be found in: /usr/gar/config/default You will find the files: gweb.cfg gwebs.def cpic.cfg qsim.cfg pthru.cfg v78sim.cfg g3270.cfg guft.cfg context.cfg Modify these files to suit your configuration. The user guides for the products describe all available parameters. Users need read permission for the configuration files they use and the files might include passwords in the parameters. For security you may create individual configuration files for each user in the directories: /usr/gar/config/$LOGNAME Each of the configuration files created in these directories will only be read for the given user, and can be protected from all others using standard access control. The default configuration directory will NOT be used for users who have a private directory. Gweb and CPI-C parameters MUST be supplied in the default directory, they do not look for a user directory. Host Links Installation and Configuration 29 G&R Command syntax Products may be started at the UNIX/Linux prompt, from Gmenu or from shell scripts etc. with commands in the form: product [-xx yyyyyy ] where -xx yyyyy is one or more legal parameters. e.g. qsim -cl 7q -xl ge -li dsa -dn en40 -da tss Parameters are by default for the product. The -li option signals the name of the line handler and that the following parameters are for the line handler instead of the product. It is also possible to switch back and forth between product parameters and line handler parameters using the -user and -host options. e.g. qsim -li dsa -dn en40 -user -xl ge -host -da tss Switching back and forth in a command line is not particularly useful, but when using a configuration file it is extremely important to remember to switch between product and line parameters as they are picked up from different sections of the file. 30 Host Links Installation and Configuration G&R Product usage Please refer to the product manuals. Host Links Installation and Configuration 31 G&R 32 Host Links Installation and Configuration G&R Host Links Server Administration Gmanager Gmanager is the Host Links administration tool. It can be used to control, configure and monitor all the G&R Host Links server programs. The dialog and interaction between the server programs and Gmanager is based on information located in a database file _active.srv that is located in the Host Links servers directory. The first time a Host Links server program starts up it registers itself in this ‘active’ file. Thereafter the server program updates this database with status information whenever the server is active. The Gmanager program is available in 2 different versions – a Windows GUI based version gmanw.exe and a character based subset gman (UNIX/Linux binary) or gman.exe (PC console application). The basic functionality of the two versions is the same, but the Windows version interfaces directly to other Windows-only Host Links administrative tools (Gconfig, Gservice), and can also start the browser directly to view HTML reports produced by Gproxy, if enabled, or to view the HTML pages associated with a Gweb or Glink for Java installation. The Gproxy reports, Gweb and Glink for Java web pages are of course available to administrators of UNIX/Linux Host Links systems, and can be viewed by starting a browser manually, and connecting to the appropriate URLs: http://mysite.mydomain.com/Gproxy http://mysite.mydomain.com/Gweb http://mysite.mydomain.com/GlinkJ A summary of the available functions follows. The Windows-only functions are marked. Host Links Installation and Configuration 33 G&R Gmanager can be used to perform the most common Host Links administrative tasks i.e.: View the last reported status information from the servers Start new server Restart a server Send a command to a server View a server log file View a server trace file Load the DSA configuration into an editor Compile the DSA configuration Call Gconfig the server configuration program (Windows) Start the configuration wizard (Windows) Load the Gservice configuration into an editor (Windows) Start the Host Links server programs using Gservice (Windows) Edit the product specific configuration files Connect directly to the Gproxy HTML pages, if enabled (Windows) Connect directly to the Gweb HTML pages, if enabled (Windows) View program version numbers, program link information (Windows) View license info and license usage (Windows) View Host Links environment information, the ‘VMAP’ (Windows) 34 Host Links Installation and Configuration G&R The commands that are accepted by all servers are: DOWN - terminates the server STATUS - reports server-specific status information to the log file PARAM - brings up a dialog box that allows the operator to give a command line parameter to the server. Note that some parameters do not work when given interactively i.e. they can only be handled at server startup time DEBUG ON/OFF - toggles on and off tracing interactively Additionally, the server in question might support other interactive commands. For a description of the supported commands, check the server-specific documentation. Host Links Installation and Configuration 35 G&R Additional tools Gdir This is a directory navigation and file edit/display/execute tool. The editor and display programs used are configurable so you can replace them with your favorites. The keyboard is configurable so that you can add shortcut keys that make several of your favorites available for use on the selected file. Gdir is supplied as a character based utility gdir (UNIX/Linux binary) or gdir.exe (PC console application). You might find this very useful when navigating in the Unix/Linux file system to look for Host Links configuration or trace files. In the Windows environment it offers somewhat different functionality than MS Explorer. Gver This is a utility program that lists the version number of the G&R Host Links release programs that you are using. Gdir is supplied as a character based utility gver (UNIX/Linux binary) or gver.exe (PC console application). 36 Host Links Installation and Configuration G&R gver -r Lists only the release number. jim@gars ~ $ gver -r 6.1.1b/spaso gver Lists details of all the G&R software installed. jim@gars ~ $ gver 3270web 5250web 7800web dkuweb 2398792 2492104 2469820 2488016 gweb/cpicweb gweb/cpicweb gweb/cpicweb gweb/cpicweb 6.1.1b/spaso 6.1.1b/spaso 6.1.1b/spaso 6.1.1b/spaso Oct Oct Oct Oct 16 16 16 16 2003 2003 2003 2003 13:49:30 13:49:30 13:49:30 13:49:30 Gdump This utility program lists the Host Links environment. It is supplied as a character based utility gdump (UNIX/Linux binary) or gdump.exe (PC console application). Host Links Installation and Configuration 37 G&R Host print in DSA networks Print to screen session If the application mixes print with normal screen output using print addressing for the print blocks, and screen addressing for screen blocks the DSA line module simply passes print output down to Glink or the Host Links emulator which in turn have numerous options that define how to handle it. Pthru Print output delivered to a VIP7800 terminal must use the defined VIP7800 print control sequences, and the VIP7800 terminal interprets them. If you are using Glink it can be configured to print on the PC printer, a file, or the LAN-spooler. VIP7800 terminals must have an attached printer. Pthru will also map VIPheader print addressing to in-line print start and print stop sequences. VIP header print addressing is used by some applications written for synchronous VIPterminals, and need to be mapped to in-line sequences for asynchronous terminals. The Pthru parameter for transparent print (-PT) can be turned off to inhibit this mapping. Qsim Print output delivered to a synchronous Questar must use print addressing in the VIP-header, or embedded ESC Z.......(US) sequences. Qsim supports 'transparent print', which means that data blocks sent to the user workstation with print status in the VIP-header will be printed on the device configured as the print path (-pp) in Qsim (see Qsim user guide). This may be a physical UNIX/Linux printer, or a file. If it is a file it may be automatically delivered to the UNIX/Linux print spooler (-pc or -pm). Additionally, if the terminal has a printer attached or is a PC with Glink, the attached printer may be configured (-pp *). The PC printer in this case may be a real printer, or it may be a file, or the LAN-spooler. 38 Host Links Installation and Configuration G&R V78sim Print output delivered to a 7800 terminal must use print addressing in the VIP-header, or embedded CSI ... p sequences. V78sim supports both. The VIP-header print addressing is treated as 'transparent print', which means that data blocks sent to the user workstation with print status in the VIP-header will be printed on the device configured as the print path (-pp) in V78sim (see V78sim user guide). This may be a physical UNIX/Linux printer, or file. If it is a file it may be automatically delivered to the UNIX/Linux print spooler (-pc or -pm). Additionally, if the terminal has a printer attached or is a PC with Glink, then the attached printer may be configured (-pp *). The PC printer in this case may be a real printer, or it may be a file, or the LAN-spooler. Print on separate session If mainframe print output is being sent to an independent mailbox then the DSA line module may be configured to merge this print with the terminal session. The resulting merged session looks to Glink or the Host Links emulators exactly as if the application had used print addressing. Please refer to the Gline manual for details of the -pco option. Alternatively a copy of Gspool can accept the print as described below. Gspool If mainframe print output is being sent to an independent mailbox (not the user terminal, but a separate LID as used for a ROP-printer), then the Gspool product may be used to accept the print. Gspool functions quite independently outside of the user process and may be configured to connect to the mainframe, or to wait for the mainframe to connect to Gspool. Printers configured in DPF8-S&F must log on to GCOS8. Printers configured in RSM8 on GCOS8, in Twriter on GCOS7 and printers configured in the SNM on GCOS6 all wait for the mainframe to connect to them. There is no Remote Batch facility available in UNIX/Linux, so GCOS8 SYSOUT has to be delivered to Gspool via a GCOS8 SYSOUT spooling program such as RDF8, DPF8-DS, RSM8 or Dispatch8. Host Links Installation and Configuration 39 G&R Context Manager Multiple sessions Many users are in a situation where they consult/update several mainframe systems as well as running local applications, and often they would like to do this without terminating one mainframe session in order to start the next. If they are running a Windows PC with Glink, or some UNIX/Linux windowing system then this is no problem, they just open multiple windows. If they are running from a regular terminal the Host Links environment provides a user interface to the UNIX/Linux multitasking capability. In this case the user starts the Context facility, rather than the individual products, and all products are started from Context. General description Context is both a menu system and a program-switcher for the Host Links products. At startup it presents a user configurable menu, showing all available mainframe systems. By pressing one key, the desired product will be started, or switched to if already started. While executing one of the Host Links products, even while in a mainframe session, it is always possible to go back to the menu or to jump directly to another product with another mainframe session. When a Host Links product is terminated, the Context menu will be shown again. All active mainframe sessions are marked with the text "RUNNING". UNIX/Linux command level is also available from the menu. When Context is terminated all active mainframe sessions will be terminated. In this way Context provides multiple simultaneous mainframe connections with individual configuration of each mainframe session. Context can also be used to start other applications with or without the possibility to switch back to other entries in the menu. You always return to the menu when you terminate the application. Host Links Installation and Configuration 41 G&R How to start Context Context is started by the command context [-par] [-i n] where the -par parameter tells Context to allow the user to edit the startup parameters interactively. The default is no display of the command line, and that all parameters have to be specified in the configuration files. The -i n parameter causes immediate start in context n. E.g. context -i 2 Use of Context without -par looks better for the inexperienced user, and will as a desirable side effect disable the user from specifying his/her own parameters for the mainframe sessions. In this way the administrator will have full control of the configurations used. Moving between active contexts When a Qsim session is started the user can always return to the Context manager by LF # or by quitting Qsim (LF Q). It is also possible to switch directly between the sessions with the key sequence: LF # In the same way the user can return from a Pthru session by command: $*$# [] In addition to the Qsim and the Pthru sessions, the Context manager also allows the user to start other applications, and to escape to UNIX/Linux command level (if allowed in the profiles file). 42 Host Links Installation and Configuration G&R If the other applications have the possibility of executing UNIX/Linux commands they may switch between contexts using the supplied utility ctxsw. ctxsw n as a UNIX/Linux command or from an application configurable menu. The application is suspended at that point, and will resume from there afterwards. The application must save and restore screen content. When the user chooses to terminate the Context manager with the Q command, the Context manager will stop the sessions that have been left active, and clean up all resources used. Context configuration files By the use of a configuration file context.cfg Context allows configuration of command keys and command descriptions in the Context menu. Context allows user-specific configurations by first searching for the context.cfg file as follows: /usr/gar/config/$LOGNAME/context.cfg If this file or directory does not exist, Context will use the default file, which MUST exist: /usr/gar/config/default/context.cfg The default file is not used at all if the user has a private file. Host Links Installation and Configuration 43 G&R The context.cfg file should have the following format: Menu [] [] where: Menu is a keyword in column 1, followed by directives with space (or tab) delimiters. a for a product using the video handler and context switching (Qsim/V78sim/G3270); e for all other program types. is the name of the program to be started (e.g. Qsim or Pthru). is a character that will be used to select a line in the menu. Use numbers from 1 and upwards so the numbering in the context switching facility matches the position of the command in the menu. can be any text describing the command. are parameters for the product to be started. Parameters may start in any column, and several may be on the same line. You should not put more parameters than necessary in context.cfg. General parameters for the products should be put their respective configuration files: /usr/gar/config/[$LOGNAME|default]/pthru.cfg /usr/gar/config/[$LOGNAME|default]/qsim.cfg 44 Host Links Installation and Configuration G&R Example of context.cfg Menu a qsim 1 Qsim session (IOF - GCOS7) -mi m1 -li dsa -ll 6144 -du art -dp art -da iof -d? passw -dn en06 Menu a qsim 2 Qsim session 2 (TSS - GCOS8) -li dsa -da tss -dn vd88 Menu a qsim 3 Qsim session 3 -li dsa -ll 6144 Menu e pthru 4 Pthru session 4 (TSS - GCOS8) -li dsa -da tss -dn vd83 -d? passw Menu e pthru 5 Pthru session 5 -li dsa Menu e pthru 6 Pthru session 6 -li dsa -ll 3000 Menu e vi 7 Program editor (vi) /tmp/tmpfile Menu a guft 8 G&R Unified file transfer Host Links Installation and Configuration 45 G&R 46 Host Links Installation and Configuration G&R Profiles configuration General The profiles are used to set various parameters for customization of the Host Links environment for different users. The profiles are read into the system each time a Host Links program is started by a non Host Links program, like the UNIX/Linux shell. A utility program called Gstart does this reading on behalf of the other products. This is all done automatically whenever you start a product. File location All PROFILES files are located within special sub-directories within the Configuration directory. The Configuration directory is per default a directory config located in the System directory. The System directory is by default /usr/gar. This name may be overridden by setting the GAR_SYSDIR environment variable. The format of the different PROFILES files is the same. When Gstart starts, it first reads the default profile in order to establish defaults for users logging on. It then reads the profile belonging to the user logging on, and finally reads the system profiles file at the end. Host Links Installation and Configuration 47 G&R The DEFAULT profiles Path name: /usr/gar/config/default/profiles This PROFILES file is used to configure default settings for all users. It is possible to override these settings in the user profile (see below), so make sure that important settings that a user should not be able to override are defined in the system profiles file (see below). The sample delivered is very simple, and defines all terminals as connected on eight bit lines: * Sample default profiles file * This file is read before the users and system profiles eightbit The USER profiles Path name: /usr/gar/config/$LOGNAME/profiles This file is the user's private configuration file, and all settings that a user makes privately should go in here. The directory containing user configurations may be specified with the CONFIGDIR directive. Typical content in the user's PROFILES file are special colors, preferred editors and file list programs. The SYSTEM profiles Path name: usr/gar/config/system/profiles This file is read after the two other PROFILES files to ensure that important settings that no user profiles should be able to override are enforced. The sample file has no directives: * Sample system profiles file * This file is read after the default and users profiles 48 Host Links Installation and Configuration G&R File organization Because Host Links is normally configured by an administrator, and is accessed by many users, the PROFILES file is organized in sections which may apply either to all users (the Default section), a group of users (the User section), specific stations (the Station section), a combination of the last two (the Station user section) or specific terminal types (the Termtype section). Each section is prefaced with a header line: DEFAULT directive ... ....... USER user[.account[.mode]] directive ... ....... STATION|TERMINAL station directive ... ....... STATIONUSER|TERMUSER station user[.account[.mode]] directive ... ....... TERMTYPE termtype directive ... ....... Directives in the Default section apply to all users (stations) within the network. The directives in the User section only apply to those identified with a matching user ID. The user and account parts of the user ID are picked up from the UNIX/Linux log-in directly. The mode part of the user ID is set to the value of the GAR_MODE environment variable, if defined. Directives in the Station section only apply to the stations with a matching UNIX/Linux device name. Directives in the Termtype section only apply to those with a matching TERM environment variable. Directives found later in the file will override those found earlier; thus you may include options for all users in the default section and reset them for some users later on in the file. Blank lines and lines beginning with an asterisk (*) are treated as comments. Host Links Installation and Configuration 49 G&R Directive format The profiles file directives have the following format: A directive begins with a keyword that identifies the command and it may have one or more arguments. Some of the arguments are interpreted by the G&R application; others may be intended for an external application and therefore passed on. The following arguments are interpreted by G&R: 50 Directive Use #A will be expanded to the account part of the user id (user.account.mode). #B expands to nothing for compatibility with the G&R/Gmail products #C will be expanded to the directory path name where the user's configuration files reside (/.../config/username). #D will be expanded to the working directory path name. #F will be expanded to the full path name of the current file. #G will be expanded to the user's full name. #H will be expanded to the home directory of the user. #I will be expanded to the help directory. #L will be expanded to the language currently in use. #M will be expanded to the mode part of the user id (user.account.mode). #N will be expanded to the file name of the current file. #S will be expanded to the System Directory. #U will be expanded to the user part of the user id (user.account.mode). #V will be expanded to workstation identification. #Z will be expanded to the extension part of the file name of the current file. #%X% will be expanded to the contents of the environment variable X. Host Links Installation and Configuration G&R Directive Use ## will be replaced by a single # character. * asterisks are used to indicate various screen update classes, see below. Screen update classes Various screen update classes are available, the class being specified by the number of asterisks before the command. The classes of commands are: Asterisks Meaning None The product clears the screen, displays the command, executes the command and, when the command terminates, waits for Enter before redisplaying the screen. * Same as None, except the product will not wait for Enter after executing the command. ** The product will execute the command without clearing the screen or displaying the command, and update only the variable data afterwards (not the menu). *** The product will not change the display, simply move the cursor to the bottom line while the command is executing. **** The product will execute the command without clearing the screen or displaying the command, but will rewrite the screen. For example the parameter DIREDIT vi #F applies to Gdir. If you select the 'edit file' option in Gdir this parameter will cause it to start the UNIX/Linux file editor to edit the file presently being pointed at with the bar cursor. After the editor has terminated, you would have to press ENTER to continue. It is therefore better to configure an editor as a class 4 command, for example DIREDIT ****#B/gedit #F Host Links Installation and Configuration 51 G&R This is the default value for DIREDIT, so if nothing is configured this command will be used. List of available directives 52 Directive Default value BWMODE OFF COLOUR Change G&R product colours, see below COLOURMODE OFF CONFIGDIR #S/config/#%LOGNAME% CURSORSIM OFF DIREDIT ****#B/gedit #F DIRUSE #S/config/default/diruse DOLLAR ON EDIT ON EIGHTBIT OFF EXEC ON EXTENDED OFF HELPDIR #S/help HOMEDIR #%HOME% KPAM ON KPNUM OFF LANGKEY none Language none LISTER ****#B/glist #F MACRO ON MENU ON MISCDIR #S/misc Host Links Installation and Configuration G&R Directive Default value SERVERDIR #S/servers SETUP ON SEVENBIT OFF Shell ON SOUND ON VIDEO None. Overrides the TERM environment variable to choose a video handler VIPGLINK Modifies the VIP78 handler OFF, unless TERM starts with glink VIPUNIX Modifies the VIP78 handler OFF, unless TERM starts with glinkvip Description of the available directives BWMODE – force colour off If you use the VIP78 video handler in Glink mode and don’t want Glink to display colours then set this option. BWmode ON (default OFF) COLOUR – change default colour settings You may change the default foreground colours used by G&R applications. If you start Gdir you will see that the screen is divided into colour sections, starting at the top with the product header section which is normally white and inverse video. Then follows the menu section that is turquoise. Fourteen sections are defined all together. You may change one or several of these colour sections. The format of the COLOUR directive is: COLOUR sectionnumber colourcode Host Links Installation and Configuration 53 G&R The section numbers range from 0 to 13. The product header is assigned to the number 0, the menu is assigned to 1 and so on. The desired colour is specified with a colour code. The available colour codes are: R(ed), B(lue), G(reen), T(urquoise), V(iolet), Y(ellow), W(hite), (blac)K, I(nverse), H(idden), F(lashing), U(nderline), L(ow intensity) A colour may also be combined with Inverse and Low intensity code. For example, the directive COLOUR 1 WL will set the menu to white, low intensity. Below are listed the section numbers together with the default setting and a short description of the sections. COLOUR COLOUR COLOUR COLOUR COLOUR COLOUR COLOUR COLOUR COLOUR COLOUR COLOUR COLOUR COLOUR COLOUR 0 WIL 1 TL 2 Y 3 W 4 RI 5 WU 6 GL 7 RI 8 WL 9 R 10 R 11 W 12 TL 13 Y Product header Menu Menu attention Prompt Field input Header text Data (normal) Marked data Information text Attention text Data red Data white Data blue Data yellow COLOURMODE – force colour on The VIP78 video handler in VIP7800 terminal mode and the VT200 video handler both default to black and white display only. This directive tells these video handlers to display in colour instead. 54 Host Links Installation and Configuration G&R Colourmode ON (default OFF) CONFIGDIR directory – directory for user configurations This directive specifies the directory where all user configuration files are stored, for example the user's PROFILES file. Note that two special configuration files, the Default and System PROFILES files, are stored in a fixed location under the #S/config directory. All user PROFILES files and other configuration files, however, are stored in the CONFIGDIR directory. CURSORSIM - software simulate cursor The TWS video handler normally lets the screen itself manage the cursor display. This directive make the video handler simulate it instead with inverse and underline attributes. Some people find this mode more visually pleasing. CURSORSIM ON DIREDIT directive – configure editor for Gdir With this directive you may configure the text editor to be used when you select the 'edit file' function in Gdir. If DIREDIT is not configured, the G&R editor, Gedit, will be started. #F will include the current file name. DIREDIT *vi #F will start the vi editor with the file you are pointing at as argument. Host Links Installation and Configuration 55 G&R DIRUSE pathname – user command file for Gdir This directive specifies the name of the file containing the user commands for the directory utility, Gdir. The default value is a file named diruse located in your own configuration directory /.../config/username/diruse If this file does not exist, the diruse file in the default configuration directory /.../config/default/diruse is used. This default file is meant as an example only and should be modified. You may share a DIRUSE file with other users or have one or more for your own usage. The following directive specifies that you have a DIRUSE file in your home directory named mydiruse. DIRUSE #H/mydiruse You can use #A, #M and #U in the specification of the DIRUSE file. DOLLAR – permission to enter directory manager This directive controls whether you are allowed to use the keys LF $ to start the Gdir Directory Manager from the program you're executing, or not. It is a security consideration to allow this or not. To disable this feature, use the directive Dollar OFF See also the EXEC and SHELL directives. EDIT - permission to run editor on screen image This directive controls whether the emulators allow you to start an editor on the current screen image. You can disable that feature by setting this directive OFF. 56 Host Links Installation and Configuration G&R EIGHTBIT - screen supports 8-bit characters Specifies that you want the extended character set (8-bit national characters) and the terminal is using a full 8-bit communications line. This is only supported for terminals with an 8-bit mode e.g. BDS, VT200 and the Glink emulator. UNIX/Linux systems must have parity and strip inhibited. Please note that older versions of Telnet often have the strip option set, and remove the top bit. EXEC – permission to execute commands This directive controls whether you are allowed to execute UNIX/Linux commands from the program you're running. It is a security consideration to allow this or not. To disable this feature, use the directive Exec OFF See also the DOLLAR and SHELL directives.. EXTENDED - 8-bit characters over 7-bit path Specifies that you want the extended character set (8-bit national characters) but the terminal is running in 7-bit mode on the communications line. This is supported only for the Questar (using SS2) and Glink (pseudo SS2). VT200, BDS and other terminals need an 8-bit line to use 8-bit characters HELPDIR directory – help base directory The default base help directory is named HELP and is located in the System Directory. The base help directory may be placed elsewhere with this directive. If you enter a command in any G&R product, you may refer to the help directory with the #I convention. You can use #A, #M and #U in the specification of the help base directory. Host Links Installation and Configuration 57 G&R HOMEDIR directory – users home directory The default home directory for a user is his UNIX/Linux home directory. You may set a permanent home directory with this directive. If you enter a command in any G&R product, you may refer to the home directory with the #H convention. For example, to copy the file you are pointing at in Gdir to the home directory using the same name you could enter the following command: cp #F #H If the name of the current file is testfile and your home directory is /home/peter, the above command would be expanded to cp testfile /home/peter You can use #A, #M and #U in the specification of the home directory. KPAM - keypad application mode Specifies that the VT200 video handler should default to do interpretation of function keys. CTRL/N may still be typed to change this while using the product. If KPAM mode is switched off the application mode sequences must then be interpreted by the Host Links product being used. KPNUM - keypad numeric mode Specifies that the VT100 and VT200 video handlers should default to interpret the number pad as sending numbers instead of function keys. Ctrl/N may still be typed to change this while using the product. 58 Host Links Installation and Configuration G&R LANGKEY xx - configure 7-bit screen language Turns on character transliteration for a specific country. It is normally used by 7bit terminals to convert 7-bit national characters from the keyboard to 8-bit internally, and convert back to 7-bit for display. An extended or 8-bit terminal may use the option to view 7-bit national characters as 8-bit, but retain the 7-bit values internally. The following keys are supported: US GB GE FR US ASCII (default) UK ASCII German French SF DE NO Swedish/Finnish Danish Norwegian SP IT JA Spanish Italian JIS ASCII Note that the value of the language key may also be toggled dynamically at any time using the CTRL/F key. The Default is US ASCII (no transliteration). LANGUAGE ccc – configure dialogue language Many G&R programs can operate with different languages, provided the correct language files are installed. Two files are needed for each language, the progtext[.ccc] and the messages[.ccc] files, located in the misc directory subordinate to the System directory. The ccc file name extension indicates the language to use, and corresponds to the argument to the LANGUAGE ccc directive. The language key can be up to 3 characters long. Default is to have no specific language key. For example, the directive to select French program texts is LANGUAGE FR Host Links Installation and Configuration 59 G&R LISTER directive – configure file list program Many of the products use Glist as the default to display files. If you prefer another list utility you may configure it with the LISTER command. The default command is LISTER ****#B/glist #F #B expands to nothing and #F refers to the current file. The **** is the standard G&R convention, telling the product that called the list command to update the whole screen as soon as the list command terminates without waiting for the user to enter a CR to continue. If you want to configure the UNIX/Linux pg command as the file list program, you should use the following configuration. LISTER pg #F The pg command terminates as soon as the complete file is displayed. With this update class the screen is not updated by Gdir until you type ENTER to allow you to read the last part of the file. MACRO - permission to define keyboard macros This directive controls whether the emulators allow you to define keyboard macros. You can disable that feature by setting this directive OFF. MENU – display program menus Most of the G&R applications have a menu in the upper part of the screen. By default this menu is always displayed. If you know the G&R products well, you may choose not to display these menus to give more room for the variable data. You may at any time turn the menu on and off while running a G&R product with the LF & command, independent of the default you have configured in the PROFILES file. 60 Host Links Installation and Configuration G&R MISCDIR directory – miscellaneous file directory This directive specifies the directory where miscellaneous files are stored. These files are all necessary, and include character set transliteration tables nnnn.chs, program text files progtext[.ccc] and status code explanations messages[.ccc]. SERVERDIR directory – directory for servers This directive specifies the top directory where configuration files for the various gateways and servers are stored. Please check the appropriate documentation for the different servers for details. SETUP - permission to run setup commands This directive controls whether the emulators allow you to change configuration parameters. You can disable that feature by setting this directive OFF. SEVENBIT - screen does not support 8-bit characters Resets the effect of EXTENDED and EIGHTBIT, for use when you want to specify, say, EXTENDED in the default section and override it for particular terminals. This is the default setting for the character set. SHELL – permit escape to shell This directive controls whether you are allowed to use the keys LF ! to start a UNIX/Linux shell from the program you're executing, or not. It is a security consideration to allow this or not. To disable this feature, use the directive Shell OFF See also the EXEC and DOLLAR directives. Host Links Installation and Configuration 61 G&R SOUND – control alarm Most G&R applications sound the alarm to indicate error situations, e.g. if you press a key with no significance, or when the mainframe system ask an emulator to beep. You can disable the alarm bell by setting this directive OFF. VIDEO handler - select video handler This directive may be used to select a video handler in the cases where the TERM variable is not set at all, or when, because of other UNIX/Linux applications, it has to be set to some specific value that Host Links doesn't recognize. The choices are currently: Handler Used by Default when TERM starts with VIP78 7800/BDS terminals and clones, Glink, other 7800 emulators glink or vip VT100 VT100 terminals and compatibles vt1 VT200 VT200 terminals and compatibles vt2. vt3 or vt4 TWS Async TWS and DKU terminals tws21 or dku7 TERM All other terminals with a suitable terminfo description Anything else The TERM environment variable might have to be set to vt220 because other UNIX/Linux applications test on the type, or have their own VT220 Terminfo file. A Glink user can still force use of the VIP7800 handler within the Host Links products: VIDEO VIP78 Host Links will switch Glink to VIP7800 on entry, and back to VTnnn mode on exit. The TERM environment variable might have to be set to myterm because the user has a special Terminfo for some UNIX/Linux application. By default Host Links will use the TERM handler, and use the myterm Terminfo to control the terminal. You can force the VT200 handler within Host Links: VIDEO VT200 62 Host Links Installation and Configuration G&R VIPGLINK - VIP78 handler in Glink mode If you have to force the VIP78 handler using the VIDEO directive, you can enable the Glink extensions with this directive, it tells the VIP78 video handler that you’re running Glink. If the TERM environment variable starts with glink then this is on by default. VIPUNIX - VIP78 handler can assume UNIX mode This directive tells the VIP78 video handler that the terminal is already in UNIX mode. For real 7800 and BDS terminals this means it is in so-called ‘Character Attribute Mode’. For Glink it means the emulator is already running in VIP7800 emulation mode so switching from VT emulation mode need not be done. If the TERM environment variable starts with glinkvip then this is on by default. Host Links Installation and Configuration 63 G&R 64 Host Links Installation and Configuration G&R Video handlers General information The Host Links video handlers are a series of compatible interfaces that allow G&R software products to communicate with any of the asynchronous terminals in general use. Handlers are available for Glink/VIP7800, DKU7102, TWS21xx, VT100 and VT200. There is also a handler that uses Terminfo to handle generic UNIX/Linux terminals. The correct handler is by default chosen based on the value of the TERM environment variable, but may also be explicitly chosen with the ‘video’ profiles directive, e.g. ‘video vt200’. A video handler runs as its own process separate from the application process. Any Host Links product using a video handler will when started attempt to contact the appropriate video handler for the user terminal. If the video handler is not yet running it is started. The two processes then communicate through shared memory and pipes. The set of screen update operations available to a product is in this way standardized, and any product that will run with one video handler will run with all of the others, giving considerable savings in development and testing, as well as a stable terminal handling environment The keyboard read and screen update functions are quite asynchronous, with priority given in the products to processing keyboard input before doing screen update. This means that menus may be avoided by typing choices in advance of the menu display and that 'paging' in data or text can be short-circuited by paging again at any point during display of a page. The screen update will terminate immediately, and the new paging command will be executed. Note that Pthru does not use a video handler. When it starts it takes control of the screen directly, handling the byte stream from the terminal itself. Host Links Installation and Configuration 65 G&R The VIP78 video handler This handler should be used for Glink as well as for Bull VIP78xx and BDS terminals or clones and emulations. The choice of VIP78 handler and behavior is best made using the TERM environment variable. A TERM variable starting with ‘vip’ selects the handler for standard terminals, and one starting with ‘glink’ selects the handler with the Glink specific features. A TERM variable of ‘glinkvip’ leaves Glink in VIP78 mode when exiting to other UNIX/Linux applications, and is recommended. A glinkvip terminfo file is supplied to improve Glink/VIP78 mode performance in such cases. Any other TERM starting with glink assumes that Glink is started in VTnnn mode, but will switch Glink to VIP78 mode while in Host Links products, and then back to VTnnn on exit. A glinkvt Terminfo file is supplied to improve Glink VTnnn performance in such cases. VIP78 handler using terminals The profiles directive ‘vipunix’ makes the handler assume the terminal is in UNIX mode, sometimes referred to as Character Attribute Mode, because attributes then follow characters rather than being set for fields. Omitting the directive makes the handler assume the terminal is in field attribute mode, which is supported by the video handler, but is not generally well supported by other UNIX/Linux applications. The profiles directive ‘colormode’ enables color support, which is by default off for VIP7800 terminals. VIP78 handler using Glink The profiles directive ‘vipglink’ selects the Glink specific features of the module. The ‘vipunix’ directive causes Glink to be left in VIP78 mode when exiting to other UNIX/Linux applications, which is now recommended. Omitting the ‘vipunix’ directive causes the video handler to switch Glink into VTnnn mode when exiting to other UNIX/Linux applications. The profiles directive ‘bwmode’ disables color support, which is by default on for Glink. 66 Host Links Installation and Configuration G&R The recommended way to log in to UNIX/Linux from a PC with Glink is now to run permanently in VIP78 emulation mode, by setting the TERM environment variable to glinkvip (usually by setting glinkvip as the Telnet terminal type response). The improved Terminfo file, glinkvip, for Glink in VIP78 mode (see below) ensures that commodity UNIX/Linux applications also function better. The TWS video handler This handler should be used for the standard UNIX/Linux terminal in the Bull SA area, the TWS21xx, which emulates the previous Questar DKU7102 terminal used with the GCOS6 range. A TERM variable starting with ‘tws21’ or ‘dku7’ selects this handler. The TWS video handler normally lets the screen itself manage the cursor display. The profiles directive ‘cursorsim’ makes the video handler simulate it instead with inverse and underline attributes. Some people find this mode more visually pleasing. The VT100 video handler This handler should be used with Digital VT100 terminals and clones and emulations of it. A TERM variable starting with ‘vt1’ selects this handler. The real VT100 family has only PF1 to PF4 function keys. Since most mainframe applications expect keys F1 to F12 with shift, as well as some other VIP and DKU specific keys, these must be defined in some way on the terminal. The VT100 handler by default uses this mapping: VT100 key Result Result after 0 KEYPAD 1 F1 SHIFT F1 KEYPAD 2 F2 SHIFT F2 KEYPAD 3 F3 SHIFT F3 KEYPAD 4 F4 SHIFT F4 KEYPAD 5 F5 SHIFT F5 Host Links Installation and Configuration 67 G&R KEYPAD 6 F6 SHIFT F6 KEYPAD 7 F7 SHIFT F7 KEYPAD 8 F8 SHIFT F8 KEYPAD 9 F9 SHIFT F9 KEYPAD , F10 SHIFT F10 KEYPAD - F11 SHIFT F11 KEYPAD . F12 SHIFT F12 KEYPAD ENTER XMIT PF1 HOME PF2 ERASE TO END OF LINE PF3 ERASE TO END OF PAGE PF4 CLEAR ‘Result after 0’ means that this is what happens if the keypad 0 key is pressed first, then the key in the left column. The interpretation of the numeric keypad can be toggled from the above to numeric using the CTRL/N key. In numeric mode the keypad may be used for keying numbers. The initial state of this interpretation can be set to numeric by using the KPNUM profile directive. The VT200 video handler This handler should be used on Digital VT200, VT300 and VT400 terminals and clones and emulations of it. A TERM variable starting with ‘vt2’, ‘vt3’ or ‘vt4’ selects this handler. The real VT200 family has 20 function keys but F1 to F5 are allocated to internal functions, and there are no shifted F-keys. Since most mainframe applications expect keys F1 to F12 with shift, as well as some other VIP and DKU specific keys, these must be defined in some way on the terminal. The VT200 handler by default uses this mapping: 68 Host Links Installation and Configuration G&R VT200 key Result Result after 0 KEYPAD 1 F1 SHIFT F1 KEYPAD 2 F2 SHIFT F2 KEYPAD 3 F3 SHIFT F3 KEYPAD 4 F4 SHIFT F4 KEYPAD 5 F5 SHIFT F5 KEYPAD 6 F6 SHIFT F6 KEYPAD 7 F7 SHIFT F7 KEYPAD 8 F8 SHIFT F8 KEYPAD 9 F9 SHIFT F9 KEYPAD , F10 SHIFT F10 KEYPAD - F11 SHIFT F11 KEYPAD . F12 SHIFT F12 KEYPAD ENTER XMIT PF1 HOME PF2 ERASE TO END OF LINE PF3 ERASE TO END OF PAGE PF4 CLEAR TAB TAB BACKTAB FINISH F4 SHIFT F4 INSERT INSERT CHARACTER INSERT LINE REMOVE DELETE CHARACTER DELETE LINE SELECT SLC PREVIOUS SCREEN PAGE UP NEXT PAGE DOWN F6 SCREEN F6 Host Links Installation and Configuration 69 G&R VT200 key Result Result after 0 F7 F7 F8 F8 F9 F9 F10 F10 F11 F11 F12 F12 F13 LF F14 V14 HELP F1 DO LF F17 RESET F18 SET ATTRIBUTE DELETE ATTRIBUTE F19 SET TABSTOP DELETE TABSTOP F20 ESCAPE INITIALIZE RESET By ‘result after 0’ is meant that this is what happens if the keypad 0 key is pressed first, then the key in the left column. The keyboard interpretation can be changed using profile directives NOKPAM and KPNUM. The NOKPAM directive turns off all interpretation. The KPNUM directive interprets the numeric keypad as numeric so that it can be used for keying numbers. There are thus four possible states for the keyboard: NOKPAM set and KPNUM not set. This gives little initial functionality, it does no VT200 keyboard mapping at all. The function keys deliver native VT200 sequences, the numeric keyboard sends the sequences associated with application mode, and these too are delivered as native VT200 sequences. The mode relies on a keyboard definition in the Host Links product to assign the native VT200 key sequences to functions in the product. The functions assigned will vary by product and are set for each product. See the Qsim, V78sim or G3270 manuals for examples of keyboard definitions. By default they all recognize the Host Links command key which is placed on F16 (DO). 70 Host Links Installation and Configuration G&R NOKPAM is set and KPNUM is set. This is just as the above, except that the numeric keypad is interpreted as numeric and can be used to key numbers. NOKPAM is not set, and KPNUM is not set. This is the default as shown in the table above. This gives maximum mapping of the keyboard into keys needed by Host Links products. NOKPAM is not set and KPNUM is set. This gives the mapping in the table above, except that the numeric keypad is used to enter numbers. The CTRL/N key can be used to toggle between the modes described above. For each press of CTRL/N the keyboard interpretation steps to the next mode. The mode is indicated with a status message. The profiles option COLOURMODE allows the video handler to send ANSI colour sequences which are interpreted by VT340, and also many VT220 clones. The term video handler This handler must be used on any terminal not supported by any of the specialized handlers described in the previous paragraphs. A TERM variable with any value other than those mentioned previously will select this handler. This handler relies on the Terminfo description of the specific terminal. We will not try to teach you how to write Terminfo descriptions from scratch here. Below you will however find a summary of what Terminfo entry labels are used for keyboard input by the term video handler, as well as what is required to be set or not set. All the other Terminfo labels for cursor motion, screen output, attributes, graphics etc. are handled in the obvious way by the video handler. In many cases the Terminfo entries delivered with the system will work reasonably well. Some amount of tweaking is normally necessary in order to get perfect results for the keyboard handling. Terminfo label Comments gn, hc, xhp, hz, xmc Required to not be set cup, il1, dl1, clear, el, ed, sgr, sgr0 Required to be set Host Links Installation and Configuration 71 G&R 72 Terminfo label Comments kcud1 Key, Cursor down kcuu1 Key, Cursor up kcub1 Key, Cursor left kcuf1 Key, Cursor right khome Key, Cursor home kbs Key, Backspace. Comes in addition to a hardcoded default of 0x08 kf63, kext Key, ESC. If neither kext nor kf63 are defined a hard-coded default of 0x1b 0x1b is used kf58, ktab Key, Tab. Comes in addition to a hard-coded default of 0x09 kf59, krdo, kcmd Key, LF. Comes in addition to a hard-coded default of 0x0a ksf, knp Key, Page down ksr, kpp Key, Page up kf1..kf12 Key, Function key F1..F12 kf13..kf24 Key, Shifted function key F1..F12 kf21..kf32 Key, Shifted function key F1..F12. Only if kf13..kf24 isn’t defined. If neither kf13..kf24 nor kf21..kf32 are defined a hard-coded default of ESC1, ESC2, ESC3, ESC4, ESC5, ESC6, ESC7, ESC8, ESC9, ESC0, ESC q, ESC q is used kf60, khlp Key, Help. Really works the same as F1 in most applications kdch1 Key, Delete character kich1 Key, Insert character kdl1 Key, Delete line kil1 Key, Insert line kclr Key, Clear Host Links Installation and Configuration G&R Terminfo label Comments kf62, kel, kend Key, Erase to end of line or move to end of field ked Key, Erase to end of screen kf0, kext Key, Transmit kf61, kbtab, kcbt Key, Back tab krmir Key, Paste character khts Key, Tab set kctab Key, Tab clear ktbc Key, Clear all tabs kf57, kcan Key, Reset to initial state kf56, kCAN Key, Reset kf55 Key, Set attribute kf54 Key, Delete attribute After you have edited your Terminfo entry you must run it through tic, the Terminfo compiler. The exceptions are systems running Hewlett-Packard HPUX 10.x, here the command is called tic_colr. Terminfo files delivered Terminfo definitions for Glink in VIP78 and VT modes (glinkvip, glinkvt), the X11 Window System’s xterm program (xtermgar), the CDE (Common Desktop Environment) program dtterm (dttermgar) and FTP Software Inc.’s PC-TCP Telnet program (pctcpgar) are included. The Glink Terminfo definitions are not needed by Host Links when running in VIP78 mode as recommended. They are included for the benefit of those using Glink to run other UNIX/Linux applications. The xtermgar, dttermgar and pctcpgar definitions are needed in order to enable all features of Host Links when run from these respective terminal emulators. Host Links Installation and Configuration 73 G&R If any of the above applies to you then you need to compile the right Terminfo file for your operating system. The Terminfo files are all placed in the directory /usr/gar/install/terminal. Go there, then su to the super user identity, then run the command: tic xxx.ti Where xxx is aix3 on the rs6ai platform, aix4 on rs6a4, mono on spasu, old on hppux and hppu1, rcolor on 386v3, 386v4 and mipv4 and color on all the others. Additionally on the hppu1 platform run the command: tic_colr color.ti Extra setup for the X11 xterm program For Sun Solaris 2.x: cat xtermgar.res >> /usr/openwin/lib/app-defaults/XTerm For most other systems: cat xtermgar.res >> /usr/lib/X11/app-defaults/XTerm Be careful to get this command right, it appends the xtermgar.res file to the end of the existing app-defaults/XTerm file. Note the use of two > characters and that XTerm at the end is spelled with a capital X and T. Some of the keyboard mappings cannot be guessed, here's an overview of the ones that aren't intuitive: CTRL-HOME CTRL-PGDN CTRL-END CTRL-INSERT CTRL-DEL CTRL-PGUP KEYPAD + KEYPAD - Clear Erase to end of page Erase to end of field Insert line Delete line Reset Transmit LF Finally you need to know how to actually start the xterm window with our extra keyboard mappings enabled. After you have done the above, the only trick needed is to include one extra option on the xterm command line: 74 Host Links Installation and Configuration G&R -name xtermgar Extra setup for the CDE dtterm program First append the supplied X resource file to the standard Dtterm resources: cat dttermgar.res >> /usr/dt/app-defaults/C/Dtterm Be careful to get this command right, it appends the dttermgar.res file to the end of the existing app-defaults/C/Dtterm file. Note the use of two greater than (>) characters and that the directory C and file Dtterm at the end are spelled with an upper case D. Some of the keyboard mappings cannot be guessed, here's an overview of the ones that aren't intuitive: CTRL-HOME CTRL-PGDN CTRL-END CTRL-INSERT CTRL-DEL CTRL-PGUP KEYPAD + KEYPAD - Clear Erase to end of page Erase to end of field Insert line Delete line Reset Transmit LF Finally you need to know how to actually start the dtterm window with our extra keyboard mappings enabled. After you have done the above, the only trick needed is to include one extra option on the dtterm command line: -name dttermgar Extra setup for the FTP Software TN.EXE program Copy the pctcpgar.map file into the directory where the PC has its PC/TCP configuration files, typically the same directory that contains PCTCP.INI. Edit the PCTCP.INI file. In the section labeled [pctcp vt], add these two lines: Host Links Installation and Configuration 75 G&R vt220-keymap = c:\pctcp\pctcpgar.map vt220-terminal-id = pctcpgar (c:\pctcp or wherever you placed it) That's all. Now just run the TN.EXE program as usual, no extra options should be needed. 76 Host Links Installation and Configuration G&R Interactive commands The video handlers accept certain commands while in execution. The commands are given as ASCII control characters by holding down the CONTROL key on the terminal and typing a character between '@' and '_' in the US ASCII character set. The commands are as follows: CTRL/F Toggle language key. The mapping to/from the extended character set will be stepped through the available ISO substitution sets. The chosen set is displayed in line 24 of the screen. US ASCII gives no mapping. CTRL/I Horizontal tab. For terminals with no TAB key. CTRL/J Line Feed. For terminals with no LF key. CTRL/K Copy field from screen. The characters between the cursor and the next attribute change on the screen (or the end of the line) are copied. CTRL/L Redisplay the entire screen. CTRL/N Select between different function key and keypad modes in the VT100 and VT200 handlers. CTRL/P Hard copy of screen. The screen content is saved on your home directory with file name screen.sav in plain text format. CTRL/U Paste field. The field previously copied with CTRL/K is inserted as keyboard input at the cursor position. You should be at a place where it would be logical for you to type the content of the field you have copied. CTRL/Z Back tab. For terminals with no back tab key. Other CTRL sequences may be allowed through for interpretation by the product using the video handler, and in this case will be accepted or not at the application level. Host Links Installation and Configuration 77 G&R 78 Host Links Installation and Configuration G&R Character sets Limitations of the 7-bit set Data processing terminals have often only the 7-bit ASCII character set, standardized by ISO 646. This gives 128 combinations of possible characters, but the first 32 and the last are reserved as ASCII control characters. Because we need 1 character as a 'space' there are 94 possible displayable characters. In this set there are 12 characters reserved for national interpretation, marked in the following table by bold numbering. National substitutions Please note that your view of these tables will be decided by the ability of your printer or screen to represent the full character set. ISO have standardized substitution sets for several languages, and these are given in the table above. Of course all of them are used for different purposes in all languages. Host Links Installation and Configuration 79 G&R ┌────┬────────────────────────┐ │hex │ 0 1 2 3 4 5 6 7 │ ├────┼────────────────────────┤ │ 0 │null. 0 3 P 8 p │ │ 1 │ . . ! 1 A Q a q │ │ 2 │ . . " 2 B R b r │ │ 3 │etx . 1 3 C S c s │ │ 4 │ . . 2 4 D T d t │ │ 5 │ . . % 5 E U e u │ │ 6 │ . . & 6 F V f v │ │ 7 │bel . ' 7 G W g w │ │ 8 │bs . ( 8 H X h x │ │ 9 │ht . ) 9 I Y i y │ │ A │lf . * : J Z j z │ │ B │vt esc + ; K 4 k 9 │ │ C │ff . , < L 5 l 10 │ │ D │cr . - = M 6 m 11 │ │ E │so rs . > N 7 n 12 │ │ F │si us / ? O o . │ └────┴────────────────────────┘ ┌──┬───┬───────────────────┐ │ N│hex│U G G F S D N S I J│ │ r│ │S B E R F E O P T A│ ├──┼───┼───────────────────┤ │ 1│23 │# £ # £ # # # £ £ #│ │ 2│24 │$ $ $ $ $ $ $ $ $ $│ │ 3│40 │@ @ § à É @ @ § § @│ │ 4│5B │[ [ Ä ° Ä Æ Æ ¡ ° [│ │ 5│5C │\ \ Ö ç Ö Ø Ø Ñ ç ¥│ │ 6│5D │] ] Ü § Å Å Å ¿ é ]│ │ 7│5E │^ ^ ^ ^ Ü Ü ^ ^ ^ ^│ │ 8│60 │` ` ` ` é ` ` ` ù `│ │ 9│7B │{ { ä é ä æ æ ° à {│ │10│7C │| | ö ù ö ø ø ñ ò |│ │11│7D │} } ü è å å å ç è }│ │12│7E │~ ~ ß . ü ü ~ ì ¯│ └──┴───┴───────────────────┘ US GB GE FR SF American British German French Swedish DE NO SP IT JA Danish Norwegian Spanish Italian Japanese Thus the character hex 5B is an American [, French °, German Ä, and Norwegian Æ. This means that when using this character set, any exchange between countries of text containing national characters is virtually impossible. However it is possible to work in this character set within the boundaries of one country, and terminals are sold within the European countries with 'national' keyboards with the national characters allocated as explained above, and with interpretation of these characters to display the national characters on the screen. Host Links supports this mode of operation with the limitations as described, and users may continue to use the data processing character set if they wish. However for users wishing to use national characters, while retaining the international interpretation of the 7-bit set, or for users who wish to produce multilingual text, the product range offers the possibility of working with an extended character set. 80 Host Links Installation and Configuration G&R The 8-bit standard Internally the Host Links platforms use 8 bits per character, giving 256 possible combinations. The assignment of characters to the combinations is done using the direct coding representation in accordance with the ISO standard 8859/Part 1, known within Bull as the D.011 PLW (Plurilingual West) standard. This means that the characters needed for general office work may be coded as one byte for all of the following languages: Danish Faeroese German Italian Spanish Dutch Finnish Icelandic Norwegian Swedish English French Irish Portuguese Additionally, because Host Links supports the use of the line graphic characters in text, the 11-line graphic characters have been allocated a place in the character set. If this extended character set is used then text can be freely exchanged between the countries mentioned with no confusion as to interpretation of national characters. Users with word processing keyboards, or with data processing keyboards with possibilities for extension are able to key most of the national characters directly from the keyboard. Technically this is possible if the terminal has an 8-bit connection and supports the international set. For 7-bit connections some terminals e.g. the DKUs (Questar) in word processing mode and Glink can still use the 8-bit set, because the terminal sends two or three 7-bit characters corresponding to one national character (e.g. e with a grave accent) and this is interpreted by the video handler and delivered as one 8-bit character. For terminals not having this possibility the administrator may configure a language key in the user profile to transliterate national 7-bit characters to 8-bit (see the LANGKEY profile directive). Host Links Installation and Configuration 81 G&R 82 Host Links Installation and Configuration G&R Host Links character set Note that the printer on which the documentation is printed will affect your view of the following table. Because this table is to be formatted and printed the ASCII control characters have been removed, and a period substituted. Generally ASCII control characters should never be used in files to be formatted and printed. dec │ 0 1 3 4 6 8 9 1 │ 1 1 1 1 1 2 2 2 │ 6 2 8 4 0 6 1 │ 2 4 6 7 9 0 2 4 │ 2 │ 8 4 0 6 2 8 4 0 ────┼────────────────────────┼─────────────────────── hex │ 0 1 2 3 4 5 6 7 │ 8 9 A B C D E F ────┼────────────────────────┼─────────────────────── 0 │ . . 0 @ P ` p │ . ° À Ð à ð 1 │ . . ! 1 A Q a q │ . ¡ ± Á Ñ á ñ 2 │ . . " 2 B R b r │ . ¢ ² Â Ò â ò 3 │ . . # 3 C S c s │ ┌ . £ ³ Ã Ó ã ó 4 │ . . $ 4 D T d t │ . ¤ ´ Ä Ô ä ô 5 │ . . % 5 E U e u │ ┐ . ¥ µ Å Õ å õ 6 │ . . & 6 F V f v │ ─ . | ¶ Æ Ö æ ö 7 │ . . ' 7 G W g w │ ┬ . § ⋅ Ç × ç ÷ 8 │ . . ( 8 H X h x │ . ¨ È Ø è ø 9 │ . . ) 9 I Y i y │ │ . © ¹ É Ù é ù A │ . . * : J Z j z │ └ . ª º Ê Ú ê ú B │ . . + ; K [ k { │ ├ . « » Ë Û ë û C │ . . , < L \ l | │ ┘ . ┐ ¼ Ì Ü ì ü D │ . . - = M ] m } │ ┤ . ½ Í Ý í ý E │ . . . > N ^ n ~ │ ┴ . ® ¾ Î Þ î þ F │ . . / ? O o . │ ┼ . ─ ¿ Ï ß ï ÿ Host Links Installation and Configuration 83 G&R 84 Host Links Installation and Configuration G&R Using the 8-bit set 8-bit terminals (EIGHTBIT) Many terminal types have an 8-bit connection to the Host Links platform and need no mapping mechanism. They send 8-bit characters as single characters on the 8-bit connection. The video handlers support the 8-bit interface with the EIGHTBIT profile. If your terminal or terminal emulator supports the ISO 8-bit character set then you should configure for eight bit. 7-bit terminals with mapping (EXTENDED) Some terminal types (see below) have a mapping mechanism for transmitting 8-bit characters over 7-bit lines. The profile directive EXTENDED informs the video handler if the extended character set is wanted. If it is, then video handler interprets each 8-bit character from the product and sends the correct series of 7-bit characters to the screen, where they are again interpreted as a single character, and displayed. Keyboard input of 8-bit characters is mapped into a series of 7-bit characters by the terminal, and the handler interprets them as one 8-bit character. This is only supported for terminals with a mapping mechanism. Glink When running the Glink terminal emulator on a 7-bit line the gv_vip78 video handler uses a simplified SS2 mechanism to reach the full character set if EXTENDED is configured. Glink transliterates this into the PC character set to give a correct display on the PC monitor, including the line-graphic characters. Keyboard input is mapped in a similar way to the intended 8-bit character by the Glink terminal simulator, and then sent as a simple SS2 sequence to the gv_vip78 video handler. The video handler interprets the SS2 sequence as a single 8-bit character. Host Links Installation and Configuration 85 G&R The DKU7102 (TWS21xx) The Questar DKU7102 is a 7-bit terminal, but if the setup menu of the terminal is configured for a Word Processing keyboard (SW 13) then it uses the SS2 mapping mechanism and the video handler (gv_tws) may be configured to use the extended character set (EXTENDED). In this case the video handler will itself turn on the extended character set in the setup menu by command (SW 14) whenever it connects to the terminal, and interpret all SS2 (single shift 2) sequences from the terminal as being single 8-bit characters. Similarly each 8-bit character is mapped to an SS2 sequence for display on the screen. See the Questar reference manual for details. The DKU7102 in extended mode can actually display the ASCII control characters 'SOH', 'STX' etc. which is very helpful. 7-bit terminals (LANGKEY) Display of 8-bit characters Many old-style terminals are 7-bit only, and have a national keyboard and screen that interprets and displays the 7-bit ISO substitution characters as national characters. For terminals without extended character sets the following rules are used when displaying 8-bit characters: • National characters with a 7-bit equivalent in the data processing set are displayed as the 7-bit equivalent. This means that a user with an extended keyboard may send a message to a German user with a 7-bit national terminal. The 'real' national characters (e.g. Ü - hex DC) would be transliterated by the video handler to the 7-bit national characters (i.e. ] - hex 5D), but displayed 'correctly'. Of course the same message displayed on a Norwegian 7-bit national terminal would be 'incorrect' because exactly the same 7-bit characters are used to display Norwegian national characters (i.e. Å - hex 5D). • National characters with accents, but with no national equivalent are displayed without the accent. • Extended characters that do not exist in the 7-bit set (for example, the ¼ (hex BC)) are displayed as a period ".". 86 Host Links Installation and Configuration G&R Entering 8-bit characters These terminals have no way of generating 8-bit characters. The national characters on the keyboard generate the 7-bit national equivalents. However if you want to work internally in Host Links with 8-bit national characters you may use the LANGKEY profiles directive to transliterate keyboard input according to one of the national substitution sets. For example, a German user with LANGKEY GE in his profile, could type the German national characters as follows: National character US ASCII value Hex character # $ § Ä Ö Ü ^ ` ä ü ß # $ @ [ \ ] ^ ` { | } 23 24 A7 C4 D6 DC 5E 60 E4 FC DF The handler transliterates the bold characters to the correct 8-bit character, even though the terminal keyboard generated the US ASCII characters. In order to input a real 7-bit character e.g. the left square bracket '[', the user would have to dynamically toggle the language key to US ASCII using the CTRL/F command to the G&R video handler. 8-bit terminals viewing 7-bit characters Users with extended character sets EXTENDED/EIGHTBIT but working in an environment with many 7-bit terminals, and where the 7-bit terminals are not using LANGKEY in the profiles, will see the national substitution characters in the true US ASCII format. This may make text difficult to read. Default national view If much of the text you view is in your local 7-bit national character set you can use LANGKEY in your own profile. The result of this is that the video handler shows both the 8 bit national characters and the 7-bit equivalents as extended characters, making it possible to read text written by '7-bit users'. Host Links Installation and Configuration 87 G&R Toggle to national view (CTRL/F) If you occasionally view text that is in some 7-bit national set then you can temporarily toggle your language key to the correct 7-bit set using the video support for CTRL/F language selection. Each time you type CTRL/F the video handler will step the character set interpretation to the next language. If you then redisplay the text on your screen it will be shown with the national interpretation of the 7-bit national characters. Data entry while viewing 7-bit While in this mode keyboard input of 7-bit characters from the 8-bit terminal would still be stored internally as 7-bit characters, but would be displayed as national equivalents. 88 Host Links Installation and Configuration G&R Glicense & license keys All G&R products require a license key to run. If you are a G&R distributor you need a license key from G&R. If you are a customer you should have received the license keys from your distributor together with the software. The licenses are stored in text format in a file named licenses. If licenses is delivered with the product files, it is merged with any existing licenses in the configuration directory when you run the install procedure. UNIX/Linux /usr/gar/config/licenses Windows server C:\gar\config\licenses Glicense The Glicense program is included in every software delivery, and it can be used even though no license key is installed. This allows you to create or modify your own licenses from a license card. You must execute Glicense from a user-id that has permission to write in the configuration directory (i.e. the Host Links administration user gar for Host Links). When executed with no parameters, Glicense will check for an existing licenses file. If found it will skip directly to the command dialog, but if there is no license then it will prompt you for distributor name, customer name and the main license key. Be careful to type the names and the key exactly as given to you by your distributor. It is important that you respect case and spaces between words. To tell Glicense explicitly where the license file is, or where it should be written, supply the full path as an option. For example: glicense /usr/gar/config/licenses Enter the license information, text and keys, exactly as specified on the supplied license card. Host Links Installation and Configuration 89 G&R Once the first time installation has been done, you can simply run Glicense without any options and it will automatically find the licenses file. When started Glicense gives you the following prompt: Enter command or '?': If you enter '?' a list of the available commands is returned: Use these commands to define/modify and save the licenses file. A = Add Add a new product to the license file. D = Delete Delete a product from the license file. R = Read Read in a new license file. M = Merge Merge in license keys from a license file W = Write Save the license file. P = Print Display a list of configured products. N = New Create a new license file. H = Hardware Change the hardware platform X = eXpiration Define an expiration date for all products. V = Version Set new version for all products Q = Quit Quit the Glicense program. ENTER The ENTER key quits Glicense If you enter the Print command, the result will be something like this: Enter command or '?': p Distributor: Bull A/S Customer: Arbeidsdirektoratet Product: Basic Product: Gline Product: Ggate Product: Gspool Product: Qsim 90 Host Links Installation and Configuration G&R License keys Below you find a complete list of all Host Links and Glink for Java license keys: License key Products that require this key basic All products. ggate Ggate. gspool Gspool. guft GUFT server. Guftc GUFT client. gproxy Gproxy. qsim Qsim. v78sim V78sim. g3270 G3270. g5250 G5250. pthru Pthru. sdkglapi GlAPI SDK. Glapi GlAPI run-time. Tnvip Enable Ggate TNVIP support ssl Enables SSL support Marben Marben OSI Stack for Windows NT 4 Marben2K Marben OSI Stack for Windows 2000 MarbenXP Marben OSI Stack for Windows XP Marben03 Marben OSI Stack for Windows 2003 Gweb Gweb Professional Edition All terminal emulations Gljopen Glink for Java Open (VTnnn/ANSI/Minitel). Gljpro Glink for Java Professional Edition. Gljent Glink for Java Enterprise Edition. Host Links Installation and Configuration 91 G&R License key Products that require this key Gljall Glink for Java All terminal emulations. Gljsa Glink for Java Standalone (No configuration server). Gljsrv Glink for Java Server (Configuration and License). Gljcnx Glink for Java Gconnect (J2EE connector) Gljdsa Glink for Java DGA (native DSA comms stack) Gljggen Glink for Java Gargen 92 Host Links Installation and Configuration G&R Sample dsa.cfg The following file is the sample delivered with Host Links for UNIX/Linux, and is found in /usr/gar/config/dsa.cfg The hash characters denote comments, and would be removed from the configuration directives after these have been edited to reflect your site and remote nodes. # # # # # # # # # # # # # # # This file configures the gl_diws and gl_dsa line modules. # # # # # # # # Some examples of usage of the first four directives follow below. Please refer to the Host Links Gline manual for details. Suppose your local DSA node name is is2c with DSA address 54:97. You want to connect with remote DSA nodes is2b, en3e, en3f and en40. is2b and en3e are reachable over WAN through the same front-end and you need gl_dsa DSA200 connections to en3e. en3f is also reachable over WAN, but through another front-end. Finally en40 is reachable over LAN. The Gline configuration compiler, glcc, must be run to activate any changes done here. The following directives may be used: sc - Session control rsc - Remote session control ts - Transport station tp - Transport provider coname - Connection name params - Parameters pool - Parameter pool costrict - Connection name strictness restrict - Parameter restrictions filter - Access filter # For machines with the Bull OSI XTI interface # and Sun Solaris 2.x platforms you need something like: # # # # # # sc is2c -addr 54:97 rsc is2b -ts fep1_wan rsc en3e -addr 54:62 -ts fep1_wan rsc en3f -ts fep2_wan rsc en40 -ts fepl_lan ts fep1_wan -class 2 -ns 123456 -tp wan Host Links Installation and Configuration 93 G&R # # # # ts ts tp tp fep2_wan -class 2 -ns 888888 -tp wan fepl_lan -class 4 -ns 080011223344 -tp lan wan -attach 123455 lan -attach 08001123355 # # # # # # # # # # For the SCO Unix, SVr4 on Intel and Hewlett-Packard HP-UX platforms you need something like: sc is2c -addr 54:97 rsc is2b -ts fep1_wan rsc en3e -addr 54:62 -ts fep1_wan rsc en3f -ts fep2_wan rsc en40 -ts fepl_lan ts fep1_wan -class 2 -ns 123456 ts fep2_wan -class 2 -ns 888888 ts fepl_lan -class 4 -ns 080011223344 # # # # # # # An RFC1006 example of usage of the first six directives follows Please refer to the Host Links Gline documentation for details. Suppose your local DSA RFC1006 node name is 'mypc'. You want to connect with remote DSA RFC1006 node name 'ph21' which has IP address 1.2.3.4 In addition, you want to use a connection pool named 'tp8ws001co' which references a pool of mailbox extensions named 'lidpool'. # # # # # # # # # # # # For the remote DSA RFC1006 node ph21, we'll give a symbolic remote session control id of 'ph21_rfc'. The gline parameter to access this system would be "-li dsa -dn ph21_rfc". The "tp rfc -who gar" indicates that the transport is G&R's rfc1006 interface sc mypc rsc ph21_rfc -scid ph21 -ts ph21_rfc ts ph21_rfc -class 0 -ns 1.2.3.4 -tp rfc tp rfc -who gar 94 Host Links Installation and Configuration G&R # # # # # # # # # # # # # # If you want to configure gline parameters centrally in the dsa.cfg file, this is done with the 'coname' directive. See the Gline manual for more information about configuring 'coname's and setting up filters to control access to them. In Glink you can select a coname entry in dsa.cfg by saving a 'DIWS/DSA host configuration' with the coname ('Connection name'). In Host Links a coname is selected with the '-co' parameter. By the use of Glink 'Connection name': 'tp8ws2' you will get the parameters defined in 'coname tp8ws2' below: coname tp8ws2 -desc "TP8 workstation 2" -dn ph21_rfc -da tpws2mbx -hm dps8 -dx mg01 # Another example of coname. This time getting the LID from a pool. # # coname tp8ws2 -desc "TP8 workstation 2" -pool lidpool # -dn ph21_rfc -da tpws2mbx -hm dps8 # # pool lidpool # -dx mg01 # -dx mg02 # -dx mg03 # -dx mg04 # # # # # # # # # coname's are also used for configuration of merged print, where data from a separate host session are merged into the terminal session, marked as print data. Glink or the Host Links emulation program enable this functionality through the use of the gline parameter '-pco ' where 'coname ' must be configured in dsa.cfg. If the gline parameter '-pcn' is used, the separate print session will be established by the line handler. The default is to wait for the host to establish the session. # # # # # # Merged print from TWriter on GCOS7. Gline parameter '-pco a2_print' The printer coname must wait for a connect from Twriter to printer mailbox mypctw coname a2_print -desc "Twriter print to MYPCTW" -ln -mn mypctw -tm a2 # Merged print from TP. Gline parameters '-pco rop1 -pcn' # The printer coname must connect to TP8 (mailbox mytp8) with LID rop1 # # coname rop1 # -da mytp8 -dx rop1 -dn ph24_lan Host Links Installation and Configuration 95 G&R 96 Host Links Installation and Configuration G&R Platform specific requirements The Host Links products are currently implemented on several different UNIX platforms, on Linux and on Windows. This chapter explains in more detail which platform(s) the different versions support. Also included for each platform are requirements for hardware, operating system, OSI stack, patches and disk space, as well as other useful notes. 386l2 (Linux) This version supports Linux distributions based on Linux kernel 2.2 and above. OSI software and hardware for Linux There is currently no OSI stack available for Linux. 386so (Solaris) This version supports implementations of System V Release 4 running on a multitude of generic and vendor specific Intel platforms. We have qualified Sun Solaris, but it may also run on other Intel versions of System VR4. OSI software and hardware for Solaris For DSA connections over LAN and X.25 we have qualified SunLink OSI release 8.1.1 with the latest OSI patch. Any LAN card supported by Solaris should work. Connections via X.25 also need SunLink X.25 release 9.1 with latest patch. Solaris release 7 needs Sunlink 9.2 with the latest patch. Any X.25 card supported by SunLink X.25 should work. Host Links Installation and Configuration 97 G&R The real memory consumption is currently not known. The SunLink OSI stack supports a maximum of 1024 transport connections. hpp11 (HP-UX Rel. 11) This version supports Hewlett-Packard HP-UX release 10.11 on all HP platforms running this OS release. There is currently no OSI support for this platform, use rfc1006 communications instead. ppca5 (AIX 5.x) This version supports AIX release 5.1/5.2 for PowerPC running on Bull Escala machines. rs6a4 (AIX rel. 4.x DPX20, RS6000) This version supports AIX release 4.3 (rs6a4) and above running on Bull DPX/20, Escala and Estrella and IBM RS/6000 machines. For DSA connections via both LAN and X.25 you need the versions of Bull CNHG069-CNHG073/OSI_LOW-MAX3 and CNHG071/XTI-API that are supported by your AIX release. Possibly these products may be bundled with other Bull products you have already installed, this can be checked with the lslpp -l utility. All LAN and X.25 cards supported by the OSI_LOW software should work. OSI releases prior to 02.02.08 support a maximum of 1024 connections. Newer releases support up to 2048 connections. The real memory consumption is currently not known. In order to use the X.25 line handler in Gline the OSI_LOW software also has to be installed. 98 Host Links Installation and Configuration G&R spaso (Solaris 2.6 SPARC) This version supports Sun Solaris 2.6/2.7/2.8 on Sun SPARC based machines or clones thereof. For DSA connections via both LAN and X.25 you need SunLink OSI release 8.1.1. Any LAN card supported by Solaris should work. Connections via X.25 also need SunLink X.25 release 9.1. Any X.25 card supported by SunLink X.25 should work. For speeds up to 19200 bits/sec the standard serial ports may also be used. The real memory consumption is currently not known. The SunLink OSI stack supports a maximum of 1024 transport connections. In order to use the X.25 line handler in Gline the SunLink X.25 software also has to be installed. Host Links Installation and Configuration 99 Installing and configuring OSI stacks Bull DPX/20 - IBM RS6000, AIX 4.1.x You should note that Bull has removed the OSI session layer access method in this generation of their OSI stack. Host Links users migrating to this release of AIX and OSI stack must at the same time migrate to the more modern XTI interface. G&R Support for the OSI-session access method (MAD) available in the earlier Bull OSI-stacks is discontinued. All new functionality requires XTI. Install Bull software Start smit and walk through the following menus: Software Installation and Maintenance Install / Update Software Install Bundles of Software (Easy Install) Install/Update Selectable Software (Custom Install) Depending on system (Estrella, DPX/20 or Escala) you will now install the OSI software from the installation media (CD-ROM or tape) labeled ‘Bull OSI COM ver. 2.x.x on AIX 4.1.x’ as a bundle of software or by selecting the appropriate modules. Make sure that you end up installing at least: OSI-LOW XTI-API Layers 1-4 Host Links Installation and Configuration 101 X.25 setup Install and configure the software according to Bull DPX/20 documentation. We cannot help you here, as the correct parameters will vary from country to country and site to site. Normally the local Bull technicians know all about this. Anyway, walk through the following smit menus: Devices Communication At this point you select the menu item that correspond to the installed adapter: X.25 CoProcessor/2 or Multiport/2 Adapter or Hispeed WAN Comm Adapter Depending on the adapter you navigate through the following set of menus. Adapter Manage Device Drivers for X.25 CoProcessor/2 or Multiport/2 Adapters Manage X.25 CoProcessor/2 Device Driver at this point you should select: Add a Device Driver if the device driver for your X.25 adapter has not been installed before. If it is already installed, select: Change / Show Characteristics of a Device Driver or if you have a Hispeed WAN Comm adapter, you should first do an easy config through the menu item: Easy Config with Bundle 102 Host Links Installation and Configuration if the device driver for your X.25 adapter has not been installed before. If it is already installed, select: Change / Show Characteristics of an Hispeed WAN Comm Adapter to end up in the following menu: Change/Show Change/Show Change/Show Change/Show Change/Show Change/Show Network Parameters Packet Parameters Frame Parameters Default for Permanent Virtual Circuits a Specific Permanent Virtual Circuit General Parameters (PVC) (PVC) At this level, walk through the menus to adjust the parameters to the X.25 network. When the X.25 logical group number in the network is different from 0 (in Norway, DATAPAK uses logical group no. 4), the trick is to adjust the parameter for: "Lowest logical channel number for a two-way SVC". In the Norwegian DATAPAK it should be: Lowest logical channel number for a two-way SVC [1024] This is because decimal 1024 is equal to hexadecimal 400, and the first VC used is 0 on logical group 4. OSI transport and session setup Start smit and walk through the following menus: Communications Applications and Services OSI Networking OSI Configuration If you do not already have a configuration, you have to create one. If you have a configuration, jump to the "Modify a configuration" section. Host Links Installation and Configuration 103 Create a configuration To create a new configuration, you may create a default, minimum configuration called OSIdefault through the menu item: Minimum Configuration or you simply select the following menu and give the configuration a name. If this is your first configuration it is automatically selected. If not you have to select it as well. Configuration Management Create a configuration Select a configuration Return to the menu OSI Configuration Modify a configuration Select adapter for OSI communication First you have to select on which communication adapters you want to run OSI communication. You can select several adapters, both LAN and X.25 adapters. Do this by the selecting the following smit menus: Configuration Definition Communications adapter access Add communications adapters At this level you ask for a list of available adapters by pressing F4, and select adapter(s). Activation of OSI stack You are now ready activate the actual OSI services and configure your maximum number of OSI connections. Note that in OSI Stack C the XTI-API and OSI lower layers (1-4), which are the Host Links prerequisites, are automatically generated and loaded when the configuration is loaded. 104 Host Links Installation and Configuration Important: Some versions of the Bull OSI stack set the value of ‘COTP LAN local retransmission time (T1)’ to 3000 ms. This is too low. You must increase it to 10000 ms. The error symptom if this isn’t done is that idle sessions are aborted with a transport disconnect error code of 04010430. It is possible to configure up to 2.048 simultaneous OSI connections, and this is done by the following smit menus, by changing the default 64 in both lines. If you are accessing two different front-ends then the total number of sessions needed would be in the ‘simultaneous’ line, and the largest number to a single Datanet would be in the ‘multiplexed’ line: Configuration of OSI Layers Max. no. of simultaneous COTP connections Max. no. of OSI COTP connec. multiplexed on a VC. Type of function assumed on system [64] [64] ES Note that Host Links does not use the Bull-specific XTI configuration files that can be managed through the smit system. No XTI configuration is necessary at this point. See the sample file in the section entitled Sample dsa.cfg on page 89. Please refer to the G&R/Gline manual for more details and examples. Loading (and generation) of the new OSI configuration Before loading the newly generated OSI configuration, you may have to unload your old configuration - currently running. This is done by selecting: Unload current loaded configuration Finally you load the new OSI configuration by selecting: Load the last selected configuration Host Links uses the dsa.cfg file for all local DSA and OSI configuration. Note that Host Links does not use the XTI configuration files, /etc/xtihosts and /etc/xtiservices, that are configurable through the XTI menu in smit. We chose to use dsa.cfg for these configuration purposes as it has a more intuitive format, and it is common to all UNIX/Linux systems supported by Host Links. See the sample file in the section entitled Sample dsa.cfg on page 89. Please refer to the G&R/Gline manual for more details and examples. Host Links Installation and Configuration 105 If you're not sure which X.25 or LAN address to use, use the osiadapterinfo command to list the adapters configured for OSI communication. Troubleshooting Learn how to use the xdmanage, xdmonitor and OSI protocol analyzer programs. They provide very good traces and are invaluable if you don't have an external line monitor like a Sniffer. You will also find the new set of trace tools available from the following smit menu very useful: Communications Applications and Services OSI Networking OSI Diagnosis Interactive Tool-Kit OSI Stack Information OSI API Trace Management OSI Layers Trace Management OSI Protocol Analyzer OSI Trace Save Without Analysis osisnapshot -dm will display OSI memory status. osiconf -d configname will display the configuration named in the command, and tell you if it is the currently selected and last generated configuration. It also tells you on which adapters XTI is defined, the number of connections and the timers configured. osiinfo will display OSI stack information. pmaderror may also be a useful command when you're not able to connect to remote systems or abnormally lose your connection. 106 Host Links Installation and Configuration Sun Solaris 2.x OSI stack X.25 setup Install and configure the software according to Sun documentation. We cannot help you here, as the correct parameters will vary from country to country and site to site. One thing we have found is that Bull X.25 software often runs into problems if the X.25 call request sent by the Sun is too 'fancy'. We have found that the results are best if we run as described below. As root, start the /opt/SUNWconn/bin/x25tool program. Define/Modify interfaces X.25 links Set Link type to WAN (1980) Create/Modify configuration files X.25 Working Facilities Set Allow extended call packets to off File Save Working Another thing worth mentioning is that there appears to be a bug in the Sun X.25 software: if you stop it without rebooting the machine, it does funny things like killing all running processes! It seems to be safest to always reboot after an X.25 configuration change. But try without first, it might work for you, and constant rebooting is no fun. Host Links Installation and Configuration 107 OSI over X.25 setup As root, start the /opt/SUNWconn/bin/ositool program. Stack Manager Configuration Devices Add X.25 device Set the SNPA address to match your X.25 address. Application Selectors Transport over CONS Set NULL PID if OSI on. Set Max. PDU Size greater or equal to the TPDU size you plan to use in dsa.cfg. This value will be the upper limit for TPDU size selection in dsa.cfg. The default is 512, and selectable values are 128, 256, 512, 1024, 2048, 4096 and 8192. Resources Set the number of contexts and channels for High Interface, Transport over CONS, CONS and Low Interface to reflect the maximum number of connections. The default is 256 contexts and channels and the maximum is 1024. Consult the SunLink OSI documentation for more information on how to assign context and channel values. Network Layer Addresses Select the NSAP family: free-form Select Type: CONS If your X.25 address has an even number of digits, type in:36 followed by the X.25 address. If your X.25 address has an odd number of digits, type in:360 followed by the X.25 address. Route Manager Category/Prefix Routes Select NSAP Prefix: 360 Select X.25 Service Set Addressing Mode to CONS-80 Set X.25 Link Type to 1980 Do the same for the 36, 521 and 52 NSAP prefixes. 108 Host Links Installation and Configuration There is a bug in the ositool program so that it sometimes displays CONS-80/1980 for the 36, 521 and 52 NSAP prefixes, even when it in reality is still set to 1988. You must go through and change all of them as above. Save Command Restart osinetd Quit ositool OSI over LAN setup As root, start the /opt/SUNWconn/bin/ositool program. Stack Manager Configuration Devices Select the DLPI device. Set the LSAP to 20. Application Selectors Transport & CLNS Set Max PDU Size greater or equal to the tpdusize you plan to use in dsa.cfg. This value will be the upper limit for tpdusize selection in dsa.cfg. The default is 512, and selectable values are 128, 256, 512, 1024, 2048, 4096 and 8192. Resources Set the number of contexts and channels for High Interface, Transport & CLNP and Low Interface to reflect the maximum number of connections. The default is 256 contexts and channels and the maximum is 1024. Consult the SunLink OSI documentation for more information on how to assign context and channel values. ES-IS Configuration Select the LLC device. Set the Protocol Subset to Null Protocol If the Default isn't set to point to the LLC device, change it so it does. Host Links Installation and Configuration 109 NOTE: There is a bug in the ositool program so that it sometimes loses this default setting, even if you haven't been in that part of the program at all! Always go into this menu when you run ositool, and change the default to point to the LLC device if it doesn't already. If you don't get OSI over LAN to work, always double-check this. Network Layer Addresses Select the NSAP family: free-form Select Type: CLNP Type in the machine's LAN address in hex format. Save Command Restart osinetd Quit ositool dsa.cfg configuration See the sample file in the section entitled Sample dsa.cfg on page 89. Please refer to the G&R/Gline manual for more details and examples. dsa.cfg changes for DSA over X.25 Add the line: tp wan -attach xxxxxx Replaces the xxxxxx with the local network address as specified in the Sun OSI config. Then point the TS records needing wan access here. 110 Host Links Installation and Configuration dsa.cfg changes for DSA over LAN Add the line: tp lan -attach xxxxxxxx Replace the xxxxxx above with the LAN address of the Sun machine as specified in the Sun OSI config. Then point the TS records needing LAN access here. Troubleshooting Learn how to use the x25trace and osi_trace programs. Both provide very good traces and are invaluable if you don't have an external line monitor like a Sniffer. Double-check that you haven't stumbled into the ositool bugs that are mentioned above. Host Links Installation and Configuration 111 HP HP-UX OSI stack Install HP software Install X.25/9000, Streams/9000 and OTS/9000 according to the instructions given in their respective HP9000 Installation and Administration guides. This implies that you should install any link product (i.e. X.25/9000 and LAN/9000) and Streams/9000 before installing OTS/9000. Note that in HP-UX 10.x the Streams software is integrated into the basic operating system and need not be separately installed. X.25 setup After you have installed the X.25/9000 hardware and loaded the X.25/9000 software with update, log in as root and do the following: At the HP-UX prompt, type: sam At the SAM Main window, highlight Networking/Communications and activate the OPEN button. At the Networking/Communications window, highlight Network Interface Cards nd activate the OPEN button. Highlight the X.25 card that you are configuring from the displayed list Choose Configure from the Actions menu and follow the 5-step menu to complete the following 5 tasks: 112 Host Links Installation and Configuration Configure X.25 address Card Type, Card Name and H/W Path are displayed and you are asked to enter: Configuration Filename: SAM suggests a name based on the device file, i.e. /etc/x25/x25config_0 for card name x25_0d. Normally you should accept this suggestion. X.25 address: Enter the X.25 address assigned by the network provider. Programmatic Access Name: Enter a name to be used for Level 3 programmatic access. Network Carrier Type: Select the network type that corresponds to the provided X.25 network. Configure Virtual Circuits Configure the number of Permanent, Switched (inbound), Switched (two-way) and Switched (outbound) VCs provided/subscribed to, and assign value(s) for first logical VC. Normally you would configure only the number of two-way VC's and the starting logical two-way VC. Configure Internet address It is not necessary to configure anything in this menu to run OTS. Verify Level 3 values Configure these values according to your X.25 subscription. The defaults are normally OK, but should be verified. Verify Level 2 values Configure these values according to your X.25 subscription. The defaults are normally OK, but should be verified. Check your X.25/9000 configuration by running x25stat/x25server or padem. Host Links Installation and Configuration 113 OSI transport and session setup Before starting the OTS configuration, you should verify that the link layers (X.25/9000 and/or LAN/9000) have been installed and configured properly, and that Streams/9000 and OTS/9000 have been installed without any error. If you are installing OTS to run over the LAN link product verify that the LAN product is configured to run with the IEEE protocol enabled. The following command will show you: grep lanconfig /etc/netlinkrc The output should look like the following for each interface you plan to install OTS over: lanconfig ether ieee where is the LAN interface name (i.e. lan0, lan1, etc.). Use an editor to add 'ieee' to the lanconfig line(s) in the /etc/netlinkrc file and reboot the system (/etc/reboot). OTS configuration involves definition of local sub-networks, remote destinations and finally a few manual modifications in a couple of files if you are installing OTS over a LAN interface. Start the configuration by running the osiadmin program. This program calls up the osiconf program to do the OTS configuration tasks. When configuration is complete, you return to osiadmin. Highlight Configure OTS and press SELECT ITEM or RETURN. Select the configuration mode (or accept the defaults shown) and press DONE. Under Subnetwork Configuration, select ADD in the CLNS over 802.3 section if you are going to connect to mainframe systems over LAN and/or select ADD in the CONS over X.25 if you are going to connect to mainframe systems via X.25 network and press SELECT ITEM. 114 Host Links Installation and Configuration Add CLNS over 802.3 Enter the following parameters in this sub-network form for each LAN interface you plan to use for Host Links. Subnetwork name: Enter a symbolic name that is meaningful to you (i.e. lan). It will be used later when you configure remote destinations. Local network address (NSAP): Enter the LAN address of your LAN interface in this field. Device interface name: Enter the device interface name in this field. It is not necessarily the same as the device file name. Typically it will be lanx, where x should be substituted with the logical unit number or select code. To view existing LAN card interface names, you may use the lanscan utility. CLNP subset: Select the Null subset by entering 0 in this field. Press PERFORM TASK when you have filled in all parameters. Host Links Installation and Configuration 115 Add CONS over X.25 Enter the following parameters in this sub-network form for each X.25 card you plan to use for Host Links. Subnetwork name: Enter a symbolic name that is meaningful to you (i.e. x25). It will be used later when you configure remote destinations. Local network address (NSAP): Enter the X.25 address assigned to you by your network provider in this field. If your X.25 address is not an even number of digits, add an upper case F at the end of the address. Subnetwork standard(s) allowed: Enter N in the ISO 8878 field, Y in the X.25 1980 field and N in the X.25 1984 and X.25 1988 fields. Subaddress/X.25 programmatic access: You must enter one pair, so use the 2 last digits in your X.25 address together with the name defined for X.25 programmatic access during X.25 configuration. Press PERFORM TASK when you have filled in all parameters. 116 Host Links Installation and Configuration Add destination systems. For each of the remote mainframes with which you are going to communicate fill in the Add Destination System form and press PERFORM TASK. If you reach all your mainframes through your local Datanet you only have to configure that Datanet in this form. Network address (NSAP): Enter the full X.25 or LAN address of the remote system. If your X.25 address is not an even number of digits, add a capital F at the end of the address. Physical address (IEEE MAC or X.121): Enter the full X.25 or LAN address of the remote system. Outgoing subnetwork name: Enter one of the local sub-network names you created during sub-network definition. End System, Intermediate System or Both?: Enter 0 for End system in this field. Request reverse charge?: You should probably configure 0 for no reverse charging in this field. Consult your network administrator and communication partner if you are not sure. Your configuration of destinations will end up in the ots_dests file that can be found in the: /etc/opt/ots/conf directory Host Links Installation and Configuration 117 Edit ots_parms and ots_subnets files These files can be found in the /etc/opt/ots/conf directory If you have configured OTS over X.25, edit ots_parms. You should set tpcons_null_pid 0 If you have configured OTS over LAN, edit both ots_parms and ots_subnets files. In ots_parms you should set tpclns_propose_ext_fmt 0 In ots_subnets you should set snet_lsap 20 in every OTS sub-net you have configured over LAN. When the configuration is completed, select Start OTS to start OTS for the first time. 118 Host Links Installation and Configuration ots_subnets Example subnet file ots_subnets: snet_clns_8023 snet_local_net_address snet_if_name snet_clnp_subset snet_checksum_on snet_esis snet_esis_record_esh snet_ish_ctimer snet_esh_ctimer snet_rci_hold_timer snet_esh_checksum_on snet_esis_reverse_path snet_max_es_entries snet_max_is_entries snet_all_es_addr snet_all_is_addr snet_lsap lan 02608C200441 lan0 0 0 1 1 60 60 30 0 0 250 15 09002B000004 09002B000005 20 snet_cons_x25 snet_local_net_address snet_allow_iso8878 snet_allow_x25_1980 snet_allow_x25_1984 snet_allow_x25_1988 snet_pgm_access snet_x25_subaddress snet_allow_fc_negotiation snet_allow_fast_select snet_allow_tc_negotiation snet_bind_by_pid x25 130355 0 1 0 0 x25 NULL 1 1 1 0 Host Links Installation and Configuration 119 ots_dests Example destination file ots_dests: dest_net_address dest_phys_address dest_out_subnet dest_esis dest_reverse_charge_req dest_iso8878 dest_x25_1980 dest_x25_1984 dest_x25_1988 dest_fc_negotiation dest_fast_select dest_tc_negotiation 130366 130366 x25 0 0 1 1 1 1 0 0 0 dest_net_address dest_phys_address dest_out_subnet dest_esis dest_reverse_charge_req dest_iso8878 dest_x25_1980 dest_x25_1984 dest_x25_1988 dest_fc_negotiation dest_fast_select dest_tc_negotiation 02608C2D8023 02608C2D8023 lan 0 0 1 1 1 1 0 0 0 dest_net_address dest_phys_address dest_out_subnet dest_esis dest_reverse_charge_req dest_iso8878 dest_x25_1980 dest_x25_1984 dest_x25_1988 dest_fc_negotiation dest_fast_select dest_tc_negotiation 130399 130399 x25 0 0 1 1 1 1 0 0 0 120 Host Links Installation and Configuration ots_parms Example osi parameters file ots_parms: #----------------------------------# | value | #----------------------------------- minimum / maximum / factory/ default #----------------------------------# Session #----------------------------------ses_tp_con_reuse_timer_init 120 # ses_tp_con_reuse_timer_resp 1200 # ses_disc_abort_timer 180 # ses_tsdu_q 8 # #----------------------------------# Session Flags 1=on(true) #----------------------------------ses_reuse_tp_con 1 # 30 30 30 1200 1200 600 120 1200 180 4 10 8 0=off(false) 0 1 1 # # # # # # # # # 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 #-----------------------------------# Transport Over CONS #-----------------------------------tpcons_max_tpdu_size 2048 # tpcons_window_size_tpdus 5 # tpcons_max_con_mux_in 10 # tpcons_max_con_mux_out 5 # 128 1 1 1 8192 15 64 20 2048 5 10 5 30 30 30 30 10 30 1 120 480 60 120 110 120 19 60 240 30 60 20 30 12 ses_fu_type_data ses_fu_err_report ses_fu_capability_data ses_fu_activity ses_fu_minor_sync ses_fu_expedited_data ses_fu_full_duplex ses_fu_half_duplex ses_ssap_id_in_ac tpcons_ts1_ts2_timer tpcons_long_con_timer tpcons_short_con_timer tpcons_tp3_ttr_timer tpcons_tp3_ttr_incr tpcons_tp4_retrans_timer tpcons_tp4_num_retrans 1 1 1 1 1 1 1 1 0 60 240 30 60 20 30 12 # # # # # # # #-----------------------------------# Transport Over CONS Flags 1=on(true) #-----------------------------------tpcons_tp0_only 0 # tpcons_pref_mux_class 2 # tpcons_tp2_flow_control 1 # tpcons_mux_net_cons 1 # Host Links Installation and Configuration 0=off(false) 0 2 0 0 1 4 1 1 0 2 1 1 121 tpcons_dr_on_proto_err tpcons_dr_er_on_proto_err tpcons_sap_id_in_cc tpcons_null_pid tpcons_network_reset tpcons_suppress_expedited tpcons_tp4_chksum tpcons_encode_priority 0 0 0 1 0 0 0 0 # # # # # # # # 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 #----------------------------------# Transport Over CLNS #----------------------------------tpclns_max_tpdu_size 1024 tpclns_window_size_tpdus 3 tpclns_retrans_timer 6 tpclns_num_retrans 12 tpclns_window_timer 50 tpclns_ack_timer 1 tpclns_send_tpdu_q 10 # # # # # # # 128 1 8192 15 4096 3 tpclns_window_size_tind # 1 5 #---------------------------------# Transport Over CLNS Flags 1=on(true) #---------------------------------tpclns_suppress_ack 0 # tpclns_ignore_ack_timer 0 # tpclns_chksum_spurious_resp 0 # tpclns_dr_on_proto_err 0 # tpclns_ignore_chksum 0 # tpclns_propose_chksum 0 # tpclns_propose_ext_fmt 0 # # multiple tpdus per end-unit data request. tpclns_multi_tpdu_per_nudtrq 1 # tpclns_encode_priority 0 # #---------------------------------# CLNS #----------------------------------clns_lifetime_parm 50 # clns_max_tpdus_reassemble clns_cntl_blk_alloc_quantum #clns_net_entity_title 50 20 1 0 1 1 1 19 100 100 20 120 20 12 50 1 10 6 5 0=off(false) 0 0 0 0 0 0 0 1 1 1 1 1 1 1 0 0 0 0 0 0 1 0 0 1 1 1 0 1 255 50 # # 10 20 1000 1000 50 20 # Hexadecimal number (optional) #----------------------------------# CONS #----------------------------------cons_max_nsdu_size 2048 cons_max_route_entries 430 cons_con_timer 300 cons_sndcp_con_timer 250 cons_sndcp_disc_timer 200 cons_x25_packet_size 128 # # # # # # 256 0 0 0 0 16 4096 2550 600 300 300 4096 2048 430 300 250 200 128 Troubleshooting Learn how to use the osidiag and nettl programs. They may provide useful traces that help you to investigate communication problems. 122 Host Links Installation and Configuration 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 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 Host Links Installation and Configuration 123 124 Host Links Installation and Configuration 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 Host Links Installation and Configuration 125 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 126 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 Host Links Installation and Configuration 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. Host Links Installation and Configuration 127 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 128 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 Host Links Installation and Configuration 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. Host Links Installation and Configuration 129 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 130 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. Host Links Installation and Configuration 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. Host Links Installation and Configuration 131 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 132 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. Host Links Installation and Configuration 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. Host Links Installation and Configuration 133 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 134 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. Host Links Installation and Configuration 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. Host Links Installation and Configuration 135 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 136 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. Host Links Installation and Configuration 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 Host Links Installation and Configuration Description 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. 137 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 138 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. Host Links Installation and Configuration 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 Host Links Installation and Configuration 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. 139

Embed!

Host Links Installation And Configuration - Gar.no

---