A fix is available
APAR status
Closed as program error.
Error description
Session setup over XCA connection is very slow.
Local fix
Change timer value in XCA major node to a lower value.
Problem summary
**************************************************************** * USERS AFFECTED: All using XCA connection networks. * **************************************************************** * PROBLEM DESCRIPTION: Allow XCA users the ability to * * control how XCA LAN connection network * * nodes are located. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR OW46623 added LANTEST support to allow XCA LAN users the ability to control how Subarea and peripheral nodes are located. This APAR extends the LANTEST support for XCA LAN connection network nodes. Before a connection can be made, the partner node must be located. To locate the partner node a test command is sent to the MACADDR to see if it responds. Initially, VTAM will send out a local test command. The local test command will flow only on the local token ring. After the test command is sent, VTAM will set a timer and wait for a test response. If the test response is not received by VTAM (LSA) before the timer expires, a global test command will be sent. The global test command contains a routing information field with the broadcast bit on. The broadcast bit allows the test command to flow into the entire network. The timer LSA sets is based on the TIMER parameter that is coded on the XCA PORT macro. The default for this timer is 30 seconds. For switched connections, a total of five test commands will be sent (1 local, 4 global), if necessary. For nonswitched connections VTAM will continuously send TEST commands until the partner node responds or the connection is inactivated. At the present, there is no way for the operator to control how VTAM searches for XCA LAN connection network devices. An existing paramter, LANTEST, is now being made available for Model Major Node DYNTYPE=VN PUs. The LANTEST parameter will allow some control over how VTAM searches for these devices. This new parameter has two flavors, LOCAL and GLOBAL. If the partner device lives on a remote ring, coding LANTEST=GLOBAL will eliminate the search of the LOCAL ring. This will eliminate unnecessary connection setup time.
Problem conclusion
ISTSDCPU - Added support for LANTEST parameter for Model Major Node PUs. ISTLSCKN - Has been included for maintenance purposes. The following documentation changes have been made: z/OS IBM Communications Server SNA Resource Definition Reference Chapter 2. Major nodes External communication adaptor (XCA) major node Under the "Operand descriptions" section, modify the existing NOTE under the LANTEST operand as follows: Note: For XCA peripheral nodes (DIAL=YES), this parameter exists under the Switched Major Node PU. For XCA connection network PUs, this parameter exists under the Model Major Node (DYNTYPE=VN). Chapter 2. Major nodes Model major node Under the "Full syntax" section, add the following LANTEST parameter to the PU syntax diagram as follows: ------LANTEST = LOCAL------ | | >----|----------------------------------> | | | -LOCAL-- | ------LANTEST = --|------|- -GLOBAL- Under the Model major node "Operand descriptions" add the following parameter definition as follows: LANTEST ------LANTEST = LOCAL------ | | >----|----------------------------------> | | | -LOCAL-- | ------LANTEST = --|------|- -GLOBAL- statements: PU dependency: XCA switched LAN connections only. This parameter allows the user to define how the XCA connection network nodes connected on the XCA LAN will be located. There are two types of TEST commands sent; LOCAL and GLOBAL. The LOCAL will only flow on the local token ring. The GLOBAL will flow with a routing information field. This routing information field has the broadcast bit on meaning to route the test into the entire network. LANTEST=LOCAL Specifies that a TEST frame will be first sent out on the LOCAL token ring. If no response is received within the PORT TIMER interval, a GLOBAL TEST frame will be sent. Each time the GLOBAL TEST receives no response within the PORT TIMER interval, another GLOBAL TEST will be sent. The GLOBAL test will be repeated up to four times at which time the connection setup is terminated if no response is received. LANTEST=GLOBAL Specifies that only GLOBAL TEST frames will be used to locate the device. Each time the GLOBAL TEST receives no response within the PORT TIMER interval, another GLOBAL TEST will be sent The GLOBAL test will be repeated up to five times at which time the connection setup is terminated if no response is received.
Temporary fix
Comments
APAR Information
APAR number
OA08856
Reported component name
VTAM V4 MVS/ESA
Reported component ID
569511701
Reported release
140
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2004-08-27
Closed date
2004-09-28
Last modified date
2004-12-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA14025 UA14026 UA14027 UA14028 UA14029
Modules/Macros
ISTLSCKN ISTSDCPU
| SC31877804 | SC31877803 | SC31877802 | SC31877801 | SC31856504 |
Fix information
Fixed component name
VTAM V4 MVS/ESA
Fixed component ID
569511701
Applicable component levels
R10A PSY UA14025
UP04/11/05 P F411
R120 PSY UA14026
UP04/11/05 P F411
R140 PSY UA14027
UP04/11/05 P F411
R150 PSY UA14028
UP04/11/05 P F411
R160 PSY UA14029
UP04/11/05 P F411
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":"140","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":"140","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 December 2004