I am out of the office until 05/03/2010.
Note: This is an automated response to your message IBMVM Digest - 22 Apr
2010 to 23 Apr 2010 (#2010-109) sent on 4/24/10 1:01:01.
This is the only notification you will receive while this person is away.
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
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
... 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
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,
We just migrated off the Luminex solution to EMC/BusTech MDL. While on Luminex,
we never had any issues with SPXTAPE or SPTAPE for that matter.
Martin V. Benedict, Sr.
Sr. Systems Programmer
IT Department
The Golub Corporation - Price Chopper Markets
461 Nott Street
Schenectady, New York, 12308
