Re: VSWITCH

2008-09-14 Thread Alan Altmark
On Thursday, 09/11/2008 at 04:38 EDT, David Kreuter [EMAIL PROTECTED] wrote: Alan and Chuckie won't like it but yes you can share an OSA OSD chpid on two or more lpars. You can (sorry Chuckie) even use the same device triplet in multiple LPARs. You can create quite a nice architecture

Can't detach a DASD device from system

2008-09-14 Thread Marcy Cortes
What is wrong with this device? Why can't I detach it from system? q de33 DASD DE33 CP SYSTEM V8XES1 0 Ready; T=0.01/0.01 11:43:51 det de33 system

Re: Can't detach a DASD device from system

2008-09-14 Thread Imler, Steven J
Try HALT DE33 ... JR (Steven) Imler CA Senior Sustaining Engineer Tel: +1 703 708 3479 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Sunday, September 14, 2008 12:48 PM To:

Re: Can't detach a DASD device from system

2008-09-14 Thread Marcy Cortes
halt de33 Halt was not initiated to DASD DE33 because the device is not active Ready; T=0.01/0.01 11:51:49 Nope. It's very odd. I was taking 17 volumes off, and only this one got

Re: Can't detach a DASD device from system

2008-09-14 Thread Quay, Jonathan (IHG)
I think, but am not sure, that if you have done a DEFINE MDISK against that volume somewhere along the way, that you see this. Look through the virtual device configuration of all the usual suspects (MAINT, OPERATOR, the userid of whatever does full volume backups, etc) or log them off.

Re: Can't detach a DASD device from system

2008-09-14 Thread Marcy Cortes
But a Q SYS ought to show that, right? The system was IPL'd about 4 hours ago as well. Anyway, I checked operator, no vdevs there. Maint is not logged on. The other systems programmers don't have it. Weird. I suppose I should open a problem with the support center. Marcy Cortes Team Lead,

Re: Can't detach a DASD device from system

2008-09-14 Thread Alan Altmark
On Sunday, 09/14/2008 at 12:53 EDT, Marcy Cortes [EMAIL PROTECTED] wrote: halt de33 Halt was not initiated to DASD DE33 because the device is not active Ready; T=0.01/0.01 11:51:49 Nope. It's very odd. I was taking 17 volumes off, and only this one got stuck... Great. LOGOFF/FORCE

Re: Can't detach a DASD device from system

2008-09-14 Thread Scott Rohling
Hmm.. Since it's showing 0 users -- maybe it's in the CPOWN list? Q CPOWN... Scott Rohling On Sun, Sep 14, 2008 at 11:05 AM, Quay, Jonathan (IHG) [EMAIL PROTECTED] wrote: I think, but am not sure, that if you have done a DEFINE MDISK against that volume somewhere along the way, that you

Re: Can't detach a DASD device from system

2008-09-14 Thread Scott Rohling
Silly me - it would have shown up as CPOWN when you did the Q DE33 -- never mind :-) Scott On Sun, Sep 14, 2008 at 11:18 AM, Scott Rohling [EMAIL PROTECTED]wrote: Hmm.. Since it's showing 0 users -- maybe it's in the CPOWN list? Q CPOWN... Scott Rohling

Re: Can't detach a DASD device from system

2008-09-14 Thread Scott Rohling
No - DEF MDISK will not show 0 users - I just tested against an unused volume on our system and it shows 1 user using the volume now... Scott On Sun, Sep 14, 2008 at 11:05 AM, Quay, Jonathan (IHG) [EMAIL PROTECTED] wrote: I think, but am not sure, that if you have done a DEFINE MDISK against

Re: Can't detach a DASD device from system

2008-09-14 Thread Quay, Jonathan (IHG)
Did you do it as a full pack i.e. 0 END? From: The IBM z/VM Operating System on behalf of Scott Rohling Sent: Sun 9/14/2008 1:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Can't detach a DASD device from system No - DEF MDISK will not show 0 users - I just

