[Info-vax] Pinning down a SYSTEM-F-EXQUOTA

[Jan-Erik Soderholm]

Jeff Goodwin wrote 2011-08-04 17:35:
> "Jan-Erik Soderholm"<jan-erik.soderholm at telia.com>  wrote in message
> news:j1bi5q$kil$1 at news.albasani.net...
>> Hi.
>>
>> I have a batch job running a Python script that exits with
>> SYSTEM-F-EXQUOTA when the Python code reads in a "to large"
>> JPG file. I can "solve" it by reducing the size of the JPG
>> file, but I'd also liked to understand what is happening.
>>
>> A 211 Kbyte file runs OK then it crashed on a 311 Kbyte file.
>>
>> The error seems to happen when the Python scripts write a
>> Base64 encoded vesion of the JPG over the net in an XML
>> transaction using SUDS (a web-service tool for Python).
>>
>> The error :
>> %TYPE-F-WRITEERR, error writing SYS$OUTPUT:.;
>> -RMS-F-SYS, QIO system service request failed
>> -SYSTEM-F-EXQUOTA, process quota exceeded
>> $
>>
>> I have mainly played with BYTLM, WSEXT and PGFLQUO, both
>> in UAF and as PQL_Mxxx params. No solution yet.
> ...
>> Jan-Erik.
>
> How about MAXBUF?
>
> -Jeff
>
>

OK, I'll look at that also. It's currently set to 32000
and seems to have a max of 64000 (?) Bytes.
This is the max size of one single I/O, right ?
It doesn't feel like the correct param...

I will probably not do any more tests until it has been
posted on the Python-VMS forum...

Thanks.

Jan-Erik.