DEFINE command - Revision history

ELowell at 21:32, 6 April 2017

2017-04-06T21:32:17Z

← Older revision		Revision as of 21:32, 6 April 2017
Line 16:		Line 16:
	<tr><th><var>[[DEFINE FIELD command\|DEFINE FIELD]]</var></th>		<tr><th><var>[[DEFINE FIELD command\|DEFINE FIELD]]</var></th>
	<td>Field names and attributes.</td></tr>		<td>Field names and attributes.</td></tr>

			<tr><th><var>[[DEFINE FIELDGROUP command\|DEFINE FIELDGROUP]]</var></th>
			<td>Field group contents, including associated fields and field groups.</td></tr>

	<tr><th><var>[[DEFINE FILE command\|DEFINE FILE]]</var></th>		<tr><th><var>[[DEFINE FILE command\|DEFINE FILE]]</var></th>
	<td>File synonym.</td></tr>		<td>File synonym.</td></tr>

	<tr><th><var>[[DEFINE LINK command\|DEFINE LINK]]</var></th>		<tr><th><var>[[DEFINE LINK command: Overview of intersystem network links\|DEFINE LINK]]</var></th>
	<td>Defines a network connection (used for Model 204 intersystem		<td>Defines a network connection (used for Model 204 intersystem
	connections).</td></tr>		connections).</td></tr>
Line 27:		Line 30:
	<td>Output definition to direct printed output.</td></tr>		<td>Output definition to direct printed output.</td></tr>

	<tr><th><var>[[DEFINE PROCESS command\|DEFINE PROCESS]]</var></th>		<tr><th><var>[[DEFINE PROCESS command: Overview of intersystem network process\|DEFINE PROCESS]]</var></th>
	<td>Process for reference by User Language statements, and the attributes of the process (used for Model 204 intersystem connections).</td></tr>		<td>Process for reference by User Language statements, and the attributes of the process (used for Model 204 intersystem connections).</td></tr>

	<tr>		<tr>
	<th nowrap><var>[[DEFINE PROCESSGROUP command\|DEFINE PROCESSGROUP]]</var></th>		<th nowrap><var>[[DEFINE PROCESSGROUP command: Overview of intersystem network processgroup\|DEFINE PROCESSGROUP]]</var></th>
	<td>Processgroup (used for Model 204 intersystem connections).</td></tr>		<td>Processgroup (used for Model 204 intersystem connections).</td></tr>

ELowell at 21:20, 6 April 2017

2017-04-06T21:20:01Z

