pwrdwnsys

1395 pts.
Tags:
scheduling batch jobs
im submitting a cl program to run in batch mode, suddenly some has given the pwrdwnsys cmd, and the server was getting down, what will happen of the prg sbmtd ? what shld the admin has todo if they found after that a job is runing?

Answer Wiki

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

Any Job will run only when the server is available.
After issuing the PWRDWNSYS command, Server will get down and the Batch Job wil be no more active.
The Progress(or Update) made by the corresponding Job will remain as usual.
And, Admin has to make the Server Up again.

Pradeep.
———————————————————————————————————————-

May I suggest that you go to your command line at the console and type GO SYMNU <enter> [SYSTEM OPERATOR MENU] and see if your system has the IPL aready setup in as a MENU item – where you just type the number and <enter> if your AS400 system has been setup with this option already. check it out. if not, then maybe IBM can direct you on the “HOW TO” set the menus up. Tom

Discuss This Question: 6  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.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Rajasekhar15
    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.,
    1,395 pointsBadges:
    report
  • deepu9321
    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.
    3,695 pointsBadges:
    report
  • CharlieBrowne
    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.
    41,380 pointsBadges:
    report
  • TomLiotta
    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
    125,585 pointsBadges:
    report
  • TomLiotta
    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
    125,585 pointsBadges:
    report
  • Rajasekhar15
    [...] 1. Members discuss the intricacies of how not to get p0wned with pwrdwnsys. [...]
    0 pointsBadges:
    report

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.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

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

Following