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

Reply via email to