CREATE command: File - Revision history

DCameron: /* Usage notes */

2019-02-11T15:16:58Z

Usage notes

← Older revision		Revision as of 15:16, 11 February 2019
Line 83:		Line 83:
	==Usage notes==		==Usage notes==
	<ul>		<ul>
	<li><var>CREATE FILE</var> creates a <var class="product">Model 204</var> file. It sets the file parameters and builds the File Control Table (FCT). It should be issued after the values for file parameters are calculated and data sets are allocated. After a file is created, it must be opened and initialized (see the <var>[[OPEN FILE command\|OPEN FILE]]</var> and <var>[[INITIALIZE command\|INITIALIZE]]</var> commands). </li>		<li><var>CREATE FILE</var> creates a <var class="product">Model 204</var> file. It sets the file parameters and builds the [[File_Control_Table_(File_architecture)\|File Control Table (FCT)]]. It should be issued after the values for file parameters are calculated and data sets are allocated. After a file is created, it must be opened and initialized (see the <var>[[OPEN FILE command\|OPEN FILE]]</var> and <var>[[INITIALIZE command\|INITIALIZE]]</var> commands). </li>

	<li>The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk and can result in a significant reduction in elapsed time for the CREATE process, especially in large files. However, if one or more of the data sets in the file are new, you must use <var>FORMAT</var>.		<li>The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk and can result in a significant reduction in elapsed time for the CREATE process, especially in large files. However, if one or more of the data sets in the file are new, you must use <var>FORMAT</var>.

DCameron: /* Syntax */

2019-02-11T15:14:24Z

Syntax

← Older revision		Revision as of 15:14, 11 February 2019
Line 57:		Line 57:
	<tr>		<tr>
	<th>parameter=value</th>		<th>parameter=value</th>
	<td><var class="product">Model 204</var> file parameters. Any number of PARAMETER statements can immediately follow the command, and each statement can contain as many parameters in any order as will fit on one input line. File parameters are optional. If you specify no values for the BSIZE, CSIZE, and DSIZE parameters, defaults are used. However, you can calculate and set values for parameters as described in [[Managing file and table sizes]].</td>		<td><var class="product">Model 204</var> file parameters. Any number of PARAMETER statements can immediately follow the command, and each statement can contain as many parameters in any order as will fit on one input line. File parameters are optional. If you specify no values for the <var>[[BSIZE_parameter\|BSIZE]]</var>, <var>[[CSIZE_parameter\|CSIZE]]</var>, and <var>[[DSIZE_parameter\|DSIZE]]</var> parameters, defaults are used. However, you can calculate and set values for parameters as described in [[Managing file and table sizes]].</td>
	</tr>		</tr>
	</table>		</table>

DCameron: /* Syntax */

2019-02-11T15:11:50Z

Syntax

← Older revision		Revision as of 15:11, 11 February 2019
Line 22:		Line 22:
	<th>filename</th>		<th>filename</th>
	<td>The name of the <var class="product">Model 204</var> file that is being created (1 to 8 characters; 1 to 7 on DOS systems).		<td>The name of the <var class="product">Model 204</var> file that is being created (1 to 8 characters; 1 to 7 on DOS systems).
	<p>The file name cannot be FILE or GROUP and cannot start with CCA, SYS, OUT, TAPE, or a number. The only exception is CCASYS: it can be created in a single user run with the <var>[[SYSOPT parameter\|SYSOPT]]</var> X’01’ bit turned off to prevent Model 204 from opening CCASYS to make it available for APSY.</p>		<p>The file name cannot be FILE or GROUP and cannot start with CCA, SYS, OUT, TAPE, or a number. The only exception is CCASYS: it can be created in a single user run with the <var>[[SYSOPT parameter\|SYSOPT]]</var> X’01’ bit turned off to prevent Model 204 from opening CCASYS to make it available for [[Application_Subsystem_development\|APSY]].</p>
	<p>Otherwise, <var class="term">filename</var> can contain only uppercase letters, numbers, and the following special characters:		<p>Otherwise, <var class="term">filename</var> can contain only uppercase letters, numbers, and the following special characters:
	</p>		</p>

