A fix is available
APAR status
Closed as program error.
Error description
When starting TCP/IP with NSC HyperChannel devices as gateway following message: EZZ4308I ERROR: CODE=80103332 DURING ACTIVATION OF DEVICE DXEA2. DIAGNOSTIC CODE: 02 Also seen EZZ4202I OPENEDITION-TCP/IP CONNECTION ESTABLISHED FOR TCPIP EZZ4308I ERROR: CODE=80100041 DURING ACTIVATION OF DEVICE DXEA1. DIAGNOSTIC CODE: 02 IST1578I SOFT INOP DETECTED FOR IUTH0140 BY ISTTCCTI CODE = 100 IST1578I SOFT INOP DETECTED FOR IUTL4100 BY ISTTCCTA CODE = 101
Local fix
The HyperChannel device must be defined to MVS as either a CTC/SCTC or 3745 device. Because of the difference in UCB structures, 2703 is not supported.
Problem summary
**************************************************************** * USERS AFFECTED: All TCP/IP Users of HYPERchannel DLC. * **************************************************************** * PROBLEM DESCRIPTION: Either * * EZZ4308I ERROR: CODE=80103332, * * or * * EZZ4308I ERROR: CODE=80100041 * * IST1578I SOFT INOP DETECTED FOR * * IUTHnnnn BY ISTTCCTI CODE = 100 * * are seen during activation of * * HYPERchannel devices. * **************************************************************** * RECOMMENDATION: * **************************************************************** The first problem, with CODE=80103332 (the meaning of this IUTSTAFD code is "Invalid Channel ID") occurs when a TCP user of the HYPERchannel DLC attempts to activate a connection, and the HYPERchannel device is not defined to MVS as a CTC device. ISTINMAV fails the activation upon seeing that the UCBDVCLS field in the UCB does not match the value X'41'. In the second problem, with CODE=80100041, the HYPERchannel device is defined as a CTC device, so ISTINMAV validates its UCB and allocates the device. However, when the Initialization channel program is issued (a Sense Statistics CCW), an ATTention interrupt is received with either DeviceEnd+ControlUnitEnd (DE+CUE), or DE+CUE+Busy. The PUPAB interrupt handler, ISTTCCTI, does not recognize this as a valid CSW status, and it generates a connection INOP, failing the activation.
Problem conclusion
VTAM is changed to permit defining the HYPERchannel device as either a CTC device or as a 3745. These changes consist of having module ISTINMAV recognize either X'40' or X'41' as a valid value for the UCB device class. If the value is X'40', a specific set of device types is checked for in the UCBTBYT4 field: X'15', X'25', or X'F1'. These three values are chosen because the UIMs provided by OS/390 for these devices are the only ones that generate the device-dependent segment (IECDUCBE) for communications devices. This device-dependent segment is required by VTAM channel end appendage interface to support the device. The NSC Hyperchannel documentation recommends that the device be defined to MVS as either a 3705 or a 3745. Their suggested definitions are shown below: For the 3705: CNTLUNIT CUNUMBR=CCCC, PATH=PP, SHARED=N, UNIT=3705, UNITADD=((BB,NN)), PROTOCOL=S4, LINK=(SS), CUADD=(L) IODEVICE ADDRESS=(DDDD,NN), UNIT=BSC1, UNITADD=(BB,NN) ADAPTER=BSCA, TCU=270X, CUNUMBR=CCCC, PART=NAME For the 3745: CNTLUNIT CUNUMBR=CCCC, PATH=PP, SHARED=N, UNIT=3745, UNITADD=((BB,NN)), PROTOCOL=S4, LINK=(SS), CUADD=(L) IODEVICE ADDRESS=(DDDD,NN), UNIT=3745, UNITADD=(BB,NN) ADAPTER=CA1, CUNUMBR=CCCC, PART=NAME The 3705 definition (otherwise known as a 2703 definition becuase of the TCU=270X parameter (where X can be 1,2,or 3) on the IODEVICE statement) cannot be supported by VTAM because the UIM for that device does not cause the UCB to contain the required device-dependent segment. Therefore, if a customer currently has a HYPERchannel device defined as a 3705 (TCU=270x) device, they must redefine it either as a 3745, as recommended by NSC, or as a CTC device. As part of the 3745 definition support, VTAM must provide its own ERP routine, so existing module ISTZBM0K is specified for that purpose, and is changed to support HYPERchannel as well as CDLC. Finally, ISTTCCTA is changed to ignore the DE+CUE and DE+CUE+BSY conditions during the initialization phase. These are transient conditions that are followed by CE+DE.
Temporary fix
Comments
APAR Information
APAR number
OW35545
Reported component name
VTAM V4 MVS/ESA
Reported component ID
569511701
Reported release
411
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1998-10-02
Closed date
1999-03-05
Last modified date
1999-04-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UW57052 UW57053 UW57054
Modules/Macros
ISTINMAV ISTTCCTA ISTZBM0K
Fix information
Fixed component name
VTAM V4 MVS/ESA
Fixed component ID
569511701
Applicable component levels
R411 PSY UW57052
UP99/03/19 P F903
R501 PSY UW57053
UP99/03/19 P F903
R701 PSY UW57054
UP99/03/19 P F903
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"411","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"411","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 April 1999