topic Connecting a Cobol SAS module from SAS 9.4 TS1M2 in Administration and Deployment

Connecting a Cobol SAS module from SAS 9.4 TS1M2

pbad — Thu, 07 Mar 2019 03:41:46 GMT

Dear team,

Very Good Morning,

We are using SAS 9.4 TS1M2 sas in zos enviroment. In order to use LE module inside JCL to connect to Cobol program Hot Fix V01044 might work but this hotfix can be used in TS1M3 or later versions. Basically we are trying to call Cobol db2 modules inside SAS program.

Do you suggest any other alternatve technique to connect to Cobold module inside SAS zos. I have created track with SAS but thought to consult a great pool of SAS experts 🙂

Please advice if you have any other alternative approach in mind.

Regards,

Pratik

Re: Connecting a Cobol SAS module from SAS 9.4 TS1M2

pbad — Thu, 07 Mar 2019 05:26:56 GMT

Hi Forgot to mention that users are calling Cobol module from SAS. This Cobol module is having DB2 calls, required to fetch the db2 data. Hence language interface is required to connect to SAS - Cobol - DB2. Unfortunately Hot Fix V01044 is not useful for SAS TS1M2.

Re: Connecting a Cobol SAS module from SAS 9.4 TS1M2

SASKiwi — Thu, 07 Mar 2019 05:41:45 GMT

So what happens now when you try CALL MODULE with DB2. Do you get the errors as documented here?

http://support.sas.com/kb/57/207.html

Re: Connecting a Cobol SAS module from SAS 9.4 TS1M2

pbad — Mon, 11 Mar 2019 05:55:10 GMT

No the errors are not the actually one, documented here. I have received the following reply from SAS.

The fix came in at 9.4M3 ad above so is not available for M2. Existing modules can still be used in an LE environment by coding the *Z control argument. i.e.CALL MODULE('*Z','xxx',yyy,zzz);
This control argument will not invoke IGZERRE since it is not supported in an LE environment. However, there could be a severe performance impact in not doing so. The V01044 provides a performant way of using CALL MODULE in an LE environment starting at M3.
My suggestion would be to try the *Z control argument to determine if any performance impact is encountered. If the module is called only a few times then any impact will be minimal. If the module is called tens of thousands of times then the time to create the runtime environment on each call may be significant.