On Wed, 10 Jul 2019 at 16:48, Phil Smith III <[email protected]> wrote:
> BUT it seems to eat storage. That is, if I run a program that calls the > API repeatedly and invalidly, it writes the errors to SYSPRINT, but gets an > S878 reason code 10 after 1900-odd iterations. I've tinkered, commenting > out the PUT: no change. So it's not the actual PUT that's irritating it. If > I comment out the CLOSE, it gets the S878 after fewer iterations, which > sort of makes sense: it's leaving the file open. But why is it running out > at all? The DD is just SYSPRINT DD SYSOUT=*, and REGION=0K. I feel like I'm > missing something basic and obvious here (not the first time). > I'm not having the necessary Aha! moment from reading your code. So I would start by looking at the associated IEA705I message that will be around somewhere (Syslog, TSO session). See what the failing request is asking for. It may be that that request is the victim rather than the offender, but it doesn't hurt to see. If the request is reasonable then get a dump and see who's used up the storage. A mere 1900 iterations must be getting (and forgetting) quite a big chunk each time, even of 24-bit storage. You might also consider pointing the DD at something that isn't SYSOUT, just to see if it could be some over optimistic code in JESn. Tony H.
