Set TSOCOMMAND to ISPSTART CMD(%exec parms...), or create an exec that has that 
command and set TSOCOMMAND to run it.

The exec in the CMD parm will be "invoked as the first dialog function" when 
ISPF starts. That can be your "TSOSTART" exec.

https://www.ibm.com/docs/en/zos/2.5.0?topic=command-parameters


Also, you don't have to run Edit to check for recovery files, you can do that 
in your own code, with EDREC INIT and EDREC QUERY. But make sure you're in the 
ISR applid!  Every applid has its OWN edit recovery.  (Best practice is to 
ALWAYS switch to ISR before invoking a Browse, View, or Edit service, for 
reasons.)



-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Bob 
Bridges
Sent: Tuesday, October 29, 2024 4:53 PM
To: [email protected]
Subject: TSOCOMMAND

I've been a TSO and ISPF user for decades (since about 1982, I guess; before 
that my employer had Roscoe), and I'm reasonably certain that TSOCOMMAND has 
been available for at least half that time.  But about a week ago I finally got 
around to experimenting with it.

What I've been doing instead is use a REXX I named TSOSTART.  It runs DDALLOC 
to attach my CLIST library to SYSPROC.  Then it runs it again a few times to 
connect other libraries, as needed, to SYSPROC and SYSEXEC.  Last, it runs View 
and Edit without a DSN, just to show me if I have a recovery file I have to pay 
attention to.

I attach the command to run TSOSTART to <Shift-PF1>, so whenever I log on I hit 
that first and then start work.  Works great, or at least I'm used to it.

In Top Secret (I happen to be at a TSS shop currently) one of the TSO 
attributes is named TSOCOMMAND; whatever command string I store there is held 
by TSS and executed at logon.  I assume RACF and ACF2 have the same feature, 
whatever it's called there.  I've been looking at that for years, thinking 
about trying it out, but <Shift-PF1> worked so well, without my having to think 
about it, that I just never got around to it.

But now I'm writing a routine for an internal auditor who has ambitions of 
learning to run it herself instead of asking me to run it every year.  I 
realized that if I made TSOCOMMAND work for me, I could fix up her ID so that 
instead of having to hit an extra PF key when she logged on, it would happen 
for her automatically.  So I finally tried it out.

Well, disappointment:  The DDALLOC part works great, attaching libraries to 
SYSPROC and SYSEXEC.  But View and Edit require ISPF, and the TSOCOMMAND string 
is run before ISPF is up.  So it works for her, but I still have to hit 
<Shift-PF1> in order to check for the recovery files.  Oh, well.

---
Bob Bridges, [email protected], cell 336 382-7313

/* If we aren't supposed to eat animals, why are they made of meat? */

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to