 |
VSE Changes to VTAM V4R2 Network Implementation Guide for MVS, VM and VSE (Information APAR II11297)
|
| | | Abstract | | Changes to the VTAM Network Implementation Guide Version 4 Release 2 for MVS, VM, and VSE (SC31-6494-01) that are applicable to VSE. | | | | | | | | Content | In section 1.4.3.1.3, Configuration Restart VSAM Files, this sample file, showing sample VSAM utility control statements used to allocate space for a configuration restart dataset, is shown:
DEFINE -
CLUSTER(NAME(ARNCKPT) -
VOLUMES(111111) -
KEYS(4 0) -
RECORDSIZE(24 136)) -
DATA(NAME(ARNCKPT.DATA) -
TRACKS(1)) -
INDEX(NAME(ARNCKPT.INDEX) -
TRACKS(1))
This section specifies step 4 as follows:
"4. Code RECORDSIZE (24 136). The average record size must be 24 bytes, and the maximum record size must be 136 bytes."
The maximum record size has changed from 136 to 158 bytes. Specifying too small a record length may result in VTAM issuing the following message:
IST184I I/O ERROR ON CKPT DS datasetname MAJOR NODE nodename RTNCD = 08 6C
DY43813
In Section 2.1.3.4 Defining Peripheral Nodes and Logical Units, 2.1.3.4.1 Defining Type 2.1 Peripheral Nodes, 2.1.3.4.1.2 CPNAME Operand, the fifth sentence is changed as follows:
(To have VTAM first use IDBLK and IDNUM, use the SWNORDER=STATNID start option or GROUP/LINE operand.)
DY43827
In section 4.1.4 "Defining CDRSCs", change:
"...becomes the owning CDRM of the resource to other VTAMs in the subarea network, unless the resource was predefined as a CDRSC with NETID and an owning CDRM name coded."
to:
"...becomes the owning CDRM of the resource to other VTAMs in the subarea network, unless the resource was predefined as a CDRSC with an owning CDRM name coded."
DY46311
Rather than locate every reference to NCP in this book and update each section to reflect the functional limitations of running an NCP on the Communication Controller for Linux on zSeries (CCL) product, a new section is added in Chapter 6 under "Operating with an NCP" (section 2.2.15 in the online version of this book) to describe these functional limitations. The new section is called "Communication Controller for Linux on zSeries considerations".
Please refer to the following TechNote for the complete text of the new section that was added to this book: VTAM Support for Communication Controller for Linux on System z (CCL).
DY45033
In Section 4.1 Implementing a Combined Subarea and APPN Network, 4.1.3 Dependent LUs, 4.1.3.1 Dependent LU Server, under 'To implement the dependent LU server function, consider the following:', replace the existing text with the new text:
Existing text:
New text:
- For DLUR-initiated PU activation, you can use the DLRORDER start option to control whether VTAM attempts first to find the PU using CPNAME or station identifier (IDBLK and IDNUM). When the DLUR PU is adjacent to the DLUS (the control point of the DLUR PU has an APPN connection with the DLUS) you must use some means other than CPNAME to find the PU. Some examples of means other than CPNAME for finding the PU are:
- DLRORDER=STATNID with IDBLK and IDNUM defined on the PU.
- Some DLURs have the capability of sending the PU name to the DLUS on REQACTPU (in the X'0E' type X'F1' control vector). In this case the DLUS VTAM tries to find the PU by name before looking for it by CPNAME or station id. See the publications for your DLUR implementation to see if this function is supported.
DY45360
The VTAM Network Implementation Guide will be changed to add, under Section 2.2.8.3 VTAM-to-VTAM XCA Connections, a new section, Sample Configuration with Multiple Protocols:
Sample Configuration with Multiple Protocols
Figure xx shows a multiple domain XCA configuration using multiple protocols with routers acting as protocol converters.
+------+ +------+
| | | |
| VTAM | | VTAM |
| | | |
+------+ +------+
| |
+----+ +----+
|OSA | |NCP |
|card| |NTRI|
+----+ +----+
| |
| Ethernet ------
| +------+ | | +------+ / \
----FDDI----|router|---|--|--|--|---|router|-----| Token- |
+------+ | | +------+ \ Ring /
------
To be in session across the XCA connection, application programs in each VTAM must be compatible application programs (that is, they must both be SNA application programs).
- To define the configuration in Figure xx, define the following in the VTAM connected through the OSA card: One external communication adapter major node for each FDDI connection to the OSA card.
- Major nodes for any devices connected to the FDDI.
The following is an example of coding used for the configuration in Figure xx:
1. Define an external communication adapter major node for the FDDI connection:
XCACON2 VBUILD TYPE=XCA XCA MAJOR NODE
PORT2 PORT MEDIUM=FDDI, FDDI
SAPADDR=4, SERVICE ACCESS POINT ADD
ADAPNO=1, ADAPTER NUMBER
CUADDR=BC0 CHANNEL UNIT ADDRESS
*
GROUP2A GROUP DIAL=YES, SWITCHED PERIPHERAL NODE
ANSWER=ON, DIAL WILL ACCEPT CALLS
CALL=INOUT, DIAL IN AND OUT
ISTATUS=ACTIVE ACTIVATED AT GEN
LINE2A LINE ANSWER=ON PU CAN DIAL IN
PU2A PU
*
GROUP2B GROUP DIAL=NO, NCP SUBAREA
ISTATUS=ACTIVE ACTIVATED AT GEN
LINE2B LINE
PU2A PU MACADDR=400077009938, MAC ADDRESS
PUTYPE=4, NCP PU
SAPADDR=8, SERVICE ACCESS POINT
SUBAREA=50, NCP'S SUBAREA NUMBER
TGN=1 TRANSMISSION GROUP NUMBER
2. Define a switched major node for the peripheral node attached to the FDDI:
SWNODE1 VBUILD TYPE=SWNET
PU2 PU DISCNT=YES, DISCONNECT FACILITY
DYNLU=YES, DYNAMIC DEFINITION OF ILU
IDBLK=002, BLOCK IDENTIFICATION
IDNUM=000002, IDENTIFICATION NUMBER
PUTYPE=2 PHYSICAL UNIT TYPE
*
LANPATH2 PATH DIALNO=0104000069020D60, TIC, SAP, MACADDR
GRPNM=GROUP2A LOGICAL GROUP DEFINITION
LU2 LU LOCADDR=2, DEPENDENT LU
ISTATUS=INACTIVE INITIAL STATUS INACTIVE
Notes:
- You need to code one LINE and PU definition statement in the dial GROUP definition statement for every simultaneous peripheral node connection.
- Switched devices connected to a FDDI can be defined to VTAM using the model major node. See section 2.2.7 "Dynamically Defining Switched Resources".
- Multiple VTAM hosts can be in session with different stations on the FDDI through one OSA card. To implement this support, code a different SAPADDR and MACADDR value combination to distinguish between the two hosts.
Caution:
The user is responsible for determining the 'smallest' frame size that the connection can support and insuring that the maximum data field length that flows across the connection does not exceed the 'smallest' frame supported.
The VTAM product has no knowledge of any technology other than what is directly attached to and adjacent to VTAM. Example: If an Ethernet bridge is remote from VTAM and is in the path to the NCP, then the maximum token ring frame size must be X'001' (1500) or less. If not, the bridge will terminate the connection if a data frame greater than 1500 is sent.
DY45045
In section 4.1.8.4, replace "SNI" with "SUBAREA" in the heading "Using the DISJOINT Operand to Define Disjoint SNI Networks"
In that same section, delete the second sentence of the fourth paragraph. The fourth paragraph should read:
"When the APPN search request is received by HOSTD, HOSTD uses this information to determine the SSCPs to which the request should be routed. HOSTD routes the request to other SSCPs that are not in NETA (the network identifier provided by HOSTC, the interchange node serving as the APPN entry point)."
Add the following NOTE before the next section:
NOTE: The above discussion of the DISJOINT operand also applies when the netids of all four hosts in figures 130 and 131 are the same (NETA). | | | | | | | |
|
|
| IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. |
|
|
|
|
| Please take a moment to complete this form to help us better serve you. |
|
 |
|
|
|
|
|
|
| Product categories: |
|
| | Software | |
| | Networking | |
| | Enterprise Connectivity | |
| | VTAM for VSE/ESA and VM/ESA | |
| | All | |
|
| Operating system(s): |
| |
VSE/ESA
|
|
| Software version: |
| |
4.2
|
|
| Software edition: |
| |
All Editions
|
|
| Reference #: |
| |
7012054
|
|
| IBM Group: |
| | Software Group |
|
| Modified date: |
| | 2009-03-03 |
|
|
