Re: How to determine SYSRES

2010-11-04 Thread Heinz-Josef Glaser
try to locate the CP-Dasds with

Q ALLOC MAP

You will see the VOLIDs and RDEVs from all CP-Dasds then.

Mit freundlichen Grüssen / Best regards
Heinz-Josef Glaser
Systemspezialist z/OS, z/VM, z/VSE
Global Technology Services
GE Server Services SPL8 Manag Serv Sys Z
IBM Deutschland
Rathausstrasse 7
09111 Chemnitz
Tel.: +49 371 6978 2876
Fax: +49 371 6978 2280
Mobile: +49 172 668 3018
E-Mail: hjgla...@de.ibm.com

IBM Deutschland Infrastructure Technology Services GmbH
Geschäftsführung: Ulrike Hetzel
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,
HRB 727973



From:   Mike Walter mike.wal...@hewitt.com
To: IBMVM@LISTSERV.UARK.EDU
Date:   27.09.10 19:27
Subject:Re: How to determine SYSRES
Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU



I guess you can match that up to the CPOWNED list to get the real CCUU,
since it is listed only as Volume Serial Number:

Or, simply: CP QUERY DASD volser

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.



Frank M. Ramaekers framaek...@ailife.com

Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
09/27/2010 12:20 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: How to determine SYSRES






I guess you can match that up to the CPOWNED list to get the real CCUU,
since it is listed only as Volume Serial Number:

Module CPLOAD was loaded from minidisk on volume 540RES at cylinder 39.
Parm disk number 1 is on volume 540RES, cylinders 39 through 158.
Last start was a system restart from SHUTDOWN REIPL.



Frank M. Ramaekers Jr.



From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Gregg
Sent: Monday, September 27, 2010 11:53 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: How to determine SYSRES

CP Query CPLOAD?
On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers 
framaek...@ailife.com wrote:
How can you determine the SYSRES volume? (Other that interrogating the
SYSTEM CONFIG under System_Residence)
(I know it?s within the CPOWNED list, but I don?t want to depend on the
VolSer to find it)  (Too bad there?s not a CP Q SYSRES)


 Frank M. Ramaekers Jr.

Systems Programmer
MCP, MCP+I, MCSE  RHCE
American Income Life Insurance Co.
Phone: (254)761-6649
1200 Wooded Acres Dr.
Fax: (254)741-5777
Waco, Texas  76701


_ This message
contains information which is privileged and confidential and is solely
for the use of the intended recipient. If you are not the intended
recipient, be aware that any review, disclosure, copying, distribution, or
use of the contents of this message is strictly prohibited. If you have
received this in error, please destroy it immediately and notify us at
privacy...@ailife.com.



--
Gregg Reed
No Plan, survives execution
_ This message
contains information which is privileged and confidential and is solely
for the use of the intended recipient. If you are not the intended
recipient, be aware that any review, disclosure, copying, distribution, or
use of the contents of this message is strictly prohibited. If you have
received this in error, please destroy it immediately and notify us at
privacy...@ailife.com.




The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if
this message has been addressed to you in error, please immediately alert
the sender by reply e-mail and then delete this message, including any
attachments. Any dissemination, distribution or other use of the contents
of this message by anyone other than the intended recipient is strictly
prohibited. All messages sent to and from this e-mail address may be
monitored as permitted by applicable law and regulations to ensure
compliance with our internal policies and to protect our business. E-mails
are not secure and cannot be guaranteed to be error free as they can be
intercepted, amended, lost or destroyed, or contain viruses. You are deemed
to have accepted these risks if you communicate with us by e-mail.


Re: How Do You Configure a 2nd VSWITCH?

2010-09-09 Thread Heinz-Josef Glaser
Dear George,

I see in your 'Query OSA' that the address 9005 is now attached to DTCVSW2.
If you need a second VSWITCH, you must use a free OSA-Address (maybe 9007
is free). You can dynamically define your VSWITCH (e.g. in Userid Maint)
and attatch him to your Linux-System, before you put this in your System
Config. Best is, you make your definitions in the profile exec of your
VM-User Autolog1 instead of System Config.

Mit freundlichen Grüssen / Best regards
Heinz-Josef Glaser
Systemspezialist z/OS, z/VM, z/VSE
Global Technology Services
GE Server Services SPL8 Manag Serv Sys Z
IBM Deutschland
Rathausstrasse 7
09111 Chemnitz
Tel.: +49 371 6978 2876
Fax: +49 371 6978 2280
Mobile: +49 172 668 3018
E-Mail: hjgla...@de.ibm.com

IBM Deutschland Infrastructure Technology Services GmbH
Geschäftsführung: Ulrike Hetzel
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,
HRB 727973


   
  From:   George Henke/NYLIC george_he...@newyorklife.com
   
  To: IBMVM@LISTSERV.UARK.EDU  
   
  Date:   09.09.10 15:42   
   
  Subject:How Do You Configure a 2nd VSWITCH?  
   
  Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU  
   






We currently have a functioning VSWITCH, LNXVSW1, related to a VSWITCH
controller, DTCVSW2 at OSA 9004.

Q VSWITCH

09:14:01 VSWITCH SYSTEM LNXVSW1  Type: VSWITCH Connected: 3Maxconn:
INFINITE
09:14:01   PERSISTENT  RESTRICTEDNONROUTER Accounting:
OFF
09:14:01   VLAN Unaware

09:14:01   MAC address: 02-00-00-00-00-01

09:14:01   State: Ready

09:14:01   IPTimeout: 5 QueueStorage: 8

09:14:01   RDEV: 9004.P00 VDEV: 9004 Controller: DTCVSW2

We are trying to understand how LNXVSW1 is related to the VSWITCH
controller, DTCVSW2 so that we can configure a second VSWITCH, LNXVSW2, for
redundancy and improved throughput.

We believe it is related through our DEFINE in SYSTEM CONFIG:

/* vswitch definitions*/
define vswitch lnxvsw1 portname lnxvsw1 rdev 9004
/* end of vswitch definition */

and our subsequent OSA ATTACH of 9004 to DTCVSW2:


Q OSA

09:14:46 OSA  9000 ATTACHED TO TCPIP9000 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9001 ATTACHED TO TCPIP9001 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9002 ATTACHED TO TCPIP9002 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9004 ATTACHED TO DTCVSW2  9004 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9005 ATTACHED TO DTCVSW2  9005 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9006 ATTACHED TO DTCVSW2  9006 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  903F ATTACHED TO SY92TEST 902F DEVTYPE OSA CHPID 0B
OSD
09:14:46 OSA  907F ATTACHED TO SY91TEST 906F DEVTYPE OSA CHPID 0F
OSD
09:14:46 OSA  90D0 ATTACHED TO VTAM 90D0 DEVTYPE OSA CHPID D1
OSE
09:14:46 OSA  9100 ATTACHED TO TCPIP9100 DEVTYPE OSA CHPID D5
OSD
09:14:46 OSA  9101 ATTACHED TO TCPIP9101 DEVTYPE OSA CHPID D5
OSD

Is this correct?

If so, then to configure a second VSWITCH, we should be able to DEFINE a
second VSWITCH, LNXVSW2, in SYSTEM CONFIG as 9005 and ATTACH the OSA 9005
TO DTCVSW1.

Is this correct?