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.
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact