From 2 replies I got, it sounds like SUBMIT and STREAMX are not the best of
buddies.  Suggestions were to use streamx instead of submit ... however, I
don't
have control over that, as the application is third-party.  So, I will have
to think
of some other avenue....
    Tom Hula

Tom Hula wrote:

> I now have jobq's working as I wished, with my speedware applications in
> one queue and all
> other applications running in a different queue so I can run speedware
> applications in the
> background (or whatever other applications I want running in the
> background).
>
> The one remaining problem is this:  I don't have direct access to the
> speedware job streams,
> which are built on the fly in temp files, streamed and deleted.  To get
> around this, I used the
> Mpex option $JOBPARMS-ALWAYS @.@ @[log in to unmask]@ @.SPWFIN "PRI=ES" in the
> streamx.data.vesoft file to force those jobs to run in the ES queue.
> Then I discovered that
> these jobs are also bypassing streamx, so I added the option
> "XL=STREAMNL.PUB.VESOFT" to the run of the speedware program to force it
>
> to use Streamx.
>
> So then I got a change in behavior due to how the Speedware SUBMIT
> command works.
> What I wanted was this:  I log on to production account, get into
> Speedware application
> and stream a job, which logs on in the Speedware application account.
> What I got was this: The same as above, except the job logs on in my
> logon account
> and proceeds to blowup because it thinks it going to be logging in
> somewhere else.
>
> Talked to Vesoft about it, and it all came down to how the Speedware
> SUBMIT
> command works ... probably uses braces or question marks internally.
> The Speedware
> application developer can't answer any questions on the topic, and I
> can't ask Speedware,
> since I don't have any support from them...all of my support is through
> the Speedware
> application developer.  I tried setting the brace and ? characters to
> other values using
> setjcw VESOFTQUESTIONDELIMITER,VESOFTOPENBRACE,VESOFTCLOSEBRACE
> to change the value of what MPEX was looking for.  Changing the {'s to
> ['s and
> }'s to ]'s didn't seem to have any effect and changing the ? to ~ caused
> the SUBMIT
> command in Speedware to fail.  If anyone has a clue how to get around
> this...
>
>     Tom Hula
>     Victor S. Barnes Co.
>     616.361.7351  x173