|
View previous topic :: View next topic
|
| Author |
Message |
vasanthz
Global Moderator
Joined: 28 Aug 2007
Posts: 1742
Location: Tirupur, India
|
|
|
|
Hi,
I am trying to invoke SAS from REXX,
Usually while invoking utilities like IEBGENER, IEBCOPY, ICETOOL in REXX we allocate the required DD statements like SYSPRINT, SYSIN, SORTIN etc.. then issue the command
| Code: |
| "CALL *(IEBCOPY)" or "CALL *(IEBGENER)" |
Similary when I tried
I got the error  ,
| Code: |
| IKJ56005I MEMBER SAS NOT FOUND WITHIN THE STANDARD SEARCH ORDER |
Could u please let me know where to find this "STANDARD SEARCH ORDER"
Is it some library?
Thanks, |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
For some reason - most places I have worked SAS is always accessed via a STEPLIB.
Look at the SAS batch JCL you submit and then include the STEPLIB datatsets into your REXX JCL or front end ISPF allocations. |
|
| Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007
Posts: 1742
Location: Tirupur, India
|
|
|
|
Thanks for responding.
A sample batch JCL which works at our shop. It has no steplib on it.
| Code: |
//PS010 EXEC SASMVS
//WORK DD UNIT=SYSALLDA,SPACE=(CYL,(5,1),RLSE)
//SYSIN DD *
data something;
put 'Yey! SAS works';
run;
/* |
"CALL *(SASMVS)" had the same error,
| Code: |
| IKJ56005I MEMBER SASMVS NOT FOUND WITHIN THE STANDARD SEARCH ORDER |
Regards, |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| That's a PROC that you are showing here, I believe the STEPLIB will be visible inside the expanded JCL. |
|
| Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007
Posts: 1742
Location: Tirupur, India
|
|
|
|
The actual JCL did not have any STEPLIB on it, so i made my previous post which was incorrect.
the JCL log showed the library,
| Code: |
| IEFC001I PROCEDURE SASMVS WAS EXPANDED USING SYSTEM LIBRARY S****.PROCLIB |
got the library, thanks again. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
I definitely DO NOT recommend invoking SAS in this way -- you're not setting up the SAS environment correctly. You probably won't get too far with SAS code if you do this.
SAS provides a CLIST library as part of their installation process, and that CLIST library contains code to invoke SAS from TSO. The SAS 9.1 and 9.2 libraries have procedure CLSTW0 to invoke SAS and set up the appropriate environment first. If you really want to invoke SAS from TSO, talk to your site support group about how to access CLSTW0 -- they may move the SAS library into your site's standard TSO library concatenation, or just move the member to a library. For testing, you could issue 'exec sas.hlq.CLIST(CLISTW0)' from ISPF option 6 or a TSO READY prompt. |
|
| Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007
Posts: 1742
Location: Tirupur, India
|
|
|
|
I use CLIST(CLISTW0) to invoke SAS interactively,
For invoking SAS from user CLISTs, I used a similar technique as that of invoking IEBGENER or IEBCOPY and it worked fine (for past few days). I was having problem with REXX though.
Maybe I have not written a complex SAS code which requires all the CONFIG and other allocations & so it did not fail  |
|
| Back to top |
|
|
|
|
