Database Management
Reference Manual
Output Syntax
: OUTPUT Command
OUTPUT Command
The following options are available:
OUTPUT CHANGES
Incorporates INCLUDE command for named items. The item must be named in both the current and referenced session. For unnamed items, a DELETE, CREATE sequence is followed.
OUTPUT REVERSE CHANGES
This is the opposite of the current OUTPUT CHANGES command: that is the output is generated can be read back in to restore the given data to how it was at the given session.
OUTPUT CHANGES SINCE
Lets you output all changes to one or more specified database elements since an earlier version of that database. The output is in the form of a macro which can recreate the changes when run on, say, a copy of the original DB. The macro is sent to a file by using the standard ALPHA FILE or ALPHA LOG commands.
Examples:
OUTPUT /ZONE-A
Outputs all elements, whether or not they have ever been changed.
OUTPUT ALL PIPE FOR /ZONE CHANGES SINCE 21 JANUARY
Outputs all changes to named element and its members since the given date.
OUTPUT /PIPE-100 CHANGES
Outputs all changes to named element and its members since last SAVEWORK command.
OUTPUT /PIPE-1 CHANGES SINCE EXTRACT
In an extract, outputs all changes made in the extract which have not been flushed to the parent.
OUTPUT /PIPE-1 CHANGES SINCE LATEST EXTRACT
In an extract database, outputs all changes compared with the latest version of the parent extract.
OUTPUT /PIPE-1 CHANGES SINCE EXTRACT 44
OUTPUT /PIPE-1 CHANGES SINCE EXTRACT PIPE/PIPE-X1
In an extract database, outputs all changes compared with the latest version of the given extract, which must be higher in the extract hierarchy.
OUTPUT /PIPE-1 CHANGES SINCE SESSION 77 EXTRACT 44
OUTPUT /PIPE-1 CHANGES SINCE OCT 2000 EXTRACT PIPE/PIPE-X1
In an extract database, outputs all changes compared with the given extract, which must be higher in the extract hierarchy, at the given session or date.
The macro is sent to a file by using the standard ALPHA FILE or ALPHA LOG commands.
You can also give an AVEVA E3D™ session number. The database states are compared between SAVEWORK operations. For example, if you last saved your design changes at 9:30 and ask for a macro containing changes since 10:00, the macro will contain all changes since 9:30.
Command Syntax:
>- OUTPUT <selele> SINCE -+- <date/time> -+-----------------------.
| | |
|- LATEST ------| |
| | |
|--SESSION nn --| |
| | |
‘---------------+- EXTRACT -+- extname -|
| |
‘- extno ---+->
•
The following options are not available with the OUTPUT CHANGES functionality. Once one (or more) of these options have been specified then REVERSE, CHANGES, etc. cannot be specified following the element to be output.
COMMENT
This specifies that certain comments will be added to the OUTPUT output. The reference number of each element will be shown immediately after the NEW (or OLD) command, the owner of each element will be given, and each reference valued attribute will be output as a comment during the first pass (normally, reference valued attributes are ignored entirely during the first pass). In addition, the position and orientation of Nozzles will be written in the coordinate system of their ZONE. All these comments will be enclosed between the standard comment delimiters, that is:
$(' comment_text '$)
TABULATE
n
This specifies that the output will be tabbed by n*d spaces at the beginning of each line, where d is the depth of the element. Note that where a logical line is split over more than one physical line in the file (which can happen very easily when a short line length has been specified on the 'ALPHA FILE' command) then subsequent physical lines are not tabbed.
n must be between 0 and 6.
TABULATE 0 is equivalent to no tabbing.
INDEX
This specifies that
•
Each line of the output will be numbered and
•
Indexes by reference number and name will be written at the end.
As with tabulate, only logical lines will be numbered; continuation lines will not be numbered.
BRIEF
This specifies that only the NEW or OLD command line will be written, that is, no attributes will be written.
NOUDA
This specifies that user defined attributes will not be written.
ONLY NOUN
or
ONLY (NOUN …. NOUN)
These options specify that only elements of the given types will be output. If more than one type is to be specified, then the list must be enclosed in brackets. At most 10 types may be specified.
PASS
n
This specifies that only the first pass (element definitions; no reference valued attributes) or the second pass (reference valued definitions, connections) will be written. n must be 1 or 2.
OLDFORMAT
This specifies that element definitions will be written using the OLD (rather than the NEW) command, that is, elements are to be updated when the file is re-read.
Locate
If the LOCATE option is used and 'output /VESS1', then the output will contain the following:
NEW LOCATE SITE /ATEST
NEW LOCATE ZONE /ZONE.EQUIP
NEW EQUIP /VESS1
Etc.
REPLACE
If the replace option is used the output will contain the following:
NEW REPLACE EQUI /VESS1
Etc.
N.B. the REPLACE command will only be output for the top level element.
If both LOCATE and REPLACE options are used, the output would be:
NEW LOCATE SITE /ATEST
NEW LOCATE ZONE /ZONE.EQUIP
NEW REPLACE EQUIP /VESS1
SAMER/EF
May be specified after the element to be output, in conjunction with the various formatting options and with 'CHANGES SINCE date' and 'REVERSE'. If specified, each 'NEW' command to originally define each element will be output in the form:
1.
NEW <eltype> <element> REF =rrrrr/rrrrr
Thus when the file is read back in, the element will be assigned the same reference number as previously. Of course, this requires that the reference number is suitable in the environment in which the file will be read.
Examples:
•
OUTPUT SAMEREF CE
•
OUTPUT SAMEREF INDEX /HTEST
•
OUTPUT SAMEREF /STAN.CATA CHANGES
•
OUTPUT SAMEREF CE REVERSE CHANGES
2.
The NEW command has been extended to allow a new keyword 'REF' followed by a reference number to be specified after the element name. If so specified, and the reference number is valid, then the element will be created with the reference number given.
If an invalid reference number is given, the command will be rejected. Two new error messages may occur:
•
859: Invalid reference number: =rrrrr/rrrrr
•
860: Reference number =rrrrr/rrrrr already exists
Examples:
•
NEW BOX /BOX1 REF =15772/17461
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.
