|
It looks like I bit myself in the b__t again with the activation group. In one test, I changed the activation group from *CALLER to QILE on the program using the service program procedures and it worked.
That would make sense if there's a RCLRSC command running somewhere in the job. You should always make sure that RCLRSC is never run against a service program.
RCLRSC only affects the default activation group, so changing the srvpgm from *CALLER to QILE may have stopped RCLRSC from having an effect on your srvpgm.
I then recreated the service program to use the QILE activation group and, so far, no errors. I know I probably should not be using this group but I am trying to get out of my current situation until I can rebuild it in different AG.
There's no real disadvantage to QILE, other than the fact that lots of software uses it because it's the default. The only dangerous aspect is that if you reclaim it, you might accidentally reclaim a 3rd party program. That's why I recommend that you make up your own named AG, and use that...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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
