Re: Some questions on SYSCALL

On Wed, 29 Jun 2022 20:22:10 -0700, Charles Mills wrote: >... >"99 Bottles of Beer" is more concise in C++ than in Python, and MUCH more >concise in BASIC. Does that make BASIC a better language? >https://en.wikipedia.org/wiki/99_Bottles_of_Beer > The BASIC is 219 characters. I converted

Re: Some questions on SYSCALL

If succinctness is the criterion, shouldn't everyone be using APL instead of COBOL? Python is not as succinct as it might be. My understanding is that Python uses AND and OR rather than the more common & and | or && and ||. Up to two more keystrokes each! Is that a bad thing? For any language

Re: Some questions on SYSCALL

> Charles knows C++ so I don't understand why he would pick REXX One factor is that my deployment machine does not have a C++ compiler and does not share DASD with my development machine. So for C++ the cycle is - Edit in IDE on Windows - Build in IDE on Windows; get to clean compile - Upload

Re: REXX outside TSO

On Wed, 29 Jun 2022 19:44:15 -0400, Bob Bridges wrote: >I've heard the word "awk", but never been exposed to it. I had the >impression, though, that I've heard of it in the context of Unix; am I >mistaken? > UNIX, yes. Which means it's readily available on z/OS, Mac OS, and Linux. Similar to

Re: Some questions on SYSCALL

