Patch-ID# 101432-05 Keywords: mandatory SunLink 8.0 BSC3270 stopbsc ASCII enterstr zsb newline Synopsis: SunLink BSC3270 8.0: Jumbo patch Date: Jan/30/97 Solaris Release: 2.x SunOS Release: 5.x Unbundled Product: SunLink BSC3270 Unbundled Release: 8.0 Relevant Architectures: sparc BugId's fixed with this patch: 1122891 1145905 1147412 1151201 1154760 1158980 1159424 1170057 1199397 1202527 1224261 1248122 1261873 1262652 Changes incorporated in this version: 1248122 1261873 1262652 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: 102062 NOTE: patch is required for Solaris 2.4 Obsoleted by: Files included with this patch: A new postinstall script called 'postinstall' which gets executed after the install of this patch package. SUNWbsccu/reloc/SUNWconn/bsc3270/stopbsc SUNWbsccu/reloc/SUNWconn/bsc3270/bsc3274 SUNWbscdr/root/kernel/drv/zsb SUNWbscdr/root/kernel/drv/zsb_2.4 SUNWbscdr/root/kernel/drv/zsb_2.5 SUNWbscdr/root/kernel/strmod/bscbp SUNWbscdr/root/kernel/strmod/bscct SUNWbscdr/root/kernel/strmod/bsclm Problem Description: (Rev 05) -------- 1248122: System Loaded with BSC3270 v8.0 encounters repeated DATA FAUL TRAP 1261873: BSC Line Monitor PANIC PC_ULM 1262652: 4 system hangs within a short period 1248122: kernel Data Fault off tcp_wput ( Bisync 3270 GW installed ) (Rev 04) -------- 1199397: BSC 3270 clients unable to send AID key after BSC line error recovery The BSC 3270 line driver was failing to recover completely from the line timing out after 20 seconds without carrier (error 532). If a 3270 client hit an AID key during the 20 second window between the initial loss of carrier and the error 532 status, then after carrier resumed and the error status was cleared the line driver would ignore all AID keys, although the host could still write to the clients. 1202527: BSC 3270 8.0 does not work on Solaris 2.4 with zs patch 102062-03 A change had been made to the include file zsdev.h, which is shared between zs and zsb. It was necessary to re-compile the zsb driver with the latest version of zsdev.h so that it would be compatible with patch 102062-03. 1224261: panic in bsc3270: "ctczec: bad size" bsc3270 was panicking with a "ctczec: bad size" message when it detected an internal error. A change was made so that we would not panic in this situation. Instead, we will log a console message. In addition, we will send a "408" status code to the status line of the te3278 session of the user to whom the 3270 data was addressed. other modifications: BSC 3270 8.0 and Solaris 2.5 A change had been made to the include file zsdev.h, which is shared between zs and zsb. It was necessary to re-compile the zsb driver with the latest version of zsdev.h so that it would be compatible with Solaris 2.5. (Rev 03) -------- 1170057: System panics when BSC gateway started on 2.4 As soon as the BSC 3270 gateway was started on a Solaris 2.4 system, the zsb driver panic'd the kernel. The struct zscom has been changed in an incompatible manner between Solaris 2.3 and Solaris 2.4. This patch includes two versions of the zsb driver. The postinstall script examines the Solaris release and installs the appropriate version. The include files and are required to be included last and in that order by drivers. Most of the .c files for the BSC driver and STREAMS modules were updated to make sure that they followed this rule. The #define STR_CLONE in zs_bsc.h conflicts with , so added ZBSC_STATE_ prefix to state names. In cpdat() in bpxzec.c and ctsndw in ctsndw.c, added cast of parms to bcopy() calls. (Rev 02) -------- 1154760: get status >402< when try to connect over bsc3270 8.0 ascii When more than 128 bytes was written to a 3270 terminal over an ASCII Bisync line, only the first 128 bytes were translated from ASCII to EBCDIC. This caused the 3270 data stream to conain invalid characters, resulting in an error code of 402 (invalid address for 3270 order). 1158980: SC1000 running 2.3 is crashing in zsb driver An SC1000 with 4 cpus was getting a kernel panic in zsb_softint(), which is in the ZSB driver for BSC3270 8.0. Two threads were updating a field at the same time, resulting in a data fault. 1159424: pe3287 converts ebcdic 0x25 (LineFeed) to 0x2d (dash) This is an ASCII Bisync line bug. A mainframe file (in EBCDIC) sent to the printer contains a x'15' NL character. The mainframe's 370x will translate that to an ASCII x'0A' LF, because there is no NL character defined in ASCII and LF is the closest equivalent. Note that the EBCDIC x'25' LF also is translated to ASCII x'0A' LF. The 8.0 BSC3270 line driver translates ASCII Bisync line data to EBCDIC. The ASCII x'0A' LF is translated to EBCDIC x'25' LF. This is desirable if the original EBCDIC character was a LF, but not if it was a NL. When pe3287 is formatting the printer data, it acts upon the control codes, and translates the normal data from EBCDIC to ASCII. Characters that are not supported by an IBM 3287 are translated to the '-' (dash) character. The EBCDIC x'25' LF character is neither a valid 3287 DSC mode printer control code nor a valid 3287 printable character. The Bisync line driver has been changed to translate ASCII x'0A' LF/NL to EBCDIC x'15' NL. (Rev 01) -------- 1122891: "bsclm_timer" system errors at console when test against an ASCII line BSC3270 8.0 does not support ASCII character set transmission on the line. 1145905: enterstr leavestr were removed from 1093 causing BSC3270 8.0 failure Entry points enterstr and leavestr were removed from Solaris 2.3 causing the BSC3270 8.0 installation process to fail in the zsb driver. 1147412: stopsna and stopsnarje commands will not find any gateways The "stopbsc" command will not find any gateways, even if a BSC3270 gateway is active. The problem is that the output of the "ps -ef" command was modified in Solaris 2.3. 1151201: BSC3270 fails on Sun4 due to older version of SCC serial comm IC Patch Installation Instructions: -------------------------------- Special Install Instructions: ----------------------------- You must reboot after installing this patch. Note: Please don't use the "ibmftp" function as described under bug id 1150305. It will crash and cause kernel panics quite often. It may be fixed by the next patch. BSC 3270 8.0 ASCII Line Support - Installation and Release Notes: This upgrade allows the BSC 3270 8.0 gateway to communicate with the host in ASCII as well as EBCDIC. The ASCII protocol is defined by IBM in their publication "IBM 3270 Information Display System - 3274 Control Unit Description and Programmer's Guide", document # GA23-0061-1. The ASCII line uses seven data bits, odd parity, with a single byte LRC (exclusive or) check character. Because transparency is not supported on the ASCII line, IBM 3270 operations requiring "Structured Field" records are not supported. See notes below concerning the ASCII to/from EBCDIC character set translations. Configure the gateway per instructions in Chapter 2 of the "SunLink BSC 3270 8.0 System Administrators Guide. The following variations apply: a. The control unit poll and select address are the same with ASCII as with EBCDIC, since the decoding is done after the line data is translated from ASCII to EBCDIC. These addresses are described in the IBM 3274 Control Unit Description manual stated above and are repeated here for reference. Note that the actual ASCII characters on the line are different, but cannot be used when configuring the gateway. Use the EBCDIC codes instead. ASCII Code EBCDIC code (use for configuration) Control Unit # Poll Select Poll Select -------------- ---- ------ ---- ------ 0 20 2D 40 60 1 41 2F C1 61 2 42 53 C2 E2 3 43 54 C3 E3 4 44 55 C4 E4 5 45 56 C5 E5 6 46 57 C6 E6 7 47 58 C7 E7 8 48 59 C8 E8 9 49 5A C9 E9 10 5B 7C 4A 6A 11 2E 2C 4B 6B 12 3C 25 4C 6C 13 28 5F 4D 6D 14 2B 3E 4E 6E 15 21 3F 4F 6F 16 26 30 50 F0 17 4A 31 D1 F1 18 4B 32 D2 F2 19 4C 33 D3 F3 20 4D 34 D4 F4 21 4E 35 D5 F5 22 4F 36 D6 F6 23 50 37 D7 F7 24 51 38 D8 F8 25 52 39 D9 F9 26 5D 3A 5A 7A 27 24 23 5B 7B 28 2A 40 5C 7C 29 29 27 5D 7D 30 3B 3D 5E 7E 31 5E 22 5F 7F b. Choose the ASCII character set. c. Ignore the parity choice or use "don't care". The parity is defined by IBM to be odd parity, and the parity choice is ignored by the gateway. d. Choose at least 3, preferably 5 leading SYNC characters. The default is two, and the default choice leads to erratic operation in some environments. e. All other options are the same with ASCII as with EBCDIC code. After configuring the gateway, proceed to start the gateway as described in chapter 3 of the System Administrator's Guide. CHARACTER SET: Some notes about the character set translations are in order here. Most BSC 3270 applications use EBCDIC code on the transmission line, and the SunLink BSC 3270 gateway internally processes all data using the EBCDIC character set. The client processes, such as TE-3278, CG-3270, or PE-3287, then translate the EBCDIC code data from the gateway to ASCII for presentation to the user via terminal emulation window, keyboard data entry or printing. The client processes each have a way to customize the EBCDIC to ASCII translation, so that character set differences and internationalization can be accomodated. For instance, chapter 9 "Localizing Client 3270" of the "SunLink Client 3270 8.0 User's Guide" describes how to modify the EBCDIC to ASCII character set translations for Client 3270 processes. Similar techniques exist for CG-3270 8.0. The translation from ASCII character set used on the transmission line to the EBCDIC code used internally by the BSC 3270 gateway is done by a fixed set of tables that cannot be modified by the user. No modification of these tables is allowed, because modifications could impact how buffer addresses and other control items are decoded in the 3270 data stream. The ASCII on the transmission line to gateway internal EBCDIC translation is defined by IBM for the 3270 and SunLink BSC 3270 conforms to that definition. This translation is less than optimum, in that, for instance, the "!" character gets translated into a "]" rather than into another "!" character, but these cannot be changed without upsetting the 3270 data stream interpretations. The user, however, is free to adjust the EBCDIC to ASCII translations as desired, and any changes to the character set translations must be made at that level. The ASCII line code to gateway internal EBCDIC translation tables coded into the BSC 3270 8.0 gateway are provided below for reference. EBCDIC characters undefined in ASCII are translated into "-", hex 2D as defined in IBM 3270 specification. /* ASCII to EBCDIC translation table*/ /* 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |*/ /* 00 */ 0x00, 0x01, 0x02, 0x03, 0x37, 0x2d, 0x2e, 0x2f, /* 08 */ 0x16, 0x05, 0x15, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f, /* 10 */ 0x10, 0x11, 0x12, 0x13, 0x3c, 0x3d, 0x32, 0x26, /* 18 */ 0x18, 0x19, 0x3f, 0x27, 0x1c, 0x1d, 0x1e, 0x1f, /* 20 */ 0x40, 0x4f, 0x7f, 0x7b, 0x5b, 0x6c, 0x50, 0x7d, /* 28 */ 0x4d, 0x5d, 0x5c, 0x4e, 0x6b, 0x60, 0x4b, 0x61, /* 30 */ 0xf0, 0xf1, 0xf2, 0xf3, 0xf4, 0xf5, 0xf6, 0xf7, /* 38 */ 0xf8, 0xf9, 0x7a, 0x5e, 0x4c, 0x7e, 0x6e, 0x6f, /* 40 */ 0x7c, 0xc1, 0xc2, 0xc3, 0xc4, 0xc5, 0xc6, 0xc7, /* 48 */ 0xc8, 0xc9, 0xd1, 0xd2, 0xd3, 0xd4, 0xd5, 0xd6, /* 50 */ 0xd7, 0xd8, 0xd9, 0xe2, 0xe3, 0xe4, 0xe5, 0xe6, /* 58 */ 0xe7, 0xe8, 0xe9, 0x4a, 0xe0, 0x5a, 0x5f, 0x6d, /* 60 */ 0x79, 0x81, 0x82, 0x83, 0x84, 0x85, 0x86, 0x87, /* 68 */ 0x88, 0x89, 0x91, 0x92, 0x93, 0x94, 0x95, 0x96, /* 70 */ 0x97, 0x98, 0x99, 0xa2, 0xa3, 0xa4, 0xa5, 0xa6, /* 78 */ 0xa7, 0xa8, 0xa9, 0xc0, 0x6a, 0xd0, 0xa1, 0x07 /* EBCDIC to ASCII translation table*/ /* 0 1 2 3 4 5 6 7 */ /* 00 */ 0x00, 0x01, 0x02, 0x03, 0x2d, 0x09, 0x2d, 0x7f, /* 08 */ 0x2d, 0x2d, 0x2d, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f, /* 10 */ 0x10, 0x11, 0x12, 0x13, 0x2d, 0x0a, 0x08, 0x2d, /* 18 */ 0x18, 0x19, 0x2d, 0x2d, 0x1c, 0x1d, 0x1e, 0x1f, /* 20 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x0a, 0x17, 0x1b, /* 28 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x05, 0x06, 0x07, /* 30 */ 0x2d, 0x2d, 0x16, 0x2d, 0x2d, 0x2d, 0x2d, 0x04, /* 38 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x14, 0x15, 0x2d, 0x1a, /* 40 */ 0x20, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 48 */ 0x2d, 0x2d, 0x5b, 0x2e, 0x3c, 0x28, 0x2b, 0x21, /* 50 */ 0x26, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 58 */ 0x2d, 0x2d, 0x5d, 0x24, 0x2a, 0x29, 0x3b, 0x5e, /* 60 */ 0x2d, 0x2f, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 68 */ 0x2d, 0x2d, 0x7c, 0x2c, 0x25, 0x5f, 0x3e, 0x3f, /* 70 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 78 */ 0x2d, 0x60, 0x3a, 0x23, 0x40, 0x27, 0x3d, 0x22, /* 80 */ 0x2d, 0x61, 0x62, 0x63, 0x64, 0x65, 0x66, 0x67, /* 88 */ 0x68, 0x69, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* 90 */ 0x2d, 0x6a, 0x6b, 0x6c, 0x6d, 0x6e, 0x6f, 0x70, /* 98 */ 0x71, 0x72, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* a0 */ 0x2d, 0x7e, 0x73, 0x74, 0x75, 0x76, 0x77, 0x78, /* a8 */ 0x79, 0x7a, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* b0 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* b8 */ 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* c0 */ 0x7b, 0x41, 0x42, 0x43, 0x44, 0x45, 0x46, 0x47, /* c8 */ 0x48, 0x49, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* d0 */ 0x7d, 0x4a, 0x4b, 0x4c, 0x4d, 0x4e, 0x4f, 0x50, /* d8 */ 0x51, 0x52, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* e0 */ 0x5c, 0x2d, 0x53, 0x54, 0x55, 0x56, 0x57, 0x58, /* e8 */ 0x59, 0x5a, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, /* f0 */ 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, /* f8 */ 0x38, 0x39, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d, 0x2d