MVSFORUMS.com

[psivamadhusudhan]

Hi All,

We have an existing CICS screen COBOL non-db2 program IVEAB1 which reads DB2 table data through driver modules and populates screen area of existing screen AB1.

We are now preparing a new COBOL non-DB2 program IVE001 as a main program to call IVEAB1 as sub programs and pass required parameters to read tables and receive data back through Linkage section. We are initiating IVE001 through new transaction AA1.

We have defined PCT, PPT, RACF entries for AA1 and RCT to link to DB2 PLAN.

All Tables and Plans are given PUBLIC access.

When we are invoking AA1 transaction, it is abending with A2DU with below DB2DIAG messages.

[kolusu]

psivamadhusudhan,

A reason code of 00F30034 means the program attempting to execute the plan is not authorized to use the plan.

So please make sure that the plan exists in the particular DB2 subsystem(Check the DB2 ID in DB2CONN setting in CICS).

You can query it using SPUFI in the table SYSIBM.SYSPLAN. Once you have determined that the PLAN does exist, you need to check if CICS user is authorized to execute it. You can check the DB2 table SYSIBM.SYSPLANAUTH for that.

Typically the DBA would be Granting Execute privilege for plan <plan name> to Public

I know you mentioned RACF but if your shop has ACF2 then you may want to take a look at this

https://www.ibm.com/support/pages/ad2u-sqlcode-922-and-sqlerrc-00f30034-when-using-ca-acf2
_________________
Kolusu - DFSORT Development Team (IBM)
DFSORT is on the Web at:
www.ibm.com/storage/dfsort

www.linkedin.com/in/kolusu

[psivamadhusudhan]

Hi Kolusu,

Plan is existing in DB2 subsystem and we are able to run batch jobs pointing to it without any access issue.

And also existing screens are able to pull data from tables using same plan.

I verified SYSIBM.SYSPLAN and SYSIBM.SYSPLANAUTH and access is provided to PUBLIC.

CICS team verified DB2T, DB2E, DB2CONN all look good.

To try it in a different manner, we even removed sub program calls and just place one SELECT SQL, even then it throwing PLAN ACCESS ERROR.

Neither CICS Admin or DB2 Admins are able to figure what is the issue as this is new CICS transaction in almost 20-25 years.

[psivamadhusudhan]

just to give more info.

we are using SCLM for program compilation.
Language used is COBOLD for new program.

Does ARCHDEF impacts the way our programs executes in CICS environment.

If anyone has SCLM knowledge, please help to share your inputs