MVSFORUMS.com

MFdigger · Posted: Tue Mar 31, 2009 10:02 am Post subject: CICS Compilation - Issue

Hi Kolusu,

I'm trying to compile a COBOL/CICS/DB2 program and created the compile JCL as per the link found mentioned below after searching the forum.

http://www.mvsforums.com/helpboards/viewtopic.php?t=1165

As in the above topic, I've created the compile JCL following the link
mentioned

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DSNAPH10/5.1.2.4?SHELF=&DT=20010209162045

While compiling I'm facing with the following error message:

8980 IGYPS0228-S An "EXEC CICS" statement was found, but the "CICS" compiler option was not in effect. The statement was discarded.

Could some one please help me what could be the issue.

Thank you
_________________
Tx
Digger

kolusu · Posted: Tue Mar 31, 2009 10:58 am Post subject:

MFdigger,

You need to have the CICS libraries concatenated to your steplib in step 3. The set up varies from shop to shop , so it would be better if you ask your colleagues about this

Kolusu

MFdigger · Posted: Wed Apr 01, 2009 11:55 am Post subject:

Hi Kolusu,

Thank you for your response. When I run the same JCL for a small test program with EXEC CICS commands its working perfectly fine but I'm not sure why its showing up this message when I'm trying to compile the clients code.

Its showing the error message exactly at the first 'EXEC CICS' Statement.
Any ideas on this?

Thank you
Rolling Eyes

_________________
Tx
Digger

kolusu · Posted: Wed Apr 01, 2009 12:25 pm Post subject:

MFdigger,

Just a wild guess , did the first EXEC CICS statement which resulted in error is a part of a COPY BOOK?

Kolusu

MFdigger · Posted: Wed Apr 01, 2009 12:42 pm Post subject:

Hi Kolusu

Thats exactly correct, its in a copybook.

Thank you
_________________
Tx
Digger

dbzTHEdinosauer · Posted: Wed Apr 01, 2009 12:56 pm Post subject:

and you used COPY to expand the copybook?

if so, COPY is a compiler directive.
use INCLUDE so that the db2 pre-compiler will expand the copybook for the SQL conversion.
_________________
Dick Brenholtz
American living in Varel, Germany

kolusu · Posted: Wed Apr 01, 2009 1:18 pm Post subject:

MFdigger,

I am guessing that you are running ENTERPRISE COBOL compiler along with Pre-compiler step. The pre-compiler does not convert EXEC CICS commands inside copybooks. Therefore, the COBOL compiler is seeing EXEC CICS when it expands the copybooks.

To resolve this you need to specify the compiler option CICS on the complie. Add this line before the ID division.

MFdigger · Posted: Thu Apr 02, 2009 12:27 pm Post subject:

Thank you dbzTHEdinosauer, Kolusu.

I changed the COPY statement to EXEC SQL INCLUDE xxxx END EXEC Statement and it worked and compiled.

Thank you very much for all your help Smile

_________________
Tx
Digger

MFdigger · Posted: Thu Apr 02, 2009 2:08 pm Post subject:

we have a dynamic call as shown below in the same copybook

kolusu · Posted: Thu Apr 02, 2009 2:54 pm Post subject:

MFdigger,

Is this a new program? if so did you define the program in PCT? And how are you issuing the new copy command?

Check this link for the command CEMT SET program

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DFHA7P03/11.103?

Kolusu

jsharon1248 · Posted: Thu Apr 02, 2009 3:22 pm Post subject:

MFdigger · Posted: Thu Apr 02, 2009 7:09 pm Post subject:

Hi Kolusu

Yes, its a new program. The main program XYEPDEF is defined in CICS system tables.

Do we have to also defined the calling program in the PCT/PPT table?
As per jsharon post, its seems like we have to also define the calling program in PPT table. I was not sure on that

Thank you Confused

_________________
Tx
Digger

MFdigger · Posted: Fri Apr 03, 2009 11:26 am Post subject:

Hi Sharon, Kolusu.

I have asked our CICS admin to define the subprograms which were called dynamically in system tables and they have been defined.

I'm facing with the same message

jsharon1248 · Posted: Fri Apr 03, 2009 11:55 am Post subject:

First verify that the PPT was created properly. Run the CEMT command for the program to verify that you can see the PPT. The next item you'll probably need to discuss with the CICS guys at your shop. The PPT's might not be defined in the same region where your transaction is executing. That being said, you need to make sure that the load lib where your load module is stored is accessible from the region where your transaction is executing. Since you're executing a COBOL CALL, not a CICS LINK or XCTL, you have to make sure that the z/OS can find the module. I think there's a STEPLIB in the CICS startup deck, but I'll be honest, I don't remember. As a last resort, try making the CALL a static call.

MFdigger · Posted: Fri Apr 03, 2009 2:08 pm Post subject:

Hi Sharon

I verified the Program 'ABCDTT' and is defined in PPT and also made sure that the program load is available in the library which is accessible from the region where tranaction is executed.