DEFINE DATASET command - Revision history

Alex: /* Syntax */

2024-07-31T17:57:43Z

Syntax

← Older revision		Revision as of 17:57, 31 July 2024
Line 162:		Line 162:
	<td>(Only z/OS.) Indicates a Generation Data Group (GDG) member.</td> </tr>		<td>(Only z/OS.) Indicates a Generation Data Group (GDG) member.</td> </tr>

	<tr> <th><var>IMAGINE</var></th>		<tr id="IMAGINE"> <th><var>IMAGINE</var></th>
	<td>Indicates that the data for the file is actually in an <var>Imagine</var> and accessed via an <var>Imagine</var> broker connected to an [[JANUS_DEFINE#Syntax\|Imagine Transparency port]]. This option is only available in <var class="product">Model 204</var> Version 8.0 and later.</td> </tr>		<td>Indicates that the data for the file is actually in an <var>Imagine</var> and accessed via an <var>Imagine</var> broker connected to an [[JANUS_DEFINE#Syntax\|Imagine Transparency port]]. This option is only available in <var class="product">Model 204</var> Version 8.0 and later.</td> </tr>

Alex: /* Syntax */

2024-07-31T17:51:35Z

Syntax

← Older revision		Revision as of 17:51, 31 July 2024
Line 17:		Line 17:
	[CLOSE={EOJ \| <u>NOUSERS</u>}] [DATALEN=n] [DCLASS]		[CLOSE={EOJ \| <u>NOUSERS</u>}] [DATALEN=n] [DCLASS]
	[DDNAME=<span class="term">name</span> \| FILENAME=<span class="term">name</span>] [DEFER] [DENSITY=<span class="term">n</span>]		[DDNAME=<span class="term">name</span> \| FILENAME=<span class="term">name</span>] [DEFER] [DENSITY=<span class="term">n</span>]
	[DIRECTORY=<span class="term">n</span>] [<b>DSN</b>AME=<span class="term">name</span>] [EATTR] [GDGRECNT] [GEN]		[DIRECTORY=<span class="term">n</span>] [<b>DSN</b>AME=<span class="term">name</span>] [EATTR] [GDGRECNT] [GEN] [IMAGINE]
	[LABEL=<span class="term">label</span>] [LARGE] [LRECL=<span class="term">n</span>] [MCLASS] [MEMBER=<span class="term">member-name</span>]		[LABEL=<span class="term">label</span>] [LARGE] [LRECL=<span class="term">n</span>] [MCLASS] [MEMBER=<span class="term">member-name</span>]
	[MEMORY] [NCP=<span class="term">n</span>] [NEW \| OLD \| COND] [PASSWORD=<span class="term">password</span>]		[MEMORY] [NCP=<span class="term">n</span>] [NEW \| OLD \| COND] [PASSWORD=<span class="term">password</span>]
Line 162:		Line 162:
	<td>(Only z/OS.) Indicates a Generation Data Group (GDG) member.</td> </tr>		<td>(Only z/OS.) Indicates a Generation Data Group (GDG) member.</td> </tr>

			<tr> <th><var>IMAGINE</var></th>
			<td>Indicates that the data for the file is actually in an <var>Imagine</var> and accessed via an <var>Imagine</var> broker connected to an [[JANUS_DEFINE#Syntax\|Imagine Transparency port]]. This option is only available in <var class="product">Model 204</var> Version 8.0 and later.</td> </tr>

	<tr> <th><var>LABEL</var></th>		<tr> <th><var>LABEL</var></th>
	<td>(Only z/OS.) Describes the label associated with a data set. The default is standard labels. Acceptable values that can be specified are as follows:		<td>(Only z/OS.) Describes the label associated with a data set. The default is standard labels. Acceptable values that can be specified are as follows:

DCameron: /* In-memory file allocation and restoration (z/OS and z/VM) */

2019-02-11T16:32:11Z

In-memory file allocation and restoration (z/OS and z/VM)

← Older revision		Revision as of 16:32, 11 February 2019
Line 466:		Line 466:
	<p>		<p>
	However, remember that restoring an in-memory file with <var>RESTORE</var> from a backup will copy the <var>FRCVOPT</var> from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <code><var>[[FOPT_command\|FOPT]]</var>=0</code>, which is TBO enabled, and TBO is supported. <var>[[REGENERATE_command\|REGENERATE]]</var> is also supported. <var>[[RESTART_command\|RESTART]]</var> recovery is not supported.		However, remember that restoring an in-memory file with <var>RESTORE</var> from a backup will copy the <var>FRCVOPT</var> from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <code><var>[[FOPT_command\|FOPT]]</var>=0</code>, which is TBO enabled, and TBO is supported. <var>[[REGENERATE_command\|REGENERATE]]</var> is also supported. <var>[[RESTART_command\|RESTART]]</var> recovery is not supported.
	Given these caveats, if you want to provide for both <var>REGENERATE</var> recovery and TBO, the best parameter settings for in-memory files are <code>FRCVOPT=X'20'</code> and <code>FOPT=0</code>.</p>		Given these caveats, if you want to provide for both <var>REGENERATE</var> recovery and [[Transaction_back_out\|TBO]], the best parameter settings for in-memory files are <code>FRCVOPT=X'20'</code> and <code>FOPT=0</code>.</p>
	<p>		<p>
	The <var>[[DUMP command\|DUMP]]</var> and <var>[[RESTORE command\|RESTORE]]</var> commands can process in-memory files. </p>		The <var>[[DUMP command\|DUMP]]</var> and <var>[[RESTORE command\|RESTORE]]</var> commands can process in-memory files. </p>

DCameron: /* In-memory file allocation and restoration (z/OS and z/VM) */

2019-02-11T16:31:15Z

In-memory file allocation and restoration (z/OS and z/VM)

← Older revision		Revision as of 16:31, 11 February 2019
Line 465:		Line 465:
	When you create an in-memory file, the default <var>[[FRCVOPT_parameter\|FRCVOPT]]</var> parameter value is X'24', which means that this file does not participate in journal and checkpoint logging.</p>		When you create an in-memory file, the default <var>[[FRCVOPT_parameter\|FRCVOPT]]</var> parameter value is X'24', which means that this file does not participate in journal and checkpoint logging.</p>
	<p>		<p>
	However, remember that restoring an in-memory file with <var>RESTORE</var> from a backup will copy the <var>FRCVOPT</var> from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <code><var>[[FOPT_command\|FOPT]]</var>=0</code>, which is TBO enabled, and TBO is supported. <var>REGENERATE</var> is also supported. <var>RESTART</var> recovery is not supported.		However, remember that restoring an in-memory file with <var>RESTORE</var> from a backup will copy the <var>FRCVOPT</var> from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <code><var>[[FOPT_command\|FOPT]]</var>=0</code>, which is TBO enabled, and TBO is supported. <var>[[REGENERATE_command\|REGENERATE]]</var> is also supported. <var>[[RESTART_command\|RESTART]]</var> recovery is not supported.
	Given these caveats, if you want to provide for both <var>REGENERATE</var> recovery and TBO, the best parameter settings for in-memory files are <code>FRCVOPT=X'20'</code> and <code>FOPT=0</code>.</p>		Given these caveats, if you want to provide for both <var>REGENERATE</var> recovery and TBO, the best parameter settings for in-memory files are <code>FRCVOPT=X'20'</code> and <code>FOPT=0</code>.</p>
	<p>		<p>

DCameron: /* In-memory file allocation and restoration (z/OS and z/VM) */

2019-02-11T16:30:06Z

In-memory file allocation and restoration (z/OS and z/VM)

← Older revision		Revision as of 16:30, 11 February 2019
Line 465:		Line 465:
	When you create an in-memory file, the default <var>[[FRCVOPT_parameter\|FRCVOPT]]</var> parameter value is X'24', which means that this file does not participate in journal and checkpoint logging.</p>		When you create an in-memory file, the default <var>[[FRCVOPT_parameter\|FRCVOPT]]</var> parameter value is X'24', which means that this file does not participate in journal and checkpoint logging.</p>
	<p>		<p>
	However, remember that restoring an in-memory file with <var>RESTORE</var> from a backup will copy the <var>FRCVOPT</var> from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <code><var[[FOPT_command\|FOPT]]</var>=0</code>, which is TBO enabled, and TBO is supported. <var>REGENERATE</var> is also supported. <var>RESTART</var> recovery is not supported.		However, remember that restoring an in-memory file with <var>RESTORE</var> from a backup will copy the <var>FRCVOPT</var> from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <code><var>[[FOPT_command\|FOPT]]</var>=0</code>, which is TBO enabled, and TBO is supported. <var>REGENERATE</var> is also supported. <var>RESTART</var> recovery is not supported.
	Given these caveats, if you want to provide for both <var>REGENERATE</var> recovery and TBO, the best parameter settings for in-memory files are <code>FRCVOPT=X'20'</code> and <code>FOPT=0</code>.</p>		Given these caveats, if you want to provide for both <var>REGENERATE</var> recovery and TBO, the best parameter settings for in-memory files are <code>FRCVOPT=X'20'</code> and <code>FOPT=0</code>.</p>
	<p>		<p>

DCameron: /* In-memory file allocation and restoration (z/OS and z/VM) */

2019-02-11T16:29:45Z

In-memory file allocation and restoration (z/OS and z/VM)

← Older revision		Revision as of 16:29, 11 February 2019
Line 463:		Line 463:
	</ul>		</ul>
	<p>		<p>
	When you create an in-memory file, the default <var>FRCVOPT</var> parameter value is X'24', which means that this file does not participate in journal and checkpoint logging.</p>		When you create an in-memory file, the default <var>[[FRCVOPT_parameter\|FRCVOPT]]</var> parameter value is X'24', which means that this file does not participate in journal and checkpoint logging.</p>
	<p>		<p>
	However, remember that restoring an in-memory file with <var>RESTORE</var> from a backup will copy the <var>FRCVOPT</var> from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <code>FOPT=0</code>, which is TBO enabled, and TBO is supported. <var>REGENERATE</var> is also supported. <var>RESTART</var> recovery is not supported.		However, remember that restoring an in-memory file with <var>RESTORE</var> from a backup will copy the <var>FRCVOPT</var> from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <code><var[[FOPT_command\|FOPT]]</var>=0</code>, which is TBO enabled, and TBO is supported. <var>REGENERATE</var> is also supported. <var>RESTART</var> recovery is not supported.
	Given these caveats, if you want to provide for both <var>REGENERATE</var> recovery and TBO, the best parameter settings for in-memory files are <code>FRCVOPT=X'20'</code> and <code>FOPT=0</code>.</p>		Given these caveats, if you want to provide for both <var>REGENERATE</var> recovery and TBO, the best parameter settings for in-memory files are <code>FRCVOPT=X'20'</code> and <code>FOPT=0</code>.</p>
	<p>		<p>

DCameron: /* Dynamic allocation at OPEN time */

2019-02-11T16:27:52Z

Dynamic allocation at OPEN time

← Older revision		Revision as of 16:27, 11 February 2019
Line 439:		Line 439:
	===Dynamic allocation at OPEN time===		===Dynamic allocation at OPEN time===
	<p>		<p>
	You can open data sets that have been defined through the <var>DEFINE DATASET</var> command but that have not yet been allocated. In this case, the data set is dynamically allocated at <var>OPEN</var> time. This is equivalent to issuing a <var>DEFINE DATASET</var> command for a data set, issuing an <var>ALLOCATE</var> command to allocate it, and then opening it. No messages are displayed when the dynamic allocation is performed; messages are issued only if the allocation fails.</p>		You can open data sets that have been defined through the <var>DEFINE DATASET</var> command but that have not yet been allocated. In this case, the data set is dynamically allocated at <var>[[OPEN_command\|OPEN]]</var> time. This is equivalent to issuing a <var>DEFINE DATASET</var> command for a data set, issuing an <var>[[ALLOCATE_command\|ALLOCATE]]</var> command to allocate it, and then opening it. No messages are displayed when the dynamic allocation is performed; messages are issued only if the allocation fails.</p>
	<p>		<p>
	Data sets that have been dynamically allocated during open processing are deallocated when they are closed. This is equivalent to closing the data set and then issuing a <var>[[FREE command\|FREE]]</var> command for it.</p>		Data sets that have been dynamically allocated during open processing are deallocated when they are closed. This is equivalent to closing the data set and then issuing a <var>[[FREE command\|FREE]]</var> command for it.</p>

DCameron: /* LARGE data sets */

2019-02-11T16:26:35Z

LARGE data sets

← Older revision		Revision as of 16:26, 11 February 2019
Line 421:		Line 421:
	<li>Data sets used for dumping and/or restoring <var class="product">Model 204</var> files</li>		<li>Data sets used for dumping and/or restoring <var class="product">Model 204</var> files</li>

	<li>Data sets used for sequential output; the <var>USE</var> command or the SOUL ~~<var>~~WRITE IMAGE~~</var>~~ statement</li>		<li>Data sets used for sequential output; the <var>USE</var> command or the SOUL [[Images#Write_Image_statement\|WRITE IMAGE]] statement</li>

	<li><var class="product">Model 204</var> file data sets</li>		<li><var class="product">Model 204</var> file data sets</li>

DCameron: /* LARGE data sets */

2019-02-11T16:25:06Z

LARGE data sets

← Older revision		Revision as of 16:25, 11 February 2019
Line 416:		Line 416:
	You can define a <var>LARGE</var> (> 64K tracks) data set under only z/OS 1.7 or later. The <var>LARGE</var> argument applies to:		You can define a <var>LARGE</var> (> 64K tracks) data set under only z/OS 1.7 or later. The <var>LARGE</var> argument applies to:
	<ul>		<ul>
	<li>[[Tracking_system_activity_(CCAJRNL,_CCAAUDIT,_CCAJLOG)#CCAJRNL\|CCAJRNL]], CCAJLOG, including GDG and stream-based journals and jlogs		<li>[[Tracking_system_activity_(CCAJRNL,_CCAAUDIT,_CCAJLOG)#CCAJRNL\|CCAJRNL]], [[Tracking_system_activity_(CCAJRNL,_CCAAUDIT,_CCAJLOG)#CCAAUDIT_and_CCAJLOG\|CCAJLOG]], including GDG and stream-based journals and jlogs
	<p class="note"><b>Note:</b> <var>LARGE</var> CHKPOINT data sets are supported as of Model 204 version 7.7.</p></li>		<p class="note"><b>Note:</b> <var>LARGE</var> CHKPOINT data sets are supported as of Model 204 version 7.7.</p></li>

DCameron: /* LARGE data sets */

2019-02-11T16:24:10Z

LARGE data sets

← Older revision		Revision as of 16:24, 11 February 2019
Line 416:		Line 416:
	You can define a <var>LARGE</var> (> 64K tracks) data set under only z/OS 1.7 or later. The <var>LARGE</var> argument applies to:		You can define a <var>LARGE</var> (> 64K tracks) data set under only z/OS 1.7 or later. The <var>LARGE</var> argument applies to:
	<ul>		<ul>
	<li>CCAJRNL, CCAJLOG, including GDG and stream-based journals and jlogs		<li>[[Tracking_system_activity_(CCAJRNL,_CCAAUDIT,_CCAJLOG)#CCAJRNL\|CCAJRNL]], CCAJLOG, including GDG and stream-based journals and jlogs
	<p class="note"><b>Note:</b> <var>LARGE</var> CHKPOINT data sets are supported as of Model 204 version 7.7.</p></li>		<p class="note"><b>Note:</b> <var>LARGE</var> CHKPOINT data sets are supported as of Model 204 version 7.7.</p></li>