Fast/Unload overview: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (add note)
m (→‎Fast/Unload topics: use template)
Line 36: Line 36:
support in each of the recent <var class="product">Fast/Unload</var> versions, see the [[M204wiki main page#Release notes, wishlists, and punch lists|release notes]].  
support in each of the recent <var class="product">Fast/Unload</var> versions, see the [[M204wiki main page#Release notes, wishlists, and punch lists|release notes]].  


<ul>
{{Template: Fast/Unload topic list}}
<li>[[Fast/Unload invocation]]
<li>[[Fast/Unload program parameters]]
<li>[[Fast/Unload Extraction Language (FUEL)]]
<li>[[Fast/Unload standard functions|Fast/Unload standard #functions]]
<li>[[Fast/Unload BLOB/CLOB processing considerations]]
<li>[[Fast/Unload datetime processing considerations]]
<li>[[Fast/Unload DATESTAT analysis]]
<li>[[Fast/Unload job statistics]]
<li>[[Fast/Unload SOUL Interface]] ([[#fusi|see below]] for a brief description)
<li>[[Fast/Unload with an external sort package]]
<li>[[Fast/Unload with DBCS data]]
<li>[[Fast/Unload customer-written assembler function packages|Fast/Unload customer-written assembler #function packages]]
<li>[[Fast/Unload user exits or filters]]
<li>[[Fast/Unload with Model 204 file groups]]
<li>[[Fast/Unload with the Sir2000 Field Migration Facility]]
<li>[[Fast/Unload floating point arithmetic and numeric conversion]]
<li>[[Fast/Unload program return codes]]
<li>[[Fast/Unload installation]]
<li>[[Fast/Unload customization of defaults]]
<li>[[Fast/Unload SMF record format]]
</ul>


<div id="fusi"></div>
<div id="fusi"></div>
==Fast/Unload SOUL Interface==
==Fast/Unload SOUL Interface==
<!--Caution: <div> above-->
<!--Caution: <div> above-->

Revision as of 19:37, 11 March 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.

Note: As of version 4.6, Fast/Unload must be running under z/OS or z/VM CMS.

Fast/Unload topics

The Fast/Unload documentation consists of the pages listed below. This list is also available as a "See also" link from each of the pages. For information about the product changes and Model 204 feature support in each of the recent Fast/Unload versions, see the release notes.

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.