Re: sysuaf

From: JF Mezei (jfmezei.spamnot_at_istop.com)
Date: 02/17/04 

Date: Tue, 17 Feb 2004 13:01:53 -0500

"Stewart, Bill" wrote:
> $ SUBMIT/QUE=NIGHT_QUE/USER=ABC999/LOG=LOGFILES:ABC070/PRIORITY=101
> CMD:CMD070.COM/NOPRINT
>
> The immediate error is:
> %SUBMIT-F-INVQUAVAL, value 'ABC999' invalid for /USER qualifier
> -RMS-E-FLK, file currently locked by another user
>
> HP is telling me that the job must have write access to that record,
> or it will die.

Well, the SUBMIT doesn't create the job, it only queues it. When the batch
symbiont actually creates the job, it does need write access to the SYSUAF to
set the date of last batch login, but you'd get a message on OPCOM about a job
not being able to run due to the above. (this is similar to when you have
multiple jobs running and the next job fails to start because its log file
cannot be opened because the version limit prevents creation of a new file and
it can't delete any of the older files because they are in use).

> Is there a good way to keep this from happening?

Can this be reproduced at will, or was it a once-in-a-blue-moon event ? I
would suspect some separate application might access SYSUAF directly and may
have taken a lock on the record for that user.

Relevant Pages