Re: JCL Question

R.Skorupka wrote: >I dare to disagree. Completely. Feel free to do that. Search the archives. My reply is for those who don't have those automation software. >1. ControlM (and others) did that despite of the reasons above. Agreed. I'm indeed using those %%variables to generate datasets and rep

Re: JCL Question

W dniu 2011-07-14 19:56, Elardus Engelbrecht pisze: R. Skorupka wrote: I believe this is main reason why JCL haven't been enhanced to have such facilities. BIG customers - those which IBM listen to - already have such facilities (in Job Scheduler) and have no reason to push IBM. Partly true

Re: JCL Question

Indeed that becomes important. When I was working on a 200 ( and growing) node jesx/rscs/ power systems it became extremely complex as sometimes when a job floated it became let's say difficult to figure out. When it became fun trying to contact the various tech people to find out about the Sys

Re: JCL Question

R. Skorupka wrote: >I believe this is main reason why JCL haven't been enhanced to have such >facilities. BIG customers - those which IBM listen to - already have such >facilities (in Job Scheduler) and have no reason to push IBM. Partly true, but the actual reason has been stated many times h

Re: JCL Question

In , on 07/13/2011 at 09:04 PM, Mike Schwab said: >I have done an IEBGENER to a INTRDR to run the same job until I broke >the loop. That's not iteration in JCL. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see We don'

Re: JCL Question

W dniu 2011-07-13 14:52, McKown, John pisze: I'd likely use JES exit 2 to insert // SET DATE=... // SET TIME=... and so on into the JCL stream immediately after the JOB card. And I like Job Scheduler Utilities for such purposes. For example ControlM has %%variables, with strong support for d

Re: JCL Question

> The trick is to run a process at 23:59:59 everyday to update the MCDATE > member > in a proclib that is in your JES2 proclib concatenation. We've done this for > years and it works well. This is exactly what we do at our shop. In case the user needs to use variables in SYSIN DD type datase

Re: JCL Question

> The ability to iterate is. Of course, that can be done with recursion > rather than explicit loops, but JCL doesn't have that either Looping/iteration, while desirable, is NOT a requirement to be a programming language. Just stepping through is adequate! - Ted MacNEIL eamacn...@yahoo.ca Twitte

Re: JCL Question

On Wed, Jul 13, 2011 at 1:07 PM, Shmuel Metz (Seymour J.) wrote: > >>Looping constructs are not required to make it a programming >>language. > > The ability to iterate is. Of course, that can be done with recursion > rather than explicit loops, but JCL doesn't have that either. > > -- >     Shmue

Re: JCL Question

How about EZACFSM1? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mosley, George Sent: Tuesday, July 12, 2011 1:28 PM To: IBM-MAIN@bama.ua.edu Subject: JCL Question Hello All. We're trying to set up a batch job that will app

Re: JCL Question

We create thousands of datasets with a date stamp as a qualifier. See example: //BJKBR14 JOB 1,'BRYAN K.',CLASS=Z,MSGCLASS=X,MSGLEVEL=(1,1) //INCL INCLUDE MEMBER=MCDATE //STEP005 EXEC PGM=IEFBR14 //DD1 DD DSN=SH

Re: JCL Question

In <1340844227-1310499369-cardhu_decombobulator_blackberry.rim.net-208261873-@b12.c1.bise6.blackberry>, on 07/12/2011 at 07:36 PM, Ted MacNEIL said: >I disagree. >JCL meets all criteria to be a programming language. Nonsense. >It doesn't do everything, but what language does? Irrelevant. Th

Re: JCL Question

In <45e5f2f45d7878458ee5ca679697335502e25...@usdaexch01.kbm1.loc>, on 07/12/2011 at 12:57 PM, "Staller, Allan" said: >IIRC, static system symbols can be substituted in JCL. For STC and TSU, but not for batch. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

Re: JCL Question

In <887215793-1310501180-cardhu_decombobulator_blackberry.rim.net-1377146756-@b12.c1.bise6.blackberry>, on 07/12/2011 at 08:06 PM, Ted MacNEIL said: >Looping constructs are not required to make it a programming >language. The ability to iterate is. Of course, that can be done with recursion r

Re: JCL Question

In , on 07/12/2011 at 03:35 PM, Jonathan Goossen said: >Job Control Language Gesundheit! That's not even a claim that it's a programming language. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see We don't care. We don

Re: JCL Question

On 7/13/2011 6:52 AM, R.S. wrote: No, in general it is matter of definition. My English is poor, but let me present another example, as off topic as dog's one: A car. In my country, Combi (Wagon) car is named in folders as 5-doors car. Hatchback is also 5-doors or 3-doors. Does anyone use the tai

Re: JCL Question

- > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Brian Westerman > Sent: Wednesday, July 13, 2011 1:00 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: JCL Question > > I have a UJV exit that we market which allows you to create > variables

Re: JCL Question

W dniu 2011-07-13 10:44, Binyamin Dissen pisze: On Wed, 13 Jul 2011 10:28:33 +0200 "R.S." wrote: :>W dniu 2011-07-12 21:36, Ted MacNEIL pisze: :>> I disagree. :>> JCL meets all criteria to be a programming language. :>> It doesn't do everything, but what language does? :>Watch the name: JOB

Re: JCL Question

On Wed, 13 Jul 2011 10:28:33 +0200 "R.S." wrote: :>W dniu 2011-07-12 21:36, Ted MacNEIL pisze: :>> I disagree. :>> JCL meets all criteria to be a programming language. :>> It doesn't do everything, but what language does? :>Watch the name: JOB CONTROL language. How many legs does a dog have, if

Re: JCL Question

W dniu 2011-07-12 21:36, Ted MacNEIL pisze: I disagree. JCL meets all criteria to be a programming language. It doesn't do everything, but what language does? Watch the name: JOB CONTROL language. In fact there is no big value in JCL classification, especially as there is no single exact defi

Re: JCL Question

I have a UJV exit that we market which allows you to create variables for BATCH jobs as well as STC's. At our customer sites we use it to control the DSN's of the backups and hundreds of other jobs. The users also take advantage of the capabilities, (the ones that know how to read the manual :

Re: JCL Question

> When we run this job, we hard code JUL09.@1408 to the end of the SYSPRINT dataset > name. > Is there a way to have the JCL automatically add the datestamp You should look at the system symbols for DUMPSRVR and see if they might be usable. It has things like date and time (various flavors) that

Re: JCL Question

02:08 PM > Subject: Re: JCL Question > Sent by: IBM Mainframe Discussion List > > contrary to popular misconceptions, JCL is not a programming > language, meaning it's not used to manipulate data. To append data > onto any existing file, code disp=mod instead of shr/new/old a

Re: JCL Question

>No looping construct. >Has TIC Looping constructs are not required to make it a programming language. It makes it easier, but it's not required. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- For IBM-MAIN subscribe /

Re: JCL Question

programming language. Has TIC :>Ted MacNEIL :>eamacn...@yahoo.ca :>Twitter: @TedMacNEIL :> :>-Original Message- :>From: Cris Hernandez #9 :>Sender: IBM Mainframe Discussion List :>Date: Tue, 12 Jul 2011 12:08:22 :>To: :>Reply-To: IBM Ma

Re: JCL Question

al Message- From: Cris Hernandez #9 Sender: IBM Mainframe Discussion List Date: Tue, 12 Jul 2011 12:08:22 To: Reply-To: IBM Mainframe Discussion List Subject: Re: JCL Question contrary to popular misconceptions, JCL is not a programming language, meaning it's not used to manipulate d

Re: JCL Question

Alan -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mosley, George Sent: Tuesday, July 12, 2011 10:28 AM To: IBM-MAIN@bama.ua.edu Subject: JCL Question Hello All. We're trying to set up

Re: JCL Question

1, Mosley, George wrote: > From: Mosley, George > Subject: JCL Question > To: IBM-MAIN@bama.ua.edu > Date: Tuesday, July 12, 2011, 1:27 PM > Hello All. > > We're trying to set up a batch job that will append a > datestamp to a dataset name. > For example: > >

Re: JCL Question

On 7/12/2011 1:27 PM, Mosley, George wrote: We're trying to set up a batch job that will append a datestamp to a dataset name. //SYSPRINT DD DSN=STRG.SRDF.INVTRKS.JUL09.@1408, Is there a way to have the JCL automatically add the datestamp? Not per se, but you could add code for the submission/

Re: JCL Question

2, 2011 1:28 PM To: IBM-MAIN@bama.ua.edu Subject: JCL Question Hello All. We're trying to set up a batch job that will append a datestamp to a dataset name. For example: //S0 EXEC PGM=EMCSRDF //SYSPRINT DD DSN=STRG.SRDF.INVTRKS.JUL09.@1408, //STORCLAS=BASE,MGMTCLAS=MEDIUM, //

Re: JCL Question

IIRC, static system symbols can be substituted in JCL. Check the Init & Tuning Guide for details as what the static system symbols are. Try: //SYSPRINT DD DSN=STRG.SRDF.INVTRKS.&SYSDATE., //STORCLAS=BASE,MGMTCLAS=MEDIUM, //DISP=(,CATLG), //SPACE=(TRK,(15,15),RL

Re: JCL Question

On Tue, 12 Jul 2011 17:27:58 +, Mosley, George wrote: > >Is there a way to have the JCL automatically add the datestamp? > No. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@b

JCL Question

Hello All. We're trying to set up a batch job that will append a datestamp to a dataset name. For example: //S0 EXEC PGM=EMCSRDF //SYSPRINT DD DSN=STRG.SRDF.INVTRKS.JUL09.@1408, //STORCLAS=BASE,MGMTCLAS=MEDIUM, //DISP=(,CATLG), //SPACE=(TRK,(15,15),RLSE),

Re: If Else JCL question

Sorry for the delayed response... Yes, it is permissible to omit the continuation mark. >From the z/OS V1R10.0 MVS JCL Reference manual section 17.1.4: Continuing a Relational Expression You can continue relational-expressions on the next JCL statement. Break the relational-expression where a

SV: SV: SV: If Else JCL question

> -Ursprungligt meddelande- > Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För Paul > Gilmartin > Skickat: den 24 januari 2011 14:55 > Till: IBM-MAIN@bama.ua.edu > Ämne: Re: SV: SV: If Else JCL question > > On Mon, 24 Jan 2011 12:37:38

Re: SV: SV: If Else JCL question

On Mon, 24 Jan 2011 12:37:38 +0100, Thomas Berg wrote: > >My main dislike with IF..THEN etc. is that the resulting JCL >is not easy to read (for me at least). With a keyword at >each EXEC it is at least more compact. And You don't have to > FSVO "easy to read" and "compact". Compare CM Poncelet'

SV: SV: If Else JCL question

> -Ursprungligt meddelande- > Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För Paul > Gilmartin > Skickat: den 22 januari 2011 01:11 > Till: IBM-MAIN@bama.ua.edu > Ämne: Re: SV: If Else JCL question > > On Fri, 21 Jan 2011 13:28:51 +0100, Th

Re: If Else JCL question

Paul Gilmartin wrote: On Fri, 21 Jan 2011 02:01:45 +, CM Poncelet wrote: Any boolean tests can be performed with 'COND=', but not so with 'IF ELSE etc.' We have already discussed this in the past. Sorry; I missed that. But please show me how 'IF ELSE ...' handles the follow

Re: If Else JCL question

Paul Gilmartin wrote: On Fri, 21 Jan 2011 02:01:45 +, CM Poncelet wrote: Any boolean tests can be performed with 'COND=', but not so with 'IF ELSE etc.' We have already discussed this in the past. Sorry; I missed that. Actually, I did not realise 'IF ELSE ...' now supports bo

If Else JCL question

This thread, like other long-running ones, has degenerated into a slanging match over trivia. As a matter of formal syntax COND= is not so powerful as IF-THEN-ELSE, and assertions to the contrary do no credit to the logical prowess of those who make them. Anciently there was in fact a distin

Re: SV: If Else JCL question

On Fri, 21 Jan 2011 13:28:51 +0100, Thomas Berg wrote: >I would have preferred something like this instead of the delivered IF..THEN >logic: > >//S050 EXEC WHATEVER,RUNIF=(RC,LE,4,S010) >RUNIF=(RC,8,S010) >RUNIF=(RUN,S020) >

Re: If Else JCL question

is Hernandez #9 Sent: Friday, January 21, 2011 4:38 PM To: IBM-MAIN@bama.ua.edu Subject: Re: If Else JCL question COND=EVEN and COND=ONLY only take effect when there is a system or user abend returned, they have nothing to do with cond code checking. If either failed to perform according to specs,

Re: If Else JCL question

wrote: > From: Stan Weyman > Subject: Re: If Else JCL question > To: IBM-MAIN@bama.ua.edu > Date: Friday, January 21, 2011, 10:34 AM > << Beware of COND=ONLY to > suppress execution.  Decades ago, a > colleague did that, but a prior step ABENDed.  > Embarrassing >

Re: If Else JCL question

s nor failure is ever final... -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Friday, January 21, 2011 10:22 AM To: IBM-MAIN@bama.ua.edu Subject: Re: If Else JCL question On Fri, 21 Jan 2011 08:08:32 -0600, Robert Birdsall wrot

Re: If Else JCL question

On Fri, 21 Jan 2011 08:08:32 -0600, Robert Birdsall wrote: >Similar to Gil's reply - skip if you've had enough... >... >// IF (STEPA.RC = 4 AND STEPB.RC = 0 AND STEPC.RUN = FALSE AND >// STEPD.RC = 8 AND STEPE.RUN = FALSE) OR >... > Is it permissible to omit the continuation mark in co

Re: If Else JCL question

Similar to Gil's reply - skip if you've had enough... I did test the following for all 4 execute STEPF conditions and some do not execute STEPF conditions. It works correctly as far as I can tell. Change the MAXCC=0 or the ',COND=ONLY' as required to test any condition you want. //JOBNAME JOB

Re: If Else JCL question

On Thu, 20 Jan 2011 15:11:40 -0800, Edward Jaffe wrote: >On 1/19/2011 10:11 AM, Donald Johnson wrote: >> We used to use a program called KABOOM, which did not exist (as I suspect >> with BLOWUP). One JCL statement, and a very prominent S806 abend. > >We use: > >//ABEND806 EXEC PGM=ABEND806 > >Thi

SV: If Else JCL question

; Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För Paul > Gilmartin > Skickat: den 21 januari 2011 07:37 > Till: IBM-MAIN@bama.ua.edu > Ämne: Re: If Else JCL question > > On Fri, 21 Jan 2011 02:01:45 +, CM Poncelet > wrote: > > >Any boole

Re: If Else JCL question

> -Original Message- > From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick > > [ snip ] > But what COND says is "execute if 4 is less than the return code". [ snip ] Almost: "Execute UNLESS 4 is less than the return code." -jc-

Re: If Else JCL question

On Fri, 21 Jan 2011 02:01:45 +, CM Poncelet wrote: >Any boolean tests can be performed with 'COND=', but not so with 'IF >ELSE etc.' We have already discussed this in the past. > Sorry; I missed that. >But please show me how 'IF ELSE ...' handles the following: > >Execute STEPF if >- STEPA s

Re: If Else JCL question

On 20 January 2011 21:31, John Eells wrote: > Erik Janssen wrote: >> >> We use EXEC PGM=IEFBR15, but the funny thing was when I used EXEC >> PGM=KABOOM or something like that (because obviously it doesn't matter what >> you use as long as the program doesn't exist), some incident manager >> inform

Re: If Else JCL question

>subtract the time spent in that RPGN from 100% to find true CPU busy on >systems that might have low utilization effects. Except for the fact that software measurements suffer from the fact that not all CPU consumed is capured. - Ted MacNEIL eamacn...@yahoo.ca

Re: If Else JCL question

Erik Janssen wrote: We use EXEC PGM=IEFBR15, but the funny thing was when I used EXEC PGM=KABOOM or something like that (because obviously it doesn't matter what you use as long as the program doesn't exist), some incident manager informed me that the standard to force an S806 abend was to use

Re: If Else JCL question

Any boolean tests can be performed with 'COND=', but not so with 'IF ELSE etc.' We have already discussed this in the past. But please show me how 'IF ELSE ...' handles the following: Execute STEPF if - STEPA sets CC=04, STEPB sets CC=00, STEPC did not execute, STEPD sets CC=08 and STEPE did n

Re: If Else JCL question

> By "as advertised", do we mean: > > IEFBR15 CSECT > BR15 > END "we" do. > I like ABEND806. Until some novice tries to generalize: > > //STEP EXEC PGM=ABEND213 > > ... and complains that it still ABENDs with 806, not 213. ROTF - hadn't thought of that. You must deal

Re: If Else JCL question

On Fri, 21 Jan 2011 11:16:46 +1100, Shane Ginnane wrote: >I usually keep an IEFBR15 laying around for test purposes. >And like Eds', this does as advertised. >Best to keep such away from your "incident manager" ;-) > By "as advertised", do we mean: IEFBR15 CSECT BR15

Re: If Else JCL question

Shane, Have you been hiding that IEFBR15 from me? I was using IFEBR14. As we know DNA stands for National Dyslexic Association...:) Wayne On Fri, Jan 21, 2011 at 11:16 AM, Shane Ginnane wrote: > I usually keep an IEFBR15 laying around for test purposes. > And like Eds', this does as advertised

