ISPF Edit Highlighting
112 views
Skip to first unread message
lbd...@gmail.com
Aug 22, 2024, 1:34:02 PM8/22/24
to ISP...@listserv.nd.edu
I’ve a PDS with an LRECL of 4096 and Edit Highlighting does not work. Is there a LRECL limit beyond which the HILITE function in ISPF Edit will not work?
Lionel B. Dyck <>< 
Github: https://github.com/lbdyck
System Z Enthusiasts Discord: https://discord.gg/sze
“Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are.” - - - John Wooden
Frank Clarke
Aug 22, 2024, 1:45:24 PM8/22/24
to isp...@listserv.nd.edu, ispf-...@nd.edu
I would be surprised to find that anything longer than 255 even has rules for highlighting. Highlighting is for source data as opposed to data data.
--
You received this message because you are subscribed to the Google Groups "ISPF discussion list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ispf-l-list...@nd.edu.
To view this discussion on the web visit https://groups.google.com/a/nd.edu/d/msgid/ispf-l-list/008901daf4b9%24773637e0%2465a2a7a0%24%40gmail.com.
You received this message because you are subscribed to the Google Groups "ISPF discussion list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ispf-l-list...@nd.edu.
To view this discussion on the web visit https://groups.google.com/a/nd.edu/d/msgid/ispf-l-list/008901daf4b9%24773637e0%2465a2a7a0%24%40gmail.com.
lbd...@gmail.com
Aug 22, 2024, 1:52:52 PM8/22/24
to ispf-...@nd.edu
In this case it is source – specially HTML and the dataset has an LRECL of 4096 while the longest actually record in the PDS is 1356.
But you make a good point – 255 seems reasonable but thought I’d ask.
Lionel B. Dyck <>< 
Github: https://github.com/lbdyck
System Z Enthusiasts Discord: https://discord.gg/sze
“Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are.” - - - John Wooden
To view this discussion on the web visit https://groups.google.com/a/nd.edu/d/msgid/ispf-l-list/860657589.19748.1724348720836%40mail.yahoo.com.
Paul Gilmartin
Aug 22, 2024, 1:58:39 PM8/22/24
to ispf-...@nd.edu
On 8/22/24 11:45, 'Frank Clarke' via ISPF discussion list wrote:
> I would be surprised to find that anything longer than 255 even has rules for highlighting. Highlighting is for source data as opposed to data data.
> .
> I would be surprised to find that anything longer than 255 even has rules for highlighting. Highlighting is for source data as opposed to data data.
Is there a rule that source data lines can't be longer lines
can't be longer than 256?
Citation needed.
Some editors (alas, not ISPF) display long lines soft-wrapped
to screen width.
--
gil
Robert Prins
Aug 22, 2024, 2:10:28 PM8/22/24
to ispf-...@nd.edu
On Thu, 22 Aug 2024 at 17:52, <lbd...@gmail.com> wrote:
In this case it is source – specially HTML and the dataset has an LRECL of 4096 while the longest actually record in the PDS is 1356.
But you make a good point – 255 seems reasonable but thought I’d ask.
It might have been reasonable 10 years ago...
Anyway SuperC has a similar ridiculous limitation in that it doesn't support detection of moved lines for LRECL> 255
If you want to highlight this kind of data, you'd have to go for the Doeg Nadel HISDSF approach, and do it yourself by adding panel-REXX.
Robert
To view this discussion on the web visit https://groups.google.com/a/nd.edu/d/msgid/ispf-l-list/00e001daf4bc%2419abf620%244d03e260%24%40gmail.com.
Frank Clarke
Aug 22, 2024, 2:33:44 PM8/22/24
to ispf-...@nd.edu
I don't know that there's a "rule", but remember that [I]SPF originated in greenscreenland in the days of 72 bytes of code and 8 bytes of sequence number. CLIST was allowed to go to 255 (!) even though you had to scroll the screen right to get out that far.
--
You received this message because you are subscribed to the Google Groups "ISPF discussion list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ispf-l-list...@nd.edu.
To view this discussion on the web visit https://groups.google.com/a/nd.edu/d/msgid/ispf-l-list/51ae8017-3b68-450a-89e2-b59c042351ee%40AIM.com.
Rupert Reynolds
Aug 22, 2024, 2:36:17 PM8/22/24
to ispf-...@nd.edu
I accept every rule of thumb has its exceptions, but several well-respected developer conference talks point the finger at long lines of 200 or more and actively look for bad habits, such as homeopathic naming.
They don't usually have to look very hard.
Long source lines are at odds with the way human eyesight works. Code works best at abou 80 to 100 IMHO, and definitely not in Cinerama :-)
Roops
To view this discussion on the web visit https://groups.google.com/a/nd.edu/d/msgid/ispf-l-list/CAFazsTCQFMGL%3DaEc5F%3DP9HJKXSwDPRPzZKHRKiAXi6FSg%2BQdcg%40mail.gmail.com.
Paul Gilmartin
Aug 22, 2024, 3:48:35 PM8/22/24
to ispf-...@nd.edu
On 8/22/24 12:36, Rupert Reynolds wrote:
> I accept every rule of thumb has its exceptions, but several well-respected developer conference talks point the finger at long lines of 200 or more and actively look for bad habits, such as homeopathic naming.
> .
> I accept every rule of thumb has its exceptions, but several well-respected developer conference talks point the finger at long lines of 200 or more and actively look for bad habits, such as homeopathic naming.
"homeopathic"? Single-character symbols?
> They don't usually have to look very hard.
>
> Long source lines are at odds with the way human eyesight works. Code works best at abou 80 to 100 IMHO, and definitely not in Cinerama :-)
Regardless, it should afford the programmer the
courtesy of an explanation when it overrides
a setting, even as it does when it overridesthe
setting of CAPS.
Nowadays much "source code" is generated by computer
programs which don't care about line length.
And I've struggled to generate JCL with a program,
obeying it's mutually incompatible rules:
o Lines *mus*t be split immediately after column 71.
o Symbols *must*never* be split.
--
gil
Rupert Reynolds
Aug 22, 2024, 5:05:29 PM8/22/24
to ispf-...@nd.edu
"homeopathic naming" was described by Kevlin Henney, (from memory). He talked about having so much redundant text in names that the small bit that tells you what it is/does is hard to find, or even to the right of the edit window.
As for generating JCL, I remember sharing your pain from years ago. From memory, the only answer that made sense at the time (I couldn't use FTINCL--maybe no ISPF environment?) was to split at commas, which made for a lot of short lines :-)
Roops
--
Paul Gilmartin
Aug 22, 2024, 6:07:19 PM8/22/24
to ispf-...@nd.edu
On 8/22/24 15:05, Rupert Reynolds wrote:
> "homeopathic naming" was described by Kevlin Henney, (from memory). He talked about having so much redundant text in names that the small bit that tells you what it is/does is hard to find, or even to the right of the edit window.
> .
> "homeopathic naming" was described by Kevlin Henney, (from memory). He talked about having so much redundant text in names that the small bit that tells you what it is/does is hard to find, or even to the right of the edit window.
Which led me to:
<https://kevlinhenney.medium.com/exceptional-naming-6e3c8f5bffac>,
with an explanation of the etymology, and with no link:
<https://en.wikipedia.org/wiki/Hungarian_notation>
> As for generating JCL, I remember sharing your pain from years ago. From memory, the only answer that made sense at the time (I couldn't use FTINCL--maybe no ISPF environment?) was to split at commas, which made for a lot of short lines :-)
And doesn't help dealing with long strings. They could
relax the prohibition on splitting symbols but that
would surely break some existing art.
Thoughtless design. When symbols were innovated they
could have been handled better.
--
gil
robhb...@gmail.com
Aug 25, 2024, 3:41:31 PM8/25/24
to ispf-...@nd.edu
Yeah, I set my REXX PDSs at VB 1028 just in case, but I only rarely allow a line of code to go past the right edge of my screen; it isn’t hard to code continuation lines.