Re: Old Style Green Screen Subfile Templates on GitHub

Hello Sergio,

Am 27.08.2025 um 01:00 schrieb Sergio Luis Puentes-Valladares <spuentes@xxxxxxxxx>:

In the documentation, it is recommended to use the *READC instruction to read the changed subfile records*, this is not recommended because the READC instruction implicitly has an associated flag, that once read goes from 1 to 0, therefore the READC instruction can only be used once

I presume you're talking about "if it's already read, don't read again"? So far, I haven't found adverse effects from using READC, because the presentation of the SFL is consistent:

User types e. g. 2 into Opt of a bunch of records, and chooses to cancel the operation right in the middle. Upon pressing F12, the user is presented with an updated SFL where already handled records have a blank in their Opt fields.

So, if the user suddenly chooses to continue, he doesn't need to go through the whole selection from the beginning, but continue where he was.

This is intentional and consistent with the behavior of IBM provided SFL-with-detail applications, such as wrk(lin|ctl|dev)d.

It is recommended to use CYCLE using the DO...ENDDO instructions (DOU ENDDO), to correctly handle data control

What exactly do you mean?

I recommend defining in the SUBFILE record, (HIDDEN) fields and I/O fields for the data that will be verified for change, so if the (HIDDEN) field is different from the I/O field itself, it means that the data was changed

Well, that's a good idea! But becomes a chore to implement and handle with many fields.

:wq! PoC