Mainframe job abend

[DDP021]

Not sure what category this should go in..Apologies if this isn't the correct one..

Here is our issue..We collect many reports into CMOD via mainframe jobs.  These jobs run under PODA* prefixes and can have multiple steps going to different reports within CMOD.  Each step contains the CMOD report id as well as an input dataset name. Lately we have been getting many PODA* job abends with the message below.  What we've found is the step that is abending, when we look, the input dataset is there.  All we do is have the PODA job restarted at the step that it abended on initially and completes successfully..We've had abends before where the is NO dataset found which causes the PODA job to abend with an "input not found" message.  These abends are different..We're just not sure why they all of a sudden are happening...It's across different PODA jobs..Anyone have any thoughts?

IDCAMS  SYSTEM SERVICES                                           T
IDC3300I  ERROR OPENING SYSIN                                     
IDC3304I ** JCL STATEMENT MISSING                                 
IDC3207I REMAINDER OF COMMAND INPUT STREAM IGNORED                 
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 16
                        ----  BOTTOM  OF  REPORT  ----             

[Ed_Arnold]

My best guess is a timing problem.  That previously JOB B could be counted on to run after JOB A creates the dataset.

But now JOB B is getting executed too soon.  That's why the re-run is successful.

Ed

[DDP021]

Thanks for the response Ed...From what we're being told, there is a 'temp' directory on the mainframe side that was out of space...They've cleaned it up and we've been running ok ever since...Just have to keep monitoring this directory or set up alerts if its filling up again.