On Tue, 13 Aug 2013 19:17:49 -0400, Peter Relson <[email protected]> wrote:
>Route does little more than send the command to another system. On that >system that command may be processed by some number of system address >spaces (such as master, consoles). Each will use whatever its lnklst is. > >I don't know by what mechanism DB2 sees commands. "-DB2T,REFRESH,EARLY" is >not shorthand for a modify command (right?), so the command is routed to >the SSI (from the system address space) and will run with the lnklst of >that space. > >So if you're seeing something "old", then that space has not run with an >updated LNKLST. And indeed you showed that the LNKLST UPDATE was done only >for the DB2 spaces. The LNKLST UPDATE was done only for the DB2 spaces, Peter, but there is one difference. We don't quite have all the info, but I'm going to make a guess that the OP is using SDSF to issue the commands, as he mentioned that his TSO logon was using the new LNKLST, too. If a TSO user issues an SVC 34 to issue the command "-DB2T,REFRESH,EARLY", and it's picked up by the SSI, which space does it execute in? You said "the command is routed to the SSI (from the system address space)" but did you assume there that the command was issued from an MCS console, and thus processed in the CONSOLE system address space? What happens when the command is issued in a TSO session? Since the TSO session was using the new LNKLST we seem to have some evidence that the command ran in the TSO session when executed directly, vs running in the CONSOLE address space (with the old LNKLST) when executed via ROUTE from the other system. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
