http://itknowledgeexchange.techtarget.com/itanswers/cl-pgm-for-full-system-save-from-the-hmc/ Thu, 23 May 2013 08:17:13 +0000 hourly 1 http://itknowledgeexchange.techtarget.com/itanswers/cl-pgm-for-full-system-save-from-the-hmc/#comment-110309 TomLiotta Wed, 22 Aug 2012 01:12:36 +0000 http://itknowledgeexchange.techtarget.com/itanswers/cl-pgm-for-full-system-save-from-the-hmc/#comment-110309 Sure, you could do it; but why would anyone want to?
 
Now, there are a couple fundamental problems with your code.
 
First, you didn’t specify a job name in your CHGJOB statement. You have the JOBQ() parameter, but that is only meaningful against a job that is currently on a jobq. You can’t change the jobq of the current job, so a job name must be supplied and it must be for a different job.
 
Second, you ran ENDSBS *ALL with no error handling at all — you merely ignore a particular condition. You risk putting your system into an unuseable state until you can force an IPL. Further, you don’t test to see if restricted state has been achieved; you jump straight to your saves. It’s almost guaranteed that restricted state will take a couple minutes or so to arrive. By that time, your SAVSYS command will probably already have failed. Your INZSYS command might take long enough, but it can’t be expected.
 
That’s about all that can be said for now.
 
Tom

]]>