RE: QCLLESRC -- MIDRANGE-L

× 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.

Subject: RE: QCLLESRC
From: <stefan@xxxxxxxxxx>
Date: Mon, 4 Nov 2024 16:50:26 +0100
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

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)

It's the other way around 😊
If you create a sourcefile with a recordlength greater than 240 then SEU can't use it.
I tried and now I need something bulletproof......

Best regards

Stefan

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QCLLESRC , Jack Woehr
Re: QCLLESRC , Javier Sanchez
Re: QCLLESRC , Rob Berendt

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.