Operation

Personal Computer

UMN:BCT - Operation

A30808-X3079-A272-2-7619
UMN:BCT - Operation Operation
Personal Computer

!
Important Notice on Product Safety
Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the
parts can also have elevated operating temperatures.
Non-observance of this conditions and the safety instructions can result in personal injury or in prop-
erty damage.
Therefore only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950. All equipment connected has to comply with the
applicable safety standards.

Copyright (C) Siemens AG 1998

Issued by the Public Communication Network Group

Hofmannstraße 51
D-81359 München

Technical modifications possible.

Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

2 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

This document consists of a total of 68 pages. All pages are issue 2.

Contents
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Other Information Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 BCT Program Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Task Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Alarm Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4 BCT Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.5 BCT Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.6 Command Assistant / EMML and BMML Mode . . . . . . . . . . . . . . . . . . . . . 11
2.7 Command File Executor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.8 General Information on Custom Form Commands and Scenarios . . . . . . . 22
2.9 Scenario Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.10 Scenario Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.11 Scenario Analyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.12 Scenario Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.13 Form Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.14 Form Analyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.15 Interactive Document Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.16 Command Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.17 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.18 Private Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3 The Log Function in BCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

3.1 Application- and User-specific Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.2 Alarm Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.3 Event Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4 Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5 BCT Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.1 General Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.2 Information Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.3 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

6 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

A30808-X3079-A272-2-7619 3
UMN:BCT - Operation Operation
Personal Computer

4 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

1 Overview
This manual describes the operation of BCT applications for BCT users.
The individual menus and menu items are not explained. When necessary, refer to the
online help for a detailed overview and explanation of the menus/menu items, shortcuts
and all icons (see “Commands” in the online help).
Applications that can only be started by administrators are described in manual
UMN:BCT-Administration.

Fig. 1.1 Online help for menus, toolbar and shortcuts

1.1 About this Manual

This manual is divided into five sections based on the BCT program group.
The individual sections cover the following subjects:
• Section 1 Overview provides information on BCT operation
• Section 2 Operation covers operation and the functions offered by the individual
BCT applications
• Section 3 The Log Function in BCT deals with the BCT log files
• Section 4 Trace Configuration contains information on the BCT trace function
(selecting components, start/stop, and evaluation)
• Section 5 BCT Help contains information on the BCT help system

1.2 Other Information Sources

For further information on the applications and Windows NT 4.0, consult the following
sources:
• The online help of the individual applications (Windows NT 4.0, BCT, PCMX,
openFT, etc.)
• Windows NT 4.0 documentation
• EWSD documentation, for operating the network element (MML commands)

A30808-X3079-A272-2-7619 5
UMN:BCT - Operation Operation
Personal Computer

2 Operation

2.1 BCT Program Group

The BCT program group contains administrator applications as well as general BCT
applications that can be started by all users. The general BCT applications are
• Task Tree
• BCT Help
The other applications can only be started by users with administrator’s rights.

To call the Task Tree

To call BCT Help

Fig. 2.1 BCT program group

2.2 Task Tree

Fig. 2.2 Task Tree icon

The Task Tree is the entry point for working with the BCT. It contains the BCT applica-
tions, command files and personal user applications, organized hierarchically. The
administrator assigns each user a Task Tree which can be adapted to the user’s indi-
vidual requirements.
The Task Tree icon is in the BCT program group or on the desktop. To have the Task
Tree started automatically when logging in under Windows NT, just copy the Task Tree
icon into the Startup program group. All programs in this group are then started auto-
matically by Windows NT.
To start BCT applications and personal applications directly from the Task Tree, double-
click the relevant icons. A command file that is called up from the Command Files menu
tree is automatically loaded into the Command File Executor. If a scenario is called up

6 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

under the Scenarios menu tree, the scenario is automatically loaded into the Scenario
Assistant.
Users can make additions to command files, scenarios, personal applications or folders
in the Task Tree, and they can also delete the added items. All tasks in the Task Tree,
except for BCT applications, can be renamed or moved to a different position within the
menu tree branch. BCT applications can only be renamed or moved into a subsidiary
folder.
The Task Tree can be reset at any time to the default status defined by the administrator.
Do this via menu item Tree -> Revert to Default Tree.

Identifies the current BCT user

Command files provided by the

system or added by the user

Scenarios provided by the

system or added by the user

Assigned
BCT applications

Private applications
installed by the user or
provided by the system

Fig. 2.3 Task Tree

A30808-X3079-A272-2-7619 7
UMN:BCT - Operation Operation
Personal Computer

2.3 Alarm Console

The Alarm Console displays alarms from the node element, as well as spontaneous
messages.
Alarms are only displayed for users who have been assigned the Alarm Console. Inde-
pendently of this, alarm messages are collected in log files and can be archived if neces-
sary. Look in BCT Info -> Alarm Log to find the path under which the log files are stored.
The main window can be resized, moved, or minimized. When it is minimized, the Alarm
Console icon changes as soon as a new alarm is received from the node element. This
means that incoming alarms can always be monitored, even if the window is minimized.
An acoustic signal for incoming alarms can be activated via Alarm Console Settings -
> Beeper.

Scroll Timer sets the

time after which an
activated Scroll
Lock is to be deacti-
vated.

Fig. 2.4 Alarm Console

Incoming alarm messages appear consecutively in the display window. Scroll them up
or down to look at a particular message.
Use Scroll Lock to hold an alarm message in the window. Move the scroll bar down to
look at new messages. If Scroll Lock is not activated or the Scroll Timer has timed out,
the most recent message is always displayed.
Use the Select, Find and Copy functions to process alarm messages. Use the clipboard
to copy the contents of the display window to other applications (e.g. text editor).
Refer to the online help for detailed information on the Alarm Console.

2.4 BCT Administration

BCT Administration is used for creating and administrating BCT users and gives access
to the Task Wizard which can be used to create templates and assign the individual BCT
users applications.

8 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

This BCT application is reserved for administrators and is described separately in the
register UMN:BCT-Administration.

Fig. 2.5 BCT Administration

2.5 BCT Info

BCT Info shows users what settings have been made on their BCT. When the applica-
tion has been started, a window with several tabbed pages opens up. The information
in the individual tabbed pages is as follows:
1. User’s name and a short description (entered by the administrator via BCT Admin-
istration).

Fig. 2.6 BCT Info - General

2. Application Log shows the BCT applications assigned to the user by the adminis-
trator. Any log files assigned to the user are shown under Log File Directory. The
log file prefix is shown under File Prefix. A log file using the prefix BMML_ , for
example, is stored in the following form: BMML_1997_06_09_114035.log =
<prefix>_<date = year_month_day>_<time = hour minute second>. If Not Config-
ured appears on the display, this means that no log file is generated for this appli-
cation. The relevant settings are made by the administrator via BCT Administration.

A30808-X3079-A272-2-7619 9
UMN:BCT - Operation Operation
Personal Computer

Fig. 2.7 BCT Info - Application Log

3. The alarm settings of the Alarm Console

To change the settings, go into Alarm Console.

Fig. 2.8 BCT Info - Alarm Settings

4. The location of the user’s alarm log file, the file prefix (e.g. al =
al_1997_06_09_114035.log) and the amount of space in the file.

Fig. 2.9 BCT Info - Alarm Log

5. The Common Log window shows the common applications (e.g. MTA) assigned to
the user by the administrator. If log files were additionally assigned to the user by the
administrator, these files are displayed in the Log File Directory. File Prefix shows
the prefix of the log files. A log file using the prefix MTA, for example, is stored in the
following form: MTA _1997_06_09_114035.log = <prefix> <date = year month day>

10 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

<time = hour minutes second>. If Not Configured is displayed, no log file is gener-
ated for this application. The corresponding settings are made by the administrator.

Fig. 2.10 BCT Info - Common Log

6. The last page shows the links to node elements. The links entered in the TNS data-
base can only be set up by an administrator. The relevant linked database is
displayed under MMA DB Name.

Fig. 2.11 BCT Info - Destinations

2.6 Command Assistant / EMML and BMML Mode

