Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

How the statement "CALL *(IEBCOPY)" works?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF
View previous topic :: :: View next topic  
Author Message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1456
Location: Azeroth

PostPosted: Wed May 19, 2010 5:34 pm    Post subject: How the statement "CALL *(IEBCOPY)" works?
Reply with quote

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
Code:
"CALL *(SAS)"


I got the error icon_eek.gif ,

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
View user's profile Send private message

expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Wed May 19, 2010 5:38 pm    Post subject:
Reply with quote

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
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1456
Location: Azeroth

PostPosted: Wed May 19, 2010 5:46 pm    Post subject:
Reply with quote

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
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Wed May 19, 2010 5:50 pm    Post subject:
Reply with quote

That's a PROC that you are showing here, I believe the STEPLIB will be visible inside the expanded JCL.
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1456
Location: Azeroth

PostPosted: Wed May 19, 2010 6:02 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7930
Location: Bellevue, IA

PostPosted: Wed May 19, 2010 6:21 pm    Post subject:
Reply with quote

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
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1456
Location: Azeroth

PostPosted: Wed May 19, 2010 7:57 pm    Post subject:
Reply with quote

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 icon_biggrin.gif
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts -913/-911 Deadlock during UPDATE stat... NoSleep319 DB2 5 Fri Nov 18, 2016 12:37 am
No new posts Amount field is getting corrupted whe... thesumitk SYNCSORT 5 Tue Oct 18, 2016 8:20 pm
No new posts Cobol EZASOKET call to SETSOCKOPT fails Andi1982 COBOL Programming 6 Thu Oct 06, 2016 7:12 pm
No new posts Strange EXEC function call in z/VM Willy Jensen CLIST & REXX 3 Wed Oct 05, 2016 2:07 pm
No new posts hot to get details when "EXEC CI... Andi1982 CICS 11 Tue Sep 20, 2016 5:01 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us