Thanks for the feedback. We have our module in the linklist. I can test with an 
lla refresh or steplib. I'm going to be closing some loopholes, so if there is 
major pushback, I wanted to be able to quickly change back.

Sent from my iPhone

> On May 2, 2014, at 5:20 PM, Skip Robinson <[email protected]> wrote:
> 
> A TSO/E exit can be localized to a single person or group for testing. Put 
> it in an APF STEPLIB and only folks who have it their logon PROC will run 
> the code. I stumbled on that a long time ago when I took a problem to 
> Level 2 only to discover that I was using some ancient version of it in my 
> STEPLIB. 
> 
> (Assuming that has not changed...)
> 
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler 
> SHARE MVS Program Co-Manager
> 626-302-7535 Office
> 323-715-0595 Mobile
> [email protected]
> 
> 
> 
> From:   Jon Perryman <[email protected]>
> To:     [email protected], 
> Date:   05/02/2014 09:48 AM
> Subject:        Re: Dynamic TSO Submit Exit
> Sent by:        IBM Mainframe Discussion List <[email protected]>
> 
> 
> 
> I opted not to suggest LINKLST. Some companies use LLA refresh for 
> production move process. Others propogate LLA refresh to all system. I 
> suggested using MLPA because it's not a permanent change so an IPL will 
> revert back to the original (if not in real LPA/LINKLST dataset).
> 
> Jon Perryman.
> 
> 
> 
>> ________________________________
>> From: John McKown <[email protected]>
>> 
>> 
>> Our IKJEFF10 (TSO submit exit) exists in LINKLIST. As I recall, in the
>> past, I have simply replaced the module in the proper library and did an 
> F
>> LLA,REFRESH to  start using the new version. Again, IIRC, this exit is
>> invoked by the TMP using a simple LINK (or something like LINK)
>> instruction. It may be necessary to have your TSO users logoff and back
> on
>> to pick up the new copy of the exit.
> 
> ----------------------------------------------------------------------
> 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

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

Reply via email to