topic Re: SYSPARM calling shell script variable in SAS Programming

SYSPARM calling shell script variable

Bensansing — Mon, 03 Aug 2015 20:00:02 GMT

Hey all,

I have wrote a sas program that takes in two sysparms upd_date and CSV.

I am automating these into autosys and running a shell script to execute my program

nohup sas program.sas -sysparm '$CSV $upd_date' -noterminal

I am wondering if there's anyway that you can read in a shell script defined variable into a sysparm call. Right now I read in my sysparms like so: %LET CSV = %SYSFUNC(TRIM(%QSCAN(&SYSPARM,1,%NRSTR(' '))));

So it is reading them in as a character $CSV and not TRANSACTION (which is what CSV is set to in shell script)

Does anyone have any tips or solutions to this, will this work or should I try a different route.

Re: SYSPARM calling shell script variable

Ksharp — Tue, 04 Aug 2015 13:53:16 GMT

%LET CSV = %SYSFUNC(TRIM(%QSCAN(&SYSPARM,1,%STR( ))));

Re: SYSPARM calling shell script variable

Bensansing — Tue, 04 Aug 2015 14:32:40 GMT

Thanks for the reply, this way is still reading in the macro variables as $CSV in my sas code and not what was defined in the shell script.

CSV=TRANSACTION in shell script. Not sure if it's possible to bring in shell script defined variables into a sysparm command.

Thanks for the input though

Re: SYSPARM calling shell script variable

RW9 — Tue, 04 Aug 2015 14:43:39 GMT

Am not too familiar with your OS syntax, however if the variable needs to be de-referenced then it can't go in quotes as far as I know. Have you tried:

nohup sas program.sas -sysparm $CSV $upd_date -noterminal

If that doesn't work you may need to wrap in a batch file to echo out the full string.

Re: SYSPARM calling shell script variable

Bensansing — Tue, 04 Aug 2015 14:58:25 GMT

Yeah that doesn't work either, I also tried concatenating full string to run into one variable which didn't work. I think I will take an approach to wrap in a batch file.

Thanks!

Re: SYSPARM calling shell script variable

data_null__ — Tue, 04 Aug 2015 15:22:24 GMT

What happens if you use SYSGET on the values scanned from SYSPARM? You may also be able to skip this SYSPARM and just use SYSGET in your code.

Re: SYSPARM calling shell script variable

Bensansing — Tue, 04 Aug 2015 15:27:11 GMT

I also tried using SYSGET yesterday and wasn't working.. was still showing up as $CSV unfortunately

Re: SYSPARM calling shell script variable

data_null__ — Tue, 04 Aug 2015 15:32:52 GMT

shell command EVAL might fix it

eval "nohup sas program.sas -sysparm '$CSV $upd_date' -noterminal"

Re: SYSPARM calling shell script variable

Tom — Tue, 04 Aug 2015 15:33:24 GMT

Use double quotes instead of single quotes in your command line. The unix shell is not expanding the variable reference and so the literal text '$CSV' will be passed to SAS as the value of SYSPARM macro variable. To test it just use ECHO command.

Compare:

echo -sysparm '$CSV $upd_date'

echo -sysparm "$CSV $upd_date"

Re: SYSPARM calling shell script variable

Bensansing — Tue, 04 Aug 2015 15:40:46 GMT

Can't believe I didnt think of that to try, thanks for everyone's input and help!

Re: SYSPARM calling shell script variable

data_null__ — Tue, 04 Aug 2015 16:15:24 GMT

Did you remove the $sign?

Re: SYSPARM calling shell script variable

Bensansing — Tue, 04 Aug 2015 16:55:35 GMT

Keep it as: nohup sas program.sas -sysparm "$CSV $upd_date" -noterminal

The change to double quotes makes it work.

"Macro variable CSV resolves to TRANSACTION"

"Macro variable upd_date resolves to 4"

Re: SYSPARM calling shell script variable

data_null__ — Tue, 04 Aug 2015 18:09:30 GMT

I was referring to SYSGET i.e. sysget('$CSV') vs sysget('CSV');