Guardian Procedure Calls Reference Manual

Condition Code Settings
indicates that an error occurred (call FILE_GETINFO_ or FILEINFO).< (CCL)
indicates that SETSYNCINFO is successful= (CCE)
indicates that the file is not a disk file.> (CCG)
Considerations
• The SETSYNCINFO procedure cannot be used with files that are larger than approximately
2 gigabytes, including both Enscribe format 2 and OSS files. If an attempt is made to use the
SETSYNCINFO procedure with these files, error 581 is returned. For information on how to
perform the equivalent task with files larger than approximately 2 gigabytes, see the
FILE_SETSYNCINFO_ Procedure (page 516).
• Increased key limits for format 2 key-sequenced files are not supported
The SETSYNCINFO procedure does not support the increased key limits for format 2
key-sequenced files (in H06.28/J06.17 RVUs with specific SPRs and later RVUs) because it
cannot handle keys longer than 255 bytes. If SETSYNCINFO is passed a synchronization
block generated by GETSYNCINFO for a key-sequenced file with a key longer than 255
bytes, an error 41 is returned. For information on how to perform the equivalent task for
key-sequenced files with keys longer than 255 bytes, see the FILE_SETSYNCINFO_ Procedure
(page 516).
• File number has not been opened
If the SETSYNCINFO file number does not match the file number of the open file, then the call
to SETSYNCINFO is rejected with file-system error 16.
• Application parameter or buffer address out of bounds
If an out-of-bounds application buffer address parameter is specified in the SETSYNCINFO
call (that is, a pointer to the buffer has an address that is outside of the data area of the
process), then the call is rejected with file-system error 22.
• Checksum error on file sync block
If an attempt is made to modify the file-system sync buffer area, the SETSYNCINFO call is
rejected with file-system error 41.
Example
CALL SETSYNCINFO ( F1 , SYNC );
1356 Guardian Procedure Calls (S)