LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (May 2002, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Wed, 15 May 2002 10:11:32 -0400
Reply-To:     "Braten, Michael (Exchange)" <mbraten@BEAR.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Braten, Michael (Exchange)" <mbraten@BEAR.COM>
Subject:      Re: SAS/JCL passing parameters
Content-Type: text/plain

#3 I would have the SAS step write its parameters to a temporary file that would be passed to the next step. The next step would read the parameters as input. The PASSed file disappears after JOB end.

//TEMPFILE DD DSN=&&TEMP,DISP=(NEW,PASS) // DCB=...... > -----Original Message----- > From: Huck [SMTP:huck@SKIPTHISFINN.COM] > Sent: Wednesday, May 15, 2002 12:24 AM > To: SAS-L@LISTSERV.UGA.EDU > Subject: Re: SAS/JCL passing parameters > > On 14 May 02 23:10:38 GMT, crm1nxa@UPS.COM (Abakah Nori crm1nxa) wrote: > > >Hi All, > > > >How do you pass a parameter from a SAS step to a non-SAS step? I have > used > >the SYSPARM several times to pass a parameter to a SAS program and would > >like to be able to do the opposite. > >Any ideas? > > (1) you write the second step to to the internal reader [ > SYSOUT=(B,,INTRDR) ] > > (2) or ya find that assembler program that can read a file and put it into > a jcl parm, > and you write to a file and as an intermediate step call that asm program. > > i vote for #1 > > > > >Thanks > > > >Abakah, Nori > >Mainframe Resources Group > >United Parcel Service > >(201) 828-2351

*********************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. ***********************************************************************


Back to: Top of message | Previous page | Main SAS-L page