On Apr 18, 2007, at 8:04 AM, Mark Jacobs wrote:
We used the KISS solution. We have all our logon procedures for
each system in
its own procedure library. Just put the correct library in the
right JES2
PROC00 concatenation and you should be set.
--
Mark:
When I worked there (where you work) we had written an exit. I had to
modify it once or twice. I believe it was IKJEFLD (its been ages I
know) IIRC you could do it in that exit. I don't believe the exit had
the code in it other than to ignore (IIRC) the proc name. We (IIRC)
only had two TSO Procs one for our NY users and one for the Chicago
users. IIRC the only difference between the two was the sysproc
concatenation. Come to think about we had more than two as we had one
for each department. No one wanted the others sysproc so there was
never an issue about signing on with someone else's proc. Its been a
while but IIRC I think we executed at logon a sysproc member to deal
with this (but I don't honestly remember). One group (I think no
longer belongs to TIME) was rather sophisticated and did a bit of
good allocations.
Ed
----------------------------------------------------------------------
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