Dme: /* Syntax */

2018-04-25T23:18:27Z

Syntax

← Older revision		Revision as of 23:18, 25 April 2018
Line 8:		Line 8:

	==Syntax==		==Syntax==
	<p class="syntax">CREATE [FILE] [(FORMAT) \| (NOFORMAT)] <var class="term">filename</var>		<p class="syntax">CREATE [FILE] [(FORMAT) \| (NOFORMAT)] <var class="term">filename</var> [FROM <var class="term">ddname</var> [,<var class="term">ddname</var>]...]
	[FROM <var class="term">ddname</var> [,<var class="term">ddname</var>]...]
	[PARAMETER <var class="term">parameter</var>=<var class="term">value</var> [,<var class="term">parameter</var>=<var class="term">value</var>]...]		[PARAMETER <var class="term">parameter</var>=<var class="term">value</var> [,<var class="term">parameter</var>=<var class="term">value</var>]...]
	[PARAMETER <var class="term">parameter</var>=<var class="term">value</var> [,<var class="term">parameter</var>=<var class="term">value</var>]...]		[PARAMETER <var class="term">parameter</var>=<var class="term">value</var> [,<var class="term">parameter</var>=<var class="term">value</var>]...]
Line 41:		Line 40:

	<p>		<p>
	The file name must be the ~~ddname~~ of the first or only data set in the file.</p>		The file name must be the DD name of the first or only data set in the file.</p>
	</td></tr>		</td></tr>

	<tr>		<tr>
	<th>ddname</th>		<th>ddname</th>
	<td>The name of a data set from which to create the file; it is required when the file is being created from more than one data set. The first <var class="term">ddname</var> specified must match <var class="term">filename</var>.		<td>The DD name of a data set from which to create the file; it is required when the file is being created from more than one data set. The first <var class="term">ddname</var> specified must match <var class="term">filename</var>.
	<p>		<p>
	<var class="term">ddname</var> cannot be longer than eight characters; if it is, the command is rejected and the following message is issued: </p>		<var class="term">ddname</var> cannot be longer than eight characters; if it is, the command is rejected and the following message is issued: </p>
Line 66:		Line 65:
	<li>The <var>FROM</var> clause is optional for files containing a single data set.</li>		<li>The <var>FROM</var> clause is optional for files containing a single data set.</li>

	<li>If specified, the <var class="term">ddname</var> of the first data set must match <var class="term">filename</var>. You can use a continuation character to enter ~~long data set~~ lists in the <var>FROM</var> ~~statement~~.</li>		<li>If specified, the <var class="term">ddname</var> of the first data set must match <var class="term">filename</var>. You can use a continuation character to enter DD name lists in the <var>FROM</var> clause.</li>

	<li><var>NO FORMAT</var> is a synonym for <var>NOFORMAT</var>.</li>		<li><var>NO FORMAT</var> is a synonym for <var>NOFORMAT</var>.</li>

JAL: misc formatting

2018-04-25T22:09:52Z

misc formatting

← Older revision		Revision as of 22:09, 25 April 2018
Line 18:		Line 18:
	</p>		</p>

	~~<b>~~Where:~~</b>~~		Where:
	<table>		<table>
	<tr>		<tr>
