Re: [IBM External] Re: The Business Case for BatchPipes in the z/OS Base (was: ... Pipes ...)

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

Re: OMVS - comparing directories for differences

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,

Re: OMVS - comparing directories for differences

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

Re: PL/I vs. JCL

True, but it is a recommended best practice to start all rexx execs with the /* REXX */ comment. IBM recommends this because REXX execs can be transported to other SAA environments. Joe On Tue, Sep 28, 2021 at 8:58 PM CM Poncelet wrote: > The "/* REXX */" part is required only if the REXX exec

Re: [IBM External] The Business Case for BatchPipes in the z/OS Base (was: ... Pipes ...)

Martin, Do you have that book somewhere still? I spent 15 minutes on google but lots of links lead nowhere. NetRexx does have a rather complete CMS Pipelines implementation (www.netrexx.org ) and I was wondering what I need to do to also have these ’halfpipes’ and

Re: OMVS - comparing directories for differences

If you want to compare file systems, you can try fscp at https://github.com/IBM/IBM-Z-zOS/tree/main/zOS-Tools-and-Toys/fscp Bill Schoen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: PL/I vs. JCL

> An earlier ply, not quoted here, asserted that column 1 is reserved for > carriage > control. That seems to conflate source code with SYSPRINT. Not at all, and more than C'1' in an assembly program makes the source code SYSPRINT. > Does TSO honor "ALLOCATDE DD(SYSUT1) DSN(*) DLM('xx') ...

Re: PL/I vs. JCL

> I recall that the /* is a hardware feature of some card readers. I believe a > 2540 card reader generated some special status (unit exception?) when it > read a card with /* in the first two columns, No, the detection of /*, or whatever DLM specifies, is strictly software, The 2540 generates

Re: OMVS - comparing directories for differences

Stuff like this from IBM's coffers is pretty neat! - KB ‐‐‐ Original Message ‐‐‐ On Wednesday, September 29th, 2021 at 6:19 PM, Bill Schoen wrote: > If you want to compare file systems, you can try fscp at > > https://github.com/IBM/IBM-Z-zOS/tree/main/zOS-Tools-and-Toys/fscp > >

Re: RMM Extended Format Record Layout

hello Robert I am interested in the subject, since soon I must install the product and use cartridges with a capacity of 8000 -> 400. Any progress you have made (jcl's, installation tips, ... etc) will be very helpful. Regards

Re: PL/I vs. JCL

On Sep 29, 2021, at 9:22 AM, Seymour J Metz wrote: > > TSO SYSPROC is the only case I know of where /* REXX */ is required. It’s required in OMVS as well. There, by experiment, the ‘/*’ must be at the beginning of the first line and the next thing after it, other than spaces, must be ‘REXX’.

Re: [IBM External] Re: The Business Case for BatchPipes in the z/OS Base (was: ... Pipes ...)

On Wed, 29 Sep 2021 06:54:09 +, Martin Packer wrote: > >Between steps can't be pipes, can be VIO. Between jobs can be pipes, can't >be VIO. > Pipes could work between steps if the PIPE SUBSYS has an implied ELASTIC stage. But that's just reinventing VIO. PIPE SUBSYS must do some buffering to

Re: PL/I vs. JCL

I used REXX in OS/2, but can't remember if it had any special requirements for the first line. I can't find any manuals online (yet). Tony Thigpen Seymour J Metz wrote on 9/29/21 10:22 AM: TSO SYSPROC is the only case I know of where /* REXX */ is required. -- Shmuel (Seymour J.) Metz

Re: PL/I vs. JCL

A quick search on ‘comment’ does not show such a requirement. René > On 29 Sep 2021, at 16:02, Seymour J Metz wrote: > > Does the ANSI standard require the first line to be a comment? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > >

Re: PL/I vs. JCL

For OS/2 the first line must be either a comment or an EXTPROC, roughly equivalent to a *IX shebang. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tony Thigpen

Re: PL/I vs. JCL

On Wed, 29 Sep 2021 02:58:19 +0100, CM Poncelet wrote: >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. >  No, it is also required if the REXX exec is to be run from a UNIX directory. In that case the

Re: PL/I vs. JCL

I forgot a point I meant to make in this reply. We discussed how to run CLIST or REXX directly from a source PDS without benefit of SYSPROC or SYSEXEC. There are several products in a z/OS configuration that are delivered by the vendor with a self contained package of execs. One of these is called

Re: OMVS - comparing directories for differences

Is it possible to use "or" as an inclusive or operator? My TSO/E REXX Reference document says I have to use the "|" as an inclusive or operator. Lennie Dymoke-Bradshaw https://rsclweb.com ‘Dance like no one is watching. Encrypt like everyone is.’ -Original Message- From: IBM Mainframe

Re: PL/I vs. JCL

By directly, do you mean explicit use of EXEC? There's an operand to distinguish CLIST from REXX. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Skip Robinson Sent: Wednesday, September

