Spool file got full. because of a tiny little COBOL logic problem and screwed up my MVS…$HASP355 SPOOL VOLUMES ARE FULL. Just because I tried to write 500,000 records to the printer? Well excusseeeee meeeeeeee (: Actually partly because of a logic problem, also because I thought I was working with a much smaller file.
I’m not a MVS systems programmer. So I did what wouldn’t have been possible…back in the day, I simply unzipped a tk4- image I did a few days ago. It didn’t have my new 3350 DASD I recently added. So I copied that DASD from the borked system to the new unzipped system. And made the necessary config changes. However, if I typed in the prefix of the name of a dataset in TSO, it couldn’t find it, but it did if I typed in the VOLID. I don’t know if that was a MVS, TSO or some kind of catalog problem. I just deleted them and reran the local Linux JCL to recreate them. A real MVS system programmer could most likely fixed the problem.