18.08.2013 Views

LINC Programming Reference Manual - Public Support Login - Unisys

LINC Programming Reference Manual - Public Support Login - Unisys

LINC Programming Reference Manual - Public Support Login - Unisys

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

EXTRACT (EX)<br />

EXTRACT (EX)<br />

The EXTRACT; command puts the current values of data items from selected Component,<br />

Event, or Report Frame records into an Extract file.<br />

An Extract file can be read by:<br />

$ The same Report that created it<br />

$ Another Report within your <strong>LINC</strong> system<br />

$ Another <strong>LINC</strong> System (on the same host or on a different host)<br />

$ A standalone program (which may read the data into a non-<strong>LINC</strong> system)<br />

$ MAPPER (by specifying the MAPPER; command option with an EXTRACT; command)<br />

When using Extract files, consider the following points:<br />

$ Up to 26 simultaneous Extract files can be created in a Report.<br />

$ Multiple extracts involving the same Extract file append to the file. For more details,<br />

see ‘‘Multiple Extracts to the Same File’’, later in this section.<br />

$ On OS 2200 based <strong>LINC</strong> Systems, the Extract file is opened when the first EXTRACT;<br />

command is executed, and is closed when the Report terminates. Therefore the data<br />

items defined in the Extract file will not be available until the EXTRACT; command is<br />

actually executed. Using data items defined in the Extract file when the file has not<br />

been opened will cause a runtime error (in UCS). Therefore, if the EXTRACT;<br />

command is executed conditionally, use of the data items should also be conditional.<br />

$ In LDA Run Time, the PACKED BINARY and TAPE options are not implemented. The<br />

location of the extract files is determined by the Extract path field in the Report<br />

Options dialog box.<br />

$ To close the current Extract file and open another one, use the SET.TITLE; command.<br />

$ When switching from reading an Extract file to appending data to it, the first<br />

EXTRACT; command should be immediately followed by a CRITICAL.POINT;<br />

command. Failure to do this could result in duplicate records on the Extract file if the<br />

Report was aborted and automatically recovered at this point.<br />

Caution (OS 2200 based <strong>LINC</strong> Systems)<br />

On OS 2200 based runtime hosts, a maximum of 60,000 tracks will be allocated<br />

to your Extract file, as the default. If you envisage your file being larger than this,<br />

catalog the file prior to running the Report. You can increase this maximum by<br />

using the file size option within @CAT. If you pre-catalog an Extract file, it must be a<br />

permanent file.<br />

v 1-121

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

Saved successfully!

Ooh no, something went wrong!