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



Sorry. 'standardization' : what language is that?

Rick.Chevalier@xxxxxxxxxxxxxxx wrote:

Bummer. We have a program using QSH to run a third party utility that
converts PDF files to TIF files. I was hoping the error numbers had
some kind of standardization.

Thanks Scott.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, April 28, 2011 1:26 PM
To: Midrange Systems Technical Discussion
Subject: Re: QSH exit status - Where to find descriptions

I don't think there's anything like what you're looking for. Exit
codes have no standard that I'm aware of. Any programmer can put any
number from 0-255 in an exit code.

By convention, zero=success, and non-zero=fail.

Beyond that, you have to look at it on a per-program basis. You have to
ask the programmer what each exit code means (or hope it's documented
somewhere.)


On 4/28/2011 1:16 PM, Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
Hopefully this is an easy question.

Can I find text descriptions of QSH exit status codes? Something
like
msgf/QSHxxxx. I'm trying to track down an exit code of 255 but
haven't been successful yet in locating a description.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.



Privileged and Confidential. This e-mail, and any attachments there
to, is intended only for use by the addressee(s) named herein and may
contain privileged or confidential information. If you have received
this e-mail in error, please notify me immediately by a return e-mail
and delete this e-mail. You are hereby notified that any
dissemination, distribution or copying of this e-mail and/or any
attachments thereto, is strictly prohibited.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my brevity.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.