ALLOCATE command - Revision history

DCameron: /* In-memory file allocation and restoration */

2019-02-04T16:23:36Z

In-memory file allocation and restoration

← Older revision		Revision as of 16:23, 4 February 2019
Line 186:		Line 186:

	<p>		<p>
	However, remember that restoring an in-memory file with RESTORE from a backup will copy the FRCVOPT from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <var>[[FOPT_parameter\|FOPT]]</var>=0, which is [[Transaction_back_out\|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 RESTORE from a backup will copy the FRCVOPT from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <var>[[FOPT_parameter\|FOPT]]</var>=0, which is [[Transaction_back_out\|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 REGENERATE recovery and TBO, the best parameter settings for in-memory files are FRCVOPT=X’20’ and FOPT=0.</p>		Given these caveats, if you want to provide for both REGENERATE recovery and TBO, the best parameter settings for in-memory files are FRCVOPT=X’20’ and FOPT=0.</p>

DCameron: /* In-memory file allocation and restoration */

2019-02-04T16:21:19Z

In-memory file allocation and restoration

← Older revision		Revision as of 16:21, 4 February 2019
Line 186:		Line 186:

	<p>		<p>
	However, remember that restoring an in-memory file with ~~<var>[[RESTORE_command\|~~RESTORE~~]]</var>~~ from a backup will copy the FRCVOPT from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <var>[[FOPT_parameter\|FOPT]]</var>=0, which is [[Transaction_back_out\|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 RESTORE from a backup will copy the FRCVOPT from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <var>[[FOPT_parameter\|FOPT]]</var>=0, which is [[Transaction_back_out\|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 REGENERATE recovery and TBO, the best parameter settings for in-memory files are FRCVOPT=X’20’ and FOPT=0.</p>		Given these caveats, if you want to provide for both REGENERATE recovery and TBO, the best parameter settings for in-memory files are FRCVOPT=X’20’ and FOPT=0.</p>

DCameron: /* In-memory file allocation and restoration */

2019-02-04T16:20:30Z

In-memory file allocation and restoration

← Older revision		Revision as of 16:20, 4 February 2019
Line 186:		Line 186:

	<p>		<p>
	However, remember that restoring an in-memory file with <var>[[RESTORE_command\|RESTORE]]</var> from a backup will copy the FRCVOPT from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <var>[[FOPT_parameter\|FOPT]]</var>=0, which is TBO enabled, and TBO is supported. <var>[[REGENERATE_command\|REGENERATE]]</var> is also supported. RESTART recovery is not supported.		However, remember that restoring an in-memory file with <var>[[RESTORE_command\|RESTORE]]</var> from a backup will copy the FRCVOPT from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <var>[[FOPT_parameter\|FOPT]]</var>=0, which is [[Transaction_back_out\|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 REGENERATE recovery and TBO, the best parameter settings for in-memory files are FRCVOPT=X’20’ and FOPT=0.</p>		Given these caveats, if you want to provide for both REGENERATE recovery and TBO, the best parameter settings for in-memory files are FRCVOPT=X’20’ and FOPT=0.</p>

DCameron: /* In-memory file allocation and restoration */

2019-02-04T16:18:52Z

In-memory file allocation and restoration

← Older revision		Revision as of 16:18, 4 February 2019
Line 186:		Line 186:

	<p>		<p>
	However, remember that restoring an in-memory file with RESTORE from a backup will copy the FRCVOPT from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with FOPT=0, which is TBO enabled, and TBO is supported. REGENERATE is also supported. RESTART recovery is not supported.		However, remember that restoring an in-memory file with <var>[[RESTORE_command\|RESTORE]]</var> from a backup will copy the FRCVOPT from that backup copy into the in-memory file, thus overriding the default. In-memory files are also created with <var>[[FOPT_parameter\|FOPT]]</var>=0, which is TBO enabled, and TBO is supported. <var>[[REGENERATE_command\|REGENERATE]]</var> is also supported. RESTART recovery is not supported.

	Given these caveats, if you want to provide for both REGENERATE recovery and TBO, the best parameter settings for in-memory files are FRCVOPT=X’20’ and FOPT=0.</p>		Given these caveats, if you want to provide for both REGENERATE recovery and TBO, the best parameter settings for in-memory files are FRCVOPT=X’20’ and FOPT=0.</p>

DCameron: /* VSAM files */

2019-02-04T16:13:37Z

VSAM files

← Older revision		Revision as of 16:13, 4 February 2019
Line 149:		Line 149:

	====VSAM files====		====VSAM files====
	<p>Although you can dynamically allocate an existing VSAM file to <var class="product">Model 204</var> with ALLOCATE, you cannot dynamically allocate a new VSAM file to <var class="product">Model 204</var>.</p>		<p>Although you can dynamically allocate an existing [[Accessing_BSAM_and_VSAM_files#VSAM_I.2FO_processing\|VSAM]] file to <var class="product">Model 204</var> with ALLOCATE, you cannot dynamically allocate a new VSAM file to <var class="product">Model 204</var>.</p>

	====Dynamic space allocation====		====Dynamic space allocation====

DCameron: /* Examples */

2019-02-04T16:10:00Z

Examples

← Older revision		Revision as of 16:10, 4 February 2019
Line 63:		Line 63:
	==Examples==		==Examples==
	====Example 1: Using a template from DEFINE DATASET====		====Example 1: Using a template from DEFINE DATASET====
	<p>The following example shows how the ALLOCATE command can be used to refer to a template previously created by the DEFINE DATASET command. The ALLOCATE command allocates a new (USE) data set with a name of OUTFILE, a scope of USER, and a data set name of M204.VEHICLES.REPORT. </p>		<p>The following example shows how the ALLOCATE command can be used to refer to a template previously created by the DEFINE DATASET command. The ALLOCATE command allocates a new (<var>[[USE_command\|USE]]</var>) data set with a name of OUTFILE, a scope of USER, and a data set name of M204.VEHICLES.REPORT. </p>
	<p>The LIKE phrase gives the OUTFILE data set some attributes of the SAMPLE data set created by the DEFINE DATASET command, namely a fixed block record format with a record length of 80 and a block size of 800, a data type organization of sequential, and a size of one cylinder on volume RPG001. </p>		<p>The LIKE phrase gives the OUTFILE data set some attributes of the SAMPLE data set created by the DEFINE DATASET command, namely a fixed block record format with a record length of 80 and a block size of 800, a data type organization of sequential, and a size of one cylinder on volume RPG001. </p>
	<p>The ALLOCATE command also creates an OUTFILE template that can be used in the LIKE phrase of another ALLOCATE or DEFINE DATASET command: </p>		<p>The ALLOCATE command also creates an OUTFILE template that can be used in the LIKE phrase of another ALLOCATE or DEFINE DATASET command: </p>

DCameron: /* Syntax */

2019-02-04T16:08:26Z

Syntax

← Older revision		Revision as of 16:08, 4 February 2019
Line 35:		Line 35:
	USER is the default.</p>		USER is the default.</p>
	<p>		<p>
	You need system administrator or User 0 privileges to use the SYSTEM option of SCOPE. Without these privileges, you can only use USER or allow SCOPE to default to USER, <i>and</i> you can allocate only those types of data sets allowed by the current setting of the <var ~~class="product"~~>~~Model 204~~</var> ~~ALOCPRIV~~ parameter.</p>		You need system administrator or User 0 privileges to use the SYSTEM option of SCOPE. Without these privileges, you can only use USER or allow SCOPE to default to USER, <i>and</i> you can allocate only those types of data sets allowed by the current setting of the <var>[[ALOCPRIV_parameter\|ALOCPRIV]]</var> parameter.</p>
	<p>		<p>
	Data sets allocated with SCOPE=SYSTEM can be released (with the FREE command) only by users with system administrator or User 0 privileges. Data sets allocated with SCOPE=USER can be released by any user, depending on the setting of ALOCPRIV.</p>		Data sets allocated with SCOPE=SYSTEM can be released (with the <var>[[FREE_command\|FREE]]</var> command) only by users with system administrator or User 0 privileges. Data sets allocated with SCOPE=USER can be released by any user, depending on the setting of ALOCPRIV.</p>
	</td></tr>		</td></tr>

DCameron: /* Syntax */

2019-02-04T16:04:03Z

Syntax

← Older revision		Revision as of 16:04, 4 February 2019
Line 25:		Line 25:
	<tr>		<tr>
	<th nowrap><var>LIKE</var> previousname</th>		<th nowrap><var>LIKE</var> previousname</th>
	<td>The data set that the user is currently allocating the attributes of a previously defined data set or template. It copies the attributes of another data set or template named by a previous ALLOCATE or DEFINE DATASET command. <i>previousname</i> is the name of a previously defined data set.		<td>The data set that the user is currently allocating the attributes of a previously defined data set or template. It copies the attributes of another data set or template named by a previous ALLOCATE or <var>[[DEFINE_DATASET_command\|DEFINE DATASET]]</var> command. <i>previousname</i> is the name of a previously defined data set.
	<p>		<p>
	Used by itself, the LIKE phrase copies all the attributes of the previously defined data set. When WITH is used, the options listed in the WITH phrase dynamically override the attributes of the data set specified by the LIKE phrase. The data set name must be unique when the WITH phrase is present.</p>		Used by itself, the LIKE phrase copies all the attributes of the previously defined data set. When WITH is used, the options listed in the WITH phrase dynamically override the attributes of the data set specified by the LIKE phrase. The data set name must be unique when the WITH phrase is present.</p>

JAL: add `'s`

2018-07-23T16:26:36Z

add <var>'s

← Older revision		Revision as of 16:26, 23 July 2018
Line 265:		Line 265:
	Model DSCB (Data Set Control Block) data sets are, in most cases, no longer required. However, the example below shows how to allocate one if required. </p>		Model DSCB (Data Set Control Block) data sets are, in most cases, no longer required. However, the example below shows how to allocate one if required. </p>
	<p>		<p>
	You can create a model DSCB and the GDG's base using the following sample JCL. The model DSCB data set, in this case DSN=SAMPLE.GDGDSNAM, must reside on the same volume as the catalog for the high-level qualifier, and the DSCB name and GDG base name must be the same.</p>		You can create a model DSCB and the GDG's base using the following sample JCL. The model DSCB data set, in this case <code>DSN=SAMPLE.GDGDSNAM</code>, must reside on the same volume as the catalog for the high-level qualifier, and the DSCB name and GDG base name must be the same. </p>
	<p class="code">//M204GDG EXEC PGM=IDCAMS		<p class="code">//M204GDG EXEC PGM=IDCAMS
	//* DSN=SAMPLE.GDGDSNAM is the Model DSCB data set		//* DSN=SAMPLE.GDGDSNAM is the Model DSCB data set
Line 285:		Line 285:
	<table>		<table>
	<tr>		<tr>
	<~~th><var class="term"~~>GDGCTL</~~var></th~~>		<td>GDGCTL</td>
	<td> ~~must~~ be the same volume as that of the user catalog.</td>		<td>Must be the same volume as that of the user catalog.</td>
	</tr>		</tr>

	<tr>		<tr>
	<~~th><var class="term"~~>NAME</~~var></th~~>		<td>NAME</td>
	<td> ~~must~~ be the same as the model DSCB DSN.</td>		<td>Must be the same as the model DSCB DSN.</td>
	</tr>		</tr>

Line 297:		Line 297:

	====Creating a new GDG data set====		====Creating a new GDG data set====
	<p>To create a new GDG data set, use the GEN=+1 keyword on [[DEFINE DATASET command\|DEFINE]]/ALLOCATE. The GDG base file must have been built previously using IDCAMS, and, if required by your level of z/OS, a model DSCB must be provided. (To create a GDG base file and model DSCB, see the previous example.)</p>		<p>
			To create a new GDG data set, use the <code>GEN=+1</code> keyword on <var>[[DEFINE DATASET command\|DEFINE]]</var>/<var>ALLOCATE</var>. The GDG base file must have been built previously using IDCAMS, and, if required by your level of z/OS, a model DSCB must be provided. (To create a GDG base file and model DSCB, see the previous example.) </p>

	====Examples for GDG usage====		====Examples for GDG usage====
	<ul>		<ul>
	<li>DEFINE/ALLOCATE a new generation of a GDG data set.		<li><var>DEFINE/ALLOCATE</var> a new generation of a GDG data set:
	<p class="code">DEFINE DATASET OUTGDG WITH SCOPE=SYSTEM -		<p class="code">DEFINE DATASET OUTGDG WITH SCOPE=SYSTEM -
	DSNAME=SAMPLE.GDGDSNAM LRECL=80 BLKSIZE=800 -		DSNAME=SAMPLE.GDGDSNAM LRECL=80 BLKSIZE=800 -
Line 307:		Line 308:
	UNIT=DISK		UNIT=DISK
	ALLOCATE OUTGDG		ALLOCATE OUTGDG
	FREE OUTGDG		FREE OUTGDG </p></li>
	</p>
	</li>

	<li>DEFINE/ALLOCATE a generation data set previously allocated in this job step. This is not a +2 generation but the same +1 generation previously allocated, freed and now reallocated as OLD.		<li><var>DEFINE/ALLOCATE</var> a generation data set previously allocated in this job step. This is not a +2 generation but the same +1 generation previously allocated, freed and now reallocated as <code>OLD</code>:
	<p class="code">DEFINE DATASET OUTGDG WITH SCOPE=SYSTEM -		<p class="code">DEFINE DATASET OUTGDG WITH SCOPE=SYSTEM -
	DSNAME=SAMPLE.GDGDSNAM GEN=+1 OLD		DSNAME=SAMPLE.GDGDSNAM GEN=+1 OLD
Line 317:		Line 316:
	</p></li>		</p></li>

	<li>DEFINE/ALLOCATE a new generation data set with DCB information different than that of a previous generation of the GDG.		<li><var>DEFINE/ALLOCATE</var> a new generation data set with DCB information different than that of a previous generation of the GDG:
	<p class="code">DEFINE DATASET OUTGDG2 WITH SCOPE=SYSTEM -		<p class="code">DEFINE DATASET OUTGDG2 WITH SCOPE=SYSTEM -
	DSNAME=SAMPLE.GDGDSNAM LRECL=132 BLKSIZE=13200 RECFM=FB -		DSNAME=SAMPLE.GDGDSNAM LRECL=132 BLKSIZE=13200 RECFM=FB -
Line 330:		Line 329:
	Due to the nature of dynamic allocation (SVC99), however, an allocation of a GDG data set for input refers to the same data set for the duration of the job or Online session, even if generations are added to the GDG.</p>		Due to the nature of dynamic allocation (SVC99), however, an allocation of a GDG data set for input refers to the same data set for the duration of the job or Online session, even if generations are added to the GDG.</p>
	<p>		<p>
	If another <var class="product">Model 204</var> job allocates a new GDG generation in the same GDG base file after the job starts, <var class="product">Model 204</var>'s allocation is not updated and no longer has the correct current generation number. Issuing FREE and ALLOCATE commands does not alter this behavior. The Online session or job must be recycled to reflect the current GDG base catalog structure for GDG input. To avoid such problems, allocate a GDG once per GDG base file in any run of <var class="product">Model 204</var>.</p>		If another <var class="product">Model 204</var> job allocates a new GDG generation in the same GDG base file after the job starts, <var class="product">Model 204</var>'s allocation is not updated and no longer has the correct current generation number. Issuing <var>FREE</var> and <var>ALLOCATE</var> commands does not alter this behavior. The Online session or job must be recycled to reflect the current GDG base catalog structure for GDG input. To avoid such problems, allocate a GDG once per GDG base file in any run of <var class="product">Model 204</var>. </p>

	[[Category: System administrator commands]]		[[Category: System administrator commands]]
	[[Category: User commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* Allocating LARGE data sets */

2017-03-31T15:40:04Z

Allocating LARGE data sets

← Older revision		Revision as of 15:40, 31 March 2017
Line 162:		Line 162:
	<p>		<p>
	LARGE CHKPOINT data sets are supported in Model 204 version 7.7 and later.</p>		LARGE CHKPOINT data sets are supported in Model 204 version 7.7 and later.</p>
	~~<li>~~		<p class="note"><b>Note:</b> When dynamically allocating a pre-existing, LARGE dataset, make sure to use LARGE and SAM in the ALLOCATE command:
	<p><b>Note:</b~~></p>~~
	<p> When dynamically allocating a pre-existing, LARGE dataset, make sure to use LARGE and SAM in the ALLOCATE command:~~</p>~~
	<ul>		<ul>
	<li>For non-Model 204, sequential files:		<li>For non-Model 204, sequential files: <br />
	<p> ALLOCATE OUTFILEA WITH OLD LARGE SAM DSN=OUTFILEA.M204</p></li>		<code>ALLOCATE OUTFILEA WITH OLD LARGE SAM DSN=OUTFILEA.M204</code></li>
	<li>For Model 204 database files:		<li>For Model 204 database files: <br />
	<p> ALLOCATE MYM204DB WITH OLD LARGE SAM DSN=MYM204DB.M204</p></li>		<code>ALLOCATE MYM204DB WITH OLD LARGE SAM DSN=MYM204DB.M204</code></li>
	</ul>		</ul></p>

	====Update units====		====Update units====

ALLOCATE command - Revision history

DCameron: /* In-memory file allocation and restoration */

DCameron: /* In-memory file allocation and restoration */

DCameron: /* In-memory file allocation and restoration */

DCameron: /* In-memory file allocation and restoration */

DCameron: /* VSAM files */

DCameron: /* Examples */

DCameron: /* Syntax */

DCameron: /* Syntax */

JAL: add 's

ELowell: /* Allocating LARGE data sets */

JAL: add `'s`