Thread View: comp.lang.rexx
5 messages
5 total messages
Started by Jim Van Sickle
Mon, 08 Sep 1997 00:00
Was ISPSTRT used to start an app?
Author: Jim Van Sickle
Date: Mon, 08 Sep 1997 00:00
Date: Mon, 08 Sep 1997 00:00
32 lines
1754 bytes
1754 bytes
Greetings...
I'd like to be able to tell from within an exec if it was started with ISPSTRT.
I like to run commands using the syntax 'TSO command-name', but would like to be
able to control how execs behave from within themselves, in other words, have
the exec check to see if it was started with ISPSTRT or from the command line.
If it was not started with ISPSTRT, I'd like the exec to start *itself* in
another session with ISPSTRT. The alternative is to either (a) replace the exec
itself with a stub that starts the real exec with ISPSTRT, or (b) have the exec
pass a parameter to itself that'll tell it how it was started (not the best
solution). Ideally the exec would have a test in the very beginning such as:
if \started_with_ispstrt /* but how do I know? */
then do
"ISPEXEC SELECT PGM(ISPSTRT) PARM(CMD(myself)...."
exit
end
rest of logic here...
Any ideas?
TIA :-)
--
***********************************************
* Jim Van Sickle <mailto:jim.vs@ibm.net> *
* Manager, Operations and Tech Support *
* United Retail, Inc. *
*---------------------------------------------*
* visit my meager web site at: *
* <http://mypage.ihost.com/jimswebsite/> *
***********************************************
Re: Was ISPSTRT used to start an app?
Author: Frank Clarke
Date: Mon, 08 Sep 1997 00:00
Date: Mon, 08 Sep 1997 00:00
24 lines
1324 bytes
1324 bytes
Jim Van Sickle <jim.vs@ibm.net> wrote:
>Greetings...
>I'd like to be able to tell from within an exec if it was started with ISPSTRT.
>I like to run commands using the syntax 'TSO command-name'...
> Ideally the exec would have a test in the very beginning such as:
>if \started_with_ispstrt /* but how do I know? */
> then do
> "ISPEXEC SELECT PGM(ISPSTRT) PARM(CMD(myself)...."
> exit
> end
....
if Sysvar("SYSISPF") <> "ACTIVE then do
address TSO "ISPSTART ......." "RESTARTED"
exit
end
/* Later, you will want to know if you were 'restarted' so that you
can... */
if sw.0restarted then exit(4) /* bypass normal exit screen */
return
Re: Was ISPSTRT used to start an app?
Author: Frank Clarke
Date: Mon, 08 Sep 1997 00:00
Date: Mon, 08 Sep 1997 00:00
8 lines
838 bytes
838 bytes
Jim Van Sickle <jim.vs@ibm.net> wrote: >Greetings... >I'd like to be able to tell from within an exec if it was started with ISPSTRT. >I like to run commands using the syntax 'TSO command-name'.... (answered on ispf-l.)
Re: Was ISPSTRT used to start an app?
Author: Doug Nadel
Date: Mon, 08 Sep 1997 00:00
Date: Mon, 08 Sep 1997 00:00
34 lines
2004 bytes
2004 bytes
I don't think there is a documented way to determine this. ISPSTRT starts a new screen, but I don't know of any way to find out how the current screen was originally started. You might be able to play some games with setting variables in the shared pool to keep a history of screen numbers in use by the command, but I'm not sure if that'd work. -Doug Jim Van Sickle <jim.vs@ibm.net> wrote: >Greetings... >I'd like to be able to tell from within an exec if it was started with ISPSTRT. >I like to run commands using the syntax 'TSO command-name', but would like to be >able to control how execs behave from within themselves, in other words, have >the exec check to see if it was started with ISPSTRT or from the command line. >If it was not started with ISPSTRT, I'd like the exec to start *itself* in >another session with ISPSTRT. The alternative is to either (a) replace the exec >itself with a stub that starts the real exec with ISPSTRT, or (b) have the exec >pass a parameter to itself that'll tell it how it was started (not the best >solution). Ideally the exec would have a test in the very beginning such as: > >if \started_with_ispstrt /* but how do I know? */ > then do > "ISPEXEC SELECT PGM(ISPSTRT) PARM(CMD(myself)...." > exit > end > >rest of logic here... > >Any ideas? >TIA :-)
Re: Was ISPSTRT used to start an app?
Author: Marc Santiago
Date: Wed, 10 Sep 1997 00:00
Date: Wed, 10 Sep 1997 00:00
57 lines
2430 bytes
2430 bytes
Forgive my ignorance, but what is ISPSTRT? Is it the exec for ISPF? You might try the SYSVAR function to pull up info about how the exec was called. For example, SYSVAR(sysicmd) - Name used to implicitly invoke the EXEC, or a null string SYSVAR(sysnest) - YES or NO. Is this exec running nested? SYSVAR(sysscmd) - Null if the TSO EXEC command was used. EXEC if the exec was run from tSO EDIT. Hope this helps some... -Skee Please note that Jim Van Sickle <jim.vs@ibm.net> wrote in article <341441E4.3B0B03DE@ibm.net>... > Greetings... > I'd like to be able to tell from within an exec if it was started with ISPSTRT. > I like to run commands using the syntax 'TSO command-name', but would like to be > able to control how execs behave from within themselves, in other words, have > the exec check to see if it was started with ISPSTRT or from the command line. > If it was not started with ISPSTRT, I'd like the exec to start *itself* in > another session with ISPSTRT. The alternative is to either (a) replace the exec > itself with a stub that starts the real exec with ISPSTRT, or (b) have the exec > pass a parameter to itself that'll tell it how it was started (not the best > solution). Ideally the exec would have a test in the very beginning such as: > > if \started_with_ispstrt /* but how do I know? */ > then do > "ISPEXEC SELECT PGM(ISPSTRT) PARM(CMD(myself)...." > exit > end > > rest of logic here... > > Any ideas? > TIA :-) > -- > *********************************************** > * Jim Van Sickle <mailto:jim.vs@ibm.net> * > * Manager, Operations and Tech Support * > * United Retail, Inc. * > *---------------------------------------------* > * visit my meager web site at: * > * <http://mypage.ihost.com/jimswebsite/> * > *********************************************** >
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads