Hi,

I suppose VTS does the compression anyway, using DDR COMPACT or not.
I have inserted the VTV- volumes as ECCST so they should be 3490(E).
However, DFSMSRM Q VOL vollabel says my vols are 3480 (320MB)  .
The first volume fills after writing about 2800 CYLS, looking from the VTS LM 
shows that the volsize is 792MB (compressed).

Janne



________________________________
From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Gentry, Stephen
Sent: 30. marraskuuta 2010 18:35
To: [email protected]
Subject: Re: DDR multivolume tape as output

Your are correct, it's COMPACT.   I always abbreviate the option.  I don't know 
if it defeats the compression.  Maybe there's a symbiotic relationship between 
the  hardware and software that they come to some sort of an agreement as to 
who does what.
(sorry, been watching too many Star Trek and Terminator movies, et al).
Steve

From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Frank M. Ramaekers
Sent: Tuesday, November 30, 2010 10:42 AM
To: [email protected]
Subject: Re: DDR multivolume tape as output

I think you mean COMPACT.   Doesn't that defeat the compression on the 3590s?



Frank M. Ramaekers Jr.





________________________________
From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Gentry, Stephen
Sent: Tuesday, November 30, 2010 7:59 AM
To: [email protected]
Subject: Re: DDR multivolume tape as output

Coming in a little late on this conversation. A couple of questions.  What are 
the virtual tapes defined as in the VTS?  3480's (I hope not), 3590's? ( "J" 
cartridge to be specific).  Taking your comments literally, you did not use the 
COMPRESS option on the DDR statement.  Using the compress option, I am able to 
get 10 (ten) 3390 mod 3's full packs on a single tape.
Steve

From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Järvinen, Janne
Sent: Tuesday, November 30, 2010 4:25 AM
To: [email protected]
Subject: Re: DDR multivolume tape as output

Unfortunatelly this did not help.

I made the mount as Kris suggested, then started my DDR session.

Got HCP704E   DEVICE <rdev!vdev> NOT OPERATIONAL  (because rdev is not attached 
to my DDR-user, I think)


________________________________
From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Kris Buelens
Sent: 30. marraskuuta 2010 10:53
To: [email protected]
Subject: Re: DDR multivolume tape as output
I've got no experience with DFSMRM
But, what about:
  DFSMSRM MOUNT CAT SCRATCH0 (NOATTACH RDEV xxxx
executed from another userid, and xxxx is the real devioce number of the tape 
MAINT has gotten as 181
(info gotten via HELP DFSMS)
2010/11/30 Janne Jarvinen 
<[email protected]<mailto:[email protected]>>
Hello,

I'm a z/OS person and have some diffuculties to uderstand how to use VTS
tapes in z/VM environment, hopefully get some help from this forum.

How to mount the second DDR dump-tape under VM?

Want to DUMP my SYSRES to tape:

1. MAINT: DFSMSRM MOUNT CAT SCRATCH0


DGTUIR2026I DFSMS request 84 accepted for
processing
Ready; T=0.01/0.01
10:24:22
TAPE 0D3F ATTACHED TO MAINT
0D3F
 10:24:24  * MSG FROM RMSMASTR:    FSMBCR2120I Request 84 complete; volume
V900
 02, category SCRATCH0, mounted on device 0D3F in library
IBMVTS1
 10:24:24  * MSG FROM RMSMASTR:    FSMBEC2125I Request 84: device 0D3F
attached
 to MAINT as 0D3F; access mode =
READWRITE

2. MAINT DDR
SYS CONS
IN 123 DASD
OUT D3F TAPE
DUMP ALL
YES

3. After writing the first tape full, DDR want's the second one.
How to mount it? The rdev d3f is attached to MAINT, so can't mount from
another machine/user. MAINT is "in DDR session" so can't mount from there
either.

4. The tapesystem is VTS using 3584 library.
Any ideas how to get the following output tapes mounted?
(I tested DDR output parm altape to write two tapes but then third tape was
required and there I was again ... )

Thanks
Janne J




--
Kris Buelens,
IBM Belgium, VM customer support

Think green - keep it on the screen. This e-mail and any attachment is for 
authorised use by the intended recipient(s) only. It may contain proprietary 
material, confidential information and/or be subject to legal privilege. It 
should not be copied, disclosed to, retained or used by, any other party. If 
you are not an intended recipient then please promptly delete this e-mail and 
any attachment and all copies and inform the sender. Thank you.
_____________________________________________________ This message contains 
information which is privileged and confidential and is solely for the use of 
the intended recipient. If you are not the intended recipient, be aware that 
any review, disclosure, copying, distribution, or use of the contents of this 
message is strictly prohibited. If you have received this in error, please 
destroy it immediately and notify us at [email protected].


Think green - keep it on the screen.
This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you. 

Reply via email to