Date:         Tue, 11 Jul 2000 08:03:53 -0700
Reply-To:     lmcgrath <lmcgrathNOlmSPAM@UWSA.EDU.INVALID>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         lmcgrath <lmcgrathNOlmSPAM@UWSA.EDU.INVALID>
Organization: http://www.remarq.com: The World's Usenet/Discussions Start Here
Subject:      Re: R: Porting macro variables between hosts

Hi Jit,

I just did something very similar, passing variables from SCL on
a PC (SAS 6.12) to a Unix host.

Here are the steps I had to take.

1.  Check your config.sas file for the autocall libraries.  One
of the entries should be for SAS\Connect -

/* Setup the SAS System autocall library definition */
-SET SASAUTOS  ( ...
                 !sasext0\connect\sasmacro
                ...   )

2.  Check your c:\sas\connect\sasmacro directory (assuming sas is
installed in c:\sas) for the syslput macro.  If it is not there,
download or copy it from sas.com, and save it as syslput.sas in
that directory.

3.  Open syslput into your program editor and submit it.  People
who had helped me said that submitting the code shouldn't be
necessary, but it seemed to fix my problem.  You might be able to
skip this step.

4.  Here are a couple pieces of code from my scl program using
syslput:

SELECT(JOB);
 WHEN('MCS1510')

         saspgm='h:\xchgopd\maad\sassource\cs1510n.sas';
  ...
END;

SELECT(JOB);

   WHEN('MCS1510')  /*  CS1510n.sas has the rsubmit block within
the pgm */
      Submit Continue;

        %syslput(UNIT,&X3);

        %syslput(CENT,&X4);

        %syslput(YEAR,&X4%substr(&X5,1,2));

        %Include '&saspgm';

       EndSubmit;

   OTHERWISE ...

END;

HTH,
 Lisa

Lisa McGrath
lmcgrath@uwsa.edu




-----------------------------------------------------------

Got questions?  Get answers over the phone at Keen.com.
Up to 100 minutes free!
http://www.keen.com