Subject: | |
From: | |
Reply To: | |
Date: | Wed, 15 Aug 2001 11:48:01 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
At 10:49 AM 8/15/2001 -0500, Carl McNamee wrote:
>We have a cobol program that uses the File Status clause in a select
>statement. Recently, we started receiving 9x errors which indicate a file
>system error where, according to the manual, the x is a binary number
>between 0 and 255. Since the value is returned into a "X (2)" field we have
>been scratching our heads on how to figure out exactly what the number is.
>Thoughts? Comments? Criticism?
Use the "CKERROR" intrinsic to decipher the 9x errors. Here is a code
snippet you might find useful:
**
SELECT ASNINVOA ASSIGN TO "ASNINVOA"
STATUS ASNINVOA-STAT.
**
77 FILE-ERROR PIC 9(4).
01 ASNINVOA-STAT.
05 ASNINVOA-STAT-1 PIC X.
05 ASNINVOA-STAT-2 PIC X.
**
IF ASNINVOA-STAT-1 = "9" THEN
CALL "CKERROR" USING ASNINVOA-STAT, FILE-ERROR
DISPLAY "!!! ASNINVO: Error on ASNINVOA; ",
"FSERR= ", FILE-ERROR
ELSE
MOVE ASNINVOA-STAT TO FILE-ERROR
DISPLAY "!!! ASNINVO: Error on ASNINVOA; ",
"COBOL file status ", FILE-ERROR
END-IF.
--------------------------------
Tom Brandt
Northtech Systems, Inc.
313 N. 1st Street
Ann Arbor, MI 48103
http://www.northtech.com/
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|