RE: Point of information: Initial library list on a SBMJOB, within a CL program

Yes, that makes sense. We had to get a vendor to update a CLP for that very reason. Don't assume customers won't change command defaults.
--
Sean Porterfield


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Monday, June 18, 2012 14:01
To: Midrange Systems Technical Discussion
Subject: Point of information: Initial library list on a SBMJOB, within a CL program

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 email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.