Getting Started with SAS under OpenVMS

Running SAS in a Detached Process

Unlike a spawned process, a detached process is independent of other processes; it is not linked to an OpenVMS parent process. A batch job is one type of detached process. To avoid the restrictions of batch processes, or to free up your DECterm window and still invoke SAS interactively or noninteractively, you can submit a SAS job to run in a detached process.

Example: Invoking the SAS Windowing Environment in a Detached Process

The following DCL COM file, DETACH.COM, invokes SAS with the SAS windowing environment interface in a detached process. (The numbered lines are explained following the code.)

   $! DETACH.COM
   $ SET NOON
1 $ DEFINE SYS$LOGIN DISK:[HOMEDIR]
   $ SET DEFAULT SYS$LOGIN
   $ @SYS$LOGIN:LOGIN.COM
   $ DEFINE SAS$NET_TYPE XCLIENT
2 $ @DUA1:[SAS92.FOUNDATION.9^2.UTILITIES.BIN]SAS92.COM
   $ SAS92/DMS
   $ EXIT

	Replace DISK:[HOMEDIR] with your own disk.
	Replace DUA1:[SAS92.FOUNDATION.9^2.UTILITIES.BIN] with your own location for SAS. Leave SAS92.COM as it is. (The SAS92.COM file defines OpenVMS logical names that SAS uses. For more information about the SAS92.COM file, see Customizing Your SAS Session Using OpenVMS Logical Names.)

To execute the DETACH.COM file, you would use a command like the following:

$ RUN/DETACHED/INPUT=DETACH.COM-
_$ /OUTPUT=DETACH.LOG-
_$ SYS$SYSTEM:LOGINOUT.EXE

Note: If your LOGIN.COM does not include a SET DISPLAY command, you must include one in your DCL COM. [cautionend]

Top of Page