![](dblue_rule.gif) |
The following example shows a switched major node for
a Dependent LU Server. It defines DLURs for the PUs and LUs that
will use this host as a dependent LU server (DLUS). This deck is
valid only for network nodes or interchange nodes.
The MAXDLUR operand on the VBUILD definition statement
specifies 20 as the maximum number of unique DLUR node definitions
in this switched major node deck.
All the PU definition statements specify values for the
IDBLK and IDNUM operands, indicating that these are all DLUR PUs that
can initiate a CPSVRMGR connection by dialing in.
Both the DLURNAME and DLCADDR operands are coded on the
PATH statements, indicating that the dependent LU server has the capability
of initiating the CPSVRMGR connection to all the specified DLUR PUs
by performing a dial-out.
The DLURNAME operand on
the PATH statements identifies: - NNCPA1 as the DLUR that owns PUs AA1PUA, AA1PUC, AA1PUD, and AA1PUE
- NNCPA3 as the DLUR that owns PU AA3PUA
- ENCPA4 as the DLUR that owns PU AA4PUA.
If the DLUS and the DLUR are in different networks, the
name assigned to DLURNAME must be network-qualified.
The first DLCADDR entry on the PATH definition statement
contains information that identifies the DLC type. For instance,
in the PATH definition statement labeled PATHAA1A, the first DLCADDR
entry specifies (1,C,INTPU): - 1
- The first DLCADDR entry must have a subfield_id of 1.
- C
- The data format of the dial information is EBCDIC.
- INTPU
- The DLC type is internal PU.
For the Communications Manager/2's implementation of the
DLUR, DLCADDR=(1,C,INTPU) must be coded for the first DLCADDR entry
because the only DLC type supported by this implementation is internal
PU.
The remaining DLCADDR entries define the DLC signaling
information (addresses and dial digits) for each DLC type. In the
same PATH definition statement, this information is specified as (2,X,056A1001):
- 2
- This subfield_id is specified by the DLC type.
- X
- The data format of the dial information is hexadecimal.
- 056A1001
- This is the DLC signaling information.
The value 056A1001 matches the IDBLK and IDNUM values,
056 and A1001, respectively, specified on the PU definition statement.
In addition to this matching requirement, the IDBLK/IDNUM specified
in the switched major node must also match the NODE_ID value specified
in the Communications Manager/2 response file (RSP) or node definition
file (NDF), for the associated LOGICAL_LINK statement.
The LOCADDR coded on the LU definition statement in the
switched major node must match the NAU_ADDRESS value, for a specific
DLUR-supported LU, that is defined in the Communications Manager/2
RSP or NDF files. *********************************************************************
* SWDLR1A - SWITCHED DECK FOR DLUS/DLUR (DEPENDENT LU SERVER)
* TESTING
*********************************************************************
*
SWDLRALL VBUILD TYPE=SWNET,MAXNO=20,MAXGRP=20,MAXDLUR=20
*
*********************************************************************
* INTERNAL PU_T2.0 IN DLUR NETA.NNCPA1
*********************************************************************
*
AA1PUA PU ADDR=01, ** LINK STATION ADDRESS ** X
IDBLK=056, ** DEVICE TYPE ** X
IDNUM=A1001, ** SERIAL NUMBER OF DEVICE ** X
ISTATUS=ACTIVE, ** BECOMES ACTIVE WITH NODE ** X
MAXPATH=1 ** NUMBER OF DIAL PATHS **
PATHAA1A PATH PID=1, ** PATH IDENTIFIER ** X
DLURNAME=NETA.NNCPA1, ** NAME OF DLUR FOR PU ** X
DLCADDR=(1,C,INTPU), ** DLC TYPE INFORMATION ** X
DLCADDR=(2,X,056A1001) ** DLC SIGNAL INFORMATION **
AA1LUA1 LU LOCADDR=1, ** LU'S LOCAL ADDRESS ** X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUA2 LU LOCADDR=2, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUA3 LU LOCADDR=3, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUA4 LU LOCADDR=4, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
.
.
.
*********************************************************************
* EXTERNAL PU_T2.0 ON TOKEN RING ON DLUR NETA.NNCPA1
*********************************************************************
*
AA1PUC PU ADDR=03, X
IDBLK=056, X
IDNUM=A1003, X
ISTATUS=ACTIVE, X
MAXPATH=1
PATHAA1C PATH PID=1, X
DLURNAME=NETA.NNCPA1, X
DLCADDR=(1,C,TR), X
DLCADDR=(2,X,056A1003), X
DLCADDR=(3,X,04), X
DLCADDR=(4,X,4000056A1003)
AA1LUC1 LU LOCADDR=1, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUC2 LU LOCADDR=2, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUC3 LU LOCADDR=3, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUC4 LU LOCADDR=4, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
*********************************************************************
* EXTERNAL PU_T2.1 ON TOKEN RING ON DLUR NETA.NNCPA1
*********************************************************************
*
AA1PUD PU ADDR=04, X
IDBLK=056, X
IDNUM=A1004, X
CPNAME=LENCPA14, X
ISTATUS=ACTIVE, X
MAXPATH=1
PATHAA1D PATH PID=1, X
DLURNAME=NETA.NNCPA1, X
DLCADDR=(1,C,TR), X
DLCADDR=(2,X,056A1004), X
DLCADDR=(3,X,04), X
DLCADDR=(4,X,4000056A1004)
AA1LUD1 LU LOCADDR=1, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUD2 LU LOCADDR=2, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUD3 LU LOCADDR=3, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUD4 LU LOCADDR=4, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
*********************************************************************
* EXTERNAL PU_T2.1 ON TOKEN RING ON DLUR NETA.NNCPA1
* NOTE: THIS PU IS NONNATIVE NETWORK ATTACH (NETQ).
*********************************************************************
*
AA1PUE PU ADDR=05, X
IDBLK=056, X
IDNUM=A1005, X
CPNAME=LENCPA15, X
ISTATUS=ACTIVE, X
MAXPATH=1
PATHAA1E PATH PID=1, X
DLURNAME=NETA.NNCPA1, X
DLCADDR=(1,C,TR), X
DLCADDR=(2,X,056A1005), X
DLCADDR=(3,X,04), X
DLCADDR=(4,X,4000056A1005)
AA1LUE1 LU LOCADDR=1, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA1LUE2 LU LOCADDR=2, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
.
.
.
*********************************************************************
* INTERNAL PU_T2.0 IN DLUR NETA.NNCPA3
*********************************************************************
*
AA3PUA PU ADDR=07, X
IDBLK=056, X
IDNUM=A3001, X
ISTATUS=ACTIVE, X
MAXPATH=1
PATHAA3A PATH PID=1, X
DLURNAME=NETA.NNCPA3, X
DLCADDR=(1,C,INTPU), X
DLCADDR=(2,X,056A3001)
AA3LUA1 LU LOCADDR=1, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA3LUA2 LU LOCADDR=2, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA3LUA3 LU LOCADDR=3, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA3LUA4 LU LOCADDR=4, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
*********************************************************************
* INTERNAL PU_T2.0 IN DLUR NETA.ENCPA4
*********************************************************************
*
AA4PUA PU ADDR=08, X
IDBLK=056, X
IDNUM=A4001, X
ISTATUS=ACTIVE, X
MAXPATH=1
PATHAA4A PATH PID=1, X
DLURNAME=NETA.ENCPA4, X
DLCADDR=(1,C,INTPU), X
DLCADDR=(2,X,056A4001)
AA4LUA1 LU LOCADDR=1, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA4LUA2 LU LOCADDR=2, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA4LUA3 LU LOCADDR=3, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
AA4LUA4 LU LOCADDR=4, X
PACING=(1,1), X
VPACING=2, X
MODETAB=MODETAB2
For a configuration where the VTAM® DLUS host and the Communications Manager/2
DLUR node are adjacent, the FQ_ADJACENT_CP_NAME defined on the DEFINE_LOGICAL_LINK
statement in the Communications Manager/2 definitions should be the
CPNAME of the VTAM that is
configured as the DLUS host.
|