PU and LU definition statements

Code one PU and LU statement for each resource to be added.
  • Code the operands in the PU and LU definition statements in the same format as they appear in the appropriate major node.
  • Code all of the operands that you want from the GROUP, LINE, or PU definition statements to which you are adding the physical unit or logical unit. VTAM® ignores NCP-only operands and might issue a warning message.
  • Sifting takes place within the hierarchy of minor nodes being added dynamically. Values for operands coded in the original hierarchy above the hierarchy being added do not sift down to the added resources. Therefore, if you want the values coded in the original hierarchy, you must code them in the group of DR definition statements for the resources you are adding.
  • The most efficient way to add a physical unit and its associated logical units is to specify them on the same ADD definition statement and not use separate ADD definition statements for the physical unit and each logical unit.
Table 1. Definition statements for dynamic reconfiguration with VARY DRDS (ADD operation)
Name Definition statement Operands Page Req Sift effect Default

Restrictions,
dependencies
name VBUILD TYPE=DR TYPE operand description R      
 
name ADD TO TO operand description R      
    DRTYPE DRTYPE operand description     NCP Adding LUs to PUs only
 
name PU            
 
name LU            
 
Legend:
R
Required operand.
Parent topic: Add operation