Line 24:		Line 24:
	<td>The name of the <var class="product">Model 204</var> file that is being created (1 to 8 characters; 1 to 7 on DOS systems).		<td>The name of the <var class="product">Model 204</var> file that is being created (1 to 8 characters; 1 to 7 on DOS systems).
	<p>The file name cannot be FILE or GROUP and cannot start with CCA, SYS, OUT, TAPE, or a number. The only exception is CCASYS: it can be created in a single user run with the <var>[[SYSOPT parameter\|SYSOPT]]</var> X’01’ bit turned off to prevent Model 204 from opening CCASYS to make it available for APSY.</p>		<p>The file name cannot be FILE or GROUP and cannot start with CCA, SYS, OUT, TAPE, or a number. The only exception is CCASYS: it can be created in a single user run with the <var>[[SYSOPT parameter\|SYSOPT]]</var> X’01’ bit turned off to prevent Model 204 from opening CCASYS to make it available for APSY.</p>
	<p>Otherwise, <var class="term">filename</var> can contain only uppercase letters, numbers, and the following special characters:</p>		<p>Otherwise, <var class="term">filename</var> can contain only uppercase letters, numbers, and the following special characters:
	<table>		</p>
			<table>
	<tr class="head"> <th>Special character name</th> <th>Keyboard symbol</th> </tr>		<tr class="head"> <th>Special character name</th>
			<th>Keyboard symbol</th> </tr>

	<tr> <th><var>At sign </var></th> <td>(@)</td> </tr>		<tr> <th><var>At sign </var></th>
			<td>(@)</td> </tr>

	<tr> <th><var>Pound sign </var></th> <td>(#)</td> </tr>		<tr> <th><var>Pound sign </var></th>
			<td>(#)</td> </tr>

	<tr> <th><var>Dollar sign </var></th> <td>($) <br />(alternately displayed as £)</td> </tr>		<tr> <th><var>Dollar sign </var></th>
			<td>($) <br />(alternately displayed as £)</td> </tr>
	</table>		</table>

Line 45:		Line 49:
	<p>		<p>
	<var class="term">ddname</var> cannot be longer than eight characters; if it is, the command is rejected and the following message is issued: </p>		<var class="term">ddname</var> cannot be longer than eight characters; if it is, the command is rejected and the following message is issued: </p>
	<p class="code">M204.1903: ~~%C EXCEEDS~~ 8 ~~CHARACTERS IN LENGTH~~		<p class="code">M204.1903: <i>item</i> exceeds 8 characters in length
	</p>		</p>
	<p>		<p>
Line 79:		Line 83:

	==Usage notes==		==Usage notes==
			<ul>
			<li><var>CREATE FILE</var> creates a <var class="product">Model 204</var> file. It sets the file parameters and builds the File Control Table (FCT). It should be issued after the values for file parameters are calculated and data sets are allocated. After a file is created, it must be opened and initialized (see the <var>[[OPEN FILE command\|OPEN FILE]]</var> and <var>[[INITIALIZE command\|INITIALIZE]]</var> commands). </li>

			<li>The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk and can result in a significant reduction in elapsed time for the CREATE process, especially in large files. However, if one or more of the data sets in the file are new, you must use <var>FORMAT</var>.
	<p>		<p>
	<var>CREATE FILE</var> creates a <var class="product">Model 204</var> file. It sets the file parameters and builds the File Control Table (FCT). It should be issued after the values for file parameters are calculated and data sets are allocated. After a file is created, it must be opened and initialized (see the [[OPEN FILE command]] and the [[INITIALIZE command]]). </p>		If <var>NOFORMAT</var> is used and the disk space of the first or only data set is unformatted, Model 204 will force formatting anyway and issue the following message.
	~~<p>~~
	The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk and can result in a significant reduction in elapsed time for the CREATE process, especially in large files. However, if one or more of the data sets in the file are new, you must use <var>FORMAT</var>.</p>
	~~<p>~~
	If <var>NOFORMAT</var> is used and the disk space of the first or only data set is unformatted, Model 204 will force formatting anyway and issue the following message. ~~</p>~~
	~~<p>~~
	~~M204.0793: I/O ERROR FORCED FORMATTING~~
	</p>		</p>
			<p class="code">M204.0793: I/O error forced formatting </p>
	<p>		<p>
	In the case of a ~~multi-~~data ~~set file~~, Model 204 ~~only~~ checks formatting of the first data set. If the first data set ~~has been~~ formatted, but subsequent data sets ~~have~~ not, ~~then~~ the CREATE FILE (NOFORMAT) command ~~will fail~~ and the following message ~~will be~~ issued:~~</p>~~		In the case of a file that has multiple data sets, Model 204 checks the formatting of only the first data set. If the first data set is formatted, but subsequent data sets are not, the <code>CREATE FILE (NOFORMAT)</code> command fails, and the following message is issued:
	~~<p>~~
	~~M204.2369: DKUPDT DISK WRITE FAILURE: </p>~~
	~~<p>~~
	<var>CREATE</var> establishes the file name and ddnames for all data sets in the file. Once a file is created, you can change the file name and ddname only by recreating the file or by running the [[RESTORE command]]. However, you can add new data sets to the file with the [[INCREASE command]].</p>
	~~<p>~~
	When it processes <var>CREATE FILE</var>, <var class="product">Model 204</var> ends any update unit in progress and begins a [[File integrity and recovery#Model 204 update units\|non-backoutable update unit]].
	</p>		</p>
	<p>		<p class="code">M204.2369: DKUPDT disk write failure: </p></li>
	~~See~~ [[~~Creating~~ a ~~file~~]] ~~for~~ more information about file creation and file parameters.</p>
			<li><var>CREATE</var> establishes the file name and DDnames for all data sets in the file. Once a file is created, you can change the file name and DDname only by recreating the file or by running the <var>[[RESTORE command\|RESTORE]]</var> command. However, you can add new data sets to the file with the <var>[[INCREASE command\|INCREASE]]</var> command. </li>

			<li>When it processes <var>CREATE FILE</var>, <var class="product">Model 204</var> ends any update unit in progress and begins a [[File integrity and recovery#Model 204 update units\|non-backoutable update unit]].
			</li>

			<li>For more information about file creation and file parameters, see [[Creating a file]].</li>
			</ul>

	[[Category: Superuser commands]]		[[Category: Superuser commands]]
	[[Category:Commands]]		[[Category:Commands]]

JDamon: /* Usage notes */

2018-04-25T18:41:14Z

Usage notes

← Older revision		Revision as of 18:41, 25 April 2018
Line 89:		Line 89:
	</p>		</p>
	<p>		<p>
	In the case of a multi-data set file, Model 204 only checks formatting of the first data set. If the first data set has been formatted, but subsequent data sets have not, then the CREATE will fail ~~when using the NOFORMAT option~~ and the following message will be issued:</p>		In the case of a multi-data set file, Model 204 only checks formatting of the first data set. If the first data set has been formatted, but subsequent data sets have not, then the CREATE FILE (NOFORMAT) command will fail and the following message will be issued:</p>
	<p>		<p>
	M204.2369: DKUPDT DISK WRITE FAILURE: </p>		M204.2369: DKUPDT DISK WRITE FAILURE: </p>

JDamon: Clarified use of NOFORMAT

2018-04-25T18:09:59Z

Clarified use of NOFORMAT

← Older revision		Revision as of 18:09, 25 April 2018
Line 82:		Line 82:
	<var>CREATE FILE</var> creates a <var class="product">Model 204</var> file. It sets the file parameters and builds the File Control Table (FCT). It should be issued after the values for file parameters are calculated and data sets are allocated. After a file is created, it must be opened and initialized (see the [[OPEN FILE command]] and the [[INITIALIZE command]]). </p>		<var>CREATE FILE</var> creates a <var class="product">Model 204</var> file. It sets the file parameters and builds the File Control Table (FCT). It should be issued after the values for file parameters are calculated and data sets are allocated. After a file is created, it must be opened and initialized (see the [[OPEN FILE command]] and the [[INITIALIZE command]]). </p>
	<p>		<p>
	The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk. If one or more of the data sets in the file are new, use <var>FORMAT</var>.</p>		The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk and can result in a significant reduction in elapsed time for the CREATE process, especially in large files. However, if one or more of the data sets in the file are new, you must use <var>FORMAT</var>.</p>
	<p>		<p>
	If <var>NOFORMAT</var> is used and the disk space is unformatted, Model 204 will force formatting anyway and issue the following message. </p>		If <var>NOFORMAT</var> is used and the disk space of the first or only data set is unformatted, Model 204 will force formatting anyway and issue the following message. </p>
	<p>		<p>
	M204.0793: I/O ERROR FORCED FORMATTING		M204.0793: I/O ERROR FORCED FORMATTING
	</p>		</p>
	<p>		<p>
	In the case of a multi-~~dataset~~ file, Model 204 ~~might not be able to detect that one~~ of the ~~datasets is unformatted~~. ~~In this case~~, the ~~initialize~~ will fail ~~with~~ the message:</p>		In the case of a multi-data set file, Model 204 only checks formatting of the first data set. If the first data set has been formatted, but subsequent data sets have not, then the CREATE will fail when using the NOFORMAT option and the following message will be issued:</p>
	<p>		<p>
	M204.2369: DKUPDT DISK WRITE FAILURE: </p>		M204.2369: DKUPDT DISK WRITE FAILURE: </p>

ELowell at 19:21, 24 April 2018

2018-04-24T19:21:51Z

← Older revision		Revision as of 19:21, 24 April 2018
Line 84:		Line 84:
	The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk. If one or more of the data sets in the file are new, use <var>FORMAT</var>.</p>		The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk. If one or more of the data sets in the file are new, use <var>FORMAT</var>.</p>
	<p>		<p>
	If <var>NOFORMAT</var> is used and the disk space is unformatted, we will force formatting anyway and issue the following message. </p>		If <var>NOFORMAT</var> is used and the disk space is unformatted, Model 204 will force formatting anyway and issue the following message. </p>
	<p>		<p>
	M204.0793: I/O ERROR FORCED FORMATTING		M204.0793: I/O ERROR FORCED FORMATTING
	</p>		</p>
	<p>		<p>
	In the case of a multi-dataset file, ~~we may~~ not be able to detect that one of the datasets is unformatted. In this case, the initialize will fail with the message:</p>		In the case of a multi-dataset file, Model 204 might not be able to detect that one of the datasets is unformatted. In this case, the initialize will fail with the message:</p>
	<p>		<p>
	M204.2369: DKUPDT DISK WRITE FAILURE: </p>		M204.2369: DKUPDT DISK WRITE FAILURE: </p>

Mlarocca: /* Usage notes */

2018-04-24T19:16:24Z

Usage notes

← Older revision		Revision as of 19:16, 24 April 2018
Line 83:		Line 83:
	<p>		<p>
	The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk. If one or more of the data sets in the file are new, use <var>FORMAT</var>.</p>		The default <var>FORMAT</var> option causes the <var>CREATE</var> command to physically format the disk space. <var>NOFORMAT</var> suppresses physical formatting of the disk. If one or more of the data sets in the file are new, use <var>FORMAT</var>.</p>
			<p>
			If <var>NOFORMAT</var> is used and the disk space is unformatted, we will force formatting anyway and issue the following message. </p>
			<p>
			M204.0793: I/O ERROR FORCED FORMATTING
			</p>
			<p>
			In the case of a multi-dataset file, we may not be able to detect that one of the datasets is unformatted. In this case, the initialize will fail with the message:</p>
			<p>
			M204.2369: DKUPDT DISK WRITE FAILURE: </p>
	<p>		<p>
	<var>CREATE</var> establishes the file name and ddnames for all data sets in the file. Once a file is created, you can change the file name and ddname only by recreating the file or by running the [[RESTORE command]]. However, you can add new data sets to the file with the [[INCREASE command]].</p>		<var>CREATE</var> establishes the file name and ddnames for all data sets in the file. Once a file is created, you can change the file name and ddname only by recreating the file or by running the [[RESTORE command]]. However, you can add new data sets to the file with the [[INCREASE command]].</p>

ELowell at 16:07, 23 March 2017

2017-03-23T16:07:34Z

← Older revision		Revision as of 16:07, 23 March 2017
Line 91:		Line 91:
	See [[Creating a file]] for more information about file creation and file parameters.</p>		See [[Creating a file]] for more information about file creation and file parameters.</p>

	[[Category: ~~User~~ commands]]		[[Category: Superuser commands]]
	[[Category:Commands]]		[[Category:Commands]]