Professional Documents
Culture Documents
E WinFIOL 6 4 Users Guide
E WinFIOL 6 4 Users Guide
USER GUIDE 1 ( 87 )
Prepared (also subject responsible if other) No
WinFIOL 6.4
User’s Guide
Copyright
Disclaimer
All rights reserved, including those to reproduce this publication or parts thereof
in any form without permission in writing from Ericsson AB.
Contents Page
1 Introduction . .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 3
1.1 WinFIOL Overview .. .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 3
1.2 Differences Between Windows and Unix Solaris Versions . ... .. ... .. ... ... .. 3
1.3 What’s New .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 4
1.4 Prerequisites . .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 5
2 Installation, Start and Exit . ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 6
2.1 Windows Version of WinFIOL ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 6
2.2 WinFIOL/U ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 9
3 Crash Course . ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 11
3.1 Introduction .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 11
3.2 Create a Channel ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 11
3.3 Connect to an Exchange .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 14
3.4 Send MML Commands .. .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 16
3.5 Close a Channel . ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 17
4 WinFIOL User Interface .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 18
4.1 Introduction .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 18
4.2 Main Window .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 18
4.3 Editor . .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 23
5 Channels . ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 28
5.1 Introduction .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 28
5.2 Channel Basics ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 28
5.3 Channel Tasks . ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 32
5.4 Channel Properties . .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 38
A4 XSEIF R3
E Open
USER GUIDE 2 ( 87 )
Prepared (also subject responsible if other) No
6 Command Handling . ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 47
6.1 Introduction .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 47
6.2 Transmission handling ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 47
6.3 Error Handling . ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 53
6.4 Messages . ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 53
6.5 Scheduler . ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 55
6.6 Dangerous Commands .. .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 58
7 Monitoring Module .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 61
7.1 Introduction .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 61
7.2 Configuration .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 61
8 Effective Use . ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 64
8.1 Introduction .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 64
8.2 Script Commands ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 64
8.3 Macros . ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 65
8.4 Phone Book .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 65
9 Browsers . ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 67
9.1 Introduction . .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 67
9.2 Usage .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 67
10 CommandForm . ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 72
10.1 Introduction .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 72
10.2 Prerequisites . .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 72
10.3 Start and Exit .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 72
10.4 CommandForm Interface .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 72
10.5 Use CommandForm .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 73
11 COM — OLE Automation ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 77
11.1 WinFIOL and COM . .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 77
11.2 COM versus DDE ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 77
11.3 Developing a COM Application .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 77
12 LDAP Client . .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 78
13 Secure TCP/IP Connection (SSH) . .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 81
13.1 Introduction .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 81
13.2 Encryption ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 81
13.3 User Keys . ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 82
13.4 Authentication . ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 84
14 Get Help .. ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 86
14.1 Online Help .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 86
14.2 Product Support .. ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 86
15 Glossary .. ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. 87
E Open
USER GUIDE 3 ( 87 )
Prepared (also subject responsible if other) No
1 Introduction
WinFIOL 6.4 is available both for 32-bit Windows and UNIX Solaris. The Solaris
version of WinFIOL is called WinFIOL/U 6.4. Typically this User’s Guide applies
to both WinFIOL and WinFIOL/U unless stated otherwise.
• Prerequisites: section 1.4.1 for Windows version, section 1.4.2 below for
WinFIOL/U (Unix Solaris version).
• Installation, start and exit: section 2.1 for Windows version, section 2.2
for WinFIOL/U.
• Protocols: The Secure Shell (SSH) protocol (see section 13) is only
available in the Windows version.
• ToolTip: The short floating help text is only available in the Windows
version.
E Open
USER GUIDE 4 ( 87 )
Prepared (also subject responsible if other) No
The user’s password is now retrieved from TSS and used when connecting
via target driver OSS(TGW).
Passwords are now hidden from view when given in the channel window.
See further chapter 5.4.3.1.
A new target type has been added which supports more generic hosts,
such as, for example, Unix and Windows telnet hosts.
WinFIOL supports access to all APG40 nodes from the same channel
window. See further chapter 5.3.1.
• Improved scheduler.
A number of new script commands has been added that simplifies printout
parsing, file retreival via http or ftp and APG40 node access.
See further the topic External Script Commands in the online help.
The Target Manager dialog now supports user created folders for channel
files. Creating of new channels has been simplified.
It is now possible to create a user defined structure from inside the Target
Manager to store channel files.
Scripts that simplify the transfer of STS data from IOG11/20 to APG40
has been included.
E Open
USER GUIDE 5 ( 87 )
Prepared (also subject responsible if other) No
1.4 Prerequisites
• Required memory
• Required memory: 32 MB
• Color monitor
E Open
USER GUIDE 6 ( 87 )
Prepared (also subject responsible if other) No
If it does not start automatically, select Add/Remove Programs from the Control
Panel and press the Install button in the following dialog box. Press Next to
search for the installation program and Finish when setup.exe is found.
Press the Next button to acknowledge the selections made in a dialog box and
the Back button to return to the previous page to change any options.
The installation process is quite simple. By default, the installation program will
install WinFIOL in its entirety. To install it without one of the utilities, uncheck
the appropriate checkboxes while installing WinFIOL (seefigure 1 ).
• Monitoring Module
• Script Module
• Command Form
• Supported Protocols:
− RS232 (serial)
− Modem (telephony)
− TCP/IP (telnet)
IOG3 settings are offered for legacy reasons and may be used "as is".
− MD110
− Eripax
− OSS (AXE)
− OSS (TGW)
− Generic
− DocView
− DynaText
− KRSWin
The KRSWin browser support is offered for legacy reasons and may
be used "as is".
You can select the directory where WinFIOL will be installed. The installation
program automatically creates additional sub-directories to this directory for
command files, channel files, macros, and message files.
2.1.3 Uninstall
To uninstall WinFIOL, select Add/Remove Programs from the Windows control
panel and select Element Management WinFIOL.
2.1.4 Start
The installation program will by default create a folder named Element
Management in the Start menu. To start WinFIOL, find the menu item named
WinFIOL and select it.
You can also start WinFIOL from the command line. For information on
command line options, see "Start options" in WinFIOL’s online help. For more
start options, select Options | Preferences | Session.
Note Even if the display settings are reachable from the menu
Options | Preferences | Appearance by selecting the Display
Properties button, it is not recommended to change the
resolution or color depth while WinFIOL is running.
E Open
USER GUIDE 9 ( 87 )
Prepared (also subject responsible if other) No
2.1.5 Exit
To exit WinFIOL, select Channel | Exit or type Alt+F4. If you want WinFIOL to
ask you to confirm before exiting, select Options | Preferences | Session and
check the appropriate box.
2.2 WinFIOL/U
2.2.1 Install
The WinFIOL/U installation package comes as a compressed tar file.
A WinFIOL directory is now created into the current directory. Now the
$WINFIOLHOME environment variable has to be set. It can be done in two
ways:
• Set it in the winfiol script, which is found in the directory you have just
created. The script is self-explanatory.
• Set it externally:
2.2.2 Uninstall
WinFIOL/U can be uninstalled by removing the WinFIOL installation directory:
/bin/rm -r ~/.winfiol
Warning: All user-specific channel files and data are deleted when the .winfiol
directory is deleted.
E Open
USER GUIDE 10 ( 87 )
Prepared (also subject responsible if other) No
2.2.3 Start
Type the following, which starts WinFIOL as a background job by default,
so that you will get the prompt back.
winfiol
2.2.4 Exit
To exit WinFIOL, select Channel | Exit or type Alt+F4.
E Open
USER GUIDE 11 ( 87 )
Prepared (also subject responsible if other) No
3 Crash Course
3.1 Introduction
The purpose of this section is to break the ice between you and WinFIOL and
introduce the most basic functions. You will go through a simple step-by-step
course during which you will create a new channel with a connection to an
exchange, associate a command file to this channel, send a few commands to
the exchange, and then close the channel.
Before you can connect to an exchange, you should have some basic
information about the connection to the exchange and the exchange type.
For instance, some parts of the course require that you are familiar with the
connection protocol.
WinFIOL/U users will see slight differences in the appearance of the WinFIOL
windows comparing to the pictures in this document. This is due to platform
differences.
We assume that you have installed WinFIOL and have started WinFIOL for
the first time (see section 2).
Open the Target Manager by selecting Open from the Channel menu or by
pressing the F9 key. The Target manager dialog box opens with one or more
pages (more information in section 5.3.1). Now we are going to open a channel.
E Open
USER GUIDE 13 ( 87 )
Prepared (also subject responsible if other) No
Create a new channel from the My Channels page by pressing the New...
button or by selecting New... from the popup menu.
E Open
USER GUIDE 14 ( 87 )
Prepared (also subject responsible if other) No
The Channel properties dialog box appears in which you can define all
channel-dependent settings. (You can activate this dialog box any time later as
well.). Type the name of the new channel or accept the suggested channel
name. Then select the Properties button. From the tree on the left of the
dialog, select Protocol. The protocol page contains a combo box from which
you can select the desired communication protocol. Depending on the selected
protocol, the tree shows some additional pages under Protocol, for example
Setup. Activate these pages to configure the communication protocol.
When the protocol has been configured, activate the Target page and select
the desired target from the combo box.
When this is done, select OK in the Channel properties dialog box, and
then Open in the Target manager dialog box. If anything is still incorrectly
configured, WinFIOL will warn you and suggest changing the configuration
from the Channel properties dialog box. You can always activate the Channel
properties yourself to change any channel settings (see section 5.4).
Assuming that you were successful in completing the previous steps, WinFIOL
now has the data necessary for physically connecting to an exchange. You can
thus make a connection in AXE and MD110 terms. Select a paragraph from
the following that suits your situation.
E Open
USER GUIDE 15 ( 87 )
Prepared (also subject responsible if other) No
Press F5 (or select the Connect button). If you have a functioning connection
with an exchange, it should automatically establish contact.
We now create an entry in the phone book and dial the number of an exchange.
1. Open the phone book by pressing the Phone Book button on the button
bar or from the Run | Phone book menu option.
E Open
USER GUIDE 16 ( 87 )
Prepared (also subject responsible if other) No
3. In the smaller text field, enter the phone number to use and in the larger
field a brief description of the connection. Click OK.
4. Click on the new entry and press the Dial button. This activates the dialling
sequence defined in the Channel | Properties dialog box. If the modem
cannot make a connection, recheck these options.
5. Press F5.
Once you have reached the target exchange, WinFIOL should find an AXE
prompt and change from a telnet terminal into an MML command handler
(see section 6).
Note that this protocol is only available in the Windows version of WinFIOL.
Simply press the Command file window button on the button bar or select File
| New from the menu bar. This creates a command file that is automatically
associated with the active channel.
Type in a few MML commands into the command file window. Here is an
example of a very simple command file (AXE):
E Open
USER GUIDE 17 ( 87 )
Prepared (also subject responsible if other) No
dpwsp;
plldp;
exrpp:rp=all;
You can save this file for later use with the Save button on the button bar
or from File | Save menu.
3.4.2.2 Send
With mouse or keys, select the area you want to send in the command file
window. Now press F4. WinFIOL starts to send the MML commands one
by one and shows you the progress of the transmission in the Transmission
dialog box. If any of the commands are faulty and not accepted by the target
exchange, the transmission is paused and you can correct the MML commands
(see section 6.3).
You can also send a whole command file without opening it into a command
file window first. To do so, press F2 in the active channel file or select Run |
Transmit File menu. Choose a file and select OK.
Once you have finished sending and receiving data with the exchange you
can close the communication channel. A channel can be closed by closing
the channel window, by Ctrl+F4 or from the Channel | Close menu. Closing a
channel needs a confirmation from you when:
1. transmission is ongoing,
4.1 Introduction
The WinFIOL user interface resembles those of many other modern Windows
applications. This section provides guidance on the most important aspects of
the WinFIOL interface.
The WinFIOL desktop consists of a set of different windows. The main window
constitutes the core of the program from which all functions and options can be
accessed and additional document windows, such as channel windows and
command file windows, can be opened. Every document window has a context
sensitive pop-up menu that can be activated with the right mouse button or
Shift+F10. These pop-up menus are not user-configurable.
When the target exchange is OSS (TGW), the pop-up menu of the input and
output windows shows an extra option: Log Off. Selecting the Log Off option
causes all channels towards that exchange to be logged off and disconnected.
The main window contains a menu bar, one or more toolbars (button bar)
and, at the bottom, a status line. Multiple document windows can be opened
in the main window.
From the menu bar, all functions within WinFIOL can be accessed.
The File menu always applies to the currently active window. If you want to
open an existing command file, when you have only for example the scheduler
window opened, choose File | Open File.
While other pull-down menu options are fixed, the Tools menu has a
configurable part which can be modified from the Options | Preferences |
Tools menu. Click the Add button and fill in the name for the menu option,
path for the program, the working directory of the program and the text for the
status line in the Hint field.
When activating programs from the Tools menu, you can from the advanced
options prevent WinFIOL from opening a new instance of a program already
running. See the help system for more information.
• Macros
• Script commands
• Separators
When starting WinFIOL for the first time, you will notice:
• Windows version: - that two menu items already exist in the user
configurable area of the Tools menu: DOS session and Calculator.
• WinFIOL/U: - that five menu items already exist in the user configurable
area of the Tools menu: Undress, Capitals, Script Check, Hex
Converter and Macro.
The toolbars are placed in the order that the checkboxes are selected. If you
want to change the order, deselect all the checkboxes and then select them
again in the order you want.
In this mode the buttons can be dragged and dropped directly to the wanted
toolbar, or they can be removed by dragging them away (until an "x" appears).
Each custom defined button can have a bitmap icon or hot key associated with
it when it is created or modified. Default buttons cannot be modified.
All the buttons are exclusively mouse-controlled. When the mouse pointer
is moved over a button, a ToolTip (short floating help text) is shown. At the
same time, a longer help text is shown on the status line at the bottom left
of the main window.
Note that user defined buttons may be corrupted when changing the resolution
or color depth of the display while WinFIOL is running. It is therefore
recommended that you exit WinFIOL before changing display settings.
Note User defined buttons is not fully supported in the UNIX version
of WinFIOL. Buttons can be dropped onto a toolbar, but not
dragged away from or moved once they have been dropped.
E Open
USER GUIDE 22 ( 87 )
Prepared (also subject responsible if other) No
The status line at the bottom of the main window displays information
depending on the active document window. When the mouse pointer is over
a button on the button bar or menu item the status line instead shows help
information for that button or menu item.
Here is the information shown on the status line from left to right for a particular
document window.
4.2.4.1 Input Window
• 2:1 (Row and line position of text cursor)
The rightmost field of the status line shows the F1 function key for accessing
the help system.
Two fields on the status line can be clicked with the mouse in order to change
the option shown in the field. These are the Insert/Overtype editor input mode
and channel mode (TTY/Setup/Buffered).
4.3 Editor
WinFIOL has a built-in editor specially designed for editing exchange data.
Many of the editor functions should be familiar to an experienced Windows
user. There are a few other functions, such as syntax highlighting, square
blocks and hex/decimal converter that are useful when handling commands
or data received from the exchange.
The command file window and input window contain an editor. In the input
window, the editor is line oriented and supports neither undo nor any function
for merging or deleting lines. In this section, editor window is used to denote a
command file window or an input window.
There are a few options that change the characteristics of the editor. These
options can be found in the Options | Preferences | Editor menu.
The editor supports tabs. By default, the tab position is four, but can be
changed from the Options | Preferences | Appearance menu. If a line
containing tabs is transmitted, all tabs are automatically replaced by spaces.
4.3.1.2 Selections
Standard Windows selecting functions such as cut, copy and paste apply also
in WinFIOL. In addition, there is a hot key (Ctrl+A) for selecting all text in a
command file window and another (Ctrl+B) for selecting text from the cursor
position onward. The latter is useful when data is to be transmitted from the
cursor until the end of the file.
E Open
USER GUIDE 24 ( 87 )
Prepared (also subject responsible if other) No
It is also possible for you to choose one of three different modes for handling
selected areas:
• Volatile, where selected text is unselected when any cursor key is pressed
and deleted when text is inserted.
• Normal, where selected text is unselected when any cursor key is pressed
but is not deleted when inserting text.
• Persistent, where selected text is neither unselected nor deleted when any
cursor key is pressed or text inserted.
Select the mode you prefer from the Options | Preferences | Editor menu.
The cut, copy, paste and delete functions found in the Edit menu work just like
in any other editor. In addition, selected text can be exported to a file from
the Block | Write Block menu. Text can also be imported from the Block |
Import Block menu.
Note that when pasting to the input window of a channel window, only the first
line is pasted even if more than one line is copied.
Find and replace can be effected with a set of options found in the Replace
dialog box. The options are:
• Case sensitive: under this option lower and upper case items are matched:
the word "AXE" is not found if "axe" is searched for.
• Whole words only: under this option only whole words are considered: the
word "AXE" is not found if "AX" is searched for.
• Origin: this option determines whether the search starts from the beginning
of the document or from the cursor location.
The Replace dialog box has an additional field called New text in which the
text to replace the search string is typed. It also has an option called Method
for replacing search strings with or without confirmation. Pressing the Replace
all button activates a global search for the string to be replaced in the whole
document.
4.3.1.4 Undo and Redo
Any cursor movement, insertion and deletion of text can be undone except in
the input window. You can define the number of actions that can be undone
from Options | Preferences | Editor menu. This number is set to 100 by
default. Undo does not work after Undress and Capital conversion.
4.3.3 Bookmarks
Bookmarks provide fast access to a specific position in a document window.
Bookmarks ranging from 1 to 9 can be set anywhere in command file windows,
input windows or output windows with a hot key (Alt + bookmark number) or
from the Bookmarks dialog box accessed from Search | Bookmarks. You
can take the cursor to a bookmark position with a hot key (Ctrl + bookmark
number) or from the Bookmarks dialog box with the Goto button.
With a the Hex convert dialog box numbers can be converted between decimal
- hexadecimal - binary - ASCII. The largest number the converter can handle is
32
2 –1. The converter is activated from the Tools | Hex convert menu or with
Ctrl+H. The converter then reads the next digits or character at the position
of the text cursor into the dialog box and shows the conversion results. The
Apply button converts a selected decimal number in the document to the
corresponding hexadecimal value.
4.3.4.3 Undress
The undress tool accessible from the Tools menu lets you go through a
selection of text or a whole text document and cut out the unwanted characters
or lines. There are several options in text undress.
The Additional lines starting with option lets you delete any lines starting
with a certain character. You can also define whether to delete lines where
there are spaces before the defined characters. This is the Must start at
first position option.
5 Channels
5.1 Introduction
In the channel properties, there are a variety of options ranging from the
channel name to more complicated ones, such as "maximum number of DDE
clients allowed". This is why channel handling was designed to meet the
requirements of all from novice to expert users. Any user can create a channel
defining only a few major options, whereas an expert might want to optimize
channel performance through fine-tuning. All functions can be controlled from a
single dialog box, thus channel handling is fast and easy (see section 5.4).
In the TTY mode, even if the input window is active, the text cursor is shown in
the output window just after the data that is last received.
For more information about input window and related topics, please refer to
the help system.
E Open
USER GUIDE 30 ( 87 )
Prepared (also subject responsible if other) No
As mentioned before, even if the input window is active, in TTY mode the text
cursor marks the data last received in the output window.
The fact that a target exchange prompt does not have to be received is
handy when logging on to UNIX or any other system utilizing e.g. the TCP/IP
telnet protocol, before the target exchange is accessed. The channel mode
automatically changes to buffered mode when the target exchange prompt is
received. Also, in the Channel Properties | Protocol | Mode dialog box, you
can define a string of characters that causes WinFIOL to automatically switch
from buffered to setup mode.
For example, when sharing a channel, the client application will lock the
channel if the option Lock the shared channel in the Channel sharing page
of the Preferences dialog box is set.
• Channel properties
• Channel mode
• Channel queue
• Sharing a channel
This feature is useful if you normally work with WinFIOL and temporarily want
to use another OPTool for a specialized task using the same channel.
• Define the tool that should be allowed to share the WinFIOL channel by
opening the WinFIOL plug-in configuration utility from the Start menu
and then select WinFIOL | Channel sharing. Then select Add and browse
for OPTool’s executable. Name shows the tool name and Application
shows the path to the executable file. Command line parameters to the tool
can be defined if needed.
To open a new channel, select Channel | Open. From the Network page of
the Target manager you can open a channel to an exchange that is managed
centrally, for example when using TMOS. The Network page is only available
when the so-called LDAP server connection or channel pool directory is defined
(see section 12 for details).
Select a node from the "tree of exchanges", or simply type the first characters
of a known target exchange in the Search field. Whenever you have selected
a target exchange that is available (shown in green), press the Open button.
(There is no need to press the Properties button at this stage.) A channel to
the selected target exchange will automatically be opened.
Anew channel can also be created by right-clicking in the tree view and
selecting New | Channel.
Warning for WinFIOL/U users: Normally a green button indicates a free channel
and a yellow button indicates a busy channel. In WinFIOL/U however, there
is no distinction between yellow and green buttons in the "tree of exchanges"
in the Network page in the WinFIOL Target Manager. This means that a
user could try to open two channels windows to the same network element,
possibly causing unexpected behavior.
E Open
USER GUIDE 33 ( 87 )
Prepared (also subject responsible if other) No
Channels that are often used can be marked as being a Favorite. A favorite is
indicated by the F in the F-column. The channels can then be sorted according
to the F-column to list favorite channels first in the list See further WinFIOL’s
online help..
If desired the channels can be selected from a tree view. Check the Tree View
check box to view the tree.
E Open
USER GUIDE 34 ( 87 )
Prepared (also subject responsible if other) No
Using the tree view, it is possible to create own folders by right-clicking in the
tree view and selecting New | Folder. The channel files can be moved to
a new folder by using Drag n’ Drop.
This requires however that the target is set to APG40 and that the IP addresses
for the APG40 nodes have been defined in Channel | Properties | Protocol |
Setup.
You can also start WinFIOL with a so-called distinguished name on the
command line. The distinguished name is the name of an exchange in the
TMOS network. Provided that an LDAP connection exists (see section 12),
WinFIOL will open a channel to that exchange.
For more information on command line options, see "Start options" in the
online help system.
Each channel can have its own log file. A log file cannot be shared among two
or more channels. Similarly, one channel cannot have more than one log file.
Pressing F8, or selecting Log output... from the File menu, allows you to
define a new log file or close an open log file for the currently active channel. If
a log file is already open, it will be closed.
Every time you open a log file you are asked whether to append or overwrite
any existing log file. The overwrite option deletes the existing log file and starts
from scratch, whereas the append option keeps the previous data and writes
new data to the end of the log file.
Pressing Shift+F8 or holding down the Shift key and clicking the Log file
button on the button bar allows you to alternatively reopen the last log file used
or close the current log file for the currently active channel.
If you press the Shift+F8 or Shift+Log file button, the log file used will either
be appended or overwritten according to the Quick-open log file setting in the
Directories page of the Preferences dialog box (Options | Preferences).
Each channel can have its own log file. A log file cannot be shared among two
or more channels. Similarly, one channel cannot have more than one log file.
Before opening or closing a log file, activate the proper channel first.
Pressing Ctrl+F8, or selecting Log input... from the File menu, allows you
to define a new input log file or close an open log file for the currently active
channel. If a log file is already open, it will be closed.
Every time you open a log file you are asked whether to append or overwrite
any existing log file. The overwrite option deletes the existing log file and starts
from scratch, whereas the append option keeps the previous data and writes
new data to the end of the log file.
The daily log creates a new log file for each day starting at midnight. The
log files are named according to the date (format yyyymmdd) and the
channel number (#number), for example, 20020621#3.log. These files
can be quite large and take up a lot of disk space.
• Scheduler log:
The scheduler log creates a log file which is connected to a given job.
The log file is created when the job starts to execute and closed after
the job has finished.
This option is used for testing purposes when you want every character,
including control characters to be added to a log file. With this option you
can examine every data character sent and received for example when
connecting with a serial protocol or TCP/IP. This option only works in the
low security mode.
• Active Printouts:
With this function you can log only those printouts you define on the Active
printouts page in the Channel | Properties menu, under the Links option.
You can define multiple printouts to be logged and use wildcards in those
definitions. See the online help for more details. See also section 5.4.6.
• Error log:
With this function you can log only those commands and/or printouts that
result in an error when they are transmitted from a command file. Define
E Open
USER GUIDE 38 ( 87 )
Prepared (also subject responsible if other) No
the error log file on the Error log page in the Channel | Properties menu,
under the Links option.
Channel properties are handled from a single dialog box activated from
the Channel | Properties menu, pop-up menu of the channel window, the
Channel Properties button on the button bar or the Properties button in
the Target Manager.
There are many different settings that can be changed for each channel
separately. These settings are divided into groups according to function.
E Open
USER GUIDE 39 ( 87 )
Prepared (also subject responsible if other) No
5.4.1 General
Channel Name and Owner
You should give each channel a descriptive name and name yourself as the
channel owner.
5.4.2 Protocol
5.4.2.1 Communication protocol
The communication protocol determines the means of data transportation.
Depending on the selected protocol, the properties tree shows some additional
pages under Protocol, for example, Mode, Setup and Advanced. Activate
these pages to configure the communication protocol.
5.4.2.2 Mode
This option defines the initial channel mode that WinFIOL uses when starting a
new channel. In TTY mode each character is sent directly to the target, in setup
mode characters are sent when enter is pressed, in buffered mode characters
are sent when enter is pressed, but only if a prompt (see section 5.4.3) has
been received from the target, otherwise the command is queued.
If you want WinFIOL to automatically switch to the setup mode. For example,
every time a UNIX prompt is received, define the UNIX prompt here. Specify at
least the last part of the UNIX prompt.
5.4.2.3 Setup
Define destination options.
5.4.2.4 Login
Define login options.
Important: Do not enable the login dialog if automated login or logout in the
Login/logout portion of channel properties is enabled.
Also note that login dialog is mandatory for OSS (TGW) target, and therefore
cannot be changed here.
5.4.2.5 Advanced
Define advanced telnet options.
5.4.2.6 Encryption
Define SSH Encryption options. See section 13.2.
5.4.2.8 Authentication
Define SSH Authentication options. See section 13.4.
E Open
USER GUIDE 40 ( 87 )
Prepared (also subject responsible if other) No
5.4.3 Target
In the Target options, you can select the target system and modify the
target-exchange-dependent control characters (such as send, release, connect
and break characters) and prompts. Selecting a target exchange affects the
control characters as well as default lists with prompts. These values are
initially defined by the type of the selected target exchange. You can restore the
default values at any time.
Here you can also select the translation file. A translation file changes received
characters into another characters. This is useful in sending and receiving 7-bit
data including special characters like å, ä and ö. Currently, translation files are
supplied with a country-specific character set for Denmark, Finland, France,
Hungary, Norway, Spain and Sweden.
Prompts for detecting passwords and failed login attempts can also be defined.
This is valid for the Windows version only.
To open a script, or save a script to a file, use the buttons to the right of the list
view. To read a script from a file while logging in or out, check the checkbox
E Open
USER GUIDE 43 ( 87 )
Prepared (also subject responsible if other) No
Use script file. If the check box is unchecked, the script is saved and read
from the channel properties.
Writing a login script: To begin writing a login script, make a manual connection
and note the prompts and responses that are needed. Fill in the same prompts
and responses in the script. Only the first few characters in each prompt
may be necessary. For example, the script prompt "User" will match both
"Username:" and "Userid" on the exchange.
The prompts have to have the right case, since the automated login/logout is
case-sensitive.
The responses can be hidden: when adding a line to the script, check the Hide
response checkbox. This means that the response is not written to the file in
plain text and is filtered out from any data that is echoed while the automated
login/logout is in progress.
If a prompt is not matched, the next prompt in the script will be tried. This
makes it possible to respond to different prompts with the same script, for
example if prompts differ between connections. The last prompt in the script
must always be recognized.
Also note that automated login and logout has no effect on the OSS (TGW)
target, even if it is possible to configure.
5.4.4.2 Special Cases of Prompt Settings
An empty prompt will cause the automated login or logout to send the response
regardless of the context of the incoming prompt. This can be useful in two
cases:
• When logging out. Often there has to be some form of event that causes
the exchange to send a prompt to the user. Therefore a logout script often
begins with an empty prompt and a carriage return character.
Any control character can be sent as response with use of the "\" character
followed by the value of the control character. The value can consist of
maximum three numbers. Special cases:
Example: "\0971" in script sends "a1" (since 97 is the ASCII code for "a").
• leave the response field blank. Each character the user types will be
echoed to the screen.
The login script will start over if it detects a failed login.Prompts indicating a
login failure can be added in Channel | Properties | Target | Login failure
(available only in Windows), or in the file prompts.xml.
5.4.5 Browser
Here you can select the document browser to be used with WinFIOL.
A document browser uses books (or libraries). When a book is defined here,
every search request will tell the browser to use that book. If no book is
defined, the browser uses the default or the last used book. The selection of
the browser book overrides the book or document database that is used by
default (see section 9).
5.4.6 Logging
This page contains options for the different log files that can be enabled.
The Log raw received data option is used when you want every character,
including control characters, to be added to a log file. With this option you can
E Open
USER GUIDE 45 ( 87 )
Prepared (also subject responsible if other) No
examine every character sent and received for example when connecting with a
modem or TCP/IP. This option only works in the low security level.
For information on the Daily log file option, see section 5.3.2.3.
The node prefix can only be enabled for APG40 targets and insert a prefix
stating to which node the communication takes place.
5.4.7 Links
5.4.7.1 Links
This page contains options related to restoring window text, traffic options,
short commands, phone book and security.
The Preferences determine whether the text is saved in input and output
windows when closing the channel in order to restore all text. You can also
select whether all channels use the same traffic options or whether each
channel has its own set of options.
You can select the Short command file to be used for each channel. The short
commands are automatically loaded when a channel is opened.
The Phone book contains numbers to dial, macros to run or commands to send
in order to establish a connection with a target exchange. On this page you can
define the default Phone book list for the channel (see also section 8.4).
If necessary, you can define a High security level for a channel, making sure
that no data about the current connection, such as login names and TCP/IP
addresses, are stored in the channel file.
5.4.7.2 DDE
DDE is not supported by WinFIOL/U.
On this page, you can define the maximum number of DDE or COM clients to
be used with WinFIOL.
The options for locking the channel are Never, on Request from a client
and Always. When a channel is locked, no commands can be sent from
WinFIOL, except by a DDE client.
The dangerous commands are defined in a text file that is loaded when a
channel is opened. There are two types of dangerous command files: the
System list of dangerous commands, which is maintained by the system
administrator, and the Public list of dangerous commands, which can be
freely changed.
Options on this page let you define and view the dangerous commands file.
You can Add, Modify and Delete the commands and warnings in the public
command file.
The Active Printout function is part of a WinFIOL plug-in. If this plug-in is not
loaded, active printouts are not available.
5.4.8 Appearance
In appearance options, you can define a set of colors and fonts for each
channel and associated command file windows to override the normal color
and font settings. This is useful when multiple channels are opened.
You can select the name shown in the title bar for a channel window in the
Channel title from options. This channel title can be the channel name, the
name of the channel file, the configuration of the channel connection, the target
exchange header or the element name.
Maximum lines defines the maximum number of buffered lines in the input and
output windows. The largest available number is 100000 lines in the output
window and 200 lines in the input window. Note that a large value consumes
more memory.
The Filter option is used to automatically filter out AXE and MD110 headers
from the exchange printout. This means that they do not show up in the output
window, log file or printer (when connecting to the printer).
E Open
USER GUIDE 47 ( 87 )
Prepared (also subject responsible if other) No
6 Command Handling
6.1 Introduction
In this section, command handling is divided into the following categories:
• Error handling, which includes error detection, error correction and error
collection.
All of these categories have many configurable options allowing you full control
over command handling in WinFIOL.
An area can be selected quickly with two hot keys: Ctrl+A selects the whole
command file and Ctrl+B selects the area between the text cursor and the end
of the command file.
During active transmission, the text in the command file window cannot be
edited. During transmission pauses, text can be edited, but lines cannot be
added or deleted.
E Open
USER GUIDE 48 ( 87 )
Prepared (also subject responsible if other) No
6.2.2.3 File
An entire command file can be sent to the currently active channel without
opening the file first in a command file window (Run | Transmit File menu
or by pressing F2). It is possible to define the line of the file from which the
transmission is initiated. WinFIOL can automatically create a log file with the
same name as the command file to be transmitted but with the file extension
".log". WinFIOL can also be configured to write an error log of commands that
failed. For more information about log files, see section 5.3.2.
It is possible to load a file being transmitted into the command file window and
continue transmission from there. This process can be carried out without
suspending the transmission.
File transmission can also be initiated by dragging a file from the File Manager
or File Explorer and dropping it into a channel window. When a file is dropped,
a dialog box for selecting the initial line of transmission and creating a log
file appears.
6.2.2.4 Scheduler
WinFIOL has a built-in scheduler that allows you to schedule command files
for transmission some time in the future. All scheduled files are listed in the
Scheduler window (see section 6.6).
6.2.3 MMLSense
MMLSense is a feature of WinFIOL that helps you with MML commands by
presenting a list with all available MML commands. When the list is active, you
can type the first characters of a command or use the cursor keys or mouse to
select the command you need from the list that appears. By pressing Enter
the selected MML command is inserted in the text.
MMLSense works on the first part of an MML command (not on the parameter
part) and only if the documentation browser and library provide WinFIOL with a
list of available commands. The feature needs ALEX as documentation browser
together with an ALEX library that contains PCM files.
6.2.4 Destination
From a command file window, commands can be sent to only one channel at a
time. However, you can use the @CHANNEL script command in a command file
to change the target channel during transmission. This way you can send data
to multiple channels in one transmission.
If you set WinFIOL to pause at exchange errors, you can also define a set of
MML commands that do not pause the transmission even if an error occurs.
These errors can still be collected to the message window. The list of error
exceptions can be modified in a dialog box accessed with the Except button.
6.2.5.2 Breakpoints
You can make WinFIOL halt an ongoing transmission at a specified breakpoint
by using one of the following methods:
• RECEIVE: with this option checked, a transmission is halted when the text
specified in the dialog box is received from the target exchange.
• END OF FILE: with this option checked, a transmission is halted when the
end of a specified or any file is reached (useful for included files).
6.2.5.3 Flow
• Auto Confirm: with this option checked, WinFIOL automatically confirms
commands requiring a confirmation, defined for AXE as ";" and in MD110
as "Y;".
• Send comments: with this option checked, WinFIOL will also send lines
that start with comment ("!" for AXE, "/*" for MD110). You may want to
switch this option off to speed up transmission.
• Auto release: with this option, when commands are sent using F4,
WinFIOL releases the terminal in order to receive a delayed printout from
the exchange. Printouts like these appear after ordered commands and
cannot be received when the terminal is connected.
• Auto reconnect and Reconnect delay: with the Auto reconnect option
checked, when commands are sent using F4, WinFIOL waits for the end of
the ordered command printout before reconnecting the terminal. It is also
possible to define a delay between the end of the printout and reconnection
or to disable auto reconnect and still use the delay option.
• Auto re-enter sub-command mode: with this option checked, after the
delayed printout has been received, WinFIOL will automatically send the
entry command to enter sub-command mode again.
6.2.5.4 Other
The Other options allows you to define situations when WinFIOL should sound
a beep, whether to ignore script commands during command transmissions
and whether to ignore script variables included in script and MML commands.
The transmission status is also shown on the progress bar using the following
color codes:
The Transmission dialog box can be set to be always on top from the pop-up
menu accessible with the right mouse button, rendering it visible even if other
windows of WinFIOL are hidden.
The transmission can also be observed in the command file window, where
the line about to be transmitted can automatically be highlighted during
transmission. This Synchronize option can be switched on and off from the
Transmission dialog box.
E Open
USER GUIDE 53 ( 87 )
Prepared (also subject responsible if other) No
The exchange cannot be released during active transmission but only during
a pause. Any commands already in the queue will be sent first as soon as
transmission is paused and an exchange prompt received.
Every target exchange defines a set of error messages recognizes these errors
from the received exchange data and pauses the transmission allowing you
to make a correction during transmission. You can also instruct WinFIOL not
to pause on any error by unchecking all the possibilities in the Pause page of
the Traffic setup dialog box.
6.3.1 Correcting
If you want to correct any errors during transmission, make sure that the
Exchange errors option under Pause at is selected. With this option checked,
WinFIOL, after receiving a recognizable error string, halts the transmission to
allow you to correct the problem. WinFIOL highlights the line with the faulty
MML command in the command file window and marks it with bookmark zero.
You can now correct the MML command and resume transmission from the
same or any other line. The procedure to be followed here is exactly the same
as with manual pausing of transmission (see section 6.2.6).
6.4 Messages
• Start transmission
• End transmission
To make the messages easier to recognize, each message type has its own
icon.
Each message type also includes a set of attributes identifying, for example,
the cause of an error, date and time of the message and channel of origin
(see section 7).
The Types and Attributes pages include a number of check boxes with the
options already presented in section 6.4.2. Here you can select the message
types to be collected in the message window and the attributes to be included
in the messages.
6.5 Scheduler
WinFIOL has a built-in scheduler that allows you to schedule command files for
transmission some time in the future. With the scheduler you can define the
starting time and sending options for file transmission. The sceduled job can be
repeated a defined number of times or for ever. The output from the scheduled
jobs can optionally be logged to file. See chapter 5.3.2.1 and chapter 5.3.2.3.
The scheduler operates in the background.
There is only one scheduler window, and it is not associated with any particular
channel. The scheduler is always active, even when the scheduler window
is closed. A pop-up menu can be activated with the right mouse button or
Shift+F10, from which you can add and delete items.
• File: name of the file to be transmitted, or blank if the item type is Sleep
• Transmit: options defining what to do with items that are missed and
when the clock is adjusted.
E Open
USER GUIDE 57 ( 87 )
Prepared (also subject responsible if other) No
• Modify: You can edit the scheduler data of an existing command file, but
only if the file has not yet been transmitted.
• Add job: In the WinFIOL — Add job to scheduler dialog box you can
add a new file to be transmitted, the target channel, the start time and date
and the number of repetitions and the interval between repetitions.
• Add sleep: In the WinFIOL — Add sleep dialog box you can add a sleep
period, with start time, stop time and repetition, for one or all channels.
• Delete: You can delete one selected file from the scheduler window.
• Delete all: With this option, all scheduled files can be deleted from the
scheduler window list.
• Load Schedule: Load a saved file with all items in the scheduler list.
• General: defining name, file name, channel and start time for the
scheduled job.
• Repeat: options defining how many times the job should be repeated
and at what interval.
6.6.1 General
The Dangerous commands function gives a warning every time you send
an MML command that is classified as dangerous. The warning also shows
an explanation why the MML command is considered dangerous. You have
the possibility either to send the command or not to send it. The dangerous
commands file is activated from the Channel | Properties menu.
The dangerous commands file is a text file that is loaded every time a channel
is opened. It is possible to define two sets of dangerous commands (that is, two
separate files): a system file and a public file. The system file is maintained by
a system administrator and you cannot change it. The public file is for your
own use. The dangerous command function is activated from the Channel |
Properties menu. In the Dangerous commands window press the File button
to select a dangerous commands file to be used.
With the Show option, you can browse either the system or the public file.
In the public file, you can also Add, Delete and Modify the commands and
warnings.
E Open
USER GUIDE 60 ( 87 )
Prepared (also subject responsible if other) No
6.6.4 Warning
A warning is issued in a pop-up window every time a dangerous command
is being sent to the target system (see figure 29). The command can be
transmitted by pressing the Transmit button and rejected by pressing the
Reject button. By pressing the Documentation button, the command
description (COD) for the currently selected MML command will be shown. A
warning will not be shown when transmitting multiple commands, for example
from a command file window or a command file from disk.
7 Monitoring Module
The Monitoring module is not included in WinFIOL/U.
7.1 Introduction
The basic idea behind this tool is that it continuously monitors a target exchange
(during or without transmission). You can instruct the monitoring module to
perform a specific task every time a specific event occurs.
7.2 Configuration
7.2.1 Basics
The monitoring module does not have to be initialized in any way. It runs all the
time. However, if you have not defined any events that will trigger an action there
is no noticeable difference to running WinFIOL without the monitoring module.
In order to use the module you need to define one or more events and actions
to them from the Monitoring Module Configuration dialog box.
The highest level of the tree shows the channels that have events or actions
assigned to them. Events can be assigned to all channels. The next level
shows either the events or the actions assigned to a channel depending on
the View option. The lowest level shows the actions assigned to an event or
events assigned to an action.
7.2.3 Events
To create an event, click the New event button. This opens a new dialog box
for defining the channel to be monitored by the module. Notice that there is an
option to monitor all channels. Here you also define the event type.
Events are divided into six types presented in figure 32. Each of these event
categories includes a set of options and attributes specifying a single event.
These options and attributes are different for each event type. You can get
information on the options from the help system.
7.2.4 Actions
There are a number of possible actions that WinFIOL can take if a defined
event occurs. These options range from a simple system beep to an email
E Open
USER GUIDE 63 ( 87 )
Prepared (also subject responsible if other) No
You can obtain information on the options associated with actions from the
help system.
E Open
USER GUIDE 64 ( 87 )
Prepared (also subject responsible if other) No
8 Effective Use
8.1 Introduction
WinFIOL has many features designed to make working with exchanges easier,
including script commands, a macro command language, and a phone book.
By automating various frequent or complex tasks, they can be performed
much more efficiently.
You can get help on a specific script command by positioning the text cursor at
a script command and pressing Ctrl+F1.
Script commands are divided into two categories, internal and external script
commands.
These script commands are the same as in the old DOS FIOL program, with
the exception of @H, @N and @Z.
Errors can be normal syntax or typing errors if the checker does not recognize
the given script command or syntax of the command attributes. The syntax
E Open
USER GUIDE 65 ( 87 )
Prepared (also subject responsible if other) No
checker also checks any references to labels and variables and gives a
warning if the specified label or variable is not defined. The syntax checker
also locates defined labels and variables that are never used or referred to
and gives a warning.
8.3 Macros
A macro is a sequence of functions combined to form a single entity that can be
initiated with a single request. All the functions included in the macro will be
run in the order they are defined in the macro file. Unlike script commands, a
macro is run and not transmitted. Macros can also be run from command files.
WinFIOL has a macro language of its own for accessing various functions. A
macro can be written in any text editor and compiled by WinFIOL after being
loaded into a command file window from the Tools | Macro | Compile menu.
This creates a macro binary file with a name defined in the macro text file and
saves it in the macro directory. This directory is defined on the Options |
Preferences | Directories | Other page.
A running macro can be initiated from several places. You can create a user
button (see section 4.2.3) on the button bar or add an item to the Tools menu or
assign a hot key to a macro from the Options | Preferences | Tools | Buttons
menu. Furthermore, macros can be run with a script command, from the phone
book and from the WinFIOL command line when starting WinFIOL (see "Start
options" in the online help system).
You can select an entry and choose Dial straight from the phone book or just
type a number to dial. These require that the active channel window has a
protocol selected that supports dialling.
E Open
USER GUIDE 66 ( 87 )
Prepared (also subject responsible if other) No
The difference between these two lists is that, unlike list A macros, list B
macros can be run even if the channel in the active channel window is closed or
there are no channel windows open.
When the Run button is pressed, the selected macro will run in the active
channel window.
9 Browsers
9.1 Introduction
When using WinFIOL, you might want to get information about an MML
command or printout. You need a documentation database and a browser to
access such information. WinFIOL’s ability to interact with a documentation
browser enables you to easily obtain the required documentation from within
WinFIOL. A request starts or activates a documentation browser and the
correct document is retrieved to the browser window.
9.2 Usage
9.2.1 Supported Browsers
9.2.1.1 Windows Version
WinFIOL supports the following documentation browsers:
• ALEX (Active Library Explorer). Both remote and local ALEX are
supported. Browse document databases over a web connection as well as
local databases with the stand-alone version.
• DocView for Windows, which is the browser delivered with the older
WinFIOL 4.x packages. WinFIOL works with both 16-bit and 32-bit
versions of DocView for Windows.
• DynaText 2.3 and 3.1. See section 9.2.3 for instructions how to set up
DynaText support.
None of the browser applications are included in the WinFIOL and Tools
package.
9.2.1.2 WinFIOL/U
WinFIOL/U supports the following documentation browsers:
In the Windows version of WinFIOL, the channel property for Remote ALEX
browser setup has an advanced setup page, as seen in figure 34. The
proxy configuration is used by CommandForm when it locates the PCM files
necessary for building command trees.
• Direct connection. WinFIOL does not use a proxy server to fetch PCM
files for CommandForm from an ALEX database.
• Use Internet Explorer proxy settings. WinFIOL will use the same settings
for proxy server as Internet Explorer.
• Proxy server. Use Address and Port as the proxy server to reach the
ALEX database. Entries listed in No proxy for are bypassed, which means
that ALEX servers matching those addresses will be accessed directly
without the use of a proxy server. The bypass addresses can be entered
as wildcard addresses, for example 172.* or *.ericsson.se.
Collection (of books): Specify the location of the DynaText browser books. For
instance, for a CD-ROM in drive D:, specify D:\EDWLIB\COLL as the location
of the book collection. Note that the directory containing the book collection
always should have a sub-directory called BOOKS.
Open the Browser | Setup page for DynaText to define the following
information:
• DynaText location: Type the location of the DynaText package or use the
browsing option to find the package. If the file dtext.exe is located in
C:\EBT23\BIN, specify C:\EBT23 as the DynaText location.
• Network element: Here the network element data from the selected
booklist.txt is shown.
If DynaText cannot be started or does not show any documentation, you may
get some EOLM error messages in standard output. These mean that the
connection to the OLDT server failed. Restart the OLDT server and try again.
• DocView: With DocView you define the name of the main database and
optionally the sub-database separated with a comma. The use of wild
cards is allowed, so the book "AS 33*, APZ 212 11/*" specifies any
database that starts with "AS 33" and any sub-database starting with APZ
212 11/. DocView is not supported in WinFIOL/U.
• DynaText: With DynaText you define the name of the subdirectory of your
DynaText books directory. DynaText is not supported in WinFIOL/U.
• ALEX: With ALEX you should define the name of the database file without
the .alx extension. For example, if you have a database called as33.alx,
type as33.
• KRSWin: With KRSWin, you have to define the name of the database
listed in the KRSWin Library list window. KRSWin is not supported in
WinFIOL/U.
• In the output window, you can click on one of the hyperlinks. In addition,
Ctrl+F1 activates a dialog box that lists all commands and printout headers
that are currently visible in the output window. In this dialog box, a
command or a printout and the preferred type of document can be selected
and a request is sent to the documentation browser.
If Ctrl+F1 is pressed when the cursor is at a script command, the request will
activate the WinFIOL help system with the information about that specific
script command.
10 CommandForm
10.1 Introduction
10.2 Prerequisites
If the browser defined for the current channel is an ALEX database, the browser
looks there for each PCM file. If the PCM file is not found, the browser looks in
<WinFIOL installation directory>/pcm directory.
To exit Command Form, select the Cancel button, or press the Esc key.
When you type an MML command into WinFIOL, the CommandForm button
on the WinFIOL toolbar becomes enabled as soon as a supported command
is recognized. When you start CommandForm, the graphical tree-structure
form is shown (figure 36). If valid parameters are supplied, these appear with
values inserted in the tree. In most, but not yet all cases, the corresponding
nodes also get selected.
The window frame contains the command name. The command’s full name is
shown immediately below the title bar.
The central part is the command tree, and below, in the command field, the
resulting command string is shown, reflecting the current selections and set
values in the command tree.
When a valid command string has been created, the Send button is enabled,
and the command can be sent to the exchange.
10.5.2 Parameters
Parameters that are followed by an ampersand & are repeatable. For
information about the parameter, click on the question mark ? next to the
parameter name.
When all selected (yellow colored) parameters have been completed, the
Send/Insert button is enabled and the command can be sent to the exchange
or to WinFIOL.
You can override the proposed syntax by typing directly in the command field,
and as soon the semicolon is entered, the Send/Insert button is enabled. No
other syntax check is done.
To match the command field entry against the syntax, use the F5 key. This
will fill in the values in the graphical parameter nodes, and alter the text in the
command field according to the graphical syntax.
In Send mode, selecting the Send button sends the command to the
exchange, provided a connection exists, whereas in Insert mode the Insert
button transfers the command string to WinFIOL.
To fetch the default values for the current command, select the Get defaults
button. The default values for the current channel have precedence over
general default values. The default command and its values are displayed for a
short time in the status bar. CommandForm fills in the values into the tree.
To delete the default values, remove all text in the command field and select
Save defaults. You will be asked whether you want to delete the default values
for the current channel or for all channels. If you choose to delete for all
channels, the defaults for the current channel, if defined, will remain.
The Send/Insert button is default button, while enabled, and can be selected
by the Enter key.
To select the Cancel button in the CommandForm window and the Close
button in the Information window, use the Esc key.
With focus on any component in the scrolled area Page Up, Page Down,
Home, End, Arrow Up and Arrow Down will scroll the tree accordingly.
To select the Help button to bring up the tool help, use the F1 key.
To get the tree to reflect a change you have made by writing in the command
field, use the F5 button (See section 10.4.5).
E Open
USER GUIDE 77 ( 87 )
Prepared (also subject responsible if other) No
The Microsoft Component Object Model, or COM, specifies strict interfaces for
reusable objects and offers mechanisms for applications to use these objects.
COM interfaces are programming language independent.
COM and automation are two of the core technologies included under the
Microsoft ActiveX technology. For detailed information about COM and
associated technologies, refer to the Microsoft literature or Microsoft’s SDK
documentation.
From version 6.0 onwards, WinFIOL is a COM object or automation object. Any
application can use WinFIOL’s automation interface and use WinFIOL as an
out-of-process object. WinFIOL has two interfaces derived from IDispatch,
IWFMain and IWFChannel with a rich set of functions. In addition, WinFIOL
supports an outgoing interface called IWFEvent. WinFIOL does not support
IErrorInfo and connection points.
12 LDAP Client
On the Network page of the WinFIOL and Tools Configuration utility you can
define the LDAP servers and the central directories to be displayed in the
WinFIOL Target Manager. In figure 41, one directory and one LDAP server
have been defined.
Figure 41 Defining a channel file directory and an LDAP server with the
WinFIOL and Tools Configuration utility
DIRSERVER="dirserver.company.se"
DIRPORT=389
SEARCHBASE="o=xxx,c=country"
The DIRSERVER line specifies the directory server host name, DIRPORT the
directory server port number, and SEARCHBASE the search base for the
network directory root. You may define more than one server.
DIRECTORY=x:\data\WinFIOL\chn
The directory tree structure of the server will be displayed on the Network
page of the Target Manager. This page is only displayed if LDAP servers or
directories have been defined in the WinFIOL and Tools configuration utility (in
Windows) or there is an existing nc.cnf configuration file in the directory of the
WinFIOL binaries (in UNIX). The nsldap32v50.dll module (from Netscape)
is also needed. You can search elements by typing matching characters in
the Search field. To open a channel, select an item from the tree structure,
either by double clicking on the item or by selecting the item and pressing the
Open button. The target properties of an element can be viewed by pressing
the Properties button.
http://ccnd.ericsson.se/em/
13.1 Introduction
The Mode, Setup and Advanced channel properties are the same as for the
telnet protocol settings, except for the Login dialog settings on the Setup page.
With public key encryption/authentication, two keys are generated: one public
key and one private key. They are therefore called asymmetrical keys. The
private key must be stored and handled in such way that it is not revealed to
anyone else. The public key, on the other hand, must be made public.
13.2 Encryption
The SSH Encryption options are found at the Channel Properties | Protocol
| Encryption pane, see figure 43.
E Open
USER GUIDE 82 ( 87 )
Prepared (also subject responsible if other) No
This pane allows you to select which ciphers (encryption algorithms) to use
for encrypting the session. The ciphers are compared to the list of ciphers on
the SSH server in the order you have listed them. The cipher that will be used
is the first cipher on your list that matches a cipher available on the remote
server. From this pane, you can also select what Message Authentication
Codes (Macs) to use for authentication.
You can set the order of preference by moving the selected ciphers or Macs up
or down in the list using the Up and Down buttons.
The SSH User Keys options are found at the Channel Properties | Protocol |
User Keys pane.
E Open
USER GUIDE 83 ( 87 )
Prepared (also subject responsible if other) No
This pane lists the keys available for public key authentication. Select the key
you want to use from the User Keys list.
In order to generate a new key pair, click the Generate New Keypair button
shown in figure 44. This will invoke the SSH key generator console application,
see figure 45.
You will be prompted for a password for the new key. This password may not
contain language specific characters. Enter it twice and the key generation is
complete. The new key will appear in the User Keys list shown in figure 44.
A private key file does not have an extension. A public key file has the same
name as the correspondent private key file, but with .pub as file extension.
13.4 Authentication
SSH in WinFIOL uses two authentication methods: password and public keys.
These methods can be used separately or in combination. In order to use public
key authentication, your public key has to be available on the remote server.
• The Public Key option defines public key authentication for the session.
E Open
USER GUIDE 85 ( 87 )
Prepared (also subject responsible if other) No
• The Password and/or Public Key option defines password and/or public
key authentication for the session. Password authentication will be tried as
the preferred authentication. If the password authentication fails, public key
authentication will be used. The option also applies to SSH servers that
requires both authentication methods.
• The Public Key and/or Password option defines public key and/or
password authentication for the session. Public key authentication will be
tried as the preferred authentication. If the public key authentication fails,
password authentication will be used. The option also applies to SSH
servers that requires both authentication methods.
E Open
USER GUIDE 86 ( 87 )
Prepared (also subject responsible if other) No
14 Get Help
In addition to this User’s Guide, WinFIOL has a complete online Help system.
To access the online Help, select Help | Index, or press the F1 function key.
15 Glossary
ALEX Active Library Explorer (Ericsson)