David, I would have to agree with the posters that felt that the best way to handle this would be to use the z/OS UNIX services to read the files. While this does mean that you will need 2 code paths, one for UNIX files and a second one for classic datasets, the advantage of this approach is that you will not need to issue the SVC 99 to build the TIOT entry. Dynamic allocation isn't needed for the UNIX services, since z/OS I/O structures like JFCB's, DEB's, etc aren't required.
Wayne Driscoll Product Developer NOTE: All opinions are strictly my own. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Eisenberg Sent: Thursday, April 10, 2008 3:14 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: TIOT filling up: too many dynamic concatenations >My apologies if this has already been answered but I haven't seen it.< No apologies necessary! The entry that was filling up was actually not MYFILE; that entry remained at 20 bytes. The ever-growing entry seemed to contain all of the history of the concatenated DDs. With each new allocation and concatenation, it grew larger. After reading all of these very informative replies, I think that the best course of action for me will be to modify the application to process one file at a time. It may not be perfect, but it will work, and it will be scalable. Thanks so much! David ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
