Rodatz, William J wrote: >We use the SMF dump exit, IEFU29, to initiate a started task to empty the SMF >dump datasets when needed. It works well but there is one issue. IEFU29 >cannot issue a START command during an IPL because the SMF subsystem comes up >before JES2. There is code in the exit that looks to see if JES2 is active. >If it is not, the exit terminates.
>For those of you who use IEFU29, have you found a work-around for this problem? Why worry? What are you trying to solve? Do you have a 'START PENDING' issue which can be a really PITA? My workaround is - I simply schedule a 'I SMF' about 2-3 hours before a scheduled IPL. During IPL, I just wait out the IPL process and then have the automation software issue again a 'I SMF' a while after IPL. I have two sets of SMF exits and jobs: - One to run the IEFU29 after a 'I SMF' command (at intervals by automation software or when as needed) which then start a STC to dump that MANx dataset where needed. - The usual SMFDUMP program which dumps all MANx datasets, do a I SMF and then dump whatever remains to be dumped. In this way, all my SMF data are dumped without any intervention at all on all our LPARs. Do you have any issues during IPL and SMF dumps? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
