WRITE

• A variable name. An array is treated as if all of its elements were specified in the order in which they are arranged in storage.

  A pointer must be associated with a target, and an allocatable object must be allocated. A derived-type object cannot have any ultimate component that is outside the scoping unit of this statement. The evaluation of output_item cannot result in a derived-type object that contains a pointer. The structure components of a structure in a formatted statement are treated as if they appear in the order of the derived-type definition; in an unformatted statement, the structure components are treated as a single value in their internal representation (including padding).

• An expression
• An implied-DO list, as described under Implied-DO List

An output_item must not be a procedure pointer.

An internal file identifier refers to an internal file. It is the name of a character variable, which cannot be an array section with a vector subscript.

If the optional characters UNIT= are omitted, u must be the first item in io_control_list. If UNIT= is specified, FMT= must also be specified.

• The statement label of a FORMAT statement. The FORMAT statement must be in the same scoping unit.
• The name of a scalar INTEGER(4) or INTEGER(8) variable that was assigned the statement label of a FORMAT statement. The FORMAT statement must be in the same scoping unit.

  Fortran 95 does not permit assigning of a statement label.

• A character constant enclosed in parentheses. Only the format codes listed under FORMAT can be used between the parentheses. Blank characters can precede the left parenthesis or follow the right parenthesis.
• A character variable that contains character data whose leftmost character positions constitute a valid format. A valid format begins with a left parenthesis and ends with a right parenthesis. Only the format codes described in the FORMAT statement can be used between the parentheses. Blank characters can precede the left parenthesis or follow the right parenthesis. If format is an array element, the format identifier must not exceed the length of the array element.
• An array of noncharacter intrinsic type. The data must be a valid format identifier as described under character array.
• Any character expression, except one involving concatenation of an operand that specifies inherited length, unless the operand is the name of a constant.
• An asterisk, specifying list-directed formatting.
• A namelist specifier that specifies the name of a namelist list that you have previously defined.

If the optional characters FMT= are omitted, format must be the second item in io_control_list, and the first item must be the unit specifier with UNIT= omitted. NML= and FMT= cannot both be specified in the same output statement.

char_expr is a scalar character expression whose value is either YES or NO. YES specifies that asynchronous data transfer statements are permitted for this connection. NO specifies that asynchronous data transfer statements are not permitted for this connection. The value specified will be in the set of transfer methods permitted for the file. If this specifier is omitted, the default value is NO.

Preconnected units are connected with an ASYNCH= value of NO.

The ASYNCH= value of an implicitly connected unit is determined by the first data transfer statement performed on the unit. If the first statement performs an asynchronous data transfer and the file being implicitly connected permits asynchronous data transfers, the ASYNCH= value is YES. Otherwise, the ASYNCH= value is NO.

A statement and the I/O operation are synchronous if ASYNCHRONOUS=NO or if both ASYNCHRONOUS= and ID= are absent. For ASYNCHRONOUS=YES or if ID= appears, asynchronous I/O is permitted only for external files opened with ASYNCHRONOUS=YES in the OPEN statement.

If a variable is used in an asynchronous data transfer statement as an item in an I/O list, a group object in a namelist or as a SIZE= specifier, the base object of the data_ref is implicitly given the ASYNCHRONOUS attribute in the scoping unit of the data transfer statement. For asynchronous nonadvancing input, the storage units specified in the SIZE= specifier become defined with the count of the characters transferred when the corresponding wait operation is executed. For asynchronous output, a pending I/O storage sequence affector shall not be redefined, become undefined, or have its pointer association status changed. For asynchronous input, a pending I/O storage sequence affector shall not be referenced, become defined, become undefined, become associated with a dummy argument that has the VALUE attribute, or have its pointer association status changed.

When an error, end-of-file or end-of-record condition occurs for a previously executed asynchronous data transfer statement , a wait operation is performed for all pending data transfer operations on that unit. When a condition occurs during a subsequent statement, any actions specified by IOSTAT=, IOMSG=, ERR=, END=, and EOR= specifiers for that statement are taken.

A wait operation is performed by a WAIT, CLOSE, or file positioning statement.

temporarily changes the current value of the I/O rounding mode for the duration of this I/O statement. If omitted, then the rounding mode is unchanged. char-expr evaluates to either UP, DOWN, ZERO, NEAREST, COMPATIBLE or PROCESSOR_DEFINED

The rounding mode helps specify how decimal numbers are converted to an internal representation, (that is, in binary) from a character representation and vice versa during formatted input and output. The rounding modes have the following functions:

• In the UP rounding mode the value from the conversion is the smallest value that is greater than or equal to the original value.
• In the DOWN rounding mode the value from the conversion is the greatest value that is smaller than or equal to the original value.
• In the ZERO rounding mode the value from the conversion is the closest value to the original value, and not greater in magnitude.
• In the NEAREST rounding mode the value from the conversion is the closer of the two nearest representable values. If both values are equally close then the even value will be chosen. In IEEE rounding conversions, NEAREST corresponds to the ieee_nearest rounding mode as specified by the IEEE standard.
• In the COMPATIBLE rounding mode the value from the conversion is the closest of the two nearest representable values, or the value further away from zero if halfway between.
• In the PROCESSOR_DEFINED rounding mode the value from the conversion is processor dependent and may correspond to the other modes. In the PROCESSOR_DEFINED rounding mode the value from the conversion is processor dependent and may correspond to the other modes. In XL Fortran, the PROCESSOR_DEFINED rounding mode will be the rounding mode you choose in the floating-point control register. If you do not set the floating-point control register explicitly, the default rounding mode is NEAREST.

• If an error, end-of-file, or end-of-record condition occurs, the variable is assigned an explanatory message as if by assignment.
• If no such condition occurs, the value of the variable is unchanged.

• A zero value if no error condition occurs
• A positive value if an error occurs.

Asynchronous data transfer must either be direct unformatted, sequential unformatted, or stream unformatted. Asynchronous I/O to internal files is prohibited. Asynchronous I/O to raw character devices (for example, tapes or raw logical volumes) is prohibited. The integer_variable must not be associated with any entity in the data transfer I/O list, or with a do_variable of an io_implied_do in the data transfer I/O list. If the integer_variable is an array element reference, its subscript values must not be affected by the data transfer, the io_implied_do processing, or the definition or evaluation of any other specifier in the io_control_spec.