Sei sulla pagina 1di 28

AMENDMENTS

The items that follow are incorporated in the update of this manual from issue 9909 to 0401:
CHAPTER/SECTION

DESCRIPTION

4.3. RETRIEVE CONVERSION

Upgraded because of conversion to Call@Net 2.5.

The items that follow are incorporated in the update of this manual from issue 0401 to 0204:
CHAPTER/SECTION

DESCRIPTION

4.3. RETRIEVE CONVERSION

Upgraded because of conversion to Call@Net 2.9.

PREFACE
This manual is valid for upgrading SOPHO ISPBX systems with System Software 805.xx to
SOPHO Call@Net (previously known as SSW 810).
Upgrading a system running an older software package than SSW 805 is described in another
manual : the SOPHO iS3000 Upgrade Manual (SSW xxx to SSW 805) with order number 3522
009 0556.

1.

INTRODUCTION

1.1.

GENERAL

For the SOPHO Call@Net system software, a new hardware platform 'the CPU3000' has
been introduced for the SOPHO iS3010, iS3030 and iS3050 systems. Also new and improved
functionality have become available in all SOPHO iS3000 systems, like Ethernet connectivity
and improved licensing.

1.2.

SUMMARY OF REQUIRED HARDWARE/FIRMWARE

SYSTEM

OLD SITUATION

iS3010, iS3030,
iS3050

CPU-ME/MT

CPU3000

VIC

VIC3000

SSM-MPC

SMPC

Dongle (+cable)

License file

CM/SM shelf

CSM shelf with BIM 2.0 connected


to the CIE2; see table Table 1-2 CIE
- BIM Combinations.

Dongle (+cable)

License file

BAC/BCC

removed

IAS-SCU link

removed

CM/SM shelf

see table Table 1-2 CIE - BIM


Combinations.

Dongle (+cable)

License file

IAS-SNS link

removed

iS3070/3090
with CM/SM
shelf

iS3070/3090
with CSM shelf

NEW SITUATION

Table 1-1 Summary of Required Hardware

POSSIBLE CONFIGURATION

PREFERRED
CONFIGURATION

CIE hardware
and bootprom

Use the present CIE board.

Replace the present CIE by a CIE2


board.

CIE firmware

Upgrade firmware package


FA1000.201 to FA1000.301.

Use firmware package FA1000.301.

BIM

Upgrade to at least BIM 1.6.

Use BIM 2.0; when necessary


replace the PC.

Table 1-2 CIE - BIM Combinations


It is mandatory to use CIE firmware package FA1000.301.
On top of the functionality offered by firmware package FA1000.201, CIE firmware package
FA1000.301 provides the 12NC + SB number of the CIE2 board and allows printf_2
adaptations for future multiple iS3000 ISPBX's in customer IP-networks.
Possible Configuration
Only the CIE-firmware package has to upgraded, allowing CSTA in Call@Net in
combination with the UNIX version of the BIM.
This alternative does not allow the use of BIM 2.0 with the old CIE hardware.
Preferred Configuration
By upgrading the complete CIE hardware, bootprom and firmware package, this
combination is able to operate with the BIM-NT version (BIM 2.0) and is prepared for
multi-point Ethernet applications expected to be available in future.
When using the new non-crossed Ethernet-plug on the CIE2 board, a hub is required to
connect BIM 2.0 in a multi-point Ethernet environment.

1.3.

BOUNDARIES, OPTIONS AND TIMERS

Be aware of the fact that in Call@Net a number of boundaries, options and timers (related to
SSW 805) are either new, changed or removed. For the meaning and exact values, refer to the
Second Line Maintenance Manual.

1.4.

CONVERSION SERVICE

The factory in Hoorn (the Netherlands) provides a conversion service. This saves you a lot of
work and a number of procedures which are described in this manual are done for you in the
factory. All the customer retrieve files containing the projecting information and

administration data must be sent to this service. Retrieve the projecting information and
administration files according the procedures in this manual.
To be able to make a optimal conversion, the following information is required:
-

Hardware layout of the PCT positions and cabinets.


Routing layout.
Status/release software/firmware packages.
SCP-upgrade order information.
New functionality, applications and expansions required.
Special attention points regarding to the administrative data.
Special arrangements/route characteristics.
Projecting data.
Administration data.

The Conversion Service in Hoorn sends back a MIS file, ODM and (if necessary) other items
which are required for upgrading. Upgrading at the site requires then:
-

Adapting the hardware (depending on the system type)


Loading the Call@Net system software.
Loading the new MIS file.
Adapting special user facilities.

Note: Once the upgrade procedure is started, do not make any changes in the system! If changes
cannot be avoided, log the changes carefully.
WARNING: MAKE A COPY OF THE REMOTE MAINTENANCE
CONFIGURATION FILES (RMAINX.CNF) TO SAVE THE VARIOUS
SETTINGS. THESE REMOTE MAINTENANCE CONFIGURATION
FILES ARE NOT PROCESSED WHEN UPGRADING THE SYSTEM
SOFTWARE.