← Older revision		Revision as of 21:20, 6 April 2017
Line 10:		Line 10:

	<tr>		<tr>
	<th>DEFINE DATASET</th>		<th><var>[[DEFINE DATASET command\|DEFINE DATASET]]</var></th>
	<td>Physical characteristics of a data set, file, or template, or identifies non-Model 204 files.</td>		<td>Physical characteristics of a data set, file, or template, or identifies non-Model 204 files.</td>
	</tr>		</tr>

	<tr>		<tr><th><var>[[DEFINE FIELD command\|DEFINE FIELD]]</var></th>
	<th>DEFINE FIELD</th>
	<td>Field names and attributes.</td></tr>		<td>Field names and attributes.</td></tr>

	<tr><th>DEFINE FILE</th>		<tr><th><var>[[DEFINE FILE command\|DEFINE FILE]]</var></th>
	<td>File synonym.</td></tr>		<td>File synonym.</td></tr>

	<tr><th>DEFINE LINK</th>		<tr><th><var>[[DEFINE LINK command\|DEFINE LINK]]</var></th>
	<td>Defines a network connection (used for Model 204 intersystem		<td>Defines a network connection (used for Model 204 intersystem
	connections).</td></tr>		connections).</td></tr>

	<tr><th>DEFINE PRINTER</th>		<tr><th><var>[[DEFINE PRINTER command\|DEFINE PRINTER]]</var></th>
	<td>Output definition to direct printed output.</td></tr>		<td>Output definition to direct printed output.</td></tr>

	<tr><th>DEFINE PROCESS</th>		<tr><th><var>[[DEFINE PROCESS command\|DEFINE PROCESS]]</var></th>
	<td>Process for reference by User Language statements, and the attributes of the process (used for Model 204 intersystem connections).</td></tr>		<td>Process for reference by User Language statements, and the attributes of the process (used for Model 204 intersystem connections).</td></tr>

	<tr><th nowrap>DEFINE PROCESSGROUP</th>		<tr>
			<th nowrap><var>[[DEFINE PROCESSGROUP command\|DEFINE PROCESSGROUP]]</var></th>
	<td>Processgroup (used for Model 204 intersystem connections).</td></tr>		<td>Processgroup (used for Model 204 intersystem connections).</td></tr>

	<tr><th>DEFINE PUNCH</th>		<tr><th><var>[[DEFINE PUNCH command\|DEFINE PUNCH]]</var></th>
	<td>Output definition to direct punched output.</td></tr>		<td>Output definition to direct punched output.</td></tr>

	<tr><th>DEFINE REMOTE</th>		<tr><th><var>[[DEFINE REMOTE command\|DEFINE REMOTE]]</var></th>
	<td>Remote LU (used for Horizon CNOS connections).</td></tr>		<td>Remote LU (used for Horizon CNOS connections).</td></tr>

	<tr><th>DEFINE SESSIONGROUP</th>		<tr><th><var>[[DEFINE SESSIONGROUP command\|DEFINE SESSIONGROUP]]</var></th>
	<td>Sessiongroup (used for Horizon CNOS connections).</td></tr>		<td>Sessiongroup (used for Horizon CNOS connections).</td></tr>

	<tr><th>DEFINE STREAM</th>		<tr><th><var>[[DEFINE STREAM command\|DEFINE STREAM]]</var></th>
	<td>Sequential I/O streams.</td></tr>		<td>Sequential I/O streams.</td></tr>
	</table>		</table>
Line 82:		Line 82:
	<tr>		<tr>
	<th>options</th>		<th>options</th>
	<td>Options for the particular forms of the DEFINE command are described ~~in sections that follow~~. Options must be separated by commas or by one or more blanks.</td>		<td>Options for the particular forms of the <var>DEFINE</var> command, such as <var>DEFINE DATASET</var>, are described on the page for each command form. Options must be separated by commas or by one or more blanks.</td>
	</tr>		</tr>
	</table>		</table>

JAL at 20:36, 10 October 2014

2014-10-10T20:36:06Z

← Older revision		Revision as of 20:36, 10 October 2014
Line 2:		Line 2:
	<br/>Defines a Model 204 entity		<br/>Defines a Model 204 entity

	<p>The DEFINE command performs the following functions:</p>		<p>
			The <var>DEFINE</var> command performs the following functions:</p>
	<table class="thJustBold">		<table class="thJustBold">
	<tr class="head">		<tr class="head">
Line 47:		Line 48:

	===General format of the DEFINE command===		===General format of the DEFINE command===
	The syntax of the DEFINE command is as follows:		The syntax of the <var>DEFINE</var> command is as follows:
	<p class="syntax">DEFINE		<p class="syntax">DEFINE
	{ DATASET \| FIELD \| FILE \| LINK \| PRINTER \| PROCESS }		{ DATASET \| FIELD \| FILE \| LINK \| PRINTER \| PROCESS
	\| PROCESSGROUP \| PUNCH \| REMOTE \| SESSIONGROUP		\| PROCESSGROUP \| PUNCH \| REMOTE \| SESSIONGROUP \| STREAM }
	\| STREAM} <span class="term">name</span>		<span class="term">name</span> [LIKE <span class="term">previousname</span>] [WITH SCOPE=SYSTEM]
	[LIKE <span class="term">previousname</span>] [WITH SCOPE=SYSTEM]
	[<span class="term">options</span> [<span class="term">options</span>]...]		[<span class="term">options</span> [<span class="term">options</span>]...]
	</p>		</p>