Re: OMVS - comparing directories for differences

I run this in batch and use superc to compare the two inputs. > On Sep 29, 2021, at 16:21, Paul Gilmartin > <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Wed, 29 Sep 2021 15:47:42 -0400, James Crudele wrote: > >> /* Rexx HFSDIRC */ >> parse arg dir1

Re: OMVS - comparing directories for differences

On Wed, 29 Sep 2021 19:47:59 -0400, James Crudele wrote: >You can try this: > >//LISTDIR EXEC PGM=IKJEFT01, >// PARM='HFSDIRC / /SERVICE' >//* >//SYSPROC DD DISP=SHR,DSN=SYS1.SBPXEXEC >// DD

Re: PL/I vs. JCL

No: If you know that the procedure being run is a CLIST, you can code the CLIST operand. If you know that the procedure being run is a REXX exec, you can code the EXEC operand. If you do not code the CLIST or EXEC operand on the EXEC command, the EXEC command processor

Re: OMVS - comparing directories for differences

You can try this: //LISTDIR EXEC PGM=IKJEFT01, // PARM='HFSDIRC / /SERVICE' //* //SYSPROC DD DISP=SHR,DSN=SYS1.SBPXEXEC // DD DISP=SHR,DSN=userid.TEST.REXX //SYSTSPRT DD SYSOUT=*

Re: EXTERNAL EMAIL: Re: zPDT Learner's Edition

> be limited by an 80 column wide editing session That hasn't been the case for four decades. I was editing on 132-wide and 160-wide screens long before z/OS existed. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe

Re: PL/I vs. JCL

There are many TSO command processors. The CLIST operand parsing is a small subset of what a command processor can do using IKJPARSE. I'm not sure what you mean by "framework" in this context, but the macros to define the command syntax are not rocket science. I wish that IBM had included

Re: PL/I vs. JCL

No; if you code an explicit DSN then SYSPROC and SYSEXEC are irrelevant. It's only whn you code *(member) that EXEC looks in the SYSPROC and SYSEXEC concatenations[*]. Also, EXEC doesn't look for DD statements, it looks at the current state of the session, which could have been modified by

Re: PL/I vs. JCL

Or use ALTLIB. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Skip Robinson [jo.skip.robin...@gmail.com] Sent: Wednesday, September 29, 2021 6:55 PM To:

Re: PL/I vs. JCL

> I believe that if a CLIST begins withh a /* Rexx */ comment but that "operand" > is omitted it will execute as a CLIST regardless. No: it examines the first line. > OMVS is worse. If an EXEC is spawned with a fully-qualified path, spawn > invokes the Rexx interpreter passing it the filename

Re: PL/I vs. JCL

On Wed, 29 Sep 2021 17:11:50 +, Seymour J Metz wrote: >By directly, do you mean explicit use of EXEC? There's an operand to >distinguish CLIST from REXX. > I believe that if a CLIST begins withh a /* Rexx */ comment but that "operand" is omitted it will execute as a CLIST regardless. OMVS

Re: PL/I vs. JCL

On Wed, 29 Sep 2021 10:48:53 -0700, Skip Robinson wrote: >Is that operand required? > Only sometimes. IBM made it as complicated as possible: -- gil

Re: OMVS - comparing directories for differences

I recall a rexx called hfsdirc. Not sure where I found it. I’m sure I can share if needed. > On Sep 28, 2021, at 22:22, Bruce Hewson wrote: > > Hello all, > > an OMVS question. > > We are looking for a way to compare 2 filesystem structures, starting at root > '/'. > > Differences we

Re: OMVS - comparing directories for differences

/* Rexx HFSDIRC */ parse arg dir1 dir2 junk dir1 = strip(dir1) dir2 = strip(dir2) if dir1 = "" or dir2 = "" then do say "Two directories must be specified" exit 4

Re: PL/I vs. JCL

How about invoking a module directly? No SYSPROC is involved here. EX 'dsn(member)' I have no way to test it at the moment. On Wed, Sep 29, 2021 at 7:22 AM Seymour J Metz wrote: > TSO SYSPROC is the only case I know of where /* REXX */ is required. > > > -- > Shmuel (Seymour J.) Metz >

Re: PL/I vs. JCL

Is that operand required? On Wed, Sep 29, 2021 at 10:12 AM Seymour J Metz wrote: > By directly, do you mean explicit use of EXEC? There's an operand to > distinguish CLIST from REXX. > > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > >

Re: PL/I vs. JCL

Hm, not a bad point, Andrew. I should maybe keep it in mind when I write for others, or when something I write for myself may eventually get into the public domain. --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* Why don't our civics courses teach pupils what the word "usurped"

Re: PL/I vs. JCL

Not sure we got here from 'PLI', but so be it. I was deeply embedded in CLIST writing by the time REXX made its way to TSO/E. Here are a few points I haven't seen from others. -- CLIST was modeled or at least inspired by the TSO command processor. That's the framework that handles most 'native'

