Title: RE: SYSTEM NETID and CPUIDs

What might be a nice default (this would have been great for me when I worked in a lab with 20+ VM images that were constantly moving to different processors) would be to be able to set the RSCS default id based upon the SYSTEM_ID. That way no matter where I IPL'd my abcVM'x01' system I would get RSCS'x01' as the RSCS id. Ofcourse I'd want to be able to set and over ride the default. Maybe put the default in the SYSTEM CONFIG and the over ride in the SYSTEM NETID?

Tom   

-----Original Message-----
From: David Boyes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 22, 2006 3:03 PM
To: [email protected]
Subject: Re: SYSTEM NETID and CPUIDs


> I already posed the design point that it would default to AT
> <system_id> VIA RSCS.  IDENTIFY already defaults to AT
> <system_id> VIA *.
>
> Is it sufficient to just change the default to VIA RSCS and
> still require the use of SYSTEM NETID if you want something
> else?

Works for me. That would fix PPS and LPR, and would be a Reasonable
Default (minimum surprise factor - IMHO).

> Do I really *need* SET commands to change these puppies?

I'd say not. The RSCSid field is not something you change unless you
know why you're making the change, and if you need to change it, you
know why (and you've already suffered through changing GCS and a few
other painful experiences). If you added a RSCS test id (lets say
RSCSTEST) to the default GCS configuration, that would remove almost all
the reasons to ever change SYSTEM NETID (if you make the proposed change
to default the RSCSid field to RSCS).

You do need to put the instructions back in the CP planning and admin
manual on *how* to change SYSTEM NETID, though. It's an integral part of
getting the system configured, even for a system that's only going to
support Linux -- at some point, you're gonna need to print something
from CMS, and odds are, that will be on a networked LAN printer, not a
channel-attached device.

It's also probably time to move PPS EXEC to MAINT 190, but that's a
different discussion.

-- db


__________________________________________________________________
<< ella for Spam Control >> has removed VSE-List messages and set aside VM-List for me
You can use it too - and it's FREE!  http://www.ellaforspam.com

Reply via email to