$SDCAC

Configuration <cnf> to be considered (if entered as the first parameter).

Configuration path to be considered (if entered as the first parameter).

Specification that all items of the configuration <cnf> or the configuration path are to be considered.

In connection with $QRY, this is the only parameter possible. The specification <ctrlf> <wa> causes an error.

Work area with item list to be considered.

Work area with conditions for selection criteria. For more information, see Syntax of Work Area <wa2>.

Character string that defines the information that is passed in the work area <wa1>; the order in which the characters appear in the string defines the order in which the information is listed in the work area <wa1>.

Padding characters that are ignored by the command.

Item name in <i_nm> format as described in Accessing Items.

Item identification.

Item type.

Specification that instructions are given in Rochade words.

Specification that namespace ID <ns_id> and item name <i_xnm> are listed in the work area for the naming group <n_gr> in this format: <ns_id> <i_xnm>

The item specified by <ns_id> must exist. If X=<n_gr> is specified, W must also be specified.

Character string that defines the information that is to appear in the result work area (current work area); the order in which the characters appear in the string defines the order in which the information is to be listed in the result work area.

Attribute contents.

Configuration in which the item was found.

Item name in <i_nm> format as described in Accessing Items.

Item identification.

Status information for the items found in the current work area; A denotes active and I inactive items

Item type

Specification that the result is to be arranged in Rochade words.

Specification that namespace ID <ns_id> and item name <i_xnm> are to be listed in the work area for the naming group <n_gr> in this format: <ns_id> <i_xnm>

If an item does not have a name in the specified naming group, NIL NIL is displayed in place of <ns_id> <i_xnm>. If X=<n_gr> is specified, W must also be specified.

Work area containing a list of attributes whose contents are to be listed in <wa4> for each item. In addition, this work area contains instructions as to how those contents are to be presented in <wa4>. For more information, see also Syntax and Semantics of Work Area <wa3>.

<bool_expr_1>

| <bool_expr_1> <OR_op> <bool_expr>

| <bool_expr_1> <XOR_op> <bool_expr>

<bool_expr_2>

| <bool_expr_2> <AND_op> <bool_expr_1>

'(' <bool_expr> ')'

| <NOT_op> <bool_expr_2>

| <i_cond>

| <att_cond>

<i_tp_cond>

| <i_nm_cond>

| <ai_nm_cond>

| <i_x_cond>

| <i_ax_cond>

| <i_st_cond>

| <i_ns_state_cond>

| <i_ref_state_cond>

| <i_cre_time_cond>

| <i_upd_time_cond>

| <i_instcnt_cond>

'TYPE' <op_1> <string_val>

| 'TYPE' <op_5> <wildcard_expr>

'NAME' <op_1> <string_val>

| 'NAME' <op_5> <wildcard_expr>

'A_NAME' <op_1> <string_val>

| 'A_NAME' <op_5> <wildcard_expr>

'XNAME' <n_gr> <ns_id> <op_1> <string_val>

| 'XNAME' <n_gr> <ns_id> <op_5> <wildcard_expr>

'A_XNAME' <n_gr> <ns_id> <op_1> <string_val>

| 'A_XNAME' <n_gr> <ns_id> <op_5> <wildcard_expr>

'CRE_TIME' <op_4> <date_expr>

'UPD_TIME' <op_4> <date_expr>

'INSTCFGCNT' <op_4> <integer>

<l_att_cond>

| <n_att_cond>

| <s_att_cond>

| <t_att_cond>

| <v_att_cond>

| <b_att_size_cond>

| <l_att_size_cond>

| <n_att_size_cond>

| <s_att_size_cond>

| <t_att_size_cond>

| <v_att_size_cond>

'LA' <la_att_sel> <l_dir> [<l_itsel_cond>] [<l_seq_cond>] [<l_info_cond>]

'NA' <na_att_sel> <n_dir> [<l_itsel_cond>] [<l_seq_cond>] [<l_info_cond>]

'SA' <att_name> <op_3> <att_val>

| 'SA' <att_name> <op_5> <wildcard_expr>

'TA' <att_name> <op_3> <att_val>

| 'TA' <att_name> <op_5> <wildcard_expr>

'VA' <att_name> <op_3> <att_val>

