|Revision V6.3-005||29 June 2018||
|Revision V6.3-004||23 March 2018|
|Revision V6.3-003||12 December 2017||
|Revision V6.3-001||20 March 2017||
|Revision V6.2-001||27 February 2015||
|Revision V6.1-000||28 August 2014||
|Revision V6.0-003||24 February 2014||
|Revision V6.0-001||21 March 2013||
In “EXCEPTION”, added a note about the handling of non-fatal errors.
|Revision V6.0-000||19 November 2012|
|Revision V5.5-000/1||05 October 2012|
|Revision V5.5-000||20 May 2012||In Section : “FIFO Characteristics”, corrected the description of FIFO behavior with WRITEs.|
|Revision V5.4-002B||26 December 2011||Conversion to documentation revision history reflecting GT.M releases with revision history for each chapter.|
Table of Contents
This chapter describes the following topics which relate to input and output processing:
Input/Output Intrinsic Special Variables, and their Maintenance.
GT.M provides several intrinsic special variables that allow processes to examine, and in some cases change, certain aspects of the input/output (I/O) processing. The focus in this chapter is how GT.M handles the standard ones, such as $IO, $X, $Y, and those that are GT.M-specific (for example, $ZA, $ZB).
Each device type supported by GT.M responds to a particular subset of deviceparameters, while ignoring others. Devices may be programmed in a device-specific manner, or in a device-independent manner. This chapter discusses each device type, and provides tables of their deviceparameters.
Input/Output Commands and their Deviceparameters
GT.M bases its I/O processing on a simple character stream model. GT.M does not use any pre-declared formats. This chapter describes the GT.M I/O commands OPEN, USE, READ, WRITE, and CLOSE.
OPEN, USE, and CLOSE commands accept deviceparameters, which are keywords that permit a GT.M program to control the device state. Some deviceparameters require arguments. The current ANSI standard for GT.M does not define the deviceparameters for all devices. This chapter includes descriptions of the GT.M deviceparameters in the sections describing each command.
The term "device" can refer to an entity manipulated by application code using Open, Use, Close, Read and Write commands as well as a device from the perspective of the operating system. We endeavor herein to always make it clear from the context which meaning is intended.