q recording shows that account is on for the designated system id and off for the rogue id. It seems that the issue may have started with a retrieve command being issued on the rogue id. That id is and always has been a class g user. It did at one point have iucv *account authority. How can a class g user get into trouble like that? -James
On 6/13/07, Schuh, Richard <[EMAIL PROTECTED]> wrote:
Any id that has the proper authority (privilege class A, B, C, E, or F) can enter a RECORDING command and start receiving data from any of the many services (EREP, Monitor, etc.). Until recording for that id is stopped, it will continue to have records queued for it to retrieve. More than one machine can retrieve the records. If your normal recording id is up and running, you should be OK. You can use the QUERY RECORDING command to determine the current state. Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of James M Sent: Wednesday, June 13, 2007 10:20 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: HCPCRC8083I Rob- I did stop and purge his recording. I wonder though if purging was the right thing to do. Was that id in fact collecting system accounting info rather than the designated system id and if so have I now lost that info for the time in question? -James On 6/13/07, Rob van der Heij <[EMAIL PROTECTED]> wrote: > On 6/13/07, James M <[EMAIL PROTECTED]> wrote: > > > I'm getting these messages every two minutes w/records growing > > 07/06/13 11:42:17 : 11:42:17 HCPCRC8083I ACCOUNTING RECORD THR > > ESHOLD HAS BEEN EXCEEDED FOR USERID XXXXXXX. > > , > > 07/06/13 11:42:17 CURRENTLY 00007980 RECORDS ARE ENQUEUED. > > > > The ID is never logged on - has minidisks that others link to. > > I'm wondering what to do and also if I did something wrong - I did > > change the account number for this user (and others who link to it) in > > the cp directory. > > Something must have started that userid and made it retrieve account > records. If you don't need it to, you may want to > RECORDING ACCOUNT OFF PURGE QID XXXX > If you let account records queue long enough you will eventually fill > up a CP warmstart. > > And you probably should remove the IUCV *ACCOUNT from users who don't > need it... > > Rob >
