Fast/Unload program parameters - Revision history

Dme: /* Harderr= {ABEND|CANCEL|SKIP|SKIP0|IGNORE|IGNORE0} */

2018-03-08T15:49:30Z

Harderr= {ABEND|CANCEL|SKIP|SKIP0|IGNORE|IGNORE0}

← Older revision		Revision as of 15:49, 8 March 2018
Line 221:		Line 221:
	that <var>FUNOUT</var> is in effect. <var>SORTOUT</var> and <var>SORTOUTD</var> will indicate <var>OFF</var>.		that <var>FUNOUT</var> is in effect. <var>SORTOUT</var> and <var>SORTOUTD</var> will indicate <var>OFF</var>.

	==Harderr= {ABEND\|CANCEL\|SKIP\|SKIP0\|IGNORE\|IGNORE0}==		==<b id="harderr"></b>Harderr= {ABEND\|CANCEL\|SKIP\|SKIP0\|IGNORE\|IGNORE0}==
	<var>HARDERR</var> sets the action to be performed when a hard error is encountered.		<var>HARDERR</var> sets the action to be performed when a hard error is encountered.
	A hard error is a missing record or extension record		A hard error is a missing record or extension record

JAL: remove divs

2016-08-05T20:26:30Z

remove divs

← Older revision		Revision as of 20:26, 5 August 2016
Line 106:		Line 106:
	The default for <var>EVERY</var> is 0, which means that all records are processed.		The default for <var>EVERY</var> is 0, which means that all records are processed.

	<~~div~~ id="fnvmask"></~~div~~>		==<b id="fnvmask"></b>FNvmask=X"yz"==
	==FNvmask=X"yz"==
	~~<!--Caution: <div> above-->~~
	<var>FNVMASK</var> specifies which of the eight characters of the name of the file being unloaded		<var>FNVMASK</var> specifies which of the eight characters of the name of the file being unloaded
	may differ from the file name stored on the disk pages of the <var class="product">Model 204</var> file.		may differ from the file name stored on the disk pages of the <var class="product">Model 204</var> file.
Line 192:		Line 190:

	<var>FSTATS</var> is not valid if the Field Statistics option is not linked with your Fast Unload load module.		<var>FSTATS</var> is not valid if the Field Statistics option is not linked with your Fast Unload load module.

	~~<div id="foutprm"></div>~~

	==FUnout==		==<b id="foutprm"></b>FUnout==
	~~<!--Caution: <div> above-->~~
	This parameter directs <var class="product">Fast/Unload</var> to perform the I/O to the		This parameter directs <var class="product">Fast/Unload</var> to perform the I/O to the
	output sequential data set(s), even if going through a sort due to		output sequential data set(s), even if going through a sort due to
