Re: Logger Space
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 data and log data sets. The section on Deleting log data give you various options depending on what application using the log streams. Using tso to delete the log data sets can cause a lot of trouble for system logger. -Nick Jones, z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Logger Space
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 streams and archive the data appropriately. See z/OS MVS Setting Up a Sysplex (SA23-1399), Planning for system logger applications, Deleting log data and log data sets. The section on Deleting log data give you various options depending on what application using the log streams. Using tso to delete the log data sets can cause a lot of trouble for system logger. -Nick Jones, z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Logger Space
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 command. Note that when you delete a log stream by deleting it from the LOGR policy, system logger deletes all the log data sets associated with the log stream that have entries in the logger directory. If a data set was orphaned or simply matches the log stream naming convention but is not in the logger directory, then system logger will NOT attempt to delete the data set when the log stream is deleted. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 it is addressed and may contain information that is privileged, confidential or exempt from disclosure by law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that you are strictly prohibited from printing, storing, disseminating, distributing or copying this message. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Neither this information block, the typed name of the sender, nor anything else in this message is intended to constitute an electronic signature, unless a specific statement to the contrary is included in this message. Thank you, Medical Mutual. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Steely Sent: Friday, January 16, 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 ORPHANED LOG STREAM DATA SETS entries These orphaned entries I use 3.4 and delete using del / purge command next to the dsn. I also have logstreams that have entries which are no longer in use. I would like to delete these dsn also. Can I use 3.4 and just delete them or is there a different way to handle these dataset ? Thanks *** CONFIDENTIALITY NOTICE *** This e-mail message and all attachments transmitted with it may contain legally privileged and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message from your system. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Logger Space
I don’t really want to delete the logstream entry just the datasets associated with the entry. Thanks -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Stone, Sandy Sent: Friday, January 16, 2015 11:54 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 it is addressed and may contain information that is privileged, confidential or exempt from disclosure by law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that you are strictly prohibited from printing, storing, disseminating, distributing or copying this message. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Neither this information block, the typed name of the sender, nor anything else in this message is intended to constitute an electronic signature, unless a specific statement to the contrary is included in this message. Thank you, Medical Mutual. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Steely Sent: Friday, January 16, 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 ORPHANED LOG STREAM DATA SETS entries These orphaned entries I use 3.4 and delete using del / purge command next to the dsn. I also have logstreams that have entries which are no longer in use. I would like to delete these dsn also. Can I use 3.4 and just delete them or is there a different way to handle these dataset ? Thanks *** CONFIDENTIALITY NOTICE *** This e-mail message and all attachments transmitted with it may contain legally privileged and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message from your system. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN *** CONFIDENTIALITY NOTICE *** This e-mail message and all attachments transmitted with it may contain legally privileged and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message from your system. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
