|
Actually, *CALLER is much more likely to exhibit problems than a named activation group is.
My guess (well, stab in the dark, really) as to what your problem is... You're running a servie program in *CALLER and calling it from the default activation group. Somewhere along the line, a program is doing a RCLRSC command, and since RCLRSC doesn't understand service programs, it's closing the files, but keeping the service program itself in memory. When it's used again, the srvpgm is horribly confused because nothing notified it that the files were going to be closed.
--- Scott Klement http://www.scottklement.com On Tue, 6 Jun 2006, Eric Wolf wrote:
Eric, For one of the programs, I am using a named activation group. For the modules that seem to be having the problem (which are in the service program), I am using *CALLER with a Shared AG(*NO). I was thinking along the same lines that maybe somewhere a RCLACTGRP was being called but I not using that command anywhere. We are running MAPICS ERP software which (primarily) is not written in ILE. I was thinking of changing the one program from the named AG to *CALLER. Eric
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
