Page 2 of 2

Re: Set Return code higher than 4095

PostPosted: Fri Dec 18, 2015 2:45 pm
by BillyBoyo
Change the PGM= to IKJEFT1A or IKJEFT1B. Get some agreement at your site about which to do (assuming you've already asked around and no-one is doing this already).

Re: Set Return code higher than 4095

PostPosted: Fri Dec 18, 2015 3:37 pm
by pranav283
Hi,

I tried using both IKJEFT1A and IKJEFT1B and to my amazement, I got what I wanted to see. The job terminated with a max cc of 104 only !

Thanks a lot @UserName and @BillyBoyo !

But how did you know/figured out that it has something to do with TMPs ?

Re: Set Return code higher than 4095

PostPosted: Fri Dec 18, 2015 4:27 pm
by BillyBoyo
TMP is a new TLA on me.

When I read your question rather than just skimmed it I noticed the DB2 part. COBOL DB2 you're going to be running under TSO. TSO-in-batch (IKJEFT01) itself is "normalising" non-zero return-codes. The two alternate entry-points, IKJEFT1A and B, don't normalise the return-code. So seeing your actual JCL makes the problem simple. Actually, reading the question more closely helped a lot as well :-)

Re: Set Return code higher than 4095

PostPosted: Fri Dec 18, 2015 4:55 pm
by pranav283
TMPs refers to nothing but Terminal Monitor Programs, which I believe you have certainly figured out by now ! ;)

And I am completely new to the fact that IKJEFT01 program can too handle/normalize non-zero return codes, rather IKJEFT1A/B can not.
Can you please share more info or any attachment/link to which you can direct me to.
Most importantly, Thanks a lot for helping me with the issue.

Pranav

Re: Set Return code higher than 4095

PostPosted: Sat Dec 19, 2015 5:47 pm
by NicC
There are other references within this very forum and all over the internet and, especially, in the IBM documentation. Why can you not search for it youself and, in doing so, enhance your knowledge and place bookmarks for future reference?