RockZap - Revision history

Tom: /* UPPER */

2022-02-18T20:07:21Z

UPPER

← Older revision		Revision as of 20:07, 18 February 2022
Line 193:		Line 193:

	===UPPER===		===UPPER===
	The <var>UPPER</var> option forces all <var class="product">RockZap</var> output to		The <var>UPPER</var> option forces all <var class="product">RockZap</var> output to upper case.

	===MISSING===		===MISSING===

Tom: /* UPPER */

2022-02-18T20:07:07Z

UPPER

← Older revision		Revision as of 20:07, 18 February 2022
Line 193:		Line 193:

	===UPPER===		===UPPER===
	The <var>UPPER</var> option forces all <var class="product">RockZap</var> output to ~~uppercase.~~		The <var>UPPER</var> option forces all <var class="product">RockZap</var> output to
	~~This is usually unnecessary, except on certain Japanese terminals and~~
	~~when sending output to uppercase-only printers.~~
	~~<var>UPPER</var> is the default setting for Hitachi and Fujitsu systems.~~

	===MISSING===		===MISSING===

Tom: /* RockZap options */

2022-02-18T20:06:24Z

RockZap options

← Older revision		Revision as of 20:06, 18 February 2022
Line 197:		Line 197:
	when sending output to uppercase-only printers.		when sending output to uppercase-only printers.
	<var>UPPER</var> is the default setting for Hitachi and Fujitsu systems.		<var>UPPER</var> is the default setting for Hitachi and Fujitsu systems.

			===MISSING===
			The <var>MISSING</var> option suppresses errors resulting from a NAME statement that references a CSECT not present in the load module.
			<var>MISSING</var> is the default.

			===NOMISSING===
			The <var>NOMISSING</var> option flags errors resulting from a NAME statement that references a CSECT not present in the load module. A missing CSECT results in a return code of 4.

	==RockZap control statements==		==RockZap control statements==

Tom: /* RockZap features */

2022-02-17T22:21:06Z

RockZap features

