Almost 26 years on this platform, and got my first CPF4235 message

There was little information provided by the help text, but a Goggle search
showed that one of my client's sandbox machines hit the 2.6 million spool
file limitation.

The developers were trying to run a simulation of production for pressure
testing, and had a couple of programs submitting report generation programs
to a bunch of different job queues.

I ended up having to hold all their job queues and kill the jobs because
every one of them was getting the error message. I first noticed it when I
got an alert from the data center that BRMS was puking.

The sad part is that when they complained that their jobs weren't running
anymore, I told them that the job queues were held so I could do some
housekeeping. The lead guy actually asked me what a job queue was. He also
said they didn't need to keep any of the reports. The CLROUTQ command took
over 6 hours to flush them all out. I now have a scheduled job that holds
all their job queues, runs the CLROUTQ command, and then releases their job
queues. Then it waits 2 hours and repeats the process.

The moral of the story? Outsourcing to inexperienced people across the pond
is like giving whiskey and car keys to a pack of teenage boys.

OK, I'm done venting.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx