ason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Thursday, December 24, 2020 5:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: B
Spiegel [dspiegel...@hotmail.com]
Sent: Thursday, December 24, 2020 6:21 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: Build and submit proc
Hi Gil,
It's not UNIX for more than one reason:
- UNIX has no drive letter
- UNIX uses a forward-slash, not, a backward-slash
- UNIX does not
Hi Gil,
It's not UNIX for more than one reason:
- UNIX has no drive letter
- UNIX uses a forward-slash, not, a backward-slash
- UNIX does not have File Extensions (although theoretically it could)
Regards
David
On 2020-12-24 17:58, Paul Gilmartin wrote:
On Thu, 24 Dec 2020 22:14:15 +, Seymo
On Thu, 24 Dec 2020 22:14:15 +, Seymour J Metz wrote:
>Eunix has even less typing:
>
>Thu 12-24-20 12:49:37{2}[h:\] cp --help
>Usage: G:\USR\BIN\cp.exe [OPTION]... [-T] SOURCE DEST
> or: G:\USR\BIN\cp.exe [OPTION]... SOURCE... DIRECTORY
>
That doesn't look much like UNIX to me. I guess that
On Thu, 24 Dec 2020 16:02:07 -0500, Steve Thompson wrote:
>So write a PROC that puts INPUT with SYSUT1 and OUTPUT with SYSUT2.
>
I could imagine that nowadays TRSMAIN is merely an ALIAS entry point that
branches to AMATERSE with an alternate DDNAME list.
>I even took this a step further and had
Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Wayne Bickerdike [wayn...@gmail.com]
Sent: Thursday, December 24, 2020 2:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: Build and submit proc
Except move is propogate a copy. CA IDEAL has MOVE A TO B and SET B = A
So write a PROC that puts INPUT with SYSUT1 and OUTPUT with SYSUT2.
I even took this a step further and had OUTPUT get deleted first before
AMATERSE.
Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct
mistaks
> On Dec 24, 2020, at 3:56 PM, Paul Gilmartin
> <00
On Wed, 23 Dec 2020 15:40:23 +, Pommier, Rex wrote:
>
>Yeah there's a problem with it - a human problem. It's easy when in a hurry
>to miss the fact they're reversed and key the input dataset name in the SYSUT2
>and the output in the SYSUT1 if you're not paying attention. Yeah I know it's
t; of Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
> Sent: Wednesday, December 23, 2020 12:55 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [External] Re: Build and submit proc
>
> On Wed, 23 Dec 2020 09:36:31 -0800, Tom Brennan wrote:
>
> >Thanks Rex, ex
List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Wednesday, December 23, 2020 12:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: Build and submit proc
On Wed, 23 Dec 2020 09:36:31 -0800, Tom Brennan wrote:
>Thanks
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Paul Gilmartin
> Sent: Wednesday, December 23, 2020 9:56 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [External] Re: Build and submit proc
>
> On Wed, 23 Dec 2020 09:36:31
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Wednesday, December 23, 2020 11:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: Build and submit proc
On Wed, 23 Dec 2020 09:36:31 -0800, Tom Brennan wrote:
>Thanks Rex, exac
On Wed, 23 Dec 2020 09:36:31 -0800, Tom Brennan wrote:
>Thanks Rex, exactly what I was going to say.
>
>On 12/23/2020 7:40 AM, Pommier, Rex wrote:
>>
>> Yeah there's a problem with it - a human problem. It's easy when in a hurry
>> to miss the fact they're reversed ...
>>
"reversed"? Is there a
Thanks Rex, exactly what I was going to say.
On 12/23/2020 7:40 AM, Pommier, Rex wrote:
Yeah there's a problem with it - a human problem. It's easy when in a hurry to
miss the fact they're reversed and key the input dataset name in the SYSUT2 and
the output in the SYSUT1 if you're not paying
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Wednesday, December 23, 2020 8:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: Build and submit proc
On Tue, 22 Dec 2020 19:51:50 -0800, Tom Brennan wrote:
>
>... look
On Tue, 22 Dec 2020 19:51:50 -0800, Tom Brennan wrote:
>
>... look out if //SYSUT2 happens to be above //SYSUT1, ...
>
Is there a problem with that? I've done it regularly; about half
the time. And over 90% with //SYSUT1 DD DATA. Easier to read
if other DD statements are closer to EXEC.
--
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tom
Brennan [t...@tombrennansoftware.com]
Sent: Tuesday, December 22, 2020 10:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Build and submit proc
Oh I think I've made more than my share of mistakes of the years :)
But
e.com]
Sent: Tuesday, December 22, 2020 3:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Build and submit proc
Whew! Then I'm lucky I never really wrote any JCL - I always copy
something similar. In fact, if JCL had DNA I bet most could be traced
back to a single IEBGENER job, formed in a tide
Don't forget to compress the PDS frequently, or make it a PDSE.
Once we had hour long queues for a compile, so I wrote a CLIST to
execute the compile and link steps, took about 3 minutes.
On Tue, Dec 22, 2020 at 11:11 AM Fred Kaptein wrote:
>
> Hello,
> I would like to build a JCL batch job call
December 22, 2020 7:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Build and submit proc
On Tue, Dec 22, 2020 at 5:56 PM Seymour J Metz wrote:
> > IMO, you could replace all your JCL with REXX code.
>
> You'd have a hard time with scheduling if you tried that.
>
> > But
On Tue, Dec 22, 2020 at 5:56 PM Seymour J Metz wrote:
> > IMO, you could replace all your JCL with REXX code.
>
> You'd have a hard time with scheduling if you tried that.
>
> > But then the programmer needs to be a REXX expert
>
> Why? Most users aren't JCL experts. Besides, in some ways REXX is
IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
John McKown [john.archie.mck...@gmail.com]
Sent: Tuesday, December 22, 2020 6:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Build and submit proc
On Tue, Dec 22, 2020 at 2:44 PM Wayne Bickerdike wrote:
> Many moons ago, when I
On Tue, Dec 22, 2020 at 2:44 PM Wayne Bickerdike wrote:
> Many moons ago, when I was a trainee programmer I asked my senior
> programmer why IBM couldn't just get rid of JCL. He laughed. I was serious,
> still am 45 years later.
>
>
Why JCL even after all this time? Cost. Let's suppose IBM wan
Ignoring the wrong and/or irrelevant comments, anyone who is having trouble
running REXX, TSO, or ISPF in batch, please write to me directly. Chances
are, I've been there and done that. (See below.)
To get you started
1. Create a JCL PROC to start TSO in batch: You can do one of these.
nansoftware.com]
Sent: Tuesday, December 22, 2020 3:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Build and submit proc
Whew! Then I'm lucky I never really wrote any JCL - I always copy
something similar. In fact, if JCL had DNA I bet most could be traced
back to a single IEBGENER job, f
ot;
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Hobart Spitz [orexx...@gmail.com]
Sent: Tuesday, December 22, 2020 4:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Build a
On Tue, 22 Dec 2020 15:05:47 -0600, Hobart Spitz wrote:
>
>Still not enough? Write (or get your favorite assembler programmer to
>write) a CMS SLEEP like program. There might be one on a CBT tape or on
>the web.
>
Assembler!? CBT tape!? What rock have you been under for the few
decades that bo
Tom
Brennan
Sent: Tuesday, December 22, 2020 12:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Build and submit proc
*** EXTERNAL EMAIL - Use caution when opening links or attachments ***
Whew! Then I'm lucky I never really wrote any JCL - I always copy something
similar. In fac
There is the matter of MSTJCLxx :)
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Wayne Bickerdike
> Sent: Tuesday, December 22, 2020 12:43 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Build and submit proc
>
> Many moons a
On Tue, Dec 22, 2020 at 2:11 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Tue, 22 Dec 2020 13:14:07 -0600, Hobart Spitz wrote:
>
> >You can do it in batch REXX.
> >
> >Stop being brain-dead and thinking about everything in terms of JCL.
> >
> >I've don't write JC
On Wed, 23 Dec 2020 07:43:24 +1100, Wayne Bickerdike wrote:
>Many moons ago, when I was a trainee programmer I asked my senior
>programmer why IBM couldn't just get rid of JCL. He laughed. I was serious,
>still am 45 years later.
>
How do you solve the ENQ deadlock problem? Telephone the sysop
| fax: 616.653.2717
> >>
> >>
> >> -Original Message-
> >> From: IBM Mainframe Discussion List On
> Behalf
> >> Of Fred Kaptein
> >> Sent: Tuesday, December 22, 2020 12:11 PM
> >> To: IBM-MAIN@LISTSERV.UA.EDU
> >>
MD RSCB2H | Grand
Rapids, MI 49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf
Of Fred Kaptein
Sent: Tuesday, December 22, 2020 12:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Build and submit proc
**CAUTION EXTERNAL EMAIL**
**DO NO
On Tue, 22 Dec 2020 13:14:07 -0600, Hobart Spitz wrote:
>You can do it in batch REXX.
>
>Stop being brain-dead and thinking about everything in terms of JCL.
>
>I've don't write JCL anymore.
>
>JCL causes brain-damage.
>
Be nice, or at least stay on-topic and ad-rem, not ad-hominem.
JCL and the I
No need to be naughty here.
Roger W. Suhr
suhr...@gmail.com
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Hobart Spitz
Sent: Tuesday, December 22, 2020 2:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Build and submit proc
You can do it in batch REXX.
Stop
gt; Sent: Tuesday, December 22, 2020 12:11 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Build and submit proc
>
> **CAUTION EXTERNAL EMAIL**
>
> **DO NOT open attachments or click on links from unknown senders or
> unexpected emails**
>
> Hello,
> I would like to build a JCL
, December 22, 2020 12:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Build and submit proc
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
Hello,
I would like to build a JCL batch job called BACKUPS, that does the following:
1) STEP01
On Tue, 22 Dec 2020 12:23:49 -0500, David Spiegel wrote:
>
>The interpretation of JCL occurs before the execution starts. Hence,
>your result.
>If you were to SUBMIT your JCL to the internal reader in STEP02 (rather
>than trying to execute the BKUP Cataloged Procedure), the new job would
>read the
Fred Kaptein
Sent: Tuesday, December 22, 2020 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Build and submit proc
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, Don’t click links or open attachments as it may be a Phishing email,
which can steal your
Thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Hi Fred,
The interpretation of JCL occurs before the execution starts. Hence,
your result.
If you were to SUBMIT your JCL to the internal reader in STEP02 (rather
than trying to execute the BKUP Cataloged Procedure), the new job would
read the updated BKUP PROC.
Regards,
David
On 2020-12-22
No. The interpreter already read the jcl at translation time.
בתאריך יום ג׳, 22 בדצמ׳ 2020, 19:11, מאת Fred Kaptein <
fred.kapt...@telus.com>:
> Hello,
> I would like to build a JCL batch job called BACKUPS, that does the
> following:
> 1) STEP01
> Create a JCL proc in MYLIB.PROCLIB(BKUP)
>
Hello,
I would like to build a JCL batch job called BACKUPS, that does the following:
1) STEP01
Create a JCL proc in MYLIB.PROCLIB(BKUP)
2) STEP02
Execute the proc MYLIB.PROCLIB(BKUP)
My testing finds that STEP02 runs the proc in MYLIB.PROCLIB(BKUP) that was
built prior to submitting job
43 matches
Mail list logo