The Command Assistant helps users to select MML commands and send them to the
node element. It supports both EMML and BMML and can be started from the Task Tree
or from the online documentation.
When you click on the Command Assistant, a login window appears where you can
choose the required operating mode. If the Work Offline box is marked, the Command
Assistant starts in the offline mode, i.e. no session is set up to a node element. However,
you can set up a session to a node element at any time under the Command Assistant
(menu item File -> Login). To set up a direct connection to a node element, users must
enter the User ID and the Password with which they were created in the node element
(for version 7.1 or higer and for version 6.2 without User ID).

A30808-X3079-A272-2-7619 11
UMN:BCT - Operation Operation
Personal Computer

Offline mode: Online mode:

no session with a node set up a session with a node
element element

Fig. 2.12 Login window

To prevent unauthorized entry of commands, the system administrator can use the Task
Wizard to assign users a limited number of MML commands. This only applies to EMML
mode, however, because in the BMML mode users do not access the installed MMA
database but instead have access to all the EWSD MML commands in the node. For
this reason, user authorization for the BMML mode should also be restricted (do not
assign the BCT application BMML to the user Task Tree using the Task Wizard).

Main window:
The Command Assistant offers two different main windows for the EMML mode (normal
and quick selection mode for MML commands) and one main window for the BMML
mode, and it always contains at least three subwindows. If necessary, users can activate
additional command output windows.
In EMML mode the Command, Command History and Output subwindows are
displayed, in BMML mode the Command Input, Command History and Output subwin-
dows. The position of the subwindows on the desktop is not fixed.

12 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Fig. 2.13 Command Assistant, EMML mode (normal command view)

Fig. 2.14 Command Assistant, BMML mode

A30808-X3079-A272-2-7619 13
UMN:BCT - Operation Operation
Personal Computer

Subwindow Command:
The left-hand part of the Command subwindow in EMML mode is the command selec-
tion area, showing the MML commands and custom forms commands assigned to the
user by the administrator. Within the menu tree, you can copy commands as often as
necessary. In the normal view the MML command long names are shown as objects in
a tree arranged hierarchically according to tasks. In the Quick Select view the MML
commands and the custom forms commands are listed alphabetically in a selection box.
To get help, move the cursor to the relevant command and then press F1.

Normal view: MML command long Quick Select view of the MML
names in EMML mode commands in EMML mode

Fig. 2.15 Display of commands

The right-hand part of the Command view contains input fields for command parame-
ters. Some parameters are shown in blue here: these are mandatory parameters that
have to be filled out. To get help, move the cursor to the relevant field and then press
F1. If the command is a Custom Form command, you can have additional help
displayed: move the cursor to the parameter field, press the right mouse button to call
up a popup menu, and click on Annotation. An additional parameter explanation will
then be displayed, as entered by the person who created the command (e.g. the
admnistrator).
In the dialog bar all the profiles for a selected command are presented in a selection
box. The command profiles can contain predefined parameters with preset values. This
is useful when repeating a command with almost identical values: the used fields can be
stored with their values in a profile, so that only small modifications have to be made.
The form for the command parameters varies according to the command profile, and it
only offers the predefined command parameters with preset values for the command
profile in question. If no command profile is selected, all the command parameters
appear.
The profiles that have been created can be exported via menu item Profile -> Export.
When you click menu item Export, a window opens where you can select the individual
command profiles on the left-hand side. On the right-hand side of the window you can
enter a name for the export file (menu item To File), or, if you click menu item To MMA
database, you can have the selected profiles exported to a different MMA database.
Use menu item Profile -> Import to import profiles from a different MMA database, or
from a file, into the open MMA database. If you select menu item From MMA database,

14 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

you also have the option of only importing specific profiles from a different MMA data-
base.
Profiles that are exported to a different MMA database or imported into an MMA data-
base can also be made available to all created BCT users. To do this, answer Yes to
the question “...available for all operation?” that appears in the case of Import/Export. If
you answer this question with No, the profiles will only be imported/exported for your
own ID.

Enter profile name. This Only the parameters selected in the

name then appears in the Create Profile window are shown.
dialog box.

Fig. 2.16 Creating a profile for a command

Parameter inputs are automatically checked for correct syntax. Click on the button to the
right of a parameter to open a dialog window showing all the available parameter values
in a pull-down menu. Select the required parameter values with Add or OK. If no pull-
down menu appears, there are no fixed values for this parameter and the correct values
can be assigned with the aid of the CML (to get help on the parameter values, press F1
in the parameter field). Select the input mode via Selection -> Specific or Range. Use
Specific to move the values to the Selected Values window one at a time using the Add
button. To combine several values, link them with &. Use Range to specify a range of
values, e.g. from 1 to 23, then link the range with &&.

A30808-X3079-A272-2-7619 15
UMN:BCT - Operation Operation
Personal Computer

Call the dialog window

Copy the parameter

value into the Selected
values window using
the Add button, and
transfer it to the input
mask with OK

Call the dialog window

Fig. 2.17 Selecting parameter values

Call the dialog window

Copy the parameter

value into the Selected
values window via the
Add button, and
transfer it to the input
mask with OK.

Fig. 2.18 Selecting specific parameter values

16 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Copy the parameter

value into the Selected
values window via the
Add button, and
transfer it to the input
mask with OK.

Fig. 2.19 Selecting a range of parameter values

Pressing the right mouse button calls up a context-sensitive menu where you can
choose whether a variable or a service routine variable is to be copied into the param-
eter field. This function makes it easier to create command files, because a command
can be saved with all its parameters and variables as a command file or appended to an
existing command file (menu item File -> Save As Command File... or Append To
Command File...).
Before a command with variables is executed, a window opens in which you can enter
values for these variables. Then the command or the command file is sent to the node
element.

A30808-X3079-A272-2-7619 17
UMN:BCT - Operation Operation
Personal Computer

The dialog bar contains all the profiles created for this command

Press the right mouse button

to call up the context-sensi-
tive menu for entering a vari-
able in the marked field.

When the command file is executed, a window

opens where you can enter a value for the rele-
vant variable .

Fig. 2.20 Command input: variable

To open MMA Help

for this parameter,
press F1 when
the cursor is in
the field or use the
right mouse button
to open the annota-
tion help

Fig. 2.21 Command input: command help

18 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

History view:
This window shows the last 32 commands that were sent, as well as status information.
To list the commands according to the various categories (status, job no., time, etc.)
double-click on the relevant field in the detail bar.
The information in the history window is saved when a user logs out from the node
element, and it is reloaded when the user logs in to a compatible node element provided
the Command Assistant has not been closed in the meantime. If the node element is not
compatible (i.e. the commands in the history window cannot be executed), History is
initialized.
Commands listed in the history view can be re-entered directly from this window,
canceled, or saved elsewhere as a command file. Call the context menu (press the right
mouse button) and select Reload to have the command reloaded from the command
history window into the input window, where it can be edited and sent again. Use Save
or Append to have the selected command saved in a command file or appended to it.
Cancel the command with Cancel. With the menu item Expand, the user can see the
history details of the MML commands in the database.

To call the context-sensitive menu in the history

view, press the right mouse button in the command
history window.

Fig. 2.22 Context-sensitive menu

The output for a job from the command history can be displayed in a separate output
window. To do this, double-click on the corresponding job or call the context-sensitive
menu with the right mouse button and select Output.
To have all commands listed
according to a specific category,
double-click on the relevant field in
the detail title bar.

Fig. 2.23 History window

Output view:
This window shows the reactions of the node element to the most recent commands. If
a specific job was double-clicked in the history view, the information relating to this job
is shown in a separate window.

A30808-X3079-A272-2-7619 19
UMN:BCT - Operation Operation
Personal Computer

The information in the output window is saved when a user logs out from the node
element and reloaded when the user logs into a compatible node element, provided the
Command Assistant has not been closed in the meantime. If the node element is not
compatible, Output is initialized (canceled).

Fig. 2.24 Output window

BMML view:
Use this window to enter MML commands directly without access to an MMA database.
It is possible to alternate between EMML and BMML via the menu item View -> BMML
Window or the BMML/EMML symbol in the toolbar. A jump is also made to BMML if the
MMA database is damaged or not available. User prompting is not provided in this case.

Fig. 2.25 BMML window

2.7 Command File Executor

The Command File Executor performs automatic input of MML commands to the node
element by means of a batch processing file (command file). To generate command
files, use a text editor, the Command File Executor, or the Command Assistant. The
easiest method is to use the Command Assistant. After calling up the Command Assis-
tant, select the appropriate command from the menu tree and enter the required values
and variables. The command is then saved in a new command file (menu File -> Save
As Command File...). All subsequent commands required for the command file are
simply appended to it (menu File -> Append To Command File...). Then the command
file can be loaded into the Command File Executor and executed.
Only one command file can be executed per Command File Executor, but the Command
File Executor can be called up several times simultaneously, and a separate command
file can be executed in each one.
The command file contains the commands to be executed, the associated parameters
and instructions for the sequencer. Instead of the parameters it may also contain vari-
ables that can be replaced by current values before the command file is executed. For
information on the syntax, refer to the online help under Functions -> Working with
command files -> Command file Syntax.
Use text editors to edit and check the command file.

20 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Fig. 2.26 Command File Executor

A command file is processed sequentially, but in Step mode commands may be skipped
in the event of a negative acknowledgement. Set the execution mode via Mode.

Mode Explanation
Normal The command file is processed line by line. If an error occurs in a
command, this command is skipped and the next command is
processed

Step The command file is processed line by line. If an error occurs in a

command, all commands are skipped up to the next step.
Processing of the command file continues after the step.

Syntax Check The command file is processed line by line, but it is not executed.
Only the command syntax is checked.

At the start of execution the Command File Executor sets up a session with the node
element. When the command file has been executed or the user has stopped file execu-
tion, the session is closed. Command files can also be sent to the destination processor
just for a syntax check, in order to eliminate any syntax errors before the command file
is actually processed.

A30808-X3079-A272-2-7619 21
UMN:BCT - Operation Operation
Personal Computer

When the command file is

started the login window opens.
Select a node element, enter the
password and confirm.

The next window requests a name

for the result file recording all the
commands sent and the node
element’s reactions. If no name is
entered, the reactions are only
displayed in the output window,
which opens automatically, or in the
user log file.

Fig. 2.27 Setting up the connection

Processing of the command file can be followed on the BCT. The command being
processed at any particular time is marked on the screen. The acknowledgements from
the CP are displayed in an output window, but they can also be recorded in a result file.
If the user was also assigned a log file for the Command File Executor (prefix
CFE_*.log), the output is stored in this file. Execution of a command file can be stopped
at any time by means of the appropriate icon or via menu item File -> Abort.

2.8 General Information on Custom Form Commands and

Scenarios
The MML commands for the CP can be combined in BMML format in batch files
(COFIP). There are two types of COFIP files: one type is stored in the CP, the other type
is stored in the BCT.
The COFIP files in the BCT are created and started with the Command File Executor
(see 2.7).
The MML commands in COFIP files are processed one by one. Conditions for branches
in the forward direction can be defined by means of SW switches. If the processing of a
COFIP file is to be interrupted and then continued, this must be taken into account when
the COFIP file is created.

22 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

In addition to the COFIP files in the BCT there are graphics-assisted applications for
creating and administrating form-assisted command files for the CP:
– Using the Form Wizard (2.13) the administrator can combine several MML
commands in a custom form. The result is a new form that permits automatic execu-
tion of several MML commands in a single call. The administrator passes these
forms on to the users.
– Using the Scenario Wizard (2.9), each user can build complex command sequences
(with logical operations) to form a scenario, also making use of the custom forms.
The result is a logically structured operational sequence for MML commands.
A custom form can contain MML commands in any desired order together with the asso-
ciated parameters. Parameters whose values are identical for several commands can
only be entered once in the form. The MML commands must be unique in the custom
form, i.e. any MML command can only appear once in the custom form. When this form
is called up with the Command Assistant, the commands are executed one by one.
A scenario contains a command sequence with a graphically represented structure. It is
executed by the Scenario Assistant. The structure is made up of individual blocks. A
block can contain, for example, branches, commands, or a filtering of outputs. custom
forms or other scenarios (subscenarios) can also be part of a block. A scenario is much
easier to handle than a COFIP file, permitting loops, branches in any direction, and
providing for automatic analysis of command results. At the beginning of a scenario it is
possible to define variables that are used as parameter values for selected MML
commands in the scenario.
The following applications are available for creating and executing custom forms and
scenarios:
• Scenario Wizard
• Scenario Assistant
• Scenario Analyzer
• Scenario Scheduler
• Form Wizard (for use by the administrator only)
• Form Analyzer
There is no special application for executing custom forms. These forms are called up
with the Command Assistant.
The administrator assigns the above applications to the user. Programs that can be
executed by the user are located in the user’s BCT Task Tree in the directory BCT Appli-
cations.

2.9 Scenario Wizard

The Scenario Wizard is used for creating/viewing/modifying/checking the scenarios that
are processed by the Scenario Assistant.
Predefined blocks can be selected from the Wizard Bar and combined to form scenarios.
The individual blocks are then provided with data, i.e. MML commands, command files
(COFIP), user-specific forms, subscenarios, evaluation criteria, branch definitions, and
global variables.
Individual blocks, or the complete scenario, can be processed in interactive or non-inter-
active mode:
– in interactive mode, user inputs are requested during processing

A30808-X3079-A272-2-7619 23
UMN:BCT - Operation Operation
Personal Computer

– in non-interactive mode, a scenario or a block can be processed without manual

input. This means that only complete, non-interactive scenarios can be started as
scheduled jobs by the scheduler.
The blocks in a scenario are linked by arrows which indicate the operational sequence.
To ensure correct execution in the Scenario Assistant, the flow (GUI) and the syntax of
scenarios are checked in the Scenario Wizard. The first step is the GUI check, which
checks the validity of the logical operations between the individual blocks. The second
step, the syntax check, checks the command syntax.
The procedure for creating a new scenario is as follows:
– call up the Scenario Wizard, select the appropriate MMA-DB, open the window for
creating a new scenario
– insert blocks in the scenario window, define the properties of the blocks, define any
variables, annotate the blocks and link them with arrows to define a sequence
– carry out the flow check and the syntax check
– annotate the scenario, if necessary, and save it
– where applicable, add the scenario to the Reference Tree
When the Scenario Wizard is activated, an empty window appears first:

Fig. 2.28 Scenario Wizard window

The example below explains how to create a new scenario.

First, click menu item FILE, NEW to open the MMA selection box:

24 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Select MMA-DB for the scenario

Click OK to confirm selection

Fig. 2.29 Selection box for MMA database

When you have selected the MMA database, a window showing the scenario flow (struc-
ture view) appears in the Scenario Wizard:

Scenario overview; the start block is

the default.

Description of the marked

block

Scenario name (here: Scenario1)

and MMA-DB (here: V13.ENGL)
Wizard bar for selecting
scenario elements

Fig. 2.30 Scenario Wizard with structure window

You can modify the font settings in the scenario window via menu item OPTIONS,
FONT. To change the colors for the blocks in the scenario window, click menu item
OPTIONS, COLOR.
An existing scenario or a scenario that is to be newly created is shown in the scenario
window. Scenarios can be edited in this window. On the left-hand side of the main
window is the wizard bar from which new scenario elements can be selected.

A30808-X3079-A272-2-7619 25
UMN:BCT - Operation Operation
Personal Computer

Standard cursor
Arrow linking blocks
Insert command block
Insert block for custom form
Insert block for COFIP
Insert block for subscenario
Insert branch block
Insert block for multiple branches
Insert block for command output analysis
Insert block for value assignment
Insert block for loops
Insert block for annotations
Insert end block

Fig. 2.31 Wizard Bar

