×
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.
That is the expected behavior. Why would anyone want it otherwise? Will
the system the program is executed on ever need to know the setup that is
on the compiling system? I would hope that "feature" would never be
implemented or tons of ISVs will have a very difficult time...
Thanks,
Tommy Holden
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 06/18/2012 12:57 PM
Subject: Point of information: Initial library list on a SBMJOB,
within a CL program
Sent by: midrange-l-bounces@xxxxxxxxxxxx
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
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
