Feedback token

A feedback token contains feedback information in the form of a condition token. The condition token set by the callable service is returned to the calling routine, indicating whether the service completed successfully.

COBOL for AIX uses the same feedback token as Language Environment, which is defined as follows:

01  FC.
    02  Condition-Token-Value.
    COPY  CEEIGZCT.
        03  Case-1-Condition-ID.
            04  Severity    PIC S9(4) COMP.
            04  Msg-No      PIC S9(4) COMP.
        03  Case-2-Condition-ID
                  REDEFINES Case-1-Condition-ID.
            04  Class-Code  PIC S9(4) COMP.
            04  Cause-Code  PIC S9(4) COMP.
        03  Case-Sev-Ctl    PIC X.
        03  Facility-ID     PIC XXX.
    02  I-S-Info            PIC S9(9) COMP.

The contents of each field and the differences from IBM Language Environment on the host are as follows:

Severity
This is the severity number with the following possible values:
0
Information only (or, if the entire token is zero, no information)
1
Warning: service completed, probably correctly
2
Error detected: correction was attempted; service completed, perhaps incorrectly
3
Severe error: service did not complete
4
Critical error: service did not complete
Msg-No
This is the associated message number.
Case-Sev-Ctl
This field always contains the value 1.
Facility-ID
This field always contains the characters CEE.
I-S-Info
This field always contains the value 0.

The sample copybook CEEIGZCT.CPY defines the condition tokens. The condition tokens in the file are equivalent to those provided by Language Environment, except that character representations are in ASCII instead of EBCDIC. You must take these differences into account if you compare the condition tokens with those provided by Language Environment.

The descriptions of the individual callable services include a listing of the symbolic feedback codes that might be returned in the feedback code output field specified on invocation of the service. In addition to these, the symbolic feedback code CEE0PD might be returned for any callable service. See message IWZ0813S for details.

All date and time callable services are based on the Gregorian calendar. Date variables associated with this calendar have architectural limits. These limits are:

Starting Lilian date
The beginning of the Lilian date range is Friday 15 October 1582, the date of adoption of the Gregorian calendar. Lilian dates before this date are undefined. Therefore:
  • Day zero is 00:00:00 14 October 1582.
  • Day one is 00:00:00 15 October 1582.

All valid input dates must be after 00:00:00 15 October 1582.

End Lilian date
The end Lilian date is set to 31 December 9999. Lilian dates after this date are undefined because 9999 is the highest possible four-digit year.

related references  
Runtime messages