The wizard bar does not have an icon for the start block, because this block is automat-
ically included in a new scenario. A scenario can only have one start block, and the start
block cannot be deleted.
To insert a new block in a scenario, first click on the appropriate block in the wizard bar
and then drop it in the scenario window. The cursor then reverts automatically to its stan-
dard appearance. If you want to insert an element more than once, press and hold CTRL
when you click on the required element in the wizard bar. The selected element is
stored, and the cursor does not revert to its standard appearance. When you have
inserted the required number of blocks, click on the standard cursor in the wizard bar to
end the insertion mode.
A scenario contains at least a start block, an end block and an action (e.g. an MML
command). Scenario blocks must be linked with arrows to form a sequence. Global vari-
ables for the entire scenario can be defined in the start block. You can user these global
variables to assign values to the parameters in other blocks.
Every block can operate in non-interactive mode with predefined parameter vaues, or it
can operate in interactive mode and request operator inputs during execution of the
scenario.
Scenario elements:

Arrow
Arrows are used to link blocks in a scenario. The wizard bar has a separate button for
drawing arrows. To link two blocks, first click on the arrow button on the wizard bar.
Press the mouse button on the first block, drag it to the second block and release it there.
The two blocks are now linked with an arrow. Arrows in an upward direction are not
allowed. To delete an arrow, highlight it and press the delete button. An arrow stores
information about the blocks it links. Two arrows are allowed to intersect, but an arrow
cannot overlap on a block.

26 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Start block
The start block is used to start the execution flow of a scenario. A valid scenario can only
have one start block. Any variables defined in the start block are used as global vari-
ables for this particular scenario, i.e. they can be used to assign values to parameters
in the other blocks in the scenario. The values of global variables can also be read from
a text file specified in the start block.

Command block
The command execution block associates an MML command that is to be executed. The
MML command is selected from the MML tree, and its parameters are defined.

Block for custom forms

The custom form execution block associates a custom form that is to be executed. You
can select a custom form from the MML Tree and define its parameters. When the
scenario is created the custom form is only linked, but it is not read or validated until just
before scenario execution begins. This ensures that even if the administrator modifies
the associated custom form later, the most recent custom form will always be read, vali-
dated and, if it is valid, executed in the Scenario Assistant.

COFIP block
The command file execution block associates a command file that is to be executed.
You can browse through the command files and then associate a particular command
file with the block. When the scenario is created the command file is only linked, but it is
not read or validated until just before scenario execution begins. This ensures that even
if the user modifies the associated command file later, the most recent command file will
always be read, validated and, if it is valid, executed in the Scenario Assistant.

Subscenario block
The subscenario execution block associates a subscenario that is to be executed. A
subscenario is a scenario file that has been validated and saved . You can browse
through the subscenarios and then associate a particular subscenario with the block.
When the scenario is created the scenario file is only linked, but it is not read or validated
until just before scenario execution begins. This ensures that even if the user modifies
the associated subscenario later, the most recent scenario file will always be read, vali-
dated and, if it is valid, executed in the Scenario Assistant. The subscenario can return
a positive integral value to the main scenario, which can indicate the result of execution.

Decision block
The decision block is used to branch the execution flow according to the decision state-
ment associated with the block. A global variable and a comparison value are used in
the decision statement. The first block connected to the decision block is made the
TRUE path by default. The user can change this later. In non-interactive mode, the deci-
sion statement is evaluated in the background and the flow is branched without
prompting the user. In interactive mode, the user is prompted to choose a particular
branch of flow by double-clicking the next block after the decision block in the scenario.

Multi-path decision block

A multi-path decision block is used to provide two or more paths for branching the
execution flow. The execution flow is branched on the basis of the evaluation of a
multiple-decision statement associated with the block. Conditional expressions

A30808-X3079-A272-2-7619 27
UMN:BCT - Operation Operation
Personal Computer

involving global variables are used in a multiple-decision statement. The expressions

need not be mutually exclusive. The condition is checked from top to bottom and the first
path whose condition is satisfied is executed. Other paths are ignored. The number of
output paths is fixed when this block is drawn up. In non-interactive mode, the multiple-
decision statement is evaluated in the background and the flow is branched without
prompting of the user. In interactive mode, the user is prompted to choose a particular
branch of flow by double-clicking the next block after the multi-path block in the scenario.

Output evaluation block

The output evaluation block is used to assign values to variables on the basis of output
from the CP. Variables associated with this block become global variables after execu-
tion of the block. In non-interactive mode, the user has to associate evaluation criteria
with the block when the scenario is created. The evaluation criteria define a specific
pattern to be searched for in the CP output. The value obtained using the evaluation
criteria is assigned to the variable. In the interactive mode, the user has to assign values
to the variables associated with this block at the time of execution.

Value Assignment Block

The value assignment block is used to declare new global variables or to assign new
values to existing variables in a scenario. The new variables apply only from this block
to the stop block or blocks that come after it in the execution flow. Redefinition will have
effect from this block onwards in the course of execution.

Loop block
The loop block is used to specify how often a section of the scenario is to be repeated
during execution. A control variable and a range of values (integers) are associated with
this block. The associated control variable is defined in the block. This is used to repeat
execution of a section of the scenario flow.

Information block
The information block contains information that is to be displayed at that particular point
in the scenario. In non-interactive mode, no information is displayed. In interactive
mode, the information associated with the block is displayed to the user.

Stop block
The stop block indicates the end of the execution flow. A scenario can have more than
one stop block. Each branch of the execution flow must end with a stop block. A return
value is associated with each stop block.
Procedure for creating new blocks:
– first, click on the required block in the wizard bar, then click on the appropriate posi-
tion in the scenario window
– next, double-click the new block in the scenario window in order to set the properties
of the block
– then link the finished block into the scenario by means of arrows
The following example shows how to create a new command block:

28 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Using the wizard bar, insert the new block

in the scenario window

Double-click the new block to open the

properties window for this block. In the
properties window, call up the MML
tree or Quick Select (the MML tree is
used in the example)

In the MML tree, double-click the

required command, enter parameter
values or variables where applicable,
select profiles where necessary,
confirm entries with OK

The MML command is now

assigned to the block.

Select options for block, e.g.

interactive

Click OK to assign options to the

block

Link the new block into the

sequence with arrows from the
wizard bar

If required, enter annotation for new block

Insert further blocks and/or stop block

Fig. 2.32 Example of how to create a new block

A30808-X3079-A272-2-7619 29
UMN:BCT - Operation Operation
Personal Computer

N.B.!
Refer to the online help for detailed information and further examples of how to create
the blocks (HELP, HELP TOPICS, TECHNICAL NOTES)
The figure below shows an example of a scenario in the scenario window:

Fig. 2.33 Scenario Wizard main window with scenario loaded

Before a scenario can be executed it must be checked with regard to its flow and its
syntax. Click menu items VALIDATE, FLOW and VALIDATE, SYNTAX respectively to
have the checks done. The syntax check can only begin when the flow check has
returned zero errors.
The result of the checks is shown at the bottom right of the output window.

Buttons for syntax or

flow check.

Output window for

syntax or flow check.

Fig. 2.34 Scenario Wizard with result of checks

30 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

After the syntax check and after the flow check, the blocks change color.
The default colors are:
– unchecked blocks: gray
– syntax-checked blocks: light blue
– flow-checked blocks: turquoise
The finished scenario can be annotated before being saved:
To annotate the scenario before saving it, click menu item FILE, ANNO-
TATION to open the annotation window

Enter annotation

Click OK to store annotation

Click menu item FILE, SAVE to open the window for saving the scenario

Select a directory

Enter a file name

Click SAVE to save the file

Fig. 2.35 Saving a new scenario

2.10 Scenario Assistant

The Scenario Assistant executes the scenarios created with the Scenario Wizard. It can
be started at once, or it can be scheduled for execution by the Scheduler Executor.
When you start the Scenario Assistant, an empty main window opens up. Here you can
open a scenario or call up the Scenario Scheduler.
Use menu item FILE, OPEN to select the scenario that you want to open.
Alternatively, you can double-click a scenario in the task tree to start the Scenario Assis-
tant directly.

A30808-X3079-A272-2-7619 31
UMN:BCT - Operation Operation
Personal Computer