| 'VA' <att_name> <op_5> <wildcard_expr>

'BA_SIZE' <att_name> <op_4> <integer>

'LA_SIZE' <la_att_sel> <l_dir> [<l_itsel_cond>][<l_seq_cond>] [<l_info_cond>] <op_4> <integer>

'NA_SIZE' <na_att_sel> <n_dir> [<l_itsel_cond>][<l_seq_cond>] [<l_info_cond>] <op_4> <integer>

'SA_SIZE' <att_name> <op_4> <integer>

'TA_SIZE' <att_name> <op_4> <integer>

'VA_SIZE' <att_name> <op_4> <integer>

'SEQN' <op_4> <integer>

'INFO' <op_3> <string_val>

| 'INFO' <op_5> <wildcard_expr>

<l_it_cond> | <l_itid_cond> | <l_sel_cond>

'ITEM' <ns_id> <i_tp> <n_gr> <i_nm>

'ITEMID' <i_id>

[<l_tp_cond>] [<i_lnm_cond>] [<l_ns_cond>] [<l_ngr_cond>]

'TYPE' <i_tp>

'NAME' <op_3> <string_val>

| 'NAME' <op_5> <wildcard_expr>

'NS' <ns_id>

'GROUP' <n_gr>

<op_2> | '~'<op_2>

<op_4> | '~'<op_4>

<op_6> | '~'<op_6>

<att_name> | '*'

<att_name> | '*' | 'NIL'

<string_val>

'ANY' <string_val>

| 'STR' <string_val>

| 'INT' <integer>

| 'REAL' <real>

| 'DATE' <date_expr>

<string_val>

<string_val>

<string_val>

<string_val>

<string_val>

'->' | '<-'

'HAS' | 'BELONGS_TO'

'*' | <string_val>

'*' | <string_val>

<string_val>

<rochade_word> | ':' <var>

Operator for comparisons with wildcard expressions. The result is true if the wildcard expression matches the comparison string.

Specifies that the search is case-insensitive for the letters A to Z. Exceptions are letters in the extended character set (for example, é, ø, and ü) for which case is significant.

Comparison operators for formulating conditions within expressions.

With text attributes, comparison operators work in this manner:

• They apply to the first line of the text attribute if you specify a concrete comparison value in the form <op_3> <att_val>. $SDCAC compares the complete content of the first line with the specified expression.
• They apply to all lines of the text attribute if you specify a wildcard expression in the form <op_5> <wildcard_expr>. $SDCAC compares each line with the specified expression.

Condition for binary attribute size in bytes.

Date expression, where these are valid expressions:

YYYYMMDDhhmmssYYYYMMDD.hhmmssYYYYMMDDhhmmssmmmYYYYMMDD.hhmmss.mmmYYYYMMDDYYMMDDhhmmssYYMMDDDD.MM.YYYY@ hh:mm:ssDD.MM.YY@ hh:mm:ssDD.MM.YYYYDD.MM.YYMM/DD/YYYY@ hh:mm:ssMM/DD/YY@ hh:mm:ssMM/DD/YYYYMM/DD/YY

Where: YYYY stands for year, MM for month, and DD for day. If the date includes a time expression, hh stands for hours, mm for minutes, and ss for seconds.

If the year is specified as a two-digit number, all dates with YY < 51 are interpreted as 20YY, while all dates with YY >= 51 are interpreted as 19YY. For instance, the date 02/22/02 is interpreted as 02.22.2002, and the date 02/22/99 as 02.22.1999.

A whole number in the range from -2147483647 to 2147483647.

Examples for valid expressions:

+0012345; 12345; -012345; 12345

When comparing integer values, 002 is greater than 1. This is in contrast to character comparison, where 002 is less than 1.

Selection conditions for links and namespace relationships for a particular item.

Further restricts the selection condition for links and namespace relationships.

• Forward links (->): The selection conditions apply to the target item.
• Backward links (<-): The selection conditions apply to the source item.
• Namespace relationship HAS: The selection conditions apply to the items that span a namespace for other items.
• Namespace relationship BELONGS_TO: The selection conditions apply to the items that are in the namespace of other items.

Selection condition for a set of items. Any combinations of <l_tp_cond>, <i_lnm_cond>, <l_ns_cond>, and <l_ngr_cond> are permitted.

The conditions can be stated in any order, and particular conditions may be omitted, but each condition may occur only once at most.

Selection conditions concerning the properties of the link or namespace relationship itself:

• INFO - Links or namespace relationships with a particular qualifier.
• SEQN - Links or namespace relationships with a particular sequence number.

Reports concerning link and namespace relationships can be grouped into efficiency categories 1 through 3, where 1 is highest and 3 is lowest:

• Category 1: Forward direction (->/HAS) without specification of name conditions or with a name condition for a particular item.
• Category 2: Forward link direction (->/HAS) with specification of name conditions for a group of items.
• Category 3: Backward link direction (<-/BELONGS_TO).

For categories 2 and 3, it can be more efficient in certain situations to determine an item set by means of $SLI and then apply further restrictions by means of $SDCAC and forward link conditions.

Conditions with forward link direction (->) can be applied more efficiently since all the required information is located in the item currently under consideration. In the case of backward link direction (<-) or in the case of name conditions for a group of items, additional items must be analyzed. In certain situations, it can be more efficient to determine an item set by means of $SLI and then apply further restrictions by means of $SDCAC and forward link conditions.

Condition to restrict the selection on the basis of these criteria:

• GROUP - Links to items belonging to a particular naming group.
• ITEM - Links to an item in a particular namespace and naming group.
• ITEMID - Links to an item with a particular item identification.
• NAME - Links to items with a particular item name.
• NS - Links to items belonging to a particular namespace.
• TYPE - Links to items of a particular item type.

A floating-point number with up to 12 places on either side of the decimal point; plus and minus signs are allowed.

If more than 12 digits to the left of the decimal point—not including leading zeros—are specified, an error message is returned.

If more than 12 decimal places are specified, the value is truncated.

These values are examples of valid floating-point expressions:

+00.1234; +.1234; .1234; +1234.00; +1234.; 1234

-00.1234; -.1234; -1234.00; -1234.

Both entries represent Rochade words, which are limited only by the length of the work area line. Rochade words can be passed in Rochade variables. In this case, you must specify the evaluation character, colon (:), before the variable name. Multiple evaluations are possible.

When using Rochade separators or special characters within a Rochade word, you must mask them with the Rochade escape character.

For more information on Rochade words and separators, see Using Rochade Words, the Escape Symbol, and Separators.

The units for the specification of text and value attribute size are characters. This guarantees a uniform interpretation of attribute size by double-byte and single-byte clients.

A wildcard expression is a Rochade word that contains a search pattern for the comparison of character strings. Asterisk (*) and question mark (?) are permitted as wildcard characters. Wildcard characters can appear in any position in a Rochade word. The wildcard character asterisk (*) must be masked with the Rochade escape character.

The asterisk (*) character represents zero to any number of characters, the question mark (?) represents exactly one character.

To use the characters *, \, and ? as regular characters within a wildcard expression, they must be masked with a backslash (\).

If a wildcard expression contains a character string without a wildcard character, $SDCAC will search exactly for that string.

Specifies conditions for the alias names of an item that was created under the classic naming concept with a maximum length of 32 characters. See also Rochade Naming Concept.

If the work area contains an A_NAME condition, $SDCAC reads every item in the database and checks if it has an alias name that meets the conditions specified in A_NAME.

The values of the $NMGRP and $NMSPC system variables are used as the naming group and namespace in such a condition.

For example, to find an item that has both the name B and the alias name B1 in the database, you should formulate such a condition:

NAME = B & A_NAME = B1

This expression returns the value TRUE if an item has both the name B and the name B1. Whether B or B1 is the actual alias name of the item does not matter.

The search for items that have either the name B or the name B1 is best formulated with this expression:

NAME = B | NAME = B1

Specifies conditions for multiple names of an item in different naming groups.

If the work area contains an A_XNAME condition, $SDCAC reads each item in the database and checks if it meets the condition.

For example, a search for an item that has the name B in naming group 1 and the name B1 in naming group 2 should be formulated with this expression:

XNAME 1 * = B & A_XNAME 2 * = B1

This expression returns the value TRUE if an item has the name B in naming group 1 and the name B1 in naming group 2.

A search for items having either the name B in naming group 1 or the name B1 in naming group 2 is best formulated with this expression:

XNAME 1 * = B | XNAME 2 * = B1

Since the evaluation of A_NAME or A_XNAME conditions is very time-consuming, you should use them only in connection with searches for alias names or multiple names in different naming groups, preferably specified with additional restrictions via NAME, XNAME, and TYPE conditions.

Returns the value TRUE if the item is active. Use NOT ACTIVE if you want to search for inactive items.

Logical functions for formulating logical expressions subject to these rules:

<operand_1> AND <operand_2> returns this result:

• TRUE if both operands have the value TRUE (such as, TRUE-TRUE).
• FALSE if one of the two operands has the value FALSE (such as, TRUE-FALSE, FALSE-TRUE, FALSE-FALSE).

<operand_1> OR <operand_2> returns this result:

• TRUE if at least one of the two operands has the value TRUE (such as, TRUE-TRUE, TRUE-FALSE, FALSE-TRUE).
• FALSE if both operands have the value FALSE (such as, FALSE-FALSE).

<operand_1> XOR <operand_2> returns this result:

• TRUE if the two operands have different logical values (such as, TRUE-FALSE, FALSE-TRUE).
• FALSE if both operands have the same logical values (such as, TRUE-TRUE, FALSE-FALSE).

NOT <operand_1> returns this result:

• TRUE if the operand has the value FALSE.
• FALSE if the operand has the value TRUE.

For logic functions, these precedence rules apply:

NOT has precedence over AND, followed by XOR and OR.

Specifies that the interpretation of the next value is to be carried out in this order and manner:

• If the next value has a valid date format, it is to be interpreted as a date.
• If the next value has the format of a floating-point number, it is to be interpreted as a floating-point number.
• If the next value has the format of an integer, it is to be interpreted as an integer.
• If the next value is neither in a date format nor a floating-point number nor an integer, it is to be interpreted as a string.

The result of comparing two values depends on their format.

So, for example, the integer 002 is greater than the integer 1. But the string 002 is less than the string 1, due to the fact that the characters are compared from left to right, thus 0 is less than 1.

Specifies conditions for the size (in bytes) of binary attributes.

Specifies conditions regarding the time that items were created.

Specifies that the next value is to be interpreted as a date.

Returns for a specific item the number of configurations in the current configuration path that meet these conditions:

• The configuration contains a version of the item.
• In the configuration path, the configuration is not located after a configuration to which the item is assigned HIDE mode.

Example:

TYPE= DO & REFERENCED & NOT ACTIVE & INSTCFGCNT > 0

This example returns all items of type DO which are referenced and for which the configuration path contains inactive versions.

Using this feature you can, for instance, distinguish between referenced items with value attributes and referenced items without value attributes.

Specifies that the next value is to be interpreted as an integer.

Specifies conditions for link attributes. The conditions are fulfilled if at least one link is found that fulfills all the specified conditions (AND operation).

The LA condition requires specification of attribute name and link direction.

If you specify an asterisk (*) as the attribute name, the LA condition applies to all link attributes.

Specifies conditions for link attribute sizes. The conditions are fulfilled if the number of links in an attribute satisfies the specified relational expression (for example, number of links > 5).

Only links that fulfill all the specified conditions (AND operation) are counted.

The LA_SIZE condition requires specification of attribute name and link direction.

If you specify an asterisk (*) as the attribute name, the sum of the links in all link attributes of the item is entered into the expression.

Specifies conditions for namespace relationships. The conditions are fulfilled if at least one namespace relationship is found that fulfills all the specified conditions (AND operation).

The NA condition requires specification of attribute name and relationship direction.

If you specify NIL as the attribute name, $SDCAC considers only items that are not assigned to any namespace attribute (such as, unclassified namespace relationships).

If you specify an asterisk (*) as the attribute name, the NA condition applies to all namespace attributes.

Specifies conditions for link attribute sizes. The conditions are fulfilled if the number of namespace relationships in an attribute satisfies the specified relational expression (for example, number of namespace relationships > 5).

Only namespace relationships that fulfill all the specified conditions (AND operation) are counted. The NA_SIZE condition requires specification of attribute name and link direction.

If you specify NIL as the attribute name, $SDCAC considers only items that are not assigned to any namespace attribute (such as, unclassified namespace relationships).

If you specify an asterisk (*) as the attribute name, the sum of the namespace relationships in all namespace attributes of the item is entered into the expression.

Specifies conditions for item names. The maximum length of the names can be 512 characters. The values of the $NMGRP and $NMSPC system variables are used as the values for naming group and namespace in such conditions.

The NAME condition is especially suited for items that were created under the classic naming concept. For these items, you can set the system variables $NMGRP and $NMSPC to 0. When searching for items that were created under the extended naming concept, ASG recommends using the XNAME condition, since it permits you to explicitly state the naming group and namespace. See also Rochade Naming Concept and Generated Item Names.

Specifies that the next value is to be interpreted as a floating-point number.

Returns the value TRUE if there is an item relationship that points to the item. In contrast, NOT REFERENCED returns the items that no item relationships point to. See also Reports Involving Inactive Items.

Specifies conditions for item-specific system attributes.

Specifies conditions for the number of characters (including one character per line for the line break) in item-specific system attributes.Attribute size = No_of_characters + No_of_lines

Returns the value TRUE if the item spans a namespace.

Specifies that the next value is a character string.

Specifies conditions for text attributes.

Specifies conditions for the number of characters (including one character per line for the line break) in text attributes.Attribute size = No_of_characters + No_of_lines

Specifies conditions for item types.

Specifies conditions regarding the time when items were updated.

Specifies conditions for value attributes.

Specifies conditions for the size (in characters) of value attributes.

Attribute type:

• B - Binary attribute
• L - Link or namespace attribute
• SA - item-specific system attribute
• T - text attribute
• V - value attribute

Time when the item version was created or modified

Serves to list the items belonging to the namespace

Lists the names of the item

Item type

Attribute name

Configuration that contains the target item

Sequence number

Item name of the target item in <i_nm> format as described in Accessing Items

Item identification of the target items

Qualifier

Item type of the target item

Alignment according to Rochade words

Item header line

The item header line in the work area has the line position that was specified in the current work area as the start line for this item’s attribute content.

The item header line contains the information that was specified in <ctrlf2>, followed by the line numbers for the first and last line for the attribute content.

Time of creation of the item version

Time of modification of the item version; nnnn is a counter that makes it possible to differentiate between the updates of two versions of an item when the time stamps are otherwise identical.

Attribute type or information

Attribute name in case of attribute type (B, L, SA, T, or V).

NAMESPACE in case of namespace content (I).

NAMELIST in case of name list (N).

Attribute content

For value attributes, the attribute content will be written immediately after the attribute name. Since value attributes never occupy more than one line, the number of lines <line_counter> will not be displayed.

For all other attributes, display of the attribute content begins in the line that follows the attribute header line. In this case, the attribute header line contains the number of lines of the attribute content that follow the attribute name.

Which content will be displayed for link attributes is specified via the <ctrl_lnk> entry in work area <wa3>.

The content of binary attributes will be displayed in hexadecimal format.

Server error

Configuration <cnf> invalid

Attribute <att_name> in <wa2> does not exist or BACKLINK, PROPERTY or DOCIDENT was specified as the attribute name

Syntax error <wa2> - operator was expected

Syntax error <wa2> - too many right parentheses

Syntax error <wa2> - missing right parenthesis

Syntax error <wa2> - elementary condition missing

Syntax error <wa2> - value does not match the type specified

Syntax error <wa2> - elementary condition invalid; $COL and $LN contain the column and line position where the error occurred

<wa2> invalid or does not exist; <wa4> could not be created

<wa1> invalid or does not exist or, within a $QRY command, an item list in the form of <ctrlf1> <wa1> was transferred to the command $SDCAC

<wa3> invalid or does not exist

Redundant entries for an attribute type in <wa3>

<wa4> not specified

First parameter invalid (neither CFG nor PATH)

Command interrupted due to a condition in $QRY

One of the entries in <ctrlf1>, <ctrlf2>, <ctrlf3> is invalid or word mode W was not specified for naming group

Not enough memory

Work area overflow

A character specified in <ctrlf1> or <ctrlf2> is invalid

The variable specified in <wa2> does not exist