Date:         Fri, 12 Jan 2001 12:01:06 -0500
Reply-To:     "Ravi, Prasad" <Prasad.Ravi@PFIZER.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Ravi, Prasad" <Prasad.Ravi@PFIZER.COM>
Subject:      Re: Passing a macro variable in a remote session
Comments: To: "Charles_S_Patridge@PRODIGY.NET" <Charles_S_Patridge@PRODIGY.NET>
Content-Type: text/plain; charset="iso-8859-1"

  Have you tried using %SYSLPUT macro, available at SAS's web site.


-----Original Message-----
From: Charles Patridge [mailto:Charles_S_Patridge@PRODIGY.NET]
Sent: Friday, January 12, 2001 9:00 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: Passing a macro variable in a remote session


Foster,

Roland is correct.  I have a couple of tips on this issue which may be
of some help as well -

tip00107 tip00109

located on http://www.sconsig.com/   and then look under Tips and
Techniques and scroll down until you find the above tips mentioned.

Regards,
Charles Patridge
Email: Charles_S_Patridge@prodigy.net


In article <B5095B60E75BD41192AF00508BCF62904D934C@dma-mail>,
  "Kerrison, Foster" <FKerrison@NT.DMA.STATE.MA.US> wrote:
> I am trying to pass a macrovar set by using %let in open code,
therefore a
> global variable on to a remote session on MVS. I am runniing V8 on a
PC and
> connecting to a MF running 6.09.
>
> Basically the program will:
>
> 1.      Convert data into a WORK. dataset
> 2.      Upload that dataset to the MF via PROC UPLOAD.
>
> Rather than paste all the code I will show only the critical pieces:
>
> %let file1 = N:\MBHP\480_4209_2000906.EXT ;
> %let dsn1  = AUG00 ;
> %let file2 = N:\MBHP\480_4209_2001008.EXT ;
> %let dsn2  = SEP00 ;
>
> I know it's wallpaper" right now, but I will fix that later.
>
> %macro testing(FILENM, NAME) ;
>
> Data one ;
>  Then convert a text file, assign vars, etc. etc.....
>
> %mend testing;
>
> %TESTING(&FILE1,&DSN1)
> %TESTING(&FILE2,&DSN2)
> .
> .
> .
>
> So now I have a set of WORK datasets (AUGOO, SEP00, and so on).
>
> I now want to load them to the MF so I log on, and upload:
>
> %let itd=xxx.yyy.zz.vv;
> option remote=itd;
> filename rlink 'c:\program files\sas institute\sas\v8\tsox.scr';
> SIGNON;
> rsubmit itd;
>
> %macro loadup (mvsdsn,sasdsn) ;
> libname mvs "&mvsdsn"
>                         disp=new
>                         space=(cyl,(90,50),rlse)
>                         unit=testda ;
> proc upload out=mvs.CLMS (compress=yes) data=WORK.&sasdsn;
> RUN ;
>
> LIBNAME MVS CLEAR ;
>
> %mend loadup ;
>
> %loadup (DMACH3.IAMH0000.MBHP.TESTAUG.FILE0000,&dsn1 ;
> %loadup (DMACH3.IAMH0000.MBHP.TESTSEP.FILE0000,SEP00) ;
>
> endrsubmit;
> signoff ;
>
> When I run the job the &DSN1 will not resolve because I assume that
the
> remote session has control, and it cannot resolve the macrovar &DSN1
> remotely.
>
> Does anyone know how I can overcome this by passing the value for
DSN1, DSN2
> etc. to the remote session? I have been trying to figure out %syslput
and
> %lput, but I cannot get them to work.
>
> Thanks in advance for any help or pointers on this,
>
> Foster Kerrison.
>

--
Charles Patridge - PDPC, Ltd.
172 Monce Road - Burlington, CT 06013 USA
Phone: 860-673-9278 or 860-675-9026
Email: Charles_S_Patridge@prodigy.net - Web: www.sconsig.com


Sent via Deja.com
http://www.deja.com/