Whaddya mean "What about SYSTEM NETID ?"
Yes, use the same procedure to replace SYSTEM NETID as mode 2 if that's
what you are asking about. The same for the SYSTEM SEGID. Neither of them
go into the INSTSEG, so don't worry about that.
If you are wondering what it's used for, it's used by the CMS IDENTIFY
command as well as NOTE and SENDFILE. It associates your cpuid with your
node name and the userid of the RSCS machine.
Jim
At 12:36 PM 5/26/2006, you wrote:
This is a multipart message in MIME format.
--=_alternative 005B3F3A0525717A_=
Content-Type: text/plain; charset="us-ascii"
What about SYSTEM NETID ?
Rob van der Heij <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System <[email protected]>
05/26/2006 10:00 AM
Please respond to The IBM z/VM Operating System
To: [email protected]
cc:
Subject: Re: z/VM 5.2 and the S disk
On 5/26/06, Jim Bohnsack <[EMAIL PROTECTED]> wrote:
> Steve--I'm not on 5.2 yet, but the procedure that I've used for many
years
> is to save the execs or whatever you need on the 190 disk as filemode
> 2. That's important. Then using the SAMPNSS EXEC that typically is
> shipped on the MAINT 493 disk, create a new NSS (Named Saved System)
> skeleton by entering "SAMPNSS CMS". At that point, having remembered to
> relink 190 as RR, enter "I 190 CLEAR PARM SAVESYS CMS". That will write
> out the directory information for 190 and 19E in the new CMS NSS. When
you
> IPL CMS, you'll be seeing the new execs.
You need to rebuild the CMS nucleus because the directory of the
S-disk is part of the nucleus. But you also need to be aware of
INSTSEG that holds copies of S-disk programs in storage. If you would
modify one of the programs on the S-disk it would not work. So to make
such changes you would need to log a local mod to the file, build it,
rebuild INSTSEG, etc.
Rob
--
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/
--=_alternative 005B3F3A0525717A_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">What about SYSTEM NETID
?</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Rob van der Heij
<[EMAIL PROTECTED]></b></font>
<br><font size=1 face="sans-serif">Sent by: The IBM z/VM Operating System
<[email protected]></font>
<p><font size=1 face="sans-serif">05/26/2006 10:00 AM</font>
<br><font size=1 face="sans-serif">Please respond to The IBM z/VM
Operating System</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
[email protected]</font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
Re: z/VM 5.2 and the S disk</font></table>
<br>
<br>
<br><font size=2 face="Courier New">On 5/26/06, Jim Bohnsack
<[EMAIL PROTECTED]> wrote:<br>
<br>
> Steve--I'm not on 5.2 yet, but the procedure that I've used for many
years<br>
> is to save the execs or whatever you need on the 190 disk as filemode<br>
> 2. That's important. Then using the SAMPNSS EXEC that
typically is<br>
> shipped on the MAINT 493 disk, create a new NSS (Named Saved System)<br>
> skeleton by entering "SAMPNSS CMS". At that point,
having remembered to<br>
> relink 190 as RR, enter "I 190 CLEAR PARM SAVESYS CMS".
That will write<br>
> out the directory information for 190 and 19E in the new CMS NSS.
When you<br>
> IPL CMS, you'll be seeing the new execs.<br>
<br>
You need to rebuild the CMS nucleus because the directory of the<br>
S-disk is part of the nucleus. But you also need to be aware of<br>
INSTSEG that holds copies of S-disk programs in storage. If you would<br>
modify one of the programs on the S-disk it would not work. So to make<br>
such changes you would need to log a local mod to the file, build it,<br>
rebuild INSTSEG, etc.<br>
<br>
Rob<br>
-- <br>
Rob van der Heij<br>
Velocity Software, Inc<br>
http://velocitysoftware.com/<br>
</font>
<br>
<br>
--=_alternative 005B3F3A0525717A_=--
Jim Bohnsack
Cornell Univ.
(607) 255-1760
