The Edit menu contains the following items:
Clock This displays the Set Clock window which makes it possible to change the simulation time.
Properties This displays a window where properties of the simulation may be set. Properties such as simulation speed, announcement settings and output design may be specified.
2.28.1 Set Clock Window
The Set Clock window is shown below:
Figure 2.22 Set Clock window
It allows the user to manipulate the clock in order to test different dates and times in the logic. Apply is used to accept the new time. Reset will cause the simulation to revert to the current date and time.
2.28.2 Properties Window
The Properties window is shown below:
Figure 2.23 Properties Window
The window includes the following permanent textfields:
Execution Speed This slider sets the speed of the simulation when running in continuous mode.
NRANAx Search Method
Indexed or Scanned,
CCTRAF Directive The CCTRAF control type is used to update data modules in a service. There are two options, Pretend to Change DB and Really change DB.
Dialogue Window There are five different settings for the Dialogue Window. Dialogue, Changed Tags, Logic Modules, Error Text and Announcement Text.
Maximum Jumps This makes it possible for the user to change the value RLT uses for maximum number of jumps to reflect the actual limit set by the SCF.
Maximum Gosub Depth
This changes the value used for maximum gosub depth.
Play Announcement This is not used in ETSI CS1/CS1+ mode.
Announcement Path This is not used in ETSI CS1/CS1+ mode.
Parts Path This is not used in ETSI CS1/CS1+ mode.
Effects Path This is not used in ETSI CS1/CS1+ mode.
Announcement Text File
This is not used in ETSI CS1 mode.
SSRDWR Configuration File
This is not used in ETSI CS1 mode.
Show SDF Window Always - Shows the SDF window every time an Update or Retrieve operation is sent.
As Needed - Shows the SDF window when an Update or Retrieve operation is sent and an operation break point has been set, or when an SDP has not been identified.
Number Analysis Search Method
The control type NRANAX may search the SMAS database by either scanning the table, or by using the table’s index. Each method has differ-ent characteristics.
Indexed Search Method
The indexed search method is faster than the scanned method when searching large number analysis tables. The best performance, using this
method, will be found when a number analysis table has about 5000 rows or more.
This method has one major disadvantage: Table entries with either * or # in the key will not be found using this method. The only way around this is to use the Scanned search method, or to always store ‘B’ for * and ‘C’ for
#.
Scanned Search Method
This method works well with small number analysis tables (under 5000 rows). This method will also find * and # if they are in the table.
CCTRAF Directive
The CCTRAF control type is used to update data modules in a service.
This provides the service functionality called customer control. This prop-erty allows the user to decide if CCTRAF should really change the data (as it would in the SCP), or if it should only pretend to change the data.
Pretend to Change DB
When this option is selected, the CCTRAF logic module will go through the entire procedure of locating the DM to change, locating the change procedure (CCPROC), sending announcements (if any), etc. It will not actually cause any data to be changed.
This is the default mode for the CCTRAF Directive.
Really Change DB
In this mode, CCTRAF will go through all the normal steps, including a change to the database. If an uninstalled service is being tested, then only the SMAS database will be changed. If the service and service data is installed, then a request for a change will be placed on the SCP request queue.
This option cannot be selected if the RLT user does not have ‘update’ priv-ileges.
Dialogue Window
By default, the Dialogue window shows the INAP messages passed to and from the SCF and SSF. This option on the properties window will allow you to select other information which can also be shown in the dialogue window. Any combination of the following may be selected:
Dialogue
INAP messages between SSF and SCF are shown.
Changed Tags
A list of tags that have changed after the execution of a logic module is shown. Both the tag name and its new value are included.
Logic Module
The SA name, the SA side (OP or NOP), the SSL name and version, the outlet used, and the logic module name are listed as each logic module is executed.
Error Text
Messages from the SCF which are normally only displayed in the call view window footer are also placed in the dialogue window.
Annc Text
The text shown on the Resource window is also added to the dialogue win-dow.
These five items allow you to log detailed information surrounding the execution of a service. The contents of the dialogue window may be saved to a file or printed for future reference.
Maximum Jumps
The maximum number of jumps from one SA to another is limited by the SCF. This limit is configurable at the time the SCF dump is built. There-fore, RLT allows you to change the value it uses for maximum number of jumps to reflect the actual limit set by your SCF.
The default value for the jump limit is 8. This is the value typically used in most SCF builds. You should not adjust this value unless you are certain your target SCF has a different limit. Using an inaccurate value will mean that RLT will fail to simulate how your service will execute on the target SCF.
Maximum Gosub Depth
The maximum gosub depth is the depth that a subroutine may be nested.
Like the jump limit, this limit is configurable at the time the SCF dump is built. RLT allows you to change the value it uses for the maximum gosub depth.
The default for the gosub depth limit is 3. This is the value typically used in most SCF builds. You should not adjust this values unless you are cer-tain your target SCF has a different limit. Using an inaccurate value will mean that RLT will fail to simulate how your service will execute on the target SCF.
Update Permission
It can be said that RLT will never change the database, because it only reads data and never writes. This assures that a novice cannot accidentally damage a working service.
However, with the implementation of CCTRAF, it is possible that RLT will write changes to data in SMAS. To assure only knowledgeable users attempt these operations, a permission file must exist which gives users update permission. Only users with update permission may modify data using RLT.
The permission file is called .rltupdates.
The permission file must exist in the subdirectory pointed to by the envi-ronment variable TMOSHOME. This is usually /opt/tmos.
The file is a list of users who have ‘update permission’. The SMAS or TMOS administrator can create the file in the following way:
cd $TMOSHOME
vi .rltupdates
List user ids of people with update permission, one per line:
etxtidw etxgroh etc...
If the file contains the word ‘all’ on a line by itself, then all users will have update permission.
This file should have read permission by all SMAS users. Write permis-sion for this file should be disabled except for the system administrator.
This can be done with the following command:
chmod 644 .rltupdates