Thanks! It turns out it is a situation of simply using one or the other. In this case I'll just use the other. Tracy Johnson Measurement Specialties, Inc. BT NNNN > -----Original Message----- > From: HP-3000 Systems Discussion > [mailto:[log in to unmask]] On Behalf Of Tom Emerson > Sent: Tuesday, December 02, 2008 7:41 PM > To: [log in to unmask] > Subject: Re: [HP3000-L] Time Warping in Your Job Streams > > > Yes, StreamX substitutions occur at SUBMISSION time, not at > "job execution" time. > > the "!HPtimef" function executes at RUN time, thus if your > job started at 5:45, but gets "suspended" for an hour or two > [so the boss's "high priority" job can complete...] and THEN > gets to the !HPTimeF statement, it will also be as of the > "current" time of the job, not 5:45... > > If you want to use StreamX substitutions that evaluate at the > time the job launches, you have to do the following: > > 1) write a "wrapper" job that simply submits the job, i.e. > > !job runme,mgr.whatever > !file strmfile=real.job > !run streamx.pub.vesoft;parm=1 > !eoj > > 2) ensure that "real.job" can be submitted by mgr.whatever > without any prompting (passwords, etc.) > > 3) submit the "wrapper' job using ";at=..." > > Note that if you try > > !job runme,mgr.whatever > !stream real.job > !eoj > > Streamx will see the "embedded" STREAM command and process > the contents of that AT THE TIME YOU SUBMIT THE OUTER job, > which defeats the purpose of using the "wrapper". You CAN, > use this form of a "wrapper" job, but you have to set a > special variable, STREAMXNONEST to 1 [I think -- it's been a > while...] This tells STREAMX to not process any "inner" jobs > [this can also be controlled in the job itself with some :: > directives -- dig out the manual for that one...] > > > > > ----- Original Message ---- > From: "Johnson, Tracy" <[log in to unmask]> > To: [log in to unmask] > Sent: Tuesday, December 2, 2008 3:01:31 PM > Subject: [HP3000-L] Time Warping in Your Job Streams > > This was one of those days were this old dog learned a new trick. > > I found out to my dismay,* that when I used a VESoft > expression for a date/time in my job stream, it would always > pick up the time it was streamed. So if I used an ;AT= or > ;IN= parameter for the future an expression using > {STRWRITE(CLOCK)} as a variable, it would always display the > time the "STREAM" command was used, not the time the job ran. > Example: STREAM MYJOB.JOB;AT=5:45 would NOT put in the > variable 5:45AM the next day, it would use whatever time I > streamed the job. > > I found that if I converted the VESoft clock (above) > expression to !HPTIMEF, the ;AT= parameter 5:45 AM got used > in my Variable (as > intended.) > > To prove that I'm not insane, can anyone else confirm? > > Tracy Johnson > Business Analyst > Measurement Specialties, Inc. > 1000 Lucas Way > Hampton, VA 23666 > Office 1-757-766-4318 > [log in to unmask] > www.meas-spec.com > > * 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 * > * To join/leave the list, search archives, change list settings, * * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *