RE: QSH and PASE

Vern,

Thanks for that.  This is helping to explain some strange behaviors when
using the PASE version of TSM.  To communicate with the running program
you use QP2TERM.  I was thinking like a 5250 screen where you call jobs
etc.  However it is different.  A better example for us traditionalists is
that it's like using messages, data queues, whatever to communicate with a
currently running program.  My problem was trying to figure out how to
shut down TSM under PASE in an orderly fashion, yet do it at night,
unattended.  IBM can figure out how to start it unattended, but not how to
stop it (at least in an orderly fashion).  Keeping in mind that they avoid
DB2 like the plague, therefore a frown can corrupt this data and require a
drastic restore.

Rob Berendt
--

Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/12/2003 02:42 PM
Please respond to Midrange Systems Technical Discussion

        To:     Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
        cc:
        Fax to:
        Subject:        RE: QSH and PASE

OS/400 PASE Callable Program APIs

The callable program APIs run an OS/400 PASE program. They are:

- Run an OS/400 PASE Shell Program (QP2SHELL and QP2SHELL2) runs an OS/400

PASE program in the job that calls the API.

- Run an OS/400 PASE Terminal Session (QP2TERM) runs an interactive
terminal session that communicates with an OS/400 PASE program (defaulting

to the Korn shell) running in a batch job.

Nothing to do with QShell. Apparently it's possible to call QShell stuff
from PASE, as well as CL programs. Yikes, what a tangled system we have
now, eh?

HTH

Vern

At 02:18 PM 3/12/2003 -0500, you wrote:
>Is it?  Or is QP2TERM primarily used by TSM to set up some environment
>variables prior to running STRQSH?
>
>Rob Berendt