XEDIT came with VM/SP Release 2, along with EXEC2. As with CLIST to REXX, EXEC 
2 was a major improvement but was missing some features of EXEC.


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

________________________________________
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Paul Gilmartin [0000000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Wednesday, December 22, 2021 2:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Top 8 Reasons for using Python instead of REXX for z/OS

On Wed, 22 Dec 2021 13:37:26 -0500, Phil Smith III wrote:
>
>>Can't you front-end that with a macro?
>
>Sure, I could, but FIND is a perfectly legitimate, related XEDIT command. So
>I don't want to replace it. An ISPF compatibility PROFILE XEDIT would do so,
>of course.
>
I did it.  It was a personal profile.

>    ... I've always assumed that PQUIT came along later in XEDIT
>development (before GA) and this was a compatibility compromise.
>
IIRC, circa VM/370 there was only QUIT.  No PQUIT; no QQUIT;
no aliases for them; no confirmation dialog.

>Ah.memories. In the early 80s, when dialup was the rule, I wrote SET VARCURL
>ON/OFF for XEDIT to do this. It wasn't that hard to make it behave. Some
>folks hated it, mind you, which is why it was a setting.
>
Sounds like what I did.  Again, a personal profile.  And i mapped my PF keypad 
to
a "⊥", matching my desktop keyboard.  I joked it was better than a password:
no one would *want* to use my logon.

"In the early 80s, when dialup was the rule, ..." we used the Simware emulator.
It went serial to the host where its server did the 3270 emulation.  A later
release did the emulation on the desktop and 3270 data streams to the host.
Performance got worse because of large blockmode transfers.  In the earlier
release, pressing ENTER completed the data transfer; in the later release,
pressing ENTER began the data transfer.  And they converted their code
from Pascal to Assembler and called it "portability".

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to