Mark the scenario

Click OPEN to open the

selected scenario

Fig. 2.36 Scenario Assistant main window with File-Open dialog

The structure window gives a detailed view of an open scenario:

CP message output area

Fig. 2.37 Main window with scenario display

Before you execute a scenario you can run a syntax check over it manually (menu item
VALIDATE, SYNTAX) and start it or stop it as you like, or interrupt it and continue it.

32 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Before starting a scenario you can set options (e.g. execute “dangerous command”).
You can view the hierarchy of the scenarios and subscenarios in a drop-down menu, but
only on the following conditions:
– the relevant scenario has been started
– the block with the subscenarios is currently being executed
The button for the scenario hierarchy is only active if the above conditions are fulfilled.
The reactions of the CP to the actions in the scenario can be displayed in a number of
ways:
– Default: the CP messages are displayed in the output window under the scenario
display window.
– For output evaluation blocks or blocks with CP messages (e.g. MML command
block) the CP messages can also be displayed in a separate output window (filtered
output). The messages are displayed block by block, i.e. all outputs for one block
are displayed together. The output evaluation block has a separate button for this
purpose, the other blocks involved activate the separate output window via a
context-sensitive menu.
– You can use menu item OPTIONS, SCENARIO RESULT FILE ... to have the CP
messages collected in an optional result file. This file also contains any error
messages relating to the scenario execution. This result file must always be created
for scenarios that are started by a scheduler.
The execution of a scenario is indicated on the screen by color coding of the blocks. The
following distinctions are made:
– blocks that were not executed, due to an error
– blocks that have already been executed
– a block that is currently being executed
– blocks that have not yet been executed or have been skipped
To start a scenario with menu item EXECUTE, RUN, proceed as follows:

A30808-X3079-A272-2-7619 33
UMN:BCT - Operation Operation
Personal Computer

Select a CP

Enter user ID and password

If applicable, select log file

for CP messages

Click OPEN to open the dialog

box for details

In the adjacent window, enter

options for scenario execution

Click OK to start the selected

scenario

Fig. 2.38 Starting a scenario in the Scenario Assistant

After a scenario has been started, an automatic syntax check is done first. If an error is
detected, the scenario is not executed.
If the scenario has an interactive start block with global variables for the scenario, the
user is prompted to enter the appropriate values.
The command window shows the form for an MML command or a custom form, if
parameter entries are necessary for the execution of this command. The block
containing the relevant command must be operating in interactive mode.
If, in the case of a non-interactive block, the parameter values are not all assigned auto-
matically, this block automatically goes into interactive mode and prompts the user to
enter the missing values. This can happen, for example, if an output evaluation has not
produced a result.

34 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

executed blocks

Buttons for
block being executed
viewing sub-
scenarios

block not yet executed

Message output window

Fig. 2.39 Example of scenario execution in the Scenario Assistant

The figure below shows how an input prompt for an MML command appears in the
Scenario Assistant:

Enter parameter value

Click OK to confirm entry (entries)

Fig. 2.40 Example of an interactive block in the scenario

A30808-X3079-A272-2-7619 35
UMN:BCT - Operation Operation
Personal Computer

You can use the context-sensitive menu in the Scenario Assistant to have information
about blocks displayed, or filtered outputs for specific blocks (if possible):

context-sensitive
menu

Fig. 2.41 Example of a context-sensitive menu

Fig. 2.42 Example of filtered output

36 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

A scenario that has been started can be stopped and continued again in different ways:
– Using menu item EXECUTE, PAUSE/RESUME
PAUSE stops the execution of a scenario at the end of a block, i.e. a block that has
been started is finished before the scenario is stopped. RESUME continues the
scenario by processing the next block.
– Using menu item EXECUTE, BREAK/RETRY
BREAK stops the execution of a scenario within a block, i.e. a block that has been
started is aborted. RETRY restarts the block that was aborted and continues the
scenario.
– Using menu item EXECUTE, STOP/START
STOP terminates the execution of a scenario immediately. The scenario cannot be
continued, it has to be restarted completely with START.
In the event of an error a scenario is automatically terminated and has to be restarted
when the error has been corrected.
If a scenario is stopped with PAUSE, the CP timeout causes this scenario to go into the
break mode after a preset period, so that it has to be continued with RETRY. This proce-
dure is necessary, so that when a connection has been aborted by the CP because of
a timeout, the BCT can automatically set up a new connection. Otherwise, the scenario
would have to be restarted from the beginning after a CP timeout.

2.11 Scenario Analyzer

The Scenario Analyzer checks for discrepancies between the commands in a scenario
linked to a specific MMA DB and the corresponding MML commands in a different data-
base version. The user then knows what modifications have to be made so that a
scenario linked to one particular MMA DB can be executed in any other database
version.
The user can select the scenarios that are to be checked and specify the database with
which they are to be compared.
The Scenario Analyzer checks the following points:
• whether the commands are present in the scenario in the new DB
• whether all mandatory parameters of the corresponding commands are covered by
the scenario in the new DB
• whether the optional parameters can be used in the scenario in the new DB
Scenarios have a hierarchical structure. Consequently, the Scenario Analyzer does not
check any blocks containing subscenarios, custom forms or COFIP files. The contents
of these blocks must be checked beforehand with the appropriate test programs.
When the Scenario Analyzer is activated, the Start dialog box appears:

A30808-X3079-A272-2-7619 37
UMN:BCT - Operation Operation
Personal Computer

Select directory for scenario files

Mark scenario file(s) for analysis

Click OPEN to open (confirm)

the selected scenarios

Select an MMA-DB for analysis

The scenarios selected with

OPEN are displayed in this Click START to start the anal-
area. ysis

Fig. 2.43 Start dialog box for Scenario Analyzer

You can select several scenario files for analysis instead of just a single file
(CTRL/SHIFT + left mouse button). To deselect files, click REMOVE.
The results of the analysis are displayed as a list with all consistent or inconsistent
scenarios. You can request detailed results for selected scenarios. The results of the
analysis can be saved in a file or printed out.

Click DETAILS for a

display of detailed informa-
tion about a marked result
line.

To mark a result line for a

detailed view, click the line
in the “Status” column.

Fig. 2.44 Scenario Analyzer Report

38 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Click CLOSE to close

the Scenario Analyzer.

Fig. 2.45 Scenario Analyzer: detailed report

Click CLOSE to close

the Scenario Analyzer.

Fig. 2.46 Example of detailed report for inconsistent scenario

If the results of the analysis have not yet been saved, the user has the option of saving
them in a file before the Scenario Analyzer is closed.

Fig. 2.47 Confirmation box for Scenario Analyzer

Any errors in the scenario must be corrected manually with the Scenario Wizard on the
basis of the analysis report.

A30808-X3079-A272-2-7619 39
UMN:BCT - Operation Operation
Personal Computer

2.12 Scenario Scheduler

The Scenario Scheduler allows scenarios to be executed according to a schedule. You
can start the Scenario Scheduler by double-clicking the icon in the task tree, or via the
Scenario Assistant.
Scenarios that are to be started by the Scenario Scheduler must have been checked for
correct syntax and must not be interactive, i.e. they must have no syntax errors and must
not require any user input.
Each user can only access the scenarios which he created or which have been assigned
to him. Only these scenarios can be stored as scheduled jobs in the Scheduler.
If a BCT user ID or user password is changed, any scenarios stored in the Scheduler for
the old user ID or for the old password will not be executed.
All scheduled jobs for scenarios appear in the Scheduled Job Table. However, a user
can only modify those scheduled jobs for which he has authorization.
To create a scheduled job you must enter the following parameters:
• scenario name
• file for result messages from the scheduled job
• CP name
or CP names, if the scheduled job is started simultaneously in several network
nodes
• user ID(s), password(s)
• starting time
• execute/do not execute dangerous commands
• any information about periodic scheduled jobs
When the Scenario Scheduler is opened, the Logon box appears:

Enter user ID and password and

confirm with OK

Fig. 2.48 Logon box for Scenario Scheduler

The stored scheduled jobs are listed

