|
Suppose you run a particular job with a job description and routing entries that use a particular class, or *CLS. And you have the temporary storage set to that class at 3GB. Now, suppose you put on an upgrade from the vendor and it now crashes because it hit this temporary storage limit. Which you increased during a previous upgrade. Now, suppose the vendor says everyone else has that particular class set to *NOMAX, as it comes defaulted that way from IBM. But you set it down to stop some runaway job years ago that you can't even remember. When you ask them why it's eating more memory they reply that the information is proprietary. Do you accept that? And just increase the size of the temporary storage associated with that class? Now suppose the vendor is IBM. The class is QGPL/QBATCH. And it's associated with Seq Nbr Program Library Compare Value 9999 QCMD QSYS *ANY of subsystem QBATCH. And the upgrade was a set of cumes and groups. And the software package is OS/400 and it's the command SAV. Do you still just accept it? I have a pmr open and this is the attitude I am getting from IBM. Now I have to decide if it's worth pursuing. As a temporary work around I doubled the size of the temp storage for that class to 6GB. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
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.