I approve of civil discourse, and I'd hate to discourage anyone from asking civilly for it. But I've been enjoying this one; yes, a few of the participants have waxed quarrelsome, but only a little, and briefly. And as Messrs Farley and Smith agree, this has been informative too. (I also

Re: REXX outside TSO

On 30/06/2022 7:44 am, Bob Bridges wrote: I've heard the word "awk", but never been exposed to it. I had the impression, though, that I've heard of it in the context of Unix; am I mistaken? Remember, the topic of the moment was whether there's any use for REXX ~outside~ TSO. This was on a

Re: REXX outside TSO

Not intending to continue this thread, but awk is a favorite tool of mine. You certainly can run z/OS awk in a fairly simple batch JCL, though I have not tried it under TSO or batch TSO. I far prefer the GNU awk (gawk) on my personal machines (Win10 64-bit), but z/OS awk is (mostly) POSIX

Re: REXX outside TSO

I've heard the word "awk", but never been exposed to it. I had the impression, though, that I've heard of it in the context of Unix; am I mistaken? Remember, the topic of the moment was whether there's any use for REXX ~outside~ TSO. This was on a Windows system; I'm guessing awk wouldn't be

Re: Some questions on SYSCALL

On 30/06/2022 5:33 am, Paul Gilmartin wrote: On Wed, 29 Jun 2022 22:22:39 +0200, Bernd Oppolzer wrote: This is an old OS/2 REXX program (from the 1990s, IIRC), used to traverse a directory tree recursively and issue a command in every subdirectory found: ... with local variables protected by

Re: Some questions on SYSCALL

I feel compelled to object. This argument has been perfectly civil, is completely pertinent, and surely has value in opening up some eyes about options for getting things done the "best" way. Yeah, the "best" is subjective, but sometimes a bit of argument will lead to some enlightenment... if

Re: Some questions on SYSCALL

On 30/06/2022 6:37 am, Farley, Peter x23353 wrote: Gentle listers, Can we all agree to let this discussion be resolved by agreeing to the Perl mongers motto, TMTOWTD TWTOWTD? Or maybe not. Show me how to create a secure socket in REXX without using PAGENT. I think the discussion you have

Re: Some questions on SYSCALL

Gentle listers, Can we all agree to let this discussion be resolved by agreeing to the Perl mongers motto, TMTOWTDI? I think the discussion you have had so far is more than sufficient. I would also suggest that you take it offline if you would prefer to continue along these lines. I will

Re: Some questions on SYSCALL

On 30/06/2022 5:52 am, Bernd Oppolzer wrote: The only reason why your Python code is shorter is because you use the builtin os.walk method to walk through the directory recursively. Isn't that the point? Python has an enormous standard library to do useful things. Also note the use of

Re: Some questions on SYSCALL

The only reason why your Python code is shorter is because you use the builtin os.walk method to walk through the directory recursively. A similar method could have been used in my REXX example, too, but I wanted a command to be issued in every subdirectory when walking through the tree, so I had

Re: Some questions on SYSCALL

On Wed, 29 Jun 2022 22:22:39 +0200, Bernd Oppolzer wrote: >> >This is an old OS/2 REXX program (from the 1990s, IIRC), >used to traverse a directory tree recursively and issue a command in >every subdirectory found: > > z/OS Rexx ought to be able to do likewise with SYSCALL readdir:

Re: Some questions on SYSCALL

On 30/06/2022 4:22 am, Bernd Oppolzer wrote: This is an old OS/2 REXX program (from the 1990s, IIRC), used to traverse a directory tree recursively and issue a command in every subdirectory found: /* rexx */ arg command call RxFuncAdd "SysLoadFuncs", "REXXUTIL", "SysLoadFuncs" call

Re: Some questions on SYSCALL

Am 29.06.2022 um 14:06 schrieb David Crayford: On 29/06/2022 6:37 pm, Seymour J Metz wrote: Sme, but manageable. The article Safe REXX at and has some tips on avoiding REXX pitfalls. What's

Re: Allocating PC numbers

Perhaps have a global name token - so applications can find it Colin On Wed, 29 Jun 2022 at 20:22, Ngan, Robert (DXC Luxoft) wrote: > Use the LXRES service. > Then all you need to do is figure out how you want to "publish" your PC > number to its potential users. > > Robert Ngan > DXC Luxoft >

Re: Allocating PC numbers

Use the LXRES service. Then all you need to do is figure out how you want to "publish" your PC number to its potential users. Robert Ngan DXC Luxoft -Original Message- Date:Tue, 28 Jun 2022 16:11:37 -0400 From:Tony Thigpen Subject: Allocating PC numbers When on z/OS and you

Re: Some questions on SYSCALL

Bill, Your input and advice and "tools and toys" for z/OS have been most helpful to so many of us over all these years. Thank you for everything you have done for us. May you enjoy good health and a relaxed retirement. All the best. Peter -Original Message- From: IBM Mainframe

Re: AF/OPER replacement with BMC Mainview AutoOperator

Hi, I worked for a few years with Mainview AutoOperator, before we were forced to change to IBM's TSA. It was a great product, very easy to use. I suppose that it can only have improved. Given the chance I would go back to it. Jack On Wed, Jun 29, 2022, 16:28 IBM user wrote: > Has anyone

Re: Some questions on SYSCALL

On 2022-06-29 08:48 AM, Bill Schoen wrote: Probably my last post before retirement tomorrow. Enjoy your retirement, Bill! -- Regards, Gord Tomlin Action Software International (a division of Mazda Computer Corporation) Tel: (905) 470-7113, Fax: (905) 470-6507 Support:

Re: REXX outside TSO

On Wed, 29 Jun 2022 12:00:12 -0400, Bob Bridges wrote: > >... writing a REXX that read the raw firewall extract and created a CSV in > about 20 seconds. REXX makes ~very~ short work of parsing. At the time I > don’t think I knew VBScript, but it surely would have been harder. > For that

Re: How to identify holddata date

Thanks Kurt. At least I know that holddata is current. Some more questions about PUTs & RSUs. - When exactly IBM releases the monthly RSU? beginning of next month? - I noticed that some PTFs such as security related have NVD like severity (Bx.y) What is A in Symptoms? - IBM plans to

REXX outside TSO

For what it's worth, I've had that need. Only twice, I admit: 1) At one employer I overheard my boss talking on the phone; apparently they'd been tracking viri by looking at firewall logs and analyzing connections that had been refused. (A machine that sends 10 000 packets to one IP address

Re: Some questions on SYSCALL

Hi Bob, "... Or are you thinking that you can make sure there's an END for each one? ..." Yes ... Here is an example: X ALL; F ALL Do 10;F All END 10 Regards, David On 2022-06-29 11:39, Bob Bridges wrote: My first language was a subset of PL/1, and I still think it's a great language, but

Re: Some questions on SYSCALL

My first language was a subset of PL/1, and I still think it's a great language, but there doesn't seem to be much call for it at the clients I serve. I didn't know PL/1 programmers indent the END with the paragraph; I thought it was just my preference, but maybe I learned it earlier than I

AF/OPER replacement with BMC Mainview AutoOperator

Has anyone replaced IBM AF/OPERator with BMC Mainview AutoOperator? The announcement letter states that IBM‘s product will be discontinued from service in April 2024. -- For IBM-MAIN subscribe / signoff / archive access

