HP3000-L Archives

June 1997, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Glenn A. Mitchell" <[log in to unmask]>
Reply To:
[log in to unmask][log in to unmask]
Subject: Condition Word 41 [...]39_5Jun199710:10:[log in to unmask]
Date:
Fri, 6 Jun 1997 11:58:32 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
Stigers, Gregory - ANDOVER wrote:
>
> HPRC tells me that their definitions for the ANSI standard's
> 'implementor-defined' file status codes 9x are the same as FSERRs.
> Looking at some of the FSErrs, I am less than convinced. Is this in fact
> the case?

That is the case.   You can call FERRMSG passing it the second byte of
the status code (stick it in the low-order byte of an S9(4) COMP field)
to get the error message text that goes with the FSERR.  For most COBOL
programs, we check for a 9x status code and then call "PRINTFILEINFO"
passing the FD name as the only parameter.  This produces the normal
tombstone for the error.
--
Glenn A. Mitchell               mailto:[log in to unmask]
Director, Computer Technology   http://www.mmc.org
Maine Medical Center
Portland, ME  04101

ATOM RSS1 RSS2