Probably the most important step to modernization.
Externalize your data definitions and you can add on to your S/36 apps using any language you want to use.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------
message: 2
date: Tue, 13 May 2025 17:16:21 +0200
from: Daniel Gross <daniel@xxxxxxxx>
subject: Re: SQL join, limit to one row per employee
Yeah - it looks like S/36.
But along time ago in a galaxy far far away, I also had "externally described" /36 files - you simply drop that DDS file into the QS36F lib and do a CPYF of the old data into it.
So - from RPG36 they're flat files - but from the OS side, they have a description.
Regards,
Daniel
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.