Re: Some questions on SYSCALL

On 29/06/2022 11:07 pm, Rony G. Flatscher wrote: Hi David, On 29.06.2022 15:54, David Crayford wrote: I know ooRexx. I ported it to z/OS 10 years ago but it was buggy and slow. Hmm, ten years ago? Over time there has been so much improvements in these and other areas including a testing

Re: Some questions on SYSCALL

On 29/06/2022 10:48 pm, Seymour J Metz wrote: Have you stopped beating your wife? There is no agreement of what is a better language, much less a description of the context in which to evaluate "better". You really are a huge twat. Why don't you just bugger off. You won't be missed.

Re: Some questions on SYSCALL

Hi David, On 29.06.2022 15:54, David Crayford wrote: I know ooRexx. I ported it to z/OS 10 years ago but it was buggy and slow. Hmm, ten years ago? Over time there has been so much improvements in these and other areas including a testing framework with quite a comprehensive coverage of the

Re: Some questions on SYSCALL

Have you stopped beating your wife? There is no agreement of what is a better language, much less a description of the context in which to evaluate "better". From: IBM Mainframe Discussion List on behalf of David Crayford Sent: Wednesday, June 29, 2022

Re: Some questions on SYSCALL

Hi Bob, When I programmed PL/I 40+ year ago, lining up the END; with the body was de rigeur. Initially, of course, that was using cards. When ISPF (or XEDIT) came along, lining up the END: with DO/SELECT etc. made a lot more sense since excluded lines could be shown by column number containing

Re: Some questions on SYSCALL

Eternal theological debates: What is the best editor? What is the best programming language? What is the best scripting language? What is the best naming convention? What is the best indentation structure? What is the best markup language? I don't expect to ever see

Retire, sure, but not leave!

Wait a minute, are you saying you won't be here any more? Why, for heaven's sake? By all means retire, but... --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* It's better to be on the ground wishing you were in the air, than in the air wishing you were on the ground. -Lesson

Re: Some questions on SYSCALL

Some years ago I accidentally left a book at church. I was pretty sure I knew where it was, so I figured I'd just pick it up the next time I was in that part of the building. But a friend returned it to me before I got around to it. I usually put my name in my books, but I hadn't in this one

Re: Some questions on SYSCALL

You're kidding, right? That convention isn't imposed by REXX, and as far as I've observed Lionel and I are two of only three people in the universe who prefer it. (And don't you be knocking our convention. Aligning the END with the rest of the paragraph is much more sensible than sticking it

Re: How to identify holddata date

> My idea was to produce a report sourceid on the global target zones (since > acept will remove the PTFs related to this sourceid) and get the last PUT > listed. This one will work even if I am running on a lower level system. > correct? REPORT SOURCEID will show you all of the sourceids

Re: [EXTERNAL] Java?

Bob, No, we run a small amount of java as straight batch. One example is the IBM SCRT monthly processing. Straight batch job: //JAVAJVM EXEC PGM=JVMLDM86,REGION=0M,PARM='/ com.ibm.scrt.SCRTe ' Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Bob Bridges

Re: Some questions on SYSCALL

Hi Rony, I know ooRexx. I ported it to z/OS 10 years ago but it was buggy and slow. There is zero chance of IBM or a vendor wasting resources on REXX today as there is no market for it. Now we have Python on z/OS REXX is very much a legacy language. That's even more pertinent with the shift

Java?

I really gotta learn Java. If five belts around my waist are good, six would be even better. But mostly I stick to languages that my clients already have, and even better if possible, know how to maintain. Where is Java usable? On the mainframe, only Unix, right? --- Bob Bridges,

Re: Some questions on SYSCALL

I'm not Dale, but actually I do. I use it because sometimes it's necessary to help me set a variable whose name is itself variable, and it's wonderful then. But otherwise I don't have much use for it, for exactly that reason. --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* How

Re: ... SYSCALL ... And Thanks!

Yes, the parameter limit is for call and function invocation. A command can only have parameter. From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> Sent: Wednesday, June 29, 2022 9:09 AM To:

Re: Some questions on SYSCALL

Happy retirement Bill! Lennie -Original Message- From: IBM Mainframe Discussion List On Behalf Of Bill Schoen Sent: 29 June 2022 13:48 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Some questions on SYSCALL There are quite a few topics in this thread, some well addressed, some maybe not,

Re: Some questions on SYSCALL

