Comments on: pwrdwnsys

By: The Most-Watched IT Questions: December 6, 2011 - ITKE Community Blog

The Most-Watched IT Questions: December 6, 2011 - ITKE Community Blog — Tue, 06 Dec 2011 14:47:32 +0000

[...] 1. Members discuss the intricacies of how not to get p0wned with pwrdwnsys. [...]

By: tomliotta

tomliotta — Tue, 22 Nov 2011 03:34:14 +0000

what shld the admin has todo if they found after that a job is runing?

It’s most likely that nothing can be done about it unless the job has some external mechanism for the operator to signal it to end. Anything the operator can do will be done by the processing of PWRDWNSYS anyway.

The best thing for the operator to do is to log that the job was running. Whatever the documented recovery is should be done when the system comes back up again.

Why would an operator run PWRDWNSYS when the system was not in restricted state? That should only happen in an emegency, so the batch job was going to be lost no matter what.

Tom

By: tomliotta

tomliotta — Tue, 22 Nov 2011 00:47:14 +0000

but does it make any error message

Does what make any error message? Are you asking about the PWRDWNSYS command or the batch job?

If the PWRDWNSYS command executes successfully, it won’t show any errors at all. Why would it? It worked the way it’s supposed to.

If PWRDWNSYS was executed with *IMMED, then the batch job won’t make any error messages because it couldn’t — the system power was pulled out from under it. If PWRDWNSYS was executed with *CNTRLD and the batch job wasn’t testing periodically for a shutdown, then the batch job won’t make any error messages because it was programmed not to care.

If PWRDWNSYS was executed with *CNTRLD and the batch job periodically tested for a shutdown (and the period was within the *CNTRLD time limit), then the batch job would make whatever error messages it was programmed to make.

Tom

By: charliebrowne

charliebrowne — Mon, 21 Nov 2011 17:25:09 +0000

Important question is “WHO has authority to do a PWRDWNSYS?”
And why would they do that without notification of others?
You really need to restrict authority to that command.

Next questions “Is the batch job updatiung files? and is the file(s) being journaled?”
Are you using commitment control?
If it is just a print or something else that can be rerun, you can just resubmit when the server comes back up.

By: deepu9321

deepu9321 — Mon, 21 Nov 2011 11:38:55 +0000

Yes. You should be looking into the List of Parameters and possible Options.
If Command is executed with an Option *CNTRLD to end with Specified DELAY time, Then system will check for the Running Jobs and will end all active Jobs in a controlled manner. In this case, Job log will be written for the Job.

If Command is executed with am Option *IMMED, Subsystem will end all the active Jobs immediately and the time allowed for clean up will be maintained from system values.

But, There will be few scenarios where the Active Jobs will not get finish even before Delay time, In this Case Active Jobs will be ended with out any log. This may cause Partial Updation(similar to *IMMED).

If there is any need to use PWRDWNSYS command, *IMMED is not suggested option. It can only used when the command is tired with *CNTRLD and unsuccessful.

Pradeep.

By: rajasekhar15

rajasekhar15 — Mon, 21 Nov 2011 09:03:42 +0000

yes i do know, but does it make any error message , if the cl program is an retrieving object from the server or someother information.,