|
My COMMON Handout, ABC's of AS/400 System Management has some detailed documentation as to how to change system command defaults, and how to replicate this from release to release. If anyone would like a copy of this please send e-mail today, and I will send it today. WARNING, the .PDF file is almost 2MB! Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com rob@xxxxxxxxx Sent by: To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> midrange-l-bounces@x cc: idrange.com Subject: Re: Problem with SBMJOB and Library List 03/20/2003 09:52 AM Please respond to Midrange Systems Technical Discussion Excellent idea Jim! Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Jim Franz" <franz400@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 03/19/2003 11:18 AM Please respond to Midrange Systems Technical Discussion To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc: Fax to: Subject: Re: Problem with SBMJOB and Library List >But on V5R1 IBM must have tightened up the screws on this command. This definitely did not change in V5R1. If you change the command default, all your clps are ok as long as they do not specifically use the option *current. You will have to change the cmd default for every future release. As others have suggested, I think your prev box command default had been changed. To keep track of all overrides to IBM stuff I do, I reapply them at every IPL in the startup program. My startup pgm then is the documentation of what is changed. On a new release, you always have to IPL, and the update will occur. jim ----- Original Message ----- From: "Robert Perno" <r_perno@xxxxxxxxxx> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, March 19, 2003 10:41 AM Subject: RE: Problem with SBMJOB and Library List > >From the responses i am getting, i guess i did not explain myself very well. > I'm sorry. Here is the actual SBMJOB command listed below: > > SBMJOB JOB(INPINPCL) JOBD(QGPL/JOBQINAR) + > RQSDTA('CALL INPINPCL') > > In JOBD JOBQINAR i have set up a special list of libraries under the INLLIBL > parm which i will use in the SBMJOB comand. This library list is not being > used when the job is submitted off. Through further testing we have found > that the above SBMJOB on our old box picked up the JOBD's library list > without having to code the parm INLLIBL(*JOBD) as someone suggested. But on > V5R1 IBM must have tightened up the screws on this command. Thanks for your > comments. Seeing as all our code on the new box uses jobd's in the SBMJOB > commands - i am going to change the default value of parm INLLIBL to *JOBD > with the CHGCMDDFT command. Can someone tell me if i need to recompile all > the CL pgms or will they work just by changing the parm. > Thanks again for all your help - this list is a blessing. > > Robert Perno > > -----Original Message----- > From: Colin Williams [mailto:colin.williams@xxxxxxxxxxxx] > Sent: Wednesday, March 19, 2003 9:40 AM > To: 'midrange-l@xxxxxxxxxxxx' > Subject: Problem with SBMJOB and Library List > > > Robert, > > The default for library list on a SBMJOB (keyword INLLIBL) is usually > *CURRENT, which uses the submitters current library list even if you have > specified a JOBD. > > If you want the JOBD from the library list to be used, specify > INLLIBL(*JOBD) on the SBMJOB, so that the library list from the JOBD is > used. Watch out for SYSLIBL and CURLIB too! This has tripped me up many > times, when I forget it! > > Cheers > Colin Williams > Bertram Books UK > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.