DataLoader/MX Reference Manual (G06.24+)

Creating a Customized Version of DataLoader/MX
DataLoader/MX Reference Manual525872-002
5-21
User Messages—C
The value returned by this procedure is the actual number of bytes written. This value
is usually the number of bytes requested to be written, but can be smaller, if writing to
a file whose record length is smaller than Len, or greater, if the file is an unstructured
file without the ODDUNST attribute and Len is odd.
If the KEYRANGE interpretation is used for output, the DTLWrite utility always calls the
BUILDKEY exit.
There are no error returns. Errors are handled by DataLoader/MX.
User Messages—C
Use these procedures to communicate with the user. In all cases, the message to be
written is specified by using the standard C print format, as indicated by
(char* Format, ... ).
DTLContinue
This procedure writes the message to the process stderr and then displays a prompt
asking if the user would like to continue. If the user indicates yes, the return value of
this procedure is nonzero. If the user indicates no, the return value of the procedure is
0 (zero).
The syntax is:
DTLFatalErr
This procedure writes the message to stderr and to stdout (unless stdout is the
same as stderr). It ignores -Q so that the message appears, at a minimum, on
stderr. After the message is written, DTLFatalErr calls the TERMINATING user exit,
passing 0 as the argument. Then it closes the error file (the -E file or stderr). Finally,
it calls exit(3). DTLFatalErr does not return.
The syntax is:
DTLPromptUser
This procedure writes a message to the process stderr and then accepts input from
the user.
short DTLContinue( char* Format, ... );
Note. Having calls to DTLFatalErr from the TERMINATING user exit is dangerous because it
can result in recursive function calls.
void DTLFatalErr( char* Format, ... );