|
View previous topic :: View next topic
|
| Author |
Message |
rss0213
New User
Joined: 20 Jan 2010
Posts: 26
Location: Alabama
|
|
|
|
Hi. We have a program that is completing successfully, but is returning a Condition Code 2024. We can't find anything in the books or on Google about this error code. Any idea what could be generating this?
One thing that might be helpful: this is a COBOL program that does an EXCI call to a CICS program. The call is executed successfully and returns the value we need, but the program still completes with CC 2024. I've attached the job output in case that's helpful. |
|
| Back to top |
|
 |
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK
|
|
|
|
| please do not attach - I, for one, will not or cannot read it. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
The attached output is useless since it appears to be line wrapped with extra spaces compressed.
A condition code 2024 is NOT something you will be able to find on the Internet. The condition code 2024 means that YOUR COBOL PROGRAM SET A RETURN CODE OF 2024. Whether it did this because of the EXCI command failing, or for some other reason, there's no way we can tell. The only certain thing at this point is that someone AT YOUR SITE must look at the source code FOR YOUR PROGRAM to determine why the 2024 occurred. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
After some further investigation, I uncovered a Control-M warning message in your job:
| Code: |
11.22.54 CTR001I CONTROL-M/RESTART, REL 6.3.09 STARTED FOR JOB JAXACCTT
11.22.54 CTR008I PROCESSING PARAMETERS: R2,,,BL,.$FIRST,,DDD,00
11.22.54 CTR024W MISSING "NONCAT2 CONTROL MEMBER" NAME PARAMETER
11.22.54 CTR026W MISSING "ORDERID" PARAMETER
11.22.55 CTR235I NONCAT2 REQUEST FROM PROCSTEP WIRACCTD PGMSTEP WIRACCT1 TO PROCSTEP PGMSTEP |
so it appears likely that you have a Control-M problem with your job. Contact your site support group if you don't know how to fix it, since they can help you with the specifics at your site of how Control-M is set up and how to resolve these messages. |
|
| Back to top |
|
|
rss0213
New User
Joined: 20 Jan 2010
Posts: 26
Location: Alabama
|
|
|
|
| Thanks for looking Robert. The Control-M re-start step actually completed successfully. The CC 2024 is not set anywhere in our code. We thought it might be getting set somewhere in the EXCI call, but then we found a blurb on the web about DFHXCIS (EXCI module, or one of its subroutines) not clearing some registers, which can cause random condition codes to be set. So we added code to set the RC to zero if the call completes successfully. Hopefully this issue is resolved now. |
|
| Back to top |
|
|
|
|
