Updating a table, even if it is in there as a load module, that happens to be 
in the NUC is one thing.  Replacing a module in the NUC is a whole different 
thing.  I could see loading a replacement module into fixed CSA and changing a 
pointer to it, assuming the address for it is in a system vector or control 
block.  Updating the NUC itself while it is running?  Not happening.

Chris Blaicher
Technical Architect
Mainframe Development
P: 201-930-8234  |  M: 512-627-3803
E: cblaic...@syncsort.com

Syncsort Incorporated
2 Blue Hill Plaza #1563
Pearl River, NY 10965
www.syncsort.com

Data quality leader Trillium Software is now a part of Syncsort.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Edward Gould
Sent: Wednesday, September 13, 2017 3:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Reload nucleus module dynamically

> On Sep 13, 2017, at 12:11 PM, Peter Hunkeler <p...@gmx.ch> wrote:
>
>> What modules do you want to reload? If that is in LPA and/or Linklist, you 
>> better be careful before issuing commands to refresh them. Of course YMMV.
>
>
> Well, the nucleus is the nucleus, LPA is the LPA, and the linklist is the 
> linklist. They are different beasts. The first two are different areas in the 
> virtual address space map, the third is noting but a list of data set to be 
> searched for load modules. The OP asked about dynamically updating the 
> nucleus, and this is nothing that MVS supports up to date.
>
>
> --
> Peter Hunkeler

Peter:
Long time ago and when MVS first came out, we used to do this quite often (once 
a week). A product we had called DUO (DOS under MVS). DUO maintained a table in 
the nucleus for which dos jobs were running. They had a bug in their code that 
would not delete entries. We had to go in and blank out the job names that were 
not running(so as not to have to IPL). We finally got tired of doing this and 
wrote a program that did it.
Worked like a charm. They asked for the program and we were not in a good mood 
so we said no. It took them a year to figure out how to do it.My memory is hazy 
here but I think the degression was “duo” -> went to some company in Dallas? 
and then a year or two later CA bought them out. By then we had gotten rid of 
all the jobs. One of the long time contributors to IBM-Main used to work for 
the company if he hasn’t retired maybe he could speak up?

Ed

>
>


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

________________________________



ATTENTION: -----

The information contained in this message (including any files transmitted with 
this message) may contain proprietary, trade secret or other confidential 
and/or legally privileged information. Any pricing information contained in 
this message or in any files transmitted with this message is always 
confidential and cannot be shared with any third parties without prior written 
approval from Syncsort. This message is intended to be read only by the 
individual or entity to whom it is addressed or by their designee. If the 
reader of this message is not the intended recipient, you are on notice that 
any use, disclosure, copying or distribution of this message, in any form, is 
strictly prohibited. If you have received this message in error, please 
immediately notify the sender and/or Syncsort and destroy all copies of this 
message in your possession, custody or control.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to