CREATE PERM GROUP command: Difference between revisions
m (Automatically generated page update) |
(→Syntax) |
||
Line 7: | Line 7: | ||
</dl> | </dl> | ||
==Syntax== | ==Syntax== | ||
<p class="syntax">CREATE PERM GROUP groupname | <p class="syntax">CREATE PERM GROUP <var class="term">groupname</var> | ||
FROM {< | FROM {<var class="term">filename</var> [AT <var class="term">location</var>] | ||
[(<b>OPT</b>IONAL) | (<b>MAND</b>ATORY)]} ,... | [(<b>OPT</b>IONAL) | (<b>MAND</b>ATORY)]} ,... | ||
[PARAMETER < | [PARAMETER <var class="term">parameter</var>[=<var class="term">value</var>] | ||
[PARAMETER < | [PARAMETER <var class="term">parameter</var>[=<var class="term">value</var>]]... | ||
. | . | ||
. | . | ||
Line 22: | Line 22: | ||
<tr> | <tr> | ||
<th>groupname</th> | <th>groupname</th> | ||
<td> is the name of the permanent file group that is being created (1 to 8 characters). The group name cannot be FILE or GROUP and cannot start with CCA, SYS, OUT, TAPE, dollar sign ($), or percent sign (%). It can contain any alphanumeric characters except: | <td> is the name of the permanent file group that is being created (1 to 8 characters). The group name cannot be FILE or GROUP and cannot start with CCA, SYS, OUT, TAPE, dollar sign ($), or percent sign (%). It can contain any alphanumeric characters except those shown in the following table: | ||
<table> | <table> | ||
Line 54: | Line 54: | ||
<th>filename</th> | <th>filename</th> | ||
<td> is the name of a <var class="product">Model 204</var> file. | <td> is the name of a <var class="product">Model 204</var> file. | ||
<p> If you are specifying Parallel Query Option/204 remote files, filename must include a remote location (AT location) or be a defined file synonym. Also, do not specify multiple identifiers for the same file; that is, you cannot include two synonyms for the same file, and you cannot include a synonym and a remote file specification for the same file. </p> | <p>If you are specifying Parallel Query Option/204 remote files, <var class="term">filename</var> must include a remote location (AT <var class="term">location</var>) or be a defined file synonym. Also, do not specify multiple identifiers for the same file; that is, you cannot include two synonyms for the same file, and you cannot include a synonym and a remote file specification for the same file. </p> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 60: | Line 60: | ||
<tr> | <tr> | ||
<th>location</th> | <th>location</th> | ||
<td> | <td>for PQO files, <var class="term">location</var> is the symbolic name (as many as eight characters) that refers to the location of the node on which the remote file resides. An unquoted equal sign (=) specifies that the file is local.</td> | ||
</tr> | </tr> | ||
Line 72: | Line 72: | ||
<tr> | <tr> | ||
<th>parameter</th> | <th>parameter</th> | ||
<td> specifies <var class="product">Model 204</var> group parameters. Any number of PARAMETER statements can follow, and each can contain as many parameters in any order as fit on one input line. Valid permanent group parameters are described in the table below. All but PRIVATE, PUBLIC, and SEMIPUB must be followed by a value. | <td>specifies <var class="product">Model 204</var> group parameters. Any number of PARAMETER statements can follow, and each can contain as many parameters in any order as fit on one input line. Valid permanent group parameters are described in the table below. All but PRIVATE, PUBLIC, and SEMIPUB must be followed by a value. | ||
<table> | <table> | ||
<caption>Parameters for CREATE PERMANENT GROUP</caption> | <caption>Parameters for CREATE PERMANENT GROUP</caption> | ||
Line 80: | Line 80: | ||
<tr> <th><var>ADDLVL</var></th> <td>Identifies the ADD field level security access level for the files making up the group. The default is 0. </td> </tr> | <tr> <th><var>ADDLVL</var></th> <td>Identifies the ADD field level security access level for the files making up the group. The default is 0. </td> </tr> | ||
<tr> <th><var>BLDGFT </var></th> <td>Indicates whether to build an internal field table for this group. Can be YES (default) or NO. | <tr> <th><var>BLDGFT </var></th> <td>Indicates whether to build an internal field table for this group. Can be YES (default) or NO. BLDGFT is ignored for groups that include remote members.</td> </tr> | ||
<tr> <th><var>MAXFAIL</var></th> <td> | <tr> <th><var>MAXFAIL</var></th> <td> | ||
<p>For scattered groups (PQO), the maximum number of optional members that can be unavailable. If more than MAXFAIL files are unavailable, the group fails to open or operations on the group are aborted.</p> | <p>For scattered groups (PQO), the maximum number of optional members that can be unavailable. If more than MAXFAIL files are unavailable, the group fails to open or operations on the group are aborted.</p> | ||
<p>The value of | <p>The value of MAXFAIL must be one of the following: </p> | ||
< | <ul> | ||
< | <li>An integer between one and the number of optional group members. </li> | ||
<li>An asterisk (*), which is equivalent to the number of optional members in the group. This setting means that the group can function without any of its optional members. This is the default. </li> | |||
</ul> | |||
<p>For ad hoc scattered groups, MAXFAIL is always set to the default.</p> | <p>For ad hoc scattered groups, MAXFAIL is always set to the default.</p> | ||
</td> </tr> | </td> </tr> | ||
Line 109: | Line 111: | ||
<tr> <th><var>UPDTFILE</var></th> <td>Defines the group's update file. | <tr> <th><var>UPDTFILE</var></th> <td>Defines the group's update file. | ||
<p>If used in PQO, UPDTFILE can refer to either local or remote files. If the update file you are naming is a remote file, you can include its remote file specification (AT location). </p> | <p>If used in PQO, UPDTFILE can refer to either local or remote files. If the update file you are naming is a remote file, you can include its remote file specification (AT <var class="term">location</var>). </p> | ||
</td> </tr> | </td> </tr> | ||
Line 123: | Line 125: | ||
===Syntax notes=== | ===Syntax notes=== | ||
Commas and equal signs are optional. | Commas and equal signs are optional. | ||
==Example== | ==Example== | ||
<p class="code"><b>CREATE PERM GROUP ACCOUNT FROM ACC1,</b> - | <p class="code"><b>CREATE PERM GROUP ACCOUNT FROM ACC1,</b> - |
Revision as of 22:22, 18 July 2013
Summary
- Privileges
- System manager
- Function
- Creates a Model 204 permanent file group
Syntax
CREATE PERM GROUP groupname FROM {filename [AT location] [(OPTIONAL) | (MANDATORY)]} ,... [PARAMETER parameter[=value] [PARAMETER parameter[=value]]... . . . END
Where:
groupname | is the name of the permanent file group that is being created (1 to 8 characters). The group name cannot be FILE or GROUP and cannot start with CCA, SYS, OUT, TAPE, dollar sign ($), or percent sign (%). It can contain any alphanumeric characters except those shown in the following table:
|
||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
filename | is the name of a Model 204 file.
If you are specifying Parallel Query Option/204 remote files, filename must include a remote location (AT location) or be a defined file synonym. Also, do not specify multiple identifiers for the same file; that is, you cannot include two synonyms for the same file, and you cannot include a synonym and a remote file specification for the same file. |
||||||||||||||||||||||||||||
location | for PQO files, location is the symbolic name (as many as eight characters) that refers to the location of the node on which the remote file resides. An unquoted equal sign (=) specifies that the file is local. | ||||||||||||||||||||||||||||
OPTIONAL | or MANDATORY indicates whether PQO scattered group operations can proceed in the absence of this group member. The default is MANDATORY. Valid abbreviations are OPT and MAND.
You cannot open a group if a mandatory member is unavailable. Also, you cannot specify OPTIONAL for local files. |
||||||||||||||||||||||||||||
parameter | specifies Model 204 group parameters. Any number of PARAMETER statements can follow, and each can contain as many parameters in any order as fit on one input line. Valid permanent group parameters are described in the table below. All but PRIVATE, PUBLIC, and SEMIPUB must be followed by a value.
|
Syntax notes
Commas and equal signs are optional.
Example
CREATE PERM GROUP ACCOUNT FROM ACC1, - ACC2, ACC3, ACC4 *** M204.0825: READING GROUP PARAMETERS PARAMETER PROCFILE = ACC1, PRIVDEF = X'3FFF' END *** M204.0830: PERM GROUP CREATED
Usage notes
The CREATE PERM GROUP command creates a permanent file group from the files specified in the command. A permanent group is a group established by the system manager and maintained permanently in an external file (the CCAGRP file) until it is explicitly deleted. Before a permanent group can be created, the system manager must create the CCAGRP file in which the group definitions are stored. This is accomplished with the CREATEG command.
When it processes CREATE PERM GROUP, Model 204 ends any update unit in progress and begins a non-backoutable update unit. For more information about Model 204 update units, see the Model 204 File Manager's Guide.
Duplicate identifiers for a local file are detected when Model 204 tries to open the group. A Model 204 messages tells you the name of the file duplicates that result from using file synonyms. You cannot:
-
Specify multiple identifiers for the same file in a CREATE GROUP command: that is, you cannot include two synonyms for the same file.
-
Include a synonym and a remote file specification for the same file.