Tom and I have always agreed on this subject. We've hammered on our automation product vendors (Candle/IBM) to provide for each task an option to bring down it or not. Some tasks should come down clean; for others it could not matter. The problem is that until all tasks managed by automation are brought down, the automation task itself cannot be mollified. We were always told that in order to restart a failed task properly, it needs to be considered 'always up'. Certainly you can choose to V XCF at any point, but do you want to delegate that decision to whichever operator happens to be driving the console?
To paraphrase the famous Mom aphorism: if automation ain't happy, ain't nobody happy. BTW Happy Mother's Day to all you moms! . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tom Brennan Sent: Friday, May 06, 2016 10:38 AM To: [email protected] Subject: (External):Re: OMVS hang at system shutdown I'm with you... It seems like operators are often told that D A,L should come back with nothing before V XCF. Of course we want to get tasks with databases shutdown nicely (CICS, DB2, etc.), and files closed (bpxoinit shutdown) and checkpoint records written ($PJES2 or even $PJES2,TERM) but why worry about things that work just fine even if they die abruptly? For example, I once saw operators waste a lot of time trying to stop LLA... Umm, just push the button. I hope nobody shows them the D A,ALL command or the system will never be shut down. Jousma, David wrote: > Why even bother shutting it down? We do the following as one of that last > few things, before doing the V XCF command. > > F bpxoinit,shutdown=forks > F bpxoinit,shutdown=filesys > > And call it good. > > _________________________________________________________________ > Dave Jousma > Assistant Vice President, Manager, Mainframe Engineering > [email protected] > 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f > 616.653.2717 > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Tom Conley > Sent: Friday, May 06, 2016 9:18 AM > To: [email protected] > Subject: Re: OMVS hang at system shutdown > > On 5/6/2016 8:47 AM, Styles, Andy , SD EP zPlatform wrote: > >>On Fri 06/05/2016 at 13:14, Tom Conley wrote: >> >> >>>>*BPXI056E OMVS SHUTDOWN REQUEST HAS COMPLETED SUCCESSFULLY >>>> >>>>(why is that an 'E' level message?) >>>> >>> >>>"E" here is not "ERROR", it's "Eventual Action", which is the "F >>>OMVS,RESTART" command. >> >>Ah! Of course - I'd forgotten IBM use the same suffix to mean different >>things. I do find it odd, though, that this is considered that way - there's >>plenty of other address spaces that you might consider "eventual action" - >>RACF (or any other ESM) for example.. >> >>Thanks, >> > > > Once upon a time (apparently pre-z/OS V1R3) OMVS was not restartable, so they > probably added the message as an E message to let the operator know that it > was restartable. > > Regards, > Tom Conley ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
