ty TTA0: produces quota error on VMS7.3-1

[Lai King Leung]

Hi

I recently had my OS upgraded from VMS 7.2-1 to VMS 7.3-1.

Now when I try to look at the serial port $ty tta0: - I get the following
-RMS-F-SYS, QIO system service request failed
-SYSTEM-F-EXQUOTA, process quota exceeded

The problem did not happen on VMS 7.2-1. Can anyone tell me why and what I should do to resolve the problem ?

Many Thanks

[Bradford Hamilton]

Hi,

$help/mess exquota says,

"EXQUOTA, process quota exceeded

Facility: SYSTEM, System Services

Explanation: An image could not continue executing or a command could not execute because the process exceeded one of its resource quotas or limits.

If this message is associated with a status code returned by a request to a DR32 interface, a DR11-W interface, or an LPA11-K driver, the AST quota for the requesting process is exceeded. In the latter case, an AST cannot be queued for a buffer full/empty AST. Normally, a start data transfer request can require no more than three AST blocks at a time.

If this message is associated with a vector disabled (VECDIS) status code, the process's paging file quota prohibits the allocation of sufficient process memory for storing its mainline vector state.

If this message is associated with a status code returned by a request to a DUP11 interface, a request cannot be queued because the buffered I/O quota is exceeded.

This message can indicate failure to create a subprocess because deductible quotas, when subtracted from the current quotas of the creator, would not leave the minimum required quotas for the creator.

This message may also occur if the size of a buffered I/O request exceeds the value of the SYSGEN parameter MAXBUF.

User Action: Use the DCL command SHOW PROCESS/QUOTAS to determine the current quotas and to determine which quota is exceeded. Determine whether any subprocesses are hibernating and are no longer performing useful functions; delete any such subprocesses.

If a program fails consistently because of insufficient quotas, ask the system manager to increase your quotas."

HTH, Brad

[Lai King Leung]

Brad

I've tried changing the quotas - in fact all the quotas and I still get the same error. We have VMS 7.3-1 installed on an ES45 machine and I have no problem accessing the TTA0: port. All the DS20 machines( total 6 ) all exhibit the previously quoted error when I attempt the command
$ ty tta0:

However, if I do
$ dump tta0:

it is OK !! Can anyone shed any more light on this matter ?

As far as I know, the ES45 came with VMS 7.3-1 whereas the DS20 were all upgraded from VMS 7.2-1 to VMS 7.3-1. Does it make any difference ?

Many Thanks
Lai King

[Brad McCusker]

Which quotas did you try to adjust?

Did you check the SYSGEN PQL* values, they could also be limiting you.

[Antoniov.]

Hello Lai,
I happened quite when I upgraded a customer machine to VMS 7.2-1.
I runned @SYS$UPDATE:AUTOGEN that change system parameter and reboot the system. I'm lucked!

You need more information.

You can execute @SYS$UPDATE:AUTOGEN SAVPARAMS that write SYS$SYSTEM:AGEN$FEEDBACK.DAT; then you can edit this file and perhaps you can found the limitated quota.
If you reboot the system specify SAVE_FEEDBACK option.

Different response between type and dump are due to I/O acces mode; type, if I good remember, use buffer I/O. You have MAXBUF at default 8192: try increase this.
Remember the problem can be a user quota. Try using another user (i.e. SYSTEM). New version of O.S., sometimes, required more resource than oldier version.

You can open two session; on first execute SH PROC/ID=xxx/CONT where ID is the second session ID executing ty TTA0:; look for process quotas and compare with system parameters.
Good luck.