I'm converting one of our apps to use CGIDEV2 - a dream to use, by the
way. I love externalizing the HTML, just like DSPF DDS.
I DO preach to the choir, don't I?
There are some things that seem to be expected. I've dug about a bit,
but there doesn't seem to be much clear documentation about bundling
this service program and its attendant objects, like the CGIDEBUG file
and data area - whose absence is tolerated, but who wants to clutter up
the job log with those extra messages?
I see references to a data area for automatically setting the job to its
default CCSID, under certain conditions. Again, is it needed?
The command to build the thing into a different library - well, the
result seems to be everything - tutorials, all that. Which we do not
want to include in the product distribution.
This mailing list archive is Copyright 1997-2026 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.