¿ªÔÆÌåÓý

Re: Managing Host ID on VM370CE


 

¿ªÔÆÌåÓý

Matthew,

You are correct the CPU serial isn¡¯t critical, and is only used in couple of places in VM/CMS. In fact in the base VM/370R6 I don¡¯t believe anything uses it.

There are modifications in VM370CE which use it. One adds a SYSID macro to DMKSYS which allows you to specify multiple CPU serial numbers and system name pairs.

There are then further modifications to examine this data and include it in banner pages and the bottom right of 3270 sessions.

The SYSTEM NETID file does a similar job for CMS. The IDENTIFY command uses the CPU ID? to identify which line in this file applies and then reports system name and the ID of the RSCS virtual machine.

?

On VM/SP its used by SENDFILE but I don¡¯t think we have SENDFILE on CE.

I assume its in two places because CP does not have access to, or even know, which disk CMS is going to use as the S-Disk.

?

Dave

?

?

From: [email protected] <[email protected]> On Behalf Of Matthew T. Kromer
Sent: Friday, August 25, 2023 11:55 AM
To: [email protected]
Subject: Re: [h390-vm] Managing Host ID on VM370CE

?

I¡¯m pretty sure, albeit going from memory, that SYSTEM NETID is used primarily by the NAMES module and very little inside CP or CMS actually cares about the CPUID. ?I don¡¯t remember what tells CP what to display in its host name fields, it may have been in DMKSYS, but it¡¯s probably been since 1992 that I last generated a VM SP nucleus. With ESA it was set in the system config.

?

While I¡¯d enjoy having a VM SP 5 system image, I don¡¯t have one and I haven¡¯t used CE that much to refresh my memory on the SP build process¡­ ? Melinda Varians cookbook has everything in it.



On Aug 25, 2023, at 5:19 AM, Alejandro olivan Alvarez <alejandro.olivan.alvarez@...> wrote:

?Thanks to all! :-)

- By one side, just in case someone google for this later, I confirm, that as pointed above, the following procedure does the trick!

DEF STOR 16M
IPL 190
SAVESYS CMS

- And in the other side, I just noticed the point on the CPU serial number on hercules config... so I changed it (never did before) and noticed the Q CPUID command yelds the number now.
I matched that number in DMKSYS ASSEMBLE but I'm not sure on the eventual consequences on such change in other parts of the system (I've learnt to not asume anything based on my experince on 'normal' computers), and/or conversly what could go wrong if someone just changes the CPU serial in hercules config but not DMKSYS ASSEMBLE (apparently, it all just works).

I have still to figure out what NetID/NodeID refer to with absolute certainty... my understanding (which I know I can't trust under Mainframe environment) suggests me that, given an scenario where multiple insntances of RSCS Virtual machines (I see we've RSCS, RSCS1 and RSCSTST on USER DIRECT) are simultaneously running on this system, NetID could be a way to provide a distinct NodeID for each network this host is connected to... but not really sure.

Join [email protected] to automatically receive all group messages.