Joe, I think the RCLACTGRP each time would hurt the performance. I think it may be better to define the file as USROPN and have Program #2 only open the first time the program #2 is called. Dave
Joe, I think the RCLACTGRP each time would hurt the performance. I think it may be better to define the file as USROPN and have Program #2 only open the first time the program #2 is called. Dave
Dave, Thanks for your response. The problem seems to be that the IBM supplied service program is the culprit adding ODPs to the job. I do have any control over that program. I am not too worried about performance because this is a one shot load. If I cannot overcome this problem, I will have to break the run into 20-30 smaller runs - so I would gladly sacrifice a little time to keep from having to go that route. Thanks, Joe
I have a program (#1) that calls a program (#2) that uses a service program (an IBM supplied service program) that uses a named activation group. When you display the job, the open file list grows everytime program #2 is called (the files are in the named activation group). I am trying to do a one shot process of several hundred thousand records and I believe this is causing me some problems (too many files open). Does this sound reasonable? If so, would it be safe to issue a RCLACTGRP after each call to program #2? What would I need to consider or check before attempting this? Thanks, Joe
Joe, Is the IBM service program performing any embedded SQL? That situation reminds me of Embedded SQL programs that are configured to close their cursors when the activation group ends, rather than when the module ends. I think you are probably stuck doing a RCLACTGRP unless you can find a way to make the service program do what you want with some other arguments or functions calls. Good luck! Kevin