On z/OS V2.2, at least (I don't recall when we added this), if you:
- Do NOT have the logrec data set named in MSTJCLxx; *and*,
- Specify LOGREC=IGNORE in IEASYSxx,
...the system should IPL without a LOGREC data set. You can use
SETLOGRC afterward, IIRC, to name a log stream or logrec data set.
By all means, try this in a safe harbor (a sysprog sandbox) first to
make sure I did not miss a step above!
Jesse 1 Robinson wrote:
I do have the dimmest memory of IPLing a new LPAR that did not yet have a
SYS&SYSCLONE LOGREC. (Disclaimer: all my memories are dim.) Perhaps the system
prompted for a usable LOGREC data set, or at least the volser of the named guy. But
I think we've established that you will not IPL without some LOGREC data set
available.
Note that this is not true for other logstream recording mechanisms like SMF
and OPERLOG. A system will limp along with no usable MANx data set; also with
no functioning OPERLOG. In fact this happens to us every time we bring up our
DR systems for the first time--without any defined logstreams. You can create a
logstream only on the exploiting system. So we IPL, then run the log stream
creation jobs for SMF, OPERLOG, and RRS.
<snip>
--
John Eells
IBM Poughkeepsie
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
