I'd like to echo earlier advice to avoid this whole problem altogether by moving to SMF logger. Among the problems solved by logger is the need to synchronize offload processes. This is because offload is independent of IPL and other system activity. There is no longer a 'full' condition to deal with. Setting up for logger requires some preparation, but no user code creation. It's all determined by parms and governed by TOD.
Although I have not set it up, SMF logger, like other logger exploitation, should be doable without a CF by using DASD-only logging. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Thursday, November 02, 2017 7:14 AM To: [email protected] Subject: (External):Re: SMF Dump Exit - IEFU29 I usually use at least 4 MAN files for low utilized systems (like a sysprog sandbox) and more for heavily used systems. That way at IPL shutdown or startup I usually have at least one free and no need to offload/switch until I am ready Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Tim Deller > Sent: Thursday, November 02, 2017 5:27 AM > To: [email protected] > Subject: Re: SMF Dump Exit - IEFU29 > > Sometimes the SMF datasets will switch during shutdown or IPL and the > exit does not catch the fact. I cobbled a program that gets run as > part of IPL to examine SMF control blocks and issue dump commands for > the datasets that need to be dumped. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
