Or behind OS/VS1.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of 
Tony Thigpen [[email protected]]
Sent: Friday, February 28, 2020 5:51 PM
To: [email protected]
Subject: Re: VSE related questions - VSAMIO on VSE

There have been a lot of cases where z/OS was behind z/VSE.

First, a CA level backup/restore program for VSAM that was offered to
z/OS but they turned it down. Much faster than EXPORT/IMPORT and even
faster than CA-Faver. We have had it since the early 80's.

Second, we support FBA and SCSI disk.

Third, the JES2 support for virtual printers/punches is missing a lot of
things that POWER on VSE supports. This causes me a lot of work when I
do a z/VSE to z/OS conversion.

Historically, we have had NJE over TCP/IP for many years before it was
added to JES2.

We actually had TCP/IP available on VSE before there was any offering
for z/OS.

We have had real data-at-rest, field level, automated encryption since
2006. (This is actually one of my products.)

Yes, there is a lot of stuff z/OS has that VSE does not, but that does
not mean VSE does not have some stuff z/OS does not have.

BTW, it is my understanding that REXX/VSAMIO on VSE was written by
Boeblingen as a white-room project that did not use any of the Armonk
stuff. Boeblingen had a real sharp REXX developer back in 2001 (yes!
2001, 19 years ago). The z/VSE VSAMIO routine will even read/write CICS
files via cross-partition communications using CICS as a FOR/DOR. And,
it's all IBM code that could be ported to z/OS is the z/OS developers
would get off their high-horses and ask for the code.

Tony Thigpen

Farley, Peter x23353 wrote on 2/28/20 5:11 PM:
> Dang it, how is it that the fine VSE developers in Boeblingen can get 
> permission from Armonk to provide VSAMIO for REXX/VSE but users of z/OS REXX 
> have to install the open-source RXVSAM package to enable dealing directly 
> with VSAM files from REXX programs?
>
> <*Grumble*>
>
> Peter
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
> Bernd Oppolzer
> Sent: Friday, February 28, 2020 4:50 PM
> To: [email protected]
> Subject: Re: VSE related questions
>
> Thank you all for your valuable advice.
>
> I already found many of the answers to my questions, and some books:
>
> REXX for VSE:
> https://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC33-6642-09
> User's Guide for Barnard FTP:
> ftp://public.dhe.ibm.com/s390/zos/vse/pdf3/ipv6vse/iesipu41.pdf
>
> REXX VSAMIO and some examples in the FTP user's guide answered all my 
> questions a) to d) I will try all this next week at my customer's site.
>
> (both REXX EXECIO and FTP can work with VSE libraries directly, which is 
> still more interesting for my use case)
>
> Thank you again,
> kind regards
>
> Bernd
> <Snipped>
> --
>
>
> This message and any attachments are intended only for the use of the 
> addressee and may contain information that is privileged and confidential. If 
> the reader of the message is not the intended recipient or an authorized 
> representative of the intended recipient, you are hereby notified that any 
> dissemination of this communication is strictly prohibited. If you have 
> received this communication in error, please notify us immediately by e-mail 
> and delete the message and any attachments from your system.
>
>
> ----------------------------------------------------------------------
> 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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to