Hello. A few days ago we started to get the following error in a JCL in Production:
Code:
IEF240I XXXX0115 PASO005 - TASK I/O TABLE EXCEEDS TIOT LIMIT OF 0032K
IEF272I XXXX0115 PASO005 - STEP WAS NOT EXECUTED.
When we looked into the docs, it said that the TIOT table is used for allocation of all Static and dynamic DD files used in the Job. This particular job has a lot of Input and output files, and one of the steps is dynamic, and process all the files that many apps has left us in a master file with names. It is created after reading an input file which has all the file names that has to be processed by that step. Accounting files with accounting records for each app in the organization.
The step that fails processes in a sort step, 200, 190, 210, it varies, input files and sort/merges them in a single file for the rest of the job to process.
We were told that this parm is changed in a sys1 library, but it requires an IPL in order to be taken the changes, however, they requested us that in the meantime, we used on each file on that step the following parm:
Code:
UNIT=(3390,64)
According to our Admin, that parm supposedly assigns 64Kb of allocation for that TIOT table for that job, however, I'm not so convinced about it.
This particular job has 30 steps in total, and quite a few files used on all that steps, so if that parm does what they say it does (allocate each file on a 3390 disk, and assign 64 Kb of memory allocation space), just by adding it to each file on that step would be enough, or should I add it to each file in the job?
I suposse he really hasn't really looked into the documentation Enrico.
We did in the mean time exactly what Expat suggested, split the JCL in several other jobs. We are testing them before uploading them today to the production site. I guess This will end as one of many cases like "Although is a technical problem, Software development should take care of it", just becouse they don't wanna do nothing at all *sighs*. What angers me is that they don't care that it has an impact in some functionalities of our application
