×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
My preferred MO is to have a sourcefile of 112 record length so that I
can have all the RPG, DDS, and CL members for a task in one place. Our
production cl source file is 92, so when the development copy gets moved
to production, I run the danger of losing essential stuff at the right
end of the source record. We discover this when the production source
fails to compile, and we've also had fun when it does ompile, but we
have production behaviors that weren't as pretty as the test behaviors.
I've since changed to my not-so-preferend MO (having a separate
source-file for CL development).
We're using WDSC V 7.0.0.8 Interim Fix 001 and i/OS V5R4M0
I saw that this was issue mentioned in the archives, but my question is:
Does RDi have a better approach for this? Like maybe a CL parser
preference that restricts CL source to 92?
PS: Replies to this post not received before 6 PM EST won't be seen by
me until Monday.
--Michael Koester
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
