This first question I would ask is does IBM actually "own" BatchPipes or
did the flog it off to an ISV like most of their other software? If it's
the latter then they will be in no position to make it freely available.
Secondly, rather than pine for something that isn't available why not
just
I think you have to remember that BatchPipes/MVS' origin story is
connecting existing batch job steps. I wouldn't want customers to have to
re-write e.g. in java.
One advantage is that it's easier to rework a pipeline - whether as a
fitting or between batch jobs - than rework some java code.
A
Thanks for the clarity. So BatchPipes are the plumbing to implement
streaming almost like the JCL equivalent of the Apache Kafka Streams API?
On 28/09/2021 4:00 pm, Martin Packer wrote:
I think you have to remember that BatchPipes/MVS' origin story is
connecting existing batch job steps. I woul
Ed Jaffe wrote:
>I meant to say there was _no defense_ that could be used by IBM against
>the rationale presented in the requirement.
Ok, then what you said indeed wasn't what you intended to say, as I suspected!
Just checkin', thanks.
("indefensible argument" means "the argument is easily atta
CBT file 527. DADSM or LISTICAT.
I have a slightly newer DADSM, mostly larger print fields.
Matthew
On Mon, 27 Sep 2021 15:26:53 -0500, Jasi Grewal wrote:
>Hi,
>
>I am interested in acquiring information on the DASD Datasets, which were
>updated recently and to understand the resources util
On 9/28/2021 8:17 AM, Phil Smith III wrote:
Ed Jaffe wrote:
I meant to say there was _no defense_ that could be used by IBM against
the rationale presented in the requirement.
Ok, then what you said indeed wasn't what you intended to say, as I suspected!
Just checkin', thanks.
("indefensible
On 9/28/21 10:01 AM, Ed Jaffe wrote:
I realized my grammatical mistake after the post was already out there,
but assumed readers would understand my meaning without the need for
follow-up clarification.
Obviously, I ASSuMEd incorrectly... 😕
Mistakes happen.
You've spoken to it.
Coffee is o
You could use the dsr smf records which will give you the types of open.
On Tue, Sep 28, 2021, 10:27 AM Matthew Stitt
wrote:
> CBT file 527. DADSM or LISTICAT.
>
> I have a slightly newer DADSM, mostly larger print fields.
>
> Matthew
>
> On Mon, 27 Sep 2021 15:26:53 -0500, Jasi Grewal wrote:
Purely by the way, but I've never really understood why so many REXX modules I
see start like this:
/* REXX */
/* Module: Name
Author: Bob Bridges the Magnificent
Purpose: Convert ANSI dates to internal format, or whatever. */
...instead of something like this:
/* This REXX conv
Sorry, Ed, was honestly unsure which direction you were pointing. Alles klar!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
I have this awkward feeling that we're fonder of boilerplate code than we
realise :-)
On Tue., Sep. 28, 2021, 21:54 Bob Bridges, wrote:
> Purely by the way, but I've never really understood why so many REXX
> modules I see start like this:
>
> /* REXX */
> /* Module: Name
> Author: Bob
On 29/09/2021 6:54 am, Bob Bridges wrote:
Purely by the way, but I've never really understood why so many REXX modules I
see start like this:
/* REXX */
/* Module: Name
Author: Bob Bridges the Magnificent
Purpose: Convert ANSI dates to internal format, or whatever. */
...inst
The "/* REXX */" part is required only if the REXX exec is to be run
from a PDS allocated to DDNAME=SYSPROC instead of to DDNAME=SYSEXEC.
SYSPROC is for CLISTs, SYSEXEC is for REXXs.
On 29/09/2021 02:07, Andrew Rowley wrote:
> On 29/09/2021 6:54 am, Bob Bridges wrote:
>> Purely by the way, bu
Hello all,
an OMVS question.
We are looking for a way to compare 2 filesystem structures, starting at root
'/'.
Differences we want to identify:-
1. directory
2. file
3. symlink
It is the last we are having trouble working out how to go about it.
Hoping someone has done this before.
Regard
Please do correct me if what I say is wrong or makes no sense.
diff -R /root1 /root2
Best output that to a file and analyze.
Setup both directories with git & git diff them via GitHub Desktop or GitKraken
or JetBrains's Space.
- KB
‐‐‐ Original Message ‐‐‐
On Wednesday, September 29t
On Tue, 28 Sep 2021 21:22:29 -0500, Bruce Hewson wrote:
>
>an OMVS question.
>
>We are looking for a way to compare 2 filesystem structures, starting at root
>'/'.
>
>Differences we want to identify:-
>
>1. directory
>2. file
>3. symlink
>
>It is the last we are having trouble working out how to
On Mon, 27 Sep 2021 11:39:17 -0500, Hobart Spitz wrote:
>
>Intra-JOB pipe - This would be similar to VIO; it doesn't exist otherwise.
>I think it would be a great feature.
>
Between steps? One might just as well use VIO.
-- gil
---
There may be a difference in 'the eye if the beholder':
/* REXX */
...is special: it is (obviously) the flag that indicates that this is rexx.
/* This REXX converts ANSI dates to internal format, or whatever. */
...is just a comment line. Anybody can change any comment at any ti
Ah, I just made the exact same point responding to this post... 😊 Sorry for
adding 'noise' to the discussion.
Fred!
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Andrew Rowley
Sent: woensdag 29 september 2021 03:07
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I vs
Else, ls -alR on both dirs.
Then, create a blank project in PyCharm/IntelliJ and navigate to the dir
containing these 2 listings.
Select both and then choose diff/compare.
Believe me, git style diff-ing is super neat and convenient, compared to the
standard diff we use on zOS.
-KB
‐‐‐ Origi
On Wed, 29 Sep 2021 05:48:25 +, kekronbekron wrote:
>Else, ls -alR on both dirs.
>Then, create a blank project in PyCharm/IntelliJ and navigate to the dir
>containing these 2 listings.
>Select both and then choose diff/compare.
>Believe me, git style diff-ing is super neat and convenient, com
Grep filters as appropriate in the middle, I suppose.
My main point being - make use of git style diff-ing.
- KB
‐‐‐ Original Message ‐‐‐
On Wednesday, September 29th, 2021 at 11:44 AM, Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Wed, 29 Sep 2021 05:48:2
Between steps can't be pipes, can be VIO. Between jobs can be pipes, can't
be VIO.
That second sentence depends on the ability to schedule two jobs (possibly
originally steps of the same job) alongside each other.
Fun stuff but / and somewhat complex - which is what inspired me to start
writing
23 matches
Mail list logo
