I should have added, this was available in DB2 V910 Lizette
-----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Tuesday, August 06, 2013 6:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: MVS ROUTE command is a bad influence on DB2 ERLY code Barbara - Yes, DB2 has added a refresh command in DB2 for Erly Code. No longer need an IPL to install. he DB2R command -REFRESH DB2,EARLY reloads the EARLY code modules that were loaded at IPL time, and rebuilds the EARLY control block. Executing the -REFRESH DB2,EARLY command is an alternative to IPLing z/OS for activating maintenance to EARLY code after you apply that maintenance to the prefix. SDSNLINK data set. When -REFRESH DB2,EARLY is run, previous copies of the EARLY modules are deleted from the system the next time that DB2 is started. This command is only valid when DB2 is inactive. Important: If prefix. SDSNLINK is LLA-managed, you must perform an LLA refresh after you apply EARLY code maintenance, and before you issue the -REFRESH DB2,EARLY command. You can perform an LLA refresh by issuing the z/OS command MODIFY LLA,REFRESH. Abbreviation: -REF DB2 Environment This command can be issued only from a z/OSR console. In a non-data-sharing environment, the command must be issued on individual subsystems. In a data sharing environment, the command must be issued on individual members of a data sharing group. The name of the DB2 subsystem is determined by the command prefix. For example, -START indicates that the DB2 subsystem to be started is the one with '-' as the command prefix The command is rejected if the DB2 subsystem is already active. The EARLY code can be properly updated only when DB2 is not active. Applications that use documented DB2 interfaces do not need to be stopped before issuing the REFRESH DB2,EARLY command Scope of the -REFRESH command: The -REFRESH command has member-only scope, and must be executed for every instance where a unique recognition character for the -START command is defined. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of nitz-...@gmx.net Sent: Monday, August 05, 2013 10:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: MVS ROUTE command is a bad influence on DB2 ERLY code > The command char is registered with the subsystem definition - I > suspect (but don't know) that when you look at the OPDATA between the 2 systems (run the command on each ) you will see a difference. > > Why Route gets involved is each system is processing the command > according to what is defined on the system that the command executes > on. More than that I don't know The way I remember it: For each command typed in, first of all an IEEsomething module gets control whose function it is to determine who should be notified to actually attach the command processor for that specific command. That IEEsomething would know to attach the VARY ucb command processor in master address space, for instance, or the control commands in console address space or wake up the address space that is addressed by a modify command. It has a list of known (system) commands. If the first thing in the typed-in string is what is recognized as a command prefix, IEEsomething would know to address the address space that established the command prefix. Now, a ROUTE command is one of many system commands known to IEEsomething. IIRC, it gets attached in console address space and all it does is send over the command string (minus the ROUTE systemname) to the system addressed in that command string. On the target system, there is also an IEEsomething runnning. It gets the command and does the same deliberation (whom to send it to), just on the other system. What I am fuzzy about is what happens when a command prefix is established (like in the DB2 case) but the actual DB2 system to execute it is down. I thought there would be an error message that the command cannot get executed. On the other hand, I was told that ERLY code can only be established via an IPL, NOT afterwards. The DB2 admins in my last installation were adamant about that. Has that changed? Barbara Nitz ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
