Note that WARNF uses the  WARN console command (under the covers) and
requires an ALLOW @.@ WARN.  This works on these systems because the $ALLOW
is explicitly stated in the SECURCON.DATA.VESOFT file and SECURITY/3000 is
enabled.

Tom G.

                -----Original Message-----
                From:   Fontaine, Charles
[mailto:[log in to unmask]]
                Sent:   Wednesday, January 27, 1999 4:22 PM
                To:     [log in to unmask]
                Subject:        Re: Jobstreams with interactive input

                Actually we find this quite useful.  We have many users who
stream
                STREAMXified jobs from a menu throughout the day.  The
STREAMX prompts allow
                them to request reports on a variety of criterium.  Because
the user returns
                to a View (block mode) screen we use the MPEX WARNF command.
This way if
                the user who streamed the job is still logged on when the
job finishes, they
                receive a message at the bottom of their screen (where the
function keys are
                normally displayed) informing them that their job has
finished.  They can
                then view/print/download the report from a VISTA folder.
Each job contains
                logic to save the reports to a Vista folder.  If the user
who streamed the
                job has logged off the system, a harmless warning message is
displayed in
                the jobs stdlist.

                %WARNF !HPSTREAMEDBY The job (#J!hpjobnum) has completed! &
                %Your extract file is: !LOGGED (Press Enter to clear this
message)

                Regards,
                Charlie Fontaine

                > ----------
                > From:         Nick Demos[SMTP:[log in to unmask]]
                > Sent:         Wednesday, January 27, 1999 4:05PM
                > To:   [log in to unmask]
                > Subject:      Re: Jobstreams with interactive input
                >
                > Battey, Jacob wrote:
                > >
                > > I noticed some interesting behavior of jobs that I can't
find documented
                > > or even mentioned anywhere, but struck me as being
potentially useful.
                > > For instance:
                > >
                > > !JOB whatever,whoever.acct;etc.
                > > !SETVAR GET_INPUT, "?PLEASE ENTER SOMETHING:?"
                > > !TELL !HPSTREAMEDBY, !GET_INPUT
                > > !EOJ
                > >
                > > Whoever streamed it gets this prompt:
                > > PLEASE ENTER SOMETHING:?
                > > before the job is actually kicked off (before it shows
up with SHOWJOB)
                > > and replaces whatever is between the question marks with
whatever you
                > > type at the prompt.
                > >
                > > I use MPEX for batch jobs.  BREAK and things behave as
they should, and
                > > I think as long as it's used with SETVAR and input is
checked doing this
                > > should be as safe as any other method of getting
interactive input.
                > > Anybody familiar with this?  In particular, anybody see
any security
                > > considerations?
                >
                > I don't see a security problem, BUT this seems kind of
hokey to
                > me.
                > The user has to be logged on and at his terminal when the
job is
                > streamed.  If he is not - no go.  If it is done in a shop
where
                > the
                > 3000 is so lightly loaded that the job is done
immediately, fine,
                > if
                > not I see trouble.
                >
                > Nick D.
                >