Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
LUGROUP operand z/OS Communications Server: SNA Network Implementation Guide SC27-3672-01 |
|
To enable this facility, code the LUGROUP operand on the PU definition statement for the PU, and code an LU group major node. The LUGROUP operand on the PU definition statement specifies the name of the model LU definition group that VTAM® uses when dynamically defining LUs. The LU group major node contains the model definition statements. Dynamic definitions for LUs are built using the model LU definitions contained in this major node. Note: Any operands that you code on the PU definition statement will
not sift down to dynamically created LU definition statements.
After you enable this facility, VTAM uses the IBM-supplied selection of definitions for dependent LUs (SDDLU) exit routine to generate LU names for the dynamically built LU definition statements. The SDDLU exit routine controls the selection of the model LU and the LU name. If you prefer to use your own naming convention or method of selecting an LU model, you can write your own exit routine. For information about coding your own exit routine, see z/OS Communications Server: SNA Customization. If you use the IBM-supplied SDDLU exit routine, code the LUSEED and LUGROUP operands on the PU definition statement. The LUSEED operand provides a pattern name that is used with the SDDLU exit routine to create a name for the dynamically created LU definition statements. Figure 1 illustrates VTAM dynamically defining dependent LUs attached through a 3174 cluster controller, and the steps listed after the table explain the process. Figure 1. Definition building for dynamically defined
dependent LUs
|
Copyright IBM Corporation 1990, 2014
|