It was not changing the h/w configuration, the devices have been in the
IOCP and actually installed for months. They were in a
Devices_NotAccpted list because our storage management group is MVS
based and does not want us to have any devices not specified as VM
devices available to the system. They are Not_Accepted because there are
6000 of them, so they would take up a lot of storage and get in the way
of some monitoring functions.The devices in question are ones being
given to VM for a project. I needed to change them to ACCEPTED and make
them available without an IPL. The commands I needed were:
SET DEVICES ACCEPTED rdev1-rdevn
SET RDEVICE rdev1-rdevn TYPE DASD
VARY ON rdev1-rdevn
It turns out that I cannot use the commands that alter the IOCDS because
the token is not a VM token. I tried and failed :-) The h/w group that
does IOCPs is also MVS based.
Regards,
Richard Schuh
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens
Sent: Tuesday, July 01, 2008 2:45 AM
To: [email protected]
Subject: Re: Making Devices Available
DEFINE DEVICE/CNTLUNIT/CHPID are the commands to dynamically
change HW the IO-config (i.e. the IOCP so to speak). SET RDEVICE is
normally required only when the device doesn't answer to a SENSID (kind
of dynamic HCPRIO)
2008/7/1 Schuh, Richard <[EMAIL PROTECTED]>:
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
--
Kris Buelens,
IBM Belgium, VM customer support
