HP Integrity NonStop J-Series - Manual (Page 89)

Web ViewPoint User Guide Version 5.14 - 528226-014 89
 FLUSH indicates, that after the first match is found, the entire line should be skipped
 – (PREPEND^MGR is not specified)
Another example of formatting commands that is specified in the sample script provided above is:
(mon) [READ] {INSTANCES} PCO SKIPLINES 4 FLUSH TAR^CHAR & "$" ENDPCO CUI SCF PAGESIZE -1;
STATUS MON $*
In this example, the command “SCF PAGESIZE -1; STATUS MON $*” gets executed. Since the
command has formatting statements, the output of the command will be formatted according to the
following.
 The first four lines of the output will be ignored (SKIPLINES 4)
 Since the SKIP parameter is not present, every line of the output will be processed
 Since the STARTCOL parameter is absent, processing of each output line will start from column
#1
 Each word in an output line will be considered as an instance if it starts with a “$” (TAR^CHAR
“$”)
 Once a match in a line has been found, the remaining part of the line should be skipped (FLUSH)
 Since the UNTIL parameter is not present, once a word has been found (which starts with a “$”),
all characters including and after the “$” will be considered to be an instance until a space/
comma character is encountered
Note:
Any object that produces instances must have an {INSTANCES} command that describes how the instances are
retrieved, and a {STATUS} command that returns some information about the object. The STATUS command
determines what is displayed by default when an instance gets clicked/ executed.
A folder that contains Instances and Subordinate objects must have a {FLAG} NCU command defined for the
object. It is a good idea to also provide an {EVENTS} and a {HELP} command.
If a command is too long to fit in one line, it can be split into 2 by an “&” (ampersand) separator character. Also
note that one command can span at most 2 lines.
Edit File Considerations:
 Each object declaration must be on its own line; empty lines are not accepted
 A command declaration can at most span two lines and must have an "&" placed at the end of the first
line.
 A line can be up to 237 characters.
 Any object that produces instances must have an {INSTANCES} command that describes how the instances
are retrieved, and a STATUS command that returns information about the object. The STATUS command
determines what is displayed by default when an instance is clicked.
 A folder that contains instances and subordinate objects must have a {FLAG} NCU command defined for
the object.
 It is recommended to provide an {EVENTS} and a {HELP} command.
Loading the File:
Once you’ve created your edit file, you can use it to load an object tree.
 In the Object Tree frame, click the Object Tree link. The Configuration window appears.
 Click the Load tree from edit file icon. The Load tree window appears.
 Enter the location of the edit file, in this example: \sierra.$guest.webocm.telserv.
 Click OK.
Every declaration that is added to the tree shows in the Results frame.