CRE Programmer's Guide

CRE Service Functions
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
6-22
CRE_File_Retrycheck_
•
A negative number, which is the negation of a CRE error number from the following
table:
Considerations
•
If the file referenced by file_ordinal is a spooler collector, the current spooling
state is either buffered spooling or undecided spooling, and the spooler has not
been initialized, CRE_File_Output_ calls the CRE_Spool_Start_ procedure.
•
If the file referenced by file_ordinal is a spooler collector open for level-3
spooling, CRE_File_Output_ calls SPOOLWRITE.
•
If file_ordinal specifies a null file—that is, CRE_File_Open_ has been called
and has granted one or more connections to the file but an operating system file
was not opened— CRE_File_Output_ sets
count_written to the value specified
in
write_count, and returns 0 as the value of the function.
•
If the file was opened by a call to the OPENEDIT system procedure,
CRE_File_Output_ calls the WRITEEDIT system procedure.
•
In all other cases, CRE_File_Output_ calls the WRITEX system procedure to write
the contents of
buffer.
•
CRE_File_Output_ does not retry operations that return an error.
CRE_File_Retrycheck_
The CRE_File_Retrycheck_ function determines whether an I/O operation that
completed with an operating system error should be retried.
file_ordinal
identifies the standard file for which to check for a retryable operation. You can use
the following symbolic names for
file_ordinal:
CRE^Standard^Input
CRE^Standard^Output
CRE^Standard^Log
Error Code Cause
55 Missing or invalid parameter
57 Parameter value not accepted
63 Undefined shared file
64 File not open
INT PROC CRE_File_Retrycheck_( file_ordinal, error )
EXTENSIBLE;
INT file_ordinal; ! in, required
INT error; ! in, optional TNS,native