Errors, C and Python
DECLARATIVES and USE catch an I/O verb that fails, and the status codes this compiler really returns get a table of their own. Three lessons then call C from COBOL and let C call a COBOL module; Python drives that module through ctypes and through stdin. The part closes on the messages, exit codes and logs a batch job leaves behind.
106
DECLARATIVES and USE
USE AFTER STANDARD ERROR, what runs when an I/O verb fails, and a message from the handler
Open
107
ON EXCEPTION and the status table
INVALID KEY, ON OVERFLOW, ON EXCEPTION, and a table of status codes this compiler really returns
Open
108
Calling C from COBOL
CALL "printf" and CALL "toupper", BY VALUE against BY REFERENCE, and the C library from COBOL
Open
109
Being called from C
cob_init, cob_call, a C driver of a COBOL module, and the buffer it passes
Open
110
A COBOL module for C
cobc -m, the shared object, a C program that links it, and the whole build in one shell block
Open
111
Calling COBOL from Python
ctypes over a module, a subprocess driver over stdin and stdout, and the record both sides agree on
Open
112
Messages, exit codes and logs
a message for the user, DISPLAY to standard error, RETURN-CODE, and a log line with a timestamp
Open