Date:         Fri, 9 Nov 2001 15:34:18 -0500
Reply-To:     Larry Bertolini <bertolini.1@OSU.EDU>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Larry Bertolini <bertolini.1@OSU.EDU>
Organization: Ohio State University
Subject:      Re: SAS & IMS
Content-Type: text/plain; charset=us-ascii

Marc,
I assume that you're aware of the SAS/ACCESS Interface to IMS-DL/I.
That product would provide the straightest path to your IMS data.

If you have that product available, but wish to access IMS from
a COBOL routine that encapsulates business logic, then I'd take
a stab at an approach like:

DATA;
  * this should get your IMS address space established */
  INFILE psbname DLI <options>;

  CALL MODULE(parm, parm,...);

If you don't have the SAS/ACCESS for IMS-DL/I product,
then perhaps you could write a COBOL stub program that
calls SAS, which calls your modules:

//stepname EXEC PGM=DFSRRC00,PARM=(DLI,stubpgm,psbname)

This might get your IMS address space set up, prior to loading
SAS.  Don't be surprised if that turns out be tricky, especially with regard
to compile and  link options that influence addressability.  Also, the
COBOL modules that you want to call, might need to have the IMS
"environment" (PCBs) in their linkage section, which means you'd have
to pass them along.  Would be a fun and interesting project; with luck,
you'll survive with your hair intact.

Marc Van Loy wrote:

> Dear SAS users,
>
> we are trying to get in contact with people that have ever used next
> mechanisme from Mainframe MVS SAS 6.09.0470P042699.
>
> CALL MODULE(xxx,....) from a datastep whereby xxx is a COBOL-IMS-module.
> CALL MODULE works fine whenever the called COBOL-module does not contain
> IMS-traffic but fails at the first contact to IMS.  Has this ever been used
> and proven waterproof be anyone?  More in particular: is there any way to
> avoid addressing errors since both the SAS datastep and the COBOL module
> will be running in the same address-space?
>
> Much obliged for your reactions,
> Marc