Re: PL/I vs. JCL

On 9/29/2021 7:22 AM, Seymour J Metz wrote: TSO SYSPROC is the only case I know of where /* REXX */ is required. In my experience, TSO/E is quite forgiving about the syntax of the first line in a REXX. You can say /* REXX is a Great Language */" and it works just fine. However, the z/OS

Re: OMVS - comparing directories for differences

On Wed, 29 Sep 2021 15:47:42 -0400, James Crudele wrote: >/* Rexx HFSDIRC */ >parse arg dir1 dir2 junk >dir1 = strip(dir1) >dir2 = strip(dir2) >if dir1 = "" or dir2 = "" then do > say "Two

Re: PL/I vs. JCL

That's why we get the big bucks. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Wednesday, September 29, 2021 11:01 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PL/I vs. JCL On Wed, 29 Sep 2021

Re: PL/I vs. JCL

>From memory, at the time Rexx first came to TSO/E the documented requirement was that line 1 must have a /* comment that included "Rexx", not case sensitive. I'm not sure, but I think line 1 could also contain code! I can't imagine why z/OS would be more finicky, unless the z/OS people saw so

Re: PL/I vs. JCL

An EX 'dsn(member)' would require no /* REXX */ card if 'dsn' is allocated to DDNAME=SYSEXEC in the user's TSO logon PROC, but would require it if is allocated to DDNAME=SYSPROC in ditto.    The OS first checks whether a SYSEXEC DD is coded and, if yes, whether the '(member)' is in it - and, if

AW: EXTERNAL EMAIL: Re: zPDT Learner's Edition

It took some days for me to put some thought into this pricing aspect. From a guy who is fascinated with the entire Z platform and all the things there to discover I am totally going to get the license. As long as IBM decides to make it available in Germany, of course. Now, if I put myself 5

Re: OMVS - comparing directories for differences

My thanks to all who responded, but especially to Bill Schoen for the fscp exec. Although not being permitted to access guthub from office directly, I was able to get a copy of the exec. I am testing now. As to original reason, looking at merging the new IBM z/OS supplied UNIX configuration

Re: z/OS Dataset Last Date Used Information

There are tools on the CBT tape.. If you're licensed for MXG, there are also tools there. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jasi Grewal

Re: [IBM External] The Business Case for BatchPipes in the z/OS Base (was: ... Pipes ...)

I think it's gone. Does anyone still have a PDF of it? Thanks, Martin Martin Packer WW z/OS Performance, Capacity and Architecture, IBM Technology Sales +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://mainframeperformancetopics.com

Re: [IBM External] The Business Case for BatchPipes in the z/OS Base (was: ... Pipes ...)

Well my friends, I found it for ye. https://web.archive.org/web/20060224031157/http://www.redbooks.ibm.com/redbooks/pdfs/sg242557.pdf *Saying this to nobody on this thread, but to some kind of people* Now tell me what's important... knowing how to get to stuff or knowing by memory all the new

Re: PL/I vs. JCL

Does the ANSI standard require the first line to be a comment? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tony Thigpen [t...@vse2pdf.com] Sent: Wednesday,

Re: PL/I vs. JCL

TSO SYSPROC is the only case I know of where /* REXX */ is required. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Phil Smith III [li...@akphs.com] Sent: Wednesday,

Re: PL/I vs. JCL

Also of note, z/VM REXX requires that the first thing in a ReEXX program *must* be a comment. It does not require the word REXX, just a comment. "/* */" is seen a lot. z/VSE REXX does not require that the first thing be a comment, but suggests that the first thing be a comment starting with

Re: [IBM External] The Business Case for BatchPipes in the z/OS Base (was: ... Pipes ...)

Ahh basicsI remember -Original Message- From: IBM Mainframe Discussion List On Behalf Of kekronbekron Sent: Wednesday, September 29, 2021 8:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM External] The Business Case for BatchPipes in the z/OS Base (was: ... Pipes ...) **

Re: [IBM External] The Business Case for BatchPipes in the z/OS Base (was: ... Pipes ...)

Thank you KB! You can imagine my disappointment at finding all the links to it at the IBM Redbooks site to be broken. Cheers, Martin Martin Packer WW z/OS Performance, Capacity and Architecture, IBM Technology Sales +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs:

Re: PL/I vs. JCL

Bob Bridges wrote: >Purely by the way, but I've never really understood why so many REXX modules I see start like this: > /* REXX */ I think (a) it's documented that way in some places; (b) Some environments may even require that; (c) that's how some/many examples have it; and (d) it's

Re: [IBM External] The Business Case for BatchPipes in the z/OS Base (was: ... Pipes ...)

BTW, are most of these recommendations still valid? - KB ‐‐‐ Original Message ‐‐‐ On Wednesday, September 29th, 2021 at 7:34 PM, Martin Packer wrote: > Thank you KB! > > You can imagine my disappointment at finding all the links to it at the > > IBM Redbooks site to be broken. > >