Re: If Else JCL question

I usually keep an IEFBR15 laying around for test purposes. And like Eds', this does as advertised. Best to keep such away from your "incident manager" ;-) Shane ... On Fri, Jan 21st, 2011 at 10:47 AM, Erik Janssen wrote: > We use EXEC PGM=IEFBR15, but the funny thing was when I used EXEC >

Re: If Else JCL question

Honestly, I no longer know. I just know it's confusing as heck, and I have yet to see a defense of it. (Well, John Gilmore seemed to think it was understandable, if not perhaps defensible). On 1/20/2011 at 3:00 PM, in message , Greg Shirey wrote: > Either I'm confused too, or COND says "do NO

Re: If Else JCL question

erwerp: Re: If Else JCL question On 1/19/2011 10:11 AM, Donald Johnson wrote: > We used to use a program called KABOOM, which did not exist (as I suspect > with BLOWUP). One JCL statement, and a very prominent S806 abend. We use: //ABEND806 EXEC PGM=ABEND806 This program does exactly what

Re: If Else JCL question

On 1/19/2011 10:11 AM, Donald Johnson wrote: We used to use a program called KABOOM, which did not exist (as I suspect with BLOWUP). One JCL statement, and a very prominent S806 abend. We use: //ABEND806 EXEC PGM=ABEND806 This program does exactly what its name implies. ;-) -- Edward E Jaffe

