To keep a record of the commands entered during an NCL session,
    use the NCL logging facility.

    All information printed out in an NCL session is stored in the
    log file after logging is enabled. This information includes
    commands, output, and error messages. All information except
    for the commands are preceded in the file by a comment symbol,
    so this file can be used as an NCL script in another session.

    Use the set ncl logfile and enable ncl logging commands to begin
    NCL logging. For example:

    ncl> set ncl logfile filename.ncl
    ncl> enable ncl logging
    ncl> show node 0 session control application fal all attributes
       .
       .
       .

    After saving the NCL commands to a log file, use the NCL log file
    as an indirect command file to be invoked (during subsequent NCL
    sessions) with the do control verb or the at sign (@) symbol.

    For example:

    ncl> enable node 0 session control
    ncl> do setup_applications.ncl
       .
       .
       .

    To display the name of the log file, enter show ncl logfile. For
    Tru64 UNIX, the utility returns the default log file name if one
    was not previously set. For OpenVMS, the default file type for an
    NCL log file is .ncl. The utility returns an error message if a
    log file does not exist.

    Use the disable ncl logging command at any time to turn off NCL
    logging or exit NCL.

    Commands saved in an NCL log file can be executed during
    subsequent NCL utility sessions. However, you must ensure that
    the proper context for the commands in the log file has been
    established. Check the contents of an NCL log file before running
    it in the utility.