Peter,

The following udc should do what you want. :SETCATALOG it at the lowest
level possible (against a single user would be best). The only thing that
you will need to do is replace the string '<keep_name>' with an actual file
name.

stream
anyparm streamparms = !['']
option norecursion
errclear
setvar _str_jobfile word("!streamparms")
setvar _str_parms ups(repl(rht("!streamparms",-delimpos("!streamparms")),"
",""))
copy !_str_jobfile,<keep_name>;yes
continue
stream !_str_jobfile !_str_parms
deletevar _str_@
**********

regards,
*****************************
Robert W.Mills, Systems Development Manager, Windsong Services
Electron House, Cray Avenue, St. Mary Cray, Kent BR5 3PN, ENGLAND
Tel: +44 (0)1689.870622 x 3005  Fax: +44 (0)1689 899026
[log in to unmask]
********************************
The thoughts, comments, and opinions expressed herein are mine.
They do not reflect those of my employer, nor anyone else.
********************************
***Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipients and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.

-----Original Message-----
From: Tom Emerson [mailto:[log in to unmask]]
Sent: 07 March 2002 16:52
To: [log in to unmask]
Subject: Re: Need help


> -----Original Message-----
> From: Peter Herpich

> need a procedure or udc to do the following.
>
> when the stream-command is executed from the CI or thru HPCICOMMAND
> I want to make a copy of the streamd file.

I'm trying to envision what "problem" this solves -- after all, streaming a
file doesn't modify or destroy the file, so why make a copy?  What do you do
if you stream the file multiple times, which "copy" do you keep? [or do you
plan on serializing the copies?]

I'll amend my earlier statement somewhat: stream doesn't modify or purge the
source file, however I can think of three instances where this doesn't
matter:
   1) the job itself modifies or purges the file; if so, the job should make
a copy before modifying/purging the file
   2) you don't have STREAMX or any similar product, so you are manually
making changes to the jobs on a frequent basis (for example, a program that
prompts for selection criteria might include a date, so every day the source
job needs to be updated...)  Again, the "policy" should be to back-up the
file before editing -- this might be where you want a special UDC...
   3) you're submitting temporary files, which will "go away" when you log
off.  Again, if you are doing this interactively, why not :SAVE a copy of
the file by hand?  Programmatically (calling HPCICOMMAND) you should FCLOSE
your output file with options to make it a permanent file, or write two
files...

Making a copy when you stream a job sounds like a band-aid solution to a
much larger problem, however placing the band-aid here doesn't cure the
problem, it only stops the bleeding for a while...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *