Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Execute REXX when starting logging into TSO
- Thread starter SowKan
- Start date
Beware of 'weasel words' (ww)...
Most (ww) installations have a CLIST or EXEC which runs at startup and allocates ISPF assets (among other things). Usually (ww) there is a convention under which a user dataset named in a particular fashion will be attached and often (ww), if that dataset contains a certain-named member, that member will be executed as part of startup. You should ask the others where you work if they know of such a protocol.
If all you get are dumb looks, you will have to do some hacking:
-- find your TSO logon PROC; its name is shown on the ISPF primary panel;
-- look in SYS1.PROCLIB for a member JES2 or JES3. This identifies all the production PROCLIBS. While you're there, see if your logon PROC is in SYS1.PROCLIB. If not, you'll have to search all those PROCLIBs to find it.
-- in the logon PROC, the startup EXEC (if it exists) will be a parm to IKJEFT01 or a command in //SYSTSIN. The EXEC itself is located in //SYSPROC or //SYSEXEC.
Frank Clarke
Tampa Area REXX Programmers' Alliance
REXX Language Assn Listmaster
Most (ww) installations have a CLIST or EXEC which runs at startup and allocates ISPF assets (among other things). Usually (ww) there is a convention under which a user dataset named in a particular fashion will be attached and often (ww), if that dataset contains a certain-named member, that member will be executed as part of startup. You should ask the others where you work if they know of such a protocol.
If all you get are dumb looks, you will have to do some hacking:
-- find your TSO logon PROC; its name is shown on the ISPF primary panel;
-- look in SYS1.PROCLIB for a member JES2 or JES3. This identifies all the production PROCLIBS. While you're there, see if your logon PROC is in SYS1.PROCLIB. If not, you'll have to search all those PROCLIBs to find it.
-- in the logon PROC, the startup EXEC (if it exists) will be a parm to IKJEFT01 or a command in //SYSTSIN. The EXEC itself is located in //SYSPROC or //SYSEXEC.
Frank Clarke
Tampa Area REXX Programmers' Alliance
REXX Language Assn Listmaster
- Status