The following qualifiers are maintained for compatibility reasons:
EXTENSION_LINE FT_FRACT_INCH FT_INCH_SIGN FT_INCH_TEXT LONG_BASE_LINE MM_OVER_INCH NO_EXTENSION_LINE NO_SIGN SHORT_BASE_LINE
--->(QUERY)--->{class selection}--->{attribute options}--->(CONFIRM)-+
|
+-----------------------+
|
+->{output options}--->
{class selection}
-->+----------+--+->|class name or pattern|---------------------------->+-----> | | | | +->(PART)->+ +->(CLASS)->+->|class name or pattern|->+->(CONFIRM)-->+ ^ v +<--------------------------+
{attribute options}
+--------------------------------------+
v ^
--+---+->{display format}----------->+---+--->
| |
+->{restrictions}------------->+
| |
+->{sort order}--------------->+
{display format}
+------------------------+
v ^
-->+-->+->|display attribute|-->+-->+->
| |
+-->(DETAIL_INFO)--------------->+
{restrictions}
--+-----------------------------+->
| |
+->(SELECT)->+->{expression}->+
^ v
+<---(AND)-------+
| |
+<---(OR)--------+
{expression}
-->|attribute name|->+-------->+--->+->|string value or pattern|-->+-----> | | | | +->(=)--->+ +->|numeric value|------------>+ | | | | +->(<>)-->+ +->(NULL)--------------------->+ | | +->(>)--->+ | | +->(<)--->+ | | +->(>=)-->+ | | +->(<=)-->+
{sort order}
+-----------------------------------------+ v ^ -->+---------------------------------------->+-> | | +->(SORT)--------->+-->|sort attribute|-->+ | | +->(REVERSE_SORT)->+
{output options}
+->+->(DEFAULT_TABLE)--------------------------------------------->+----->
| |
+->(SCREEN)---------------------------------------------------->+
| |
+->(PROMPT_LINE)----------------------------------------------->+
| |
+->{file specification}---------------------------------------->+
| |
+->(TABLE)------------------------+----+->|display table|------>+
| | | |
+->(USER_TABLE)->|logical table|->+ +->(DEFAULT_TABLE)------>+
| |
+->(END)---------------->+
{file specification}
--+----------------+---|filename|---> | | +-->(DEL_OLD)----+ | | +-->(APPEND)-----+
QUERY produces a listing of elements belonging to one or more classes.
Sample output:
NAME REVISION VERSION CLASS PLATING CREATE_DATE ------------------- --------- ------- ------- -------- ----------------- R07_JJ A.00 3 Rivet nickel 89/04/01 09:43:52 R19_JJ A.00 3 Rivet nickel 89/05/21 11:33:23 R19_K_3 A.00 3 Rivet copper 89/04/11 01:43:32 R99_KK A.00 1 Rivet copper 89/08/20 01:05:42 R99_KK B.00 1 Rivet copper 89/09/05 05:33:04
By default, the query function looks only for the element(s) with the newest revision and version. If you want to see other versions, you may select based on the attributes REVISION and VERSION.
SECURITY:
If you do not have read permission for an element, it is not displayed.
STRING PATTERNS AND SPECIAL (WILDCARD) CHARACTERS:
You may specify patterns for strings (for example, class names, element names and attribute names) with special (wildcard) characters, such as '*' and '?'. The '*' character matches any number of characters. The '?' matches exactly one arbitrary character. The following examples show various uses for patterns:
strings that BEGIN with 'box'
'box*'
strings that END with 'box'
'*box'
strings that CONTAIN 'box'
'*box*'
strings that are five letters long, STARTING with 'box'.
'box??'
strings that are five letters long, ENDING with 'box'.
'??box'
See the CATALOG command for additional patterns for matching strings.
CLASS SELECTION:
You may select one class name, a class name pattern, or a list of class names. You may choose the class names from the set of all classes or restrict the search to part classes only (using the PART option). You may enter a list of class names, or patterns with special (wildcard) characters.
DISPLAY FORMAT:
To choose the attributes to display, simply enter the atribute names in the desired order. Normally, each query item is diplayed on one row of the screen, or is stored in one record of the selected file or display table. Attributes are arranged in columns, with the attribute name as the column title string. You may display the same attribute in multiple output display columns.
If you specify the DETAIL_INFO option, the normal format is not used. Instead, all information is listed for each item, one attribute per line. If you use this option, the output of your query may only be directed to the screen or to a file.
RESTRICTIONS:
You may specify combinations of attribute values to limit the selection of items to be displayed. For example, you could select all items with a desired weight and diameter, or all items created on a certain date. You may use string patterns with either the '=' operator or the '<>' operator.
If you want to specify more than one search condition ( either for restricting or for extending the set of result records ) you may combine them by using the logical operators AND and OR. AND restricts the set of result records. OR extends the set of result records.
If you specify three or more search conditions combined by the operators AND and OR, the first two conditions are combined first, then the result of that combination is combined with the third, and so on. That means that if you typed search conditions and operators as follows:
Search1 Op1 Search2 Op2 Search3 Op3 Search4
they would be grouped as:
(((Search1 Op1 Search2) Op2 Search3) Op3 Search4)
For example, you are looking for all drawings, which are archived and which belong to "peter" or to "paul" then you must specify the following sequence of search conditions:
'OWNER' = 'peter' OR 'OWNER' = 'paul' AND 'ARCHIVE_DATE' <> NULL
If you would specify the same search conditions with the same logical operators but in the sequence
'ARCHIVE_DATE' <> NULL AND 'OWNER' = 'paul' OR 'OWNER' = 'peter'
you would get all drawings which belong to "paul" and which are archived plus all ( not only the archived ) drawings which belong to "peter". The reason therefore is that internally the first sequence is evaluated as
(( 'OWNER' = 'peter' OR 'OWNER' = 'paul' ) AND 'ARCHIVE_DATE' <> NULL )
whereby the second sequence is evaluated as
(( 'ARCHIVE_DATE' <> NULL AND 'OWNER' = 'paul' ) OR 'OWNER' = 'peter' )
The sequence of the specified search conditions is important for the set of result records.
Different classes may define the same attribute name to have different types and precisions. The system allows you to enter either a string or a number as the selection value for any attribute. There is no type checking as you are entering select values. However, the data type is checked for each class when the query command is sent to the database.
SORT ORDER:
To sort the output in ascending (increasing) order, you enter the SORT option, then the attribute name. To sort in descending order, you may use the REVERSE_SORT option. You can use either option more than once; the second sort option specifies the ordering of records that are alike under the first sort option, and so on. The sort attributes do not need to be displayed.
If you do not specify any sort conditions, the items are sorted in ascending order on the first displayed column.
When multiple classes are combined in one query command, the output is always grouped by class. The sort conditions that you specify are applied separately within each class. You may not specify sorting by class name within the query command. However, you may use the SORT_LTAB command to sort the results table by any combination of attributes (including class name) after the query has completed.
OUTPUT OPTIONS:
Query output may be sent to a table, the SCREEN, or to a file. To use an output file that already exists, you must use DEL_OLD, which deletes the old file, or APPEND, which causes the new output to be written at the end of the old file.
If the output is sent to SCREEN, to a file or to the DEFAULT_TABLE the format of the output ( the width of the columns and the column headers ) are specified automatically depending on the whole width of the screen, on the table width and on the width of the attributes that you selected for display.
The normal total display width for output to the screen or a file is 124 characters. The total width for the default table depends on the arrangement of the screen viewports (normally 80 characters).
To customize the table output format, you must first create a display table with the desired size, position and labels. Then when you use the query command, you select the TABLE option and enter the name of the table.
Normally, the data is stored in the 'query_results' logical table. You may instead choose the USER_TABLE option to specify a different data storage area. By default, user tables are not displayed on the screen. If you want to display the user table, you may also specify the DEFAULT_TABLE option or the name of a display table.
If you instead specify the END option, the output is stored in the user table without assigning a display table to it. If you have previously assigned a display table for this user table (with a previous query command or with the TABLE_LAYOUT or CONNECT_TABLE command), the output is displayed, but the column layout and titles are not modified. If no display table is assigned to the user table, the output is not displayed.
NUMBER OF RECORDS READ:
As records are retrieved from the database, you will see a running count of items read. The count may differ from the actual number of result lines, for the following reasons:
The query commands complete without any error message if no entries match the specification. The default display table lists the number of entries found.
--->(QUERY_ADD_CLASS)--->|query name|--->+--->|new class name|--->+--->(END)---> | | +<-----------------------+
Adds a list of classes to the specified query. Wildcards are allowed for the new class name. You may not enter classes for AREAS and CLASSES queries. The class list must be set for ELEMENTS, ATTRIBUTES, RELATED_CLASSES and STRUCTURES queries. To display elements related to files, simply add the desired classes to a FILES query.
--->(QUERY_ADD_COLUMN)-->|query name|-->+-->|attribute name|-->+-->(END)--> | | +<---------------------+
Adds a list of display columns to the specified query. You may enter any number of attribute names to display, then use END to terminate the command.
--->(QUERY_ADD_SELECT)--->|query name|--->+
|
+<----------------------------------------+
|
| +<---------------------------------------+
| | ^
| v |
+--->+------------>+--->|select condition|--->+--->(END)--->
| |
+--->(AND)--->+
| |
+--->(OR)---->+
|select condition|:
--->|attribute name|--->+------------->+--->+--->|string|--->+---> | | | | +--->( = )--->+ +--->|number|--->+ | | | | +--->( <> )--->+ +---->(NULL)---->+ | | +--->( > )--->+ | | +--->( < )--->+ | | +--->( >= )--->+ | | +--->( <= )--->+
Adds a list of select conditions to the specified query. Wildcards are allowed for string values. You first select an attribute name and a relational operator (=, <>, >, >=, <, <=). The default operator is '='. You should enter a number or string value appropriate to the type of attribute you selected. You may add any number of conditions, separated with AND and OR, then terminate the command with END.
For ELEMENTS and FILES queries, by default only the current revision and version of each element is displayed. To see old revisions and versions, you may enter a select condition on either revisions or versions, or both.
+<-------------------------+ | ^ v | -->(QUERY_ADD_SORT)-->|query name|-->+-->|sort specification|-->+-->(END)-->
|sort specification|:
--+---------------+--->|attribute name|---> | | +-->(REVERSE)-->+ | | +-->(NORMAL)--->+
Adds a list of sort conditions to the specified query. The REVERSE option causes sorting in descending order for the following attribute names. The NORMAL option restores sorting to ascending order. END terminates the command.
If you do not specify any sort conditions, by default the query results will generally be sorted in ascending order, based on the first display field that you specify. However, for ELEMENTS and FILES queries, the results are always grouped first by class name. Other sort conditions only apply within each class. That means that CLASS is ignored as a sort attribute for ELEMENTS and FILES queries.
You may not sort STRUCTURES queries by the STRUCTURE_DMS field. This field is ignored as a sort condition. You may not specify sort conditions for ATTRIBUTES or RELATED_CLASSES queries. The output order is specified by the system.
You may use the POST SORT operation to sort or re-sort the query results table after the query has completed.
--->(QUERY_AREAS)--->{attribute options}--->(CONFIRM)--->{output options}--->
QUERY_AREAS produces a listing of storage areas.
Sample output:
AREA_NAME PATH CURRENT -------------------- ------------------------------- ------- DMS_area /users/admin/me10/storage 1
See the QUERY function for more information about selection, attribute options and output.
The CoCreate/DMS query commands provide easy access to many types of data stored in a relational database.
CoCreate/DMS helps you manage design data and manufacturing documentation throughout the life of the product, which may include several revisions. The database maintains information needed to generate part lists for ME10 and ME30 designs.
You may store detailed part attributes, such as sizes, materials and cost. You may then create lists of items matching various selection criteria. You may display tables of information on the screen or output it to a file or the printer.
CoCreate/DMS helps you maintain a history of product changes. This information is useful for answering questions about current and past products: structure, designer, date of creation, released by, released when, archived where, revisions, versions, etc.
You can generate hierarchical descriptions of products and their subassemblies. You can cross reference subassemblies to find out where they are used.
You can keep your documentation consistent by maintaining lists of aspects (cuts) files that are affected if the model changes.
The query capabilities that CoCreate/DMS offers are similar to the CATALOG functions available within ME10/ME30. In particular, the query commands allow the same types of pattern matching as the CATALOG command for selecting groups of objects. This pattern matching uses special 'wildcard' characters.
The CoCreate/DMS commands provide easy access to the database for common operations. For certain difficult problems, you may bypass the common commands and access the data directly through the SQL query language.
->(QUERY_CLASSES)->+->(ATTRIBUTES)--+-->{class selection}--+->{output options}
| | |
| +--+ |
| | |
+->(RELATED_CLASS)->+ |
| |
+->{attribute options}-->(CONFIRM)----->+
QUERY_CLASSES performs several functions:
1) You can display class definitions, including system defined and user defined attributes. Each definition includes the attribute type (string, integer, decimal, or float). For string attributes, the maximum length is displayed. For decimal attributes, the scale and precision are displayed. To access this function, pick the ATTRIBUTES option and enter a set of classes.
Sample output:
Class Attribute Type Length Scale Precision
------------ ---------------- -------- -------- --------- ---------
drawings NAME String 255
drawings REVISION String 8
drawings VERSION Integer
.
.
drawings BACKEDUP_LAST String 18
2) You can display parent/child relationships between classes. To access this function, pick the RELATED_CLASS option and enter a set of classes.
Sample output:
Parent_Class Child_Class --------------------------------- ------------------------------- models drawings
3) You can produce a list of classes and their system defined attributes. With this command you can determine whether the elements of a given class are releasable, may have revisions and versions, and whether the class is a part class. You may initiate this function by picking the SELECT, SORT, or REVERSE_SORT attribute options or by entering the name of a class attribute to display.
Sample output:
CLASS_NAME PART REVISIONING VERSIONING RELEASABLE --------------------- ---- ----------- ----------- ----------- Rivets 1 1 1 1 drawings 0 1 1 1 models 0 1 1 1
See the QUERY function for more information about selection, attribute options and output.
--->(QUERY_COPY)--->|source query name|--->|destination query name|--->
Makes a copy of the specified query. You first enter the name of an existing query, then you enter a name for the copy. The copy name must not refer to an existing query. The new copy becomes the current query.
--->(QUERY_CREATE)-->|query name|--->
Creates a query with type ELEMENTS. If you want a different type of query, you should set the type before editing any other query attributes. To change the type, see the QUERY_TYPE command. If the named query already exists, it is re-initialized. The class, select, sort and display lists are cleared. The default display mode is selected.
--->(QUERY_CREATE_CLASSIFICATION)-+------------+---->|query name|---> | | +-(ELEMENTS)-+
Creates a named query for CLASSIFICATION module. If the named query already exists, it is re-initialized. With ELEMENTS option, the query can only be used for querying class elements otherwise, it is applicable only for querying nodes from CLASSIFICATION tree. Upon creation, the class, select, sort and display lists are cleared. The default display mode is selected.
--->(QUERY_DELETE)--->+--->|query name|--->+--->(CONFIRM)---> | | +------->(ALL)------>+
Deletes a single query or all defined queries. Enter the name of the query you wish to delete, or select the option ALL. Select CONFIRM. The query is cleared to default values.
--->(QUERY_DELETE_CLASS)--->|query name|--->+--->|previous class name|--->+---> | | +----------->(ALL)----------->+
Deletes one class or all classes from the specified query.
--->(QUERY_DELETE_COLUMN)-->|query name|-->+-->|previous attribute name|-->+--> | | +------------>(ALL)------------>+
Deletes one display column or all display columns from the specified query. To remove a single attribute, enter the previously entered display column name. The attribute name is removed from the list. The option ALL removes all display columns.
--->(QUERY_DELETE_SELECT)--->|query name|--->+
|
+<-------------------------------------------+
|
+--->+--->|previous select condition|--->+--->
| |
+-------------->(ALL)-------------->+
|select condition|: See QUERY_ADD_SELECT.
Deletes one select condition or all select conditions from the specified query. You specify the select condition the same as you did for QUERY_ADD_SELECT. The condition is removed from the list.
--->(QUERY_DELETE_SORT)--->|query name|-->+--->|sort attribute name|--->+---> | | +----------->(ALL)----------->+
Deletes one sort condition or all sort conditions from the specified query. The selected attributes are removed from the list.
--->(QUERY_DESTINATION)--->|query name|--->+-->(DEFAULT_TABLE)----->+---> | | +-->(TABLE)------------->+ | | +-->(USER_TABLE)-------->+ | | +-->(SCREEN)------------>+ | | +-->(FILE)-------------->+ | | +-->(DEL_OLD)----------->+ | | +-->(APPEND)------------>+ | | +-->(PROMPT_LINE)------->+
Selects the type of output destination for later query execution. Other named query commands specify the actual file names and table names.
To direct output to the full CoCreate/DMS screen, select SCREEN. The next time you query the database, the results are displayed in the system screen editor.
To direct output to a new file, first select FILE, then use the QUERY_FILE_NAME command to enter the name of a new file. The next time you query the database, the results are stored in the selected file.
To store output in a file that may already exist, first select DEL_OLD, then use the QUERY_FILE_NAME command to enter the name of a file. The next time you query the database, the old copy of the file is deleted if it already existed, and the results are stored in the selected file.
To add output to a file that may already exist, first select APPEND, then use the QUERY_FILE_NAME command to enter the name of a file. The next time you query the database, the results are added to the end of the selected file.
To output to a logical table, first select USER_TABLE, then use the QUERY_USER_TABLE_NAME command to enter the name of an existing logical table. The next time you query the database, the results are output to the selected tables. The Display Table name is ignored. The results are not displayed unless you explicitly connect a display table to the logical table.
To output to a pre-formatted display table, first select TABLE, then use the QUERY_TABLE_NAME command to enter the name of an existing display table. You should have previously specified the desired title strings, borders, colors, column widths, etc. You may optionally use the QUERY_USER_TABLE_NAME command to enter the name of an existing logical table. The next time you query the database, the results are displayed to the selected tables.
To restore the default output mode, select DEFAULT_TABLE. If you changed the display table name, you may use the QUERY_TABLE_NAME command to enter the name of the original display table. If you changed the logical table, you may use the QUERY_USER_TABLE_NAME command to enter the name of the original logical table. The next time you query the database, the results are displayed in the selected tables with default title strings, borders, colors and column widths.
To direct output to the CoCreate/DMS prompt line, select PROMPT_LINE. The next time you query the database, the results are displayed one line at a time on the prompt line. After each line of output is displayed, you must press any key to continue to the next line.
--->(QUERY_DIRECTION)--->|query name|--->+--->(DOWN)--->+---> | | +--->(UP)----->+
Sets the direction of search for a STRUCTURES query. If the direction is DOWN, the query shows subassemblies of the starting element (lower-level elements in the structure). If the direction is UP, the query shows major assemblies where the starting element is used (higher-level elements in the structure). The default search direction for new queries is DOWN.
--->(QUERY_EXECUTE)--->|query name|--->
Queries the database and displays the results. You will see a running count of records read. The data is output in the previously selected display mode. (See QUERY_DESTINATION for more information about display options.)
->(QUERY_FILES)->+--->{attribute options}--->(CONFIRM)--->{output options}-->
|
+->(ELEMENTS_TO_FILES)->{elements_to_files}->+
| |
+->(FILES_TO_ELEMENTS)->{files_to_elements}->+
|
+<-------------------------------------------+
|
| +-----------------------+
| v ^
+->+->|display attribute|->+->(CONFIRM)-->{output options}-->
{elements_to_files}
-->{file restrictions}--+
|
+-----------+
|
+-->+->{class selection}-->{element restrictions}-+->(CONFIRM)-->
| |
^ v
+---------------------------------------------+
{files_to_elements}
-->-+->{element id}--------------------------------------------------->+
| |
+->(CLASS)->|class name|->{element restrictions}------------------>+
|
+------------------------------------------------------------------+
|
+->(FILE)->{file restrictions}---->
{element id}
-->|element name|--+-------------------------------------------------------+-> v | +->(SEL_OLD)--+->|revision string|->|version number|-+->+ | | +->|revision string|------------------>+ | | +->|version number|------------------->+
QUERY_FILES produces a listing of files, a listing of files belonging to some specified elements or a listing of elements to which some specified files belong.
The QUERY_FILES command include three file query modes:
1) The simple mode outputs all selected files, regardless of any related elements.
2) The ELEMENTS_TO_FILES mode outputs all selected files for a given element. Following each file record, a record is output for each related element (if any) that matches the element select conditions. The ELEMENTS_TO_FILES mode allows you to specify a separate select condition for the starting files and for each destination class (or group of classes). By default, the function displays all revisions and version of the elements.
3) The FILES_TO_ELEMENTS mode outputs all selected elements related to a given file. Following each element record, a record is output for each related file (if any) that matches the file select conditions. You may specify a separate select condition for the starting class (or group of classes) and for the destination files. By default, the function looks only for the source elements with the newest revision and version. If you want to see other versions, you may select based on the attributes REVISION and VERSION.
See the QUERY function for more information about selection, attribute options restictions and output.
Security: Your permissions are only checked if you are using one of the options FILES_TO_ELEMENTS or ELEMENTS_TO_FILES. You must have read permissions for the elements to which the files are related. Using FILES_TO_ELEMENTS, you only see the files related to elements for which you have read permissions. Using ELEMENTS_TO_FILES, you only see the elements which have relations to your specified files and for which you have read permissions.
--->(QUERY_FILE_NAME)--->|query name|--->|output file name|--->
Selects the name of the file to use for later query execution. The file name is used in connection with the FILE, DEL_OLD and APPEND query destinations. See QUERY_DESTINATION for more information.
--->(QUERY_LEVELS)--->|query name|--->+--->|max. level|--->+---> | | +------>(ALL)------->+
Sets the maximum number of levels to display for a STRUCTURES query.
--->(QUERY_LIMIT)--->|number|--->
QUERY_LIMIT is a CoCreate/DMS command which sets the maximum number of records returned by a query. This helps prevent 'Out of memory' conditions. This command applies to all types of standard queries (QUERY, QUERY_CLASSES, QUERY_FILES, etc.) as well as to named queries, such as those used for Classification.
By default, the startup macros set the query limit to 1000 records. You may permanently change the initial limit by editing the following line in the db_defaults file:
LET Query_max_records 1000
If any query exceeds the limit, the following error message is reported:
*** The query limit of 1000 result records has been exceeded
Press tablet stylus or any key to continue
After you respond to the message, the query will terminate and display the records already found. If the query was issued from a macro, the macro is aborted.
Some queries display a nested or hierarchical structure (for example, STRUCTURE, WHERE_USED, FILES_TO_ELEMENTS, ELEMENTS_TO_FILES, and Classification queries). In these cases, the query generally reads the higher levels elements of the structure before reading the lower levels. After the query limit is reached, the displayed results may have "missing lines" in the middle, not just at the end. So, if you exceed the limit for these types of queries, you should not depend on the partial results. Instead you should either restrict the query by adding select conditions, or increase the query limit.
--->(QUERY_LIST)--->|output spec|--->
Lists all defined queries to a file or displays the list on the screen. Only the query names are displayed. The 'output spec' may be SCREEN, PROMPT_LINE, DEL_OLD, APPEND, or a file name. The list of defined queries is output to the specified destination.
--->(QUERY_MODIFY_CLASS)--->|query name|--->+ | +<------------------------------------------+ | +--->|previous class name|--->|new class name|--->
Substitutes one class for another in the class list for the specified query.
--->(QUERY_MODIFY_COLUMN)--->|query name|--->+ | +<-------------------------------------------+ | +--->|previous attribute name|--->|new attribute name|--->
Substitutes one display column for another in the display column list for the specified query. You first enter the display column that you want to change, then you enter a new attribute name. The new attribute name replaces the old attribute name in the list.
--->(QUERY_MODIFY_SELECT)--->|query name|--->+ | +<-------------------------------------------+ | +--->|previous select condition|--->|new select condition|--->
|select condition|: See QUERY_ADD_SELECT.
Substitutes one select condition for another in the select condition list for the specified query. Enter the select condition that you want to change just as for QUERY_ADD_SELECT. Then enter a new select condition. The new condition replaces the old condition in the list.
--->(QUERY_MODIFY_SORT)--->|query name|--->+ | +<-----------------------------------------+ | +--->|previous sort attribute name|--->|new sort value|--->
|sort value|:
--->+---------------->+--->|sort attribute name|--->
| |
+--->(REVERSE)--->+
Substitutes one sort condition for another in the sort condition list for the specified query. You do not need to specify the sort direction (NORMAL/REVERSE) for the previous sort condition. For the new sort condition, you should specify no direction to select NORMAL, ascending sort, or REVERSE to select descending sort.
--->(QUERY_REFRESH)--->|query name|--->
Selects the specified query as the current query and updates a logical table with the complete specification for this query. The other named query commands automatically update portions of the logical table data with values that they modify.
--->(QUERY_RENAME)--->|old query name|--->|new query name|--->
Renames the specified query. You first enter the name of an existing query, then you enter a new name for that query. The new name must not refer to another existing query. The name of the query is updated.
--->(QUERY_SAVE)--->+--->|query name|--->+--->|output spec|---> | | +------->(ALL)------>+
Stores the specification of the query to a file or displays it on the screen. The format is compatible with the INPUT command. The 'output spec' may be SCREEN, PROMPT_LINE, DEL_OLD, APPEND, or a file name. The query specifications, including output options, selected classes, select conditions, sort conditions and display columns, are stored. The query results are not stored.
--->(QUERY_SELECT_TABLE_NAME)--->|query name|--->|select logical table name|--->
This table is used by Classification queries to display select conditions.
--->(QUERY_SET_SELECT)--->|query name|--->|select factor|--->
|select factor|:
+----->(NOT)----->|select factor|------>+
| |
--->+--------->|select condition|---------->+--->
| |
+--->( [ )--->|select expr|--->( ] )--->+
|select expr|:
+<---+<---(AND)<---+<---+
| | | |
| +<---(OR)<----+ |
| |
--->+--->|select factor|--->+--->
|select condition|: See QUERY_ADD_SELECT.
The QUERY_SET_SELECT command allows more complex select conditions than those that you can create with QUERY_ADD_SELECT, including NOT and grouping. You may group select conditions by entering square brackets as you would use parentheses in a mathematical expression.
The QUERY_SET_SELECT command places the current select expression in the input line. You may edit the expression with the editing keys (such as Insert char, Delete char and the arrow keys).
--->(QUERY_SORT_TABLE_NAME)--->|query name|--->|sort logical table name|--->
This table is used by Classification queries to display sort conditions.
--->(QUERY_START_ELEMENT)--->|query name|-->|element name|-->
Sets the starting element for a STRUCTURES query. Also selects the current revision and version of that element.
--->(QUERY_START_REVISION)--->|query name|-->|revision string|-->
Sets the starting revision string for a STRUCTURES query. If the element class does not allow revisioning, the new value is ignored.
--->(QUERY_START_VERSION)--->|query name|-->|version number|-->
Sets the starting version number for a STRUCTURES query. If the element class does not allow versioning, the new value is ignored.
--->(QUERY_TABLE_NAME)--->|query name|--->|output display table name|--->
Selects the name of the display table to use for later query execution. The file name is used in connection with the DEFAULT_TABLE and TABLE query destinations. The default display table name for new queries is 'dms_qry_results_disp'. See QUERY_DESTINATION for more information.
--->(QUERY_TREE_CHILD_NODE)-->|node query name|-->|elem query name|--+
v
+<--------------------------------------------------------------+
|
| +<--------+
| | |
+--+->{node}-+-->(END)--->
{node}
---+->|name|-------------+---> | | +->(TOP)--------------+ | | +->(LAST)-------------+ | | +->(CURRENT)----------+ | | +->(BACK)-->|steps|---+
Query child nodes of a given node in the current classification tree. When the node being queried is an CoCreate/DMS class, elem query conditions are used, otherwise node query conditions are used. Querying a node makes the next current node.
An existing node can be specified by typing its name or picking it from a table. Option TOP specifies the top node of the current tree, which also is the name of the current tree. Option CURRENT specifies the current node in the history of the node queries. Option LAST gives the last current node, BACK identifies a node queried earlier by given steps in the history.
For default queries, logical tables 'cnc_query_sort', 'cnc_query_select' and 'cnc_query_results' are used for query editing and results output respectively. In this case, the display table names are same as the logical table names. Attributes for the default query are taken from the query pages associated with the node being queried. For the results, the title strings of the results logical table are generated using the attribute values of the history nodes, starting at the current node and going back to the top node.
A classification privilege of 4 is required to use this command.
--->(QUERY_TREE_ELEMENTS)-->|node query name|-->|elem query name|-->{node}-->
{node}
---+->|name|-------------+---> | | +->(TOP)--------------+ | | +->(LAST)-------------+ | | +->(CURRENT)----------+ | | +->(BACK)-->|steps|---+
Query elements of the child classes of a node in the current classification tree. For the class selection, a named node query is used after which, element selection is performed on these classes using named element query. Classes selected can be direct or indirect children of the given node.
An existing node can be specified by typing its name or picking it from a table. Option TOP specifies the top node of the current tree, which also is the name of the current tree. Option CURRENT specifies the current node in the history of the node queries. Option LAST gives the last current node, BACK identifies a node queried earlier by given steps in the history.
For default queries, logical tables 'cnc_query_sort', 'cnc_query_select' and 'cnc_query_results' are used for query editing and results output respectively. In this case, the display table names are same as the logical table names. Attributes for the default query are taken from the query pages associated with the node being queried. For the results, the title strings of the results logical table are generated using the attribute values of the history nodes, starting at the current node and going back to the top node.
A classification privilege of 4 is required to use this command.
+<---------+
| |
--->(QUERY_TREE_PARENT_NODE)-->|node query name|--+->{node}--+->(END)--->
{node}
---+->|name|-------------+---> | | +->(TOP)--------------+ | | +->(LAST)-------------+ | | +->(CURRENT)----------+ | | +->(BACK)-->|steps|---+
Query parents of a node in the current classification tree using a named node query.
An existing node can be specified by typing its name or picking it from a table. Option TOP specifies the top node of the current tree, which also is the name of the current tree. Option CURRENT specifies the current node in the history of the node queries. Option LAST gives the last current node, BACK identifies a node queried earlier by given steps in the history.
For default queries, logical tables 'cnc_query_sort', 'cnc_query_select' and 'cnc_query_results' are used for query editing and results output respectively. In this case, the display table names are same as the logical table names. Attributes for the default query are taken from the query pages associated with the node being queried. For the results, the title strings of the results logical table are generated using the attribute values of the history nodes, starting at the current node and going back to the top node.
A classification privilege of 4 is required to use this command.
--->(QUERY_TYPE)-->|query name|--+-->(ELEMENTS)------->+--> | | +-->(FILES)---------->+ | | +-->(STRUCTURES)----->+ | | +-->(CLASSES)-------->+ | | +-->(ATTRIBUTES)----->+ | | +-->(AREAS)---------->+
Sets the type of a query. Re-initializes all fields and attributes. Any previously entered query attributes are reset to their default values. This command should immediately follow the QUERY_CREATE command.
To generate a top-down STRUCTURE query, you use the STRUCTURES query type with direction set to DOWN (the default). To generate a bottom-up WHERE_USED query, you use the STRUCTURES query type and set the direction to UP.
For queries similar to the ELEMENTS_TO_FILES and FILES_TO_ELEMENTS options of the QUERY_FILES command, you use the FILES query type and add the classes for the related elements.
--->(QUERY_USER_TABLE_NAME)--->|query name|--->|output logical table name|--->
Selects the name of the logical table to use for later query execution. The file name is used in connection with the DEFAULT_TABLE, TABLE and USER_TABLE query destinations. The default logical table name for new queries is 'dms_qry_results_tab'. See QUERY_DESTINATION for more information.