Hi Brian, When you instruct PIPE to execute a COMMAND (or a CMS command in your case) PIPE doesn't get control back until the command terminates. The messages you want to see are being issued WHILE DDR is running, so PIPE can't do anything with them (display them or otherwise) until DDR terminates. DDR is prompting you, you might want to look at setting prompts off and let your PIPE or EXEC react to any failure messages instead.
-Mike -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Brian Nielsen Sent: Wednesday, March 22, 2006 4:13 PM To: [email protected] Subject: DDR in Pipelines question I've been writing some programs to improve our DDR backup process and have 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 is 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 time 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