Click ADD to open the
with their status in this area.
window for adding new
scheduled jobs

Fig. 2.49 Overview of jobs for the Scenario Scheduler

40 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Add Job box: If Broadcast is marked, the

selected custom form is
executed in several network
nodes simultaneously.

In this list, mark the network

nodes for Broadcast jobs
with CTRL/SHIFT + left
mouse button

Click this button to see more

details.

The scenario for the scheduled job, the result file, the start time and the option for
dangerous commands are entered in the left-hand area of the dialog box shown
above.

Add Job box and EWSD details for Broadcast jobs:

Click OK to close this

dialog box

Click SET to accept the EWSD user

details.
Click OK to close this dialog
box

Fig. 2.50 Add Job box for the Scenario Scheduler

Several network nodes are selected for Broadcast jobs. These network nodes can be
sent the same user details or different user details. In the example above, the network
nodes are all sent the same user details.

A30808-X3079-A272-2-7619 41
UMN:BCT - Operation Operation
Personal Computer

Further details for

scheduled jobs

Click OK to confirm the sched-

uled job

To cancel a selection made in the field “Days” or “Date”: posi-

tion the mouse cursor on the marked place, press CTRL+left
mouse button

Fig. 2.51 Advanced Options box for Scenario Scheduler

The example above contains a periodic scheduled job which is carried out on the first
day of a month if this day is also a Sunday. The scheduled job ends on 31.12.1999 at
12:00 noon.
When the scheduled job has been confirmed, it appears as a new line in the job window:

New scheduled job

Click CLOSE to
close the application

In this column, mark the relevant scheduled

job for processing

Fig. 2.52 Overview of Scenario Scheduler jobs

Every scheduled job that appears as a line in the Job window can still be modified or
canceled. You can also request details of every scheduled job.

42 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

Before a scheduled job can be executed, you must mark it. To do this, click on the rele-
vant job in the first column (Status).
To change a marked job, click MODIFY; to delete it, click DELETE. Details of a sched-
uled job are displayed after a double click on the appropriate line of the first column
(Status).
To end the Scenario Scheduler, click CLOSE.

2.13 Form Wizard

The Form Wizard, which is only available to administrators, is used tor creating and
modifying custom forms. The administrator puts the forms at the disposal of the users,
who can use them, add their own profiles to them and insert them in scenarios, but
cannot change them.
A custom form contains a selection of MML commands with the associated parameters
(which may have been renamed). Mandatory parameters are automatically taken over
from the MML commands into the custom form, and they cannot be removed. Parameter
values that are identical for several commands only have to be entered once in the
custom form.
The Form Wizard has the operating modes “Guided” and “Expert”.
– In Guided mode the Form Wizard prompts the user for confirmation before default
entries are made, for example when two (or more) commands in a custom form have
identical parameters. In this case the user must decide whether to use one and the
same parameter for the commands in question or whether to rename parameters so
as to be able to distinguish between the parameters of the different commands. If an
identical parameter is valid for several commands, the same parameter value is
entered for these commands. If the parameters are renamed, different parameter
values can be entered for each individual command.
– In Expert mode it is automatically assumed that an identical parameter is valid for all
the relevant commands and therefore supplies the same value for these commands.
The user is not asked to make a decision.
The MMA help is available in the Form Wizard for every command listed in the MML tree
(F1 key). For every custom form and each parameter in the custom form annotations
should be added with the Form Wizard.
Commands and parameters can be listed in the custom form in any order. The
command sequence in the Form Wizard can be changed at any time with the Command
Manager. However, each MML command can only occur once in the same custom form.
The parameter sequence can also be changed at any time with a context menu (click
the right mouse button on the parameter in the parameter list).
The finished custom form is automatically stored in the Reference Tree, and from there
it is assigned to the users and stored in their own MML command tree.
The Form Wizard offers a preview of a custom form, showing you what the form looks
like in EMML mode in the Command Assistant.
The Command Assistant treats the custom forms like any MML command. There is only
one unique BCT job identification for the entire custom form. On the basis of the BCT
job identification the result for the custom form is displayed as a single entry in the
Command History Window.
Inividual MML commands or CP messages refering to individual MML commands can
be displayed using a context-sensitive menu (right mouse button).

A30808-X3079-A272-2-7619 43
UMN:BCT - Operation Operation
Personal Computer

A point to note is that the Command Assistant processes the MML commands from a
custom form one by one and therefore aborts the execution of a custom form as soon
as an MML command cannot be executed.
In the custom form the associated profiles can also be used for the MML commands.
When the custom form is created, a profile can be selected (if available) for each MML
command. It is also possible at any time, using the Command Assistant, to set up a
Custom Form Profile for the complete custom form.
The Command Assistant performs an extended syntax check of the custom form before
it is executed. In the Command Assistant it is also possible to check, after parameter
input, that the predefined value ranges have been adhered to.
Since a custom form is called up in the Command Assistant just like any other MML
command, please refer to the appropriate section for the Command Assistant for further
information on executing custom forms.
The Form Wizard has an import and export function with which selected custom forms
can be imported from, or transferred to, other databases or data media.
The procedure for creating a new custom form is as follows:
– open the Form Wizard
– select and enter MML commands for the form, select optional parameters, rename
parameters if necessary, add annotations for parameters (these annotations can be
read later in the Command Assistant via the context menu)
– if necessary, enter logical expressions and conditions for command execution via
the Expression Builder, enter annotations for parameters (if not already done)
– save the new form with FILE, SAVE, assign a short name and a long name,
add an annotation for the custom form if required, specify the sequence of the MML
commands
– if necessary, check the form view in the Command Assistant with VIEW, PREVIEW
– using the Task Wizard, assign the new custom form to the users (see Register
ADMIN)
The use of the Form Wizard is explained below by means of an example. When the
program has been started, the MMA-DB has to be selected first, then the empty main
window appears:

Select MMA DB

Fig. 2.53 Selecting the MMA DB

44 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

MML tree or alphabetical Parameter list

list of commands

MML commands in the

custom form

Command list for the

marked parameter

Annotation for the marked

parameter

Fig. 2.54 Form Wizard window

The available MML commands can be displayed in various ways:

– in the standard view, as an MML tree (click the required command to select it, or
search with menu items TREE, FIND MML COMMAND)
– as an alphabetical command list (switch over with menu item COMMAND, QUICK
SELECT, click on the required command in the list, or enter the first letter)
In the following example, the tree view is used.
When the user double-clicks the required commands in the MML tree the selected MML
commands are transferred to the custom form. The default setting is “Guided mode”. If
a parameter occurs in several MML commands, the user is asked to make a decision.

Before a command is inserted, parame-

ters can be renamed here if necessary.

Click OK to execute the marked action

Fig. 2.55 User prompt in Guided mode

A30808-X3079-A272-2-7619 45
UMN:BCT - Operation Operation
Personal Computer

In the above example, an identical parameter, and therefore the same parameter value,
is used for several commands.

A context menu (right mouse button)

A double click at a parameter offers operations to move or sort param-
starts renaming dialog eters in the list

Fig. 2.56 Form Wizard main window with commands loaded

In the main window you can select the commands for a custom form from the menu tree.
The main window contains a number of subwindows. In the Custom Form window the
MML tree is displayed on the left-hand side, and the mandatory parameters and the
selected optional parameters on the right-hand side. At the bottom of the right-hand
window, annotations for marked parameters can be entered in the Annotations field. The
Commands field shows the origin of a marked parameter.
The bottom part of the main window contains the MML commands in the loaded form.
Command parameters can be renamed at any time. To do this, select the parameter to
be renamed with a double clickin the corresponding command window. Then a dialog
box for renaming the selected parameter starts.
A renamed parameter is only valid for the MML command for which it had been selected.
If a renamed parameter was valid for several commands before renaming it is removed
from this combination after renaming.
The following example demonstrates parameter renaming:

46 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

A context menu (right mouse button)

A double click at a parameter offers operations to move or sort param-
starts renaming dialog eters in the list

Enter new parameter name in this field

In the example the parameter “CXGRP” has

