×
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 Kevin,
Just a quick note on top of Scott's notes. The batch routing process
starts out in OPM compatibility mode. So if the first program you
submit is *CALLER, then your job stream is in OPM compatibility mode.
No, that's not true. Not if you're using the same terminology that I'm
using!
When I say "OPM Compatibility Mode", I mean programs compiled with
DFTACTGRP(*YES). If you've specified DFTACTGRP(*NO) and
ACTGRP(*CALLER), it will not inherit OPM compatibility mode from the caller.
It's true that it'll run in the default activation group -- but the
other aspects of OPM compatibility will not be inherited. It will run
like an ILE program -- the only difference being that the activation
group can't be reclaimed.
That means that default scope of the ovr and dltovr commands changes.
In OPM mode the default acts like *CALLLVL.
That's true. Because it's running in the default activation group, the
value *ACTGRPDFN (which is the default value for the OVRSCOPE parameter
of the OVRxxx CL commands) will act like *CALLLVL.
However, that's an aspect of being in the default activation group, not
an aspect of being in OPM-compatibility mode.
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
