On 10/18/07, Anne D. Crabtree <[EMAIL PROTECTED]> wrote:
> EREP OFF 2839 002 OPEREREP INACTIVE
> ACCOUNT ON 00004589 020 OPERACCT INACTIVE
And when you fix OPERACCT, do the same for OPEREREP ;-)
Eventually this will fill up precious space in CP (though that might
Thanks so much! You are always a great help!
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Thursday, October 18, 2007 9:23 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: OPERACCT
It means that at one day, your
It means that at one day, your VM system had two non-standard users:
OPEREREP and OPERACCT (I think the latter comes from a CA product).
Getting rid of those users in Q RECORDING isn't easy: requires a cold start
(I think).
But indeed, you should turn the collection for them off; otherwi
On my z/vm 5.3 system, I keep getting messages HCPCRC8083I about
accounting record threshold being exceeded for OPERACCT. I am using
DISKACNT to accumulate accounting records and it is the only userid
listed in System_Userids for ACCOUNT. When I query recording, I get
this:
q recording
