I think I heard at the SHARE session on Safe Software's relatively cheap 
"Safe DR" product that they had to modify DDR to play nicely at all.

If you don't want to pay the higher price for all the capabilities of: 
CA's VM:Backup 
(http://supportconnectw.ca.com/public/vm/backup/vmbackupsupp.asp), 
CA's VM:Backup-HIDRO 
(http://supportconnectw.ca.com/public/vm/hidro/vmdrsupp.asp),or 
IBM's "Backup and Restore Manager for z/VM" 
(http://www-306.ibm.com/software/stormgmt/zvm/backup/) 
(sorry if I missed any), then you might want to check out "SAFE DR" 
(http://www.vm.safesoftware.com/SafeDR.htm) rather than reinventing the 
wheel.

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.




"Brian Nielsen" <[EMAIL PROTECTED]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
03/22/2006 03:13 PM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
DDR in Pipelines question






I've been writing some programs to improve our DDR backup process and hav
e 
run into an issue using DDR in a pipeline.  I'm using the following pipe 

to capture the output from DDR:

/* save the DDR output */ 
'PIPE', 
  'CMS DDR DDR CNTRL' o_fm,
  '| CONS',
  '| >>' log_fid, 
  '| stem ddr_output.' 

The DDR CNTRL file might look like this:

SYSPRINT CONS 
INPUT 190 DASD ZZZZZZ 
OUTPUT 181 TAPE (LEAVE
DUMP ALL 


Two problems are:
1) DDR does not send any messages into the pipeline until the DDR is 
complete, whereas prompts display immediatly on the terminal.  So there i
s 
no information from non-prompt messages, such as

     "HCPDDR711D VOLID READ IS MNT190 NOT ZZZZZZ"

on which to base decisions in real time if prompted.

2) Prompt messages are never sent to the pipeline.


Is there any way to get DDR to play nicely in a pipeline?  It would be 

nice to be able to insert additional code in the pipe to know in real tim
e 
when unpredictable events happen after the dump has started (such as END 

OF VOLUME).

If not, are there any available methods to programatically capture and 

process DDR messages as they occur?  Obviously, the simpler the better.

Brian Nielsen




 
The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited.

Reply via email to