Article View: comp.lang.asm370
Article #1056Re: JCL Question about the RC system Variable
From: Denis
Date: Fri, 31 Mar 2000 00:00
Date: Fri, 31 Mar 2000 00:00
58 lines
3142 bytes
3142 bytes
Thanx for your answers, but this does not answer my question The solutions you propose (COBOL, asm or IDCAMS) allows me to write a program for which the RC of the execution step will be 4. This is not what I want to achieve: What I want to do is, in the middle of a JCL, reset the internal value of RC stored somewhere by JES I want to say to JES is: From that execution point in the JCL, forget the maximum return code of all the previously executed steps (i.e. the global RC variable) and reset it to 4 (or force the value of the global RC indicator to 4) By "global RC indicator", I mean the RC variable handled by JES not related to any particular step, present in any JCL and that you can test in IF statements without the step qualifier.The solution you give allows me to force the value of the step.RC value for a particular step, not the "global" one. Thomas David Rivers wrote in message <38E4B15C.B33B23C6@dignus.com>... >Terry Heinze wrote: > >> You can't set the RC in JCL with a JCL statement, but you COULD exec a COBOL >> pgm that set the value of RETURN-CODE for the step the pgm was executed in. >> The value of the RC in your first step would remain that value for the >> during of the job. In other words, replace // SET RC=4 by // EXEC >> PGM=SETRC4 then test the result of the step executing SETRC4. Each step >> returns it's own RC, so in ob containing 4 steps, there are 4 different RCs >> you can test. > >Well - a COBOL program may be a little overboard; just write a quick >ASM program that puts 4 in R15 and does a BALR 14,15. That will >set the 4 as the RC. > >Something like: > > SET4RC CSECT > L 15,=F'4' > BALR 14,15 > LTORG > END SET4RC > >Assemble this, link it and there you go. > >A fancier version might, perhaps, look at the incoming PARMS >value (off of R1) and simply set the return code to whatever >that specified, etc... > > - Dave Rivers - > > >-- >rivers@dignus.com Work: (919) 676-0847 >Get your mainframe (370) `C' compiler at http://www.dignus.com > > >
Technical Details
Message-ID:
<8c2drm$ir1$1@hardcopy.ny.jpmorgan.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<8c1rst$dnl$1@hardcopy.ny.jpmorgan.com> <8c28kc$2a5k$1@newssvr04-int.news.prodigy.com> <38E4B15C.B33B23C6@dignus.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fd4af,c33c463b6179897e X-Google-Attributes: gidfd4af,public X-Google-Thread: 10d15b,42752b244b2e1d2d X-Google-Attributes: gid10d15b,public X-Google-Thread: 11415f,42752b244b2e1d2d X-Google-Attributes: gid11415f,public X-Google-Thread: f8131,42752b244b2e1d2d X-Google-Attributes: gidf8131,public X-Google-Thread: 101deb,42752b244b2e1d2d X-Google-Attributes: gid101deb,public From: "Denis" <grosnou@antispam.skynet.be> Subject: Re: JCL Question about the RC system Variable Date: 2000/03/31 Message-ID: <8c2drm$ir1$1@hardcopy.ny.jpmorgan.com> X-Deja-AN: 604818822 Distribution: inet References: <8c1rst$dnl$1@hardcopy.ny.jpmorgan.com> <8c28kc$2a5k$1@newssvr04-int.news.prodigy.com> <38E4B15C.B33B23C6@dignus.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Organization: J.P. Morgan & Co Newsgroups: comp.lang.asm370,comp.lang.cobol,comp.lang.pl1,bit.listserv.tsorexx,bit.listserv.ibm-main