Hi David, On 29.06.2022 14:06, David Crayford wrote: On 29/06/2022 6:37 pm, Seymour J Metz wrote: Sme, but manageable. The article Safe REXX at and has some tips on avoiding REXX pitfalls.

Re: Some questions on SYSCALL

Why don't you speak for yourself? When I saw a van with the license number PEDANT, I was jealous. From: IBM Mainframe Discussion List on behalf of David Crayford Sent: Wednesday, June 29, 2022 9:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Some

Re: ... SYSCALL ... And Thanks!

On 29/06/2022 9:09 pm, Paul Gilmartin wrote: On Jun 29, 2022, at 06:48:14, Bill Schoen wrote ... re: write buffer is a variable name This was done for a variety of reasons, but primarily, rexx has a limit to number of parameters that can be passed to an address environment. I think TSO

Re: Some questions on SYSCALL

On 29/06/2022 9:20 pm, Paul Gilmartin wrote: On Jun 29, 2022, at 07:02:39, David Crayford wrote: ... That doesn't eliminate confusion at all. If you have a large loop and you don't understand your code then your code is crap. Any decent code editor will match blocks on key-press. ISPF

The fog clears, a little bit

Dale, I never got it quite clear in my head until just now. I'm comfortable when I have to examine RC to see how a routine worked, but I knew that RESULT also did something, sometimes, and I was never sure exactly what. Many times in past programs I had to test my program looking at RC and at

Re: Some questions on SYSCALL

On Jun 29, 2022, at 07:02:39, David Crayford wrote: > ... > That doesn't eliminate confusion at all. If you have a large loop and you > don't understand your code then your code is crap. Any decent code editor > will match blocks on key-press. ISPF doesn't meet that criteria! > The

Re: ... SYSCALL ... And Thanks!

On Jun 29, 2022, at 06:48:14, Bill Schoen wrote > ... > re: write buffer is a variable name > This was done for a variety of reasons, but primarily, rexx has a limit to > number of parameters that can be passed to an address environment. > I think TSO rexx limits it to 20. If it took a

Re: Some questions on SYSCALL

On 29/06/2022 8:48 pm, Paul Gilmartin wrote: On Jun 29, 2022, at 06:37:39, Lionel B. Dyck wrote: Some align the end with the do, others align the end with the code in the do structure. The key is a consistent style for readability. The REXXFORM results of my example are: /* rexx */ x =

Re: Some questions on SYSCALL

Thanks David, I learned something there that I didn't know. Cheers On 29/06/2022 8:50 pm, David Spiegel wrote: Hi David, The paragraphing style was used historically by PL/I. Rexx syntactically is a PL/I derivative, Regards, David On 2022-06-29 08:32, David Crayford wrote: On 29/06/2022

Re: Some questions on SYSCALL

On Jun 29, 2022, at 05:56:50, Seymour J Metz wrote: > > Passing the buffer by value would cause the parameters of write to be > inconsistent with the parameters of read. IMHO, making them consistent is > intuitive. > Both are by name. I was incorrect earlier.

Re: Some questions on SYSCALL

Hi David, The paragraphing style was used historically by PL/I. Rexx syntactically is a PL/I derivative, Regards, David On 2022-06-29 08:32, David Crayford wrote: On 29/06/2022 8:27 pm, Lionel B. Dyck wrote: The formatting was a quick and dirty - I typically use the REXXFORM edit macro to

Re: Some questions on SYSCALL

There are quite a few topics in this thread, some well addressed, some maybe not, but I'll pitch in... re: syscalls environment should be integrated into rexx this is included in the default environments for rexx running in mvs (irxjcl), tso, and ispf calling syscalls('ON') is not required to

Re: Some questions on SYSCALL

On Jun 29, 2022, at 06:37:39, Lionel B. Dyck wrote: > > Some align the end with the do, others align the end with the code in the do > structure. The key is a consistent style for readability. > > The REXXFORM results of my example are: > > /* rexx */ >

Re: Some questions on SYSCALL

On 29/06/2022 8:37 pm, Lionel B. Dyck wrote: Some align the end with the do, others align the end with the code in the do structure. The key is a consistent style for readability. The REXXFORM results of my example are: /* rexx */ x = bpxwunix('find /u/user/work/',,out.,err.) do I = 1 to

Re: Some questions on SYSCALL

