Shmuel wrote:
>Your guess is worth what I paid for it. I started on the 3277 back when the
competition was the 2260 and am at home with 3270 data streams.
>What you wrote was "this will mean a new application *cannot* use existing
hardware,", which isn't even close to saying that you need
ubject: Re: AUXLIST (was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
Shmuel wrote:
>It's in reference to the fact that after I repeatedly asked why you
believed that it would cause problems for existing displays, and after it
explained that it wouldn't, you simply repeated the same b
Shmuel wrote:
>It's in reference to the fact that after I repeatedly asked why you
believed that it would cause problems for existing displays, and after it
explained that it wouldn't, you simply repeated the same baseless claim.
That's very different from not liking dual paths, which you never
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Sunday, February 27, 2022 11:29 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AUXLIST (was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
Shmuel wrote:
>Who
Shmuel wrote:
>Whoosh!
I'm going to assume that's in reference to your sending a blank reply rather
than an appalling lack of comity.
>The whole point of Read Partition Query is so that software can detect what
features are supported. Had IBM implemented a Start Fiewld Contifuous buffer
Smith III [li...@akphs.com]
Sent: Friday, February 25, 2022 6:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AUXLIST (was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
Shmuel wrote:
>Huh? Where does "the image won't fit on a 24x80 screen" come from?
>Supporting new dev
(was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
Shmuel wrote:
>Huh? Where does "the image won't fit on a 24x80 screen" come from?
>Supporting new device capabilities does not mean that old devices are
unsupported. ISPF supports, e.g., colors, but it works on a 3277 as
The attribute byte does not really take up a space on the screen. Within
the datasteam, you can put stuff on the screen 'out of order' and thus
put something else on the screen that overwrites the spot you thought
you put the attribute byte into. So, if build the datasteam from end to
start,
Shmuel wrote:
>Huh? Where does "the image won't fit on a 24x80 screen" come from?
>Supporting new device capabilities does not mean that old devices are
unsupported. ISPF supports, e.g., colors, but it works on a 3277 as well as
it ever did. Had IBM done as I suggest, there would not have
, February 24, 2022 4:54 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AUXLIST (was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
Shmuel wrote:
>Memory was less expensive when the 3278 and 3279 came out, and optionally
inserting character attributes would not have been a major redesign.
Shmuel wrote:
>Memory was less expensive when the 3278 and 3279 came out, and optionally
inserting character attributes would not have been a major redesign.
The addition of extended attributes (SA orders) would have been the
plausible time. In fact, those are so close to this that it MUST
@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Thursday, February 24, 2022 2:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AUXLIST (was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
On Thu, 24 Feb 2022 18:47:14 +, Seymour J Metz wrote
I think we would all agree that the defaults for XEDIT are "not the way
I would have done it." But, we should also agree that changing just
about anything with XEDIT is possible, and in most cases easy using the
tools provided with XEDIT.
So, let's not hang our thoughts about XEDIT based on
Paul Gilmartin wrote:
>But it's overdue for the ISPF and XEDIT designers to do what ISPF promised
>never to do: introduce support for curses/terminfo-based terminals. Most
>desktops have those nowadays.
Not sure how that would work, since it's a 3270 data stream. Would mean a
HUGE rewrite,
On Thu, 24 Feb 2022 18:47:14 +, Seymour J Metz wrote:
>It was a fundamental design flaw on the 3277; IBM could have easilly fixed it
>with the introduction of EDS. Why isn't there a protected character attribute?
>
Storage was expensive. The designers budgeted for 1920 bytes.
[IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Thursday, February 24, 2022 1:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AUXLIST (was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
Paul Gilmartin wrote:
>Bad definition. XEDIT shouldn't entice users to en
Paul Gilmartin wrote:
>Bad definition. XEDIT shouldn't entice users to enter data that
>t won't "take". The field should have the read-only attribute.
>Is there any rationale for making it writable?
Well, it's not a separate field: this is 3270, so there would be an
attribute byte on the
Shmuel wrote:
>I would argue that multiple edits that are part of a single enhancement
belong in a single checkin. For context, this is based on using a home grown
IDE that timestamped changed lines, solicited and formatted change
descriptions, and generally did the grunt work to have a good
On Wed, 23 Feb 2022 10:16:18 -0500, Phil Smith III wrote:
>
>>I resorted to using basic XEDIT and generating my updates
>
>>with SuperC UPDCMS8.
>
(Why is quoted material appearing double-spaced? Is this a perversion
of a markdown filter?)
>As others have pointed out, this is easily remedied by
: Re: AUXLIST (was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
Paul Gilmartin wrote:
>I had a disappointment with XEDIT Update mode: If I touch
>a line; have second thoughts and restore it, even by an
>immediate ERASE EOF, it puts the line needlessly in the
>Update fi
Paul Gilmartin wrote:
>I had a disappointment with XEDIT Update mode: If I touch
>a line; have second thoughts and restore it, even by an
>immediate ERASE EOF, it puts the line needlessly in the
>Update file. Working in a cooperative development project,
>I resorted to using basic XEDIT and
On Wed, 23 Feb 2022 09:32:57 -0500, Tony Thigpen wrote:
>If it's a single line change, I just edit the resulting ptf member and
>remove the extra modification. If it's in a group of lines being
>changed, it's most likely going to be in the ptf anyway.
>
SuperC is less error-prone than I am.
And
[000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Wednesday, February 23, 2022 9:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AUXLIST (was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
On Wed, 23 Feb 2022 07:11:20 -0500 Tony Thigpen wrote:
:>I use a system that generates the AUX files dynamica
On Wed, 23 Feb 2022 14:21:05 +, Seymour J Metz wrote:
>> diff/patch is more flexible; no 73-80 dependency.
>
>In simple cases I can see that, but what happens when blocks of code repeat?
>Sometimes you need both a screwdriver and a hammer.
>
Or when a sizeable block of code is moved. I know
If it's a single line change, I just edit the resulting ptf member and
remove the extra modification. If it's in a group of lines being
changed, it's most likely going to be in the ptf anyway.
Tony Thigpen
Paul Gilmartin wrote on 2/23/22 09:01:
On Wed, 23 Feb 2022 07:11:20 -0500 Tony Thigpen
IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Wednesday, February 23, 2022 9:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AUXLIST (was XEDIT equivalent to ISPF C - OO/OO (copy overlay))
On Wed, 23 Feb 2022
On Wed, 23 Feb 2022 07:11:20 -0500 Tony Thigpen wrote:
>>
>> :>I use a system that generates the AUX files dynamically for each "xedit
>> :>with update function". There is only one CTRL file, ...
>> :>
I had a disappointment with XEDIT Update mode: If I touch
a line; have second thoughts and
All that is in my AUXLIST is:
ASS1
ASS2
This for an assembler program with 2 updates.
Tony Thigpen
Binyamin Dissen wrote on 2/23/22 07:52:
On Wed, 23 Feb 2022 07:11:20 -0500 Tony Thigpen wrote:
:>You should continue the conversation over on the VM list.
:>I use a system that
On Wed, 23 Feb 2022 07:11:20 -0500 Tony Thigpen wrote:
:>You should continue the conversation over on the VM list.
:>I use a system that generates the AUX files dynamically for each "xedit
:>with update function". There is only one CTRL file, which has:
:>TEXT MACS
:>FIXES AUXLIST
:>My
29 matches
Mail list logo
