------------ on Wed, 30 Jan 2013 19:02:25 -0800, Phil Smith wrote: >We have a started task running. It has various SPOOL files open, to which it's >writing - SYSPRINT et al., including SYS00001. We have a LOG SPIN command, >which can close SYS00001; subsequent output to that DD then goes to SYS00002. > >Should we then be able to purge the SYS00001? It's closed - nothing is writing >to it. but P in SDSF says "INVALID COMMAND". > >This is an issue because the whole point of doing a LOG SPIN is to be able to >purge the closed piece of the log. What am I missing? Is there a way to purge >the file? > >Thanks for any advice/thoughts/whatever.
Phil, You mentioned you are dealing with output from an STC, but you didn't mention if the task has been functioning for some time and now isn't working like it was before or if it is a new task that isn't working as hoped for... So I'll take my stab at it approaching this as a latter case of something new. To be able to process SYSOUT type data sets after they have been closed, but before the job/task has finished, FREE=CLOSE must be specified either on the file's DD statement or internally within the program code. If you couple that with the timing/volume options of the SPIN operand, you should be able to periodically process output for a long running task in a somewhat automated fashion. I'm wondering why you want to purge a log data set without examining it beforehand instead of keeping it around for whatever purpose it supported (at least for some limited time), but that is your business. regards, Russell West Compass Computing Resources ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
