AS/400 novice questions about powering down system

15 pts.
AS/400 administration
We have a system that will need shut down in the next month or so because the cache batteries need replaced.  I was wondering what commands I need to do make all this happen.  I know we need to do a PWRDWNSYS.  Do I need to do commands before or after the shut down?  Like shutting down the subsystems or anything else and if so what are they specifically. 

I might be making this harder than it really is, but I'm scared as hell at being burned by this machine that I know only a little about so any guidnace from anyone would be greatly appreciated.

Software/Hardware used:

Answer Wiki

Thanks. We'll let you know when a new response is added.

You can end subsystems ahead of time if you want to, but it is not necessary.
PWRDWNSYS *IMMED will termineate everything and shut it down.
Just be sure nothing is running that you do not want to cancel.


Do <i>not</i> use the *IMMED option. Per my IBM CE when *IMMED is used the system does not write the cache contents to disk. Use *CNTRLD with a delay of a minute or so.

Discuss This Question: 5  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Gsherin
    ok fair enough, pardon my ignorance for the followup questions. Is that a matter of just going into WRKACTJOB and having the CPU% be 0% or does that mean not having things sitting in EVTW, DLYW or some other status within any of the SBS? Because the way our stuff is set up there always is stuff just sitting there. We also have EZPRINT and SLEEPER(hopefully you know what those are) running on this machine. Does anything have to be done about them before I shut it down?
    15 pointsBadges:
  • CharlieBrowne
    No, you do not have to worry about those jobs. Your main concern would be any batch jobs that are running. Normally they are in sbs QBATCH. Or users signed on the the system and those would normally be in QINTER. Your DLYW *Delay Wait) and EVTW (Event Wait) are jobs just sitting out there waiting for some action to trigger them. You do not have to worry about them. They should start automatically whith your next IPL.
    62,385 pointsBadges:
  • TomLiotta
    While it's not required to end active jobs before PWRDWNSYS, it is a very good practice to do so. It should only take a few minutes, and you might avoid some unexpected problems by doing so. You'll want to go through the process at the console since nothing else will be available by the time you get to the end of this. A basic sequence might go this way:
    1. ENDMSF
    2. ENDWTR *ALL
    It may take a couple minutes for all of the activity to settle after those are run. There might be other commands that you' should run along with ENDMSF. Examples I've seen in the past are ENDFAXSPT and ENDOPTSPT, but they depend on things you might not have installed. Once things settle:
    You can use WRKACTJOB with F5=Refresh to see the jobs going through their shutdown steps. Watch for any jobs that attempt to end but that cannot complete. (That's unlikely, but you don't want to go to the next steps until this part stops its activity.) When the system is quiet again, you can use WRKSBS to see a list of active subsystems. You can use '8=Work with subsystem jobs' to step through the subsystems and see any that have no remaining jobs. Empty subsystems can be ended and taken out of your way. Usually, communications and spooling subsystems (probably QCMN and QSPL) can be ended safely at this point even if jobs are still there (as long as the jobs aren't stuck in an ending status). Those subsystems can be ended with ENDSBS xxxx OPTION(*CNTRLD) DELAY(10). If possible, always give a few seconds to the jobs to end. At this point, all communications should already be ended. Server processes are also ended, so it's not likely that anything new is going to come in from the outside. I'm not familiar with EZPRINT nor SLEEPER. They should both have vendor-supplied methods of shutting them down. It might be commands, or they might run in their own subsystems and simply react automatically when those subsystems are ended (assuming you end them *CNTRLD with a few seconds allowed.) Your WRKSBS list of subsystems should now be fairly short. If no jobs seem to be in trouble, you can probably end all remaining subsystems with ENDSYS OPTION(*CNTRLD) DELAY(20). When that finishes, a message will be sent to QSYSOPR telling you that the system has been ended to restricted state. When that message appears, you can run PWRDWNSYS OPTION(*CNTRLD) DELAY(30) RESTART(*NO), and then sign off. Since your console job should be the only one running, the power-down sequence should begin as soon as your signoff completes even if 30 seconds hasn't passed yet. I like to have a CL script that walks through the commands listed above along with any customization for specific systems. It's a few minutes extra, but it catches a few things that can sometimes cause trouble after the next IPL. It helps to keep the system database cross-reference in good condition, and it avoids some problems from hung jobs. As was originally said, none of it is necessary -- most of the times. When something isn't quite right with the system, though, it can be handy to catch it before pushing things over the edge. Tom
    125,585 pointsBadges:
  • jinteik
    Can I also recommend, that you do full backup of the system before you do the change of cache battery? this is more for safety reasons.
    18,995 pointsBadges:
  • slack400
    Don't sweat a Full System Backup over a cache battery replacement. I'd hope your group has some idea as to how a startup and shutdown for your environment usually plays out. PWRDWNSYS *IMMED will get you where you need to be. After the work is done power up the system and hopefully your QSTRUP program has been updated properly over the years to ensure the right subsystems and services are brought up for your environment.
    2,740 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: