home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Newsgroups: bit.listserv.ibm-main
- Path: sparky!uunet!stanford.edu!bcm!convex!darwin.sura.net!wupost!uwm.edu!psuvax1!psuvm!auvm!ulkyvm!deehre01
- Organization: University of Louisville
- References: <IBM-MAIN%92111714552871@DEARN>
- Message-ID: <92322.102102DEEHRE01@ulkyvm.louisville.edu>
- Date: Tue, 17 Nov 1992 10:21:02 EST
- Sender: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1.BITNET>
- Comments: Warning -- original Sender: tag was NNEWS@ULKYVM
- From: David Ehresman <DEEHRE01@ULKYVM.LOUISVILLE.EDU>
- Subject: Re: How to expand SYS1.LOGREC
- Lines: 25
-
- In article <IBM-MAIN%92111714552871@DEARN>, Gregory Plucinski 257508
- <GRZES@PLWATU22.BITNET> says:
- >
- >
- > SYS1.LOGREC is open during IPL but not reserved.
- > try this way :
- >
- > allocate new one (for example SYS2.LOGREC)
- > format it (IFCDIP00)
- > rename old one (to for example SYS3.LOGREC
- > rename new one to SYS1.LOGREC
- >
- > IPL system
- >
- > scratch SYS3.LOGREC
- >
- > I use oldest version of MVS but this way should be ok for You.
- >
- > (by the way You can IPL system without SYS1.LOGREC )
- >
- > Gregory
- On the off chance that MVS remembers the location of SYS1.LOGREC from
- open time, I would suggest not scratching the renamed (old) LOGREC
- data set until after the next IPL. MVS may still be using it
- until that time.
-