Allocating and directing files dynamically - Revision history

ELowell at 21:07, 6 February 2017

2017-02-06T21:07:40Z

← Older revision		Revision as of 21:07, 6 February 2017
Line 770:		Line 770:
	Use the option to print separator pages in block character format in conjunction with the <var>SEP</var> and <var>HDR1</var>, <var>HDR2</var>, and <var>HDR3</var> parameters. </p>		Use the option to print separator pages in block character format in conjunction with the <var>SEP</var> and <var>HDR1</var>, <var>HDR2</var>, and <var>HDR3</var> parameters. </p>
	<p>		<p>
	To use this option, the IBM-supplied block character routine, IEFSD095, must be [[~~Upgrading to~~ Model 204 ~~7.5 or later~~ on IBM z/OS#Linking the Model 204 ONLINE load module\|linked in the Online load module]].		To use this option, the IBM-supplied block character routine, IEFSD095, must be [[Model 204 installation on IBM z/OS#Linking the Model 204 ONLINE load module\|linked in the Online load module]].
	</p>		</p>

	[[Category:System management]]		[[Category:System management]]
	[[Category:System-level capabilities of Model 204]]		[[Category:System-level capabilities of Model 204]]

ELowell at 22:11, 26 September 2016

2016-09-26T22:11:56Z

← Older revision		Revision as of 22:11, 26 September 2016
Line 348:		Line 348:

	<p class="note"><b>Note:</b>		<p class="note"><b>Note:</b>
	Server data sets are not supported when allocated above the 64K cylinder boundary. An attempt to open any server data set allocated above 64K cylinders results in issuing error [[M204.2917~~\|message 2917]],~~ which identifies the server data set name, and run termination.		Server data sets are not supported when allocated above the 64K cylinder boundary. An attempt to open any server data set allocated above 64K cylinders results in issuing error message M204.2917 (which identifies the server data set name) and run termination.
	</p></li>		</p></li>
	</ul>		</ul>

ELowell: /* Tailoring the Model 204 separator page */

2016-08-30T16:19:05Z

Tailoring the Model 204 separator page

← Older revision		Revision as of 16:19, 30 August 2016
Line 770:		Line 770:
	Use the option to print separator pages in block character format in conjunction with the <var>SEP</var> and <var>HDR1</var>, <var>HDR2</var>, and <var>HDR3</var> parameters. </p>		Use the option to print separator pages in block character format in conjunction with the <var>SEP</var> and <var>HDR1</var>, <var>HDR2</var>, and <var>HDR3</var> parameters. </p>
	<p>		<p>
	To use this option, the IBM-supplied block character routine, IEFSD095, must ~~reside in~~ the ~~system library SYS1.AOSB0 and must be~~ linked in the ~~ONLINE~~ load module~~. For more information, see the [https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.hasc300/has2c32527.htm IBM Knowledge Center topic~~] ~~on this routine~~.</p>		To use this option, the IBM-supplied block character routine, IEFSD095, must be [[Upgrading to Model 204 7.5 or later on IBM z/OS#Linking the Model 204 ONLINE load module\|linked in the Online load module]].
			</p>

	[[Category:System management]]		[[Category:System management]]
	[[Category:System-level capabilities of Model 204]]		[[Category:System-level capabilities of Model 204]]

ELowell: /* Large data set support */

2016-08-11T19:55:04Z

Large data set support

← Older revision		Revision as of 19:55, 11 August 2016
Line 76:		Line 76:
	Large data sets are supported for <var class="product">Model 204</var> database files and journal files, including CCAJLOG, GDG (z/OS only) and stream-based journals, and sequential data sets, including file dumps.</p>		Large data sets are supported for <var class="product">Model 204</var> database files and journal files, including CCAJLOG, GDG (z/OS only) and stream-based journals, and sequential data sets, including file dumps.</p>

	<p>Large checkpoint data sets are supported on z/OS in Model 204 version 7.7 or later.</p>		<p>Large checkpoint data sets are supported on z/OS in Model 204 version 7.7 and later.</p>
	<p>		<p>
	The <var class="product">Model 204</var> <var>DEFINE DATASET</var> and <var>ALLOCATE DATASET</var> commands include the <var>LARGE</var> argument that indicates a data set may have more than 64K tracks.</p>		The <var class="product">Model 204</var> <var>DEFINE DATASET</var> and <var>ALLOCATE DATASET</var> commands include the <var>LARGE</var> argument that indicates a data set may have more than 64K tracks.</p>

ELowell: /* Large data set support */

2016-08-08T22:19:19Z

Large data set support

← Older revision		Revision as of 22:19, 8 August 2016
Line 75:		Line 75:
	<p>		<p>
	Large data sets are supported for <var class="product">Model 204</var> database files and journal files, including CCAJLOG, GDG (z/OS only) and stream-based journals, and sequential data sets, including file dumps.</p>		Large data sets are supported for <var class="product">Model 204</var> database files and journal files, including CCAJLOG, GDG (z/OS only) and stream-based journals, and sequential data sets, including file dumps.</p>

			<p>Large checkpoint data sets are supported on z/OS in Model 204 version 7.7 or later.</p>
	<p>		<p>
	The <var class="product">Model 204</var> <var>DEFINE DATASET</var> and <var>ALLOCATE DATASET</var> commands include the <var>LARGE</var> argument that indicates a data set may have more than 64K tracks.</p>		The <var class="product">Model 204</var> <var>DEFINE DATASET</var> and <var>ALLOCATE DATASET</var> commands include the <var>LARGE</var> argument that indicates a data set may have more than 64K tracks.</p>
Line 113:		Line 115:
	</p></li>		</p></li>
	</ul>		</ul>

	===z/VM considerations===		===z/VM considerations===
	<p>		<p>

ELowell: /* DEFINE DATASET command */

2016-08-08T21:52:50Z

DEFINE DATASET command

← Older revision		Revision as of 21:52, 8 August 2016
Line 47:		Line 47:
	The <var>[[DEFINE command\|DEFINE]]</var> command defines types of data structures, such as data sets, sequential I/O streams, program communication processes used by SOUL requests, and output destinations.</p>		The <var>[[DEFINE command\|DEFINE]]</var> command defines types of data structures, such as data sets, sequential I/O streams, program communication processes used by SOUL requests, and output destinations.</p>
	<p>		<p>
	The <var>DEFINE DATASET</var> command enables a user with system manager privileges to specify the physical characteristics of dynamically created data sets. <var>DEFINE DATASET</var> creates a template, identified by a name, which is referenced by <var>ALLOCATE</var> and <var>FREE</var> commands. </p>		The <var>[[DEFINE DATASET command\|DEFINE DATASET]]</var> command enables a user with system manager privileges to specify the physical characteristics of dynamically created data sets. <var>DEFINE DATASET</var> creates a template, identified by a name, which is referenced by <var>ALLOCATE</var> and <var>FREE</var> commands. </p>

	===z/OS considerations===		===z/OS considerations===
Line 241:		Line 241:
	</p></li>		</p></li>
	</ul>		</ul>

	==Extended Task Input/Output Table support==		==Extended Task Input/Output Table support==
	<p>		<p>

ELowell: /* Tailoring the Model 204 separator page */

2016-06-22T23:46:14Z

Tailoring the Model 204 separator page

← Older revision		Revision as of 23:46, 22 June 2016
Line 768:		Line 768:
	Use the option to print separator pages in block character format in conjunction with the <var>SEP</var> and <var>HDR1</var>, <var>HDR2</var>, and <var>HDR3</var> parameters. </p>		Use the option to print separator pages in block character format in conjunction with the <var>SEP</var> and <var>HDR1</var>, <var>HDR2</var>, and <var>HDR3</var> parameters. </p>
	<p>		<p>
	To use this option, the IBM-supplied routine, IEFSD095, must reside in the system library SYS1.AOSB0 and must be linked in the ONLINE load module. ~~Refer to the IBM Systems Modifications Manual for~~ more information ~~about~~ the routine.</p>		To use this option, the IBM-supplied block character routine, IEFSD095, must reside in the system library SYS1.AOSB0 and must be linked in the ONLINE load module. For more information, see the [https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.hasc300/has2c32527.htm IBM Knowledge Center topic] on this routine.</p>

	[[Category:System management]]		[[Category:System management]]
	[[Category:System-level capabilities of Model 204]]		[[Category:System-level capabilities of Model 204]]

JAL: /* z/OS considerations */

2014-11-20T20:28:53Z

z/OS considerations

← Older revision		Revision as of 20:28, 20 November 2014
Line 71:		Line 71:
	<li>If you specify the <code>STRNO</code> parameter in the DD statement, you must give it the same value as the <var>STRINGS</var> parameter in the <var>DEFINE DATASET</var> statement. Preferably, do not specify <code>STRNO</code> in the DD statement. </li>		<li>If you specify the <code>STRNO</code> parameter in the DD statement, you must give it the same value as the <var>STRINGS</var> parameter in the <var>DEFINE DATASET</var> statement. Preferably, do not specify <code>STRNO</code> in the DD statement. </li>
	</ul>		</ul>

	===Large data set support===		===Large data set support===
	<p>		<p>

JAL: typos

2014-11-20T17:33:05Z

typos

← Older revision		Revision as of 17:33, 20 November 2014
Line 22:		Line 22:
	In z/OS and z/VM environments, you can perform dynamic file allocation in the following ways: </p>		In z/OS and z/VM environments, you can perform dynamic file allocation in the following ways: </p>
	<ul>		<ul>
	<li>Create a data set template with the <var>[[DEFINE DATASET command\|DEFINE DATASET]]</var> command in the CCAIN input stream before User 0's parameter line:~~</li>~~		<li>Create a data set template with the <var>[[DEFINE DATASET command\|DEFINE DATASET]]</var> command in the CCAIN input stream before User 0's parameter line:
	<p class="code">DEFINE DATASET <i>name</i> WITH SCOPE=SYSTEM		<p class="code">DEFINE DATASET <i>name</i> WITH SCOPE=SYSTEM
	<i>other parameters</i>		<i>other parameters</i>
Line 32:		Line 32:
	</p></li>		</p></li>

	<li>Allocate data set units in the JCL for the run and then dynamically issue the allocation command sequence:~~</li>~~		<li>Allocate data set units in the JCL for the run and then dynamically issue the allocation command sequence:
	<p class="code">ALLOCATE DATASET <i>name</i> WITH SCOPE=USER		<p class="code">ALLOCATE DATASET <i>name</i> WITH SCOPE=USER
	FREE DATASET <i>name</i>		FREE DATASET <i>name</i>
Line 130:		Line 130:

	<li>You can specify SECONDARY under z/VM, but no secondary allocation occurs when running under z/VM. The secondary space information is stored in the Volume Table of Contents (VTOC) when allocation is done under z/VM. </li>		<li>You can specify SECONDARY under z/VM, but no secondary allocation occurs when running under z/VM. The secondary space information is stored in the Volume Table of Contents (VTOC) when allocation is done under z/VM. </li>
	~~</li>~~

	<li>The <code>VOLUME</code> option is required under z/VM when you create a new data set, or when you reference an existing data set that resides on an unaccessed-format or z/VSE-format minidisk. The <code>VOLUME</code> option is meaningful only during dynamic allocation. </li>		<li>The <code>VOLUME</code> option is required under z/VM when you create a new data set, or when you reference an existing data set that resides on an unaccessed-format or z/VSE-format minidisk. The <code>VOLUME</code> option is meaningful only during dynamic allocation. </li>

JALWiccan: Automatically generated page update

2014-11-06T17:08:03Z

Automatically generated page update

← Older revision		Revision as of 17:08, 6 November 2014
Line 771:		Line 771:
	To use this option, the IBM-supplied routine, IEFSD095, must reside in the system library SYS1.AOSB0 and must be linked in the ONLINE load module. Refer to the IBM Systems Modifications Manual for more information about the routine.</p>		To use this option, the IBM-supplied routine, IEFSD095, must reside in the system library SYS1.AOSB0 and must be linked in the ONLINE load module. Refer to the IBM Systems Modifications Manual for more information about the routine.</p>

	[[Category:System ~~Manager~~]]		[[Category:System management]]
	[[Category:System-level capabilities of Model 204]]		[[Category:System-level capabilities of Model 204]]