DATA Step, Macro, Functions and more

PC vs MAINFRAME

Reply
Frequent Contributor
Posts: 89

PC vs MAINFRAME


dear all,

after a remote submit I frequently use code below to view the remote data:

. . . . code . . .

 

%sysrput
pad=
%SYSFUNC(PATHNAME(WORK));

  

ENDRSUBMIT;

 

libname rwork "&pad." server=prdsys;



HOW do I code the opposite?

something like this . . . but what servername to use . . . ??

%syslput pad=%bquote(%SYSFUNC(PATHNAME(WORK)));

RSUBMIT;

%put &pad. ;

libname rwork "&pad." server=XXXXXX ;

. . . code . . .

GreetZ,

Herman







Occasional Contributor
Posts: 7

Re: PC vs MAINFRAME

You can't ...

... unless you are running a SAS/CONNECT server on your local machine. I don't expect that will be the case. If you are running SAS/CONNECT locally, than the servername is the hostname of your local machine

Super User
Posts: 5,429

Re: PC vs MAINFRAME

Just out of curiosity, what are you trying to achieve?

Data never sleeps
Frequent Contributor
Posts: 89

Re: PC vs MAINFRAME

>>> all code is submittted on SAS PC,

because of large datasets i do a remote submit on mainframe,

afterwards i read in the created subset on pc and process it

so from pc view this rwork libname works

BUT,

now if have a dataset on pc and  i want, from mainframe, read it in directly (without doing a proc upload)

H.

Super User
Posts: 5,429

Re: PC vs MAINFRAME

PROC UPLOAD will always be more efficient than reading a data set via a remote libname (exception: a very narrow where-clause on an indexed variable - but I doub't that your work-tables are indexed..?)

Data never sleeps
Ask a Question
Discussion stats
  • 4 replies
  • 380 views
  • 6 likes
  • 3 in conversation