Don't really want to do that. I want to take an existing EXEC that doesn't create a log file and run it through this to produce a log file.
I guess we can't timestamp each line accurately (from an existing EXEC)? Frank M. Ramaekers Jr. > -----Original Message----- > From: CMSTSO Pipelines Discussion List [mailto:CMS- > [email protected]] On Behalf Of Paul Gilmartin > Sent: Wednesday, May 22, 2013 11:02 AM > To: [email protected] > Subject: Re: [CMS-PIPELINES] Help with log timestamping > > On 2013-05-22, at 09:14, Frank M. Ramaekers wrote: > > > I've written the following EXEC to execute any other EXEC and > > timestamp each output line: > > ... > > "? CMS" ExecFn args, > > > If you're using this to generate your test data, be aware that the CMS stage > buffers _all_ its output and passes it to the next stage in a blast. Try using a > pipline with a DELAY stage to test. > > > TESTRUNN EXEC A1 V 130 > > > > |...+....1....+....2.. > > > > 0 * * * Top of File * * > > 1 /* */ > > 2 Trace "O" > > 3 Say "First line" > > 4 "CP SLEEP 6 SEC" > > 5 Say "Second line" > > 6 Exit > > 7 * * * End of File * * > > > > > > My output looks good, except for the fact that the timestamps are all > > the same. > > > > TESTRUNN LOG A1 V 80 Trunc=80 > > |...+....1....+....2....+....3. > > 0 * * * Top of File * * * > > 1 20130522 094935 First line > > 2 20130522 094935 Second line > > 3 * * * End of File * * * > > -- gil _____________________________________________________ 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].
