Fast/Unload invocation - Revision history

JAL: move ID

2017-11-15T17:42:18Z

move ID

← Older revision		Revision as of 17:42, 15 November 2017
Line 33:		Line 33:
	files making up the logical file. </li>		files making up the logical file. </li>

	<b id="ccadd"~~></b>~~		<li id="ccadd"><b>SYSUDUMP</b> or <b>SYSMDUMP</b>
	~~<li~~><b>SYSUDUMP</b> or <b>SYSMDUMP</b>
	<ul>		<ul>
	<li>Prior to version 7.7:		<li>Prior to version 7.7:

Dme: /* DD names */

2017-01-26T19:31:35Z

DD names

← Older revision		Revision as of 19:31, 26 January 2017
Line 33:		Line 33:
	files making up the logical file. </li>		files making up the logical file. </li>

			<b id="ccadd"></b>
	<li><b>SYSUDUMP</b> or <b>SYSMDUMP</b>		<li><b>SYSUDUMP</b> or <b>SYSMDUMP</b>
	<ul>		<ul>
Line 45:		Line 46:
	</ul>		</ul>

	~~<p id="ccadd">~~		As of the version 7.7 integration of Fast/Unload with the Online load module, these additional DD names can be used with PGM=FUNLOAD for possible problem diagnosis by Rocket Technical Support. They are not required.
	As of the version 7.7 integration of Fast/Unload with the Online load module, these additional DD names can be used with PGM=FUNLOAD for possible problem diagnosis by Rocket Technical Support. They are not required. ~~</p>~~
	<ul>		<ul>
	<li><b>CCASNAP </b> —		<li><b>CCASNAP </b> —

JAL: /* Invoking Fast/Unload under z/OS */ single word change: "installed" replaces "invoked"

2016-09-12T19:12:29Z

Invoking Fast/Unload under z/OS: single word change: "installed" replaces "invoked"

← Older revision		Revision as of 19:12, 12 September 2016
Line 1:		Line 1:
	==<b id="invkmvs"></b>Invoking Fast/Unload under z/OS==		==<b id="invkmvs"></b>Invoking Fast/Unload under z/OS==
	For versions of <var class="product">Fast/Unload</var> through 4.7, the product is ~~invoked~~ as a standalone z/OS program. As of the next version after 4.7, <i>numbered 7.7</i> to associate it to Model 204 version 7.7, the product is integrated with the Model 204 Online load module and invoked as part of the integrated load module.		For versions of <var class="product">Fast/Unload</var> through 4.7, the product is installed as a standalone z/OS program. As of the next version after 4.7, <i>numbered 7.7</i> to associate it to Model 204 version 7.7, the product is integrated with the Model 204 Online load module and invoked as part of the integrated load module.

	Regardless of product version, <var class="product">Fast/Unload</var> is invoked with the EXEC JCL card, and its		Regardless of product version, <var class="product">Fast/Unload</var> is invoked with the EXEC JCL card, and its

JAL: misc formatting

2016-09-12T19:00:58Z

misc formatting

← Older revision		Revision as of 19:00, 12 September 2016
Line 49:		Line 49:
	<ul>		<ul>
	<li><b>CCASNAP </b> —		<li><b>CCASNAP </b> —
	If Fast/Unload encounters an abend, a Model 204 snap is created and sent to the CCASNAP DD. Since this is key to diagnosing many problems, Fast/Unload ensures that the DD name is allocated (to SYSOUT=A) if it has not been provided. </li>		If Fast/Unload encounters an abend, a Model 204 snap is created and sent to the <code>CCASNAP</code> DD. Since this is key to diagnosing many problems, Fast/Unload ensures that the DD name is allocated (to <code>SYSOUT=A</code>) if it has not been provided. </li>

	<li><b>CCAAUDIT</b> —		<li><b>CCAAUDIT</b> —
	You can capture the normal Model 204 audit trail if you provide a CCAAUDIT DD. This is a small file (generally less than 100 records) and the information is usually not important, but it might be helpful for problem diagnosis.		You can capture the normal Model 204 audit trail if you provide a <code>CCAAUDIT</code> DD. This is a small file (generally less than 100 records) and the information is usually not important, but it might be helpful for problem diagnosis.

	<li><b>CCAPRINT</b> —		<li><b>CCAPRINT</b> —
	You can capture the normal Model 204 file for initialization		You can capture the normal Model 204 file for initialization
	if you provide a CCAPRINT DD. This is a small file (generally less than 50 records) and the information is usually not important, but it might be helpful for problem diagnosis. You should be able to define this as a SYSOUT file.		if you provide a <code>CCAPRINT</code> DD. This is a small file (generally less than 50 records) and the information is usually not important, but it might be helpful for problem diagnosis. You should be able to define this as a SYSOUT file.
	</ul>		</ul>

