RE: error checking following QSH execution

Dan, 

QSH002 is really just an indication that the return code was "not normal" --
whatever that might mean.  I'm not too sure of the mechanics of error
handling in QSH.  I was just interested in trapping ANY error, so it was a
no-brainer for my application. Sorry I can't say more....


Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Dan [mailto:dbcemid@xxxxxxxxx]
Sent: Tuesday, May 06, 2003 10:29 AM
To: Midrange Systems Technical Discussion
Subject: RE: error checking following QSH execution


Thanks Eric!

Is it usually enough to know that QSH0002 was issued, or do you want to
interrogate the reason
code and/or error number?  The message shows what the reason codes are, but
they are very vague. 
Where are the errno's documented?  Are they set by the Java application?

Specifically, I have been asked to trap errors such as when the spool file
no longer exists when
the java program expects it to be available to create the PDF from it.
Also, any errors when the
email fails to send.  

Bottom line:  It would be nice to be able to issue a message "PDF creation
failed because spool
file no longer exists".  Note: I would like to avoid having to test for its
existence before
calling the java program.

--- "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx> wrote:
> Dan
> 
> QSH throws an *Escape message QSH0002 to return error notification to
OS400.
> Read the HELP for the QSH command, and you will find:
> 
> *ESCAPE Messages                                                   
> QSH0002     Error found with QSH session, reason code &1, errno &2.

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
_______________________________________________
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.cgi/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.