Post by George on Jun 9, 2020 13:39:31 GMT -5
Robert: I see a problem similar to what the XFORM sample XHEX macro faces.
File-Aid had the advantage of using ISPFs Dialog Manager. It could display each 'field' as a unique 3270 Field, and easily identify and associate the incoming changed data to the Format field.
With SPFLite, no such 'fielding' exists, just text lines. I would fear that users could so easily, with INSERT mode on, muck up the screen layout to the point that Format could no longer figure out how to re-build the actual record.
It's interesting, but mainframe FILE-Aid mainly dealt with nice fixed layout record definitions, as that was the mainframe 'way' of organizing data. PC stuff has gone mostly the other way, with free-form text strings, XML style definitions etc. I'm not sure how relevant this support would be to most users.
George
File-Aid had the advantage of using ISPFs Dialog Manager. It could display each 'field' as a unique 3270 Field, and easily identify and associate the incoming changed data to the Format field.
With SPFLite, no such 'fielding' exists, just text lines. I would fear that users could so easily, with INSERT mode on, muck up the screen layout to the point that Format could no longer figure out how to re-build the actual record.
It's interesting, but mainframe FILE-Aid mainly dealt with nice fixed layout record definitions, as that was the mainframe 'way' of organizing data. PC stuff has gone mostly the other way, with free-form text strings, XML style definitions etc. I'm not sure how relevant this support would be to most users.
George