← Older revision		Revision as of 22:21, 17 February 2022
Line 79:		Line 79:
	however, using the <var>[[#* !NOVERIFY\|* !NOVERIFY]]</var> statement.</li>		however, using the <var>[[#* !NOVERIFY\|* !NOVERIFY]]</var> statement.</li>

	<li><var class="product">RockZap</var> 1.7 and later support ~~LARGE~~ z/OS datasets.</li>		<li><var class="product">RockZap</var> 1.7 and later support z/OS datasets with the LARGE attribute.</li>

	</ul>		</ul>

Tom: /* RockZap features */

2022-02-17T22:20:34Z

RockZap features

← Older revision		Revision as of 22:20, 17 February 2022
Line 78:		Line 78:
	You can override this feature,		You can override this feature,
	however, using the <var>[[#* !NOVERIFY\|* !NOVERIFY]]</var> statement.</li>		however, using the <var>[[#* !NOVERIFY\|* !NOVERIFY]]</var> statement.</li>

			<li><var class="product">RockZap</var> 1.7 and later support LARGE z/OS datasets.</li>

	</ul>		</ul>

Tom: /* Differences between RockZap and IMASPZAP */

2022-02-17T22:16:34Z

Differences between RockZap and IMASPZAP

← Older revision		Revision as of 22:16, 17 February 2022
Line 87:		Line 87:
	<li><var class="product">RockZap</var> only modifies direct access load libraries.		<li><var class="product">RockZap</var> only modifies direct access load libraries.
	<var class="product">RockZap</var> does not		<var class="product">RockZap</var> does not
	modify any other types of direct access data sets.</li>		modify PDSEs or any other types of direct access data sets.</li>

	<li>The following SPZAP statements are not supported but are ignored		<li>The following SPZAP statements are not supported but are ignored

Tom: /* RockZap DD statements */

2017-03-10T21:23:05Z

RockZap DD statements

← Older revision		Revision as of 21:23, 10 March 2017
Line 347:		Line 347:
	<ul>		<ul>
	<li>SYSLIB points to the load library PDS (Partitioned Data		<li>SYSLIB points to the load library PDS (Partitioned Data
	Set) containing the load module you want to ZAP.</li>		Set) containing the load module you want to ZAP. The load library cannot be a PDSE (Partition Data Set Extended) dataset.</li>

	<li>SYSIN contains the ZAP control statements and must		<li>SYSIN contains the ZAP control statements and must

DCameron: /* RockZap options */

2016-07-28T15:26:30Z

RockZap options

← Older revision		Revision as of 15:26, 28 July 2016
Line 135:		Line 135:
	For example, to force uppercase output and to		For example, to force uppercase output and to
	backout ZAPs, use the following EXEC statement:		backout ZAPs, use the following EXEC statement:
	<p class="code">//ROCKZAP EXEC ~~PRM~~=ROCKZAP,PARM='UPPER,BACKOUT'		<p class="code">//ROCKZAP EXEC PGM=ROCKZAP,PARM='UPPER,BACKOUT'
	</p>		</p>

JAL: add note to NAME

2016-04-08T22:16:58Z

add note to NAME

← Older revision		Revision as of 22:16, 8 April 2016
Line 165:		Line 165:

	===MODULE===		===MODULE===
	The <var>MODULE=<i>modname</i></var> option allows the module name on each <var>NAME</var> statement to be overridden with a single load-module name. This means that you can use the same <var>ROCKZAP</var> jobstream to apply the same zaps to different load modules in the designated load library (SYSLIB) without making changes to any of the <var>NAME</var> statements.		The <var>MODULE=<i>modname</i></var> option allows the module name on each <var>NAME</var> statement to be overridden with a single load-module name. This means that you can use the same <var>ROCKZAP</var> jobstream to apply the same zaps to different load modules in the designated load library (SYSLIB) without making changes to any of the <var>[[#NAME\|NAME]]</var> control statements.

	For example, <code>PARM='MODULE=ONLINE'</code> applies the zaps to the module named <code>ONLINE</code> in the designated load library, regardless of the load-module name on each <var>NAME</var> statement. Then, using the same job stream, <code>PARM='MODULE=ONLINTST'</code> applies the same zaps to the module named <code>ONLINTST</code>, again, regardless of the load-module name on each <var>NAME</var> statement.		For example, <code>PARM='MODULE=ONLINE'</code> applies the zaps to the module named <code>ONLINE</code> in the designated load library, regardless of the load-module name on each <var>NAME</var> statement. Then, using the same job stream, <code>PARM='MODULE=ONLINTST'</code> applies the same zaps to the module named <code>ONLINTST</code>, again, regardless of the load-module name on each <var>NAME</var> statement.
Line 265:		Line 265:

	===NAME===		===NAME===
	The <var>NAME</var> statement identifies a load module, and optionally a CSECT		The <var>NAME</var> statement identifies a load module, and optionally a CSECT, that defines the context for the <var>VER</var> and <var>REP</var> statements that follow.
	that defines the context for the <var>VER</var> and <var>REP</var> statements that follow.
	<var>NAMEX</var> is a synonym for <var>NAME</var> that allows compatibility with the Fujitsu		<var>NAMEX</var> is a synonym for <var>NAME</var> that allows compatibility with the Fujitsu
	OSIV ZAP utility.		OSIV ZAP utility.
Line 281:		Line 280:
	<td>The name of the control section in the load module. A <var class="term">csect</var> value is optional. If the CSECT name is missing, subsequent verify and replace displacements are calculated from offset 0 in the load module.</td></tr>		<td>The name of the control section in the load module. A <var class="term">csect</var> value is optional. If the CSECT name is missing, subsequent verify and replace displacements are calculated from offset 0 in the load module.</td></tr>
	</table>		</table>

			<p class="note"><b>Note:</b> You can use the <var>[[#MODULE\|MODULE]]</var> parameter to override the module name in <var>NAME</var> statements. </p>

	===DUMP or DUMPT===		===DUMP or DUMPT===

ELowell at 17:52, 24 February 2016

2016-02-24T17:52:45Z

← Older revision		Revision as of 17:52, 24 February 2016
Line 436:		Line 436:
	</p>		</p>

	[[Category:~~RKtools~~]]		[[Category:RKTools]]