18.08.2013 Views

(SYSLIB) Programming Reference Manual - Public Support Login ...

(SYSLIB) Programming Reference Manual - Public Support Login ...

(SYSLIB) Programming Reference Manual - Public Support Login ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SAR$ WRITE<br />

Table 18–3. SAR$: WRITE Procedure CALL_STATUS Codes<br />

Octal Code Status<br />

011 The value for OUTPUT_BUFFER_WORD_LENGTH is too small; use the word<br />

length returned in RECOMMENDED_BUFFER_LENGTH.<br />

012 An I/O error has occurred in a WRITE procedure. See the IO_STATUS_CODE<br />

field for the status code and Table 18–4.<br />

013 An invalid value is specified for OUTPUT_RECORD_TYPE.<br />

014 An incorrect ACD subroutine version is being used with SAR$.<br />

015 The attribute table contains an index that is either zero, not in sequential<br />

order, or greater than the text length.<br />

016 The attribute table contains an invalid attribute type or an invalid value for the<br />

attribute type.<br />

017 An illegal character set type is specified for the<br />

OUTPUT_IMAGE_CHARACTER_TYPE.<br />

020 Line numbers are not allowed for this output file type.<br />

021 The WRITE packet is not initialized; a call to SAR_OPEN_OUTPUT must be<br />

made before calls to SAR_WRITE, SAR_WRITE_CONTROL, or<br />

SAR_CLOSE_OUTPUT.<br />

022 The image buffer has overflowed; use the word length in<br />

RECOMMENDED_BUFER_LENGTH for IMAGE_BUFFER_WORD_LENGTH<br />

and call SAR_WRITE again.<br />

024 An error has occurred in adding the element to the table of contents; see the<br />

SUB_STATUS_CODE field for the ER PFI$ status code and the Exec ER<br />

<strong>Programming</strong> <strong>Reference</strong> <strong>Manual</strong>.<br />

026 An error has occurred in executing the symbiont file closing breakpoint; see<br />

the SUB_STATUS_CODE field for the ER CSF$ status code returned for<br />

@SYM and @BRKPT in dynamically submitted control statements in the Exec<br />

ER <strong>Programming</strong> <strong>Reference</strong> <strong>Manual</strong>.<br />

027 SDF control records cannot be written to this output file type.<br />

030 Symbiont write control records cannot be written to this output file type.<br />

031 The file name buffer address in the FIP is NULL; an address of an SDF file<br />

name must be specified.<br />

032 The file name buffer address in the FIP is NULL; an address of a symbiont file<br />

name must be specified.<br />

033 The element name buffer address in the FIP is NULL; an address of an SDF<br />

element name must be specified.<br />

034 An illegal value is specified for the file name buffer byte length; legal values<br />

are from 1 to 12.<br />

035 An illegal value is specified for the element name buffer byte length; legal<br />

values are from 1 to 12.<br />

036 An illegal value is specified for the version name buffer byte length; legal<br />

values are from 1 to 12.<br />

18–20 7833 1733–004

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!