Keyboard Shortcuts
Likes
Search
Managing Host ID on VM370CE
Hi again Folks.
I've been quite successfuly playing with RSCS and XNET on a small set of 'networked' VM370CE instances, but there's a thing that I had let aside from the start that is really annoying me and I feel (maybe because I'm a Linux guy) that I must have to deal with once and for all: Proper identification of the running instances. I don't expect it to be trivial (as usual :-P) but certainly something worth of learning how to. The first and more evident issue on having systems just 'as is' is that, on 3270 terminals, all terminals do show the same 'VM370CE' string down right... this very very annoying. The second one is the eventual use of an ID when using using RSCS. I think it is for the NJE capable version of RSCS (I haven't needed it so far in my labs) but worth digging a little about it. So far, my investigations point me to understand that there's no unique (/etc/hostname equivalent) ID setting (which is no problem) and at least two distinct terms appeared to dig in:? SYSID and NetID. - Regarding SYSID My investigation ends as I'm unable to find HRC108DK MEMO or anything related. I also read that SYSID wasn't part of the original VM/370 and trying to find anything about it on IBM books is futile, as it is a kind of addon that came from Sixpack. Could someone give me some clue? ...I'm sure this can be done! - Regarding NetID This one was initially easier, as I came across a very suspicious file named SYSTEM NETID S2 sitting on one of the Maint disks. The contents remind me as a kind of 'hosts' file with three columns CPUiD NodeID and NetID ... not one, but three IDs! This file, but, sits on what I think is a system disk, R/O, and I bet a certain kind of procedure has to be followed to modify it. Could any one point me on where could I further investigate on this? Thank you very much in advance. Cheers! ?? |
The main IBM documentation?for VM/370 Release 6 is here:? The process and procedures for modifying VM are on the Service disk: MAINT 5E5. When you logon to MAINT, the Service disk (5E5) is accessed at filemode B. The MAINT MEMO file on that disk describes the general method of maintaining or modifying the VM system disks. The DMKSYS ASSEMBLE file contains the SYSID MACRO, which?is where you supply?the System Name you choose for your VM/370 system. Bob Bolch On Thu, Aug 24, 2023 at 5:55?AM Alejandro olivan Alvarez <alejandro.olivan.alvarez@...> wrote: Hi again Folks. |
Hi again.
OK... Thanks Bob, I managed to tweak SYSID :-) ... I recall the MAINT MEMO since I learn how to tweak DMKRIO, so it turned out to be exactly the same procedure. I still have not found the documentation on that particular macro, but just by trial error I fugured that it's limited to 8 chars (but surprisingly accepts chars such as '/' and '-') ... but I'll like to learn more about what DEFAULT= means there and overall whats beyond all that. OTOH, For NetID, which at first glance appeared to be the easy one to have it tweaked, it turns out that I quickly managed to get the system screwed (it wasn't that hard! :-P). I tried accesing the S disk in write mode on another letter, edit SYSTEM NETID, and then re-ipl 190... but a message appeared about virtual machine size beig too small for a non-shared cms (or something like that) and the VM wen to CP. From that point, CMS fails to IPL any more, going back to CP telling 'program interrupt loop'... So clearly there must be some kind of procedure to achieve this.? What is the right wat to apply changes to that file at disk S? or where could I read about how to handle the need for such changes? Cheers! |
开云体育I think you have missed one thing. The whole point of the CPUID? in the SYSTEM NETID is that you can have the same VM IPLd on multiple different hardware systems. The IDENTIFY command then matches the CPU serial number to that of the processor and reports i Dave ? From: [email protected] <[email protected]> On Behalf Of Alejandro olivan Alvarez
Sent: Thursday, August 24, 2023 4:37 PM To: [email protected] Subject: Re: [h390-vm] Managing Host ID on VM370CE ? Hi again. |
toggle quoted message
Show quoted text
On Aug 24, 2023, at 11:36 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. |
开云体育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:
|
开云体育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.
|
The RSCS IDs on VMCE are there for future use. There is no code on the current VMCE release which uses them. Bob Bolch On Fri, Aug 25, 2023, 6:55 AM Matthew T. Kromer <zerohero0h@...> wrote:
|
On Thu, Aug 24, 2023 at 11:29 AM, Dave Wade wrote:
Are there limitations on the SYSTEM or NET ID? Like Alphanumeric only? Or are some special characters allowed? I realize I might be a special character that's not allowed ;-) ?... Mark S. |
I found this thread from earlier in the year, so hope it is not too old to resurrect.
I am also trying to update my SYSTEM NETID file on S. When I access the disk D (RW) and make the updates, then follow these commands, the file does not update: DEF STOR 16M IPL 190 SAVESYS CMS However, after IPL, it is still here on the D drive (which is S R/W). Help please! |