Re: If Else JCL question

%$%$#@$CONDCODES<<<<<<<<<<<<<<<<<< John Donnelly National Semiconductor Corporation 2900 Semiconductor Drive Santa Clara, CA 95051 408-721-5640 408-470-8364 Cell cjp...@nsc.com -Original Message- From: IBM Mainframe Discuss

Re: If Else JCL question

Either I'm confused too, or COND says "do NOT execute if 4 is less than the return code"; that is - COND=(4,LT). Unless you meant something else... Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick Sent: Thursday, J

Re: If Else JCL question

>Where was blue kryptonite when we needed it! Somebody save me! C'mon! - Ted MacNEIL eamacn...@yahoo.ca -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET

If Else JCL question

Mark Pace wrote: | I wasn't looking for a lesson. Thank you very little. and I was not offering one to Mr Pace but to others here who may prefer logic to sloganeering. The relational expressions a > b and b < a are equivalent; and either can be obtained from the other by simple, readily l

Re: If Else JCL question

I wasn't looking for a lesson. Thank you very little. On Thu, Jan 20, 2011 at 3:57 PM, john gilmore wrote: > I was looking this morning at data on non-multiple and multiple human > births in which live births were classified as single(si), double(do), > triple(tr), quadruple (qa), or quintuple (q

