Remember this is a sample directory entry, it can be tailored to look like pretty much anything you like.

The secondary user can or can not be used if you like. The secondary user provides another point of control for the virtual machine to receive messages and issue commands.

The additional CPU is also optional, and if it is not *absolutely* required for the workload I would suggest removing it and changing the numeric value in the MACHINE statement to 1.

Austin, Alyce (CIV) wrote:
Hi again,

When I log on to "client", I get the following message:

LOGON CLIENT
HCPLGN196I Secondary user not in CP directory

I use the client sampdir downloaded from Novell:

USER CLIENT xxxxxxxxx 512M 512M G IPL CMS PARM AUTOCR MACHINE XA 2 CPU 0 ??? CPU 1 ??? CONSOLE 0009 3215 T CONLOG ??? SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A ...

Do I need a secondary user defined and do I need both
CPU statements?

Thanks,
Alyce


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Rich Smrcina
Sent: Thursday, September 25, 2008 9:37 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SLES10 Client

Only for initial installation and adding more packages. For normal operation of your colony, it does not need to be up.

Austin, Alyce (CIV) wrote:
So, the starter systems does need to be up to implement the new
server?
Thanks,
Alyce

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
Behalf Of David Boyes
Sent: Wednesday, September 24, 2008 3:10 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SLES10 Client

OK, then Rich is correct. You're telling it the address of the install
server (where it's going to get the files to install the new server).
The new server will eventually need a unique address of it's own,
though.


--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service:  360-715-2467
rich.smrcina at vmassist.com
http://www.linkedin.com/in/richsmrcina

Catch the WAVV!  http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009

Reply via email to