Andrew,
Instead of coding the exit, how about this:
In a shop I once worked for a few years ago, I used to put saved TSO Logon
Messages into the BRODCAST dataset to indicate the system you logged on to,
e.g., (now this is an old example ...)
se ' z/OS 11 44 ',save
se ' 111 4 4 ',save
se ' 11 4 4 ',save
se ' 11 :: 444444 ',save
se ' 111111 :: 4 ',save
se 'Welcome to the z/OS v1.4 Production system on CPU1 ',save
se '*************************************************************',save
To put the messages into BRODCAST, the above commands were executed as
subcommands under OPER within a simple Clist. This needed to be run once on
every LPAR whenever the text needed to change. My Test LPAR had a different
set of messages.
Or perhaps you can use a common Clist or REXX Exec which is executed from
the PARM='...' parameter of every Logon proc. Inside this Exec, you can use
system symbols and other variables to determine the system / LPAR this is
running on and write an appropriate bunch of logon messages. For example:
sysproc = sysvar('sysproc')
sysid = mvsvar('sysname')
say " |\/\/\/| "
say " | | "
say " |_ | "
say " | (o)(o) "
say " C _) "
say " | ,___| " sysid "at your service."
say " | / " "You are logged on using proc " sysproc
say " /____\ "
say "/ \ "
Regards,
Ulrich Krueger
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