2.

UPGRADING THE HARDWARE

2.1.

iS3010/3030/3050

In the iS3010, iS3030 and iS3050 systems the CPU-ME/MT (and VIC, when present) have to
be replaced by the CPU3000 and mandatory VIC3000.
The CPU3000 board has the following options to allow for system expansion and
improvement:
-

extra FEPROM and DRAM to provide flexible memory configuration:


- a Single Inline Memory Module (SIMM) with 8 Mb of FEPROM;
- a Single Inline Memory Module (SIMM) with 16 Mb of FEPROM;
- a daughter board with 16 Mb of DRAM;
- a daughter board with 32 Mb of DRAM.
an Accelerator Module (AM3000) to give the system a higher performance capacity.

The PMC has to be upgraded with the latest bootprom.


The dongle and dongle cable have to be removed; see 3. LICENSING.
Be aware that the SSM-MPC, when present, can not be used anymore : the SMPC has to be
used.

2.2.

iS3070 WITH CM/SM SHELF (Z8K PROCESSOR)

In the iS3070 system the CM/SM shelf has to be replaced by a CSM shelf containing the latest
CIE board (CIE2). Details can be found in the SOPHO iS3000 Upgrade Manual (SSW xxx to
SSW 805).
The dongle and dongle cable have to be removed; see 3. LICENSING.

2.3.

iS3070/3090 WITH CSM SHELF

In the iS3070/3090 with the CSM shelf only the present CIE firmware package has to be
replaced by FA1000.301. It is not necessary to replace the installed CIE and BIM. Be aware
that some new functionality offered by the latest CIE2/BIM 2.0 combination is not supported.
The dongle and dongle cable have to be removed; see 3. LICENSING.

2.4.

IAS BOARD

