home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: bit.listserv.ibm-main
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!sdd.hp.com!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu!j-grout
- From: j-grout@uxa.cso.uiuc.edu (grout john robert)
- Subject: Re: How to expand SYS1.LOGREC
- References: <IBM-MAIN%92111717415102@RICEVM1.RICE.EDU>
- Message-ID: <Bxx43G.HHw@news.cso.uiuc.edu>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Reply-To: j-grout@uiuc.edu
- Organization: University of Illinois at Urbana
- Date: Wed, 18 Nov 1992 15:23:38 GMT
- Lines: 18
-
- Leonard D Woren <LDW@USCMVSA.BITNET> writes:
-
- >As someone else already replied, you can just rename the existing one,
- >allocate and initialize a new one, and IPL. Don't forget to dump the
- >data from the old one before you scratch it. And yes, don't scratch
- >the old one before IPLing. It's opened only at IPL time. Also note
- >that you can't move SYS1.LOGREC because it has absolute disk addresses
- >in it. I heard a story of one site that reorganized sysres and ended
- >up with logrec data in the middle of an SMP dataset because they
- >didn't re-init logrec.
-
- So one should allocate SYS1.LOGREC with DSORG=PSU (for physical
- sequential unmovable) to tell the system (and any helpful
- reorganization utilities) that it can't be moved.
- --
- John R. Grout j-grout@uiuc.edu
- University of Illinois, Urbana-Champaign
- Center for Supercomputing Research and Development
-