!AD not found in configuration

    Explanation: A node name that was associated with a script was
    not present in the configuration. This error can also occur
    during scheduler initialization if both the SYSGEN parameter,
    SCSNODE, and the logical, SYS$NODE are undefined on the node
    where the scheduler is running. In the case of the scheduler, the
    node name reported in the message will be blank.

    User Action: If the error occurs in the scheduler log file,
    define either the logical name SYS$NODE or the SYSGEN parameter
    SCSNODE and restart the scheduler. If the error occurs when
    entering a command, ensure you have spelled the node name
    correctly and that the node exists on the local system.