NET/MASTER Network Control Language (NCL) Reference Manual

FILE PUTGET
Verbs
106126 Tandem Computers Incorporated 3–99
Considerations
The &SYS.FILE.RC system variable reflects the result of all file operations within
NCL. NCL sets this variable on completion of the FILE PUTGET verb as follows:
Return Code Meaning
0 PUTGET completed successfully.
4 End-of-file detected.
8 A file system error occurred during processing. Further information is contained
in the &SYS.FILE.ERROR system variable.
12 Not used.
16 An error occurred. Further information is contained in &SYSMSG.
It is the user’s responsibility to test the &SYS.FILE.RC system variable for errors.
There is an implicit resumption of the NCL procedure after any errors, unless the
user has coded an error handler for the FILE_ERROR condition. See the core
statements ON and RESUME in Section 2, “Core Statements.”
For return codes other than 0 (zero) and 4, the FILE_ERROR condition is signalled.
This condition can be trapped (or intercepted) by an error handler.
See also FILE OPEN, FILE PUT, and FILE SET.
FILE PUTGET works in the same way as the Guardian WRITEREAD procedure
call. Refer to the Guardian Programmer’s Guide for more information on
WRITEREAD.
When reading files that are described by user-defined maps, NCL converts data
from an internal to an external format. A conversion takes place in the opposite
direction when such files are written. For more information on user-defined maps
and on the data conversion that occurs when a FILE verb is used to process files
described by user-defined maps, refer to the NonStop NET/MASTER NCL
Programmer's Guide.
Example
The following example sends a REQUEST INFO message to a server process ($SERV)
and stores the response in the variable &RESPONSE:
FILE OPEN ID=$SERV FORMAT=UNMAPPED
FILE PUTGET DATA="REQUEST INFO" TO VARS=&RESPONSE