Thanks, Peter, The reason I didn't include that detail is because I didn't think it was relevant to the question: "Why does ROUTE change the results of "-DB2T,REFRESH,EARLY". This command executes on the same lpar after being ROUTed from a remote lpar. It's surprising to me that simply routing the command causes a different linklst to be used (guessing the old one). But apparently that's what happens. I did something like the following. The log has "wrapped" on our DR system so I can't get to it any more, without reproducing the scenario.
I did this from lpar SYSP, which is remote to SYSD, where DB2 runs at our DR site. While DB2T was up, I issued ROUTE SYSD, SET PROG=JM, with the contents of that member= ****** ********************************* Top of Data *************** 000002 LNKLST DEFINE NAME(LNKLST04) COPYFROM(LNKLST01) 000003 LNKLST ADD NAME(LNKLST04) DSN(DSN910.DB2T.SDSNLINK) 000004 VOLUME(DB2001) AFTER(SYS3.CW.ECC.MLCX880.SLCXLOAD) 000005 LNKLST ACTIVATE NAME(LNKLST04) ****** ******************************** Bottom of Data ************* I followed the above with ROUTE SYSD, SETPROG LNKLST,UPDATE,JOB=DB2T*. I was lucky in that the RUNNING DB2T address spaces were 'active but terminating' at the time I issued UPDATE. Otherwise, there are no address spaces to UPDATE if DB2T is completely down. But this UPDATE only updates the terminating address spaces, right? not the next startup. The next startup should always get the new linklst, but I don't know enough about DB2 to know how ERLY code reacts. (It seems you are saying 'all bets are off') Let me restate that DB2T has to be down when REFRESH, EARLY is issued. So I cannot depend on the subsystem character to route the REFRESH command. This is why I felt it necessary to use ROUTE. Lastly, I issued ROUTE SYSD,-DB2T,REFRESH,EARLY. The results of the REFRESH displayed the old ptf eyecatchers/linklst, until... ...my (also mysitfied) coworker signed on locally to our DB2 lpar and issued the REFRESH. The results then included the new eyecatchers, indicating the new linklist was honored. To verify my observation from the remote lpar, I again issued ROUTE SYSD,-DB2T,REFRESH,EARLY. And again, the output reflected the old ptf eyecatchers. In effect, the two of us were resetting the maintenance each time. Whenever I ROUTED the command from SYSP, it appeared to use the old linklst. So now I feel a bit like a keystone cop telling this story, but this behavior of ROUTE doesn't seem intuitive. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
