24.05.2014 Views

XL Fortran Enterprise Edition for AIX : User's Guide - IBM

XL Fortran Enterprise Edition for AIX : User's Guide - IBM

XL Fortran Enterprise Edition for AIX : User's Guide - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Note: You may need the old setting to read existing data files that contain<br />

NAMELIST output.However, use the standard-compilant new <strong>for</strong>mat in<br />

writing any new data files.<br />

With namelist=old, the nonstandard NAMELIST <strong>for</strong>mat is not considered an<br />

error by the langlvl=95std, langlvl=90std, or langlvl=2003std setting.<br />

Related In<strong>for</strong>mation: For more in<strong>for</strong>mation about NAMELIST I/O, see<br />

Namelist Formatting in the <strong>XL</strong> <strong>Fortran</strong> <strong>Enterprise</strong> <strong>Edition</strong><br />

<strong>for</strong> <strong>AIX</strong> Language Reference.<br />

nlwidth=record_width<br />

By default, a NAMELIST write statement produces a single output record long<br />

enough to contain all of the written NAMELIST items. To restrict NAMELIST<br />

output records to a given width, use the nlwidth run-time option.<br />

Note: The RECL= specifier <strong>for</strong> sequential files has largely made this option<br />

obsolete, because programs attempt to fit NAMELIST output within the<br />

specified record length. You can still use nlwidth in conjunction with<br />

RECL= as long as the nlwidth width does not exceed the stated record<br />

length <strong>for</strong> the file.<br />

random={generator1 | generator2}<br />

Specifies the generator to be used by RANDOM_NUMBER if<br />

RANDOM_SEED has not yet been called with the GENERATOR argument.<br />

The value generator1 (the default) corresponds to GENERATOR=1, and<br />

generator2 corresponds to GENERATOR=2. If you call RANDOM_SEED with<br />

the GENERATOR argument, it overrides the random option from that point<br />

onward in the program. Changing the random option by calling SETRTEOPTS<br />

after calling RANDOM_SEED with the GENERATOR option has no effect.<br />

scratch_vars={yes | no}<br />

To give a specific name to a scratch file, set the scratch_vars run-time option to<br />

yes, and set the environment variable <strong>XL</strong>FSCRATCH_unit to the name of the<br />

file you want to be associated with the specified unit number. See “Naming<br />

Scratch Files” on page 332 <strong>for</strong> examples.<br />

unit_vars={yes | no}<br />

To give a specific name to an implicitly connected file or to a file opened with<br />

no FILE= specifier, you can set the run-time option unit_vars=yes and set one<br />

or more environment variables with names of the <strong>for</strong>m <strong>XL</strong>FUNIT_unit to file<br />

names. See “Naming Files That Are Connected with No Explicit Name” on<br />

page 331 <strong>for</strong> examples.<br />

uwidth={32 | 64}<br />

To specify the width of record length fields in un<strong>for</strong>matted sequential files,<br />

specify the value in bits. When the record length of an un<strong>for</strong>matted sequential<br />

file is greater than (2**31 - 1) bytes minus 8 bytes (<strong>for</strong> the record terminators<br />

surrounding the data), you need to set the run-time option uwidth=64 to<br />

extend the record length fields to 64 bits. This allows the record length to be<br />

up to (2**63 - 1) minus 16 bytes (<strong>for</strong> the record terminators surrounding the<br />

data). The run-time option uwidth is only valid <strong>for</strong> 64-bit mode applications.<br />

xrf_messages={yes | no}<br />

To prevent programs from displaying run-time messages <strong>for</strong> error conditions<br />

during I/O operations, RANDOM_SEED calls, and ALLOCATE or<br />

DEALLOCATE statements, set the xrf_messages run-time option to no.<br />

Otherwise, run-time messages <strong>for</strong> conversion errors and other problems are<br />

sent to the standard error stream.<br />

58 <strong>XL</strong> <strong>Fortran</strong> <strong>Enterprise</strong> <strong>Edition</strong> <strong>for</strong> <strong>AIX</strong> : User’s <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!