Specifications

ManualsBrandsEicon Networks ManualsAdapterCX1

pcMAINFRAME



and Across the Boards



Communications Device Drivers

cfSOFTWARE Confidential



2000

Summary of content (232 pages)

PAGE 1
pcMAINFRAME and Across the Boards Communications Device Drivers cfSOFTWARE Confidential  2000
PAGE 3
Across the Boards Communications Device Drivers Table of Contents Page i Table of Contents Introduction .........................................................................................................................1 Section 1 - Device Driver List.............................................................................................3 1.1 pcMAINFRAME 3.x Device Codes.........................................................................................................
PAGE 4
Across the Boards Communications Device Drivers Table of Contents Page ii 4.13 4.14 4.15 4.16 4.17 4.19 4.20 4.21 4.22 4.23 4.24 4.25 4.25a 4.25b 4.25c 4.25d 4.25e 4.25f 4.26 4.27 4.28 4.29 4.30 4.31 4.32 4.33 4.34 4.35 4.36 CFXLV3X.BIN, CFXLV3X.WBN - IBM Level 3 PC-3270 Emulation - * PSAPI * CFXLV3X.302 - IBM Level 3 PC-3270 Emulation With Fix for 3.02 Bug.....................................34 CFXHLLX.BIN, CFXHLLX.WBN - DOS HLLAPI-based Emulators ..............................................
PAGE 5
Across the Boards Communications Device Drivers Table of Contents Page iii 4.37 CFXNFSW.DLL 4.38 CFXNFSW.DLL 4.39 CFXT3NW.DLL 4.40 CFXT3NW.DLL 4.41 CFXT3WS.DLL 4.42 CFXT3WS.DLL 4.43 CFXT3FT.DLL 4.44 CFXT3FT.DLL 4.45 CFXT2LW.DLL 4.46 CFXT2NF.DLL 4.47 CFXT2NW.DLL 4.48 CFXT2WS.DLL 4.49 CFXT2FT.DLL 4.50 4.51 4.52 4.53 4.55 CFXNVLW.DLL CFXDN22.DLL CFXWHLL.DLL CFXOMNW.DLL CFXIBWS.DLL 4.56 CFX62DE.DLL 4.59 CFXT3WS3.DLL 4.60 CFXT3WS3.DLL 4.61 CFXCMGS.DLL 4.62 4.65 CFXEXTO.
PAGE 6
Across the Boards Communications Device Drivers Table of Contents Page iv 4.70 4.75 4.76 4.79 4.80 4.81 4.82 4.83 4.84 4.85 4.86 4.87 4.88 4.89 4.90 4.91 4.92 4.93 4.94 4.95 4.96 4.102 4.103 4.104 4.105 4.106 4.107 4.109 4.110 4.111 4.112 4.113 CFXT3LO.DLL - Telnet TN3270 with Structured Fields - Novell LAN Workplace for OS/2 .......................................................................104 CFXWHLL3.DLL - Windows Open HLLAPI (WOSA) - 32 bit.......................................................
PAGE 7
Across the Boards Communications Device Drivers Table of Contents Page v 4.114 4.115 4.116 4.117 4.118 4.122 4.123 4.124 4.125 4.126 4.127 4.129 4.130 4.131 4.132 4.133 4.134 4.135 4.136 4.137 4.138 4.139 4.140 4.141 4.143 4.144 4.145 4.146 4.147 4.148 4.149 CFXATLW.DLL - APPX/TCP - Novell LAN Workplace for DOS (Windows Support).......................................140 CFXATNF.DLL - APPX/TCP - Sun PC/NFS (Windows Support) .......................................................................
PAGE 8
Across the Boards Communications Device Drivers Table of Contents Page vi 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17 TCP/IP Host Names and Addresses .....................................................................................................185 Multiple COMM Port and Modem Server Support in Across the Boards/DOS...................................186 VTAM/NCP Issues for Across the Boards..........................................................................................
PAGE 9
Across the Boards Communications Device Drivers Table of Contents Page vii 6.31 6.32 6.33 6.34 6.35 6.36 6.37 6.38 6.39 MAINCON Panel F3 5250 HLLAPI...................................................................................................336 MAINCON Panel G1 Dynacomm Elite LU6.2 ...................................................................................338 MAINCON Panel G2 WinCPIC LU6.2 ..............................................................................................
PAGE 10
Across the Boards Communications Device Drivers Table of Contents Page viii cfSOFTWARE Confidential, 2000
PAGE 11
Across the Boards Communications Device Drivers Introduction Page 1 Introduction This manual describes the configuration and usage of the many communications devices supported by Across the Boards and pcMAINFRAME. This manual consists of eight major sections: 1. 2. 3. 4. 5. 6. 7. 8.
PAGE 12
Across the Boards Communications Device Drivers Introduction Page 2 cfSOFTWARE Confidential, 2000
PAGE 13
Across the Boards Communications Device Drivers Section 1 - Device Driver List Page 3 Section 1 - Device Driver List Device Driver Name Notes ATB dvc# DIALOG dev(name) CFXASNC CFXIRMA CFXPCOX CFXPC3X CFXFORT CFXIDEX CFXITTX CFXIBMX CFXASTX CFXPROX CFXMPLS CFXPATH CFXSPEC CFXLV3X CFXHLLX CFX525X CFXDECX CFX232X CFX525A CFXVINX CFXTTYX CFXTYMX CFXDFTX CFX400X CFXEXTW (1-Y) (1345-H) (12) (1) (1345-H) (12) (12) (1345-H) (12) (134J) (12) (12) (Y) (12) (12) (12) (134) (13-Y) (12) (12) (1) (134) (124-S) (12
PAGE 14
Across the Boards Communications Device Drivers Section 1 - Device Driver List Page 4 Device Driver Name Notes CFXT3WS CFXT3FT CFXT3FT CFXT2LW CFXT2NF CFXT2NW CFXT2WS CFXT2FT CFXNVLW CFXDN22 CFXWHLL CFXOMNW CFXIBWS (3-S) (3-S) (3-S) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) CFX62DE CFXT3WS3 CFXT3WS3 CFXCMGS CFXEXTO CFXT3IO CFXT3IO CFXT3FO CFXT3FO CFXT3LO CFXT3LO CFXWHLL3 CFXRUMO CFX5253 CFX147W CFXIRMA3 CFXFORT3 CFXIBMX3 CFXWHL5 CFXRUMB3 CFXCMG5 CFXT2IO CFXT2FO CFXT2LO CFXNULL CFXRUM5 CFXIRM5 CFXT2WS3 C
PAGE 15
Across the Boards Communications Device Drivers Section 1 - Device Driver List Page 5 Device Driver Name Notes ATB dvc# DIALOG dev(name) CFXT4NW CFXT4WS CFXT4FT CFXT4IO CFXT4FO CFXT4LO CFXT4WS3 CFX320X3 CFXATLW CFXATNF CFXATNW CFXATWS CFXATFT CFXATWS3 CFXNSEL3 CFXWRQI3 CFXIBMW3 CFXIBWS3 CFXRASW CFX62WC3 CFXATPP CFXATPPD CFX62NS3 CFX62EP3 CFX62RU3 CFXATPP3 (3) (3) (3) (4) (4) (4) (5) (W) (3-D) (3) (3) (3-D) (3) (5) (5) (5) (5) (5) (3-D) (5) (3-D) (6) (5) (5) (5) (5) 105 106 107 109 110 111 112 113 11
PAGE 16
Across the Boards Communications Device Drivers Section 1 - Device Driver List Page 6 (5) An ATB/Win32 driver named *3.DLL exists. NOTE: Unless note (T) is also specified, this driver can be loaded by ATB/Win16 via the CFXNTGT thunking module. See Section 5.8 for additional information. If a Win16 driver of the same driver also exists (“2” or “3”), the Win32 driver can be loaded via an alternate device name/number if note (H) is also specified. (6) An ATB/DOS extended DOS driver named *.DLL exists.
PAGE 17
Across the Boards Communications Device Drivers Section 1 - Device Driver List Page 7 1.1 pcMAINFRAME 3.x Device Codes pcMAINFRAME Version 1.x - Version 3.x used a one character code to refer to various Across the Boards device drivers (ATB/DOS only). The assignments are shown below: Device Driver Name ATB dvc# DIALOG dev(name) CFXASNC.BIN CFXIRMA.BIN CFXPCOX.BIN CFXPC3X.BIN CFXFORT.BIN CFXIDEX.BIN CFXITTX.BIN CFXIBMX.BIN CFXASTX.BIN CFXPROX.BIN CFXMPLS.BIN CFXPATH.BIN CFXSPEC.BIN CFXLV3X.
PAGE 18
Across the Boards Communications Device Drivers Section 1 - Device Driver List Page 8 cfSOFTWARE Confidential, 2000
PAGE 19
Across the Boards Communications Device Drivers Section 2 - Across the Boards Memory Sizes Page 9 Section 2 - Across the Boards Memory Sizes Across the Boards Memory Overhead (as of 6/24/93) The memory requirements are listed for the various possible combinations of Across the Boards modules. Note that for OS/2 and Windows the sizes of both the linked-in and DLL versions of Across the Boards are listed.
PAGE 20
Across the Boards Communications Device Drivers Section 2 - Across the Boards Memory Sizes Page 10 cfSOFTWARE Confidential, 2000
PAGE 21
Across the Boards Communications Device Drivers Section 3 - General Information Page 11 Section 3 - General Information General Device Support The Across the Boards device-drivers that work through 3270 emulation all support the Model-2 devices with 24 lines of 80 columns (1920 byte buffers). Some drivers also support other 3270 Models (3, 4 and 5) and some support extended attribute bytes (EABs). Configuration Program - MAINCON MAINCON.
PAGE 22
Across the Boards Communications Device Drivers Section 3 - General Information Page 12 3270 Controllers (continued) The FILE TRANSFER AID bit (.... .1..) must be ON. That means that hex 04 must be ORed to any other value desired for Feature 125. NOTE: The new IBM 3174 Model 90R microcode B Version 2.0 has a bug that causes it NOT to honor the TRANSFER AID bit. You must apply patch PTR 9032 from IBM to fix this problem.
PAGE 23
Across the Boards Communications Device Drivers Section 3 - General Information Page 13 Flicker CICS 1.7 XA MRO-ed terminals In CICS 1.7 XA with MRO-ed terminals, there is substantial flicker of the system wait X. This can cause the assumption of a completed message and free keyboard when in fact there is more data coming from the mainframe. A ZAP is available for the CUT mode modules: CFXIRMA, CFXFORTE, and CFXIBMX. Contact cfSOFTWARE if you think this problem has arisen. Example ZAP DEBUG CFXdddd.
PAGE 24
Across the Boards Communications Device Drivers Section 3 - General Information Page 14 CICS Terminal Definition A critical factor in the use of 3270 terminals is the size of the terminal I/O area. This is defined in the TIOAL parameter in the TCT entry or in the IOAREALEN parameter of the TYPTERM entry if RDO is used to define terminals. If the device is non-SNA the value specified should be at least as large as the maximum message that will be sent to the device.
PAGE 25
Across the Boards Communications Device Drivers Section 4 - Device Driver Configuration and Usage Page 15 Section 4 - Device Config.
PAGE 26
Across the Boards Communications Device Drivers Section 4 - Device Driver Configuration and Usage Page 176 cfSOFTWARE Confidential, 2000
PAGE 27
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 177 Section 5 - General Configuration and Usage Information 5.1 Protocol Converter 3101 and VT100 - Special Considerations Converter Quirks The following list must be considered a small fraction of the total selection of protocol converters. In addition, due to constant changes and RPQs to converter hardware and software for the same brand/model this quirk list may not be valid. Expect the worst.
PAGE 28
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 178 5.1 Protocol Converter 3101 and VT100 (continued) IBM AS/400 - VT100 protocol conversion The AS/400 places asterisks in column 80 from row 9 down to simulate terminal lights or some such thing. This disrupts data transfer. NOTE: To turn off this asterisking, send ESC ^W (hex 1B 17) from the PC to the AS/400 before doing any data transfer or APPX CONNECT COMTEX.
PAGE 29
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 179 5.1 Protocol Converter 3101 and VT100 (continued) Under VTAM the confirmation send was done before the asterisk was replaced. It appeared that the asterisk was always replaced with a blank in both environments which should have caused a problem, but the trace sample was small and it may have been that the data byte was in fact always a blank.
PAGE 30
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 180 5.1 Protocol Converter 3101 and VT100 (continued) Data Stream - Works only with Data-Stream microcode versions above 2.0. (A ROM upgrade may be required) Data Lynx - Do not load TERMLYNX TSR software (grabs COMM port interrupt) or use program UNCLINK to cause TSR to release COMM port (program CLINK re-establishes it for TSR).
PAGE 31
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 181 5.
PAGE 32
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 182 5.2 Configuring the Telnet TN3270 Drivers (continued) Configuration of Telnet TN3287 Support In addition to the TN3270 options described above, the “TN3270 with TN3287” drivers support several configuration options related to printer support. There is a second MAINCON configuration panel for the TN3287 driver which contains the additional options.
PAGE 33
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 183 5.2 Configuring the Telnet TN3270 Drivers (continued) The ApkPrint base terminal key will initiate a local copy operation. When the host name is entered, a specific printer LU may be requested. The syntax is: hostname [port] [:[luname][/prtluname] Examples: Request LU “LU2T0001” (with associated printer): CF370.CFSOFT.COM :LU2T0001 Request LU “LU2T0001” with specific printer “LUPRT1” CF370.
PAGE 34
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 184 5.3 Configuring the Telnet VT220 Drivers MAINCON Configuration Panel: E2: “Telnet VT220” MAINCON must be used to configure the Telnet VT220 drivers. With the exception of the first panel, the MAINCON configuration for the Telnet VT220 drivers is identical to that of the async/serial VT220 driver. This Section describes only the differences in the Telnet VT220 configuration.
PAGE 35
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 185 5.4 TCP/IP Host Names and Addresses The Telnet drivers accept host names or addresses entered via the keystroke functions while in disconnected state or via the TELNETCON control string. This may be an IP “dotted-decimal” address or the name of the host to be resolved via the /etc/hosts file or the name service in use.
PAGE 36
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 186 5.5 Multiple COMM Port and Modem Server Support in Across the Boards/DOS MAINCON Configuration Panel: D1: “Comm Port Assignments” Version 3.06 of Across the Boards adds support for multiple COMM ports (ports beyond COM1 and COM2) and NASI and INT 14 based modem servers (also known as async gateways). A new MAINCON configuration screen allows the configuration of COM1 through COM15.
PAGE 37
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 187 5.5 Multiple COMM Port and Modem Server Support (continued) Configuration for INT 14 is similar to the preceding examples with the following exceptions: 1. 2. 3. Again, the choice of COMM port is not significant (1-15 may be used). On the “Communication Port Assignments” configuration screen, specify type “INT14” for the COMM port you have chosen.
PAGE 38
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 188 5.6 VTAM/NCP Issues for Across the Boards 5.6.1 Buffer size problems in cfDFT and other structured field drivers Environments generating SNA sense codes of X’800A’ (in some drivers, especially cfDFT, reported as X’0A80’), may have a configuration problem in NCP or VTAM. The sense code is most often returned after an APPX send operation involving a large structured field.
PAGE 39
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 189 5.7 Windows NT CFXNTDD.SYS Installation CFXIRMA3.DLL (device number 1), CFXIBMX3.DLL (#7) and CFXFORT3.DLL (#4) require that CFXNTDD.SYS be installed. NOTE: Drivers 81, 82, 83 are synonyms for 1, 4, and 7. Run the INSTNTDD.EXE installation program or use the following manual procedure: 5.7.1 Copy CFXNTDD.SYS to \WINNT\SYSTEM32\DRIVERS 5.7.2 Use REGINI to add the items in CFXNTDD.
PAGE 40
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 190 5.8 ATB/Win16 Applications under WOW (Windows-on-Windows) in Windows NT and in Windows 95 The WOW (Windows-on-Windows) environment of Windows NT provides the capability to run 16 bit Windows applications under Windows NT. WOW prevents many ATB/Win16 device drivers from running, either because they access hardware directly or invoke an unavailable API. In many cases CFXNTGT.
PAGE 41
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 191 5.8 ATB/Win16 Applications under WOW (Windows-on-Windows) in Windows NT and in Windows 95 (continued) ATB/Win32 Driver Driver Name CFXIRMA3.DLL* CFXFORT3.DLL* CFXIBMX3.DLL* CFX220X3.DLL* CFXT3WS3.DLL CFXT3WS3.DLL CFXWHLL3.DLL CFXRUMB3.DLL CFXT2WS3.DLL CFXEXTW3.DLL CFX320X3.DLL* CFXT4WS3.DLL CFXATWS3.DLL CFXNSEL3.DLL CFXWRQI3.DLL CFXSWFT3.DLL CFXIBMW3.DLL CFXIBWS3.DLL CFX62WC3.DLL CFX62NS3.
PAGE 42
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 192 5.9 Identifying HLLAPIs While this document describes many of the existing Windows and OS/2 HLLAPIs, and the ATB/Win16, ATB/Win32, and ATB/OS2 drivers to use with them, in some cases the end-user is not sure which 3270 emulator they have installed, or they may have a 3270 emulator that we have not seen before. The various 3270 emulators load various named DLLs to provide their HLLAPI.
PAGE 43
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 193 5.9 Identifying HLLAPIs (continued) HLLAPI DLL name ATB/OS2 Driver(s) using that name ACS3EHAP.DLL* ACS3EHAP.DLL* ACS3EHAP.DLL* ACS3EHAP.DLL*% EEHLLAPI.DLL CFXCMGX.DLL CFXCMGS.DLL CFXEXTO.DLL CFXCMG5.DLL CFXRUMO.
PAGE 44
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 194 5.10 Configuring the APPX/TCP Drivers MAINCON Configuration Panel: E5: “APPX/TCP” MAINCON Configuration Panel: E6: “APPX/TCP - cfPPP” MAINCON must be used to define at least one configuration record for APPX/TCP drivers to use. Each configuration record is used for one host connection and specifies various data about each connection. This is essentially identical in function to CPI-C (LU6.
PAGE 45
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 195 MAINCON can be used to enable a trace of the TCP/IP activity between the driver and the host. Entering a trace size other than zero will enable the trace. The trace data is kept in a circular buffer and will be written when the driver is closed. A file called TCPTRAC.BUF will be produced in the current working directory. The program TRACEFMT.EXE will format the TCPTRAC.BUF file.
PAGE 46
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 196 5.11 Configuring the Telnet VT320 Drivers MAINCON Configuration Panel: E4: “Telnet VT320” MAINCON must be used to configure the Telnet VT320 drivers. With the exception of the first panel, the MAINCON configuration for the Telnet VT320 drivers is identical to that of the async/serial VT320 driver. This Section describes only the differences in the Telnet VT320 configuration.
PAGE 47
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 197 5.12 DOS HLLAPI Passthroughs Numerous Windows, Windows NT/95 and OS/2 3270 emulators provide virtual device drivers which provide DOS applications access to the Windows emulator’s HLLAPI via the traditional DOS HLLAPI (Interrupt 7F) interface (using CFXHLLX.BIN, driver #14).
PAGE 48
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 198 5.13 CFXVXDT/CFXVXDS Usage - ATB/Win16 Driver Access for ATB/DOS Selected ATB/Win16 drivers can be used from ATB/DOS applications when the DOS application is running in a DOS session under Windows 3.1 (386 Enhanced Mode only) or Windows 95. Windows NT is not supported. The use of such a driver is mostly transparent to the ATB/DOS application, but some system setup is required.
PAGE 49
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 199 5.13 CFXVXDT/CFXVXDS Usage (continued) The following should be considered: - Explicit directory specifications work as expected. An explicit directory specification will contain a drive letter followed by a colon and a backslash. One exception is when a drive letter is mapped locally to the DOS session and is not mapped the same way for CFXVXDS.
PAGE 50
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 200 5.14 cfPPP Driver Usage Several Across the Boards TCP/IP drivers with embedded TCP/IP and PPP stacks are available. Several special considerations apply when using these drivers. General Program Flow The use of cfPPP based drivers proceeds in three steps: link startup, application driver usage, and link shutdown.
PAGE 51
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 201 5.14 cfPPP Driver Usage (continued) When the SysReq key is sent, The TTY screen is cleared, the keyboard is locked, and the status of the PPP link is displayed on the first line. At link startup this will be “PPP: Negotiating” while the PPP negotiation happens, and when the link is fully established “PPP: Connected” is displayed.
PAGE 52
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 202 5.14 cfPPP Driver Usage (continued) ; Dial phone send ‘ATDT9,16305742790’ cr waitfor ‘CONNECT’ waitfor ‘LAPM’ delay (.
PAGE 53
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 203 5.15 CFXSWTC - ATB/DOS Extended DOS Driver Support Some ATB/DOS drivers are implemented as extended DOS applications. These drivers require special support by the application to get the extended DOS environment loaded. To use an extended mode driver the application load sequence should be changed from: program parm1 parm2... to: cfxswtc cfx????.dll c:\dir\program.exe parm1 parm2... CFXSWTC.
PAGE 54
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 204 5.16 LU6.2 Configuration This section provides an overview of setting up LU6.2 connections for use with Across the Boards and pcMAINFRAME. This section covers the mainframe (VTAM and CICS) configurations in detail, only an overview is given of the PC side (emulator) configuration. See the device specific sections for more information about configuring emulators for LU6.2 support.
PAGE 55
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 205 5.16 LU6.2 Configuration (continued) VTAM VTAM 3.4 or later is recommended. Note: the following discussion assumes that the emulator connects directly to a VTAM rather than through an NCP. The NCP configuration requirements are similar to the VTAM configuration described below, but are not otherwise discussed. The VTAM supporting (e.g., connected to) the PC should be set up as an APPN node.
PAGE 56
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 206 5.16 LU6.2 Configuration (continued) Sample major node “PC001001”: **P/390 VM****************************************PC001001/SYS4** 3172 (AWS3172) DEVICES (280) 06/02/98 ***************************************************************** 09 TOKENRING STATIONS -- IDNUM=01001 LU 6.
PAGE 57
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 207 5.16 LU6.2 Configuration (continued) pcMAINFRAME Host-Init Considerations pcMAINFRAME Host-Init (CFXINIT) requires the definition of a group of VTAM APPLs. For LU6.2 support, the following additional requirements must be met: “APPC=YES” must be specified on each APPL. Most LU6.2 connections will use modes #INTER or #BATCH.
PAGE 58
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 208 5.16 LU6.2 Configuration (continued) CONNECTION and SESSION definitions will need to be made for each CICS that will be accessed by the emulator. The following discussion assumes that the definitions will be made view Resource Definition Online (aka RDO and CEDA). MVS NOTE: it is possible in CICS/ESA v4 to auto-install parallel session definitions.
PAGE 59
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 209 5.16 LU6.
PAGE 60
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 210 5.16 LU6.2 Configuration (continued) Emulator Configuration The emulator or gateway must be configured with definitions that match the VTAM and CICS definitions. The exact way this is accomplished is dependent on the emulator or gateway in question, so only the general points are listed here. See the device specific sections for more information about configuring emulators for LU6.2 support.
PAGE 61
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 211 5.16 LU6.2 Configuration (continued) CPI-C Side Information Definitions Side information is used to provide default settings for an application program, although in many cases the application allows the settings configured in side-info to be overridden. A minimal side-info record is required.
PAGE 62
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 212 5.16 LU6.2 Configuration (continued) Pacing Proper pacing in an SNA network is important to prevent congestion and buffer overflow errors. In SNA configurations without much LU6.2 activity, certain default pacing values may be set that can cause problems. LU6.2 sessions are capable of generating very large quantities of traffic in a single direction without responses from the receiver.
PAGE 63
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 213 5.17 Configuring the Telnet TN5250 Drivers MAINCON Configuration Panel: E8: “Telnet TN5250” Configuration of Telnet TN5250 Drivers If MAINCON is not used to configure the Telnet TN5250 drivers, the driver will run as a IBM 3179-2 type of 5250 terminal, with no TCP/IP trace and using the Telnet Well-Known-Port as the default (#23).
PAGE 64
Across the Boards Communications Device Drivers Section 5 - General Configuration and Usage Information Page 214 5.17 Configuring the Telnet TN5250 Drivers (continued) When first opened, the drivers display an NVT screen with a message requesting entry of the host name or address. The NVT screen consists of one enterable line (at the bottom), and a scrolling message area above the enterable area. 5250 screen attributes are emulated on the NVT screen by the driver.
PAGE 65
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 215 Section 6 - MAINCON Driver Configuration Device Configuration In many cases pcMAINFRAME and Across the Boards have defaults which allow the use of a communications device without any further configuration. For devices requiring configuration (for example, protocol converters, cfDFT, or LU 6.
PAGE 66
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 216 Running MAINCON MAINCON can be run from the DOS or OS/2 command line, as well as clicking on the icon Device Configuration (pcMainframe for Windows only). It displays its main menu. Enter the two character code associated with the menu entry and the selected configuration panel will be displayed. Alter the parameters as needed, and press PF10 to save the configuration file.
PAGE 67
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 217 6.1 MAINCON Panel A1 VDT/Keyboard Config Configuration filename: MAINCFG.VDT Used by All Drivers __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 1 of 3 ---------- Video Monitor Mode ---------0 = AUTO, 1 = BW80, 3 = IBM 3270PC...... 0 = fast mode, 1 = slow (well behaved).. Controller Language..................... Alternate key-scancode file suffix......
PAGE 68
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 218 6.1 MAINCON Panel A1, VDT/Keyboard Config (continued) 3. Keyboard Language Code Causes the Controller Language Variable 10, Extra 10 and Extra-Extra 10, and the 3270 Controller Language Set Translate Table to be loaded as appropriate for the selected 3270 Keyboard Language. The following are defined: 1 - U.S. English 2 - Dutch 3 - French AZERTY 4 - German 5 - Italian 6 - Spanish 7 - Brazilian 8 - U.K.
PAGE 69
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 219 6.1 MAINCON Panel A1, VDT/Keyboard Config (continued) 8. Video Dimensions DIALOG and CFXDIAL only. Ignored for OS/2 versions of DIALOG and CFXDIAL (OS/2 versions of DIALOG support 80x25 screens only). Ignored for model 2 only versions of DIALOG and CFXDIAL. If set to “Autodetect”, DIALOG will make use of the 80x43 or 80x50 display available on EGA and VGA displays when displaying 3270 models other than 2.
PAGE 70
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 220 6.
PAGE 71
Ctrl Shift Caps Lock Tab ~ Esc Alt X PF24 PF23 Z S PF14 PF13 D C F V AltCr CrBlk F5 B cfSOFTWARE Confidential, 2000 M < > : PF22 P PF10 PA3 L PF21 O 0 Alt ? { PF11 - F9 " Shift } PF12 = DvCncl Reset F10 F12 Ctrl Enter \ Backspace F11 Del Ins Print Screen Default 3270 Keyboard Layout N Test Click F8 PF9 9 PA2 K PF20 I PF8 PA1 J PF19 U 8 Print Er EOF Ident F7 F6 PF7 7 Mar H PF18 Y PF6 6 Dup G PF17 T PF5 5 ErInp F4 PF
PAGE 72
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 222 6.2 MAINCON Panel A2 APPX and Troubleshooting Configuration filename: MAINCFG.PPX Used by All Drivers __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 1 of 2 --- Communications Trouble Shooting --PC APPX Trace Level..................... Mainframe APPX Trace Level.............. Mainframe APPX Trace Queue type......... Serial Line Trace.......................
PAGE 73
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 223 6.2 MAINCON Panel A2, APPX and Troubleshooting (continued) 5. Serial Line Trace Size in K bytes This option allows the user to configure the amount of space to be allocated to the serial line trace buffer. If zero is specified or the device driver is unable to allocate the specified amount, a default allocation will be made (the size of the default allocation varies by device). 6.
PAGE 74
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 224 6.2 MAINCON Panel A2, APPX and Troubleshooting (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 2 of 2 --- Communications Trouble Shooting --Safe-character mode..................... Flicker check time (in 100ths second)... Transaction via Keystroke............... Protocol Converter Send Options......... APPX Block Size......................... Reliable Link Pacing......
PAGE 75
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 225 6.2 MAINCON Panel A2, APPX and Troubleshooting (continued) 11. Protocol Converter Send Options This option allows the customization of 3270 sends to protocol converted attached PCs. This field should almost never be changed. The following options are available: 0 - Normal: No Erase-Write, ETB Confirm will be sent separately. 1 - No Erase-Write, ETB Confirm will be included in the primary send.
PAGE 76
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 226 6.3 MAINCON Panel B1 CUT Mode/Single Session 3270 IBM 3270 Connection Configuration filename: MAINCFG.IBM Used by cf Device Drivers: # 7 83 Name CFXIBMX CFXIBMX3 Description IBM 3278/9 CUT Mode WOW IBM 3278/9 CUT Mode __________________ __________________ ACROSS-THE-BOARDS(r) Config ---- IBM 3270 Connection (CUT mode) ---First IBM port address (in hex)......... IBM RAM address (in hex)................
PAGE 77
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 227 6.4 MAINCON Panel B2 CUT Mode/Single Session DCA Irma Coax Card Configuration filename: MAINCFG.IRM Used by cf Device Drivers: # 1 81 Name CFXIRMA CFXIRMA3 Description Irma/Irma2/Irma3 WOW Irma/Irma2/Irma3 __________________ __________________ ACROSS-THE-BOARDS(r) Config --------------- DCA Irma --------------Irma Card Model......................... 0 First I/O port address (in hex).........
PAGE 78
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 228 6.5 MAINCON Panel B3 Forte Configuration filename: MAINCFG.FOR Used by cf Device Drivers: # 4 82 Name CFXFORT CFXFORT3 Description Forte WOW Forte __________________ __________________ ACROSS-THE-BOARDS(r) Config ------------- Forte 3278/9 ------------First I/O port address (in hex)......... 280 If the I/O port address has been changed from 280, then enter the new I/O port address here.
PAGE 79
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 229 6.6 MAINCON Panel B4 IDEAcomm Configuration filename: MAINCFG.IDE Used by cf Device Drivers: # 5 Name CFXIDEX Description IDEA Card __________________ __________________ ACROSS-THE-BOARDS(r) Config ------------- IDEA 3278/9 -------------IDEAcomm RAM address (in hex)........... FFF0 If RAM address changed from FFF0 (1FF0 on PS/2s), enter new RAM address here.
PAGE 80
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 230 6.7 MAINCON Panel B5 AST Remote Configuration filename: MAINCFG.AST Used by cf Device Drivers: # 8 Name CFXASTX Description AST Remote __________________ __________________ ACROSS-THE-BOARDS(r) Config -------------- AST Remote -------------Logical unit (LU)....................... 0 AST interrupt number (in hex)........... 59 Enter LU number to connect to (0 to 31 if bisync, 2 to 255 if SNA).
PAGE 81
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 231 6.8 MAINCON Panel B6 Pathway Remote Configuration filename: MAINCFG.PTH Used by cf Device Drivers: # 11 Name CFXPATH, CFXPAT4, OLDPATH, OLDPAT4 __________________ Description Pathway/ICOT Remote __________________ ACROSS-THE-BOARDS(r) Config ------------ Pathway Remote -----------Logical unit (LU)....................... 0 Pathway interrupt number (in hex).......
PAGE 82
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 232 6.9 MAINCON Panel B7 CUT Mode/Single Session 3270 Xircom Pocket Configuration filename: MAINCFG.XIR Used by cf Device Drivers: # 32 Name CFXXIRC Description Xircom Pocket 3270 __________________ __________________ ACROSS-THE-BOARDS(r) Config ------ Xircom Pocket 3270 Adapter -----Xircom Multiplex ID..................... C7 CUT mode model and EAB support..........
PAGE 83
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 233 6.10 MAINCON Panel C1 Multi-host Session HLLAPI/API/Workstation/etc. Configuration filename: MAINCFG.
PAGE 84
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 234 6.10 MAINCON Panel C1, Multi-host Session (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config ----- Any HLLAPI, PS-API or cfDFT ----Host Session letter..................... E Process EABs............................ N Trace HLLAPI Calls......................
PAGE 85
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 235 6.10 MAINCON Panel C1, Multi-host Session (continued) 2. Process EABs Some HLLAPI implementations do not support EABs properly. Specify ‘Y’ only if you require EABs. EABs will only be returned if the underlying emulator is configured to return them.
PAGE 86
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 236 6.11 MAINCON Panel C2 cfDFT Coax Configuration filename: MAINCFG.DFT Used by cf Device Drivers: # 23 28 Name CFXDFTX, CFXDFTN, CFXDFTS CFXDFTX, CFXDFTN, CFXDFTS Description cfDFT cfDFT without SF Support __________________ __________________ ACROSS-THE-BOARDS(r) Config ------- cfDFT via IBM Coax Card -------First coax card port address (in hex)... Coax card RAM address (in hex)..........
PAGE 87
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 237 6.11 MAINCON Panel C2, cfDFT Coax (continued) 6. Trace Size in KB Defines the size of the allocated trace buffer in KB. If zero, the cfDFT trace is disabled. Specifying an odd trace size will perform a “before and after” trace, an even trace size will trace before or after as is appropriate for the event being traced. In general, the cfDFT trace should only be enabled when instructed to do so by cfSOFTWARE.
PAGE 88
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 238 6.12 MAINCON Panel C3 PCOX/CXI/Novell Configuration filename: MAINCFG.PCX Used by cf Device Drivers: # 2 Name CFXPCOX Description PCOX/CXI __________________ __________________ ACROSS-THE-BOARDS(r) Config ----------- PCOX/CXI/Novell -----------Novell API interrupt number (in hex).... 6F Host Session letter.....................
PAGE 89
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 239 6.13 MAINCON Panel C4 Banyan VINES Configuration filename: MAINCFG.VIN Used by cf Device Drivers: # 20 Name CFXVINX Description Banyan VINES __________________ __________________ ACROSS-THE-BOARDS(r) Config ------------- Banyan VINES ------------Logical unit (LU)....................... 0 Host Session letter.....................
PAGE 90
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 240 6.14 MAINCON Panel D1 COMM Port Assignment Configuration filename: MAINCFG.
PAGE 91
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 241 6.14 MAINCON Panel D1, COMM Port Assignment (continued) 2. Type ‘C’ (COMM Port) This identifies the serial device as a standard 8250 compatible serial port. Serial Across the Boards device driver (CFXPROX, CFXDECX and CFXTYMX) will program the serial port directly. The following fields are required for a Type ‘C’ record: 2.1. I/O Port Origin Address The address of the first I/O port of the 8250.
PAGE 92
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 242 6.14 MAINCON Panel D1, COMM Port Assignment (continued) 4. Type ‘I’ (INT 14) This identifies the serial device as a INT 14 compatible async or modem server. Serial Across the Boards device drivers (CFXPROI, CFXDECI and CFXTYMI) will use the INT 14h API provided by the INT 14 redirector. Programming note: The basic dialect of the INT 14 interface is identical to the IBM PC BIOS INT 14h serial port services.
PAGE 93
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 243 6.15 MAINCON Panel D2 IBM 3101 Configuration filename: MAINCFG.PRX Used by cf Device Drivers: # 9 Name CFXPROX, CFXPROI, CFXPRON, HYDPROX, HYDPROI, HYDPRON Description IBM 3101 Protocol Converter For DOS, CFXPROX is the direct to COMM port driver, CFXPROI is the INT 14h driver, and CFXPRON in the NASI driver. The correct driver is automatically loaded as defined in MAINCFG.POR.
PAGE 94
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 244 6.15 MAINCON Panel D2, IBM 3101 (continued) 5. HW Flow - Hardware Flow Control Option ‘0’/‘1’/‘2’ - none/CTS-RTS/DSR-DTR. Selects type of hardware flow control, usually used with error correcting modems. Setting CTS/RTS will prevent the driver from sending data unless the modem raises CTS, setting DSR/DTS prevents the driver from sending unless the modem raises DSR.
PAGE 95
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 245 6.15 MAINCON Panel D2, IBM 3101 (continued) 15. Print Routing Printer passthrough support.
PAGE 96
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 246 6.15 MAINCON Panel D2, IBM 3101 (continued) These panels define what is sent to the host when the 3101 terminal is used for 3270 emulation. Each entry defines the sequence sent for a single 3270 key. For example, the 3270 protocol converter attached by the host may be configured to emulate the 3270 Clear key function when it receives the sequence Esc L.
PAGE 97
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 247 6.15 MAINCON Panel D2, IBM 3101 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page ----3101---Space ! “ # $ % & ‘ ( ) * + , . / IBM 3101 - ASCII Key Values -----PC ASCII---------3101---SP 0 ! 1 “ 2 # 3 $ 4 % 5 & 6 ‘ 7 ( 8 ) 9 * : + ; , < = .
PAGE 98
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 248 6.
PAGE 99
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 249 6.16 MAINCON Panel D3 DEC VT100 Configuration filename: MAINCFG.DEC Used by cf Device Drivers: # 16 Name CFXDECX, CFXDECI, CFXDECN Description DEC VT100 Protocol Converter For DOS, CFXDECX is the direct to COMM port driver, CFXDECI is the INT 14h driver, and CFXDECN in the NASI driver. The correct driver is automatically loaded as defined in MAINCFG.POR.
PAGE 100
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 250 6.16 MAINCON Panel D3, DEC VT100 (continued) 5. HW Flow - Hardware Flow Control Option ‘0’/‘1’/‘2’ - none/CTS-RTS/DSR-DTR. Selects type of hardware flow control, usually used with error correcting modems. Setting CTS/RTS will prevent the driver from sending data unless the modem raises CTS, setting DSR/DTS prevents the driver from sending unless the modem raises DSR.
PAGE 101
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 251 6.16 MAINCON Panel D3, DEC VT100 (continued) 15. Print Routing Printer passthrough support.
PAGE 102
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 252 6.16 MAINCON Panel D3, DEC VT100 (continued) These panels define what is sent to the host when the VT100 terminal is used for 3270 emulation. Each entry defines the sequence sent for a single 3270 key. For example, the 3270 protocol converter attached by the host may be configured to emulate the 3270 Clear key function when it receives the sequence Esc L.
PAGE 103
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 253 6.16 MAINCON Panel D3, DEC VT100 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page ---VT100---Space ! “ # $ % & ‘ ( ) * + , . / DEC VT100 - ASCII Key Values -----PC ASCII--------VT100---SP 0 ! 1 “ 2 # 3 $ 4 % 5 & 6 ‘ 7 ( 8 ) 9 * : + ; , < = .
PAGE 104
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 254 6.
PAGE 105
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 255 6.17 MAINCON Panel D4 Tymnet78 Configuration filename: MAINCFG.TYM Used by cf Device Drivers: # 22 Name CFXTYMX, CFXTYMI, CFXTYMN Description Tymnet78 For DOS, CFXTYMX is the direct to COMM port driver, CFXTYMI is the INT 14h driver, and CFXTYMN in the NASI driver. The correct driver is automatically loaded as defined in MAINCFG.POR. For Windows and OS/2, CFXTYMX supports all functions.
PAGE 106
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 256 6.17 MAINCON Panel D4, Tymnet78 (continued) 2. Print Routing Printer passthrough support.
PAGE 107
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 257 6.17 MAINCON Panel D4, Tymnet78 (continued) 10. Parity ‘E’ = Even, ‘O’ = Odd, ‘S’ = Space, ‘M’ = Mark, and ‘N’ = None. 11. Data Bits ‘7’ or ‘8’ data bits. 12. Stop Bits ‘1’ or ‘2’ stop bits. 13. Attributes This field control whether or not 3270 attributes are to be interpreted.
PAGE 108
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 258 6.17 MAINCON Panel D4, Tymnet78 (continued) NOTE: The key definitions for the Tymnet78 driver should not normally be changed from the defaults. These panels define what is sent to the host when the VT220/VT320 terminal is used for 3270 emulation. Each entry defines the sequence sent for a single 3270 key.
PAGE 109
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 259 6.17 MAINCON Panel D4, Tymnet78 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page --TYMNET78-Space ! “ # $ % & ‘ ( ) * + , . / TYMNET78 - ASCII Key Values -----PC ASCII-------TYMNET78-SP 0 ! 1 “ 2 # 3 $ 4 % 5 & 6 ‘ 7 ( 8 ) 9 * : + ; , < = .
PAGE 110
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 260 6.
PAGE 111
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 261 6.18 MAINCON Panel D5 TTY and PC-to-PC (RS232) Configuration filename: MAINCFG.PC2 Used by cf Device Drivers: # 17 21 Name CFX232X, CFX232I, CFX232N CFXTTYX, CFXTTYI, CFXTTYN Description PC-to-PC RS232 Async TTY For DOS, CFX232X and CFXTTYX are the direct to COMM port drivers, CFX232I and CFXTTYI are the INT 14h drivers, and CFX232N and CFX232I are the NASI drivers.
PAGE 112
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 262 6.18 MAINCON Panel D5, TTY and PC-to-PC(continued) 4. Parity ‘E’ = Even, ‘O’ = Odd, ‘S’ = Space, ‘M’ = Mark, and ‘N’ = None. 5. Data Bits ‘7’ or ‘8’ data bits. 6. Stop Bits ‘1’ or ‘2’ stop bits. 7. Main Esc CFXTTYX use only. Leave this field set to blank.
PAGE 113
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 263 6.19 MAINCON Panel D6 DEC VT220 Configuration filename: MAINCFG.220 Used by cf Device Drivers: # 33 94 Name CFX220X CFX220X3 Description VT220 Driver WOW VT220 Async __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 1 of 14 ---- Protocol Converter (DEC VT220) ---Autowrap (0 or 1)....................... Reset needed after BELL? (0=No, 1=Yes).. XON/XOFF (in hex) FF if no XON/XOFF...
PAGE 114
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 264 6.19 MAINCON Panel D6, DEC VT220 (continued) 5. HW Flow - Hardware Flow Control Option ‘0’/‘1’/‘2’ - none/CTS-RTS/DSR-DTR. Selects type of hardware flow control, usually used with error correcting modems. Setting CTS/RTS will prevent the driver from sending data unless the modem raises CTS, setting DSR/DTS prevents the driver from sending unless the modem raises DSR.
PAGE 115
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 265 6.19 MAINCON Panel D6, DEC VT220 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 2 of 14 ---- Protocol Converter (DEC VT220) ---Machine Mode (1,2,3,4).................. VT200 ID (1,2,3,4)...................... User Features (0 = Unlock, 1 = Lock).... Rows & Columns.......................... New Line (CR/CRLF)...................... Margin Bell (On/Off)..................
PAGE 116
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 266 6.19 MAINCON Panel D6, DEC VT220 (continued) 20. Warning Bell When ‘1’ (ON) is selected, an audible alarm will sound when an operation error occurs or the display station received control-G code. If you select ‘0’ (Off), and then the alarm will not be sounded when error occurs or control-G received. 21.
PAGE 117
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 267 6.19 MAINCON Panel D6, DEC VT220 (continued) These panels define what is sent to the host when the host requests the Answerback string or a user defined key is sent. Each entry defines the sequence sent for one user defined key or for the answerback string. For example, the user defined key F6 might be defined to send ‘ABCD’ by entering A, B, C and D in the first four fields for the F6 entry in the table.
PAGE 118
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 268 6.19 MAINCON Panel D6, DEC VT220 (continued) These panels define what is sent to the host when the VT220 terminal is used for 3270 emulation. Each entry defines the sequence sent for a single 3270 key. For example, the 3270 protocol converter attached by the host may be configured to emulate the 3270 Clear key function when it receives the sequence Esc L.
PAGE 119
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 269 6.
PAGE 120
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 270 6.
PAGE 121
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 271 6.
PAGE 122
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 272 6.
PAGE 123
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 273 6.
PAGE 124
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 274 6.20 MAINCON Panel D7 DEC VT320 Configuration filename: MAINCFG.320 Used by cf Device Drivers: # 102 113 Name CFX320X CFX320X3 Description VT320 Driver WOW VT320 Async __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 1 of 14 ---- Protocol Converter (DEC VT320) ---Autowrap (0 or 1)....................... Reset needed after BELL? (0=No, 1=Yes).. XON/XOFF (in hex) FF if no XON/XOFF.
PAGE 125
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 275 6.20 MAINCON Panel D7, DEC VT320 (continued) 5. HW Flow - Hardware Flow Control Option ‘0’/‘1’/‘2’ - none/CTS-RTS/DSR-DTR. Selects type of hardware flow control, usually used with error correcting modems. Setting CTS/RTS will prevent the driver from sending data unless the modem raises CTS, setting DSR/DTS prevents the driver from sending unless the modem raises DSR.
PAGE 126
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 276 6.20 MAINCON Panel D7, DEC VT320 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 2 of 14 ---- Protocol Converter (DEC VT320) ---Machine Mode (1,2,3,4).................. VT300 ID (1,2,3,4,5).................... User Features (0 = Unlock, 1 = Lock).... Rows & Columns.......................... New Line (CR/CRLF)...................... Margin Bell (On/Off)..................
PAGE 127
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 277 6.20 MAINCON Panel D7, DEC VT320 (continued) 20. Margin Bell When ‘1’ (ON) is selected, an audible alarm will sound when the cursor reaches the right margin; either column 73 (80- column mode) or column 125 (132-column mode). If you select ‘0’(Off), and the alarm will not be sounded when the right margin is reached. 21. Backspace/Del key When ‘1’ is selected, the Backspace key sends an 0x08 (BS).
PAGE 128
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 278 6.20 MAINCON Panel D7, DEC VT320 (continued) These panels define what is sent to the host when the host requests the Answerback string or a user defined key is sent. Each entry defines the sequence sent for one user defined key or for the answerback string. For example, the user defined key F6 might be defined to send ‘ABCD’ by entering A, B, C and D in the first four fields for the F6 entry in the table.
PAGE 129
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 279 6.
PAGE 130
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 280 6.20 MAINCON Panel D7, DEC VT320 (continued) These panels define what is sent to the host when the VT320 terminal is used for 3270 emulation. Each entry defines the sequence sent for a single 3270 key. For example, the 3270 protocol converter attached by the host may be configured to emulate the 3270 Clear key function when it receives the sequence Esc L.
PAGE 131
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 281 6.
PAGE 132
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 282 6.
PAGE 133
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 283 6.
PAGE 134
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 284 6.
PAGE 135
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 285 6.
PAGE 136
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 286 6.21 MAINCON Panel E1 Single Session TN3270 Configuration filename: MAINCFG.
PAGE 137
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 287 6.21 MAINCON Panel E1, Single Session TN3270 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config -------- Single Session TN3270 --------3270 Terminal Model..................... Trace size in K bytes................... Destination Port Number................. Disconnect Option....................... Minimum Response Time................... Accept Spurious Writes..................
PAGE 138
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 288 6.21 MAINCON Panel E1, Single Session TN3270 (continued) 6. Accept Spurious Writes Some TN3270 servers insert spurious write commands into the outbound 3270 datastream while structured fields are being sent and received. This configuration option can be used to compensate for this behavior. When set to ‘0’, 3270 Write commands will be will be interpreted as standard for 3270 commands.
PAGE 139
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 289 6.22 MAINCON Panel E2 Telnet VT220 Configuration filename: MAINCFG.
PAGE 140
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 290 6.22 MAINCON Panel E2, Telnet VT220 (continued) 4. Half-Duplex Setting this field to ‘1’ will cause the VT220 emulator to operate in half-duplex mode. Half-duplex mode is significantly inferior to full-duplex mode for terminal emulation and data transfer. Full-duplex mode should be used where ever possible. 5. Trace Size in K bytes Defines the size of the allocated trace buffer in KB.
PAGE 141
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 291 6.22 MAINCON Panel E2, Telnet VT220 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 2 of 14 --- Protocol Converter (TELNET VT220) --Machine Mode (1,2,3,4).................. VT200 ID (1,2,3,4)...................... User Features (0 = Unlock, 1 = Lock).... Rows & Columns.......................... New Line (CR/CRLF)...................... Margin Bell (On/Off)..............
PAGE 142
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 292 6.22 MAINCON Panel E2, Telnet VT220 (continued) 14. Warning Bell When ‘1’ (ON) is selected, an audible alarm will sound when an operation error occurs or the display station received control-G code. If you select ‘0’ (Off), and then the alarm will not be sounded when error occurs or control-G received. 15.
PAGE 143
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 293 6.22 MAINCON Panel E2, Telnet VT220 (continued) These panels define what is sent to the host when the host requests the Answerback string or a user defined key is sent. Each entry defines the sequence sent for one user defined key or for the answerback string. For example, the user defined key F6 might be defined to send ‘ABCD’ by entering A, B, C and D in the first four fields for the F6 entry in the table.
PAGE 144
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 294 6.22 MAINCON Panel E2, Telnet VT220 (continued) These panels define what is sent to the host when the VT220 terminal is used for 3270 emulation. Each entry defines the sequence sent for a single 3270 key. For example, the 3270 protocol converter attached by the host may be configured to emulate the 3270 Clear key function when it receives the sequence Esc L.
PAGE 145
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 295 6.
PAGE 146
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 296 6.
PAGE 147
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 297 6.
PAGE 148
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 298 6.
PAGE 149
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 299 6.
PAGE 150
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 300 6.23 MAINCON Panel E3 DECNET VT220 Configuration filename: MAINCFG.DN2 Used by cf Device Drivers: # 51 Name CFXDN22 Description DECNET/Pathworks VT220 As of 10/26/93, these drivers are only available in the Windows environment. __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 1 of 14 --- Protocol Converter (DECNET VT220) --Autowrap (0 or 1).......................
PAGE 151
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 301 6.23 MAINCON Panel E3, DECNET VT220 (continued) 5. Trace Size in K bytes Defines the size of the allocated trace buffer in KB. If zero, the trace is disabled. Otherwise, the trace size can be defined up 63K bytes. 6. DECNET Connection Type Leave zero to use any available (fastest); specify 1 to use LAT; 2 to use CTERM; and 3 to use TELNET/BAPI.
PAGE 152
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 302 6.23 MAINCON Panel E3, DECNET VT220 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 2 of 14 --- Protocol Converter (DECNET VT220) --Machine Mode (1,2,3,4).................. VT200 ID (1,2,3,4)...................... User Features (0 = Unlock, 1 = Lock).... Rows & Columns.......................... New Line (CR/CRLF)...................... Margin Bell (On/Off)..............
PAGE 153
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 303 6.23 MAINCON Panel E3, DECNET VT220 (continued) 13. Warning Bell When ‘1’ (ON) is selected, an audible alarm will sound when an operation error occurs or the display station received control-G code. If you select ‘0’ (Off), and then the alarm will not be sounded when error occurs or control-G received. 14.
PAGE 154
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 304 6.23 MAINCON Panel E3, DECNET VT220 (continued) These panels define what is sent to the host when the host requests the Answerback string or a user defined key is sent. Each entry defines the sequence sent for one user defined key or for the answerback string. For example, the user defined key F6 might be defined to send ‘ABCD’ by entering A, B, C and D in the first four fields for the F6 entry in the table.
PAGE 155
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 305 6.23 MAINCON Panel E3, DECNET VT220 (continued) These panels define what is sent to the host when the VT220 terminal is used for 3270 emulation. Each entry defines the sequence sent for a single 3270 key. For example, the 3270 protocol converter attached by the host may be configured to emulate the 3270 Clear key function when it receives the sequence Esc L.
PAGE 156
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 306 6.
PAGE 157
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 307 6.
PAGE 158
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 308 6.
PAGE 159
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 309 6.
PAGE 160
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 310 6.
PAGE 161
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 311 6.24 MAINCON Panel E4 Telnet VT320 Configuration filename: MAINCFG.
PAGE 162
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 312 6.24 MAINCON Panel E4, Telnet VT320 (continued) 4. Half-Duplex Setting this field to ‘1’ will cause the VT220 emulator to operate in half-duplex mode. Half-duplex mode is significantly inferior to full-duplex mode for terminal emulation and data transfer. Full-duplex mode should be used where ever possible. 5. Trace Size in K bytes Defines the size of the allocated trace buffer in KB.
PAGE 163
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 313 6.24 MAINCON Panel E4, Telnet VT320 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 2 of 14 --- Protocol Converter (TELNET VT320) --Machine Mode (1,2,3,4).................. VT300 ID (1,2,3,4,5).................... User Features (0 = Unlock, 1 = Lock).... Rows & Columns.......................... New Line (CR/CRLF)...................... Margin Bell (On/Off)..............
PAGE 164
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 314 6.24 MAINCON Panel E4, Telnet VT320 (continued) 14. Backspace/Del key When ‘1’ is selected, the Backspace key sends an 0x08 (BS). When ‘2’ is selected, the Backspace key is in Delete mode and an 0x7f (DEL) is sent. 15. Warning Bell When ‘1’ (ON) is selected, an audible alarm will sound when an operation error occurs or the display station received control-G code.
PAGE 165
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 315 6.24 MAINCON Panel E4, Telnet VT320 (continued) These panels define what is sent to the host when the host requests the Answerback string or a user defined key is sent. Each entry defines the sequence sent for one user defined key or for the answerback string. For example, the user defined key F6 might be defined to send ‘ABCD’ by entering A, B, C and D in the first four fields for the F6 entry in the table.
PAGE 166
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 316 6.24 MAINCON Panel E4, Telnet VT320 (continued) These panels define what is sent to the host when the VT320 terminal is used for 3270 emulation. Each entry defines the sequence sent for a single 3270 key. For example, the 3270 protocol converter attached by the host may be configured to emulate the 3270 Clear key function when it receives the sequence Esc L.
PAGE 167
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 317 6.
PAGE 168
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 318 6.
PAGE 169
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 319 6.
PAGE 170
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 320 6.
PAGE 171
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 321 6.
PAGE 172
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 322 6.25 MAINCON Panel E5 APPX/TCP Configuration filename: MAINCFG.
PAGE 173
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 323 6.25 MAINCON Panel E5, APPX/TCP (continued) 2. Connect Timeout Defines the time that the driver will wait for the host application to respond to the connect request. The APPX/TCP configuration panels allow for the definition of up to eight configurations for connecting to the host. Each configuration has a “Key” which is used by the application to select which configuration record to use.
PAGE 174
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 324 6.25 MAINCON Panel E5, APPX/TCP (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config ------------- APPX/TCP ----------------Key......... CONFIG #1 Description. Sample Configuration #1 Host Name... cf370.cfsoft.com Port Number. 02500 PGM......... Connect Opt. 2 Connect data Enter 1-16 character key to be used for this configuration record.
PAGE 175
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 325 6.26 MAINCON Panel E6 APPX/TCP - cfPPP Configuration filename: MAINCFG.ATP Used by cf Device Driver: # 131 132 136 Name CFXATPP CFXATPPD CFXATPP3 Description APPX/TCP cfPPP Driver APPX/TCP cfPPP Driver (DOSX) NT-ATCP-PPP APPX/TCP cfPPP Driver (Win32) __________________ __________________ ACROSS-THE-BOARDS(r) Config -----------APPX/TCP - cfPPP------------Trace size in K bytes.........
PAGE 176
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 326 6.26 MAINCON Panel E6, APPX/TCP - cfPPP (continued) To add a new configuration record, tab to the configuration record list and press F2 -- the configuration panel will be displayed. Enter a key and any other required data, then press F10. To delete a configuration record, tab to that configuration record and press F3.
PAGE 177
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 327 6.26 MAINCON Panel E6, APPX/TCP - cfPPP (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config -----------APPX/TCP - cfPPP------------Key......... CONFIG #1 Description. Sample Configuration #1 Host Name... cf370.cfsoft.com Port Number. 02500 PGM......... Connect Opt. 2 Connect data Enter 1-16 character key to be used for this configuration record.
PAGE 178
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 328 6.27 MAINCON Panel E7 TN3270 with TN3287F Support Configuration filename: MAINCFG.TN7 Used by cf Device Driver: # 139 140 Name CFXT7WS3 CFXT7WS3 Description TN3270 w/TN3287 Win32Sockets non-SF TN3270 w/TN3287 Win32Sockets __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 1 of 2 ------ TN3270 with TN3287 Support -----3270 Terminal Model..................... Trace size in K bytes...
PAGE 179
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 329 6.27 MAINCON Panel E7, TN3270 with TN3287 Support (continued) 5. Minimum Response Time option Forces a minimum amount of delay before sending a response to the host. Used to force a more “human” response time. Specified in hundreths of a second, the default is zero. (0-999).
PAGE 180
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 330 6.27 MAINCON Panel E7, TN3270 with TN3287 Support (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config Page 2 of 2 ------ TN3270 with TN3287 Support -----Print routing (in hex).................. Delay Printer Connect................... Autodrop Base Session with Printer...... Allow "CONNECT" for Printer Session..... Search for Missing FMH-1................
PAGE 181
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 331 6.27 MAINCON Panel E7, TN3270 with TN3287 Support (continued) 12. Drop Session with Printer When set to ‘0’, a failure of the printer session will not cause any state change for the base terminal session. When set to ‘1’ a print session failure will cause the base terminal session to drop. 13.
PAGE 182
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 332 6.28 MAINCON Panel E8 Single Session TN5250 Configuration filename: MAINCFG.TN5 Used by cf Device Driver: # 141 Name CFXT5WS3 Description TN5250 Win32Sockets As of this writing (04/19/99), TN5250 drivers are only available in the Win32 environments. __________________ __________________ ACROSS-THE-BOARDS(r) Config -------- Single Session TN5250 --------5250 Terminal Model.....................
PAGE 183
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 333 6.28 MAINCON Panel E8, Single Session TN5250 (continued) 3. Destination Port Number Default port number of Telnet server to connect to. The Well-Known-Port for Telnet (#23) is the default. 4. Telnet TN5250 Disconnect Option ‘0’ (the default) uses normal TN5250 disconnect processing. ‘1’ forces a Telnet disconnect whenever TN5250 mode is ended. 5.
PAGE 184
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 334 6.29 MAINCON Panel F1 PC Support AS/400 Configuration filename: MAINCFG.400 Used by cf Device Driver: # 24 Name CFX400X Description PC Support AS/400 __________________ __________________ ACROSS-THE-BOARDS(r) ---------- PC Support AS/400 Host Session letter (A to E)............ PC Support API interrupt (in hex)....... Keyboard Type (3/5)..................... Screen Attribute Type (3/5).............
PAGE 185
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 335 6.30 MAINCON Panel F2 5250, IBM and AST Configuration filename: MAINCFG.525 Used by cf Device Driver: # 15 19 79 Name CFX525X CFX525A CFX5253 Description 5250 - IBM 5250 - AST Special 5250 for S/36 & ES/3270 __________________ __________________ ACROSS-THE-BOARDS(r) Config ------------ 5250 Emulation -----------5250 Station number..................... 0 Keyboard Type (3/5).....................
PAGE 186
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 336 6.31 MAINCON Panel F3 5250 HLLAPI Configuration filename: MAINCFG.
PAGE 187
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 337 6.31 MAINCON Panel F3, 5250 HLLAPI (continued) 2. Process EABs Some HLLAPI implementations do not support EABs properly. Specify ‘Y’ only if you require EABs. EABs will only be returned if the underlying emulator is configured to return them.
PAGE 188
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 338 6.32 MAINCON Panel G1 Dynacomm Elite LU6.2 Configuration filename: MAINCFG.DE6 Used by cf Device Driver: # 56 Name CFX62DE Description Dynacomm Elite __________________ __________________ ACROSS-THE-BOARDS(r) Config --------- Dynacomm Elite LU6.2 --------Trace size in K bytes......... 0000 Connect timeout (seconds)..... 0000 Default configuration key.....
PAGE 189
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 339 6.32 MAINCON Panel G1, Dynacomm Elite LU6.2 (continued) To modify a configuration record, tab to that configuration record and press F4 -- the configuration panel will be displayed. Modify the record as needed, then press F10. To set the default configuration record, tab to that configuration record and press F5. The key of the current default configuration record is display in the upper part of the panel.
PAGE 190
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 340 6.32 MAINCON Panel G1, Dynacomm Elite LU6.2 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config --------- Dynacomm Elite LU6.2 --------Key......... CONFIG #1 Description. Sample Configuration #1 LU Alias.... PLU Alias... Mode Name... PGM......... User ID..... Password.... Sec. Type...
PAGE 191
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 341 6.33 MAINCON Panel G2 WinCPIC LU6.2 Configuration filename: MAINCFG.WC6 Used by cf Device Driver: # 99 130 Name CFX62WC CFX62WC3 Description WinCPIC LU6.2 (Win16) WinCPIC LU6.2 (Win32) __________________ __________________ ACROSS-THE-BOARDS(r) ----------- Config WinCPIC LU6.2 ------------- Trace size in K bytes......... 0000 Connect timeout (seconds)..... 0000 Default configuration key.....
PAGE 192
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 342 6.33 MAINCON Panel G2, WinCPIC LU6.2 (continued) To modify a configuration record, tab to that configuration record and press F4 -- the configuration panel will be displayed. Modify the record as needed, then press F10. To set the default configuration record, tab to that configuration record and press F5. The key of the current default configuration record is display in the upper part of the panel.
PAGE 193
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 343 6.33 MAINCON Panel G2, WinCPIC LU6.2 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) ----------- Config WinCPIC LU6.2 ------------- Key......... CONFIG #1 Description. Sample Configuration #1 PLU Alias... Mode Name... PGM......... Side Info... User ID..... Password.... Sec. Type...
PAGE 194
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 344 6.34 MAINCON Panel G3 Personal Comm LU6.2 NT/95 Configuration filename: MAINCFG.NS7 Used by cf Device Driver: # 133 Name CFX62NS3 Description PCOM/Network Services for Win32 CPIC __________________ __________________ ACROSS-THE-BOARDS(r) Config ------ Personal Comm LU6.2 NT/95 ------Trace size in K bytes......... 0000 Connect timeout (seconds)..... 0000 Default configuration key.....
PAGE 195
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 345 6.34 MAINCON Panel G3, Personal Comm LU6.2 NT/95 (continued) To modify a configuration record, tab to that configuration record and press F4  the configuration panel will be displayed. Modify the record as needed, then press F10. To set the default configuration record, tab to that configuration record and press F5.
PAGE 196
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 346 6.34 MAINCON Panel G3, Personal Comm LU6.2 NT/95 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config ------ Personal Comm LU6.2 NT/95 ------Key......... CONFIG #1 Description. Sample Configuration #1 PLU Alias... Mode Name... PGM......... Side Info... User ID..... Password.... Sec. Type...
PAGE 197
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 347 6.35 MAINCON Panel G4 Extra! LU6.2 NT/95 Configuration filename: MAINCFG.EP7 Used by cf Device Driver: # 134 Name CFX62EP3 Description Extra! for Win32 CPIC __________________ __________________ ACROSS-THE-BOARDS(r) Config ---------- Extra! LU6.2 NT/95 ---------Trace size in K bytes......... 0000 Connect timeout (seconds)..... 0000 Default configuration key.....
PAGE 198
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 348 6.35 MAINCON Panel G4, Extra! LU6.2 NT/95 (continued) To modify a configuration record, tab to that configuration record and press F4 -- the configuration panel will be displayed. Modify the record as needed, then press F10. To set the default configuration record, tab to that configuration record and press F5. The key of the current default configuration record is display in the upper part of the panel.
PAGE 199
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 349 6.35 MAINCON Panel G4, Extra! LU6.2 NT/95 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config ---------- Extra! LU6.2 NT/95 ---------Key......... CONFIG #1 Description. Sample Configuration #1 PLU Alias... Mode Name... PGM......... Side Info... User ID..... Password.... Sec. Type...
PAGE 200
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 350 6.36 MAINCON Panel G5 Rumba LU6.2 NT/95 Configuration filename: MAINCFG.RU7 Used by cf Device Driver: # 135 Name CFX62RU3 Description Rumba for Win32 CPIC __________________ __________________ ACROSS-THE-BOARDS(r) Config ---------- Rumba LU6.2 NT/95 ----------Trace size in K bytes......... 0000 Connect timeout (seconds)..... 0000 Default configuration key.....
PAGE 201
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 351 6.36 MAINCON Panel G5, Rumba LU6.2 NT/95 (continued) To modify a configuration record, tab to that configuration record and press F4 -- the configuration panel will be displayed. Modify the record as needed, then press F10. To set the default configuration record, tab to that configuration record and press F5. The key of the current default configuration record is display in the upper part of the panel.
PAGE 202
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 352 6.36 MAINCON Panel G5, Rumba LU6.2 NT/95 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config ---------- Rumba LU6.2 NT/95 ----------Key......... CONFIG #1 Description. Sample Configuration #1 PLU Alias... Mode Name... PGM......... Side Info... User ID..... Password.... Sec. Type...
PAGE 203
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 353 6.37 MAINCON Panel G6 WinAPPC LU6.2 Configuration filename: MAINCFG.SS7 Used by cf Device Driver: # 137 Name CFX62SS3 Description SNA Server APPC Driver (Win32) __________________ __________________ ACROSS-THE-BOARDS(r) ----------- Config WinAPPC LU6.2 ------------- Trace size in K bytes......... 0000 Connect timeout (seconds)..... 0000 Default configuration key.....
PAGE 204
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 354 6.37 MAINCON Panel G6, WinAPPC LU6.2 (continued) To modify a configuration record, tab to that configuration record and press F4 -- the configuration panel will be displayed. Modify the record as needed, then press F10. To set the default configuration record, tab to that configuration record and press F5. The key of the current default configuration record is display in the upper part of the panel.
PAGE 205
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 355 6.37 MAINCON Panel G6, WinAPPC LU6.2 (continued) __________________ __________________ ACROSS-THE-BOARDS(r) ----------- Config WinAPPC LU6.2 ------------- Key......... CONFIG #1 Description. Sample Configuration #1 LU Alias.... PLU Alias... Mode Name... PGM......... User ID..... Password.... Sec. Type...
PAGE 206
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 356 6.38 MAINCON Panel G7 Personal Comm LU6.2 NT/95 APPC Configuration filename: MAINCFG.IB7 Used by cf Device Driver: # 138 Name CFX62IB3 Description IBM PCOM APPC Driver (Win32) __________________ __________________ ACROSS-THE-BOARDS(r) Config ---- Personal Comm LU6.2 NT/95 APPC ---Trace size in K bytes......... 0000 Connect timeout (seconds)..... 0000 Default configuration key.....
PAGE 207
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 357 6.38 MAINCON Panel G7, Personal Comm LU6.2 NT/95 APPC (continued) To modify a configuration record, tab to that configuration record and press F4 -- the configuration panel will be displayed. Modify the record as needed, then press F10. To set the default configuration record, tab to that configuration record and press F5.
PAGE 208
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 358 6.38 MAINCON Panel G7, Personal Comm LU6.2 NT/95 APPC (continued) __________________ __________________ ACROSS-THE-BOARDS(r) Config ---- Personal Comm LU6.2 NT/95 APPC ---Key......... CONFIG #1 Description. Sample Configuration #1 LU Alias.... PLU Alias... Mode Name... PGM......... User ID..... Password.... Sec. Type...
PAGE 209
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 359 6.39 MAINCON Panel X1 CFMPIPE Driver Configuration filename: MAINCFG.CMP Used by cf Device Driver: # 149 Name CFXCFMP3 Description CFMP Driver for TPNS Handling __________________ __________________ ACROSS-THE-BOARDS(r) Config ----------- cfMEMPIPE Driver ----------Trace size in K bytes................... 0 Connect timeout (seconds)...............
PAGE 210
Across the Boards Communications Device Drivers Section 6 - MAINCON Driver Configuration Page 360 cfSOFTWARE Confidential, 2000
PAGE 211
Across the Boards Communications Device Drivers Miscellaneous Topics Page 361 Section 7 - Miscellaneous Topics 7.1 Rational Systems DOS Extender This DOS extender has been used to implement ATB/DOS in a environment where the application is in protected mode, and the ATB modules are loaded in real mode with a mode switch occuring under the applications control. A problem is that Rational Systems DOS Extender makes the switch and leaves interrupts disabled. This causes the VTIC calibrate to hang.
PAGE 212
Across the Boards Communications Device Drivers Miscellaneous Topics Page 362 7.2 WATCOM C The WATCOM C compiler does not, by default, use standard Microsoft C calling conventions. It can be forced to generate MS C style calls on a routine-by-routine basis, however.
PAGE 213
Across the Boards Communications Device Drivers Miscellaneous Topics Page 363 7.3 Language Translation Considerations The following known peculiarities exist with regard to APPX’s internal “variable 10” and the “extras”. 1. Languages 4, 5, 7, and S (German, Italian, Brazilian, and Finnish/Swedish) include the carat (^ ASCII 5EH) in their Var-10. This character is generally mistranslated by Cut-mode drivers to a not sign (ª ASCII AAH). This is likely to be common with HLLAPI-based configurations also.
PAGE 214
Across the Boards Communications Device Drivers Miscellaneous Topics Page 364 7.4 Year 2000 Date Handling in Across the Boards Correct handling of the century change in 1999/2000 is a concern to many mainframe installations. Across the Boards has few date dependencies, and applications will have few, if any, problems with the year 2000 related to Across the Boards. The date handling in the various Across the Boards modules is summarized below. XAPI No date dependencies.
PAGE 215
Across the Boards Communications Device Drivers Miscellaneous Topics Page 365 7.5 MAINCON ASCII Characters Several configuration panels in MAINCON allow the coding of strings of ASCII character sequences. In these locations MAINCON accepts several types of entries: - Displayable characters - Control characters - Hex values - ASCII Mnemonics - “BRK” (see description) There is more than one possible coding for each ASCII character.
PAGE 216
Across the Boards Communications Device Drivers Miscellaneous Topics Page 366 7.5 MAINCON ASCII Characters (continued) Control Characters The ASCII characters in the range 01h through 1Fh have standard control character assignments. For example, pressing “Ctrl-A” on the keyboard generates an ASCII 01H character. A control character may be entered by prefixing the displayable character with a “^”. For example, “Ctrl-A” would be coded as “^A”.
PAGE 217
Across the Boards Communications Device Drivers Miscellaneous Topics Page 367 7.
PAGE 218
Across the Boards Communications Device Drivers Miscellaneous Topics Page 368 cfSOFTWARE Confidential, 2000
PAGE 219
Across the Boards Communications Device Drivers Miscellaneous Topics Page 369 Device Index 3 3174....................................................................................................11, 12, 28, 50, 56, 57, 58, 79, 129, 177, 237 3270PC .................................................................................................................................................................21 3274............................................................................................
PAGE 220
Across the Boards Communications Device Drivers Device Index Page 370 Attachmate Extra! LU6.2 NT/95 ....................................................................................................................... 347 Attachmate Extra! Personal Client....................................................................................................................... 66 Attachmate for Windows ...........................................................................................................
PAGE 221
Across the Boards Communications Device Drivers Miscellaneous Topics Page 371 CFXCA403.............................................................................................................................................5, 170, 191 CFXCFMP3....................................................................................................................................5, 175, 191, 359 CFXCMG5 ..........................................................................................................
PAGE 222
Across the Boards Communications Device Drivers Device Index Page 372 CFXSWTC ................................................................................................................................................ 157, 203 CFXT2FO.............................................................................................................................................. 4, 118, 289 CFXT2FT ............................................................................................................
PAGE 223
Across the Boards Communications Device Drivers Miscellaneous Topics Page 373 DCA/Irma ......................................................................................................................................... See Irma/DCA DEC VT100....................................................................................................................... See Protocol Converters DEC VT220..............................................................................................................
PAGE 224
Across the Boards Communications Device Drivers Device Index Page 374 FTP PC/TCP.................................... See APPX/TCP. See Telnet VT320. See Telnet VT220. See Telnet TN3270 Version 2.20 ............................................................................................................... 85–86, 90, 133–34, 144 FTP PC/TCP for OS/2 Version 1.30 ...............................................................................................................................
PAGE 225
Across the Boards Communications Device Drivers Miscellaneous Topics Page 375 IBM Workstation Software Version 1.00 ..................................................................................................................................................21 Version 1.10 ..................................................................................................................................................21 Version 1.12 ......................................................................
PAGE 226
Across the Boards Communications Device Drivers Device Index Page 376 M MainLink II.......................................................................................................................................................... 25 Memorex 3278 coax card .................................................................................................................................... 22 Memorex Telex.................................................................................................
PAGE 227
Across the Boards Communications Device Drivers Miscellaneous Topics Page 377 Novell LAN Workplace for DOS ...................................................................................................................82, 87 Version 4.01 ............................................................................................................................82, 87, 130, 140 Novell LAN Workplace for OS/2 Version 3.0B ....................................................................................
PAGE 228
Across the Boards Communications Device Drivers Device Index Page 378 PC/NFS non-SF ........................................................................................................................ See Telnet TN3270 PCI..................................................................................................................................... See Protocol Converters PCI 1076......................................................................................................................
PAGE 229
Across the Boards Communications Device Drivers Miscellaneous Topics Page 379 RabbitGATE/RabbitSTATION ............................................................................................................................36 RabbitLAN Version 5.30 (DOS).......................................................................................................................................41 Rally (replaces Irma 5250) Version 2.00 ..........................................................................
PAGE 230
Across the Boards Communications Device Drivers Device Index Page 380 Sun PC/NFS......................................................................................................................................................... 83 Version 5.00 ....................................................................................................... 83, 85, 88, 90, 131, 133, 141 SYNC-UP modem+3274 emulation .................................................................................................
PAGE 231
Across the Boards Communications Device Drivers Miscellaneous Topics Page 381 WOW VT220 Async ..........................................................................................................................................263 WOW VT320 .....................................................................................................................................................139 WOW VT320 Async ...............................................................................................
PAGE 232
Across the Boards Communications Device Drivers Device Index Page 382 cfSOFTWARE Confidential, 2000