JAL: misc formatting

2016-09-12T18:57:46Z

misc formatting

← Older revision		Revision as of 18:57, 12 September 2016
Line 6:		Line 6:
	<p class="code">// EXEC PGM=FUNLOAD </p>		<p class="code">// EXEC PGM=FUNLOAD </p>

	===~~DDnames~~===		===DD names===
	The following ~~DDnames~~ are used by <var class="product">Fast/Unload</var>:		The following DD names are used by <var class="product">Fast/Unload</var>:
	<ul>		<ul>
	<li><b>FUNIN</b> — This DD contains the statements used to describe the unload.		<li><b>FUNIN</b> — This DD contains the statements used to describe the unload.
Line 32:		Line 32:
	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		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
	files making up the logical file. </li>		files making up the logical file. </li>
	~~</ul>~~

	~~Prior to version 7.7, it is recommended that you allocate either~~ SYSUDUMP or ~~SYSMDUMP to the~~ <~~var class="product"~~>~~Fast/Unload~~</~~var~~> ~~job step:~~		<li><b>SYSUDUMP</b> or <b>SYSMDUMP</b>
	<ul>		<ul>
	<li><b>SYSUDUMP</b> or <b>SYSMDUMP</b>		<li>Prior to version 7.7:
	</li>		<p>
			It is recommended that you allocate either <code>SYSUDUMP</code> or <code>SYSMDUMP</code> to the <var class="product">Fast/Unload</var> job step. </p></li>

			<li>As of version 7.7:
			<p>
			<i>Do not use <code>SYSUDUMP</code></i>. <code>SYSMDUMP</code> is still useful. </p></li>
			</ul></li>
	</ul>		</ul>

Line 52:		Line 57:
	You can capture the normal Model 204 file for initialization		You can capture the normal Model 204 file for initialization
	if you provide a CCAPRINT DD. This is a small file (generally less than 50 records) and the information is usually not important, but it might be helpful for problem diagnosis. You should be able to define this as a SYSOUT file.		if you provide a CCAPRINT DD. This is a small file (generally less than 50 records) and the information is usually not important, but it might be helpful for problem diagnosis. You should be able to define this as a SYSOUT file.

	~~<li><b>SYSMDUMP</b> —~~
	~~This can still be useful with version 7.7 but <code>SYSUDUMP</code> should no longer be used.~~
	~~</li>~~
	</ul>		</ul>