Some align the end with the do, others align the end with the code in the do structure. The key is a consistent style for readability. The REXXFORM results of my example are: /* rexx */ x = bpxwunix('find /u/user/work/',,out.,err.) do I = 1 to out.0

Re: Some questions on SYSCALL

On 29/06/2022 8:27 pm, Lionel B. Dyck wrote: The formatting was a quick and dirty - I typically use the REXXFORM edit macro to clean up alignments and keep things neat. I'm not knocking your code Lionel. It's more the case that I don't like what has become common formatting of REXX code

Re: CSSMTP

Looking at the CSSMTP documentation it seems to imply that if you have NODENAME=REQUIRED that you need to have DEST and DESTID the same as what you have coded for ExtWrtName" They give the examples of: $ADD DESTID(),DEST= To dynamically adding it and coding the following

Re: Some questions on SYSCALL

The formatting was a quick and dirty - I typically use the REXXFORM edit macro to clean up alignments and keep things neat. You can find it at https://github.com/lbdyck/rexxform - I ported it from z/VM to work as an edit macro. Yes - you could use SYSCALLS and get the same info but this was a

Re: Some questions on SYSCALL

Thanks Lionel. If I want to get the directory entry I suppose I have to also execute bpxwunix("ls ") or use SYSCALLS? BTW, I really wish the "end" scope terminater would match the "do" column alignment. It's just another reason for me to hate on REXX when it's become common practice to uses

Re: Some questions on SYSCALL

Perhaps something like this will give you what you want to recursively traverse a directory: x = bpxwunix('find /u/user/work/',,out.,err.) do I = 1 to out.0 say out.i end Lionel B. Dyck <>< Website: https://www.lbdsoftware.com Github: https://github.com/lbdyck “Worry more about your

Re: Some questions on SYSCALL

On 29/06/2022 6:37 pm, Seymour J Metz wrote: Sme, but manageable. The article Safe REXX at and has some tips on avoiding REXX pitfalls. What's the point in managing something when you can just

Re: Allocating PC numbers

Thanks Peter. I have been running my test program (that I got from somewhere) and realized that I was off-base with my understanding. I am also coming to understand that some of the stuff done by the program was not needed or incorrect, but still worked. For instance, it does an AXRES,

Re: Some questions on SYSCALL

Passing the buffer by value would cause the parameters of write to be inconsistent with the parameters of read. IMHO, making them consistent is intuitive. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List

Re: Some questions on SYSCALL

I don't have a problem with checking return codes, but IMHO the SIGNAL statement is badly broken and the handling of exceptions is much better in, e.g., Ada, Java, PL/I. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe

Re: Some questions on SYSCALL

You can invoke a command either with an explicit environment or with an explicit environment. An address statement with only one operand changes the current (implicit) environment, but it does cause any environment to go away. There is no PEN environment; you need address SYSCALL "open"

Re: zVM v7.1 : Populating VMSYS: Root BFS

Hi, I just picked up zVM support after skipping for many years and experiencing an odd BFS issue. - We need to populate VMSYS root and it seems that loadbfs does not perform it anymore. - I tried from starting with scratch SFS system:  - Then using bfsroot - loadbfs bfs loadbfs and

Re: Some questions on SYSCALL

See z/OS 2.5 TSO/E REXX Reference, SA32-0972-50. There are three ways to write an assembler routine. The first two are almost identical and have access to services documented in Chapter 12. TSO/E REXX programming services at

Re: Allocating PC numbers

how do you determine what PC number the new routine is going to use? Is there a list of 'used' ones somewhere? Are, do you do some sort of loop checking to see what is free? I'd answer "no, not at all like that". You (the PC-owner-to-be) have to have reserved a linkage index (LX, via LXRES).

Re: Some questions on SYSCALL

Not quite; SYSCALL is no longer the current (i.e., implicit) environment but it is still available as an explicit environment: address TSO address SYSCALL foo /* TSO is still the current envirenment */ -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3

is there any documentation on using the new 64 bit instructions?

Thanks for all of the comments. I had some offline as well as online. I found John R. Ehrman's book very interesting, a bit of bedtime reading. I called my code using #PRAGMA LINKAGE(xxx,OS), and did not need to worry about XPLINK. Because the z/OS routines I was using are 31 bit, I needed to

Re: Some questions on SYSCALL

Sme, but manageable. The article Safe REXX at and has some tips on avoiding REXX pitfalls. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3