×
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.
On a 7.5 to which I have access there is a QCLLESRC in QGPL - it was not created by IBM, it also does not have the description about being a default source file, as many others in QGPL do. And it's record length is 112. I believe I know the names - owner and created by - and it's likely one of them is aware of a change. But IBM did not put that in here automatically that I can see.
Personally I don't see a reason for a longer record length for CLLE, and I don't find mention of it in the Memorandum To Users for any releases from 7.2 on. I'm aware of some who set all new source files to 112, the CL compiler could not care less, seems to me, but I've not tested anything where the content is past 80.QMQRY and QMFORM have special lengths (91 and 162, resp., which is 79 and 150 source data lengths)
Curious!
Vern
On Mon, 4 Nov, 2024 at 9:12 AM, Bryan Dietz <bdietz400@xxxxxxxxx> wrote:
To: midrange-l@xxxxxxxxxxxxxxxxxx
look at the "created by" in the object description.
If a new standard, then *IBM would be the created by user.
Bryan
smith5646midrange@xxxxxxxxx<mailto:smith5646midrange@xxxxxxxxx> wrote on 11/4/2024 8:58 AM:
My client has a few source files named QCLLESRC on their machine with record
length of 112. When I asked about them, I was told they are the new IBM
standard for CL ILE source. When I look at my 7.3 machine (max release that
I can upgrade to), there are no QCLLESRC files. That tells me that for 7.3
and earlier, there were no QCLLESRC files distributed by IBM. Is this a new
IBM standard that came about in 7.4 or 7.5 that I am unaware of?
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
