× 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.



   You have to do some reading up on the technical manuals.  I tend to focus
   in a particular area, get it resolved, before focus in some other area. 
   My memory is that I had to do some WRKSYSVAL settings to
   * tell the 400 to hang onto disk space in spool area from deleted reports
   for a few days after they deleted, so new spool space used efficiently, by
   eating space of recently deleted other reports.
   * automatically recover disk space from deleted spool reports after a few
   days, to balance out excess hoarding being deleted a lot at one time.
   * do this sooner in an IPL, which we have setup in GO POWER to have the
   400 shut down in wee hours of weekends when we not expect anyone will be
   using the system anyway ... there is also a topic of electricity
   consumption, not much, but it adds up ... over the life of a computer, the
   cost of the electricity can exceed the cost of the hardware, according to
   some business news stories.

   You might also check GO CLEANUP.  Ours runs at like 3 am.
   Different things stored different lengths of time ... I want to be able to
   check on problems that might not get reported to IT promptly.

   We use GO CMDSCDE to schedule things, most of them in wee hours of
   weekdays.  I guess some system cleanup tasks could be added to collection
   this way.

     Does an IPL do this automatically?  Reclaim the delete spooled files?

   We have an AS/400 model 170 on V5R1, running BPCS405CD.  My vague memory
   says it was Dec 1999 that it first arrived at our company. 

   Our modifications include stuff like embedded SQL and RPG/LE that are not
   native to BPCS405CD, but I have been using Query/400 very heavily because
   corporate need is usually RAPID deployment of new stuff, and I can get
   something new deployed with Query/400 in hours, where solid high level
   language development can take days, with the tools my company has invested
   in (pretty much native/400 only).

   I have encountered lots of things. 
   I not know correct, or popular naming for all of the phenomena.
   not recognize "stiction" context

   One thing that concerns me is the degree to which people all through the
   company have become dependent on reports stored in spool that were
   generated months ago, at a company which has not purchased any backup for
   what is in spool.  I do monitor disk space regularly.  We Ok in that
   department, for the moment, partly because I regularly attack ancient
   data.  I am heavily relying on WRKSYSVAL to manage sizes of 400
   performance ingredients.

   Since I am the person who runs END MONTH Fiscal, and now have Different
   OUTQ for each of about a year's worth of EOMs, with typically 50-75
   reports per end month, and several other specialized OUTQ, when we try to
   go into WRKSPLF AL it is VERY SLOW to get there as compared to WRKSPLF
   someone who not generate, or hoard, many reports.  This is why I pretty
   much use WRKOUTQ whatever nowadays to access reports I need.

     Al,

     How old is your machine? What model and OS level? Have you ever
     encountered "stiction"?
     --

     Paul Nelson

   -
   Al Macintyre
      veteran of over 20 years working in ERP
      veteran of over 40 years of working at IBM Customer sites
      veteran of over 60 years trying to communicate, sometimes unwisely
      Programmer, Operations, Security
      jack of all AS/400/BPCS trades, master of some

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.