Disclaimer Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law. Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or entity for any actions, claims, loss or damage arising from the use or possession of any information, particulars, or errors in this publication, or any incorrect use of the product, whatsoever.
Trademarks AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden. AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its subsidiaries, registered in the UK, Europe and other countries (worldwide). The copyright, trade mark rights, or other intellectual property rights in any other product, its name or logo belongs to its respective owner.
About the DESIGN Reference Manual The AVEVA PDMS DESIGN Reference Manual describes all the DESIGN commands in detail. It also describes how the DESIGN database is structured. DESIGN is normally used interactively. The Graphical User Interface (GUI) provides discipline-based applications which help you to create, check and report on the model. How to use the applications is described in user guides. This manual is written for experienced users of AVEVA PDMS DESIGN who need to use commands; for example, to write batch macros or to customise the GUI. If you are going to customise the GUI, you will also need to refer to the Software Customisation Guide and Software Customisation Reference Manual for information about PML, the AVEVA programming language.
1.2
Organisation of the DESIGN Reference Manual The DESIGN Reference Manual has three parts:
1.3
•
Part 1 (this volume) describes general DESIGN commands, which are used, for example, for setting up the display, and querying and navigating around the DESIGN database. It also describes how to use the command syntax graphs, which are used to show all the options available for each command.
•
Part 2, Creating the Model, describes the commands for creating database elements and setting their attributes.
•
Part 3, Utilities, describes the DESIGN Utilities for data consistency checking and clash detection, and for exporting DESIGN data to programs such as Review.
Organisation of this Manual This manual, Part 1, is divided into the following chapters: •
Chapter 2 describes How to Use the Syntax Graphs, and also shows the standard syntax graphs which are often referenced from other graphs.
•
Chapter 3, General Commands, describes commands used for saving work, setting units and tolerances, and handling alphanumeric output. These commands are common to several PDMS modules, but are included here for convenience.
•
Chapter 4, Display, describes how to control the way the model is displayed in a graphical view.
•
Chapter 5, Interacting with a Graphical View, describes how commands can accept input from picked items in the graphical view, and how to define construction aids and label the design elements. Note that the commands in this chapter have generally been
DESIGN Reference Manual How to Use the Syntax Graphs
2
How to Use the Syntax Graphs The commands described in this chapter are presented in the form of syntax graphs. •
Syntax graphs are read from top left to bottom right. The start point is shown by >, and you can follow any path through the graph until the exit point, shown by >, is reached.
•
Points marked with a plus sign (+) are option junctions which allow you to input any one of the commands to the right of the junction. For example:
means you can type in ABC or PQR or just press Enter to get the default option.
•
Text in angle brackets <. . . > is the name of another syntax graph. This convention is used for syntax which occurs in many places. The graphs referred to are described at the end of this section. For example:
means that you can enter any combination of option1 and/or option2 and/or option3, where the options can be commands, other syntax diagrams, or command arguments.
DESIGN Reference Manual How to Use the Syntax Graphs
.----<------. / | >---*--- name ----+---> •
2.1
means that you may type in a list of PDMS names, separated by at least one space.
Commands Commands These are shown in a combination of uppercase and lowercase letters, where the capital letters indicate the minimum abbreviation. Note: This convention does not mean that the second part of the command must be typed in lowercase letters; commands may be entered in any combination of uppercase and lowercase letters. For example, the command
CONStruct can be input in any of the following forms:
CONS CONST CONSTR CONSTRU CONSTRUC CONSTRUCT Commands shown in all uppercase letters cannot be abbreviated.
2.2
Command Arguments Command arguments These are shown in lowercase letters. These are just descriptions of what you need to enter. The most commonly used descriptions are as follows:
integer
A positive or negative whole number. For example: 2 -5 25
value
A signed number with or without a decimal point. For example: 2.5 5 -3.8
letter
A single alphabetic character
word
A sequence of up to four letters, e.g. GATE WN P (may be longer in some cases, but only the first four characters are significant).
text
A string of alphanumeric or symbol characters, which may include spaces, enclosed between single closing quotation marks or | characters. This is normally used to add descriptive material to an appropriate attribute. For example: DUTY ’Low Pressure’
DESIGN Reference Manual How to Use the Syntax Graphs
space
The space bar (not usually specified unless of special significance)
name
A sequence of characters preceded representing a PDMS Element name.
by
a
slash/and
For example:
/BRANCH7
/305.ABC
/P4/NOZ
Note: A name should always be followed by a space (unless at the end of a line).
filename
An external file name of the form/filename
varid
An identifier (for use with the VARIABLE command within macros) of the form !name where ‘name’ is a text string. For example:
!COUNTER, comma
!height
The ‘,’ character, which can be used to concatenate DESIGN commands. For example:
NEW FLANGE SELECT WITH STYP WN, CONNECT plus minus star slash
These are the + (add), - (subtract), * (multiply) and / (divide) operators, which can be used in arithmetic expressions. For example:
(1 + 2), (1 - 2), (1 * 2), (1 / 2) Note that there must be a space before and after each of these operators. Note: PML 1 expressions and variables are explained in the Software Customisation Reference Manual.
2.3
Standard Syntax Graphs If a syntax graph refers to a second syntax graph, the name of the second graph is shown in angle brackets. This convention is usually used for standard syntax graphs which are widely used. These syntax graphs are summarised below, and then shown in detail.
DESIGN Reference Manual How to Use the Syntax Graphs
2.3.1
Mathematical, textual or logical expressions
3D Design points (P-points, pins or P-lines)
or
Axial position
3D position
Axial direction
3D direction
Selection
Universal Expression If a value given in a command needs to be calculated from other known values, you can enter an expression, which is evaluated by DESIGN as it executes the command. You will find details of PML 1 expressions in the Database Reference Manual. On-line help describing expressions syntax is available from within DESIGN applications.
2.3.2
Date/Time has the general format Time Day Month Year. Time has the format hour:mins. If no Time is given, the default is 23:59. Day is a single or two-digit integer. If no Day is given, the default is today. If no Time is given, Day must be specified. Month may be entered as a word, or as a number surrounded by spaced / characters. If no Month is given, the default is the current month. Year may be entered as four digits or as two digits. Two-digit years are interpreted within the date window current_year - 99 to current_year For example, in the year 2004: 03
means
2003
04
means
2004
05
means
1905
If no year is given, the default is the current year.
DESIGN Reference Manual How to Use the Syntax Graphs
Examples:
2.3.3
10:30
Assumes current date
22 / 8 / 1999
Assumes time to be 23:59
22 August
Assumes current year and time 23:59
Physical Dimension This syntax allows you to override the working (default) units for dimensions . >--+-- value ----. | | ‘-- ---+-- EXponential value --. | | ‘-----------------------+-- MM ------. | | |-- Metres --| | | |-- INches --| | | |-- FT ------| | | |-- FEet ----| | | |-- text ----| | | ‘------------+-->
Examples:
5
5
in current working units
EX3
5500
in current working units
5.3/4
5.75
in current working units
5’
5 feet
(only use when working units are FINCH)
5’6
5 feet 6 inches
(only use when working units are FINCH)
5’6.3/4
5 feet 6.75 inches
(only use when working units are FINCH)
5 INCHES
5 inches
(regardless of current working units)
5 M
5 metres
(regardless of current working units)
5’6.3/4 IN
5 feet 6.75 inches
(regardless of current working units)
(5 + 2) IN
7 inches
(regardless of current working units)
Note: Values are always held within DESIGN as metric units. When output, values are rounded as follows: •
DESIGN Reference Manual How to Use the Syntax Graphs
| |-| |-| ‘->-+-| ‘->-+-| |-| |-| |-| | | ‘--
| -- -----| | OWNer -----------------| | END -------------------+---> TUBe--. | ROD --+--> LAst -----. | FIrst ----| | PREvious -| | NEXt -----+-- integer --. | | ‘-------------+-- MEMbers--. | integer -----------------------------+-- OF ->
Identification by physical position in the design model: .----<----. / | >- CLOSest -*- -+- WITH -. | | ‘---------------+- UP ----. |- DOWN --| |- EAST --| |- WEST --| |- NORTH -| ‘- SOUTH -+-. .----------------------------<--------------------’ ‘-+- EXTENT -. | | ‘-----------------+- AFTER -. | | ‘----------------+- FROM -. | | ‘---------------+->
WITH
specifies rule restricting choice of element (default is no restriction);
EXTENT
specifies how far to search before giving up (default is 10 metres);
AFTER
specifies that search is to start after given distance in given direction (default is zero);
FROM
specifies reference position from which search is initiated (default is CE).
DESIGN Reference Manual How to Use the Syntax Graphs
Examples:
OWN
Owner of Current Element
GOTO SPRE
Specification of Current (piping) Element
NEXT 2
Second Next Element at same level
4
Fourth Member of Current Element
LAST 3 MEM
Third Last Member of Current Element
END
Next element up in hierarchy
SITE
Site above Current Element
ZONE 3
Third Zone
NEXT 2 PIPE
Second Next Pipe
PREV BOX FIRST ZONE OF /SITE 5 PIPE OF /VALV101 FIRST MEM OF BRAN3 OF /PIPE10 HEAD OF FIRST BRAN Closest valve to current element in East direction in design model (note that syntax accepts only cardinal directions, which must be entered in full)
CLOSEST VALV EAST
CLOS VALV NORTH FROM E10 Closest valve in North direction starting from given 0 N200 U300 position (valves found before this position are ignored)
2.3.5
D Design Points This syntax describes 3D Design Points and their Attributes. A Design Point is: •
= >--+-- North --. | | |-- Y ------| | | ‘-- South --+-- --> = >--+-- Up ----. | | |-- Z -----| | | ‘-- Down --+-- --> = >--+-- East --. | | |-- X -----| | | ‘-- West --+-- --> = >--+-- WRT --. | | ‘-- IN ---+-- -->
Examples:
2.3.7
E1000
East 1000
Z10
Up 10
E30 D10 S20
East 30 Down 10 South 20
E0 IN SITE
East 0 in Site
D Position This syntax provides a 3D position in terms of a specified coordinate, a known identity or point, or a cursor position. General axial position: (see previous subsection)
DESIGN Reference Manual How to Use the Syntax Graphs
| | ‘-- South ---+-->
| | ‘-- West --+-->
= >--+-- Up -----. | | |-- Z ------| | | ‘-- Down ---+-->
= >--+-- --. | | ‘-- value ---+-->
Examples:
2.3.9
E
East
E45N
East 45 North
W-33D
West 33 Up
Y
North
N45E33D
North 45 East 33 Down
N10E10
North 45 East
D Direction This syntax provides a 3D direction by making use of a specified axis direction, a design point, or two 3D positions. General axial direction:
DESIGN Reference Manual How to Use the Syntax Graphs
2.3.10
Selection This syntax lets you describe elements you want to include in, or exclude from, operations. Typically, the following criteria are used to define a selection: •
A class of elements or element types to be selected. You can specify whether all members are to be included, or whether only items (the lowest level components in the hierarchy below a given element) should be included. See below.
•
A logical expression to be satisfied for all selected elements. These expressions return either True or False, and are usually used to check the values of attributes. See the Plant Design Software Customisation Reference Manual.
•
A physical volume in which all selected elements must lie. This volume is always orthogonal to the World coordinate axes. You can specify this in terms of two diagonally opposite points of an enclosing box, or as a volume around an element (with an optional clearance around the element selected). See below.
•
A point in the hierarchy below which all selected elements must lie. You can follow this with an exclusion list to exclude elements from the selection. See below.
•
A list (or collection), such as a drawlist, obstruction list or claimlist, of which the selected elements must be members.
All of these criteria are optional, except for class. If all element types are valid, this should be ALL. If you specify more than one criterion, the specifications must be in the above order, as shown by the following graphs: = >-+- ALL -----------------------. | | | .------<-----. | | | | | ‘- -*- -’ | | | ‘----------------+--. | .-----------------<------------------------’ | +- WIth --. | | |- WHere -+- -. | | ‘--------------------+- -. | | ‘------------+- -. | | ‘------------+- -. | | ‘-------------+-->
allows you to specify a volume to be selected: = >-+- WITHIN -----------. | | ‘- EXCLusive WITHIN -+-- VOLume - -+- -. | | | | ‘--------| | | ‘- - TO - -------+->
Selects all elements where XLEN is greater than 1000mm
ALL WITHIN W8000N17000U1000 TO W1400N13500U1200
Selects all elements within the defined volume
ALL PIPE WITHIN VOLUME /PIPE1 1500
Selects all piping elements within a volume defined as a box drawn around /PIPE1, with a clearance of 1500mm between the edges of /PIPE1 and the volume box.
You can minimise the time taken for any selection operation by making the selection criteria as specific as possible, so that only relevant parts of the databases are searched for the required elements. Where known, specify the element type (e.g. ALL BOX ...), the database element under which the search is to be restricted (e.g. ALL BOX FOR /ZONE1 ...), the volume in which you are interested (e.g. ALL BOX WITHIN N5000 E5000 U0 TO N10000 E12000 U8000 ...), and so on. If you do not do this, all databases in the current MDB will be searched, whether or not they contain relevant types of element, and performance will be impaired.
2.4
Command Input Modes Generally, in DESIGN you are able to access the full range of DESIGN command syntax. However there are two modes where the syntax is restricted to commands only relevant to that mode. The modes are: •
MDB mode allows you to change or query databases during a DESIGN session. Described in DESIGN Databases and MDBs.
Entering DESIGN or Outfitting Design Keyword: DESIGN , OUTFITTING Description: Use the DESIGN command to enter Plant DESING or in the case of Marine projects use the OUTFITTING command to enter Outfitting Design. These command are available throughout PDMS.
3.2
Saving
3.2.1
Saving DESIGN Work See Database Reference Manual Section 7
3.3
Alpha Display
3.3.1
Saving the Alpha Log Keywords: ALPHA LOG
ALPHA FILE
Description: Lets you save the alpha display information to a text file. Two types of output are available, depending on the command used. ALPHA LOG enables the contents of either or both of the COMMANDS and REQUESTS alpha regions to be written to a file. ALPHA FILE enables the contents of the REQUESTS regions only to be written to file. The ALPHA LOG and ALPHA FILE commands may be used to save data such as the results of a data consistency check, or be used as a general output facility.
Note: After an ALPHA file has been opened, subsequent output will be directed to both the file and the screen until the file is closed, or until you change to another PDMS module. Examples: Log information displayed in the COMMANDS region in file /LF1
ALP LOG
/LF1 COMMANDS
ALP LOG
/LF1 OVER COMM Log information displayed in the COMMANDS region in file /LF1. Any existing file /LF1 will be overwritten.
ALP LOG ALP FILE
/LF /LF2
ALP LOG END ALP FILE END
Log information displayed in both alpha regions in file /LF2 Log information displayed in REQUESTS region only Finish logging data
Changing Modules You can change to another PDMS module by typing the name of the module. DESIGN automatically saves your work before changing module.
3.4.2
Exit from DESIGN without Saving Changes Keywords: QUIT FINISH Description: QUIT exits from DESIGN without saving any changes or the display setup. QUIT has the effect of deleting any changes made since the last SAVEWORK, module change or MDB change. FINISH also exits from DESIGN without saving any changes, but in this case you are taken directly to the operating system of your computer. Examples:
Setting Working Units and Tolerances These functions let you set the dimensioning units and precision for design placement and element searching operations. The designer can choose at any time to work with metric or imperial units and can differentiate between the units used for nominal pipe bores and for general linear dimensions. Tolerance settings are available for general 3D positioning, plus special tolerance controls for pipe and structural steelwork layouts. A search radius (the ‘hit radius’) can be specified for cursor picking operations.
Description: You can choose to work with units for nominal bores and dimensions other than those specified in the Catalogue. The PDMS default is to work in millimetres for nominal bores and distances. However, the Catalogue can contain company-specific instructions that alter the defaults; say, feet and inches. After the units setting is changed, all input and output will take place in the new units unless specifically stated. Examples:
MM BORE
All bores will be input and output in mm
FINCH DIS
All distances and coordinates will be input and output in feet and inches
UNITS /PERCHES
All distances and coordinates will be input and output in the units defined in the units definition element /PERCHES in the Properties Database
UNITS DEF
Uses the default Catalogue database units
UNITS
’Standard’ PDMS units
Note: 3 feet 6 inches must be input as 3’6 when using FINCH units. Command Syntax:
>--+-| |-| |-| ‘--
MILlimetre --. | MM ----------| | INch --------| | FInch -------+-- BOres ------. | | ‘-- DIstances --+-->
Gives tolerance and level settings, as well as unit settings
Setting Output Precision of Distance Units Note: You must not change the precision if you are customising the AVEVA Applicationware. You should only use this command if you are writing a completely new application. Keywords: PRECISION Description: Output dimensions, in the current units, are normally rounded to the following degrees of precision: Millimetres
To the nearest mm (e.g. 316)
Inches
To the nearest 0.1 inch (e.g. 38.8)
Feet and inches
To the nearest 1/32 inch (e.g. 3’7.15/32)
Output for setting variables defaults to the following, higher, precisions: Millimetres
To two decimal places (e.g. 316.25)
Inches
To two decimal places (e.g. 38.75)
Feet and inches
To the nearest 1/64 inch (e.g. 3’7.31/64)
You may control the output precision of distances in some modules by using the PRECISION command. This allows you to specify the number of decimal places for MM or INCH output, or the largest fraction denominator for FINCH output. Precision levels for general output and for the setting of variables are specified separately. To specify the output precision, use the command:
PRECision opt1 DIstance opt2 value opt3 where the command options (opt1, opt2 and opt3) are as follows: opt1 defines how the specified precision is to be applied. It is one of the following: OUTput
For general dimensions
VARiables
For setting variables
If opt1 is omitted: •
Both Output and Variables are set if opt2 is DEFAULT
opt2 defines whether you are changing to a newly-defined precision or back to the default settings. It is one of the following: TO DEFault If opt2 is omitted, TO is assumed. opt3, which only applies if opt2 is TO, qualifies the number specified by value. The available choices are: DECimals
Decimal places
DPls
Decimal places
THs
As in 64ths
NDs
As in 32nds
If opt3 is omitted, value is assumed to apply as follows: •
If current units are MM or INCH: value is Decimals
•
If current units are FINCH: value is THs or NDs
Examples:
3.5.3
PREC OUT DI DEF
Set default precision for output
PREC VAR DEF
Set default precision for variables
PREC DI DEF
Set default precision for output and variables
PREC DI 1 DP
Set output to 1 decimal place (MM or INCH units)
PREC OUT DI 4 DEC
Set output to 4 decimal places (MM or INCH units)
PREC VAR DI 3 DP
Set variables to 3 decimal places (MM or INCH units)
PREC DI 64THS
Set output to 1/64 inch precision (FINCH units)
Switching between Actual and Nominal Bores The PRECISION command also allows you to output actual bore dimensions (rather than Nominal bore values) when required. To switch to output of actual bore dimensions, use the command:
PRECISION BORE ACTUAL To switch back to using nominal bore values:
Audible Error Trace Keywords: ALARM Description: When a macro error occurs, there is an audible alarm at the workstation to signal that the error has occurred. Occasionally, macro errors can be anticipated and no audible warning is required. This command allows the audible warning to be switched on or off either interactively or via a macro. If the audible warning is ON, it will sound whenever an error alert is displayed. The default setting is ON . Examples:
ALARM ON
Sets the audible tone to be on.
ALARM OFF
Suppresses the audible tone until it is turned on again.
Command Syntax:
>-- ALARM --+-- ON ---. | | ‘-- OFF --+-->
3.7
Switching Text Output Off Keywords: TRACE Description: This command, applicable in TTY mode only, controls the automatic output of the Current Element name and attributes. When macros are being run, TRACE is always set to OFF automatically. Examples:
TRACE OFF
Stops the automatic output of Current Element name.
TRACE ON
Restarts automatic output of Current Element name.
Giving Operating System Commands from PDMS Keywords: SYSCOMmand Description: PDMS normally assumes that any command input in response to its prompt character (*) is an instruction to the current module, and will check its validity on that assumption. You can issue an operating system (OS) command to the host computer from within PDMS by entering the SYSCOM command followed immediately (without pressing Return) by the OS command enclosed between apostrophes (’) or vertical bars (|). The effect applies only to the single command line; as soon as the OS command has been executed, control is returned to PDMS. Note: Do not try to issue OS commands which might disrupt PDMS operations; for example, commands which would close or amend files currently in use by PDMS. Example:
SYSCOM 'dir'
3.9
Lists directory from which you entered PDMS.
General Querying Facilities You will often find, when working in PDMS, that you need to check existing information about some aspect of the program’s operations; for example: •
Current usage in terms of users, modules and DBs.
•
The currently selected output device.
•
The unique code which identifies the process you are running and the station you are running it from (useful for generating unique workfile names).
•
The current setting, perhaps the default setting, of a command option.
•
The contents of part of a particular DB; for example, the current setting of an attribute or the list of member elements owned by a specific element.
•
The elements which match specific selection criteria entered by you.
To ask for such information from within DESIGN, type
Query(almost always abbreviated to Q) followed by the relevant querying option as described in the following sections. (You also will find more specific querying syntax throughout this set of manuals.)
3.9.1
Querying Your Current Module To check the version number or revision date of your current module, enter one of the following:
Q BANner Q BANner FULL This will cause PDMS to redisplay the banner which was shown when you first entered DESIGN.
Design Mk11.3.1 (WINDOWS-NT 4.0) (29 Feb 2000 : 22.40) (the FULL option will also display data about the software components used by DESIGN).
3.9.2
Querying Your System To ask about your current MDB, enter
Q MDB To output all valid teams for the current user, enter
Q TEAM To output the current PDMS user name, enter
Q USER To output your login name, enter
Q LOGIN/NAME To output the value of an environment variable, enter
Q EVARiable Note: If the environment variable name contains any non-letter characters, it must be enclosed in quotes. To output information about a file, enter
Q FILE To output information about an open file, enter
Q OPENFILE with the file identified by . The information returned is governed by the attribute which can be: NAME
The name of the file as typed in the OPENFILE Command
MODE
The mode as given in the OPENFILE command
FULLName
The fully specified filename
ENTRY
The entry name of the file (i.e. without directories)
SIZE
The size of the file in bytes when it was last closed (it does not increase as it is written to)
DTM
The date and time the file was last modified
OWNER
The owner (creator) of the file
LOCK
Indicates if the file is locked (valid only for OPENFILE)
SORT
Type: File, Directory or Other (e.g. a link)
Note: In all the above, environment variables in filenames are always expanded, even for NAME.
Querying Your Current Output Devices To check the current types of alphanumeric and graphics devices to which DESIGN is expecting to send your output, especially if you have not changed the default settings, enter
Q DEVice To check either type of device separately, enter one of the following:
Q DEVice ALPha Q DEVice GRAphics To check the current settings for your graphics device, enter any of the following (the list is not comprehensive):
3.9.4
Q SETPens
Gives all logical pen settings
Q SETPens number
Gives setting for logical pen number
Q LINESTyle
Gives line type (dotted, dashed etc.)
Q COLours or Q COLORs
Gives colours of all logical colour numbers
Q COLours number
ives colour of logical colour number
Q COLours BACKground
gives colour set for display background
Q COLours ALPHa
Gives colour set for alphabetic characters and so on.
Querying the Command Implementation Mode To check the current state of the command implementation mode, that is, whether you have Actions On or Off , enter
Q ACTions
3.9.5
Asking for a Unique Workstation Code To generate a unique string, based upon your current process and workstation in use, enter
Q UNIQueid This returns a unique string, which is machine dependent. This is useful for generating workfile names that will not clash with names generated by other users.
3.9.6
Querying Elements and Attributes in DBs To check what the current element is, enter
Q CE To check the membership list of the current element, enter
Q MEMbers The members will be listed in the order of their positions in the membership list. To find out which element owns the current element (the inverse of the preceding example), type
Q OWNer To ask what types of element may legally be members of the current element, type
Q LISt To ask whether an element exists, type
Q EXISTS [] [UPDATE] The optional lets you check whether the identified element is of a given type. The optional UPDATE can be used to tell you whether the identified element can be updated or not. The responses to this query are:
TRUEA
If you did not specify and the element exists.
TRUE
If you specified and the element exists and is also of the given .
TRUEC
If the element exists and can be updated.
FALSEA
If the element does not exist.
FALSEB
If the element exists but is not of the given .
FALSEC
If the element exists but cannot be updated (if UPDATE was used).
To ask what elements match specified criteria, enter