Re: anyone using PROGRAM STATUS clause in SPECIAL-NAMES?

Here's one I threw together:

IDENTIFICATION DIVISION.
PROGRAM-ID. ChkStatus.

ENVIRONMENT DIVISION.
CONFIGURATION SECTION.
SPECIAL-NAMES.
PROGRAM STATUS IS Program-Info.

DATA DIVISION.
WORKING-STORAGE SECTION.
01 Program-Info.
05 Program-Name PIC X(10).
05 Program-Library PIC X(10).
05 Module-Name PIC X(10).
05 Statement-Number PIC X(10).
05 Optimization-Level PIC X(06).
05 Exception-ID PIC X(07).

01 Five PIC S9(9) BINARY VALUE 5.
01 Zero-Value PIC S9(9) BINARY VALUE 0.

PROCEDURE DIVISION.
MAIN-LINE.
DISPLAY Program-Info.
DIVIDE Zero-Value INTO Five
ON SIZE ERROR DISPLAY Program-Info
END-DIVIDE.
STOP RUN.

Hope this helps,
Bruce Vining




"Michael Rosinger" <mrosinger@xxxxxxxxx>
Sent by: cobol400-l-bounces@xxxxxxxxxxxx
04/16/2007 12:54 PM
Please respond to
COBOL Programming on the iSeries/AS400 <cobol400-l@xxxxxxxxxxxx>


To
cobol400-l@xxxxxxxxxxxx
cc

Subject
[COBOL400-L] anyone using PROGRAM STATUS clause in SPECIAL-NAMES?






Is anyone using the PROGRAM STATUS clause in SPECIAL-NAMES? I can't get
the
program to populate the data area I reference. When I force a dump using
QlnDumpCobol, the area shows up in the dump but is not populated. The
COBOL
Reference says the that the area is populated "when an error occurs..."
but
does not define what "error" is. Can't I force it to be populated? There
is
very good information there that I would like to take advantage of in the
program.

Anyone got a working example they would care to share? TIA