Fast/Unload overview: Difference between revisions

From m204wiki
Jump to navigation Jump to search
No edit summary
Line 11: Line 11:
The generated machine language performs the output function and other general-purpose manipulation.</li>
The generated machine language performs the output function and other general-purpose manipulation.</li>


<li>A reporting facility which provides a job log and statistics and file and field statistics, and reports
<li>A reporting facility which provides a job log, job statistics, file statistics, and field statistics, and reports
any special conditions or errors that might have occurred during
any special conditions or errors that might have occurred during
a run.</li>
a run.</li>

Revision as of 01:00, 10 February 2015

Fast/Unload is a utility which quickly unloads data from a Model 204 file to one or more sequential data sets. Fast/Unload consists of several functional units:

  • A data extraction facility which reads data from a Model 204 file.
  • A compiler which converts a special data language (FUEL) to machine language. The generated machine language performs the output function and other general-purpose manipulation.
  • A reporting facility which provides a job log, job statistics, file statistics, and field statistics, and reports any special conditions or errors that might have occurred during a run.

Fast/Unload can either be invoked directly as a standalone load module or from a SOUL program. When invoked as a standalone load module, Fast/Unload enqueues the data file in share mode unless explicitly requested otherwise. If the enqueue fails, the Fast/Unload terminates with an error condition code. Therefore, you must ensure that when Fast/Unload is run as a standalone load module, Model 204 does not have the file enqueued in exclusive mode.

Fast/Unload topics

Fast/Unload SOUL Interface

The Fast/Unload SOUL Interface, purchased as a separate Fast/Unload option, allows one to invoke Fast/Unload using the FastUnload or FastUnloadTask method of the Recordset class, or using the $Funload function in a SOUL program.

With this approach, an application builds a set of records to be unloaded, using standard User Language statements; for example, you can reduce unload time by restricting the set of records using indexed Model 204 fields. The Fast/Unload load module runs in a subtask (or PST under CMS) of Model 204. Since the unload is from a Model 204 record set, the Fast/Unload SOUL Interface automatically provides the ability to unload data from a Model 204 group; standalone Fast/Unload provides that functionality by allowing multiple Model 204 file names on the OPEN statement.

The Fast/Unload SOUL Interface processing can be synchronous or asynchronous.

A system manager can cancel or examine Fast/Unload requests, and each user can perform the same functions on asynchronous requests that he or she initiated.