Guardian Programmer's Guide

Table Of Contents
Mixed Data Model Programming
Guardian Programmer’s Guide 421922-014
A - 4
Data Scanning and Movement within 64-bit
Segments
For more information on pool routines, see Guardian Procedure Calls Reference
Manual. The POOL64_* routines are available in H06.20, J06.09 and subsequent
RVUs. All TNS/E C/C++ compilers support the necessary 64-bit addressing constructs.
The epTAL compiler supporting 64-bit addressing is available as of H06.23 and J06.12;
the constructs must be enabled using the __EXT64 directive. The KPOOL64 header
file, for use with epTAL, is available as of H06.24 and J06.13.
Data Scanning and Movement within 64-bit Segments
C/C++ programs can move data to, from and within a 64-bit segment using functions
defined in string.h. These routines accept 64-bit pointer arguments and data
lengths. Those that return a pointer, return a 64-bit pointer. The 64-bit capable
functions have names that are formed from their standard C counterparts by
appending '64'. For example, the 64-bit capable version of memcpy() is named
memcpy64(). These functions are available in H06.22, J06.11 and subsequent RVUs.
epTAL programs can use the normal data scanning or movement constructs with 64-bit
pointers.
File I/O to/from 64-bit Segments
Guardian programs can perform I/O operations directly to and from 64-bit segments
using 64-bit Guardian I/O procedures. These procedures are:
CANCELREQL
FILE_AWAITIO64_
FILE_COMPLETEL_
FILE_CONTROL64_
FILE_CONTROLBUF64_
FILE_LOCKFILE64_
FILE_LOCKREC64_
FILE_READ64_
FILE_READLOCK64_
FILE_READUPDATE64_
FILE_READUPDATELOCK64_
FILE_REPLY64_
FILE_SETMODENOWAIT64_
FILE_UNLOCKFILE64_
FILE_UNLOCKREC64_
FILE_WRITE64_