Fast/Unload invocation: Difference between revisions
m (more conversion cleanup) |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
<!-- Page name: Fast/Unload invocation--> | <!-- Page name: Fast/Unload invocation--> | ||
<div id="invkmvs"></div> | <div id="invkmvs"></div> | ||
==Invoking Fast/Unload as a standalone z/OS program== | ==Invoking Fast/Unload as a standalone z/OS program== | ||
| Line 7: | Line 8: | ||
<var class="product">Fast/Unload</var> is simply invoked via the EXEC JCL card. | <var class="product">Fast/Unload</var> is simply invoked via the EXEC JCL card. | ||
The program name | The program name | ||
of <var class="product">Fast/Unload</var> as distributed is | of <var class="product">Fast/Unload</var> as distributed is FUNLOAD. | ||
The following DDNAMEs are used | The following DDNAMEs are used | ||
by <var class="product">Fast/Unload</var>: | by <var class="product">Fast/Unload</var>: | ||
<ul> | <ul> | ||
<li | <li>FUNIN — This DD contains the statements used to describe the unload. | ||
FUNIN must be composed of fixed | FUNIN | ||
must be composed of fixed length, 80 byte records. | |||
<li | <li>FUNPRINT — This DD will be used as a log file and for reporting errors. | ||
This DD will also be referred to as the <b>report data set</b>. | This DD will also be referred to as the <b>report data set</b>. | ||
<li><i>destination</i> — | <li><i>destination</i> — | ||
A DD is required for each of the sequential data sets (which must be unique) | 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. | 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. | versions prior to 4.1. | ||
</ul> | </ul> | ||
<p></p> | |||
A DD statement is also required for the input <var class="product">Model 204</var> data file. | A DD statement is also required for the input <var class="product">Model 204</var> data file. | ||
The DD statement for the <var class="product">Model 204</var> file <b>must</b> match the internal | The DD | ||
statement for the <var class="product">Model 204</var> file <b>must</b> match the internal | |||
name of the data file. | name of the data file. | ||
In addition, if a <var class="product">Model 204</var> data file is made up | In addition, if a <var class="product">Model 204</var> data file is made up | ||
of multiple physical files, DD cards must be provided for all physical | of multiple physical files, DD cards must be provided for all physical | ||
files making up the logical file. | files making up the logical file. | ||
<p></p> | |||
It is also recommended that you allocate either a | It is also recommended that you allocate either a SYSUDUMP or SYSMDUMP | ||
file to the <var class="product">Fast/Unload</var> job step. | file to the <var class="product">Fast/Unload</var> job step. | ||
<p></p> | |||
<p></p> | |||
The following is an example of JCL that runs <var class="product">Fast/Unload</var> in a z/OS | The following is an example of JCL that runs <var class="product">Fast/Unload</var> in a z/OS | ||
environment | environment. | ||
<p class="code"><nowiki>//FUNLOAD JOB (0),CLASS=C,MSGCLASS=A,NOTIFY=HOMER | <p class="code"><nowiki>//FUNLOAD JOB (0),CLASS=C,MSGCLASS=A,NOTIFY=HOMER | ||
//FUNLOAD EXEC PGM=FUNLOAD,REGION=1024K | //FUNLOAD EXEC PGM=FUNLOAD,REGION=1024K | ||
| Line 59: | Line 61: | ||
<!--Caution: <div> above--> | <!--Caution: <div> above--> | ||
<p></p> | |||
<var class="product">Fast/Unload</var> must be invoked by the <var class="product">Model 204</var> CMS interface because | <var class="product">Fast/Unload</var> must be invoked by the <var class="product">Model 204</var> CMS interface because | ||
it uses the CMS interface's EXCP and BSAM simulation. | it uses the CMS interface's EXCP and BSAM simulation. | ||
The program name | The program name | ||
of <var class="product">Fast/Unload</var> as distributed is | of <var class="product">Fast/Unload</var> as distributed is FUNLOAD. | ||
A FILEDEF must be provided for any DD to be used by <var class="product">Fast/Unload</var>. | A FILEDEF must be provided for any DD to be used by <var class="product">Fast/Unload</var>. | ||
Note that | |||
because <var class="product">Fast/Unload</var> uses the <var class="product">Model 204</var> CMS interface, any file | |||
can be on an OS format minidisk. | |||
The following DDNAMEs are used by <var class="product">Fast/Unload</var>: | The following DDNAMEs are used by <var class="product">Fast/Unload</var>: | ||
<ul> | <ul> | ||
<li | <li>FUNIN - This DD contains the FUEL used to describe the unload. | ||
FUNIN must | |||
be composed of fixed length, 80 byte records. | |||
<li | <li>FUNPRINT - This DD will be used as a log file and for reporting errors. | ||
This DD will also be referred to as the <b>report data set</b>. | This DD will also be referred to as the <b>report data set</b>. | ||
<li><i>destination</i> - | |||
<li><i>destination</i> | |||
A DD is required for each of the sequential data sets (which must be unique) | 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. | 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. | versions prior to 4.1. | ||
</ul> | </ul> | ||
<p></p> | |||
A FILEDEF statement is also required for the input <var class="product">Model 204</var> data file. | A FILEDEF statement is also required for the input <var class="product">Model 204</var> data file. | ||
The FILEDEF statement for the <var class="product">Model 204</var> file <b>must</b> match the internal | The | ||
FILEDEF statement for the <var class="product">Model 204</var> file <b>must</b> match the internal | |||
name of the data file. | name of the data file. | ||
In addition, if a <var class="product">Model 204</var> data file is made up | In addition, if a <var class="product">Model 204</var> data file is made up | ||
of multiple physical files, FILEDEF commands must be provided for all physical | of multiple physical files, FILEDEF commands must be provided for all physical | ||
files making up the logical file. | files making up the logical file. | ||
<p></p> | |||
<p></p> | |||
The following is an example of an EXEC that runs <var class="product">Fast/Unload</var> in a CMS | The following is an example of an EXEC that runs <var class="product">Fast/Unload</var> in a CMS | ||
environment. | environment. | ||
| Line 104: | Line 108: | ||
Exit rc; | Exit rc; | ||
</nowiki></p> | </nowiki></p> | ||
Note that in the above example the <var class="product">Fast/Unload</var> Extraction Language program is | |||
< | in file FUN FUNLOAD on a CMS format disk and the <var class="product">Model 204</var> data file | ||
in file | SIRXREFD is on an OS format minidisk. | ||
==See also== | ==See also== | ||
[[Fast/Unload overview#WIKFUN$$topics|Fast/Unload topics]] | [[Fast/Unload overview#WIKFUN$$topics|Fast/Unload topics]] | ||
Revision as of 19:39, 15 January 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 <var class="product">Fast/Unload</var> */ 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 that 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.