Shelling out CRTLF via QCMDEXC -- question about success/failure -- MIDRANGE-L

Subject: Shelling out CRTLF via QCMDEXC -- question about success/failure
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Mon, 8 Jun 2026 14:31:07 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I've got a project in which I will be using a QCMDEXC call to shell out a CRTLF (from a generated source member). What is the easiest way for the calling program to determine whether the CRTLF was successful?

--
JHHL

Follow-Ups:

Re: Shelling out CRTLF via QCMDEXC -- question about success/failure , David Gibbs
Re: Shelling out CRTLF via QCMDEXC -- question about success/failure , Jason Olson
Re: Shelling out CRTLF via QCMDEXC -- question about success/failure , Jason Olson
Re: Shelling out CRTLF via QCMDEXC -- question about success/failure , Jon Paris
Re: Shelling out CRTLF via QCMDEXC -- question about success/failure , Rob Berendt
Re: Shelling out CRTLF via QCMDEXC -- question about success/failure , Vern Hamberg

This mailing list archive is Copyright 1997-2026 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.