Thanks for all the hints everyone. I went thru the scenario again several times, and found that updating the CONSOLE address space after changing the linklist causes ROUTED commands to work correctly. It appears ROUTED commands arrive on the local system as issued by the CONSOLE address space, while locally issued commands issued by a TSO user appear to recognize that LLA has a 'new' linklst.
I verified this by issuing the command, "D PROG,LNKLIST,USERS,NAME=CURRENT" and noting there were only 2 users of the 'new' linklst: LLA, & my tsoid. As soon as I updated the CONSOLE address space with, "RO SYSD,SETPROG LNKLST,UPDATE,JOBNAME=CONSOLE", the ROUTED command recognized the new linklst. Bottom line, after creating a new linklist: RO SYSD,SETPROG LNKLST,UPDATE,JOBNAME=DB2T* -- Bad idea. Doesn't refresh ROUTED commands. Whereas: RO SYSD,SETPROG LNKLST,UPDATE,JOBNAME=* -- does. It includes CONSOLE. Thanks Peter, for pointing me in the right direction. -Jim (way too much time on my hands) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
