Fast/Unload invocation: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (→‎See also: use template)
Line 107: Line 107:
</nowiki></p>
</nowiki></p>


<p class="note"><b>Note:</b> In the above example, the Fast/Unload Extraction Language program is
<p class="note"><b>Note:</b> In the above example, the Fast/Unload Extraction Language program is in file <code>FUN FUNLOAD</code> on a CMS format disk, and the <var class="product">Model&nbsp;204</var> data file <code>SIRXREFD</code> is on an OS-format minidisk.
in file <code>FUN FUNLOAD</code> on a CMS format disk, and the <var class="product">Model 204</var> data file <code>SIRXREFD</code> is on an OS-format minidisk.


==See also==
==See also==
{{Template:Fast/Unload topic list}}
{{Template:Fast/Unload topic list}}

Revision as of 21:29, 16 April 2015

Invoking Fast/Unload as a standalone z/OS program

Fast/Unload is simply invoked via the EXEC JCL card. The program name of Fast/Unload as distributed is FUNLOAD. The following DDNAMEs are used by Fast/Unload:

  • FUNIN — This DD contains the statements used to describe the unload. FUNIN must be composed of fixed-length, 80-byte records.
  • FUNPRINT — This DD will be used as a log file and for reporting errors. This DD will also be referred to as the report data set.
  • destination — A DD is required for each of the sequential data sets (which must be unique) declared as an output stream to which records are to be unloaded. FUNOUT is the default output stream for FUEL programs written for versions prior to 4.1.

A DD statement is also required for the input Model 204 data file. The DD statement for the Model 204 file must match the internal name of the data file. In addition, if a Model 204 data file is made up of multiple physical files, DD cards must be provided for all physical files making up the logical file.

It is also recommended that you allocate either a SYSUDUMP or SYSMDUMP file to the Fast/Unload job step.

The following is an example of JCL that runs Fast/Unload in a z/OS environment.

//FUNLOAD JOB (0),CLASS=C,MSGCLASS=A,NOTIFY=HOMER //FUNLOAD EXEC PGM=FUNLOAD,REGION=1024K //STEPLIB DD DSN=M204.FUNLOAD.LOAD,DISP=SHR //SYSUDUMP DD DSN=SYSOUT=* //SIRXREFD DD DSN=ULSPF.V404.SIRXREFD,DISP=SHR //FUNOUT DD UNIT=TAPE,VOL=SER=DUMP1, // LABEL=(1,SL),DISP=(NEW,PASS), // DSN=SIRXREFD.OUTPUT,DCB=BLKSIZE=30000 //FUNPRINT DD SYSOUT=* //FUNIN DD * OPEN SIRXREFD FOR EACH RECORD PUT '*' OUTPUT PAI END FOR //

Invoking Fast/Unload as a standalone CMS program

Fast/Unload must be invoked by the Model 204 CMS interface because it uses the CMS interface's EXCP and BSAM simulation. The program name of Fast/Unload as distributed is FUNLOAD. A FILEDEF must be provided for any DD to be used by Fast/Unload. Note that because Fast/Unload uses the Model 204 CMS interface, any file can be on an OS format minidisk. The following DDNAMEs are used by Fast/Unload:

  • FUNIN — This DD contains the FUEL used to describe the unload. FUNIN must be composed of fixed length, 80 byte records.
  • FUNPRINT — This DD will be used as a log file and for reporting errors. This DD will also be referred to as the report data set.
  • destination — A DD is required for each of the sequential data sets (which must be unique) declared as an output stream to which records are to be unloaded. FUNOUT is the default output stream for FUEL programs written for versions prior to 4.1.

A FILEDEF statement is also required for the input Model 204 data file. The FILEDEF statement for the Model 204 file must match the internal name of the data file. In addition, if a Model 204 data file is made up of multiple physical files, FILEDEF commands must be provided for all physical files making up the logical file.

The following is an example of an EXEC that runs Fast/Unload in a CMS environment. Note that while REXX is used here, the EXEC could be written in EXEC or EXEC2.

/* Exec to run Fast/Unload */ Address command; 'FILEDEF * CLEAR'; 'FILEDEF FUNIN DISK FUN FUNLOAD A'; 'FILEDEF FUNPRINT DISK FUN LISTING A', '(RECFM VB LRECL 137 BLOCK 4096'; 'FILEDEF FUNOUT TAP1 (LRECL 10000 BLOCK 30000 RECFM VB'; 'FILEDEF SIRXREFD I DSN ULSPF V404 SIRXREFD'; 'M204CMS FUNLOAD'; Exit rc;

Note: In the above example, the Fast/Unload Extraction Language program is in file FUN FUNLOAD on a CMS format disk, and the Model 204 data file SIRXREFD is on an OS-format minidisk.

See also

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=Fast/Unload_invocation&oldid=77067"