In Call@Net, projecting the recording channel (circuit 1) of the IAS is different. Circuit 1 has
to be projected as an LCT, instead of an IAS-TS resource. Furthermore a DNR has to be
assigned to this PCT. The 'announcement recording prefix' has to be removed. Because the
recording channel is now an LCT, not more than 4 DNRs can be assigned to it (as with other
LCTs). So when in a SSW 805 more than four recording prefixes were assigned to that circuit,
only the first four are converted.
Upgrading from CPU-ME/MT system to CPU3000
Apart from different projecting of circuit 1, the signalling group of :
- board type 56 has to be changed to 7B05;
- board type 57 has to be changed to 7B04.
Upgrading in a 'single unit' CCS system
Apart from different projecting of circuit 1, board type 55 has to be changed to 56 and
signalling group 7B05 has to be projected. Furthermore the cable from IAS to the
switching network has to be removed and the corresponding (SW) link has to be deleted.
Because the board now uses the PM bus, the corresponding strap (X 3.2 as illustrated in
the Maintenance Manual Part 3) has to be set for PM bus, instead of SM interface.
When the channels in the unit group containing the IAS board were occupied by another
board, then this board, or the IAS board has to be moved to a free unit group. When the
IAS was in an 'old' PM (PM2500 with PSC/PPU) the IAS board has to be moved to a PMC
shelf or PM part of CSM shelf. This is because each Call@Net system containing an IAS
has to consist out of at least one PMC.
If the IAS board is not located at a valid position (e.g. another board is present in the same
Unit group, all IAS related subcommands will be removed from the projecting. After
loading Call@Net the service engineer should move the IAS board to a PCT position in
the unit and assign it by hand. Also the recording DNRs should be assigned manually.
Upgrading in a 'multi unit' CCS system
All IAS related subcommands will be removed from the projecting. After loading
Call@Net the service engineer should check if all IAS boards are located at PCT positions.
If not the boards should be moved. When all boards are located correctly they can be
assigned by hand. Also the recording DNRs should be assigned manually.

2.5.

DCC BOARD

2.5.1.

Upgrading DCC Boards from SSW 805 to Call@Net

The upgrade procedure requires the Windows DECT Manager (version 2.0.1 or later).
Before starting the upgrade, carry out the following procedure:
1. Check that the system is configured with SSW 805 software.
2. Check that the DCC package is F43140.103 or later.
If it is not, first upgrade the DCC package to F43140.103 (or later).
3. Make a DCC backup with the Windows DECT Manager.
4. Make a note of (or print) the "NUMBER-CIRCUIT" relations known by the Windows
DECT Manager (see Configuration tab). This information is needed later.
5. Print, or note down the comment information of the different tabs.
The reason for this is because when the system is later configured with Call@Net, it is
required to make a new DAS at the Windows DECT Manager. This action means that all
comment information will be lost.
When the preparations described above are completed the update can be started.
1. Make a retrieve output with OM command RTRIEV.
2. Convert the retrieve output with the latest RCONV810 version.
3. Verify the RCONV output files and take note of the changes, possible errors and warnings
(normal practice).
4. Prepare the system for upgrading to Call@Net, including the projecting files generated by
RCONV810.
5. Load the system with package Call@Net.
6. When the system is operational, verify that the DECT terminals still operate normally.
7. Install a new DAS to the DCC board using the DECT Manager.
8. Select the DAS and backup the subscription information from the DCC board.
9. When applicable, restore the comment information in the different tabs (see item 5 in the
previous list).
DNR-MSN Relationships
When the Desk Sharing facility has been used it is possible that the "DNR - fixed MSN"
relationship may need to be changed for DNRs that are assigned to a DCC. Use OM command
DIFMSN for retrieving the fixed MSN.
What must be established is that all DNRs assigned to the same EHWA of a DCC circuit have

the same fixed MSN.


The value of the fixed MSN can be found with the DECT Manager by retrieving the NUMBER
that is related to the DCC circuit . This NUMBER must be used as the fixed MSN for DNRs
assigned to the same DCC circuit (see also item 4 in the first list above).
If the fixed MSN is not correct, change it to the applicable DNR value using the OM command
CHFMSN. Do this verification (and possible modification of the fixed MSN) for all DCC
circuits.

2.5.2.

Projecting Changes

Upgrading from SSW 805 to Call@Net, with RCONV810 changes the DCC mode from not
concentrated to concentrated. This results in the following projecting changes:
Board type of the DCC is changed from 15 to 16 (30B+D)
Signalling group of the DCC board is changed from:
- 0920 to 6204
- 0921 to 6205
- 0922 to 6206
- 0923 to 6207
Some of the PM data belonging to signalling groups 0920 ... 0923 are moved to signalling
group 6204 ... 6207 (see table below).

0920 ... 0923

6204 ... 6207

Byte 0 and 1

Byte 0 and 1

Byte 8 ... 43

Byte 4 ... 39

Byte 44 ... 62

Byte 44 ... 62

Table 2-1 PM data moved from old to new DCC signalling groups
The bytes not present in the table above are not moved from signalling groups 0920 ...
0923 to signalling groups 6204 ... 6207.
Signalling group 9600 contains DCC parameters that do not belong to a particular DCC
signalling group. It is possible that the PM data, byte 9 has been changed for this signalling
group, as follows:
- Where the old value was even, the new value = old value + 1
- Where the old value was not even, the value is not changed.
This implies that the DCC board is running in concentrated mode.

BSPT at DCC circuit 16 is moved to circuit 1


Boundary 303 (number of DCCs projected as 30B+D) is increased if the previous (SSW
805) value was too low.

2.5.3.

Fallback

In the unfortunate event that a fallback to SSW 805 is required, this can be executed as follows:
1.
2.
3.
4.

Restore the SSW 805 configuration in the PABX system


Install a new DAS to the DCC board using the Windows DECT Manager
Select the DAS and backup the subscription information from the DCC board
When required, restore the comment information that was printed out during step 5 of
2.5.1. Upgrading DCC Boards from SSW 805 to Call@Net

2.6.

OTHER BOARDS

For other boards, such as DTX-I, DLX-U, etc. it is advised to use the latest firmware packages.

2.7.

PMC - CSN COMBINATION

In combination with the CPU3000, the CSN must be classified as a board using a PCP channel.
This means that in the primary PM with the CPU3000 and CSN, there are 13 PCP channels
available for PCT boards and hatches, instead of 14 PCP channels in case of CPU-ME/MT and
CSN in SSW 805.
The following conversion is applied :
If the highest used hatch on the primary PMC is no longer available, that hatch is removed and
the warning 'HATCH REMOVED' is given. Also a warning is given when a PCT board can no
longer be assigned.

10

3.

LICENSING

3.1.

GENERAL

In Call@Net no longer a dongle is required for the licensing mechanism. Therefore all related
OM (sub-)commands for dongle equipment type and device assignments are removed from
Call@Net.
In Call@Net the licensing mechanism consists of a license file on the LBU (CPU3000 or BIM).
This means that all 'hardware dongle' related items are not relevant anymore. Since the
CPU3000 is introduced with Call@Net, a (technical) upgrade to the new license mechanism
is not applicable.
CCS was introduced in SSW 805. A (technical) upgrade from CCS SSW 805 to CCS Call@Net
requires an upgrade scenario for the license mechanism.
The following (technical) upgrade scenarios are recognised :
-

the CIE has no Board Parameter Device (in this document the CIE);
the CIE has already a Board Parameter Device (in this document the CIE-2).

PROCEDURE: Upgrade actions in case the CIE has no Board Parameter


Device
Actions
1. The ethernet low layer address has to be retrieved from the BIM 1.6 PC and has to be sent
to the IPSC (together with the upgrade request). The low layer address can be obtained
via the 'getnet' tool on the BIM. This tool must be installed on the BIM version 1.6 before
it can be used. When the BIM is configured for remote access, then 'getnet' can be used
remotely.
2. The database of the customer in the IPSC is used to generate the appropriate License
String.
3. The CIE and the BIM shall be downloaded with the latest software.
4. A text label which contains the fingerprint must be put on the BIM by the service engineer.
This label makes it possible to obtain the fingerprint even when the system is not
operational.

11

PROCEDURE: Upgrade actions in case the CIE has already a Board


Parameter Device
Actions
1. The CIE identifications (12NC + SB number) are already administered in the IPSC but no
customer allocation is done yet.
2. The CIE identification must be read from the CIE board and sent to the IPSC, together
with the upgrade request. The fingerprint (=CIE identification) is available on a label on
the board. When more than one CIE is used in the system, then the identification of the
CIE to which the LBU is connected must be used.
3. The database of the customer in the IPSC is used to generate the appropriate License
String.
4. The CIE and the BIM have to be downloaded with the latest software.

3.2.

CSTA ASPECTS

From Call@Net and onwards no free licenses are coded in the CPU software anymore. In
SSW 805 two CSTA license features are implemented in the CPU software :
-

1 iSLink and 4 Monitors are for free.


Customers with 5 iSLinks will get the 6th iSLink for free.

The free 1 iSLink and 4 Monitors were intended to let customers try the CSTA functionality.
This try-out function is now a 'try&buy' license.
New deliveries do not include the free 6th iSLink license. Upgrade customers (from SSW 805
to Call@Net) receive the 6th iSLink for free. The 'Salesbuilder' program checks whether a
customer has a license for 5 iSLinks and will then generate a License String containing 6 iSLinks.

12

4.

UPGRADING PROJECTING DATA FROM SSW 7XX/


800/805

4.1.

GENERAL

This chapter describes how to upgrade the projecting of an iS3000 with SSW 7xx/800/805 to
Call@Net.
The existing System Software cannot be upgraded. Call@Net must be stored into the system
as a new software package. The projecting information which is already in the system must be
upgraded. This must be done by means of the tool RCONV (Retrieve Conversion).
New software must be loaded together with the converted file with projecting information.
The functionality of the units is maintained and additional functionality is added.

4.2.

IMP NETWORK UPGRADING

SOPHO iS3070/3090 units can be connected together as one IMP network (or refered to as
an iSNet Metropolitan Area Network). Often such a large network cannot be upgraded to the
Call@Net at the same time. Unit-by-unit the ISPBX units in the network are loaded with the
new System Software. This causes unit-incompatibility during the period that the IMP network
is going to be upgraded. In fact the network comprises two different networks: a network
operating on the old software and a network operating on Call@Net. As result of the
differences in facilities between SSW 805 and Call@Net the communication between these
networks is restricted.
A minimum of compatibility between the two networks is maintained to make calls and a
number of basic facilities are possible. The use of operational maintenance and system
assurance however is not possible.
Before the compatibility facility can be used, the network system option LOSYSOP 053 must
be true in all units of the network. This enables the unit compatibility facility. The option can
be set with the command EXSUBC with the subcommand S92200.
If the option is true throughout the network, the following OM command is used to indicate
that the total network is compatible or incompatible:
CHCOMP: <INC-OR-COM>;

If compatible the parameter INC-OR-COM is '0'; if incompatible the parameter is '1'.

13

The compatibility between two units in the network can be displayed with OM command:
DICOMP: <UNIT 1>[,<UNIT 2>];

The displayed information is the status of unit 2 as seen by unit 1.


After all units in the network are operational with the new software package, switch back the
compatibility status of the network to 'compatible'. Use OM command CHCOMP and clear
the network system option again. Now all facilities are equally available throughout the IMP
network with the Call@Net.
For a detailed description of the software upgrading via the unit compatibility facility, see the
Maintenance Manual.

4.3.

RETRIEVE CONVERSION

4.3.1.

General

The Retrieve Conversion tool (RCONV) is a software tool that converts retrieve output files
of an iS3000 ISPBX to projecting files that serve as input. It is part of the upgrading system
software procedure. This document describes the actions to be performed during upgrading
of system software.
This new release of RCONV for Call@Net is used for upgrading iS3000 system software to
Call@Net. It contains - besides all existing steps - new additional steps to convert from SSW
805 CCS to Call@Net CCS and from SSW 805 CPU-ME/MT to Call@Net CPU3000.
The Retrieve Conversion procedure which is described here can be used to upgrade systems
with the following System Software:
-

SSW 720.4x
SSW 725.xx
SSW 730.xx
SSW 735.xx
SSW 740.2x
SSW 741.2x
SSW 800.2x
SSW x805.2x
SSW 810.2x

In case of the SOPHO iS3070/3090, the SOPHO ISPBX may consist of more than one unit. In

14

this section the general case of N units is handled. Of course, for the SOPHO iS3010, iS3030
and iS3050 the value of N is equal to 1.
The tool RCONV runs on a IBM compatible PC. The minimum system requirements are:
-

486 processor;
8 Mb RAM memory;
10 Mbytes free disc space on the hard disc;
floppy drive.

The following sections describe the upgrade procedures. First read them carefully. This gives
you a thought of how the tool is to be used and which sequence of steps you have to follow.

4.3.2.

Procedure

The procedure indicates the flow actions which must be performed. The actions are explained
in more detail in the section 4.3.3. Command Layout and Parameters and 4.3.4. Description
of Steps.
Parameters like "uu", "rrr" etc. used in this procedure are explained in more detail in section
4.3.3. Command Layout and Parameters.
In case a step (in the initiation procedure or convert procedure) is unable to convert, a manual
action is needed. In such a case error files PRuu_ERR.sss and ORuu_ERR.sss are generated. In
these error files an abstract is given of all items that should be checked manually. These items
are identically marked in the output files PRuu.sss and ORuu.sss. Each item must be solved
before continuation of intermediate steps.
In the procedure three main actions are distinguished:
Initiation
This initiation procedure performs a file format conversion to readable ASCII. The files
PRuu.TXT and ORuu.TXT are generated. For SSW 720.4x, SSW 725.xx and 730.1x it also
performs a conversion to 730.20. In that case also the files PRuu.730 and ORuu.730 are
generated.
1. Remove all old RTRIEV files : RCONV needs 'version 1' files
2. Create retrieve output files (in all units) of the iS3000 in order to obtain a set of
ORuu.POM and PRuu.POM files on the LBUuu of unit "uu". Use OM command:
"BMLOCK" and "RTRIEV"
3. Prepare two sets of blank and formatted diskettes. Each set consists of one diskette per
unit. Label the diskettes of set one with: "uu-1", where "uu" is the unit number. Label the

15

diskettes of set two with: "uu-2"


4. Copy the retrieve files from the LBUuu (of all units) to diskette(s) labelled "uu-1". In case
of N units, now N diskettes are obtained, each labelled: "uu-1" and containing two files:
PRuuV1.POM and ORuuV1.POM
5. Check that the *.POM files have version number 1. If this is not the case (for example:
PR05V3.POM) rename this file to version number 1 (in this example: PR05V1.POM)
6. Create a subdirectory "C:\CNVqqq" on the hard disk of the PC, where "qqq" is the name
of the new SSW package: "SSWqqq.qq". Here the conversion shall take place
7. Copy all RCONV files from the diskette to the subdirectory made previously
8. Copy all retrieve files from the "uu-1" diskette(s) to the subdirectory made previously.
Execution
Now the actual conversion procedure is done by calling the RCONV conversion steps. These
steps perform a conversion of retrieve files from one package "rrr" to another "sss". The step
takes input from PRuu.rrr and ORuu.rrr files and stores the result in PRuu.sss and ORuu.sss
files. When the PRuu.rrr and ORuu.rrr files cannot be found (no conversion necessary during
previous step), the ORuu.TXT and PRuu.TXT are taken. The last step generates the files
PRuu.NEW and ORuu.NEW.
Consult section 4.3.4. Description of Steps for details about the RCONV conversion steps.
1. Determine the RCONV conversion steps that you must execute; use the table below.

16

ORIGINAL
SYSTEM
SOFTWARE

RCONV STEP "nn"


1

2, 3

5, 6,
7

7a, 8

10

11

12 to
15

720.4x, 725.xx
730.1x, 730.2x

735.1x

735.2x

740.2x

741.2x

800.2x

805.2x

806.2x

810.2x

Table 4-1 Required Conversion Steps.


2. Execute the selected RCONV steps (from the step table) by calling the batch files:
STEPnn.BAT, where "nn" is the step number. Execute the steps in a rising sequence.
Execute each step for all units, when converting a multi unit network configuration. After
this, execute the next determined step for all units and work your way up through the
determined steps. Using this working method, the steps that do not need the unit number
as a parameter (e.g. step 5 or step 7) have to be executed only once. These steps analyse
the data of all the current, converted to this level of SSW release, OR/PR files.
In case of DPNSS and DASS routes in a multi unit configuration it is not allowed to do all
steps in one go, manually or by the stepall batch file. It will result in inconsistent data.
Note: After each RCONV step informational messages or conversion errors may occur. Repair
them all before executing a next step.
3. Now, a set of N diskettes is obtained; one for every unit"uu". Each diskette is labelled: "uu2" and contains two files: PEuuV1.POM and LLuuV1.POM. These can now be used for the
upgrade of the iS3000.
4. When desired, the subdirectory that has been used for the conversion on the hard disk can
now be erased.
Release

17

Now the conversion is done, you can start with reloading the system.
1. Install the new software package on the LBU of the iS3000.
2. Copy the new projecting files from the "uu-2" diskette(s) to the LBUuu (of all units) of the
iS3000; for details see Maintenance Manual, Part 1.
3. Remove all versions "v" of all MIS files LMuu01Vv.POM (from LBUuu) for all units "uu".
4. Perform OM command "STLOAD" on all units, to load the package and to re-project the
system.
The result of the upgrade action is an iS3000 system with N units, each running the
Call@Net.2x software package.
The functionality of the units is maintained; all data and facilities that were available in the
previous used SSW are now available with Call@Net.

4.3.3.

Command Layout and Parameters

The conversion steps have a specific command layout with parameters. The following
describes the layout and parameters:
Command layout
The general command layout of a conversion step is:
STEPnn [uu] [ppp[.pp]] [xxx]
where "nn" represents the step number, "uu" represents the two digit unit number and
"ppp[.pp]" represents the original system software package number ("SSW ppp.pp"). Some
steps take an extra parameter "xxx". Depending on the step some parameters are omitted or
optional.
Example:
For an iS3000 with SSW 805.20 as original package, 06 as unit number and a CSN-BC installed
(denoted with 'Y'), the command line for step 11 is as follows:
step11 06 0805.20 y
Parameters
In the file names you will often find notations, called parameters, which refer to a system type,
unit, or function. The following overview shows an overview of these parameters with their
meaning and syntax:

18

mmmm

nn
ppp[.pp]

:
:

qqq[.qq]
rrr

:
:

sss

uu

4.3.4.

Four digit number indicating the type of iS3000


7100 = SOPHO iS3070;
8100 = SOPHO iS3030 and iS3050 with CSN-BC;
8110 = SOPHO iS3010, iS3030 and iS3050 without CSN-BC
One or two digit RCONV step number 1 ... 12
Three or six character SSW original package name.
720.40, 725, 730.10, 730.20, 730.30, 735.10, 735.20, 740.20, 741.20,
800.20, x805.20, x810.20
Note that SSW 805/810 is indicated by 4 characters :
- 0805.20 for CPU-ME/MT systems
- 7805.20 for CPS systems
- 9805.20 for CCS systems (CSM shelf)
- 6810.20 for CPU3000 (without AM) systems
- 9810.20 for CCS and CPU3000 (with AM) systems
Six character SSW new package name 810.20
Three character SSW name, used as an extension for files which are
used as input for a conversion proces.
Three character SSW name, used as an extension for files which are
converted to this "sss" software.
Two digit unit number 01 ... 09, 10 ... 14.

Description of Steps

The RCONV tool consists of several files that are listed in Table 4-2 Description of Steps. and
Table 4-3 Description of Step "STEPALL"..

19

FILE NAME

PURPOSE

STEP1.BAT

File format conversion and 720.40/725/730.10 to 730.20


conversion

STEP2.BAT

730.20/730.30 to 735.10 pre-conversion

STEP3.BAT

730.20 to 735.10 conversion

STEP4.BAT

735.10 to 735.20 conversion

STEP5.BAT

735.20 to 740.20 pre-conversion

STEP6.BAT

735.20 to 740.20 conversion

STEP7.BAT

735.20 to 740.20 post-conversion

STEP7A.BAT

Creates S30290.TXT file, used by step8

STEP8.BAT

740.20 to 741.20 conversion

STEP9.BAT

741.20/800.20 to 805.20 conversion

STEP10.BAT

805.20 (Z8K) to 805.20 (CCS) conversion

STEP11.BAT

805.20 to 810.20 conversion

STEP12.BAT

810.2x to 810.25 conversion

STEP13.BAT

810.28 to 810.29 conversion

STEP14.BAT

File format conversion

STEP15.BAT

Copy to floppy

STEPALL.BAT

Executes STEP1.BAT to STEP15.BAT

Table 4-2 Description of Steps.

20

STEPALL.BAT

EXECUTES STEP1.BAT to STEP14.BAT

CNV73020.EXE

used by STEP1.BAT

CONVPRE.EXE

used by STEP2.BAT

CNV73510.EXE

used by STEP3.BAT

CNV73520.EXE

used by STEP4.BAT

PRE74020.EXE

used by STEP5.BAT

CNV74020.EXE

used by STEP6.BAT

POST7402.EXE

used by STEP7.BAT

PRE74120.EXE

used by STEP7A.BAT

CNV74120.EXE

used by STEP8.BAT

CNV80520.EXE

used by STEP9.BAT

SC805_1.EXE

used by STEP10.BAT

CNV81020.EXE

used by STEP11.BAT

POST810.EXE

used by STEP12.BAT

TO81029.EXE

used by STEP13.BAT

CONVERT.EXE

used by STEP1.BAT and STEP14.BAT

CONVERT.MSG

used by STEP1.BAT and STEP14.BAT

RTM.EXE

used by CNV81020.EXE

DPMI16BI.OVL

used by CNV81020.EXE

Table 4-3 Description of Step "STEPALL".


The properties of the steps are specified in more detail in the following overview :
STEP 1
Command
Function

:
:

Execute
Input file
Output file
Error file
SSW

:
:
:
:
:

step1 uu ppp[.pp]
Convert both retrieve files to readable ASCII format.
For 720.40, 725 and 730.10 also a retrieve conversion to 730.20 is
performed.
CONVERT.EXE [, CNV73020.EXE]
PRuuV1.POM, ORuuV1.POM
PRuu.TXT, ORuu.TXT [, PRuu.730, ORuu.730]
PRuu_ERR.730, ORuu_ERR.730
720.40, 725, 730.10 =>730.20

21

22

Remark

Manual

STEP 2
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark

:
:
:
:
:
:
:
:

Manual

STEP 3
Command
Function
Execute
Input file

:
:
:
:

Output file
Error file
SSW
Remark
Manual

:
:
:
:
:

STEP 4
Command
Function

:
:

For other packages than 720.40, 725 and 730.10, only format
conversion is done.
Refer to error files.
step2 ppp[.pp]
Prepare retrieve conversion to 735.10.
CONVPRE.EXE
PRuu.730, ORuu.730 or else: PRuu.TXT, ORuu.TXT
S45050.TXT, S45060.TXT, S46010.TXT
730.20 =>735.10
All S45050 subcommands are collected from all ORuu.TXT (or
ORuu.730) files. The result is written to the file S45050.TXT.
Also a file S45060.TXT is created to indicate if DASS is present or not.
All S46010:2,route,1,1; sub-commands are collected from all
ORuu.TXT (or ORuu.730) files. The result is written to the file
S46010.TXT.
Therefore all ORuu files, converted to SSW 730.20,of all units must be
present, so that they can be scanned for DASS routes.
-

step3 uu ppp[.pp]
Convert retrieve files to 735.10.
CNV73510.EXE
PRuu.730, ORuu.730 or else: PRuu.TXT, ORuu.TXT S45050.TXT,
S45060.TXT, S46010.TXT
PRuu.735, ORuu.735
PRuu_ERR.735, ORuu_ERR.735
730.20 =>735.10
Refer to error files.
The files PRuu.730 and ORuu.730 may be deleted, when desired.
When .735 output files are generated the files PRuu.TXT and
ORuu.TXT may be deleted.

step4 uu ppp[.pp]
Convert retrieve files to 735.20.

Execute
Input file
Output file
Error file
SSW
Remark
Manual

:
:
:
:
:
:
:

CNV73520.EXE
PRuu.735, ORuu.735 or else: PRuu.TXT, ORuu.TXT
PRuu.352, ORuu.352, PRuu.DNR, ORuu.DNR
PRuu_ERR.352, ORuu_ERR.352
735.10 =>735.20
Refer to error files.
The files PRuu.735 and ORuu.735 may be deleted, when desired.
When .352 output files are generated the files PRuu.TXT and
ORuu.TXT may be deleted. When .DNR output files are generated,
these files may be deleted.

STEP 5
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark

:
:
:
:
:
:
:
:

Manual

step5 ppp[.pp]
Prepare retrieve conversion to 740.20.
PRE74020.EXE
ORuu.352 or else: ORuu.TXT (of all units 'uu'!)
S45190.TXT
735.20 =>740.20
All DPNSS routes are be collected from ORuu.TXT (or ORuu.735)
files of all units "uu". Therefore all ORuu files,converted to SSW 735.20
of all units must be present so that they can be scanned for DPNSS
routes. The result is written to the file S45190.TXT.
This command writes the amount of processed files to the screen.
-

STEP 6
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark

:
:
:
:
:
:
:
:

Manual

step6 uu ppp[.pp]
Convert retrieve files to 740.20.
CNV74020.EXE
PRuu.352, ORuu.352 or else: PRuu.TXT, ORuu.TXT S45190.TXT
PRuu.TMP, ORuu.TMP, ASDGCO.TXT
PRuuERR.740, ORuu_ERR.740
735.20 =>740.20
DPNSS routes are taken from the S45190.TXT file and inserted in the
ORuu.TMP file.
Refer to error files.
The files PRuu.352 and ORuu.352 may be deleted, when desired.

23

24

STEP 7
Command
Function
Execute
Input file

:
:
:
:

Output file
Error file
SSW
Remark

:
:
:
:

Manual

STEP 7A
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark

:
:
:
:
:
:
:
:

Manual

The S30290 sub-commands are taken from the OR files and inserted
in the newly created S30290.TXT file. The command writes the
amount of processed units to the screen
-

STEP 8
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark

:
:
:
:
:
:
:
:

step8 uu ppp[.pp]
Convert retrieve files to 741.20.
CNV74120.EXE
PRuu.740, ORuu.740 or else: PRuu.TXT, ORuu.TXT
PRuu.741, ORuu.741
PRuu_ERR.741, ORuu_ERR.741
740.20 =>741.20
-

step7 ppp[.pp]
Post-process retrieve conversion to 740.20.
POST7402.EXE
PRuu.TMP, ORuu.TMP or else: PRuu.TXT, ORuu.TXT
ASDGCO.TXT
PRuu.740, ORuu.740
PRuuERR.740, ORuu_ERR.740
735.20 =>740.20
The S45170 sub-commands are taken from the ASDGCO.TXT file
and inserted in the ORuu.740 file.
This command writes the amount of processed units to the screen.
-

step7a ppp[.pp]
Pre-process for step8 (conversion to 741.20).
PRE74120.EXE
ORuu.TXT or else: ORuu.740 of all units
S30290.TXT

Manual

Refer to error files.


The files PRuu.740 and ORuu.740 may be deleted, when desired.
When .741 output files are generated the files PRuu.TXT and
ORuu.TXT may be deleted.

STEP 9
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark
Manual

:
:
:
:
:
:
:
:
:

step9 uu ppp[.pp]
Convert retrieve files to 805.20.
CNV80520.EXE
PRuu.741, ORuu.741 or else: PRuu.TXT, ORuu.TXT
PRuu.805, ORuu.805
PRuu_ERR.805, ORuu_ERR.805
741.20/800.20 =>805.20
Refer to error files.
The files PRuu.741 and ORuu.741 may be deleted when desired.
When .NEW output files are generated, the files PRuu.TXT and
ORuu.TXT may be deleted.

STEP 10
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark
Manual

:
:
:
:
:
:
:
:
:

step10 uu ppp[.pp] [z8k] [compact]


Convert SSW7805 CPS retrieve files to SSW9805 CCS
SC805_1.EXE
PRuu.805, ORuu.805 or else: PRuu.TXT, ORuu.TXT
PRuu.805, ORuu.805
PRuu.LOG, ORuu.LOG (log files)
7805.20 CPS =>9805.20 CCS
Refer to error files.
Before conversion is executed, the input files are copied to resp.
PRuu_Z8K.805 and ORuu_Z8K.805

STEP 11
Command
Function
Execute
Input file
Output file
Error file
SSW

:
:
:
:
:
:
:

step11 uu ppp[.pp]
Convert retrieve files to 810.20.
CNV81020.EXE
PRuu.805, ORuu.805 or else: PRuu.TXT, ORuu.TXT
PRuu.020, ORuu.020
PRuu_ERR.810, ORuu_ERR.810
805.20 =>810.20

25

26

Remark
Manual

:
:

Refer to error files.

STEP 12
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark
Manual

:
:
:
:
:
:
:
:
:

step12 ppp[.pp]
Convert retrieve files from 810.2x to 810.25.
POST810.EXE
PRuu.810, ORuu.810 or else: PRuu.TXT, ORuu.TXT
PRuu.025, ORuu.025
810.2x =>810.25
S37100.txt
-

STEP 13
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark
Manual

:
:
:
:
:
:
:
:
:

step13 uu ppp[.pp]
Convert retrieve files from 810.25 to 810.29.
TO81029.EXE
ORuu.025 or ORuu.TXT
ORuu.029
810.25 =>810.29

STEP 14
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark

:
:
:
:
:
:
:
:

Manual

step14 uu [LST]
Convert to S2500 file format.
CONVERT.EXE
PRuu.NEW, ORuu.NEW
PEuuV1.POM, LLuuV1.POM, PEuu.LST, LLuu.LST
all
This step converts the PEuu.NEW and ORuu.NEW to loadable
projecting files PEuuV1.POM and LLuuV1.POM.
-

STEP 15
Command
Function

:
:

step15 uu [b:]
Copy to floppy.

Execute
Input file
Output file
Error file
SSW
Remark

:
:
:
:
:
:

Manual

STEP ALL
Command
Function
Execute
Input file
Output file
Error file
SSW
Remark

:
:
:
:
:
:
:
:

Manual

4.4.

PEuuV1.POM, LLuuV1.POM
A:*.* or B:*.*
all
This step copies all projecting files of one unit to a diskette. By default,
the files are copied to drive A. Depending on the presence of the
optional parameter, the files are copied to B.
stepall uu ppp[.pp] [z8k] [compact]
Call all steps.
(All steps.)
PRuuV1.POM, ORuuV1.POM
PEuuV1.POM, LLuuV1.POM
PRuu.ERR, ORuu.ERR
all
This step can be used to execute all steps in one go.
Once running, this batch file does not stop executing when
conversion errors occur during executing the steps.
Note that this batch file (Step All) can not be used in case of a multi
unit configuration. Ignoring this, may result in inconsistent network
data.
When intermediate error files are generated, problems must be
solved and the related steps have to be repeated again.

MEMORY CONSTRAINTS

No memory calculations are performed in this version of RCONV. Use the separate MEMCAL
tool to check if the projecting files fits into the memory of the system.

27

28