Hi Peter,
I think Neale Ferguson has good advice for you on your earlier question.
If you have your OPERATOR userid logged on automatically during system
startup, and don't logoff, you don't risk having some other Class A user
picked as "operator". If I had to maintain a system, I would want the
OPERATOR console online near a computer operator or system administrator
who could respond to system messages.
It also sounds like your user is running with "TERM MODE CP" (the "CP QUERY
TERM" command shows you the current attributes). You can fix that with the
command:
CP TERM MODE VM
You can put this in a PROFILE EXEC on the users 191 disk. Here is a
trivial example of a REXX language PROFILE EXEC:
/* User profile (Line 1 of a REXX exec has to be a comment line) */
'CP TERM MODE VM'
Exit 0
Finally... You have three OSA cards, with device addresses starting with
F800, FC00, and FD00. It sounds like you have already defined one host
interface on each card and attached it to your primary VM stack (user
TCPIP). Unlike the typical PC network card, your OSA Express card can
support lots of host interfaces. CP cannot attach F800-F802 to a VSWITCH
at the same time you are using it for TCPIP, but you can define another set
of 3 devices (e.g. F803-F805) and assign F803 to your VSWITCH. When the
VSWITCH is active, CP QUERY OSA will show these additional OSA devices
attached to your controller (VSWCTRL1).
Do not try to attach OSA devices to VSWCTRL1 yourself. Let CP do that
based on your VSWITCH definition.
Do not try to define DEVICE and LINK statements for the VSWITCH in your
controller (VSWCTRL1). Let the controller create the necessary definitions
dynamically.
Regards,
Dennis
----------------------------------------------------------------
Dennis Musselwhite ([EMAIL PROTECTED]) +1(607)429-3831
z/VM Development -- CP Network Simulation -- IBM Endicott NY
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
