Le 16/09/2020 à 14:05, Rob Berendt a écrit :
We're doing our quarterly downtimes this week. The first one is our P8. Five lpars of IBM i, of which one hosts disk for the others. Two lpars of VIOS.
The saves are done on the four guests. Three of the four guests are down. The fourth one is still at D6000298, which it has been before I began my 45 minute commute into work. This guest comes off of the slow 10K spinning disk ASP on the host.

Gee a power down right after a full system save, on slow disks. Sure sounds like:

IBM i 7.4
System in restricted state (Normally a good place to be before you issue the PWRDWNSYS). What options do you use on CLRPOOL? This lpar is not running a "traditional" load of batch and interactive. If there were ever two interactive users at once that would be a large number. Three might be a record. Mostly Domino work. One Domino server. Therefore no QINTER, QBATCH but instead it uses QBASE.

When it is possible to control the power down sequence, I am often used to end the applications, initiate several times a CHGASPACT *FRCWRT to force memory to be dumped to disk, go to restricted state in a controlled way, continue CHGASPACT until the system is in restricted state..

Then I initiate the PWRDWNSYS with a short delay only when there is no more disk activity as WRKSYSACT shows.

I had this long D6000298 issue in the past and I always feel uncomfortable until it completes after several tens of minutes. Not sure if it solves all the causes, because I do not really know them, but I never got them again.

Rob Berendt
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818

This thread ...


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

This mailing list archive is Copyright 1997-2020 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].