been selected with a double click in the
command window of “MODCXCPT”. That
means the renamed parameter is valid only for
the command mentioned above and not valid
for “MODCXSCFEA” any more.

Parameter list after renaming of “CXGRP” to “CXGRP1” for the command

“MODCXCPT”:

Fig. 2.57 Parameter renaming

To start the Command Manager, click menu item COMMAND, MANAGER. The
sequence of the MML commands can be changed in the Command Manager. Condi-
tions and logical expressions can be entered for the command parameters.

A30808-X3079-A272-2-7619 47
UMN:BCT - Operation Operation
Personal Computer

In the following example, the command DISPKEYWORD is only executed if a value is

specified for the parameter “OPMODE” when the custom form is called up in the
Command Assistant. Otherwise this command is skipped.

Click DELETE to delete a

command from the form

Click MOVE UP/DOWN to

change the sequence of the
MML commands

Click ADVANCED to start the

Expression Builder for the
marked command

In the Expression Builder, logical

expressions or conditions relating to
command parameters can be
defined

Click CHECK to check logical expres-

sions and conditions before they are
accepted

Click OK to accept the entries in the Expression

Builder. Then click CLOSE to close the Command
Manager.

Fig. 2.58 Command Manager and Expression Builder

To check the appearance of the custom form in the Command Assistant, use menu item
VIEW, PREVIEW:

48 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

This view appears when the

custom form is called up
with the Command Assistant

Fig. 2.59 Form Wizard preview window

The preview window shows only the fields for the command parameters but not the
selection fields for the profiles. The profiles are only managed by the Command Assis-
tant.
The finished form is saved with menu item FILE, SAVE:

A30808-X3079-A272-2-7619 49
UMN:BCT - Operation Operation
Personal Computer

Enter short name

Enter long name

Enter annotation for the

custom form

Fix the execution

sequence for the MML
commands with MOVE
UP/DOWN

Click ADVANCED to start the

Click OK to save Expression Builder

Fig. 2.60 “Save As” window

To end the Form Wizard use menu item FILE, EXIT.

The custom form is now available in the Reference Tree and can be opened with the
Form Wizard for subsequent editing or deletion.

Before a user can call up this form with the Command Assistant, the administrator must
first copy it with the Task Wizard into the user’s task tree. This also applies to the admin-
istrator’s task tree.
To remove a custom form from a task tree:
– use the Task Wizard to remove the custom form from the task tree of the user in
question
To delete custom forms:
– using menu item FILE, DELETE in the Form Wizard, delete the custom form from
the Reference Tree (this custom form is then automatically removed from all user
task trees)

2.14 Form Analyzer

The Form Analyzer detects discrepancies between the MML commands in a custom
form assigned to one particular MMA DB and the corresponding MML commands in a
different database version.
The user then knows what modifications have to be made so that a custom form linked
to one particular MMA DB can be executed in any other database version.
The user can select the MMA DB with assigned custom forms that is to be analyzed and
the MMA DB with which it is to be compared. Individual forms or all user-specific forms
of an MMA DB can be selected for the comparison.

50 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

The Form Analyzer checks the following points:

• whether the commands in the custom form are available in the new DB
• whether all mandatory parameters of the corresponding commands are covered by
the custom form in the new DB
• whether the optional parameters in the custom form can be used in the new DB
The Form Analyzer should also be used to analyze a form imported from a different
database. A newly imported custom form is already linked to the current database when
the import process is completed (the current database is set whenever the Form Wizard
is opened). For this application, the source and target database are identical for the
check with the Form Analyzer.
The following example shows how to use the Form Analyzer. When the Form Analyzer
has been opened, the Start dialog box appears first.

Select
source data- Start analysis
base for
comparison

Select form to be
Select target checked
database for
comparison

For newly imported custom forms:

source database=target database
This shows whether the imported form can be
processed in this database without modifications

Fig. 2.61 Form Analyzer Start dialog box

In the Start dialog box you select the source and target database and the custom forms
that are to be checked. Click Start to start the analysis.
The result of the analysis is displayed or printed out as a list with all the consistent or
inconsistent custom forms. Detailed results can be requested for selected custom forms.

A30808-X3079-A272-2-7619 51
UMN:BCT - Operation Operation
Personal Computer

Display detailed
results

Fig. 2.62 Form Analyzer Report

Fig. 2.63 Form Analyzer Details

The following example shows the detailed report for inconsistent custom forms:

52 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

The detailed report gives

hints for removing incon-
sistencies.

Fig. 2.64 Example of detailed report for inconsistent custom form

Click Close to close the application.

Before the application is closed, the

user has the option of saving the
results.

Fig. 2.65 Form Analyzer end window

Any discrepancies must then be corrected manually by the user on the basis of the anal-
ysis report.

A30808-X3079-A272-2-7619 53
UMN:BCT - Operation Operation
Personal Computer

2.15 Interactive Document Browser

Acrobat Reader is supplied on the same CD as the online documentation and must be
installed according to the instructions on the inside of the CD cover. When Acrobat
Reader has been installed on the PC, start it by clicking on the Interactive Browser icon.
When Acrobat Reader is clicked on, the file _startup.pdf must started manually the CD.
This lists the documentation on the CD. Online manuals can be accessed from this list.

Fig. 2.66 Interactive document browser with procedure loaded

MML commands (written in blue and underlined in green) can be loaded directly from
the online documentation to the Command Assistant and then sent to the CP. To do this,
click on the appropriate icon or activate the menu item Plug-Ins -> Change Link. If the
link to the Command Assistant is not activated, the command goes to the CML instead
of invoking the Command Assistant.

Click on this icon to load MML commands

directly from the online documentation to
the Command Assistant, in order to have
them sent to the CP

Fig. 2.67 Connecting the interactive document browser

54 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

2.16 Command Files

Under the Task -> Add -> Command Files branch, users can add their own command
files to the menu tree.

First, create directories

(e.g. version-related name)
under which the command
files can be added

Fig. 2.68 Menu tree (command files)

To do this, the open the Task menu and click on Add -> Command File... .

Enter a name in the Add Command File

mask under Description.

The command file is stored under this

name in the menu tree
.
Now switch to Command File, select the
command file using the Browse button,
and confirm it with OK.

The command file is created with the

parameters under menu branch Command
Files.

If necessary, the command file can now be

moved to a different directory.

To do this, select the command file, press

and hold the left mouse button, and then
drag the command file to a different direc-
tory and release the mouse button.

Fig. 2.69 Setting up a command file in the Task Tree

A30808-X3079-A272-2-7619 55
UMN:BCT - Operation Operation
Personal Computer

2.17 Scenarios
Under the Task -> Add -> Scenarios branch, users can add their own scenario files to
the menu tree.

First, create directories

under which the scenario
files can be added

Fig. 2.70 Menu tree (scenario files)

To do this, the open the Task menu and click on Add -> Scenario... .

Enter a name in the Add Scenario mask

under Description.

The scenario is stored under this name in

the menu tree
.
Now switch to Scenario File, select the
scenario file using the Browse button, and
confirm it with OK.

The scenario is created with the parame-

ters under menu branch Scenario.

If necessary, the scenario can now be

moved to a different directory.

To do this, select the scenario, press and

hold the left mouse button, and then drag
the scenario to a different directory and
release the mouse button.

Fig. 2.71 Setting up a scenario in the Task Tree

56 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

2.18 Private Tasks

Under Private Tasks, users can add programs to their menu tree (e.g. text editors,
backup programs, etc.).

Private applications of a BCT

user

Fig. 2.72 Menu tree (Private Tasks)

To do this, select Task in the menu bar and click on Add Private Task....

In the Add Private Task mask, enter a

name under Description.

The program is stored under this name in

the menu tree (e.g. text editor).

Switch to Command Line, select the

program with the Browse button and
confirm it with OK.

Then confirm the Add Private Task mask

with OK.

The program is created with the parame-

ters under the menu branch Private Task.

Fig. 2.73 Private task

A30808-X3079-A272-2-7619 57
UMN:BCT - Operation Operation
Personal Computer

58 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

