BPXWDYN is a Unix Service as far as I am concerned as it's part of z/OS Unix System Services. Check out which manual it's documented in. I suspect it's under the Unix FMID as well but I haven't checked that part.
I consider anything that begins BPX to be z/OS Unix System Services but I'm willing to be corrected on that one. I certainly haven't used them all. -----Original Message----- From: Paul Gilmartin <[email protected]> Sent: 14 April 2020 5:16 pm Subject: Re: Any shop use UNIX in a production job? On Tue, 14 Apr 2020 12:59:54 +0300, Alan(GMAIL)Watthey wrote: >John, > >You make it sound like Rexx and Unix are mutually exclusive. I have a Unix >job that runs in production. Well, it depends on your definition of >production of course. It actually runs on every system we have. > >It's started each midnight by CROND so definitely only has access to Unix >services and it is all written in Rexx. > What do you mean to restrict by "only has access to Unix services"? That Rexx can perform allocations with BPXWDYN. It can invoke load modules with ADDRESS LINKMVS. It can use ADDRESS TSO (surrogate) and thereby ISPF services. Is there anything it could have done under IRXJCL, but not under UNIX? (Or are you just asserting the not "mutually exclusive"?) The exception I see is initiator ENQ serialization and deadlock prevention. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
