You don't want to 3.4 delete the data sets, this may cause logger to think the
log stream is damaged.
You'll want to evaluate what is in the log streams and archive the data
appropriately.
See z/OS MVS Setting Up a Sysplex (SA23-1399), Planning for system logger
applications, Deleting log
Just delete the log stream using the utility and then redefine it.
Rob Schramm
On Jan 17, 2015 9:34 AM, Nick Jones nrjo...@us.ibm.com wrote:
You don't want to 3.4 delete the data sets, this may cause logger to think
the log stream is damaged.
You'll want to evaluate what is in the log
Mark ,
Since you are looking at deleting orphaned logstream datasets , neither TSO
delete or deleting the logstream is going to work
Ane excerpt from MVS setting up a sysplex - Finding and deleting orphaned log
data sets says ,
The orphaned data sets should be deleted using the IDCAMS delete
I was researching logger space issue's . So I am executing PGM=IXCMIAPU with
sysin:
//SYSINDD *
DATA TYPE(LOGR) REPORT(NO)
LIST LOGSTREAM NAME(x...) DETAIL(YES)
This provides me
, 2015 12:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Logger Space
I was researching logger space issue's . So I am executing PGM=IXCMIAPU with
sysin:
//SYSINDD *
DATA TYPE(LOGR) REPORT(NO)
LIST LOGSTREAM NAME(x...) DETAIL(YES)
This provides me with the NUMBER OF POSSIBLE
Subject: Re: Logger Space
Use the same utility used to allocate and/or report them with:
DELETE LOGSTREAM NAME(name)
s
http://www.medmutual.com/
Visit http://www.medmutual.com/
CONFIDENTIALITY NOTICE:
This message is intended only for the use of the individual or entity to which