If Else JCL question

I was looking this morning at data on non-multiple and multiple human births in which live births were classified as single(si), double(do), triple(tr), quadruple (qa), or quintuple (qi). Now if one were interested only in single births it would be folly to write ¬do & ¬tr & ¬qa & ¬qi inste

Re: If Else JCL question

M-MAIN@bama.ua.edu] On Behalf Of >> Paul Gilmartin [paulgboul...@aim.com] >> Sent: 20 January 2011 02:45 >> To: IBM-MAIN@bama.ua.edu >> Subject: Re: If Else JCL question >> >> On Wed, 19 Jan 2011 13:13:03 -0800, Cris Hernandez #9 wrote: >> >> >

Re: If Else JCL question

On Thu, 20 Jan 2011 20:04:08 +, CM Poncelet wrote: >But one of the most useful purposes of COND= testing is >COND=(0,LE,) ... which ensures the current jobstep will NOT >execute unless previous jobstep did NOT execute. So 'NOT >logic' can still do what 'IF ELSE etc.' cannot. CP > What am I m

Re: If Else JCL question

On Thu, 20 Jan 2011 14:22:36 -0500, Mark Pace wrote: >One thing I've been taught since I was in school 30+ years ago. Do not use >NOT logic. COND goes against everything I've worked at my entire career. > Assemblerthink. Or maybe BASICthink. The IF ... GOTO ... paradigm tersified and carried t

Re: If Else JCL question

