Defining non-3390 T-Disks

2010-04-24 Thread Mark Post
I want to be able to define temporary 3380 or 9336 devices. Doing a define t3390 works just fine, but t3380, t9336, and tfb-512 all return HCPLNM091E DASD 0200 not defined; temp space not available Is there something that needs to be defined elsewhere to make this possible? I searched the CP

Re: Defining non-3390 T-Disks

2010-04-24 Thread Robert Reuscher
You have to TDISK space defined on those particular device types to be able to define the space by a user. It doesn't simulate different device types, it only uses what you actually have TDISK space defined on your real volumes. On Apr 24, 2010, at 10:43 AM, Mark Post wrote: I want to be

Re: Defining non-3390 T-Disks

2010-04-24 Thread Richard Troth
... or T3370 or T3350 ... or T3330? How far back would you want to go? :-) What RR said. You must have the same kind of physical disk in temp land as the particular temp type you're defining. Of course, VFB-512 uses RAM to fake it, presenting a virtual 9336 because a physical 9336 (and a

Re: Defining non-3390 T-Disks

2010-04-24 Thread Benedict, Martin
Try reducing the size. --Original Message-- From: Mark Post To: IBMVM@LISTSERV.UARK.EDU ReplyTo: The IBM z/VM Operating System Subject: Defining non-3390 T-Disks Sent: Apr 24, 2010 11:43 I want to be able to define temporary 3380 or 9336 devices. Doing a define t3390 works just fine