Line 294:		Line 289:
	is used. <var>IOAPP</var> is ignored for Hitachi and IBM systems.		is used. <var>IOAPP</var> is ignored for Hitachi and IBM systems.

	<~~div~~ id="libuff"></~~div~~>		==<b id="libuff"></b>LIBuff=n==
	==LIBuff=n==
	~~<!--Caution: <div> above-->~~
	This specifies the size of the work area used to hold a normalized		This specifies the size of the work area used to hold a normalized
	FUEL statement ("normalized" means reducing to a single blank		FUEL statement ("normalized" means reducing to a single blank
Line 420:		Line 413:
	The maximum value for <var>NOBUFF</var> is 99.		The maximum value for <var>NOBUFF</var> is 99.

	<~~div~~ id="noenq"></~~div~~>		==<b id="noenq"></b>NOEnq==
	==NOEnq==
	~~<!--Caution: <div> above-->~~
	This parameter indicates that <var class="product">Fast/Unload</var> does not attempt to use standard <var class="product">Model 204</var> enqueuing on the input data file.		This parameter indicates that <var class="product">Fast/Unload</var> does not attempt to use standard <var class="product">Model 204</var> enqueuing on the input data file.
	By default, <var class="product">Fast/Unload</var> attempts to obtain		By default, <var class="product">Fast/Unload</var> attempts to obtain
Line 578:		Line 569:
	The default for <var>SKIPREC</var> is 0, which means that no records are skipped.		The default for <var>SKIPREC</var> is 0, which means that no records are skipped.

	<~~div~~ id="soutprm"></~~div~~>		==<b id="soutprm"></b>SORTOut \| SORTOUTD==
	==SORTOut \| SORTOUTD==
	~~<!--Caution: <div> above-->~~
	In contrast to the <var>[[#FUnout\|FUNOUT]]</var> parameter, both these parameters tell the		In contrast to the <var>[[#FUnout\|FUNOUT]]</var> parameter, both these parameters tell the
	external sort package to write the sorted records directly to the output		external sort package to write the sorted records directly to the output

JAL: /* FStats[=AVGTOT|MINMAX] */ typo

2016-08-05T20:23:59Z

FStats[=AVGTOT|MINMAX]: typo

← Older revision		Revision as of 20:23, 5 August 2016
Line 191:		Line 191:
	(see [[Fast/Unload customization of defaults#cusfst\|Setting default FSTATS processing]]).		(see [[Fast/Unload customization of defaults#cusfst\|Setting default FSTATS processing]]).

	<var>FSTATS</var> is not valid if the Field Statistics ~~Option~~ is not linked with your Fast Unload load module.		<var>FSTATS</var> is not valid if the Field Statistics option is not linked with your Fast Unload load module.

	<div id="foutprm"></div>		<div id="foutprm"></div>

Dme: /* Error message FUNL0093 and ORECERR */

2016-03-25T22:36:49Z

Error message FUNL0093 and ORECERR

← Older revision		Revision as of 22:36, 25 March 2016
Line 489:		Line 489:
	Usually, if you encounter the message which indicates an output error (<code>FUNL0093</code>), the corrective action will be to increase the <code>LRECL</code> of the output file. If, for some reason that is not the correct action, you may find that you can use <var>ORECERR=SKIP</var> or <var>ORECERR=IGNORE</var>, but this means that data might be lost in the output file.		Usually, if you encounter the message which indicates an output error (<code>FUNL0093</code>), the corrective action will be to increase the <code>LRECL</code> of the output file. If, for some reason that is not the correct action, you may find that you can use <var>ORECERR=SKIP</var> or <var>ORECERR=IGNORE</var>, but this means that data might be lost in the output file.

	If <b>certain</b> <var>PUT</var> statements ~~may~~ cause the output error, you might be able to check for the truncation before the <var>PUT</var> (using, for example, the <var>#OUTPOS</var> or <var>#OUTLEN</var> [[FUEL#spvars\|special variables]]). However, this might mean that the design and usage of your output file needs to be changed.		If you can identify <b>certain</b> <var>PUT</var> statements which, depending on data values, can cause the output error, you might be able to check for the truncation before the <var>PUT</var> (using, for example, the <var>#OUTPOS</var> or <var>#OUTLEN</var> [[FUEL#spvars\|special variables]]). However, this might mean that the design and usage of your output file needs to be changed.

	==Sbbuff=n==		==Sbbuff=n==

Dme: /* Error message FUNL0093 and ORECERR */

2016-03-24T16:18:22Z

Error message FUNL0093 and ORECERR

← Older revision		Revision as of 16:18, 24 March 2016
Line 487:		Line 487:

	===Error message FUNL0093 and ORECERR===		===Error message FUNL0093 and ORECERR===
	In some ~~cases~~, you can use <var>ORECERR=SKIP</var> or <var>ORECERR=IGNORE</var>, but this means that data might be lost in the output file.		Usually, if you encounter the message which indicates an output error (<code>FUNL0093</code>), the corrective action will be to increase the <code>LRECL</code> of the output file. If, for some reason that is not the correct action, you may find that you can use <var>ORECERR=SKIP</var> or <var>ORECERR=IGNORE</var>, but this means that data might be lost in the output file.

	If <b>certain</b> <var>PUT</var> statements may cause the output error, you might be able to check for the truncation before the <var>PUT</var> (using, for example, the <var>#OUTPOS</var> or <var>#OUTLEN</var> [[FUEL#spvars\|special variables]]). However, this might mean that the design and usage of your output file needs to be changed.		If <b>certain</b> <var>PUT</var> statements may cause the output error, you might be able to check for the truncation before the <var>PUT</var> (using, for example, the <var>#OUTPOS</var> or <var>#OUTLEN</var> [[FUEL#spvars\|special variables]]). However, this might mean that the design and usage of your output file needs to be changed.

Dme: /* Orecerr={CANCEL|SKIP|IGNORE} */

2016-03-24T15:44:44Z

Orecerr={CANCEL|SKIP|IGNORE}

← Older revision		Revision as of 15:44, 24 March 2016
Line 480:		Line 480:
	<li><var>CANCEL</var> — Stop the <var class="product">Fast/Unload</var>. </li>		<li><var>CANCEL</var> — Stop the <var class="product">Fast/Unload</var>. </li>
	<li><var>SKIP</var> — Skip the current record. </li>		<li><var>SKIP</var> — Skip the current record. </li>
	<li><var>IGNORE</var> — Ignore the error and simply truncate the record. </li>		<li><var>IGNORE</var> — Ignore the error and simply truncate the value in the output record. </li>
	</ul>		</ul>

	The default value for this parameter is <var>CANCEL</var>.		The default value for this parameter is <var>CANCEL</var>.
	For any value of <var>ORECERR</var>, output record errors are reported.		For any value of <var>ORECERR</var>, output record errors are reported.

			===Error message FUNL0093 and ORECERR===
			In some cases, you can use <var>ORECERR=SKIP</var> or <var>ORECERR=IGNORE</var>, but this means that data might be lost in the output file.

			If <b>certain</b> <var>PUT</var> statements may cause the output error, you might be able to check for the truncation before the <var>PUT</var> (using, for example, the <var>#OUTPOS</var> or <var>#OUTLEN</var> [[FUEL#spvars\|special variables]]). However, this might mean that the design and usage of your output file needs to be changed.

	==Sbbuff=n==		==Sbbuff=n==

Dme: /* Orecerr={CANCEL|SKIP|IGNORE} */

2016-03-24T15:27:38Z

Orecerr={CANCEL|SKIP|IGNORE}

← Older revision		Revision as of 15:27, 24 March 2016
Line 470:		Line 470:
	via the <var class="product">Fast/Unload SOUL Interface</var>.		via the <var class="product">Fast/Unload SOUL Interface</var>.

	==Orecerr={CANCEL\|SKIP\|IGNORE}==		==<b id="orecerr"></b>Orecerr={CANCEL\|SKIP\|IGNORE}==
	This parameter sets the action to be performed when an output record error is		This parameter sets the action to be performed when an output record error is
	encountered.		encountered.

JAL: /* Frecord=n */ fix heading ID below

2016-02-17T21:11:51Z

Frecord=n: fix heading ID below

← Older revision		Revision as of 21:11, 17 February 2016
Line 170:		Line 170:
	indicated starting record number. </p>		indicated starting record number. </p>

	The <var>FRECORD</var> parameter applies only to the first file, if a group unload		The <var>FRECORD</var> parameter applies only to the first file, if a group unload is being performed.
	is being performed.

	~~<div id="fstp"></div>~~
	==<b id="fstp"></b>FStats[=AVGTOT\|MINMAX]==		==<b id="fstp"></b>FStats[=AVGTOT\|MINMAX]==
	This parameter gathers field, Table, and procedure statistics,		This parameter gathers field, Table, and procedure statistics,

JAL: /* FStats[=AVGTOT|MINMAX] */ fix heading ID

2016-02-17T21:11:10Z

FStats[=AVGTOT|MINMAX]: fix heading ID

← Older revision		Revision as of 21:11, 17 February 2016
Line 174:		Line 174:

	<div id="fstp"></div>		<div id="fstp"></div>
	==FStats[=AVGTOT\|MINMAX]==		==<b id="fstp"></b>FStats[=AVGTOT\|MINMAX]==
	~~<!--Caution: <div> above-->~~
	This parameter gathers field, Table, and procedure statistics,		This parameter gathers field, Table, and procedure statistics,
	and it checks file integrity during the run.		and it checks file integrity during the run.

JAL: minor formatting

2016-02-04T17:57:06Z

minor formatting

← Older revision		Revision as of 17:57, 4 February 2016
Line 2:		Line 2:
	Some basic parameters are provided to control the operation of		Some basic parameters are provided to control the operation of
	<var class="product">Fast/Unload</var>.		<var class="product">Fast/Unload</var>.
	These parameters must be provided either as a <code>PARM</code> on the EXEC		These parameters must be provided in either of these ways:
	card in z/OS~~, for~~ example:		<ul>
			<li>As a <code>PARM</code> on the EXEC card in z/OS. For example:
	<p class="code"><nowiki>//FUNLOAD EXEC PGM=FUNLOAD,REGION=4096K,		<p class="code"><nowiki>//FUNLOAD EXEC PGM=FUNLOAD,REGION=4096K,
	// PARM='NEBUFF=8 SEBUFF=1 SBBUFF=3 SEQ'		// PARM='NEBUFF=8 SEBUFF=1 SBBUFF=3 SEQ'
	</nowiki></p>		</nowiki></p></li>
	~~Or the parameters may be~~ options on the <var>M204CMS</var> command in CMS~~, for~~ example:
			<li>As options on the <var>M204CMS</var> command in CMS. For example:
	<p class="code"><nowiki>'M204CMS FUNLOAD ( NEBUFF 8 SEBUFF 1 SBBUFF 3 SEQ %'		<p class="code"><nowiki>'M204CMS FUNLOAD ( NEBUFF 8 SEBUFF 1 SBBUFF 3 SEQ %'
	</nowiki></p>		</nowiki></p></li>
			</ul>

	Under z/OS, parameters are specified either by a parameter name alone or		Under z/OS, parameters are specified either by a parameter name alone or