Line 94:		Line 94:
	</p>		</p>
	<p>		<p>
	In the example, the correct ID specification PRINTER1 is misspelled. However, the DEFINE command runs. An error occurs if an attempt is made subsequently to run a USE P1 command that accesses the incorrect DEFINE PRINTER definition. </p>		In the example, the correct ID specification <code>PRINTER1</code> is misspelled. However, the <var>DEFINE</var> command runs. An error occurs if an attempt is made subsequently to run a <code>USE P1</code> command that accesses the incorrect <var>DEFINE PRINTER</var> definition. </p>
	<p>		<p>
	The example also shows the use of the hyphen (<tt>-</tt>) as a continuation character. A continuation character preceded by a space is required at the end of an input line, if the command parameters continue onto the next line.</p>		The example also shows the use of the hyphen (<tt>-</tt>) as a continuation character. A continuation character preceded by a space is required at the end of an input line, if the command parameters continue onto the next line.</p>
Line 100:		Line 100:
	==Usage notes==		==Usage notes==
	<ul>		<ul>
	<li>You can create a template and assign it a name with the DEFINE command (except for DEFINE FIELD). The template can contain all the attributes needed to create a new template. You can refer to the template name in a DEFINE command or in an ALLOCATE command where a DEFINE DATASET command previously defined the template. The attributes of a template override those of the previously defined entity.</li>		<li>You can create a template and assign it a name with the <var>DEFINE</var> command (except for <var>DEFINE FIELD</var>). The template can contain all the attributes needed to create a new template. You can refer to the template name in a <var>DEFINE</var> command or in an <var>ALLOCATE</var> command where a <var>DEFINE DATASET</var> command previously defined the template. The attributes of a template override those of the previously defined entity.</li>

	<li>The definition of any entity can be replaced by entering a DEFINE command, the previously defined entity name, and any attributes to be altered. Issuing a DEFINE command with the same name as one presently in use overrides the current template definition. You, therefore, might unintentionally replace an existing entity definition, because <var class="product">Model 204</var> does not check if the entity name entered is unique. </li>		<li>The definition of any entity can be replaced by entering a <var>DEFINE</var> command, the previously defined entity name, and any attributes to be altered. Issuing a <var>DEFINE</var> command with the same name as one presently in use overrides the current template definition. You, therefore, might unintentionally replace an existing entity definition, because <var class="product">Model 204</var> does not check if the entity name entered is unique. </li>

	<li>When it processes a DEFINE command, <var class="product">Model 204</var> ends any current ~~User Language~~ update unit and begins a non-backoutable update unit. If a <var class="product">Model 204</var> command non-backoutable update unit is in progress, the DEFINE command is included in that [[File integrity and recovery#Update units and transactions\|update unit]]. </li>		<li>When it processes a <var>DEFINE</var> command, <var class="product">Model 204</var> ends any current SOUL update unit and begins a non-backoutable update unit. If a <var class="product">Model 204</var> command non-backoutable update unit is in progress, the <var>DEFINE</var> command is included in that [[File integrity and recovery#Update units and transactions\|update unit]]. </li>

	<li>DEFINE commands that contain invalid or mutually exclusive options are rejected by <var class="product">Model 204</var>. </li>		<li><var>DEFINE</var> commands that contain invalid or mutually exclusive options are rejected by <var class="product">Model 204</var>. </li>
	</ul>		</ul>

	[[Category:Commands]]		[[Category:Commands]]

JAL: /* General format of the DEFINE command */

2014-10-10T20:27:34Z

General format of the DEFINE command

← Older revision		Revision as of 20:27, 10 October 2014
Line 49:		Line 49:
	The syntax of the DEFINE command is as follows:		The syntax of the DEFINE command is as follows:
	<p class="syntax">DEFINE		<p class="syntax">DEFINE
	{DATASET \| FIELD \| FILE \| LINK \| PRINTER \| PROCESS		{ DATASET \| FIELD \| FILE \| LINK \| PRINTER \| PROCESS }
	\| PROCESSGROUP \| PUNCH \| REMOTE \| SESSIONGROUP		\| PROCESSGROUP \| PUNCH \| REMOTE \| SESSIONGROUP
	\| STREAM} <span class="term">name</span>		\| STREAM} <span class="term">name</span>
Line 60:		Line 60:
	<tr>		<tr>
	<th>name</th>		<th>name</th>
	<td> ~~is the~~ <var class="product">Model 204</var> name of the entity defined. The name in a data set, link, printer, process, processgroup, punch, or stream definition can be up to 8 characters in length. Field names can be up to 255 characters in length.</td>		<td>The <var class="product">Model 204</var> name of the entity defined. The name in a data set, link, printer, process, processgroup, punch, or stream definition can be up to 8 characters in length. Field names can be up to 255 characters in length.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th><var>LIKE</var></th>		<th><var>LIKE</var></th>
	<td> ~~gives~~ the entity that you are currently defining the attributes of a previously defined entity or template specified by the phrase LIKE <i>previousname</i>. LIKE is not supported for field definitions.</td>		<td>Gives the entity that you are currently defining the attributes of a previously defined entity or template specified by the phrase <code>LIKE <i>previousname</i></code>. <var>LIKE</var> is not supported for field definitions.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th>previousname</th>		<th>previousname</th>
	<td> ~~means the~~ name of the previously defined entity or template.		<td>The name of the previously defined entity or template.
	<p>Used by itself, LIKE copies all the attributes of the entity defined by a previous DEFINE command. When used with WITH, the options listed in the WITH phrase override the attributes of the entity specified by the LIKE phrase. </p>		<p>Used by itself, <var>LIKE</var> copies all the attributes of the entity defined by a previous <var>DEFINE</var> command. When used with <var>WITH</var>, the options listed in the <var>WITH</var> phrase override the attributes of the entity specified by the LIKE phrase. </p>
	</td>		</td>
	</tr>		</tr>
Line 77:		Line 77:
	<tr>		<tr>
	<th><var>SCOPE=SYSTEM</var></th>		<th><var>SCOPE=SYSTEM</var></th>
	<td> ~~is required~~ and indicates that the definition is available to all users for the entire run. </td>		<td>Required, and indicates that the definition is available to all users for the entire run. </td>
	</tr>		</tr>

	<tr>		<tr>
	<th>options</th>		<th>options</th>
	<td> for the particular forms of the DEFINE command are described in sections that follow. Options must be separated by commas or by one or more blanks.</td>		<td>Options for the particular forms of the DEFINE command are described in sections that follow. Options must be separated by commas or by one or more blanks.</td>
	</tr>		</tr>

	</table>		</table>

JAL at 23:09, 10 July 2014

2014-07-10T23:09:16Z

← Older revision		Revision as of 23:09, 10 July 2014
Line 3:		Line 3:

	<p>The DEFINE command performs the following functions:</p>		<p>The DEFINE command performs the following functions:</p>
	<table>		<table class="thJustBold">
	<tr>		<tr class="head">
	<th>Command</th><th>Specifies...</th>		<th>Command</th><th>Specifies...</th>
	</tr>		</tr>

	<tr>		<tr>
	<th>DEFINE DATASET</th>		<th>DEFINE DATASET</th>
	<td>Physical characteristics of a data set, file, or template, or identifies non-Model 204 files.</td>		<td>Physical characteristics of a data set, file, or template, or identifies non-Model 204 files.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th>DEFINE FIELD</th>		<th>DEFINE FIELD</th>
	<td>Field names and attributes.</td></tr>		<td>Field names and attributes.</td></tr>

	<tr><th>DEFINE FILE</th>		<tr><th>DEFINE FILE</th>
	<td>File synonym.</td></tr>		<td>File synonym.</td></tr>

	<tr><th>DEFINE LINK</th>		<tr><th>DEFINE LINK</th>
	<td>Defines a network connection (used for Model 204 intersystem		<td>Defines a network connection (used for Model 204 intersystem
	connections).</td></tr>		connections).</td></tr>

	<tr><th>DEFINE PRINTER</th>		<tr><th>DEFINE PRINTER</th>
	<td>Output definition to direct printed output.</td></tr>		<td>Output definition to direct printed output.</td></tr>

	<tr><th>DEFINE PROCESS</th>		<tr><th>DEFINE PROCESS</th>
	<td>Process for reference by User Language statements, and the attributes of the process (used for Model 204 intersystem connections).</td></tr>		<td>Process for reference by User Language statements, and the attributes of the process (used for Model 204 intersystem connections).</td></tr>
	<tr><th>DEFINE PROCESSGROUP</th>
			<tr><th nowrap>DEFINE PROCESSGROUP</th>
	<td>Processgroup (used for Model 204 intersystem connections).</td></tr>		<td>Processgroup (used for Model 204 intersystem connections).</td></tr>

	<tr><th>DEFINE PUNCH</th>		<tr><th>DEFINE PUNCH</th>
	<td>Output definition to direct punched output.</td></tr>		<td>Output definition to direct punched output.</td></tr>

	<tr><th>DEFINE REMOTE</th>		<tr><th>DEFINE REMOTE</th>
	<td>Remote LU (used for Horizon CNOS connections).</td></tr>		<td>Remote LU (used for Horizon CNOS connections).</td></tr>

	<tr><th>DEFINE SESSIONGROUP</th>		<tr><th>DEFINE SESSIONGROUP</th>
	<td>Sessiongroup (used for Horizon CNOS connections).</td></tr>		<td>Sessiongroup (used for Horizon CNOS connections).</td></tr>

	<tr><th>DEFINE STREAM</th>		<tr><th>DEFINE STREAM</th>
	<td>Sequential I/O streams.</td></tr>		<td>Sequential I/O streams.</td></tr>
Line 37:		Line 48:
	===General format of the DEFINE command===		===General format of the DEFINE command===
	The syntax of the DEFINE command is as follows:		The syntax of the DEFINE command is as follows:
	<p class="~~code~~">		<p class="syntax">DEFINE
	DEFINE
	{DATASET \| FIELD \| FILE \| LINK \| PRINTER \| PROCESS		{DATASET \| FIELD \| FILE \| LINK \| PRINTER \| PROCESS
	\| PROCESSGROUP \| PUNCH \| REMOTE \| SESSIONGROUP		\| PROCESSGROUP \| PUNCH \| REMOTE \| SESSIONGROUP
	\| STREAM} <~~var~~ class="term">name</~~var~~>		\| STREAM} <span class="term">name</span>
	[LIKE <~~var~~ class="term">previousname</~~var~~>] [WITH SCOPE=SYSTEM]		[LIKE <span class="term">previousname</span>] [WITH SCOPE=SYSTEM]
	[<~~var~~ class="term">options</~~var~~> [<~~var~~ class="term">options</~~var~~>]...]		[<span class="term">options</span> [<span class="term">options</span>]...]
	</p>		</p>

Line 76:		Line 86:

	</table>		</table>

	==Syntax notes==		==Syntax notes==
	Certain rules concerning options are checked at a point later than the time of definition. Refer to the following example:		Certain rules concerning options are checked at a point later than the time of definition. Refer to the following example:
	<p class="~~syntax~~">DEFINE PRINTER P1 WITH -		<p class="code">DEFINE PRINTER P1 WITH -
	SCOPE=SYSTEM		SCOPE=SYSTEM
	ROUTER=VM -		ROUTER=VM -
	ID=PRIIINTER1		ID=PRIIINTER1
	</p>		</p>
	<p>In the example, the correct ID specification PRINTER1 is misspelled. However, the DEFINE command runs. An error occurs if an attempt is made subsequently to run a USE P1 command that accesses the incorrect DEFINE PRINTER definition. </p>		<p>
	<p>The example also shows the use of the hyphen (-) as a continuation character. A continuation character preceded by a space is required at the end of an input line, if the command parameters continue onto the next line.</p>		In the example, the correct ID specification PRINTER1 is misspelled. However, the DEFINE command runs. An error occurs if an attempt is made subsequently to run a USE P1 command that accesses the incorrect DEFINE PRINTER definition. </p>
			<p>
			The example also shows the use of the hyphen (<tt>-</tt>) as a continuation character. A continuation character preceded by a space is required at the end of an input line, if the command parameters continue onto the next line.</p>

	==Usage notes==		==Usage notes==
	<p>You can create a template and assign it a name with the DEFINE command (except for DEFINE FIELD). The template can contain all the attributes needed to create a new template. You can refer to the template name in a DEFINE command or in an ALLOCATE command where a DEFINE DATASET command previously defined the template. The attributes of a template override those of the previously defined entity.</p>		<ul>
	<p>The definition of any entity can be replaced by entering a DEFINE command, the previously defined entity name, and any attributes to be altered. Issuing a DEFINE command with the same name as one presently in use overrides the current template definition. You, therefore, might unintentionally replace an existing entity definition, because <var class="product">Model 204</var> does not check if the entity name entered is unique. </p>		<li>You can create a template and assign it a name with the DEFINE command (except for DEFINE FIELD). The template can contain all the attributes needed to create a new template. You can refer to the template name in a DEFINE command or in an ALLOCATE command where a DEFINE DATASET command previously defined the template. The attributes of a template override those of the previously defined entity.</li>
	<p>When it processes a DEFINE command, <var class="product">Model 204</var> ends any current User Language update unit and begins a non-backoutable update unit. If a <var class="product">Model 204</var> command non-~~back outable~~ update unit is in progress, the DEFINE command is included in that update unit. ~~For more information about <var class="product">Model 204~~</~~var> update units, see the <var>Model 204 File Manager's Guide.</var> </p~~>
	<p>DEFINE commands that contain invalid or mutually exclusive options are rejected by <var class="product">Model 204</var>. </p>		<li>The definition of any entity can be replaced by entering a DEFINE command, the previously defined entity name, and any attributes to be altered. Issuing a DEFINE command with the same name as one presently in use overrides the current template definition. You, therefore, might unintentionally replace an existing entity definition, because <var class="product">Model 204</var> does not check if the entity name entered is unique. </li>

			<li>When it processes a DEFINE command, <var class="product">Model 204</var> ends any current User Language update unit and begins a non-backoutable update unit. If a <var class="product">Model 204</var> command non-backoutable update unit is in progress, the DEFINE command is included in that [[File integrity and recovery#Update units and transactions\|update unit]]. </li>

			<li>DEFINE commands that contain invalid or mutually exclusive options are rejected by <var class="product">Model 204</var>. </li>
			</ul>

	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* Syntax notes */

2013-07-29T19:17:27Z

Syntax notes

← Older revision		Revision as of 19:17, 29 July 2013
Line 83:		Line 83:
	ID=PRIIINTER1		ID=PRIIINTER1
	</p>		</p>
	<p>In the example, the correct ID specification PRINTER1 is misspelled. However, the DEFINE command ~~executes~~. An error occurs if an attempt is made subsequently to ~~execute~~ a USE P1 command that accesses the incorrect DEFINE PRINTER definition. </p>		<p>In the example, the correct ID specification PRINTER1 is misspelled. However, the DEFINE command runs. An error occurs if an attempt is made subsequently to run a USE P1 command that accesses the incorrect DEFINE PRINTER definition. </p>
	<p>The example also shows the use of the hyphen (-) as a continuation character. A continuation character preceded by a space is required at the end of an input line, if the command parameters continue onto the next line.</p>		<p>The example also shows the use of the hyphen (-) as a continuation character. A continuation character preceded by a space is required at the end of an input line, if the command parameters continue onto the next line.</p>

	==Usage notes==		==Usage notes==
	<p>You can create a template and assign it a name with the DEFINE command (except for DEFINE FIELD). The template can contain all the attributes needed to create a new template. You can refer to the template name in a DEFINE command or in an ALLOCATE command where a DEFINE DATASET command previously defined the template. The attributes of a template override those of the previously defined entity.</p>		<p>You can create a template and assign it a name with the DEFINE command (except for DEFINE FIELD). The template can contain all the attributes needed to create a new template. You can refer to the template name in a DEFINE command or in an ALLOCATE command where a DEFINE DATASET command previously defined the template. The attributes of a template override those of the previously defined entity.</p>

ELowell at 18:53, 23 July 2013

2013-07-23T18:53:31Z

@@ Line 1: / Line 1: @@
+<b>Function</b>
 <b>Where:</b>
 <table>

Alex: Automatically generated page update

2013-02-28T01:04:40Z

Automatically generated page update

New page

Where:
<table>
<tr>
<th>name</th>
<td> is the <var class="product">Model 204</var> name of the entity defined. The name in a data set, link, printer, process, processgroup, punch, or stream definition can be up to 8 characters in length. Field names can be up to 255 characters in length.</td>
</tr>

<tr>
<th><var>LIKE</var></th>
<td> gives the entity that you are currently defining the attributes of a previously defined entity or template specified by the phrase LIKE previousname. LIKE is not supported for field definitions.</td>
</tr>

<tr>
<th>previousname</th>
<td> means the name of the previously defined entity or template.
Used by itself, LIKE copies all the attributes of the entity defined by a previous DEFINE command. When used with WITH, the options listed in the WITH phrase override the attributes of the entity specified by the LIKE phrase. 
</td>
</tr>

<tr>
<th><var>SCOPE=SYSTEM</var></th>
<td> is required and indicates that the definition is available to all users for the entire run. </td>
</tr>

<tr>
<th>options</th>
<td> for the particular forms of the DEFINE command are described in sections that follow. Options must be separated by commas or by one or more blanks.</td>
</tr>

</table>
==Syntax notes==
Certain rules concerning options are checked at a point later than the time of definition. Refer to the following example:
DEFINE PRINTER P1 WITH -
SCOPE=SYSTEM
ROUTER=VM -
ID=PRIIINTER1

In the example, the correct ID specification PRINTER1 is misspelled. However, the DEFINE command executes. An error occurs if an attempt is made subsequently to execute a USE P1 command that accesses the incorrect DEFINE PRINTER definition. 
The example also shows the use of the hyphen (-) as a continuation character. A continuation character preceded by a space is required at the end of an input line, if the command parameters continue onto the next line.
==Usage notes==
You can create a template and assign it a name with the DEFINE command (except for DEFINE FIELD). The template can contain all the attributes needed to create a new template. You can refer to the template name in a DEFINE command or in an ALLOCATE command where a DEFINE DATASET command previously defined the template. The attributes of a template override those of the previously defined entity.
The definition of any entity can be replaced by entering a DEFINE command, the previously defined entity name, and any attributes to be altered. Issuing a DEFINE command with the same name as one presently in use overrides the current template definition. You, therefore, might unintentionally replace an existing entity definition, because <var class="product">Model 204</var> does not check if the entity name entered is unique. 
When it processes a DEFINE command, <var class="product">Model 204</var> ends any current User Language update unit and begins a non-backoutable update unit. If a <var class="product">Model 204</var> command non-back outable update unit is in progress, the DEFINE command is included in that update unit. For more information about <var class="product">Model 204</var> update units, see the <var>Model 204 File Manager's Guide.</var> 
DEFINE commands that contain invalid or mutually exclusive options are rejected by <var class="product">Model 204</var>. 
[[Category:Commands]]