That's what I'm thinking is that even though the CL is an OPM CL program, when it gets called and exits, the PASE environment is still running because it was called from within an ILE caller ?
Yikes. Activation groups can be fun :-)
Ultimately the end pase thing works, but would be fun to understand the consistency thing :-)
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
date: Thu, 26 Jun 2014 11:01:05 -0400
from: Michael Ryan <michaelrtr@xxxxxxxxx>
subject: Re: Calling and Ending Pase Environment from a CL Program
When Called via ILE
I wonder is PASE is ending with the activation group?
On Thu, Jun 26, 2014 at 10:56 AM, Richard Schoen <richard@xxxxxxxxxxxxxxx>
I have an interesting one.
We have a CL command that calls an OPM CLP that then calls a pase shell
command via a call to QP2TERM.
This seems to work fine if run multiple times concurrently from a CL
process and the PASE session seems to end fine which is what I expect to
Customer has written an RPG APP where they are building and calling the CL
command concurrently from within an RPG ILE subprocedure.
On the first call the command returns fine, but subsequent calls tell them
that PASE is already active.
If they call QP2EndPase from the RPG before calling our API then things
Does anyone have an idea why the Pase environment would stay active in
this scenario ?
I'm guessing the Qp2EndPase method was made available for a reason :)
Any thoughts welcome.