×
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.
Hi Jerry,
Jerry Adams wrote:
H DEBUG(*Yes)
H DFTACTGRP(*NO)
H ACTGRP('QILE')
H DATFMT(*ISO)
H DATEDIT(*YMD)
H OPTION(*NODEBUGIO)
I basiscally agree with your suggestion, except:
I would recommend that you avoid using QILE. It's a very small thing --
but I suggest instead of specifying QILE, you use an activation group
named after your company. Such as ACTGRP('BWWHOLE') (For B&W
Wholesale). It will work EXACTLY the same way as QILE. But, if you
install 3rd party software, it might mistakenly reclaim QILE and reclaim
your programs without you realizing it, or you might mistakenly reclaim
their programs. It's much less likely that a 3rd party would name their
actgrp BWWHOLE.... Like I said, it's a very small thing, with a very
small likelihood of mattering to anyone -- but it's so easy to specify
ACTGRP('BWWHOLE') instead of ACTGRP('QILE') that you might as well do it...
Second... I would suggest adding using OPTION(*SRCSTMT) (so you'll have
OPTION(*SRCSTMT:*NODEBUGIO)) That way, when an error occurs and the
error message reports a program statement number, the statement number
will match your source code.
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