Line 79:		Line 80:
	</nowiki></p>		</nowiki></p>

	The same JCL can be used for version 7.7 and later except ~~for a change to~~ the load library, something like the following ~~which references~~ the integrated Model 204 library:		The same JCL can be used for version 7.7 and later, except:
			<ul>
			<li>Change the load library. Use something like the following to reference the integrated Model 204 library:
	<p class="code">//STEPLIB DD DISP=SHR,DSN=M204.V77.LOADLIB		<p class="code">//STEPLIB DD DISP=SHR,DSN=M204.V77.LOADLIB
	</p>		</p></li>

	<~~div id="invkcms"~~></~~div~~>		<li>Consider using the additional [[#ccadd\|optional 7.7 DD statements]]. </li>
			</ul>

	==Invoking Fast/Unload as a standalone CMS program==		==<b id="invkcms"></b>Invoking Fast/Unload as a standalone CMS program==
	~~<!--Caution: <div> above-->~~

	<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.

Dme: /* DDnames */

2016-09-10T12:40:47Z

DDnames

← Older revision		Revision as of 12:40, 10 September 2016
Line 52:		Line 52:
	You can capture the normal Model 204 file for initialization		You can capture the normal Model 204 file for initialization
	if you provide a CCAPRINT DD. This is a small file (generally less than 50 records) and the information is usually not important, but it might be helpful for problem diagnosis. You should be able to define this as a SYSOUT file.		if you provide a CCAPRINT DD. This is a small file (generally less than 50 records) and the information is usually not important, but it might be helpful for problem diagnosis. You should be able to define this as a SYSOUT file.

			<li><b>SYSMDUMP</b> —
			This can still be useful with version 7.7 but <code>SYSUDUMP</code> should no longer be used.
			</li>
	</ul>		</ul>

Dme: /* DDnames */

2016-09-10T12:19:32Z

DDnames

← Older revision		Revision as of 12:19, 10 September 2016
Line 32:		Line 32:
	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		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
	files making up the logical file. </li>		files making up the logical file. </li>
			</ul>

	~~<li><b>SYSUDUMP</b> or <b>SYSMDUMP</b> —~~		Prior to version 7.7, it is recommended that you allocate either SYSUDUMP or SYSMDUMP to the <var class="product">Fast/Unload</var> job step:
	It is recommended that you allocate either ~~of these files~~ to the <var class="product">Fast/Unload</var> job step. </li>		<ul>
			<li><b>SYSUDUMP</b> or <b>SYSMDUMP</b>
			</li>
	</ul>		</ul>

	<p id="ccadd">		<p id="ccadd">
	As of the version 7.7 integration of Fast/Unload with the Online load module, these additional DD names can be used with PGM=FUNLOAD for possible problem diagnosis by Rocket Technical Support. They are not required. </p>		As of the version 7.7 integration of Fast/Unload with the Online load module, these additional DD names can be used with PGM=FUNLOAD for possible problem diagnosis by Rocket Technical Support. They are not required. </p>

JAL: /* Sample JCL */ reference to integrated load library

2016-09-09T22:44:57Z

Sample JCL: reference to integrated load library

← Older revision		Revision as of 22:44, 9 September 2016
Line 70:		Line 70:
	//		//
	</nowiki></p>		</nowiki></p>

			The same JCL can be used for version 7.7 and later except for a change to the load library, something like the following which references the integrated Model 204 library:
			<p class="code">//STEPLIB DD DISP=SHR,DSN=M204.V77.LOADLIB
			</p>

	<div id="invkcms"></div>		<div id="invkcms"></div>

JAL: /* Invoking Fast/Unload as a standalone z/OS program */ add integration of F/U and Online

2016-09-09T22:24:28Z

Invoking Fast/Unload as a standalone z/OS program: add integration of F/U and Online

← Older revision		Revision as of 22:24, 9 September 2016
Line 1:		Line 1:
	==<b id="invkmvs"></b>Invoking Fast/Unload ~~as a standalone~~ z/OS ~~program~~==		==<b id="invkmvs"></b>Invoking Fast/Unload under z/OS==
	<var class="product">Fast/Unload</var> is invoked with the ~~EXEC JCL card~~.		For versions of <var class="product">Fast/Unload</var> through 4.7, the product is invoked as a standalone z/OS program. As of the next version after 4.7, <i>numbered 7.7</i> to associate it to Model 204 version 7.7, the product is integrated with the Model 204 Online load module and invoked as part of the integrated load module.
	~~The program name~~ of <var class="product">Fast/Unload</var> as distributed is <code>FUNLOAD</code>.
			Regardless of product version, <var class="product">Fast/Unload</var> is invoked with the EXEC JCL card, and its
			program name as distributed is <code>FUNLOAD</code>:
			<p class="code">// EXEC PGM=FUNLOAD </p>

	===DDnames===		===DDnames===
Line 48:		Line 51:

	===Sample JCL===		===Sample JCL===
	The following is an example of JCL that runs <var class="product">Fast/Unload</var> in a z/OS environment.		The following is an example of JCL that runs pre-7.7 <var class="product">Fast/Unload</var> as a standalone program in a z/OS 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

JAL: add 7.7 ddnames available to FUNLOAD

2016-09-08T23:49:13Z

add 7.7 ddnames available to FUNLOAD

← Older revision		Revision as of 23:49, 8 September 2016
Line 3:		Line 3:
	The program name of <var class="product">Fast/Unload</var> as distributed is <code>FUNLOAD</code>.		The program name of <var class="product">Fast/Unload</var> as distributed is <code>FUNLOAD</code>.

	===~~DDNAMEs~~===		===DDnames===
	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><~~code~~>FUNIN</~~code~~> — This DD contains the statements used to describe the unload.		<li><b>FUNIN</b> — This DD contains the statements used to describe the unload.
	FUNIN must be composed of fixed-length, 80-byte records. </li>		<code>FUNIN</code> must be composed of fixed-length, 80-byte records. </li>

	<li><~~code~~>FUNPRINT</~~code~~> — This DD is used as a log file and for reporting errors.		<li><b>FUNPRINT</b> — This DD is used as a log file and for reporting errors.
	This DD is referred to as the <b>report data set</b>. No DCB information is required, but if supplied:		This DD is referred to as the <b>report data set</b>. No DCB information is required, but if supplied:
	<ul>		<ul>
	<li>RECFM may be <var class="term">x</var>[B][A], where <var class="term">x</var> is <code>F</code> or <code>V</code>. If not specified, it defaults to <code>VBA</code>. ASCII carriage control (the <code>A</code> suffix) is always used.		<li><code>RECFM</code> may be <var class="term">x</var>[B][A], where <var class="term">x</var> is <code>F</code> or <code>V</code>. If not specified, it defaults to <code>VBA</code>. ASCII carriage control (the <code>A</code> suffix) is always used. </li>
	<li>LRECL defaults to either 133 (for RECFM F) or 137 (for RECFM V)
	<li>BLKSIZE defaults to 8192 (for RECFM F) or 8196 (for RECFM V)		<li><code>LRECL</code> defaults to either 133 (for <code>RECFM F</code>) or 137 (for <code>RECFM V</code>) </li>

			<li><code>BLKSIZE</code> defaults to 8192 (for RECFM F) or 8196 (for RECFM V) </li>
	</ul>		</ul>
	</li>		</li>

	<li><i>destination</i> —		<li><b><i>destination</i></b> —
	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.		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.
	<code>FUNOUT</code> is the default output stream for FUEL programs written for versions prior to 4.1. </li>		<code>FUNOUT</code> is the default output stream for FUEL programs written for versions prior to 4.1. </li>

	<li><i>input</i> —		<li><b><i>input</i></b> —
	A DD statement is required for the input <var class="product">Model 204</var> data file.		A DD statement is 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 name of the data file.		The DD statement for the <var class="product">Model 204</var> file <b>must</b> match the internal name of the data file.
Line 28:		Line 30:
	files making up the logical file. </li>		files making up the logical file. </li>

	<li><~~code~~>SYSUDUMP</~~code~~> or <~~code~~>SYSMDUMP</~~code~~> —		<li><b>SYSUDUMP</b> or <b>SYSMDUMP</b> —
	It is recommended that you allocate either of these files to the <var class="product">Fast/Unload</var> job step. </li>		It is recommended that you allocate either of these files to the <var class="product">Fast/Unload</var> job step. </li>
	</ul>		</ul>
			<p id="ccadd">
	As of the version 7.7 integration of Fast/Unload with the Online load module, these additional DD names can be used with PGM=FUNLOAD for possible problem diagnosis by Rocket Technical Support. They are not required.		As of the version 7.7 integration of Fast/Unload with the Online load module, these additional DD names can be used with PGM=FUNLOAD for possible problem diagnosis by Rocket Technical Support. They are not required. </p>
	<ul>		<ul>
	<li><~~code~~>CCASNAP </~~code~~> —		<li><b>CCASNAP </b> —
	If Fast/Unload encounters an abend, a Model 204 snap is created and sent to the CCASNAP DD. Since this is key to diagnosing many problems, Fast/Unload ensures that the DD name is allocated (to SYSOUT=A) if it has not been provided. </li>		If Fast/Unload encounters an abend, a Model 204 snap is created and sent to the CCASNAP DD. Since this is key to diagnosing many problems, Fast/Unload ensures that the DD name is allocated (to SYSOUT=A) if it has not been provided. </li>

	<li><~~code~~>CCAAUDIT</~~code~~> —		<li><b>CCAAUDIT</b> —
	You can capture the normal Model 204 audit trail if you provide a CCAAUDIT DD. This is a small file (generally less than 100 records) and the information is usually not important, but it might be helpful for problem diagnosis.		You can capture the normal Model 204 audit trail if you provide a CCAAUDIT DD. This is a small file (generally less than 100 records) and the information is usually not important, but it might be helpful for problem diagnosis.

	<li><~~code~~>CCAPRINT</~~code~~> —		<li><b>CCAPRINT</b> —
	You can capture the normal Model 204 file for initialization		You can capture the normal Model 204 file for initialization
	if you provide a CCAPRINT DD. This is a small file (generally less than 50 records) and the information is usually not important, but it might be helpful for problem diagnosis. You should be able to define this as a SYSOUT file.		if you provide a CCAPRINT DD. This is a small file (generally less than 50 records) and the information is usually not important, but it might be helpful for problem diagnosis. You should be able to define this as a SYSOUT file.