× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks, Patrick.  Turns out that this redirect doesn't work on syntax
errors.  I'd like to simply keep that screen from displaying and,
instead, just let the CLP handle the error.

Dan

--- Patrick L Archibald <Patrick.Archibald@HOMETELCO.COM> wrote:
> --
> [ Picked text/plain from multipart/alternative ]
> Add the following after your command:   >/dev/null 2>&1
>
> For example:
>
> qsh cmd('java myProgram   >/dev/null 2>&1')
>
> Thanx, PLA
>
> Dan wrote:
>
> >>From the QSH command help:
> >
> >
> >>If run in an interactive job, STRQSH starts
> >>an interactive shell session.
> >>
> >>
> >
> >When I execute a command through QSH and the exit status <> 0, there
> >appears some kind of error screen that shows the error that caused
> the
> >screen to appear and then offers: "Press ENTER to end terminal
> >session."
> >
> >The qsh command is executed in a CL but run interactively.  Is it
> >possible to keep this screen from appearing, and make it act as if
> it
> >were running in batch?  (FWIW, I am doing a RCVMSG on QSH0005 to
> check
> >for the exit status.)  Is "redirection" what I'm looking for?
> >
> >Any examples would be greatly appreciated for this qsh "newbie".
> >
> >TIA, Dan

__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.