_ From: IBM Mainframe Discussion List [IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin [paulgboul...@aim.com] Sent: 20 January 2011 02:45 To: IBM-MAIN@bama.ua.edu Subject: Re: If Else JCL question On Wed, 19 Jan 2011 13:13:03 -0800, Cris Hernandez #9 wrote: suppose I

Re: If Else JCL question

>One thing I've been taught since I was in school 30+ years ago. >Do not use NOT logic. >COND goes against everything I've worked at my entire career. I started as a JCL jockey (Prod Support/Job Scheduling) in 1981, and I believe the 'NOT Logic' is why a lot of people have problems. I used to ke

Re: If Else JCL question

t the COND > right. > > > From: IBM Mainframe Discussion List [IBM-MAIN@bama.ua.edu] On Behalf Of > Paul Gilmartin [paulgboul...@aim.com] > Sent: 20 January 2011 02:45 > To: IBM-MAIN@bama.ua.edu > Subject: Re: If Else JCL question > > On

Re: If Else JCL question

t: Re: If Else JCL question On Wed, 19 Jan 2011 13:13:03 -0800, Cris Hernandez #9 wrote: >suppose I'm old school, never saw a need to code IF-THEN-ELSE in JCL, only use >cond code checking and never have any issues with step execution or job flow. >the only cond code testing I e

Re: If Else JCL question

> -Original Message- > From: IBM Mainframe Discussion List On Behalf Of Gainsford, Allen > > > the only cond code testing I ever do when writing procs is, > > "if it's true, it's through", meaning the step/job won't > > execute if the COND is true. > > Heh. I learned that one as "If true

Re: If Else JCL question

On Wed, 19 Jan 2011 13:13:03 -0800, Cris Hernandez #9 wrote: >suppose I'm old school, never saw a need to code IF-THEN-ELSE in JCL, only use >cond code checking and never have any issues with step execution or job flow. >the only cond code testing I ever do when writing procs is, "if it's true,

Re: If Else JCL question

> the only cond code testing I ever do when writing procs is, > "if it's true, it's through", meaning the step/job won't > execute if the COND is true. Heh. I learned that one as "If true, don't do". Works out the same, and is catchy enough for me to remember it... Allen Gainsford ==

Re: If Else JCL question

won't execute if the COND is true. I guess IBM added all that IF-THEN-ELSE stuff because too many coders never learned that lesson. hernandez --- On Wed, 1/19/11, Erik Janssen wrote: > From: Erik Janssen > Subject: Re: If Else JCL question > To: IBM-MAIN@bama.ua.edu > D

Re: If Else JCL question

IN@bama.ua.edu > Date: 01/19/2011 12:08 PM > Subject: Re: If Else JCL question > Sent by: IBM Mainframe Discussion List > > On Wed, 19 Jan 2011 09:50:56 -0600, Jonathan Goossen wrote: > > >We force an ABEND by calling a program that always ABENDs > > > >//STEP1

Re: If Else JCL question

On Wed, 19 Jan 2011 13:11:26 -0500, Donald Johnson wrote: >We used to use a program called KABOOM, which did not exist (as I suspect >with BLOWUP). One JCL statement, and a very prominent S806 abend. >*don* > Why do I do things the hard way!? I never considered that. >>//STEP EXEC PGM=I

Re: If Else JCL question

We used to use a program called KABOOM, which did not exist (as I suspect with BLOWUP). One JCL statement, and a very prominent S806 abend. *don* On Wed, Jan 19, 2011 at 1:07 PM, Paul Gilmartin wrote: > On Wed, 19 Jan 2011 09:50:56 -0600, Jonathan Goossen wrote: > > >We force an ABEND by calling

Re: If Else JCL question

On Wed, 19 Jan 2011 09:50:56 -0600, Jonathan Goossen wrote: >We force an ABEND by calling a program that always ABENDs > >//STEP1 ... >//IF (STEP1.RC EQ 0) then >//STEP2 ... >//ELSE >//SAEXEC PGM=BLOWUP >//ENDIF > Do you really _want_ the ABEND? If not, why not move the ELSE and ENDIF to

Re: If Else JCL question

, John Verzonden: woensdag 19 januari 2011 15:14 Aan: IBM-MAIN@bama.ua.edu Onderwerp: Re: If Else JCL question I like using COND= on the JOB card. Suppose each step must end with an RC LE 0. //MYJOB JOB COND=(4,LE) This flushes the remaining steps in a job after the step which gets an RC greater

Re: If Else JCL question

MEGA Life and Health Insurance Company.SM > -Original Message- > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mark Pace > Sent: Wednesday, January 19, 2011 7:58 AM > To: IBM-MAIN@bama.ua.edu > Subject: If Else JCL question > &

Re: If Else JCL question

Our QuickRef states that the nesting level is 15. IBM Mainframe Discussion List wrote on 01/19/2011 08:19:08 AM: > From: Mark Pace > To: IBM-MAIN@bama.ua.edu > Date: 01/19/2011 08:19 AM > Subject: Re: If Else JCL question > Sent by: IBM Mainframe Discussion List >

Re: If Else JCL question

07:58 AM > Subject: If Else JCL question > Sent by: IBM Mainframe Discussion List > > Seems to be a very rookie question, but I can't find the answer. > > I have a series of JCLs that I want to put together as 1 JCL with IF THEN to > test RC. What I can't find is a

Re: If Else JCL question

sidiaries of HealthMarkets, Inc. -The Chesapeake > Life Insurance Company(r), Mid-West National Life Insurance Company of > TennesseeSM and The MEGA Life and Health Insurance Company.SM > > > > > -Original Message- > > From: IBM Mainframe Discussion List > > [mail

Re: If Else JCL question

Life and Health Insurance Company.SM > -Original Message- > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mark Pace > Sent: Wednesday, January 19, 2011 7:58 AM > To: IBM-MAIN@bama.ua.edu > Subject: If Else JCL question > &

If Else JCL question

Seems to be a very rookie question, but I can't find the answer. I have a series of JCLs that I want to put together as 1 JCL with IF THEN to test RC. What I can't find is a way to stop the JCL if a step has a bad RC. ie: STEP1 IF (STEP1.RC EQ 0) then STEP2 ELSE ABEND or GOTO EOJ or somehow en

Re: simple JCL question

On Wed, 25 Aug 2010 14:21:46 -0500, Mike Schwab wrote: >> >Or, consider the procname in >//stepname EXEC procname,keywords=values >to be the positional parameter, with an option is to replace >'procname' with 'PROC=procname' or 'PGM=pgmname'. > Humpty Dumpty. If so, it was irresponsible to choose

Re: simple JCL question

On Wed, Aug 25, 2010 at 12:33 PM, Shmuel Metz (Seymour J.) wrote: > In <008301cb4453$4242cec0$c6c86c...@org>, on 08/25/2010 >   at 05:44 AM, Charles Mills said: > >>PGM= is positional, is it not? > > Yes. I could make a case that it shouldn't be, and it's as confusing > as the default for SPACE.

Re: simple JCL question

In <008301cb4453$4242cec0$c6c86c...@org>, on 08/25/2010 at 05:44 AM, Charles Mills said: >PGM= is positional, is it not? Yes. I could make a case that it shouldn't be, and it's as confusing as the default for SPACE. Or take the change in the processing of DD overrides - please! -- Sh

Re: simple JCL question

Charles Mills wrote: | PGM= is positional, is it not? and this of course is a debater's point, but it is one I should have been tempted to make too in response to a too sweeping "WTF?". The first parameter following EXEC may be any one of o PGM=, o PROC=, or just o . This last defaul

Re: simple JCL question

On 24 Aug 2010 13:25:12 -0700, st...@trainersfriend.com (Steve Comstock) wrote: >Exactly. In my JCL class, I proclaim, "parameters are either >keyword or positional", then I explain what those two terms >mean; then when we get to the EXEC statement I recall that >earlier assertion and then say, "I

Re: simple JCL question

PGM= is positional, is it not? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Shmuel Metz (Seymour J.) Sent: Tuesday, August 24, 2010 8:38 AM To: IBM-MAIN@bama.ua.edu Subject: Re: simple JCL question In , on 08/19/2010 at 06

Re: simple JCL question

Paul Gilmartin wrote: On Tue, 24 Aug 2010 11:38:09 -0400, Shmuel Metz (Seymour J.) wrote: You generally laud JCL for embracing Assembler's syntactic conventions. Another it spurned was order-independence of keyword arguments. WTF? Keyword arguments in JCL are order-independent. Perhaps you are

Re: simple JCL question

(nor do I want them to). Rex -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Tuesday, August 24, 2010 3:07 PM To: IBM-MAIN@bama.ua.edu Subject: Re: simple JCL question On Tue, 24 Aug 2010 11:38:09 -0400, Shmuel Metz (Se

Re: simple JCL question

On Tue, 24 Aug 2010 11:38:09 -0400, Shmuel Metz (Seymour J.) wrote: > >>You generally laud JCL for embracing Assembler's syntactic >>conventions. Another it spurned was order-independence of keyword >>arguments. > >WTF? Keyword arguments in JCL are order-independent. Perhaps you are >thinking of r

Re: simple JCL question

On Tue, Aug 24, 2010 at 11:38 AM, Shmuel Metz (Seymour J.) wrote: >Perhaps you are > thinking of references to specific steps, but there's no analog to > that in assembler. Sure there is -- the order of the instructions! (Although with OoO Execution, even THAT changes...) Yes, I'm kidding. Of co

Re: simple JCL question

In , on 08/19/2010 at 06:37 PM, Paul Gilmartin said: >You generally laud JCL for embracing Assembler's syntactic >conventions. Another it spurned was order-independence of keyword >arguments. WTF? Keyword arguments in JCL are order-independent. Perhaps you are thinking of references to speci

  1   2   3   >