james smith wrote:
RS/Mike
What does SETLOGRC (the SET LOGREC command) have to do with OPERLOG?
OPERLOG is controlled via the VARY OPERLOG command.
You can also use OPERLOG as a DASD-only log stream. This method is only
suitable for a single system sysplex. I believe IBM has announced that
Funny how as we 'mature' these viruses seem to strike more often :-))
James F. Smith
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of R.S.
Sent: 06 January 2007 22:48
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SYSlog to OPERLIB
james smith
Hi all,
We have 2 boxes, 2 separate locations. Location1 has 4 lpars, and location2
has 2 lpars,
one lpar being a backup to the production lpar at location1.
I am planning to move to operlib from syslog at both locations, but I can
find where a migration
like this is documented.
--
Thanks,
Mike
Mike Szyszka wrote:
Hi all,
We have 2 boxes, 2 separate locations. Location1 has 4 lpars, and
location2
has 2 lpars,
one lpar being a backup to the production lpar at location1.
I am planning to move to operlib from syslog at both locations, but I
can
find where a migration
like
lpar at location1.
I am planning to move to operlib from syslog at both locations, but I
can
find where a migration
like this is documented.
Do you mean SYSLOG to OPERLOG ?
If yes then:
1. All systems affected have to be in parallel sysplex.
2. Then define SYSPLEX.OPERLOG logstream and issue
@BAMA.UA.EDU
Subject: Re: SYSlog to OPERLIB
Thanks They are not in a parallel sysplex, and will not be in the future
at all.
On 1/5/07, R.S. [EMAIL PROTECTED] wrote:
Mike Szyszka wrote:
Hi all,
We have 2 boxes, 2 separate locations. Location1 has 4 lpars, and
location2
has 2 lpars,
one
6 matches
Mail list logo