Marc's Place

1 ATTACH

   Transfers control from your current process to the specified
   process. The LATCP ATTACH command is similar to the DCL ATTACH
   command. For example, from the DCL command level you can enter
   the DCL SPAWN command to create a LATCP subprocess without ending
   your DCL session, execute several LATCP commands at the LATCP
   prompt, then use the ATTACH command to return to DCL.

   Format

     ATTACH  [process-name]

2 Parameter

process-name
   Specifies the name of a parent process or spawned subprocess to
   which control passes. The process must already exist, be part of
   your current job, and share the same input stream as your current
   process.

   Process names can contain from 1 to 15 alphanumeric characters.
   If a connection to the specified process cannot be made, LATCP
   displays an error message.

   If you specify the /PID qualifier, do not use the process name
   parameter. If you omit the /PID qualifier, you must use the
   process name parameter.
   To display processes, use the DCL SHOW SYSTEM command.

2  Qualifier

/PID
      /PID=pid

   Specifies the process identification (PID) of the process that
   will have terminal control. When you specify a PID, you can omit
   the leading zeros. If you specify a PID, do not use the process
   name parameter. If you omit the PID qualifier, you must use the
   process name parameter.

2 Example

 $ SET PROCESS/NAME="TOP_LEVEL"
 $ SPAWN RUN SYS$SYSTEM:LATCP
 LATCP> SHOW NODE/ALL
    .
    .
    .
 LATCP> ATTACH "TOP_LEVEL"
 $

     In this example, the user enters the DCL SPAWN command to
     create a LATCP subprocess and uses LATCP to display the status
     of all nodes known to the local node. After using LATCP, the
     user enters the ATTACH command to return to the DCL command
     level.
© 1997- Marc Vos (and others)   -   Privacy Statement   -    Contact Me

On this website, Google Analytics is used to track visitor statistics. These are anonymised data about the number of visitors, which pages they visit on this site, from which regions they visit, which web browsers they use, etc.. You will also see non-personalised ads via Google AdSense. Cookies from Paddle or Paypal are placed when you click on a 'Buy now!' or 'Donate!' button, and possible cookies from Disqus when you use that system to comment on one or more blogposts.
Privacy Statement