I think I see what's happening. I'm guessing that task NETVTSO runs SUB=MSTR and so cannot write output to JES. DDs SYSOUT and SYSPRINT (plus NVCMDIN whatever that is) are allocated to temporary datasets. If NETVTSO is never actually shut down before V XCF OFF, then system dataset cleanup may not get control.
This made me look at our automation tasks (Netview/SA). They all have either DUMMY or a 'permanent' (non-temporary) dataset allocated to print output DDs. You might reconsider the value of allocating any output DD to a temporary dataset. Under ordinary circumstances it gets deleted by the system. Otherwise it's a piece of litter to clean up. In no case I can think of could you ever look at the contents, which makes it pretty useless. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Mike Schwab <[email protected]> To: [email protected], Date: 07/15/2014 07:08 AM Subject: Re: Cleanup Sort Volumes Sent by: IBM Mainframe Discussion List <[email protected]> Exactly. The task starts shortly after IPL and runs 24*7 until just before the next shutdown. SYS13349.T061014.RA000.NETVTSO.NVCMDIN.H06 SYS13349.T061014.RA000.NETVTSO.SYSOUT.H06 SYS13349.T061014.RA000.NETVTSO.SYSPRINT.H06 are on DIS,NEW volumes on our system. On Mon, Jul 14, 2014 at 6:23 PM, Skip Robinson <[email protected]> wrote: > There may be some confusion over the term 'temporary dataset'. In the > mainframe world, that does not mean just any old file that isn't needed > long term. There are two types of data sets: temporary and non-temporary. > z/OS does not define 'permanent' at all, only 'temporary'. Temporary data > sets are assigned patterned names generated by the system. They cannot be > cataloged. The only valid disposition is either PASS or DELETE, not KEEP. > If the final disposition in a job is PASS, the system substitutes DELETE. > > Finding a true temporary data set on a volume after the creating task has > ended implies either a system crash or an APARable failure in the > operating system. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] > > > > From: Mike Schwab <[email protected]> > To: [email protected], > Date: 07/14/2014 02:58 PM > Subject: Re: Cleanup Sort Volumes > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > We have some small datasets from started tasks. Don't delete until > the next IPL. > > On Mon, Jul 14, 2014 at 3:19 PM, Doug <[email protected]> wrote: >> Some shops allow the sort volumes to be used for datasets that are > passed between jobs and the last job of the series 'is supposed to' issue > a delete. (or not) grins. >> >> . >> >>> On Jul 14, 2014, at 13:09, "R.S." <[email protected]> > wrote: >>> >>> My €0.02: It is strange that temporary datasets survived end of job. >>> Usually it is the system responsibility to clean up after the job. >>> >>> Assumption: nobody gave the SORTWK datasets permanent names. >>> >>> -- >>> Radoslaw Skorupka >>> Lodz, Poland ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
