CICS program output different when ran using CEDF.



Support for CICS/ESA, CICS/TS & Transaction Gateway, CICS Configuration Manager and CICS Performance Analyzer

CICS program output different when ran using CEDF.

Postby rogerstrycova » Sun Oct 03, 2021 4:52 pm

I have a problem where my CICS application gives a different result compared to when run with CEDF. I have a program where I make some updates to a db2 table, write to vsam. When I run the application, the tasks always fails. But when I run it in CEDF, tasks are successfully done, no errors. Somebody got any idea why this happens?
rogerstrycova
 
Posts: 2
Joined: Tue Sep 14, 2021 8:32 pm
Has thanked: 0 time
Been thanked: 0 time

Re: CICS program output different when ran using CEDF.

Postby sergeyken » Sun Oct 03, 2021 7:07 pm

rogerstrycova wrote:I have a problem where my CICS application gives a different result compared to when run with CEDF. I have a program where I make some updates to a db2 table, write to vsam. When I run the application, the tasks always fails. But when I run it in CEDF, tasks are successfully done, no errors. Somebody got any idea why this happens?

Based on the provided information, there is only one idea: something goes wrong.
Javas come and go, but JCL stays forever.
User avatar
sergeyken
 
Posts: 216
Joined: Wed Jul 24, 2019 10:12 pm
Has thanked: 5 times
Been thanked: 19 times

Re: CICS program output different when ran using CEDF.

Postby Robert Sample » Sun Oct 03, 2021 8:22 pm

the tasks always fails
This tells us absolutely nothing that we could use to help you. When you say "fails", do you mean:
- the task abends (and if so, WHAT IS THE ABEND CODE CICS TELLS YOU?)
- the task goes into a loop and has to be canceled
- the updates are not applied to the database (and if so, what are the SQL codes?)
- the write to the VSAM data set fails (and if so, what are the file status codes for the write?)
- some other problem / issue / result?

I have actually seen this exact behavior in the past. The CICS program was issuing improper MAP commands (it's been many years so I don't recall the exact sequence of commands). When run with CEDF, the screen displays between each command prevented the map problem from happening. The root cause turned out to be COBOL code that was falling through an exit and getting into the CICS MAP code when it should not have been.
Robert Sample
Global moderator
 
Posts: 3664
Joined: Sat Dec 19, 2009 8:32 pm
Location: Dubuque, Iowa, USA
Has thanked: 1 time
Been thanked: 272 times


Return to CICS

 


  • Related topics
    Replies
    Views
    Last post