I have already done that. Now, they need to be defined.
 
Regards, 
Richard Schuh 
 
 

________________________________

        From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Raymond Noal
        Sent: Monday, June 30, 2008 3:27 PM
        To: [email protected]
        Subject: Re: Making Devices Available
        
        
        Richard,
         
        It should not be that complicated.
         
         
        Issue the following to see if it applies to your system - HELP
CPSET DEVICES - and check if you have the proper features statement(s)
set. You should be able to issue - SET ACCEPTED rdev-rdev.
         
        HITACHI
         DATA SYSTEMS 
        Raymond E. Noal 
        Senior Technical Engineer 
        Office: (408) 970 - 7978 
         
        
________________________________

        From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard
        Sent: Monday, June 30, 2008 3:19 PM
        To: [email protected]
        Subject: Making Devices Available
         
        We have some DASD devices that were, until a few minutes ago, in
the Devices_NotAccepted list. I have made some of them accepted, both in
the SYSTEM CONFIG and by command. Now, I am confronted with a DEFINE
DEVICE command that, from the HELP files is as clear as murky water to
me (the problem may well be between my ears). Is it as simple as "DEFINE
DEVICE F6EF-F6F7 UNITADD EF CUNUMBER nnnn DASD" (nnnn to be filled in
when someone supplies the value from the IOCP - I do not have ready
access)? Assuming that I get them defined, is all that is left varying
them online? They will initially be attached to the user who is going to
prepare them for use, so there will be no ATTACH to SYSTEM.
        Regards,
        Richard Schuh 
         

Reply via email to