Hi Matt,

You need to run a CP  QUERY DASD LN44A9 command on a class A user. If the 
volume does not exist, that is your problem. If it exists, but if it is not 
attached to SYSTEM, it is not available for minidisk use. (ATTACH xxxx SYSTEM 
LN44A9)

Peter

-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dazzo, 
Matt
Sent: June 3, 2015 3:29 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: RHEL Install zvm

Here is the actual user direct, I pasted an old one into the email. I get the 
messages 191, 192 not linked and DMSACP113S A(191) not attached or invalid 
device address. Thanks Matt

USER LNXMAINT LNXMAINT 512M 512M BEG                    
 INCLUDE TCPCMSU                                        
 LINK TCPMAINT 592 592 RR                               
 MDISK 191 3390 0001 0020 LN44A9 MR READ WRITE MULTIPLE  MDISK 192 3390 0021 
1500 LN44A9 MR READ WRITE MULTIPLE

LOGON LNXMAINT                                                    
HCPLNM108E LNXMAINT 0191 not linked; volid LN44A9 not mounted     
HCPLNM108E LNXMAINT 0192 not linked; volid LN44A9 not mounted     
z/VM Version 6 Release 3.0, Service Level 1501 (64-bit),          
built on IBM Virtualization Technology                            
There is no logmsg data                                           
FILES:   NO RDR,   NO PRT,   NO PUN                               
LOGON AT 15:28:11 EDT WEDNESDAY 06/03/15                          
z/VM V6.3.0    2015-06-01 12:41                                   
                                                                  
DMSACP113S A(191) not attached or invalid device address          
Ready; T=0.01/0.01 15:29:07                                       

-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Neale 
Ferguson
Sent: Wednesday, June 03, 2015 2:56 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: RHEL Install zvm



On 6/3/15, 2:39 PM, "Dazzo, Matt" <mda...@pch.com> wrote:

>MDISK 191 3390 0001 0020 LN2C17 MR READ WRITE MULTIPLE
>    
> MDISK 192 3390 0021 0980 LN2C17 MR READ WRITE MULTIPLE
>      
>
>Activate the new user direct
>
>LOGON LNXMAINT    
>HCPLNM108E LNXMAINT 0191 not linked; volid LN44A9 not mounted 
>HCPLNM108E LNXMAINT 0192 not linked; volid LN44A9 not mounted
Strange that your directory entry specifies volume LN2C17 but LNXMAINT is 
looking for volume LN44A9. Because it cannot find that volid, it cannot give 
you a 191 or 192 minidisk.


> I do (att xxx * 191) Start the format, the format process formats the 
>entire disk not just the first 20 cyl of 191.


What are you attaching as 191 and why? The MDISK statements mean that when you 
logon to LNXMAINT it will (should) have a 191 and 192 disk there for you to 
format. However, the mismatch in VOLIDs is puzzling. On MAINT, what does #CP Q 
DA LN44A9 and #CP Q DA LN2C17 report?

Neale



The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material.  Any 
review retransmission dissemination or other use of or taking any action in 
reliance upon this information by persons or entities other than the intended 
recipient or delegate is strictly prohibited.  If you received this in error 
please contact the sender and delete the material from any computer.  The 
integrity and security of this message cannot be guaranteed on the Internet.  
The sender accepts no liability for the content of this e-mail or for the 
consequences of any actions taken on the basis of information provided.  The 
recipient should check this e-mail and any attachments for the presence of 
viruses.  The sender accepts no liability for any damage caused by any virus 
transmitted by this e-mail.  This disclaimer is property of the TTC and must 
not be altered or circumvented in any manner.

Reply via email to