> -----Original Message-----
> From: Friedrich Harasleben
>
> I need to start a Job from within an ACCESS application [...]
> As the function might be used by different persons at he same time, I
> want to use unique filenames, BUT HAVE NOT FOUND ANY WAY TO MODIFY the
> FILEEQs in the Job BEFORE STREAMING it?

There are several solutions available:
  1) [most obvious] have ACCESS transmit the jobstream replacing bits as
needed -- remember, the STREAM command can take input from $STDIN, and since
you already have a connection via reflection [presumably to a session with
direct access to the MPE prompt], this would be trivial
     DOWNSIDE: any changes to the job requires rewriting your ACCESS
application to actually implement the job change, then redistributing that
application to all of your users [which can be mitigated somewhat if the
"application" resides in a common location, i.e., a shared directory or as
part of the Database everyone is using]

  2) [as mentioned] put a placeholder in the job to represent the filename,
then pass the jobstream through a pre-processor to make the switch at the
time you submit the job.  There are free solutions [I think AWK was
mentioned] as well as commercial ones [Streamx/3000 comes to mind]
     DOWNSIDE: additional cost (if purchased) and training (if you currently
do not have anyone familiar with AWK or Streamx or whatever product you
choose)
     Upside: job source remains on the HP; changes are centralized, etc.

   3) [most work, perhaps?] variant of number 2, and I think someone already
mentioned it: use reflection to transfer the job source to the PC, then use
Access to do the find & replace mentioned above; then transfer the file back
to the HP and submit the modified job [either via $STDIN or by using a
temporary name -- you don't want to overwrite the original!]

   4) look into the "global variables" topic that has been floating around
here -- basically, set a variable in your "session" that is accessible to
the "job" once streamed using logic like this:

   !FILE INPUT=!globalvar;<options>

[I'm thinking this might be a 7.0 "feature", however -- I haven't been
paying strict attention to that thread]  If it is a 7.0 (or future) feature
that you don't have, an alternate might be to write the name of the file to
another filename (that is a standard name) and have the job do this:

    !INPUT actualname < STDFILE
    !FILE INPUT=!actualname

Of course, you cannot have two people submit this job concurrently [then
again, this is true with the "global var" approach anyway...]

Have fun

Tom

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