home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!stanford.edu!bcm!convex!darwin.sura.net!wupost!gumby!yale!yale.edu!news.yale.edu!mars.caps.maine.edu!maine.maine.edu!cunyvm!psuvm!auvm!COMPCTR.CCS.CSUS.EDU!RYERSONRA
- X-Mailer: Pegasus Mail v2.1c R5.
- X-Pmrqc: 1
- Message-ID: <MAILQUEUE-99.921117095107.352@compctr.ccs.csus.edu>
- Newsgroups: bit.listserv.ibm-main
- Date: Tue, 17 Nov 1992 09:51:04 PST
- Sender: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1.BITNET>
- From: Rob Ryerson <RYERSONRA@COMPCTR.CCS.CSUS.EDU>
- Subject: DFHSM and the SETSYS MONITOR Control Parm
- Comments: To: ibm-main@ricevm1.bitnet
- Lines: 9
-
- Can't address all your questions, but at R6 my experience with the
- NEWCOPY parm is that if you cross the threshold % set for the warning
- message, nothing will 'reset' the condition except performing the
- NEWCOPY option. After you have corrected the problem, eg. include
- more extents, repro the dataset, or extend it, you should perform
- the NEWCOPY to allow DFHSM to display the correct %'s. I don't
- remember if we continued to get syslog messages, but I do remember
- that a QUERY againsts the CDS's continued to show inaccurate totals
- until a NEWCOPY.
-