Re: Can't detach a DASD device from system

2008-09-14 Thread Scott Rohling
Yes I did -- but anticipating you - I defined one from cyls 1-5 instead --- and it shows 1 user in use on the volume: q 6227 DASD 6227 CP SYSTEM DXX00D 0 Ready; T=0.01/0.01 12:34:06 def mdisk 100 1 5 dxx00d DASD 0100 DEFINED Ready; T=0.01/0.01 12:34:14 q 6227 DASD 6227 CP SYSTEM DXX00D 1

Re: WAIT STATE

2008-09-14 Thread Martin, Terry R. (CMS/CTR) (CTR)
Hi, I am still working with this before I re-build system test system. This LPAR does not have a console (need to get cables to connect it) so I only have the HMC system console. I got as far as getting the LPAR to load to this console and I see what my problem was (HCPZPM6705E) as I thought I

Re: Can't detach a DASD device from system

2008-09-14 Thread Marcy Cortes
Oh joy... PMR 11647,379 opened. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If

Bismillah [IslamCity] 12 Foods of Prophet Muhammad (SAW)! -- Ramzan Special

2008-09-14 Thread Najam Manzoor
As Received 12 Foods of Prophet Muhammad (SAW) (Arranged Alphabetically) Barley: Good in fever, while use in a soup form. Dates: The Prophet (SAW) said that a house without dates has no food. It should also be eaten at the time of childbirth. Figs: It is a fruit from paradise

Re: WAIT STATE

2008-09-14 Thread Rich Greenberg
On: Sun, Sep 14, 2008 at 04:40:03PM -0400,Martin, Terry R. (CMS/CTR) (CTR) Wrote: } Just so I understand. The pack that the Parm file is on is my RES pack. } I first thought was to attach it to my other VM system and some how get } to the bad CONFIG file and fix it. Am I on the right track?

Re: WAIT STATE

2008-09-14 Thread Quay, Jonathan (IHG)
Yes, you are on the right track, if you know the minidisk location of MAINT CF1 on your res pack. From: The IBM z/VM Operating System on behalf of Martin, Terry R. (CMS/CTR) (CTR) Sent: Sun 9/14/2008 4:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: WAIT STATE

Re: WAIT STATE

2008-09-14 Thread Martin, Terry R. (CMS/CTR) (CTR)
Thanks all for the help I will try some of these things and let you know how it works out! Thanks Again, Terry -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Greenberg Sent: Sunday, September 14, 2008 4:44 PM To:

Re: WAIT STATE

2008-09-14 Thread Martin, Terry R. (CMS/CTR) (CTR)
Hi I am having a little problem maybe you can see what I am doing wrong! I defined the mdisk starting at 38 ending at 159 for my parmfile: q v 195 DASD 0195 3390 53DRES R/W159 CYL ON DASD 514B SUBCHANNEL = 000E When I trying accessing it I get this: acc 195 x

Re: WAIT STATE

2008-09-14 Thread Thomas Kern
Please make sure of your starting cylinder, ending cylinder and length before you do format it. Starting at 38, ending at 159 should not show up as a 159 cyl minidisk. /Tom Kern Adam Thornton wrote: On Sep 14, 2008, at 3:33 PM, Martin, Terry R. (CMS/CTR) (CTR) wrote: Hi I am having a

Re: WAIT STATE

2008-09-14 Thread Scott Rohling
As nerve-wracking as it can be -- there really is no better learning experience than fixing things like this in a crisis.. Welcome to disaster-avoided club, Terry :-) Scott

Re: WAIT STATE

2008-09-14 Thread Adam Thornton
On Sep 14, 2008, at 3:33 PM, Martin, Terry R. (CMS/CTR) (CTR) wrote: Hi I am having a little problem maybe you can see what I am doing wrong! I defined the mdisk starting at 38 ending at 159 for my parmfile: q v 195 DASD 0195 3390 53DRES R/W159 CYL ON DASD 514B SUBCHANNEL = 000E