Re: Another quick PASE question -- MIDRANGE-L

× 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.

Subject: Re: Another quick PASE question
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Mon, 26 Nov 2018 11:39:49 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 11/26/2018 11:36 AM, James H. H. Lampert wrote:

While I know that ">/dev/null" will redirect stdout to the
bit-bucket, and I know that in BASH, "&>/dev/null" will redirect both
stdout and stderr to the bit-bucket, what can I do when executing a
PASE command via QP2SHELL, to direct both stdout and stderr to the
bit-bucket?

cmd > /dev/null 2>&1

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Another quick PASE question , James H. H. Lampert

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.