A fix is available
APAR status
Closed as program error.
Error description
Enterprise Extender connection is being initiated by a Cisco router and receive BF-TG error with SENSE 08090000. IST1576I DYNAMIC SWITCHED MAJOR NODE ISTDSWMN CREATED IST1085I BF-TG ACTIVATION ERROR CP xxxx.xxxxxx SENSE = 08090000 IST381I REQCONT FOR ID = CNV00003 FAILED - CANNOT DEFINE NODE IST680I CONNECTION REQUEST DENIED - ID = xxxxxx INVALID NETWORK NAME
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All zOS Communication Server V1R2 users of * * Enterprise Extender connections. * **************************************************************** * PROBLEM DESCRIPTION: Enterprise Extender connection * * being initiated from a Cisco * * router fails with BF-TG error * * with SENSE 08090000 * **************************************************************** * RECOMMENDATION: * **************************************************************** An Enterprise Extender (EE) connection being initiated from a Cisco router fails when attempting to use an EE connection network. Message IST1085I will be received indicating a BF-TG error has been received with a sense code of 08090000. In addition an IST381I or IST1267I message will be displayed on the host indicating that the REQCONT command has failed. For z/OS V1R2 it was decided to require a specific type of EE line to be available for a dial-in connection. Therefore, when a host dials another host for an EE line initiation, the XID received is examined to determine what type of EE connection is being activated (EE Connection Network (Global or Local) or non-EE connection network). An appropriate line is selected from one of the defined GROUPs, within the XCA major node. The problem is that the Cisco router always sends a null XID in their EE connection initiation. This causes VTAM to always select a non-connection network line. VTAM will then respond with a pre-negotiation XID. At this time, the line is then associated with the other EE endpoint. The Cisco router will then send a pre-negotaion XID. If a connection network is being used the CV4680 will have the V4680LCN bit set on. The EE PU PAB (associated with the EE non-connection network line) will be dispatched with the prenegotiation XID and will build a REQCONT signal. This signal will be forwarded through PUNS to the Configuration Services (CS) layer. During REQCONT processing, module ISTACCQ3 will invoke ISTACCNP for TG negotiation. ISTACCNP will notice that the line selected, EE non-connection network, does not match the criteria received on the REQCONT signal. The REQCONT is then rejected with the following error messages: IST1576I DYNAMIC SWITCHED MAJOR NODE ISTDSWMN CREATED IST1085I BF-TG ACTIVATION ERROR CP xxxx.xxxxxx SENSE = 08090000 IST381I REQCONT FOR ID = xxxxxxxx FAILED - CANNOT DEFINE NODE IST680I CONNECTION REQUEST DENIED - ID = xxxxxx INVALID NETWORK NAME
Problem conclusion
The following modules/macros have been changed: IPTTIMER - Has been changed so allow an RPH to be specified on the generated TPWAIT macro. ISTIPNCB - Defined new bit, IPNCB_NONCN_LINK, to indicate at least one non-connection network line has been activated. Bit IPNCB_DEAD_PORT has been redefined to be ABNL. ISTAUCAL - Has been changed to allocate the T1 and TL timer (ISTHTMBK) controls blocks within the ISTAUNCB itself. Code has also been added to turn bit IPNCB_NONCN_LINK on when a non-connection network line is being activated. ISTAUCDL - Changed to no longer free the T1 and TL timers, as they are now contained within the AUNCB. ISTAUCII - Changed to correct line association for Cisco EE VRN partner. ISTAUNCB - Defined new bit, AUNCB_NULL_XID_RCVD, to indicate a null XID has been received from EE partner. ISTAUCOA - Both modules have been recompile only to pick up ISTAUCPF IPNCB_DEAD_PORT definition change. Module ISTAUCLA has been included for maintenance purposes.
Temporary fix
Comments
APAR Information
APAR number
OW52458
Reported component name
VTAM V4 MVS/ESA
Reported component ID
569511701
Reported release
120
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2001-12-03
Closed date
2002-02-08
Last modified date
2002-05-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UW86344
Modules/Macros
IPTTIMER ISTAUCAL ISTAUCDL ISTAUCII ISTAUCLA ISTAUCOA ISTAUCPF ISTAUNCB ISTIPNCB
Fix information
Fixed component name
VTAM V4 MVS/ESA
Fixed component ID
569511701
Applicable component levels
R120 PSY UW86344
UP02/03/26 P F203
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":"120","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":"120","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
17 May 2002