I submit that there is something else to consider. People tend to approach
any new language thinking in terms of the language that they were most
skilled in previously. Because REXX is so flexible, there is little need
to learn some of the unique features of REXX. Some people never take off
the
ns are commonly
over 100s of stages, and 1000s of stages are not uncommon.
REXX is the new C.
On Sat, Jul 1, 2023 at 8:15 AM Walt Farrell wrote:
> On Thu, 29 Jun 2023 18:10:06 -0500, Hobart Spitz
> wrote:
>
> >https://chat.openai.com/share/1718b445-7a89-47a3-ab23-b670aa8c221
https://chat.openai.com/share/1718b445-7a89-47a3-ab23-b670aa8c2211
OREXXMan
Q: What do you call the residence of the ungulate with the largest antlers?
A: A moose pad.
:-D
Would you rather pass data in move mode (*nix piping) or locate mode
(Pipes) or via disk (JCL)? Why do you think you rarely
I don't see a question, so I'm responding to what I think you want.
It has long been true that BUFSIZE defaults to the largest
available BLKSIZE The requirement was written in the 1980s. (It might
depend on your access method.) So, I very much doubt the the BLISIZE
difference is the problem.
T
Steve wrote:
>So the question of where LISTDSI is found is moot, in that my
>environment is correct once using "CC = 'LISTDSI' ('SYSUT1 FILE')".
The quotes around LISTDSI serve no function, unless you are inside a
routine with the same name and you don't want recursion. Since the
interpreter only
On Mon, 20 Feb 2023, 17:07 Steely.Mark, wrote:
> Here is a simple REXX for LISTDSI:
>
> /* A SIMPLE REXX TEST PROGRAM */
> variable = 'data.set.name'
> x = LISTDSI(variable)
> say x
>
Be careful. If you meant a fully qualified dataset name, you need to code
this.
Variable = " 'data.set.name' "
Steve;
You need to brush up on your REXX.
- TSO is the default ADDRESSing environment, in most cases. Adding or
removing ADDRESS TSO will not make any difference.
- The -3 you are getting means there is no such command found. The manual
clearly states that LISTDSI is a built-in function under
rarely see *nix commands
with more than a dozen filters, while Pipelines specifications are commonly
over 100s of stages, and 1000s of stages are not uncommon.
REXX is the new C.
On Mon, Feb 20, 2023 at 3:05 PM Hobart Spitz wrote:
> LISTDSI is a REXX function, It is not a host command; ADDRESS
LISTDSI is a REXX function, It is not a host command; ADDRESS has no
effect on LISTDSI.
Use CALL LISTDSI DSNVAR ... or IF LISTDSIO\(DSNVAR) = 0 THEN ... , e.g, in
any mixed case where you have stored the dataset name in DSNVAR or the
variable of your choice. (All REXX functions can also be inv
IMHO, the fault lies in the character stream orientation of UNIX, C, HTML
etc. The shorted-sighted design was motivated by the limited budgets and
underpowered systems of many early UNIX users.
On record oriented systems, (z/OS and z/VM) common operations are faster,
because the needed informatio
You have these options:
1 - Select the member manually, and invoke your REXX edit macro.
2 - Write another module the invokes the edit service in the library and
member, and runs the edit macro.
3 - Write one dual mode module. I do not recommend this.
Edit commands are only valid in REXX EXECs th
Just taking a guess here: Most ISPF services run at the same task level as
the invoking user program. I believe that EDIT (and View) run at a
different task level, and therefore may not have access to the same
parameter pointers.
OREXXMan
Q: What do you call the residence of the ungulate with t
> signal evac
> End
> Else Do
> rptRsn = 'Move from N-Backup library complete'
> End
>End
>call buildrpt
>"LMMLIST Dataid("Nbkp") OPTION(free)"
>"LMCLOSE Dataid("Nlib")"
>
Are you doing LMFREE, on the dataid from LMINIT, when you are finished with
each library?
It sounds like you are exceeding resources for LMINITs.
I don't think FREE/CLOSE is needed. LMINIT and LMFREE are faster, more
reliable and easier to use.
It also sounds like you are not getting the return
On Fri, Feb 3, 2023 at 9:00 AM zMan wrote:
> O my.
>
> I was on a call with a bunch of customers a few years ago. One of them was
> having a very basic problem with a COBOL program calling our product. I
> explained that they needed to put the name of into a variable
> that gets passed as the fi
When you get the error, display zerrsm and zerrlm.
We need to see your code.
I think Seymour is asking the right question.
On Fri, 3 Feb 2023, 07:19 Cameron Conacher, <03cfc59146bb-dmarc-
requ...@listserv.ua.edu> wrote:
> Good Morning,
> I have a small REXX which essentially copies members
All;
Your feedback has been appreciated.
Here is the plan for the next update, tentatively for Feb. 1. Please let
me know if there is anything important I missed.
*2023/02 Update (as planned) *
* Additional filters and functions (Any case is OK.):
On Sat, Jan 7, 2023 at 8:10 PM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
> On Fri, 6 Jan 2023 15:33:44 -0600, Hobart Spitz wrote:
> >
> >https://www.cbttape.org/updates.htm
> >
> >
> https://docs.google.com/presentation/d/1C7htK9I
On Sat, Jan 7, 2023 at 11:17 AM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
> On Fri, 6 Jan 2023 15:33:44 -0600, Hobart Spitz wrote:
> >
> >
> https://docs.google.com/presentation/d/1C7htK9I4rL-4pUZcdhfeA4-IY2Kjxm-HJQ4fuljMs3I/edit?usp=sharing
zPipe is a piping facility for z/OS. It's available on CBT Tape file1035
on the updates page.
https://www.cbttape.org/updates.htm
The CBT file contains fuller code and more modules than in the presentation
below.
Here is the presentation about it.
https://docs.google.com/presentation/d/1C7htK
This is an initial version of zPipe and includes some of the most important
modules. The primary goal being to get feedback on the approach. The rest
of the 100 modules are more Pipelines compatible and I hope to add them to
the CBT distribution after I convert them to this technique and finish
t
w to
adjust my plans for CDT, Dallas. As of this writing it is 18:33.
Thanks.
All the best.
- Hobart Spitz
(USA, cell) 443-297-7879
OREXXMan
Q: What do you call the residence of the ungulate with the largest antlers?
A: A moose pad.
:-D
Would you rather pass data in move mode (*nix piping) o
I missed the "authorized" part the first time around.
I don't think anyone has mentioned the TSOEXEC command. It runs an
authorized command (authorized) from an unauthorized environment. (No, I
didn't leave out a blank. TSOEXEC is the full 7 character command name.
Google it.)
OREXXMan
Q: W
IDCAMS commands, like RACF commands are TSO commands. No need for LINKMVS;
I 've never done it, so it might not even work.
Be sure to follow TSO dataset name syntax: Fully qualified names in
apostrophes or unqualified names without.
"listc ent(ispf.ispprof)"
for example.
On Tue, 16 Aug 2022, 1
I don't think VARSTORAGE(HIGH) is the best approach. I would stick with
LOW. The message suggests that RACF is running out of storage. .OUTTRAP
knows nothing about userlists, so it's probably not an OUTTRAP
message. Further, the return code is not from OUTTRAP, it is from the
command being execu
I think it's worth mentioning that the reason that SET must be
unconditional is that JES has to issue ENQs after, AFAIK, the initial JCL
scan and before execution starts. If a dataset has an embedded symbolic,
doing the correct ENQ when the value might change at execution time could
cause all kind
I've found the REXX function sysvar("symdef", "jobname") words well in more
than one site.
OREXXMan
Would you rather pass data in move mode (*nix piping) or locate mode
(Pipes) or via disk (JCL)? Why do you think you rarely see *nix commands
with more than a dozen filters, while Pipelines specif
AFAIK, the interpreter uses 31 bit addresses.
The default is LOW probably to ensure compatibility with 24 bit programs.
On Tuesday, December 14, 2021, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Tue, 14 Dec 2021 18:38:44 -0600, Hobart Spitz wrote:
>
I don't think anyone has suggested PROFILE VARSTORAGE(HIGH).
On Tuesday, December 14, 2021, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Tue, 14 Dec 2021 23:14:10 +, Gibney, Dave wrote:
>
> >Can you stop with the non-breaking space failing html
> >
> It's not e
.
REXX is the new C.
On Thu, Dec 9, 2021 at 3:15 PM Hobart Spitz wrote:
> XC
>
> OREXXMan
> Would you rather pass data in move mode (*nix piping) or locate mode
> (Pipes) or via disk (JCL)? Why do you think you rarely see *nix commands
> with more than a dozen filter
XC
OREXXMan
Would you rather pass data in move mode (*nix piping) or locate mode
(Pipes) or via disk (JCL)? Why do you think you rarely see *nix commands
with more than a dozen filters, while Pipelines specifications are commonly
over 100s of stages, and 1000s of stages are not uncommon.
REXX is
Really How is your solution a single instruction?
Here are single instruction solutions.
"pipe < ddname=sortin | sort unique | > ddname=sortout"
or
"pipe < your.data | sort unique | > your.output
or
// EXEC PGM=PIPE,PARM='< your.data | sort unique | > your.output'
People really need to stop
Cross posted to IBM-MAIN, TSO REXX, and Pipelines.
The ISPF stacking character can be set to "|", but TSO tries to execute
the passed stack data after each command. If that could be disabled, data
could be passed from program to program, providing a stack based piping
capability.
Does anyone
Years ago, before HSM, I wrote some code to deal with issues like this.
IIRC, it went something like this.
- About 4 times a day a job would run to identify problem packs
(volumes) by relative ranking, noting the 4 worst of each. IIRC, it used
the LSPACE(?) macro.
- Low free space.
AFAIK, RXY format instructions support negative offsets just fine.
LHY 5,-1(0,12)
On Sun, 24 Oct 2021, 7:55 am Peter Relson, wrote:
> Eric R posted (from the PoP):
>
> When, during the generation of the address, an
> address is obtained that exceeds the value allowed
> for the address size (2^
Ed, Johnathan;
You guys are *so *lucky.
A few quick notes to get you started:
- Unlike Unix piping, terminal output from the last stage is not
implied. (You'll find this makes sense later.)
pipe < some.dsn | count words lines | term
- The <, >, and >> are filters on their own, also
Cross posted to IBM-MAIN and CMSTSO-Pipelines lists.
Overview:
1. An ALU (Arithmetic Logical Unit) load estimation shows CMS/TSO
Pipelines is orders of magnitude more ALU efficient than UNIX piping.
2. UNIX piping is significantly better than JCL step-to-step data
passing and, consequ
Gil wrote:
>On Mon, 27 Sep 2021 07:26:51 -0500, Hobart Spitz wrote:
>>I'm going to pivot here. I'm putting my support behind putting BatchPipes
>>in the z/OS base (rather than just Pipes). If you agree, please
>>write/support such a requirement and/or educate your
I'm going to pivot here. I'm putting my support behind putting BatchPipes
in the z/OS base (rather than just Pipes). If you agree, please
write/support such a requirement and/or educate your management to get
interested. BatchPipes includes BatchPipesWorks, a not so current, but
still highly use
As a developer, I love REXX and I love Pipes. Together, they are
programmer heaven. Whenever I write something new, whether in z/OS or
z/VM, I write a REXX EXEC. Under z/OS, I SPAWN the EXEC when I want to run
it in batch.
I have used BatchPipes only briefly, but I know Pipes fairly well. Pipe
if it writes a record to, say, two
> >destinations, it's got to copy one of them.
> >
> It could be deferred; Copy-on-Write, optimizing for what Hobart earlier
> calledd the "typical case" of stages that don't modify the data.
> But incurring the complexity of a
as been looking for an HLL for program products; REXX is that language.
On Mon, Sep 20, 2021 at 8:10 PM Phil Smith III wrote:
> Hobart Spitz wrote, in part:
>
> >This is a great comment. I hadn't given that much thought to the
> question.
>
> >Not to split hairs, but
milar to a SORTOUT exit that implements
> this switch?
>
> On Mon, Sep 20, 2021 at 4:27 PM Hobart Spitz wrote:
> >
> > Phil;
> >
> > This is a great comment. I hadn't given that much thought to the
> question.
> >
> > Not to split hairs, but I
Paul said:
> I'm guessing the atypical case is a stage such as FANOUT which
necessarily
copies the data.
Not sure what you mean by atypical. FANOUT is typical in the respect that
it doesn't create an actual copy of the input record. It just looks like
it. FANOUT, and non-record-changing stages
and 1000s of stages are not uncommon.
IBM has been looking for an HLL for program products; REXX is that language.
On Mon, Sep 20, 2021 at 12:48 PM Phil Smith III wrote:
> Hobart Spitz wrote, in part:
>
> >The case *for *Pipes in the z/OS base.:
>
> > 2. Hardware usage would
Thank you for your relevant and helpful comments. They are very much
appreciated, as I omitted some topics. I'll do my best to address them
here. Pardon the lack of brevity.
Concerning EXECIO:
Yes, the z/OS and z/VM EXECIO versions are mostly incompatible.
Once you have Pipes you don't n
IMHO, the Business Cases on Pipes in the z/OS Base are as follows. (Pipes
is already available as part of BatchPipes.)
The case *for *Pipes in the z/OS base.:
1. Development costs would drop for customers, vendors, and IBM, since
everyone could use Pipes in their software.
2. Hardware u
To the OP, have you considered the ISRDDN command SAVE?
On running ISRDDN in batch, you can make it work if you can skip
full-screen displays. These approaches come to mind:
1 - Use CONTROL NONDISPL ... .
2 - ISPSTART has options to execute commands.
3 - ZSTART can be set to execute commands on s
.
On Tue, Dec 22, 2020 at 3:33 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> 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. Ther
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 o
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.
On Tuesday, December 22, 2020, Jousma, David <
01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:
> I would build the JCL, and then FTP
Had a similar problem. I used this solution.
http://billlalonde.tripod.com/back/stup006.htm
On Monday, December 14, 2020, Seymour J Metz wrote:
> Yes - you only have one level of expansion.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> _
REPRO?
On Saturday, December 12, 2020, Seymour J Metz wrote:
> CCSID would determine which characters were treated as valid. I would not
> expect IDCAMS to second guess the user's InfoPrint parameters.
>
> Ideally there should be a common print validation service and every
> utility would have a
CMS/TSO Pipes!!!
On Sat, 14 Nov 2020, 8:26 pm Mike Schwab, wrote:
> You have to remember that S/360 was the first 8 bit computer. Prior
> computers used 4 bits for a digit and 6 bits for a character. They
> designed EBCDIC to be easily converted for use with existing 7 track
> tape drives, pri
Incorrect.
You use a pipe-fitting on the JCL DD, something like "bpread | sysout q | >
dd=out2 | > dd=out3" for as many outputs as you like.
I'm iffy on the exact syntax for specifying the stream separator, but the
fanout stage can do the same:
"(end ?) bpread | fo: fanout | sysout q ? fo: | d
They find each other via the name of the pipe.
OREXXMan
JCL is the buggy whip of 21st century computing. Stabilize it.
Put Pipelines in the z/OS base. Would you rather process data in move mode
or locate mode?
IBM has been looking for an HLL for program products; REXX is that language.
On Wed
If there are any z/VMers subscribed, it would be interesting to also
compare the PIPE Q output under CMS.
Thanks.
OREXXMan
JCL is the buggy whip of 21st century computing. Stabilize it.
Put Pipelines in the z/OS base. Would you rather process data in move mode
or locate mode?
IBM has been looki
o help you with this. I hope you’re
> staying safe and healthy.
>
No apologies necessary. If you know anyone who can help, please get us in
contact or share this email.
>
>
> Best regards,
>
> Cheryl
>
>
>
> ===
>
> Cheryl Watson
>
&
Pipes.
On Thu, 28 Mar 2019, 2:11 pm Kirk Wolf, wrote:
> You could do it with Co:Z Batch + Dataset Pipes without creating a
> temporary file:
>
> //SHELL EXEC PGM=COZBATCH
> //IN DD DISP=SHR,DSN=...
> //OUT DD DISP=(NEW,CATLG),DSN=...,
> // DCB=(RECFM=VB,LRECL=27994),SPACE=
> //STDIN D
I think you need to give us some more information. I'm not familiar with
XQUERY and it's quirks. What kind of response are you expecting? Is the
output dataset empty?
That said, it's been so long since I've run anything in batch without REXX
I don't recall if vanilla TSO reports non-zero return
Peter cover it well.
A DISPLAYd panel cannot invoke a CLIST.
A SELECTd panel can invoke any command, CLIST, REXX EXEC, or PGM, by
setting &ZSEL.
On Sun, 19 Aug 2018, 12:36 am Jesse 1 Robinson,
wrote:
> I have an app that imbeds REXX code in a panel. The REXX code happens to
> be in the )Init sec
Keep in mind that if you do VDEFINE(s), you MUST do VDELETE(s) for the same
variables, before you FREEMAIN (e.g.) and/or exit. Otherwise, enjoy
tracking down mysterious S0C4s, etc. ISPF will think that the storage is
still allocated to the function pool variable(s) and may read from or write
to i
Substring?
OREXXMan
JCL is the buggy whip of 21st century computing. Stabilize it.
Put Pipelines in the z/OS base. Would you rather process data one
character at a time (Unix/C style), or one record at a time?
IBM has been looking for an HLL for program products; REXX is that language.
On Mon,
I think there are positive ways to view this.
- According to one report Broadcom has a history of buying troubled
companies and turning them around.
- If prices go up, some sites will be forced to drop products that are
not used much, or are otherwise not earning their keep, in favor o
It is typical in buyouts for the buyer's stock to go down and the company
being bought to go up, with exceptions.
OREXXMan
JCL is the buggy whip of 21st century computing. Stabilize it.
Put Pipelines in the z/OS base. Would you rather process data one
character at a time (Unix/C style), or one r
a time?
IBM has been looking for an HLL for program products; REXX is that language.
On Wed, Jul 11, 2018 at 3:13 PM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Wed, 11 Jul 2018 14:59:15 -0400, Hobart Spitz wrote:
>
> >You're in TSO. Add
), or one record at a time?
IBM has been looking for an HLL for program products; REXX is that language.
On Wed, Jul 11, 2018 at 2:48 PM, John McKown
wrote:
> On Wed, Jul 11, 2018 at 1:38 PM Hobart Spitz wrote:
>
> > John; So the production schedules set policy in your shop. Do they
You're in TSO. Add this line, or equivalent, before the DELETE.
listd 'your.pds' mem
OREXXMan
JCL is the buggy whip of 21st century computing. Stabilize it.
Put Pipelines in the z/OS base. Would you rather process data one
character at a time (Unix/C style), or one record at a time?
IBM has be
(Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> ____
> From: IBM Mainframe Discussion List on behalf
> of Hobart Spitz
> Sent: Wednesday, July 11, 2018 1:30 PM
> To: IBM-MAIN@listserv.ua.edu
> Subject: Re: REXX as JCL replacement
>
> Skip;
>
> What y
hern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-543-6132 Office ⇐=== NEW
> robin...@sce.com
>
>
> -Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> B
Gil wrote:
>SORT is quasi-batch:
A REXX filter using ADDPIPE, or a "sipping" filter using CALLPIPE, can run
SORT(s) to completion completely independently of the main pipe, to name
just two possibilities. The terminology in the PIPElines documentation is
"delaying records". Most built-in filters
e idea of REXX as a JCL replacement. It can provide a lot better
> logic. I don't know that it will make many inroads due to lack of
> man-power, but it can be a method to the future.
>
> One of our staff looked seriously at JOL and rejected it.
>
> Tony Thigpen
>
> Hobart Spi
to change.
OREXXMan
JCL is the buggy whip of 21st century computing. Stabilize it.
Put Pipelines in the z/OS base. Would you rather process data one
character at a time (Unix/C style), or one record at a time?
IBM has been looking for an HLL for program products; REXX is that language.
On Mon,
The JOL effort is commendable, but replacing JCL is about much more than a
nicer syntax or easy movement between foreground and background.
At the risk of repetition, other reasons are (1) to eliminate the
separation between scripting code and application code and (2) to interface
with other softw
John wrote:
>it is not the default but is the only correct way to access a vsam file.
>disp=shr,dsn=.vsam (possible bufno,bufni,...etc)
Does any one know it that also applies to PDSEs? AFAIK, they are VSAM
datasets.
OREXXMan
JCL is the buggy whip of 21st century computing. Stabilize it.
Put
It beats the alternative. The more I proofread, the more improvements I
make and the longer my posts get. 8-D
OREXXMan
JCL is the buggy whip of 21st century computing. Stabilize it.
Put Pipelines in the z/OS base. Would you rather process data one
character at a time (Unix/C style), or one rec
It might be worth pointing out what might be a little known fact. Any
allocation, primary or secondary, can be done in up to 5 extents. That
means that, on a highly fragmented pack, SPACE=(CYL,(5,5)) might only get
16 cylinders (in 16 extents) before running out of extends. Fragmentation
at this
Steve, thanks for the kind words.
One afterthought that might improve the use of the TSO PROC, if one is so
inclined. Use // EXEC TSO,CMD=REXXTRY , Put REXXTRY into one of the
SYSEXEC/SYSPROC libraries, if it's not already there. It gives access to
most of REXX to the SYSTSPRT records. REXXT
cesses, must be SHaRed. What am I missing?
Thanks.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> ________
> From: IBM Mainframe Discussion List on behalf
> of Hobart Spitz
> Sent: Monday, July 9, 2018 8:46 AM
Ward wrote:
>What are the problems (perceived or real) that will be resolved by
replacing JCL with REXX?
I think that it's important to first understand the characteristics on
which many people base their thinking that JCL is good and may never go
away. The point is important, and the basis is a
How about something like:
*/* REXX */*
*...*
*"pipe (end ?) ? < file1.data | g: gather | join | pick 1.1500 /== 1501-*",*
* "| c: count lines | literal Mismatched record pairs: | cons",*
* "? < fileb.data | g:",*
* "? c: | var BadCount"*
*exit BadCount*
It works like this:
- < reads a fil
I think a more encompassing approach would be for JOL to be a function,
command or environment which could be invoked from REXX. That way, you
don't have to reinvent or do without all the things that REXX brings to the
table, both as a language and as something that interfaces with many parts
of z
This probably doesn't need to be said, but all(/most?) Access Method
Services (IDCAMS) commands are TSO commands.
Under TSO, it's enough to write:
...
call outtrap "CmdOut."
"listcat cluster"
call outtrap "off"
...
or
...
"pipe listcat | stem CmdOut."
...
In PIP
How about something like this?
Use REXX syntax and a JCL host command with JCL-like semantics:
/* REXX */
arg String /* From SUBMIT or start task command. */
"jcl job myjob: (acct),'john smith',class=t,msgclass=h,notify="userid()
"jcl exec pgm=myprog,parm="date("s")
"jcl sysprint: dd sysout=*"
)Why don't we just skip the JCL, and write our jobs in REXX? The two
Here, here!! Actually, there is one thing that is critical to retiring
JCL. It's a host command that allows a REXX program to list and wait for
all it's datasets and their enqueues to be available. This is not trivial,
so tha
I'm not sure which message(s) you are looking for, and I'm not familiar
with PIPElines in NetView.
That said, this should get you closer. In PIPElines environment with which
I am familiar, this would be my first recommendation:
"pipe (listerr) SAFE * | STEM MSG. | cons"
"... | cons" writes the
Mouse selection exists. Configure your mouse to send CUR SEL, which
emulates a light-pen press. The panel needs to make the field
light-pen/CUR SEL compatible.
We did this in the early 80s, writing an in-house emulator, before
emulators were available.
OREXXMan
JCL is the buggy whip of 21st cen
I'm *really* rusty, but would .AUTOSEL help? IIRC, it would give you
control back in additional situations.
Another thought:. It may help to check .RESP for a scroll key, save that
value, and set .RESP to ENTER .
Both are a bit cludgy, but something along those lines may help.
On Tue, 19 Jun 20
edu> wrote:
> On 2018-06-13, at 07:18:40, Hobart Spitz wrote:
>
> > Cross posted to CMSTSO Pipelines and IBM-MAIN
> >
> > Someone shared with me a performance comparison between Pipelines vs.
> > native *nix commands, both on OPENVM.
> >
> > Under the
Bruce;
I'm not sure whether you are asking for help, reporting a problem in a
sample, or offering a solution.
Since you haven't said which line failed, I'm just be guessing.
I think you need to quote StdErr. . That should allow you to turn NOVALUE
back on. I prefer to use it most of the time a
Cross posted to CMSTSO Pipelines and IBM-MAIN
Someone shared with me a performance comparison between Pipelines vs.
native *nix commands, both on OPENVM.
Under the OPENVM shell, this command ran 75 secs. with a 170M file in BFS:
$ time cat m170file.data | wc -b
This command, also under OPENVM
> Mainframe Systems Programmer – RavenTek Solution Partners
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Hobart Spitz
> Sent: Friday, May 11, 2018 9:57 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [
ammer – RavenTek Solution Partners
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Hobart Spitz
> Sent: Friday, May 11, 2018 9:48 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Re: [TSO-REXX] Sdsf rexx
>
> &
"pipe listpds" dsn "| stem members."
OREXXMan
JCL is the buggy whip of 21st century computing.
We want Pipelines in the z/OS base.
On Fri, May 11, 2018 at 9:00 AM, Carmen Vitullo wrote:
> outrap with LISTD works well
> soemthing like this works well
>
>
>
> X = Listdsi(DSN 'DIRECTORY NORECALL')
I think the real downside is cost of going to a new "platform", even tho
it's still within z/OS. That means training,
development/conversionj/implementation, testing, deployment, new operations
procedures and training, maintenance, etc.
Add in the general problem of rewriting any software in its
For those who may not be aware, SIGNAL is *not* a GOTO.
I counted 18 SIGNALs, and only 1 CALL. Many of the SIGNALs here seem to
have been better done with DO...END.
In the words of TRL, SIGNAL terminates "all active pending DO loops, DO
groups, IF constructs, SELECT construct, and INTERPRET inst
Somewhere, maybe in a different branch of this topic, there was a
discussion about the pros and cons of replacing Assembler with Java. I
apologize for posting here if it's the wrong place, but I can't seem to
find the original discussion, and I have a question that seems relevant and
important, IM
Jantje wrote:
>Commas at the beginning or at the end makes no difference... :
As far as the language syntax goes, this is a true statement. As far as
maintainability goes, that is another story. When I continue a statement,
I prefer to break between arguments, as there is typically less of lang
Pipe stepa ! stepb
(No pipe char on my phone)
On 4 Dec 2017 10:20 am, "Kirk Wolf" wrote:
> Right. Its often a good idea to set up alternate temp filesystems - either
> TFS or ZFS.
> The $TMPDIR environment variable can be set to point so that most commands
> will use this rather than /tmp.
> U
Sorry for the delay in responding.
I'm guessing that Sri is thinking of BatcfhPipes between two otherwise
independent batch JOBs. That is different animal entirely, even though
BatchPipes and BatchPipesWorks (Pipelines/Pipes) can work together.
As for Jesse's question about how to do restart, th
1 - 100 of 117 matches
Mail list logo
