VSAM IO for VSE/REXX is an IBM item.
VSE REXX has a few things that z/OS does not. It's come up in the past,
I just can't remember the details.
VSE also had NJE over IP a long time before z/OS.
VSAM shareoption-4 really works correctly in VSE but was never fully
implemented in z/OS. (I long time ago, I talked to an ex-IBM person that
was on the OS/390(?) VSAM team. They ran out of time so they documented
a work-around. When it was time to finish the project, someone decided
that "it was good enough" and no more time would be spent on making it
work.)
As someone who has converted sites from VSE to z/OS, VSE/Power supports
"channel-12" on all devices, even spooled devices, but JES2 only
supports "channel-12" on real devices, not spooled devices. This caused
a lot of problems at one shop I converted.
VSE has had JCL "GOTO" since "whenever", but JES2 did not have it for a
long time. (And don't get me started on z/OS JCL's 'backward' condition
code processing.)
Just like many big brothers think of their little brother is a 'turd',
most z/OS sysprogs are blind to what z/VSE can really do.
Tony Thigpen
Dave Clark wrote on 2/1/22 15:50:
"IBM Mainframe Assembler List" <[email protected]> wrote on
02/01/2022 03:42:51 PM:
The external assembler REXX function I am working on is so that I
don't have to depend upon the built-in REXX VSAMIO function.
Why does VSE get VSAMIO but MVS doesn't?
I could understand if REXX in VM was more advanced, but VSE??
Sorry. ;-) I thought you guys would already have something like
REXX VSAMIO. It is an add-on provided by the IBM VSE group. They have
provided many add-ons for various things in the VSE environment.
But you guys have something that you can use with the ADDRESS
command to access DFSMS AMS data, yes?
Sincerely,
Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************
