VTAM® issues this message when command2 has been scheduled for nodename. command1 is responsible for scheduling command2. For example, explicit deactivation of a peripheral node causes implicit deactivation of that node’s LUs.

See Command and RU types in VTAM messages for a description of command1 and command2.

If nodename is session-capable, VTAM issues nodename as a network-qualified name in the form netid.name.