Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!esosun!net1!sdcsvax!ucbvax!NGP.UTEXAS.EDU!mic
From: mic@NGP.UTEXAS.EDU (Mic Kaczmarczik)
Newsgroups: mod.computers.vax
Subject: Re: VMS4.4 (really using ASSIGN within SAS)
Message-ID: <8611111539.AA21363@ngp.utexas.edu>
Date: Tue, 11-Nov-86 10:39:20 EST
Article-I.D.: ngp.8611111539.AA21363
Posted: Tue Nov 11 10:39:20 1986
Date-Received: Wed, 12-Nov-86 21:36:47 EST
References: <12253823381.38.CP.PAVER@MCC.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: ngp!mic@ngp.utexas.edu (Mic Kaczmarczik)
Organization: UTexas Computation Center, Austin, Texas
Lines: 31
Keywords: SAS spawn
Approved: info-vax@sri-kl.arpa
Summary: Logicals set in subprocesses aren't seen by parent

In article <12253823381.38.CP.PAVER@MCC.COM> CP.PAVER@MCC.COM (Bob Paver) writes:
>		[workaround for running SAS under VMS 4.4]
>                                         I've also had trouble with 
>VMS ASSIGN statements executed from with SAS programs.  SAS can't 
>translate the logicals unless I use ASSIGN/JOB.  Don't know if this is
>a bug or a feature!
>-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>Bob Paver	(512) 338-3316
>Microelectronics and Computer Technology Corp. (MCC)
>3500 West Balcones Center Drive
>Austin, TX  78759
>
>ARPA:  paver@mcc.com
>UUCP:  {ihnp4,seismo,harvard,gatech}!ut-sally!im4u!milano!paver
>-------

This is a necessary side-effect of the SAS `VMS' command.  To execute
general VMS commands from within SAS, SAS spawns a DCL subprocess to
parse and execute the command.  This means that executing

	VMS 'ASSIGN BAR FOO';

inside SAS causes a logical name to be set in the *subprocess'*
logical name table -- SAS can't see it because the change isn't
propagated to the SAS process' own logical name table!  Using
ASSIGN/JOB works because all processes and subprocesses in a job share
the LNM$JOB table, so SAS can see the logical name.

Mic Kaczmarczik
U.T. Austin Computation Center User Services
mic@ngp.utexas.edu