DYNLU


     .-DYNLU--=--value_of_dynlu_start_option-----.     
>>-+-+-------------------------------------------+-+-----------><
   | |           .-value_of_dynlu_start_option-. | |   
   | '-DYNLU--=--+-----------------------------+-' |   
   |             +-NO--------------------------+   |   
   |             '-YES-------------------------'   |   
   | .-DYNLU--=--YES-. (1)                         |   
   '-+---------------+-----------------------------'   
     '-DYNLU--=--YES-'

Notes:

DYNLU=YES is the only valid value if the TRLE operand is coded.

statements:

dependencies:

CDRDYN

Specifies whether dynamic allocation of CDRSC definitions is supported. If you do not code this operand, the default is the value you coded on the DYNLU start option.

If dynamic allocation of CDRSC definitions is not supported for a particular PU, a resource that was dynamically defined as a CDRSC cannot use that PU to connect to a session.

DYNLU=NO

Specifies that dynamic allocation of CDRSC definitions is not supported. If you code DYNLU=NO and plan to connect to other nodes using CP-CP sessions, then predefine each node in the CDRSC major node. If you do not, CP-CP session setup fails.

DYNLU=YES

Specifies that dynamic allocation of CDRSC definitions is supported.

For subarea nodes (HOSTSA is specified), DYNLU=YES is meaningful only when the host CDRM is activated and CDRDYN=YES is specified on the CDRM definition statement.

For APPN-only nodes (HOSTSA is not specified), DYNLU=YES is meaningful even though a host CDRM cannot be activated.

Note: If you have coded a DYNLU value in the adjacent CP major node for the adjacent CP to which this physical unit is linked, that value overrides the DYNLU value you code on this PU definition statement. For additional DYNLU considerations, see DYNLU under the adjacent control point major node.