×
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, James:
This is a long standing problem with all OS/400 *CMDs in CL programs you
ship to other machines. (probably since System/38 CPF....)
The "trick" to avoid these issues is:
1. always prompt commands
2. and always press F10=Additional parameters, and/or press F9=All
parameters,
3. always "fill in" all the parameters, by typing over the values you
see shown on-screen (the defaults)
That way, by specifying the "defaults" you force the CL compiler to
include those values in the compiled *PGM, so you "lock in" your
defaults at your shop, and they will still be there, when you send the
compiled *PGM to other machines or LPARs..
Hope that helps,
Mark S. Waterbury
> On 6/18/2012 2:00 PM, James Lampert wrote:
I have a CL program that contains a SBMJOB. The INLLIBL is not specified
in the CL, but the default on our boxes is *CURRENT.
The default INLLIBL parameter for a SBMJOB on a customer box that's
currently giving us some grief is *JOBD, and the INLLIBL on the job
description in question is *SYSVAL.
It's acting like it's going by the default on the system where the CL is
being executed, rather than the default on the system where the CL was
compiled. Is that expected behavior?
--
JHHL
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.