3 The Log Function in BCT

PCs used as a BCT keep log files for a wide variety of applications. The general log file
is for alarms from the EWSD network element. In addition to this there are log files for
the various BCT applications that can be created for each user.
The number of log files saved on the PC depends on the size of the log files assigned
by the BCT administrator. An approximate guide is the set size of the log file, e.g. 8 MB
/ 1.37 MB (rounded up) = 6 log files for each BCT application (e.g. for Command Assis-
tant).
Set size of the log file
8 MB
e.g. 8 MB for the
alarm log file 1.37 MB The set size of the log file
is divided by the
1.37 MB
predefined value 1.37 MB.
1.37 MB This has the advantage
that the log files can be
1.37 MB saved on disk.
The result gives the
1.37 MB
number of log files for an
1.37 MB application. In this
example: 8/1.37~6.

Fig. 3.1 Log file

The log files are arranged cyclically, i.e. when the last log file of a BCT application is full,
the first log file is overwritten again. However, the user is warned before this happens.
The administrator defines the path under which the log files are stored. The log files that
are generated can be read with any text editor.
al_1997-07-12_233456.log

xx...xx_yyyy-mm-dd_hhmmss.log

Prefix Year Month Day Hour Minute Second

Date and time of generation of the log file

Fig. 3.2 Naming conventions for log files

For example, the log file of the BCT application Command Assistant, which logs the
dialog between the EWSD network element and the Command Assistant application,
has the following name:

A30808-X3079-A272-2-7619 59
UMN:BCT - Operation Operation
Personal Computer

x:\Program Files\Siemens\BCT\UserLog\Schmidt\CA_1997-07-25_094559.log for the

first log file
x:\Program Files\Siemens\BCT\UserLog\Schmidt\CA_1997-07-25_101348.log for the
second log file, etc.
x:\Program Files\Siemens\BCT\UserLog\Schmidt\ is the backup path defined by the
system, and CA_1997-07-25_094559.log (serial) is the log file.
For information on the settings, look in BCT Info. The backup paths and the prefixes of
the log files are stored in BCT Info.

3.1 Application- and User-specific Log Files

When a user sends MML commands to the EWSD network element and executes them
via the Command Assistant, Command File Executor etc., the commands and the
network element’s reactions are stored in an application-specific log file. The adminis-
trator can assign these application-specific log files to each user, i.e. log files for appli-
cations are also user-specific.
If the default settings were used when the files were created, the log files are stored
under x:\Program Files\Siemens\BCT\UserLog\ (x=drive). The log files have the prefix
BMML_, CA_, CFE_ or SA_ and end with .log (e.g. CA_1997_06_09_114035.log =
<prefix>_<date = year_month_day>_<time = hour minute second>). Use any text editor
to read the log files.

3.2 Alarm Log Files

All reports from the EWSD network element that are not a direct reaction to a command
are stored in the alarm log file. This applies even if the user is not logged into an EWSD
network element. The alarm log file is a general log file; it is not created on a user-
specific basis.
If the standard installation path for BCT was used, the alarm log file is stored under
x:\Program Files\Siemens\BCT\AlarmLog\ (x=drive). The alarm log file has the prefix al
and ends with .log (e.g. al_1997_06_09_114035.log = <prefix>_<date =
year_month_day>_<time = hour minute second>). The alarm log file can be read with
any text editor.

3.3 Event Viewer

Fig. 3.3 Event Viewer icon

Display of system events.

The event viewer helps the administrator to monitor events in the BCT. It displays logs
for system, security and application events. For further information, refer to the Windows
NT Online Help. The Event Viewer is called via the menu Start -> Programs -> Admin-
istrator Tools -> Event Viewer.

60 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

4 Trace Configuration
The BCT Trace function is provided for problem and error analysis in BCT. When neces-
sary, select the BCT components on which information is required and start the trace
process. Only activate the tracer for diagnostic information in the event of an error.
Start and execute BCT Trace via the file manager under the path
x:\Program Files\Siemens\Bct\BCTExecutables (x = BCT VC2 installation drive), file
traceconfig.exe.

The functions provided by Trace Configuration are:

– trace start/stop
– selection of BCT component(s) to be traced, including background processes
– selection of SW modules to be traced in the relevant BCT component
– definition of the trace levels to be logged
– view of the log file

The trace runs until it is stopped with Trace -> Stop (button or menu item). Forward the
log file to Service for analysis.
When Trace Configuration is selected, the BCT Components box appears in the
window. Select the individual components from this list. A double click on a selected
component initializes the Trace Settings for Alarm Handler window. The components
and modules for the trace are selected in this window (default setting “All” for compo-
nents and modules).
Partially qualified inputs are possible, and the selection can be modified. Selected
components can be unmarked and removed from the list.
Do not change the default value for trace level. This value decreases or increases the
tracing levels. This means that each message received by the tracer has a certain
priority. A message with a higher priority than that set under Level will not be saved in
the trace log.
Activate the tracer with the Trace -> Start button or menu item. The trace configuration
cannot be modified until the trace funcion has been stopped.
The Trace presettings remain intact when the Trace window is closed and are available
again when the Trace window is re-opened.
The Trace window cannot be started several times simultaneously.
For detailed information on the Trace window, refer to the Online Help.

A30808-X3079-A272-2-7619 61
UMN:BCT - Operation Operation
Personal Computer

To select or deactivate
components, open the
selection window with a
double click

Fig. 4.1 BCT Tracer

To view the trace log file (Tracelog.txt) click on the relevant icon or select menu item
View -> Trace File.... This log file contains the selected BCT components listed
according to time. If a new trace is started, the information in the file Tracelog.txt is
added. If an empty file is required for a new trace, the file Tracelog.txt can be renamed
or deleted. BCT Trace then automatically creates a new file with the name Tracelog.txt
under the BCT directory \TRACE.

62 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

selected BCT components

Level of Tracing 1-100

information

Fig. 4.2 Display of a tracer log file

i File analysis is done by a system specialist.

A30808-X3079-A272-2-7619 63
UMN:BCT - Operation Operation
Personal Computer

64 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

5 BCT Help

5.1 General Help

General help on the BCT software is available in the BCT Help window of program group
BCT and gives a brief explanation of all the BCT applications. For further information on
Help, refer to UMN:BCT Register Introduction.
To open the BCT Help window, double-click the BCT Help icon.

Fig. 5.1 BCT window with the BCT Help icon

A window opens with the tabbed pages Contents, Index and Find.

The tabbed pages offer the

following items:

Contents:
A list of all BCT help topics

Index:
A subject-oriented search

Find:
A method for finding terms in
an alphabetical list

Fig. 5.2 Help Topics: BCT Help window

A30808-X3079-A272-2-7619 65
UMN:BCT - Operation Operation
Personal Computer

5.2 Information Code

If an information code is displayed on the PC, it usually means a warning or a fault in
the BCT (e.g. faulty link to the CP). An information code displayed during operation can
be interpreted with the aid of BCT Help. When BCT Help is opened up, the menu item
Troubleshooting -> Information Code provides information on the type and cause of
the problem, as well as hints on what steps to take. In most cases, however, an admin-
istrator should be called on to deal with the problem.

Go into BCT Help.

Under Trouble shooting, open the Infor-
mation codes page and access the infor-
mation in Help by entering the first letter of
the information code number.

Fig. 5.3 Window with information code display

66 A30808-X3079-A272-2-7619
Operation UMN:BCT - Operation
Personal Computer

5.3 Troubleshooting
If problems occur during operation of BCT, BCT Help offers assistance. After calling up
BCT Help the next step is to select the Find page and enter a keyword. In this example,
the user is looking for information on connections. The Help pages containing the
keyword are then displayed. To open pages, select them and then click on the Display
button. When the correct page is selected, information on the nature of the error and
corrective action is presented. In most cases, however, an administrator should be
called on to deal with the problem.

Fig. 5.4 Troubleshooting

A30808-X3079-A272-2-7619 67
UMN:BCT - Operation Operation
Personal Computer

6 Abbreviations

68 A30808-X3079-A272-2-7619