EDITRAN/G - Indraeditran.indra.es/EN/doc/win_unix/editran/EDITRAN_G_EN.pdf · EDITRAN/G Application Generic Interface Windows/Unix User manual INDRA 17/03/2017

EDITRAN/G

Application Generic Interface

Windows/Unix

User manual

INDRA 17/03/2017

EDITRAN/G Windows/Unix User manual INDEX

AUINDRA. All rights reserved. EDITRAN/G

1. INTRODUCTION ................................................................................................................................... 1-1

2. DESCRIPTION ...................................................................................................................................... 2-1

2.1. GENERAL FEATURES ...................................................................................................................................... 2-2

2.2. SPECIFIC FEATURES ....................................................................................................................................... 2-3 2.2.1. Versions 3.0, 3.1..................................................................................................................................................................................................................... 2-3 2.2.2. Version 4.0 ................................................................................................................................................................................................................................ 2-3 2.2.3. Version 4.1 ................................................................................................................................................................................................................................ 2-3 2.2.4. Version 5.0 ................................................................................................................................................................................................................................ 2-3 2.2.5. Version 5.1 ................................................................................................................................................................................................................................ 2-3

3. EDITRAN/G MANAGEMENT (UNIX). ................................................................................................... 3-1

3.1. OPERATION INTERFACE ................................................................................................................................. 3-1 3.1.1. SCREENS .................................................................................................................................................................................................................................... 3-1 3.1.2. HELP ............................................................................................................................................................................................................................................ 3-2 3.1.3. KEYS ............................................................................................................................................................................................................................................. 3-2 3.1.4. SELECTION BY LIST ............................................................................................................................................................................................................... 3-3

3.2. EDITRAN/G OPERATOR .................................................................................................................................. 3-3 3.2.1. UPLOADING TRANSMISSION PRESENTATION........................................................................................................................................................... 3-4 3.2.2. INITIALIZING TRANSMISSION PRESENTATION ......................................................................................................................................................... 3-4 3.2.3. TRANSMITTING PRESENTATION ..................................................................................................................................................................................... 3-4 3.2.4. INTERRUPTING EMISSION PRESENTATION................................................................................................................................................................ 3-5 3.2.5. INITIALIZING RECEPTION PRESENTATION ................................................................................................................................................................. 3-5 3.2.6. DOWNLOADING RECEPTION PRESENTATION............................................................................................................................................................ 3-5 3.2.7. RECEIVING PRESENTATION ............................................................................................................................................................................................... 3-5 3.2.8. INTERRUPTING RECEPTION PRESENTATION ............................................................................................................................................................ 3-5 3.2.9. MONITORING PRESENTATION STATUS ....................................................................................................................................................................... 3-6

3.3. CONTROL FILES MANAGEMENT ..................................................................................................................... 3-7 3.3.1. MONITORING PRESENTATION STATUS ....................................................................................................................................................................... 3-7 3.3.2. MODIFICATION OF PRESENTATION STATUSES ........................................................................................................................................................ 3-9 3.3.3. LOG MONITORING ............................................................................................................................................................................................................... 3-10

3.4. EDITRAN/G ADMINISTRATOR ...................................................................................................................... 3-11 3.4.1. LOCAL ENVIRONMENT ...................................................................................................................................................................................................... 3-12 3.4.2. REMOTE ENTITY PROFILE ............................................................................................................................................................................................... 3-13 3.4.3. APPLICATION PROFILE ..................................................................................................................................................................................................... 3-15 3.4.4. PRESENTATION ................................................................................................................................................................................................................... 3-17 3.4.5. PROFILE GENERIC MONITORING .................................................................................................................................................................................. 3-23

3.4.5.1. REMOTE ENTITIES ................................................................................................................................................................................................. 3-23 3.4.5.2. APPLICATIONS ........................................................................................................................................................................................................ 3-24 3.4.5.3. PRESENTATIONS ................................................................................................................................................................................................... 3-24

4. EDITRAN/G MANAGEMENT (WINDOWS) ............................................................................................ 4-1

4.1. OPERATION INTERFACE ................................................................................................................................. 4-1 4.1.1. SCREENS .................................................................................................................................................................................................................................... 4-1

4.2. BOOTING AND STOPPING EDITRAN .............................................................................................................. 4-2

4.3. EDITRAN/G OPERATOR .................................................................................................................................. 4-3 4.3.1. Upload transmission presentation ................................................................................................................................................................................. 4-3 4.3.2. Process after transmission ................................................................................................................................................................................................ 4-4 4.3.3. Transmitting presentation ................................................................................................................................................................................................. 4-4 4.3.4. Interrupting transmission ................................................................................................................................................................................................... 4-4 4.3.5. Initializing reception presentation ................................................................................................................................................................................. 4-5 4.3.6. Dowloading reception .......................................................................................................................................................................................................... 4-5 4.3.7. Receiving presentation ....................................................................................................................................................................................................... 4-5 4.3.8. Interrupting reception ......................................................................................................................................................................................................... 4-6

4.4. FILE MONITORING .......................................................................................................................................... 4-6 4.4.1. Monitoring presentation statuses .................................................................................................................................................................................. 4-6 4.4.2. Modifying presentation statuses .................................................................................................................................................................................... 4-8 4.4.3. Log monitoring ........................................................................................................................................................................................................................ 4-9

4.5. EDITRAN/G ADMINISTRATOR ...................................................................................................................... 4-10 4.5.1. Local environment .............................................................................................................................................................................................................. 4-10 4.5.2. Remote entity profile ........................................................................................................................................................................................................ 4-11 4.5.3. Application profile .............................................................................................................................................................................................................. 4-13 4.5.4. Presentation profile ........................................................................................................................................................................................................... 4-14

EDITRAN/G Windows/Unix User manual INDEX

AUINDRA. All rights reserved. EDITRAN/G

4.5.5. PROFILES GENERIC MONITORING ................................................................................................................................................................................ 4-19

5. ANNEXES ............................................................................................................................................. 5-1

5.1. WILDCARDS USED FOR RECEPTION TARGET ................................................................................................ 5-1

5.2. COMMANDS ..................................................................................................................................................... 5-3 5.2.1. editrang ...................................................................................................................................................................................................................................... 5-3 5.2.2. conver[40|41|50] ................................................................................................................................................................................................................... 5-3 5.2.3. conver51 .................................................................................................................................................................................................................................... 5-3 5.2.4. traduct ........................................................................................................................................................................................................................................ 5-4 5.2.5. igacmd ......................................................................................................................................................................................................................................... 5-5 5.2.6. menug ......................................................................................................................................................................................................................................... 5-6 5.2.7. estcmd ........................................................................................................................................................................................................................................ 5-6 5.2.8. igaperfi........................................................................................................................................................................................................................................ 5-7 5.2.9. modiperfi .................................................................................................................................................................................................................................... 5-7 5.2.10. histcmd ................................................................................................................................................................................................................................ 5-8 5.2.11. igacode................................................................................................................................................................................................................................. 5-9 5.2.12. USER PROGRAMS ............................................................................................................................................................................................................ 5-9

5.2.12.1. List of transmitted or received files ............................................................................................................................................................. 5-10 5.2.13. editrang.out .................................................................................................................................................................................................................... 5-11

5.2.13.1. EDITRAN/G output differentiated by presentation ............................................................................................................................... 5-11 5.2.14. editrang.cfg..................................................................................................................................................................................................................... 5-12 5.2.15. editrang.hlp ..................................................................................................................................................................................................................... 5-12 5.2.16. editrang.msg .................................................................................................................................................................................................................. 5-12 5.2.17. editrang.sts ..................................................................................................................................................................................................................... 5-12 5.2.18. editrang.log ..................................................................................................................................................................................................................... 5-12

5.3. CODES AND MESSAGES FOR THE OPERATOR ............................................................................................. 5-13 5.3.1. EDITRAN/G messages ....................................................................................................................................................................................................... 5-13 5.3.2. EDITRAN/G result codes .................................................................................................................................................................................................. 5-16 5.3.3. Exception codes .................................................................................................................................................................................................................. 5-17

5.4. TABLA DE CODIGOS A7I (REINTENTABLES – NO REINTENTABLES). .......................................................... 5-18

5.5. TABLA DE CODIGOS A7I (GENERACION DE ALARMAS). .............................................................................. 5-18

EDITRAN/G Windows/Unix User manual 1.INTRODUCTION

INDRA. All rights reserved. EDITRAN/G Page 1-1

1. INTRODUCTION

The Indra EDITRAN protocol has two basic components:

Communications platform (EDITRAN/P).

It includes all the services directly related to communication facilities (protocol, interface

with the transmission services X.25, X.28, X.32, RDSI, LU6.2, local networks, etc.).

Application generic interface (EDITRAN/G).

It isolates the communication services provided by EDITRAN/P for the user applications,

and it is the link between them and the transmission processes.

EDITRAN/P transmits file, with a certain structure, from a local extreme node to a

remote one. These files are called transmission and reception buffers.

To obtain transmission buffers from application conventional files and, by contrast, to

obtain these application files from reception buffers, is necessary to use upload a download

programs that, altogether, are called application interface.

In this document are described the procedures for the correct operation of the module

EDITRAN/G.

EDITRAN/G Windows/Unix User manual 2.DESCRIPTION


2. DESCRIPTION

To work with EDITRAN/G, is necessary to maintain a profiles file with information about:

Local entity. For its identification, we use 9 numeric characters.

Remote entity. The same as the previous one.

Presentation application. 6 numeric characters identify it. It is used to define the nature

of the information to be exchanged.

Presentation session. It is identified by a name that is recommended to be defined by

the code (or name) of the remote entity + the presentation application (for example,

9999-PRUEBA). The information contained in this profile comes, to a large degree, from

the three previous profiles that correspond to it.

A presentation session may comprise up to 20 EDITRAN transmission sessions (in native

operating mode). That is to say, the information to be exchanged can be transmitted through

up to 20 circuits at the same time.

To control a presentation session we can use the transmission and reception

presentation status file, that reflects for each session the states through it passes. The

presentation states are the result of the set of transmission states. They change as the

processes occur, and they are useful to allow or deny the requests, and also to establish the

differences among the executed processes. For example, if we get a transmission request and

the state is NOT UPLOADED, the system orders first the uploading and then the transmission.

But if the state is BUFFER UPLOADED, the transmission is ordered right away.

In a log file are written the messages generated by the different EDITRAN/G

components. This file can be monitored and listed filtering by different criteria.

There are some commands, provided during the installation, with which we can invoke

the same functions we invoke with the operator menu.

It is possible to work with EDITRAN/G in compatible mode with versions 4.0, 4.1 and 5.0,

and also in native mode with versions 5.1. The running mode is determined by the remote

EDITRAN/G version of the presentation profile.



2.1. GENERAL FEATURES

In native mode running, there are general features (they are specified in the

presentations profiles) and specific functions (determined by the converters we used).

The following ones, among others, are general functions:

Possibility to process transmission application files with logs of fixed length, variable

length, hybrid and/or binary files.

A presentation session can use up to 20 EDITRAN transmission sessions; hence the

identification of the presentation application doesn’t correspond with the transmission

application defined in EDITRAN. This can also happen in case there is only one

transmission session associated to a presentation session.

The information of a transmission application can be subjected to several presentation

optional functions (chryptography, zipping and EBCDIC/ASCII translation), and it can be

uploaded to specific buffers, up to a maximum of 20, depending on the number of

transmission sessions specified and on the chosen splitting criteria. The buffer logs are

totally uploaded with continuous strings of characters and with control information that

allows remote EDITRAN/G to perform presentation operations conversely.

The system counts the presentation session number between both extreme nodes, so it

increases with every hereinafter exchange. This number will be moved to the number of

exchange session in the transmission and reception buffers, so it won’t be allowed to

transmit if it differs from one extreme node to another.

EDITRAN/P will transmit to the remote node using the transmission sessions specified in

the local node. They will have to match the ones defined in the remote EDITRAN/G. In

these transmission sessions we could define the presentation functions to be performed

by EDITRAN/P, chryptography, zipping and/or CRC, but it doesn’t make sense if they

have already been made to the application data.

In the remote extreme node, the information will be received in buffers, up to a

maximum of 20, depending of the transmission sessions used. This information will

comprise head data, so that the remote EDITRAN/G can check whether the options used

by the transmitter are coherent with the ones of the receiver, and so that it also can

check the features of the received information. The information of the reception buffer

or buffers is downloaded to as many application files as they have been used during the

transmission upload in the other extreme node, after having performed the presentation

functions conversely.



2.2. SPECIFIC FEATURES

The specific features are associated to the remote EDITRAN/G version indicated in the

presentations profiles. Below are listed some of the outstanding features of each version. You

can see the changes document of each version for further information.

2.2.1. Versions 3.0, 3.1

The maximum number of files that can be transmitted is 9999 among homogeneus

environments (Unix, Windows), and 99 for the rest of them.

It transmits files with fixed or variable format, from 1 up to 99999 bytes per log. Among

homogeneous environments, they also can be exchanged in binary mode.

The transmission logic unit (or batch) is the file. That is to say, application synchronisms are

not incorporated.

The zipping and data alphabet is at presentation level, not for file.

It incorporates the possibility of RSA authentication.

2.2.2. Version 4.0

It is allowed to send files in binary mode to any environment.

Features such as zipping and translating apply from this version at a file level.

It incorporates optional translation in reception.

The user will be able to define tables to adapt the EDITRAN charsets to the local ones of

each entity.

It incorporates PKI cyphering.

2.2.3. Version 4.1

Signature verification of the files to be transmitted.

Triple DES chryptography.

By each presentation, a file with a list of the transmitted/received files is generated.

It incorporates sending with delivery confirmation: EDITRAN/IC.

Integration with the subsystem EDITRAN/GC for the external key exchange.

2.2.4. Version 5.0

There is no limit on the number of files that can be sent in every transmission.

There is no limit on the size of the application file. The system supports files up to 2 GBytes.

Is not necessary to define the remote entity alphabet.

2.2.5. Version 5.1

It incorporates sending with remote downloading confirmation.

EDITRAN/G Windows/Unix User manual 3.EDITRAN/G MANAGEMENT (UNIX).

INDRA. All rights reserved EDITRAN/G Page 3-1

3. EDITRAN/G MANAGEMENT (UNIX).

When running menug in the EDITRAN folder, the general menu of the EDITRAN/G

manager will be activated, as we can see below:

+-----------------------------------------------------------------------------+

| dd/mm/aaaa - GESTOR DE EDItran/G - EDItran/G V#.#.# |

| 10:14:18 |

+-----------------------------------------------------------------------------+

| |

| |

| |

| 1.- OPERADOR DE EDITRAN/G |

| |

| 2.- GESTOR DE FICHEROS DE CONTROL |

| |

| 3.- ADMINISTRADOR DE EDITRAN/G |

| |

| OPCION : |

| |

| |

| |

| |

| |

| |

| |

| F1 ? Ayuda On-Line F2 Campo por defecto F3 Fin entrada |

| F4 Pantalla por defecto F6 Shell OS ESC Menu previo |

+-----------------------------------------------------------------------------+

If is the first time we run EDITRAN/G, we will have to enter the data of the local

environment (see section EDITRAN/G ADMINISTRATOR) and to reboot the EDITRAN system.

3.1. OPERATION INTERFACE

In the screenshots included in this document, the different types of fields are

represented in the following way:

3.1.1. SCREENS

In the screens of the EDITRAN/G menu system, we can distinguish three areas:

+-----------------------------------------------------------------------------+

| dd/mm/aaaa - GESTOR DE EDItran/G - EDItran/G V#.## |

|(1)00:00:00 - OPERADOR DE EDItran/G - |

+-----------------------------------------------------------------------------+

| 1.- CARGAR PRESENTACION DE EMISION |

| 2.- INICIALIZAR PRESENTACION DE EMISION |

| 3.- EMITIR PRESENTACION |

| 4.- INTERRUMPIR PRESENTACION DE EMISION |

| 5.- INICIALIZAR PRESENTACION DE RECEPCION |

| 6.- DESCARGAR PRESENTACION DE RECEPCION |

| 7.- RECIBIR PRESENTACION |

| 8.- INTERRUMPIR PRESENTACION DE RECEPCION |

| C.- CONSULTA DE ESTADOS DE PRESENTACION |

| OPCION : |

| PRESENTACION : |

| |

| |


|(2) F4 Pantalla por defecto F6 Shell OS ESC Menu previo |

+-----------------------------------------------------------------------------+

| PRESENTACION : ESTADO EMISION : |

| ESTADO RECEPCION : |

|(3) |

+-----------------------------------------------------------------------------+



(1) Title

In this area, we can see general information about EDITRAN/G:

Current date and time (in the moment we activate the screen).

Screen object: administrator, operator, etc.

Version and Operating System.

(2) Options

In this area can appear the different menu options, the parameters to be filled by the

operator, or the results of the performed requests.

(3) Information

In this area we can see the progress information of the presentations that the system

sends to the operator:

Presentation.

Transmission and reception status.

Text with information about the progress.

3.1.2. HELP

EDITRAN/G has a help system sensitive to context. In this way, when we click on F1 or ?,

a window with the help text associated to the field or to the screen where the cursor is at

that time will appear.

3.1.3. KEYS

In EDITRAN/G, and within the menu, we can use the following keys:

F1

?

Help sensitive to context.

F2 Introduces the default values of the current field, whenever possible.

F3 Ends the input of the current screen, validating all the fields.

F4 Introduces the default values of the current screen, whenever possible.

F6 Performs an exit to the operating system to execute other commands (shell), leaving

EDITRAN/G resident. To go back to EDITRAN/G, we have to execute the exit command.

Enter Ends the input in the current field, updating its value. If we don’t enter any value, it inserts

the one of the last request.

Spacebar Selects the value of the field from a list of values:

A (o) B ( ) C ( )

or activates/deactivates the value of the field with only two possible values:

D [X]

Esc Aborts the input and goes back to the previous menu.

Delete Deletes the character before the cursor.

Tab Goes to the next field, without having to update or modify its value.

Arrows They move the cursor in the screen to the next/previous field, or to the next/previous

value within the field.

PgUp

Control-U

Page up.

PgDn

Control-D

Page down.



3.1.4. SELECTION BY LIST

In the Operator and Administrator menus described below, the user must introduce a

name for the presentation. In these cases, if instead a name we write a search filter, it will

display a screen with the list of presentations that match the given mask.

The following screen is an example in which transmissions are launched from the list

generated when we have selected the presentations that end with 14 (*14).

┌──────────────────────────────────────────────────────────────────────────────┐

│ dd/mm/aaaa - GESTOR DE EDItran/G - EDItran/G V#.#.# │

│ 16:32:59 - OPERADOR DE EDItran/G - │

├──────────────────────────────────────────────────────────────────────────────┤

│ PRESENTACION │

│┌────────────────────────────────────────────────────────────────────────────┐│

││ HP-TCP-14 ENVIADO ││

││ S LINUX-14 ││

││ AIX-TCP-14 ││

│└────────────────────────────────────────────────────────────────────────────┘│

│ │

│ │

│ │

│ │

│ │

│ │

│ │

│ Enter Seleccionar ESC Cancelar │

│ PgUp Ctrl-U Pagina Anterior PgDn Ctrl-D Pagina Siguiente │

├──────────────────────────────────────────────────────────────────────────────┤

│ PRESENTACION : HP-TCP-14 EMISION : NO CARGADA │

│ RECEPCION : NO CARGADA │

│ Error en proceso de usuario previo a emision USER_PRVEMI │

└──────────────────────────────────────────────────────────────────────────────┘

3.2. EDITRAN/G OPERATOR

To operate on the exchange presentations, we must choose option 1 from the main

menu EDITRAN/G MANAGER. The following options will be displayed:

+-----------------------------------------------------------------------------+


| 10:15:01 - OPERADOR DE EDItran/G - |

+-----------------------------------------------------------------------------+

| 1.- CARGAR PRESENTACION DE EMISION |

| 2.- INICIALIZAR PRESENTACION DE EMISION |

| 3.- EMITIR PRESENTACION |

| 4.- INTERRUMPIR PRESENTACION DE EMISION |

| 5.- INICIALIZAR PRESENTACION DE RECEPCION |

| 6.- DESCARGAR PRESENTACION DE RECEPCION |

| 7.- RECIBIR PRESENTACION |

| 8.- INTERRUMPIR PRESENTACION DE RECEPCION |

| C.- CONSULTA DE ESTADOS DE PRESENTACION |

| OPCION : |

| PRESENTACION : |

| |

| |



+-----------------------------------------------------------------------------+

| PRESENTACION : ESTADO EMISION : |

| ESTADO RECEPCION : |

| |

+-----------------------------------------------------------------------------+



3.2.1. UPLOADING TRANSMISSION PRESENTATION

The system validates the state of the transmission presentation session (that is to say,

the state of all the transmission sessions that compose it).

The upload is performed if the state of the session is NOT UPLOADED (NO CARGADO)

(see the meaning of the different states). At the end of the process, it becomes UPLOADED

BUFFER (CARGADO TAMPON).

The unique procedure before the transmission is launched.

If the state of the session is NOT UPLOADED (NO CARGADO), we must add 1 to the

presentation number, whenever SESSION INCREASE (INCREMENTO SESIÓN) is S. This

presentation number, depending on the converters used, passes to the exchange number of

the control log of the transmission in the transmission buffer or buffers. In this case, it must

match the one registered in the reception buffers in the remote node.

The converter program previous to the transmission, specified in the corresponding

session profile, is invoked. Depending on the features of every converter, several application

and/or presentation processes can be performed. In any case, we will obtain one or several

transmission buffers whose state is BUFFER UPLOADED (CARGADO TAMPON).

EDITRAN is notified about the buffers preparation, with as many A8R messages as

transmission sessions have been uploaded. The state then becomes BUFFER UPLOADED

(CARGADO TAMPÓN).

The user program previous to transmission, defined in the profile, is invoked.

The physical name of the buffer file and the length of the log are taken from the

corresponding EDITRAN transmission session profile.

3.2.2. INITIALIZING TRANSMISSION PRESENTATION

The process is performed if the state of the presentation is transmitted,

INTERRUPTED OR BUFFER UPLOADED (TRANSMITIDA, INTERRUMPIDA o CARGADO

TAMPÓN). At the end of the process, it becomes NOT UPLOADED (NO CARGADA).

This process is automatically performed when the transmission of all the sessions

associated to the presentation is ended, or when the user wants to cancel a pending

transmission. The transmission buffer files associated to the presentation are deleted.

3.2.3. TRANSMITTING PRESENTATION

The state of the presentation will have to be NOT UPLOADED, BUFFER UPLOADER

OR INTERRUPTED (NO CARGADA, CARGADO TAMPON o INTERRUMPIDA). If NOT

UPLOADED (NO CARGADA) performs the process previous to transmission, as we saw for

the uploading, the state will become BUFFER UPLOADED (CARGADO TAMPON).

Once the state become BUFFER UPLOADED (CARGADO TAMPON), the system sends

EDITRAN as many A1R as transmission sessions compose the presentation. The same thing is

done for INTERRUPTED (INTERRUMPIDA), as we are willing to continue with a previously

interrupted session. The state of the session will become TRANSMITTING

(TRANSMITIENDO).



3.2.4. INTERRUPTING EMISSION PRESENTATION

It is to interrupt the current transmission, whose state must be TRANSMITTING

(TRANSMITIENDO) or INTERRUPTED (INTERRUMPIDO), for which are sent to EDITRAN as

many EDP as transmission sessions of the presentation there are. EDITRAN returns to

EDITRAN/G the control of the transmission buffers. The state of the session becomes

INTERRUPTED (INTERRUMPIDO).

3.2.5. INITIALIZING RECEPTION PRESENTATION

The estate of the reception presentation is validated. That is to say, the state of all the

transmission sessions that compose it.

The initialization is executed if the state of the session is TRANSMITTED OR

INTERRUPTED (TRANSMITIDO o INTERRUMPIDO). At the end of the process, it becomes

NOT UPLOADED (NO CARGADO).

3.2.6. DOWNLOADING RECEPTION PRESENTATION

The process is performed if the state of the session is TRANSMITTED OR

INTERRUPTED (TRANSMITIDA o INTERRUMPIDO). At the end of the process, it becomes

NOT UPLOADED (NO CARGADO).

If there are several transmission sessions in the presentation, and if the request comes

from EDITRAN, the system indicates the end of reception for only one of them, whose state

becomes TRANSMITTED (TRANSMITIDO); at this moment, EDITRAN/G can know the real

number of sessions used by the transmission remote node (this data is displayed in a head

log) and it deletes the log of states of the presentation. When it comes to the last spare one,

the process of downloading the presentation begins.

In any case, the unique procedure after reception is launched. The converter program,

along with the user program after transmission, is invoked, as long as they exist in the

presentation profile.

The reception buffers associated to the presentation are deleted.

3.2.7. RECEIVING PRESENTATION

The estate of the presentation must be NOT UPLOADED, TRANSMITTED or

INTERRUPTED (NO CARGADA, TRANSMITIDA o INTERRUMPIDA). If it is NOT UPLOADED

(NO CARGADA) or TRANSMITTED (TRANSMITIDA), it performs the process previous to

reception, as it has been seen. So it would become NOT UPLOADED (NO CARGADA).

Once the buffer is uploaded (CARGADO TAMPON), the system sends to EDITRAN as

many A1R as presentation transmission sessions have been defined, as we don’t know

exactly how many of them will be used by the transmitter. The same action is performed for

INTERRUPTED (INTERRUMPIDA), as it is manifested the will to continue with a session

previously interrupted. The status of the session becomes TRANSMITTING

(TRANSMITIENDO).

3.2.8. INTERRUPTING RECEPTION PRESENTATION

It is to interrupt the reception in progress, that will have to be TRANSMITTING

(TRANSMITIENDO), for which they are sent to EDITRAN as many EDR as transmission



sessions has the presentation. EDITRAN gives back to EDITRAN/G the control of the reception

buffers. The status of the session becomes INTERRUPTED (INTERRUMPIDO).

3.2.9. MONITORING PRESENTATION STATUS

To monitor a specific presentation, we have to tap the presentation and click on Enter.

In the information area of the screen (lower part) will appear the information of the emission

and reception status for the requested presentation.



3.3. CONTROL FILES MANAGEMENT

+-----------------------------------------------------------------------------+


| 10:20:00 - GESTOR DE FICHEROS DE CONTROL - |

+-----------------------------------------------------------------------------+

| |

| |

| |

| 1.- CONSULTA DE ESTADOS DE PRESENTACION |

| |

| 2.- MODIFICACION DE ESTADOS DE PRESENTACION |

| |

| 3.- CONSULTA DE LOG |

| |

| OPCION : |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

Select the desired option and click on Enter.

3.3.1. MONITORING PRESENTATION STATUS

+-----------------------------------------------------------------------------+

| dd/mm/aaaa - GESTOR DE FICHEROS DE CONTROL - EDItran/G V#.#.# |

| 10:20:55 - CONSULTA DE PRESENTACION - |

+-----------------------------------------------------------------------------+

| |

| |

| |

| |

| PRESENTACION (E/R) : |

| |

| PRESENTACION : |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+



Select the presentation to be monitored and click on Enter.

+-----------------------------------------------------------------------------+

| dd/mm/aaaa - CONSULTA DE PRESENTACION - EDItran/G V#.#.# |

| 10:21:46 - EMISORA - |

+-----------------------------------------------------------------------------+

| PRESENTACION : E TEST ESTADO PRESENTACION : INTERRUMPIDA |

| INICIO : 24/10/2000 08:07:26 No PRESENTACION : 0957 |

| FIN : 00/00/0000 00:00:00 PRESENTACION PENDIENTE : No |

| |

|SESION No ULT CAMBIO ESTADO ESTADO |

+-----------------------------------------------------------------------------+

|TEST 0957 24/10/2000 08:07:40 INTERRUMPIDO |

+-----------------------------------------------------------------------------+

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| PgUp Ctrl-U Pagina Anterior PgDn Ctrl-D Pagina Siguiente ESC Salir |

+-----------------------------------------------------------------------------+

PRESENTATION STATUS

It can have the following values:

NOT UPLOADED (NO

CARGADA)

None of the buffer of the related EDITRAN sessions is uploaded.

CSB UPLOADED

(CARGADO CSB)

Intermediate status before uploading buffer.

BUFFER UPLOADED

(CARGADO TAMPÓN)

Some of the buffers of the related EDITRAN sessions are

uploaded.

TRANSMITTING

(TRANSMITIENDO)

Some of the EDITRAN sessions are transmitting.

TRANSMITTED

(TRANSMITIDA)

All the buffers have been transmitted but not uploaded.

INTERRUPTED

(INTERRUMPIDA)

Some of the related EDITRAN sessions are interrupted.

PRESENTATION IS PENDING

Its value is Yes (Sí) when there has been an uploaded but it has not been yet emitted.

PRESENTATION

The presentation number is initialized to 1. It increases in one unit every time a

presentation transmission upload is performed. More specifically, when the transmission

presentation status changes from NOT UPLOADED (NO CARGADO) to BUFFER

UPLOADED (CARGADO TAMPÓN), despite this status automatically becomes first

BUFFER UPLOADED (CARGADO TAMPON) and then TRANSMITTING (TRANSMITIENDO).



EDITRAN SESSIONS

Appear as many lines as transmission sessions are used in the presentation, up to 20.

They appear in each line: session and description of the session status, and also date

and time of the change of status. The emission or reception statuses can be:

NOT UPLOADED (NO

CARGADO)

When the system has performed the process after session emission

of reception.

TRANSMITTING

(TRANSMITIENDO)

When the emission or reception has been requested to EDITRAN.

TRANSMITTED

(TRANSMITIDO)

When an end of emission or reception comes from EDITRAN,

reporting the correct transmission of the buffer.

BUFFER UPLOADED

(CARGADO TAMPÓN)

When the emission uploading is performed. Not available for

EDITRAN.

INTERRUPTED

(INTERRUMPIDO)

When we receive an EDITRAN/G operator interruption, or when we

receive an A7I from EDITRAN/P.

3.3.2. MODIFICATION OF PRESENTATION STATUSES

Modifying the status of the presentations is an extra operation that must be performed

only in anomalous circumstances, having activated the option “Increase presentation number

(Incrementar número de presentación)”.

+-----------------------------------------------------------------------------+


| 10:23:30 - MODIFICACION DE PRESENTACION - |

+-----------------------------------------------------------------------------+

| |

| |

| |

| |

| PRESENTACION (E/R) : |

| |

| PRESENTACION : |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+



The presentation session number is displayed, and it can be modified. The system will

ask whether we want to initialize the presentation statuses. We will enter Y (S) or N (N); if we

enter S, the statuses will become NOT UPLOADED (NO CARGADA). With Enter we will perform

the modification, and with Esc we will cancel it.

+-----------------------------------------------------------------------------+

| dd/mm/aaaa - MODIFICACION DE PRESENTACION - EDItran/G V#.#.# |

| 10:24:09 - EMISORA - |

+-----------------------------------------------------------------------------+

| |

| PRESENTACION : E TEST |

| |

| |

| |

| Esta opcion requiere el dialogo previo con el operador |

| del centro remoto para la resincronizacion del numero |

| de sesion y estados de presentacion entre los extremos |

| |

| Pulse ESC para no realizar la modificacion |

| |

| |

| |

| No SESION DE PRESENTACION : 0957 |

| |

| INICIALIZAR ESTADO PRESENTACION (S/N) : N |

| |



+-----------------------------------------------------------------------------+

3.3.3. LOG MONITORING

+-----------------------------------------------------------------------------+


| 10:24:49 - CONSULTA DE LOG - |

+-----------------------------------------------------------------------------+

| |

| |

| PRESENTACION : |

| |

| FECHA (DD/MM/AA) : / / |

| |

| HORA (HH/MM/SS) : : : |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

These data are used in the selection criteria for log monitoring. The system will display

messages generated from the entered date.

PRESENTATION (PRESENTACIÓN): it can be a particular one, a mask (for example P* to

display all that begin with P) or zeros or blank for all.

DATE (FECHA): from a particular date, or no date if we want the latest registered

information to be displayed.

TIME (HORA): from a particular time within a date.



+-----------------------------------------------------------------------------+


| 10:26:35 - CONSULTA DE LOG - |

+-----------------------------------------------------------------------------+

| PRESENTACION : TEST FECHA : 01/01/01 HORA : 00:00:00 |

| |

|PRESENTACION FECHA HORA MENSAJE |

+-----------------------------------------------------------------------------+

|TEST 22/05/2013 13:21:13 Informa carga de tampon a EDItran (A8R) ETEST|

|TEST 22/05/2013 13:21:13 Solicita emision a EDItran (A1R) ETEST |

|TEST 22/05/2013 13:21:24 Sesion EDItran emitida (A3P) ETEST |

|TEST 22/05/2013 13:21:24 Fin posterior emision sesion EDItran (A3R) ET|

|TEST 22/05/2013 13:21:24 Peticion de inicializacion de emision |

|TEST 22/05/2013 13:21:24 Inicializacion de emision correcta y finaliza|

|TEST 22/05/2013 13:21:24 Lanza proceso de usuario posterior a emision |

|TEST 22/05/2013 13:21:24 Proceso de usuario posterior a emision finali|

|TEST 22/05/2013 13:21:24 Peticion de emision |

|TEST 22/05/2013 13:21:24 Lanza proceso de usuario previo a emision USE|

|TEST 22/05/2013 13:21:24 Proceso de usuario previo a emision finalizad|

|TEST 22/05/2013 13:21:24 Conversion de emision correcta y finalizada |

|TEST 22/05/2013 13:21:25 Carga de presentacion emisora correcta y fina|

+-----------------------------------------------------------------------------+


+-----------------------------------------------------------------------------+

One we have entered log monitoring, we will navigate the menu using PgUp or Ctrl-U to

see the previous page, and y PgDn or Ctrl-D to see the next page. With Esc we will go back to

the monitoring options screen.

It will show the presentation session, and the date, time and text of the message.

3.4. EDITRAN/G ADMINISTRATOR

We can access the EDITRAN/G administrator choosing the option 3 from the main menu.

The following screen will be displayed:

+-----------------------------------------------------------------------------+


| 10:27:44 - ADMINISTRADOR DE EDItran/G - |

+-----------------------------------------------------------------------------+

| |

| |

| 1.- ENTORNO LOCAL |

| |

| 2.- PERFIL ENTIDAD REMOTA |

| |

| 3.- PERFIL APLICACION |

| |

| 4.- PERFIL PRESENTACION |

| |

| 5.- CONSULTA GENERICA DE PERFILES |

| |

| OPCION : |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+



3.4.1. LOCAL ENVIRONMENT

Only in EDITRAN/G profiles exists a local environment log that must be registered during

the installation; after that, we can modify or monitor it.

+-----------------------------------------------------------------------------+

| dd/mm/aaaa - ADMINISTRADOR DE EDItran/G - EDItran/G V#.#.# |

| 10:28:40 - ENTORNO LOCAL - |

+-----------------------------------------------------------------------------+

| |

| |

| |

| A.- ALTA |

| |

| C.- CONSULTA |

| |

| M.- MODIFICACION |

| |

| OPCION : |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

+-----------------------------------------------------------------------------+


| 10:29:16 - ENTORNO LOCAL - |

+-----------------------------------------------------------------------------+

| |

| |

| CODIGO EDITRAN/G LOCAL : 000000120 |

| |

| NOMBRE EDITRAN/G LOCAL : EDITRAN |

| |

| VERSION EDITRAN/G LOCAL : #.# |

| |

| VERSION EDITRAN/P LOCAL : #.# |

| |

| |

| |

| |

| |

| |

| |

| Pulse una tecla para continuar |

+-----------------------------------------------------------------------------+

LOCAL EDITRAN/G CODE (CÓDIGO EDITRAN/G LOCAL): the same as in EDITRAN/P.

LOCAL EDITRAN/G NAME (NOMBRE EDITRAN/G LOCAL)

LOCAL EDITRAN/G VERSION (VERSION EDITRAN/G LOCAL)

LOCAL EDITRAN/P VERSION (VERSION EDITRAN/P LOCAL)

With Enter we will register it; with Esc we will cancel. The values entered here will be

taken as default values when registering presentations.

Modifying and monitoring the local environment is done like registering, but in this case

the corresponding profile must have been created previously.

The local environment cannot be cancelled.



3.4.2. REMOTE ENTITY PROFILE

+-----------------------------------------------------------------------------+


| 10:31:39 - ENTIDAD REMOTA - |

+-----------------------------------------------------------------------------+

| |

| |

| A.- ALTA |

| |

| B.- BAJA |

| |

| C.- CONSULTA |

| |


| |

| |

| OPCION : REMOTO : |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

We have to enter the chosen option and the remote entity code, that must be the same

as it is used in EDITRAN/P.

+-----------------------------------------------------------------------------+


| 10:32:27 - ENTIDAD REMOTA - |

+-----------------------------------------------------------------------------+

| |

| REMOTO : 000099940 |

| |

| DESCRIPCION : TEST |

| VERSION EDItran/G REMOTA : 4.1 |

| ASCII/EBCDIC (A/E) : A |

| |

| - PARAMETROS DE CRIPTOGRAFIA - |

| CRIPTOGRAFIA (S/N) : S |

| VERSION DE CRIPTOGRAFIA : 2.2 |

| ALGORITMO CONFIDENCIALIDAD : DES |

| ALGORITMO AUTENTICACION : DES |

| GESTION CLAVES V3.0 (S/N) : |

| CLAVE LOCAL : |

| CLAVE REMOTA : |

| PASSWD: |

| |

| |


+-----------------------------------------------------------------------------+

DESCRIPTION (DESCRIPCIÓN)

Descriptive name for the remote entity.

REMOTE EDITRAN/G VERSION (VERSION EDITRAN/G REMOTA)

4.0 If the remote entity is going to use EDITRAN/G V4.0.






ASCII/EBCDIC

A ASCII

E EBCDIC

Is necessary to provide the charset used by the remote server, ASCII or EBCDIC, as

long as the remote version is lower than 5.0. This does not imply that a data

translation will be performed, as this is determined in the list of files to be

transmitted.

CRYPTOGRAPHY (Y/N) (CRIPTOGRAFIA (S/N))

S If we wish to use EDITRAN/G cryptography.

N If we don’t wish to use EDITRAN/G cryptography.

CRYPTOGRAPHY VERSION (VERSIÓN CRIPTOGRAFÍA)

This field is mandatory if cryptography is activated.

2.2 For the security subsystem of the EDITRAN/P 2.2 version.

3.0 When the keys Exchange is performed out of EDITRAN.

CONFIDENTIALITY ALGORITHM (ALGORITMO CONFIDENCIALIDAD)

Algorithm used for data encryption. We will leave it blank if we don’t want to use data

encryption.

DES if we want to use DES encryption.

TD2 TRIPLE-DES encryption with double key.

TD3 TRIPLE-DES encryption with triple key.

AUTHENTICATION ALGORITHM (ALGORITMO AUTENTICACIÓN)

Algorithm used for key encryption. Mandatory if cryptography is activated.

DES if you wish to authenticate the extreme nodes (valid for versions 2.2 and 3.0).

RSA if you wish to authenticate the extreme nodes (valid for version 3.0).

PKI if you wish to authenticate the extreme nodes (valid for version 3.0).

SNC if you wish to authenticate the extreme nodes with the SNCE cryptography

model. This option is valid only in HP-UX environments.

V3.0 KEYS MANAGEMENT (GESTIÓN CLAVES V3.0)

When we chose this facility in 3.0 cryptography versions, the module EDITRAN/GC

will be the one to provide the tags corresponding to the active keys for the

subsystems indicated in the parameters LOCAL KEY (CLAVE LOCAL) and REMOTE

KEY (CLAVE REMOTA).

Y (S) Labels provided by EDITRAN/GC.

N (N) Labels provided by the user.

LOCAL KEY (CLAVE LOCAL)

Label of the DES auxiliary key, private RSA or PKI certificate alias. It is mandatory

when the cryptography version is 3.0 and if there is authentication.

REMOTE KEY (CLAVE REMOTA)

Label of the DES auxiliary key, public RSA or remote DN. It is mandatory when the

cryptography version is 3.0 and if there is authentication.

PASSWD

Pin used to access an own certificate. It is mandatory when there is PKI

authentication.

With Enter we will perform the registration. With Esc we will cancel it. The value of the

data from a remote entity will pass to the presentations of this entity, when they are

registered, as values by default.



Modification and monitoring of a remote entity profile are performed in the same way as

registration, despite the profile must already exist. The modified values are not passed to the

concurrent ones of the presentations within the same entity.

When we delete a remote entity profile, appears a screen like the one described in the

first place. With Enter we confirm the deletion, and with Esc we cancel it.

In every option, except registration, we can use filters to select the presentation from

the list.

3.4.3. APPLICATION PROFILE

+-----------------------------------------------------------------------------+


| 10:46:03 - APLICACION - |

+-----------------------------------------------------------------------------+

| |

| |

| A.- ALTA |

| |

| B.- BAJA |

| |

| C.- CONSULTA |

| |


| |

| |

| OPCION : APLICACION : |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

+-----------------------------------------------------------------------------+


| 10:59:37 - APLICACION - |

+-----------------------------------------------------------------------------+

| APLICACIÓN : PRUEBA |

| DESCRIPCION : Pruebas |

| TABLA CONVERSION EMISION : |

| TABLA CONVERSION RECEPCION : |

| |

| - PROGRAMAS DE USUARIO - |

| PREVIO EMISION : USER_PRVEMI |

| PREVIO RECEPCION : USER_PRVREC |

| POSTERIOR EMISION : USER_PSTEMI |

| POSTERIOR RECEPCION : USER_PSTREC |

| EXCEPCION : USER_EXCEPT |

| |

| |

| |

| |

| |


+-----------------------------------------------------------------------------+

DESCRIPTION (DESCRIPCIÓN)

Name of the presentation application.



CONVERSION TABLES (TABLAS DE CONVERSIÓN)

Text files, edited by the user, with the correspondance table between the

codification scheme of characters, both local and the one belonging to EDITRAN, and

both used for transmission and for reception. Each line will be from the following

type, being the characters defined in hexadecimal:

<character-EDITRAN> <character-local>

If no local translation is needed, these fields can be left blank. In a different case, we

will use the file name without putting the last character, as it is used only to identify

the alphabet: ‘A’ for ASCII, or ‘E’ for EBCDIC. For example, if the user creates the file

mitablaA to enter ASCII characters, in the profile it would be necessary to put only

mitabla.

USER PROGRAMS (PROGRAMAS DE USUARIO)

They are invoked by EDITRAN/G in the processes before and after transmission and

reception, and also exception.

These programs will be provided by the user and they will be invoked during the

presentation processes.

The arguments to invoke these programs are described in the sections about user

programs.

If we want to perform any action, it will have to be included in the corresponding

procedure.

With Enter we perform the registration. With Esc we quit it. The values of the data from

a presentation application are passed to the presentations of that entity, as values by default,

when they are registered.

Modification and monitoring of a presentation application profile is performed in the

same way as registration, but the profile must already exist. The modified values are not

passed to the concurrent ones from the presentations of the same entity.

When deleting an applicaton profile, will appear a screen like the one described before.

With Enter we confirm the deletion, and with Esc we cancel it.



3.4.4. PRESENTATION

+-----------------------------------------------------------------------------+


| 11:08:52 - PRESENTACION - |

+-----------------------------------------------------------------------------+

| |

| |

| A.- ALTA |

| |

| B.- BAJA |

| |

| C.- CONSULTA |

| |


| |

| |

| OPCION : |

| PRESENTACION : |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

We have to enter the desired option, and also the codes of both the remote entity and

the presentation application. If these profiles already exist, the screens will take their data as

a template. If they don’t exist, the user will have to fill them at that time.

To navigate them we have to use the arrows, Esc to cancel the registration, Enter to go

on and to perform the registration, and F3 to end filling data in the current screen and thus

validate all the fields. All the data filled in any case are validated, except if we click on Esc.

PRESENTATION AND LOCAL ENVIRONMENT DATA (DATOS DE LA PRESENTACIÓN Y

DEL LOCAL)

+-----------------------------------------------------------------------------+


| 11:10:24 - CONSULTA PRESENTACION - |

+-----------------------------------------------------------------------------+

| |

| PRESENTACION : TEST |

| |

| REMOTO : 000099910 ES UNA ENTIDAD EDITRAN (S/N) : S |

| APLICACION : PRUEBA |

| |

| - DATOS DEL LOCAL - |

| |

| CODIGO EDITRAN/G LOCAL : 000000120 |

| |

| NOMBRE EDITRAN/G LOCAL : editran |

| |

| |

| |

| |

| |

| |

| |


+-----------------------------------------------------------------------------+



REMOTE NODE DATA (DATOS DEL REMOTO)

+-----------------------------------------------------------------------------+



+-----------------------------------------------------------------------------+


| |

| - DATOS DEL REMOTO - |

| DESCRIPCION : TEST |

| VERSION EDItran/G REMOTA : 5.1 |

| ASCII/EBCDIC (A/E) : A |

| |

| - PARAMETROS DE CRIPTOGRAFIA - |

| CRIPTOGRAFIA (S/N) : S |

| VERSION DE CRIPTOGRAFIA : 2.2 |

| ALGORITMO CONFIDENCIALIDAD : DES |

| ALGORITMO AUTENTICACION : DES |

| GESTION CLAVES V3.0 (S/N) : |

| CLAVE LOCAL : |

| CLAVE REMOTA : |

| PASSWD: |

| |

| |


+-----------------------------------------------------------------------------+

They are the ones described in the section REMOTE ENTITY PROFILE (PERFIL

ENTIDAD REMOTA).

APPLICATION DATA (DATOS DE LA APLICACIÓN)

+-----------------------------------------------------------------------------+



+-----------------------------------------------------------------------------+


| |

| - DATOS DE LA APLICACIÓN - |

| DESCRIPCION : Pruebas |

| TABLA CONVERSION EMISION : |

| TABLA CONVERSION RECEPCION : |

| |







| |

| |

| |

| |

| |

| |


+-----------------------------------------------------------------------------+

They are the ones described in the section APPLICATION PROFILE (PERFIL

APLICACIÓN).



PRESENTATION DATA (DATOS DE LA PRESENTACIÓN)

+-----------------------------------------------------------------------------+



+-----------------------------------------------------------------------------+


| |

| - DATOS DE LA PRESENTACION - |

| |

| INCREMENTAR No PRESENTACION (S/N) : N |

| TIPO DE CARGA (S/N) : N |

| PEDIR CONFIRMACION DESCARGA (S/N) : N |

| NUMERO DE SESIONES DE TRANSMISION : 01 |

| CRITERIO DE DIVISION (V/S/F/N) : N (Vol/Sinc/Fich/Ninguno) |

| |

| - APLICACIONES EDItran/P - |

| 1: PRUEBA 2: 3: 4: 5: |

| 6: 7: 8: 9: 10: |

| 11: 12: 13: 14: 15: |

| 16: 17: 18: 19: 20: |

| |

| |

| |

| |


+-----------------------------------------------------------------------------+

INCREASE PRESENTATION NUMBER (Y/N) (INCREMENTAR Nº PRESENTACIÓN

(S/N))

It specifies wheter it is necessary to increase the presentation number, and thus the

interchange session number of each EDITRAN/P sessions associated to this one en

the previous transmission and reception processes.

TYPE OF LOAD (TIPO DE CARGA)

With an accumulative type of load, it is allowed to reload the buffer with new

application files, as long as the transmission has not begun yet. The accumulative

load requires a unique transmission session to be used.

N A single load per transmission.

A Allows to load several times before transmitting.

ASK FOR LOAD CONFIRMATION (PEDIR CONFIRMACIÓN DESCARGA)

With a remote download confirmation the transmission won’t be terminated until the

result of the downloading is confirmed from the remote node. When the download

ends with an error, the user process after reception will receive, in the parameter

“result”, the value indicating it. During reception, the result of the last download is

returned, if the remote node asks for it.

NUMBER OF TRANSMISSION SESSIONS (NÚMERO DE SESIONES DE

TRANSMISIÓN)

Number of EDITRAN/P sessions associated to the EDITRAN/G presentation. Then we

must specify which ones they are. These sessions must have been registered

previously. All EDITRAN/P sessions will have the same local and remote codes than

the EDITRAN/G presentation.



DIVISION CRITERION (V/S/F/N) (CRITERIO DE DIVISIÓN (V/S/F/N))

It is only necessary if we are going to use several trasnsmission sessions for the

presentation one. We can specify the following values:

V The information would be distributed equally among the different buffers, with a

mínimum of 400.000 octets by each buffer. This means that some of the defined

transmission sessions might not be used in the presentation.

S The distribution is made by batch, marked by syncpoints, depending on the

converter. Sequential complete batches would be assigned to each transmission

buffer.

F The distribution is made by file. Sequential complete files would be assigned to

each transmission buffer.

N Distribution is not made.

PRESENTATION TRANSMISSION FILES (FICHEROS DE EMISION DE LA

PRESENTACION)

+-----------------------------------------------------------------------------+



+-----------------------------------------------------------------------------+


| |

| - FICHEROS DE EMISION DE LA PRESENTACION - |

| C F A T D |

| O M L R E |

| M T F A L LONG NOMBRE |

+-----------------------------------------------------------------------------+

| N F E S N 04020 /home/editran/origen/* |

| |

| |

+-----------------------------------------------------------------------------+

| COMPROBAR LAS FIRMAS DIGITALES CON EDITRANFF (S/N): N |

| |

| - DESTINO DE RECEPCION - |

| /home/editran/destino/ |

| DELIMITADOR (D/U/N) : N TRADUCIR(A/E/N): |

| |

| |


+-----------------------------------------------------------------------------+

This section has 7 columns:

First column: COM

It refers to the zipping of the file(s) we want to send. It can have the following

values:

F Zipping is activated.

N Zipping is inhibited.

Second column: FMT

It refers to the format of the files we want to send. It can have the following values:

F Fixed. The application files are read as fixed length records. Length is determined

by the following parameter.

In this format, there is the optional possibility of deleting delimitators (newline).



V Variable. Application files are read line by line, and the line delimiter is CR-LF in

PC’s and CR in UNIX machines. These delimiters are not sent to the remote system;

during the remote conversión process, the inverse operation is performed. The

delimitation characters appropriate for the reception system are inserted. This is the

format that should be used to transmit text files between heterogeneous

environments (UNIX PC, UNIX CICS, and so on).

H Hybrid. Files are read as variable and they are sent to the remote system as fixed,

filling with blanks each line until the log length defined in the field LONG is

completed.

B Binary. Transparent mode (without transformations).

Only for homogeneous environments if the remote version is 4.1 or higher.

Third column: ALF

It refers to the alphabet of the file(s) we want to send. It can have the following

values:

A Ascii. The file(s) data are in Ascii.

E Ebcdic. The file(s) data are in Ebcdic.

Fourth column: TRA

It refers to whether we want to translate the alphabet of the files we wish to send. It

can have the following values:

S if we want to translate it.

N if we don’t want to translate it.

Fifth column: DEL

For files with fixed format, it indicates that each record ends with a newline that

must be deleted from the data sent to the remote node.

Sixth column: LONG

Se refiere a la longitud de registro del fichero o ficheros que queremos enviar.

Seventh column: NAME (NOMBRE)

It refers to the path where are the file(s) to be sent.

CHECKING DIGITAL SIGNATURES WITH EDITRAN/FF (COMPROBAR LAS FIRMAS

DIGITALES CON EDITRAN/FF)

In the process of uploading EDITRAN/G, the system invoques an EDITRAN/FF service

that validates the sending is enabled, verifying that all the digital signatures for the

presentation files exist and that they are correct.

RECEPTION TARGET (DESTINO DE RECEPCIÓN)

Is the path where we will store the received files. As file name, we can specify a mask

using the characters that will be described below. During the dowloading, the name

of the files is done one by one, applying the given format. Is not possible to define

characters that are not admitted by the operating system (\, /, :, ?, *, “, <, >, etc.).

We can use wildcards during reception. See the section 5.1 WILDCARDS USED FOR

RECEPTION TARGET of this manual.

DELIMITATOR (D/U/N) (DELIMITADOR (D/U/N)):

D Downloads fixed files with DOS delimitator.

U Downloads fixed files with UNIX delimitator.

N Downloads fixed files without adding delimitator.



TRANSLATE (A/E/N) (TRADUCIR (A/E/N)):

A Translation into ASCII if data are received in EBCDIC.

E Translation into EBCDIC if data are received in ASCII.

N There is no translation.

IT IS AN EDITRAN ENTITY (S/N) (ES UNA ENTIDAD EDITRAN (S/N))

Only when the EDITRAN/P network protocol is SWIFT, it is possible to make

transmission with entities in which EDITRAN is not installed. In these cases, this field

will be set as N. The only parameters that we need to set are the ones that appear in

the following screen.

+-----------------------------------------------------------------------------+



+-----------------------------------------------------------------------------+

| PRESENTACION : TEST APLICACIÓN EDItran/P : PRUEBA |

| |

| - FICHERO DE EMISION DE LA PRESENTACION - |

| /home/editran/origen/Swift/fichero |

| COMPROBAR LAS FIRMAS DIGITALES CON EDITRANFF (S/N): N |

| |

| - DESTINO DE RECEPCION - |

| /home/editran/destino/Swift/fichero |

| |







| |

| |

| |


+-----------------------------------------------------------------------------+

− PRESENTATION TRANSMISSION FILE (FICHERO DE EMISIÓN DE LA

PRESENTACIÓN)

− RECEPTION TARGET (DESTINO DE RECEPCIÓN)

In this case, we only can send or receive a unique file for each transmission.



3.4.5. PROFILE GENERIC MONITORING

+-----------------------------------------------------------------------------+


| 12:59:39 - CONSULTA GENERICA - |

+-----------------------------------------------------------------------------+

| |

| |

| 1.- ENTIDADES REMOTAS |

| |

| 2.- APLICACIONES |

| |

| 3.- PRESENTACIONES |

| |

| |

| |

| OPCION : |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

3.4.5.1. REMOTE ENTITIES

It obtains a list of remote entities with the data of the presentations in which they are

being used. If the list is longer than a single screen, we can navigate through the pages with

PgUp or Ctrl-U to go to the previous page, and with PgDn or Ctrl-D to go to the next one. With

ESC we go back to the generic monitoring menu.

+-----------------------------------------------------------------------------+

| dd/mm/aa - GESTOR DE FICHEROS DE CONTROL - EDItran/G V#.## |

| 13:00:31 - CONSULTA GENERICA DE PERFILES - |

+-----------------------------------------------------------------------------+

| REMOTO PRESENTACION LOCAL APLICACION |

+-----------------------------------------------------------------------------+

| 000099910 000099910 000000 |

| 000099910 TEST 000000120 PRUEBA |

+-----------------------------------------------------------------------------+

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |


+-----------------------------------------------------------------------------+



3.4.5.2. APPLICATIONS

It obtains a list of applications with the data of the presentations where they are being

used. If the length of the list is longer than a single screen, we can navigate through them

with PgUp or Ctrl-U to go to the previous page, and with PgDn or Ctrl-D to go to the next

page. With Esc, we will go back to the generic monitoring menu.

+-----------------------------------------------------------------------------+



+-----------------------------------------------------------------------------+

| APLIC PRESENTACION LOCAL REMOTO |

+-----------------------------------------------------------------------------+

| PRUEBA PRUEBA 000000000 |

| PRUEBA TEST 000000120 000099910 |

+-----------------------------------------------------------------------------+

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |


+-----------------------------------------------------------------------------+

3.4.5.3. PRESENTATIONS

It obtains a list of presentations and their description. If the length of the list is longer

than a single screen, we can navigate through them with PgUp or Ctrl-U to go to the previous

page, and with PgDn or Ctrl-D to go to the next page. With Esc we will go back to the generic

monitoring menu.

+-----------------------------------------------------------------------------+



+-----------------------------------------------------------------------------+

| PRESENTACION LOCAL REMOTO APLICACION |

+-----------------------------------------------------------------------------+

| TEST 000000120 000099910 PRUEBA |

+-----------------------------------------------------------------------------+

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |


+-----------------------------------------------------------------------------+

EDITRAN/G Windows/Unix User manual 4. EDITRAN/G MANAGEMENT (WINDOWS)


4. EDITRAN/G MANAGEMENT (WINDOWS)

If we click on the option EDITRAN/G Menu (Menú EDItran/G) will appear the EDITRAN/G

managing menu.

If this is the first time you run EDITRAN/G, you will have to enter the local environment

data (see section 4.5 EDITRAN/G ADMINISTRATOR).

4.1. OPERATION INTERFACE

In the screenshots included in this document, the different types of fields are

represented in the following way:

4.1.1. SCREENS

In the screens of EDITRAN for WINDOWS we can distinguish three areas:

(1) Menus

In the menus area we can choose the different options to operate EDITRAN.

Booting and stopping EDITRAN, reports, system administration.

We can activate them with the cursor, using the highlighted letters.

(2) Toolbar

In this area appear different icons indicating different actions, equivalent to the

ones in the menus; if we place the cursor over each icon, we will get information

about their actions at the bottom of the screen.



(3) Information

In this area we will find the information sent by EDITRAN to the operator:

− Session.

− Transmission and reception statuses.

− Transmission and reception counters.

− Informative text or messages from the remote operator.

(4) HELP

EDITRAN/G has a help system available. In this way, when we click on the key F1 it will

appear a window with the help text.

4.2. BOOTING AND STOPPING EDITRAN

To boot and stop EDITRAN, we must chose the option File (Archivo) in the general menu,

and then chose the option Boot EDItran (Arrancar EDItran) or Stop EDItran (Parar EDItran).

The following icon from the bar tool is equivalent to booting and stopping EDITRAN

using the menu:

Clicking on the semaphore, it will remain green and this will perform the action of

booting EDITRAN/G and EDITRAN/P.

Clicking on the symbol with the green semaphore, we will cause the stop of EDITRAN/G

and EDITRAN/P. The semaphore will remain red:



4.3. EDITRAN/G OPERATOR

To operate on the exchange presentations, we must choose the option EDITRAN/G from

the main menu, considering that if we want to act on a specific presentation, we must click on

the cursor over it and choose it (the white background will appear blue). If we don’t do it, will

appear a window for us to choose the presentation to be used:

The following options will be presented:

We also can click on the right button to display a contextual menu with the same

options.

4.3.1. Upload transmission presentation

The status of the transmission presentation session is validate (that is to say, the

status of all the transmission sessions that compone it).

The process previous to user transmission is launched.

The upload is executed if the session status is NOT UPLOADED (NO CARGADO) (see

the meaning of the different statuses). If the process has worked correctly, it

becomes BUFFER UPLOADED (CARGADO TAMPÓN).

If the status of the session is NOT UPLOADED (NO CARGADO), we add 1 to the

number of the presentation, as long as SESSION INCRESING (INCREMENTO SESIÓN) is

S. This presentation number, depending on the used converters, is passed to the

number of control record exchange of the transmission in the transmission buffer or

buffers. In this case, it must match the one registered in the reception buffers in the

remote node.

The converter program before transmission, specified in the profile of the

corresponding session, is invoked. Depending on the features of each converter,

different application and/or presentation processes can be performed. In any case, we



obtain one or several transmission buffers with status BUFFER UPLOADED (CARGADO

TAMPÓN).

EDITRAN is reported about the readiness of the buffers, with as many A8R messages

as transmission sessions have been uploaded. Their status becomes BUFFER

UPLOADED (CARGADO TAMPÓN).

The user program before transmission, if it exists in the profile, is invoked.

The physical name of the buffer file, as well as the length of the record, is taken from

the corresponding EDITRAN/G presentation.

This button is equivalent to the action performed through menus:

4.3.2. Process after transmission

The process is performed if the status of the session is TRANSMITTED (TRANSMITIDO),

INTERRUPTED (INTERRUMPIDO) or LOADED (CARGADO). At the end of the process, it becomes

NOT LOADED (NO CARGADO).

This process is made automatically when the transmission of all the sessions associated

to the presentation is finished, or when the user wants to cancel a pending transmission. The

transmission buffer files associated to the presentation are deleted.

Clicking this option is equivalent to doing the same using menus:

4.3.3. Transmitting presentation

The status of the presentation must be NOT UPLOADED (NO CARGADA), BUFFER

LOADED (CARGADO TAMPÓN) or INTERRUPTED (INTERRUMPIDA). If NOT UPLOADED (NO

CARGADA) performs the process before transmission, as we have already seen for the upload,

so it would become BUFFER UPLOADED (CARGADO TAMPÓN).

Once the status is BUFFER UPLOADED (CARGADO TAMPÓN), as many AR1 as

transmission session compose the presentation are sent to EDITRAN. The same is done for

INTERRUPTED (INTERRUMPIDA), since we manifest our will to continue with a previously

interrupted session. The status of the session becomes TRANSMITTING (TRANSMITIENDO).


4.3.4. Interrupting transmission

It is to interrupt the current emission, which status must be TRANSMITTION

(TRANSMITIENDO) or INTERRUPTED (INTERRUMPIDO). For this, it will be sent to EDITRAN as

many EDP as presentation transmission sessions are. EDITRAN returns EDITRAN/G the control

over the transmission buffers. The status of the session passes to INTERRUPTED

(INTERRUMPIDO).




4.3.5. Initializing reception presentation

The status of the reception presentation is validated. That is to say, the status of all the

transmission sessions that compose it is validated.

The initialization is executed if the session status is TRANSMITTED (TRANSMITIDO). At

the end of the process, it becomes NOT LOADED (NO CARGADO).

The unique process before reception is launched.

If the status of the session is TRANSMITTED (TRANSMITIDO), we add 1 to the number of

presentation, if SESSION INCREASING (INCREMENTO SESIÓN) is S. This presentation number,

depending on the converters used, is passed to the exchange number of the transmission

control log in the reception buffer(s). In this case, it must match the one registered in the

transmission buffers in the remote node during the next exchange.

The converter program before reception, specified in the corresponding session profile,

is invoked, in case it exists. We obtain one or several reception buffers with status BUFFER

UPLOADED (CARGADO TAMPÓN), though they are still not available for EDITRAN.

The user program before reception, in case it exists, is invoked.

The physical name of the file and the length of the record are taken from the

corresponding EDITRAN transmission profile.

Clicking this option is equivalent to doing the same using menus.

4.3.6. Dowloading reception

The process is performed is the status of the session is TRANSMITTED

(TRANSMITIDA) or INTERRUPTED (INTERRUMPIDA). At the end of the process, it

becomes NOT UPLOADED (NO CARGADO).

If there are several transmission sessions in the presentation session, and if the request

comes from EDITRAN, it indicates the end of reception of only one of them, whose status

becomes TRANSMITTED (TRANSMITIDO); at that moment, EDITRAN/G can know the real

number of sessions used by the remote transmitter (as this data comes in a header record),

and it deletes from the presentation statuses record the spare ones. When reaching the last

request, it triggers the process of presentation dowloading.

In any case, the unique process after reception is launched and the converter program

and the user program, both after transmission, are invoked, in case they exist in the

presentation profile.

The reception buffers associated to the presentation are deleted.

Clicking on this option is equivalent to doing the same using menus.

4.3.7. Receiving presentation

The status of the presentation must be NOT UPLOADED (NO CARGADA), TRANSMITTED

(TRANSMITIDA) or INTERRUPTED (INTERRUMPIDA). If NOT UPLOADED (NO CARGADA) or

TRANSMITTED (TRANSMITIDA) perform the process before reception, as we have already

seen, it would become NOT UPLOADED (NO CARGADA).



Once BUFFER is UPLOADED (CARGADO TAMPÓN), are sent to EDITRAN as many A1R as

transmission sessions of the presentation have been defined, as we don’t know exactly how

many are going to be used by the transmitter. The same is done for INTERRUPTED

(INTERRUMPIDA), as we express our will to continue with a previously interrupted session.

The status of the session becomes TRANSMITTING (TRANSMITIENDO).

Clicking this option is equivalent to doing the same using menus.

4.3.8. Interrupting reception

It is to interrupt the current reception, which must be TRANSMITTING

(TRANSMITIENDO), for which are sent to EDITRAN as many EDR as transmission sessions the

presentation has. EDITRAN returns EDITRAN/G the control of the reception buffers. The

status of the session becomes INTERRUPTED (INTERRUMPIDO).


4.4. FILE MONITORING

4.4.1. Monitoring presentation statuses

To monitor a specific presentation, we have to type it and then choose the type of

presentation (transmission or reception). In the screen information area (lower part) will

appear the information of the requested presentation.



PRESENTATION STATUS

It can have the following values:

NOT UPLOADED (NO

CARGADA)

None of the buffers of the EDITRAN associated sessions is

uploaded.

CSB UPLOADED

(CARGADO CSB)

Intermediate status before uploading buffer.

BUFFER UPLOADED

(CARGADO TAMPÓN)

Some of the buffers of the EDITRAN sessions are uploaded.

TRANSMITTING

(TRANSMITIENDO)

Some of the EDITRAN sessions are transmitting.

TRANSMITTED

(TRANSMITIDA)

All the buffers have been transmitted but not uploaded.

INTERRUPTED

(INTERRUMPIDA)

Some of the associated EDITRAN sessions are interrupted.

PRESENTATION PENDING

Its value is Yes (Sí) when there has been an upload, and also for the ones that have not

yet been transmitted.

PRESENTATION

The presentation number is initialized to 1. We increase by one unit every time a

presentation transmission is made, and more specifically, when the status of the

transmission presentation passes from NOT UPLOADED (NO CARGADO) to BUFFER

UPLOADED (CARGADO TAMPÓN). Anyway, this status automatically changes to BUFFER

UPLOADED (CARGADO TAMPÓN) and then to TRANSTIMMED (TRANSMITIENDO).

EDITRAN SESSIONS

Appear as many lines as transmission sessions are used in the presentation, that will be

only one in 1.2 version, and up to 20 in the rest of versions. In each line appear: session

and description of the session status, date and time of the status change. The

transmission or reception statuses can be:

NOT UPLOADED (NO

CARGADO)

When the process after session transmission or reception has been done.

TRANSMITTING

(TRANSMITIENDO)

When transmission or reception has been requested to EDITRAN.

TRANSMITTED

(TRANSMITIDO)

When a transmission or reception end comes from EDITRAN informing

about the correct transmission of the buffer.

BUFFER UPLOADED

(CARGADO

TAMPÓN)

When the transmission upload is performed. Not available for EDITRAN.

INTERRUPTED

(INTERRUMPIDO)

When an interruption from the EDITRAN/G operator is received, or when a

A71 is received from EDITRAN/P.



4.4.2. Modifying presentation statuses

Modifying presentation statuses is an operation that must be done only in anomalous

circumstances, if we have previously activated the option “Increasing presentation number (Incrementar número de presentación)”.

The presentation session number es presented and it can be modified. The system also

asks whether we want to initialize the presentation statuses. These statuses will become

NOT UPLOADED (NO CARGADA).



4.4.3. Log monitoring

We will choose the session, the date and the time and then we will click OK.

In case it is a general monitoring, we will select <all> (<todas>) in the section

Presentation (Presentación).

Messages are shown from the defined date to the current date of the request.

If we define 00:00:00 in Time (Hora) it will show all the messages, regardless of the

time.

The file editrang.log is cyclically treated.



4.5. EDITRAN/G ADMINISTRATOR

We access the EDITRAN/G administrator by clicking the option Administrator

(Administrador) in the main menu. The following screen will be displayed:

4.5.1. Local environment

We define a set of parameters within the product, which allows knowing the installation

where the product is going to run. It also allows to identifying the local EDITRAN/G

installation to others.

Only in EDITRAN/G profiles exists a local environment log that must be registered during

the installation; after that, it can be modified or monitored.

Local EDItran/G code (Código EDItran/G local) (the same already defined in

EDItran/P.)

Local EDItran/G name (Nombre EDItran/G local)

Local EDItran/G version (Versión EDItran/G local)

The values entered here are taken as default values when registering presentations.

Modifying and monitoring the local environment must be done exactly like registering,

but in this case the corresponding profile needs to have been created previously.

The local environment cannot be deleted.



4.5.2. Remote entity profile

We have to define all the remote clients EDITRAN is going to interconnect with.

If we choose the option Remote entity profile (Perfil de entidad remota) will appear a

screen in which we have to identify the remote entity we want to exchange files with.

The screen is the following one:

Remote entity code (Código de entidad remota):

Enter the remote entity code, which must be the same we used in EDITRAN/P.

Description (Descripción):

Descriptive name of the remote entity.

Remote EDItran/G version (Versión EDItran/G remota):

The remote EDItran/G version also determines the transmission and reception

converter to be used.

4.0 If the remote entity is EDITRAN/G V4.0






Char set:

We can choose ASCII or EBCDIC.

Is necessary to provide the alphanumeric char set that is going to be used by the

remote machine, (ASCII or EBCDIC). This does not imply that there will be data

translation, as this is defined in the presentation profile.

Cryptography:

It can have two values:

No (No): when we don’t want to use chryptography during the upload/download

(default value).

Yes (Sí): when chryptography is used. Now we will list and describe all the

parameters involved in the chryptographic system.

Confidentiality algorithm (Algoritmo de Confidencialidad): it indicates

whether we want to cipher data in real time while uploading/downloading. It can

have the following values:

□ Nothing defined: when we don’t want to cipher data while

uploading/downloading, but to cipher while transmitting (EDITRAN/P).

□ DES: if we want to cipher data while uploading/downloading.

□ TD2: triple-DES cipher with double key.

□ TD3: triple-DES cipher with triple key.

Authentication algorithm (Algoritmo Autenticación): indicates the algorithm

used to cipher the session key and the data exchanged to authenticate the

extreme nodes. It is mandatory if there is a confidentiality algorithm. It can have

the following values:

□ Nothing defined: when we don’t want to authenticate the extreme nodes

(this option is not valid if we want to cipher data while

uploading/downloading).

□ DES: if we want to authenticate the extreme nodes with DES algorithm (valid

for chryptography versions 2.2 and 3.0).

□ RSA: if we want to authenticate the extreme nodes with RSA algorithm

(valid for chryptography version 3.0 in EDITRAN/P).

□ PKI: if we wish to authenticate the extreme nodes with PKI, this option

enables a field in which we can enter the key PIN (valid for cryptography

version 3.0).

The values of the data of a remote entity are passed to the presentations of these

entities, when they are registered, as default values.

Modifying and monitoring a remote entity profile can be done in the same way as

registering, despite the profile must already exist. The modified values are not transferred to

the ones that match the presentations from the same entity.



4.5.3. Application profile

If we choose the option Application profile (Perfil de aplicación), will appear a screen in

which we will have to identify the remote entity we want to exchange files with.

The screen is the following:

Application (Aplicación)

Choose the name for the application we want to register, delete or modify.

Description (Descripción)

Name of the presentation application.

Conversion tables (Tablas de conversión)

They are text files, edited by the user, with the table of correspondances between

the codification scheme of local characters, and the one of EDITRAN, used both for

transmission and reception. Each line will be from the following type, with

hexadecimal character definition:

<character-EDITRAN> <character-local>

If we don’t need any local translation, these fields will be left blank. In any other case,

we will use the file name without the last character, which is the one which identifies

the alphabet: A for ASCII, or E for EBCDIC. For example, assuming that the user

creates the file mitablaA to translate ASCII characters, in the profile we would only

type mitabla.



User programs (Programas de usuario)

They are invoked by EDITRAN/G in the processes before and after exception

transmission and reception. These programs will be provided by the user and will be

invoked during the presentation processes.

The arguments used to invoke these programs are described in the sections about

user programs.

If we want to perform any action, it will have to be included in the corresponding

process.

The values of the data from a presentation application are passed to the

presentations of that entity, when they are registered, as default values.

Modifying and monitoring an application profile is done in the same way that

registering, despite the profile must already exist. The modified values are not

transferred to the ones that match the presentations of the same entity.

4.5.4. Presentation profile

It is identified by the local entity, the remote entity and the presentation application.

The information contained in this profile comes, to a large degree, from the previous three

corresponding profiles, besides the transmission and reception file(s).

A presentation session can have up to 20 EDITRAN/P transmission sessions, according

to its operating mode. That is to say, the information to be exchanged can be transmitted by

up to 20 circuits at the same time.

To control a presentation session, we can use the file of transmission and reception

statuses. It shows, for each session, the different statuses through which it passes. The

presentation statuses are the result of the set of transmission statuses. They change as the

processes occur, and they are used to allow or to deny the requests, and also to stablish

differences among the executed processes. For example: if the system receives a

transmission request and the status is "not uploaded (no cargado)", the upload is demanded

first and after that the transmission. But if the status is "uploaded (cargado)", the

transmission is demanded right away.

If we choose the option Presentation profile (Perfil de presentación), will appear a

window with different labels to choose, such as Presentations (Presentaciones), Local entity

(Entidad local), Remote entity (Entidad remota), Application (Aplicación) and Files (Ficheros).



Presentations screen:

Presentation (Presentación)

Choose the name for the presentation you want to register, delete or modify.

Presentation data (Datos de la presentación)

− Increase presentation number (Yes/No) (Incrementar número de

presentación (Si/No))

It specifies whether the number of presentation should be increased, and

therefore the exchange session number for each EDITRAN sessions associated to

it during the previous transmission and reception processes.

− Number of presentation sessions (Número de sesiones de presentación)

Number of EDITRAN sessions associated to the EDITRAN/G presentation. Then we

have to specify which ones they are. These EDITRAN sessions must have been

previously registered in EDITRAN/P. All EDITRAN sessions will have the same code

than the EDITRAN/G presentation.

− Division criteria (Criterio de División (V/S/F/N))

Only in native mode, and if we are going to use several transmission sessions for

the presentation session. We can specify the following values:

□ None (Ninguno): No division is performed.

□ Volume (Volumen): The information about the transmission application

would be shared equally among the different buffers, with a minimum of

400.000 octets per buffer. That means some of the transmission defined

sessions might not be used in the presentation.

□ Synchronism (Sincronismo): Distribution by batch marked by synchronism

points, depending on the converter. Sequent complete batches would be

assigned to each transmission buffer.

□ File (Fichero): Distribution by file, depending on the converter. Every

transmission buffer is assigned sequent complete files.



− Upload type (Tipo de carga)

With a cumulative upload type, it is allowed to reload the buffer with new

application files, as long as the transmission has not yet begun. Cumulative upload

forces to use a single transmission session.

Normal (Normal) A single upload per transmission.

Cumulative (Acumulativa) Allows several uploads before transmitting.

− Ask for download confirmation (Pedir confirmación de descarga)

With remote download confirmation, the transmission will not be terminated until

the result is received from the remote note. When the download finishes with an

error, the user process after reception will receive in the parameter the result

indicating this fact. In reception, the result from the last download is returned, as

long as the remote node requests it.

EDItran/P applications (Aplicaciones EDItran/P)

Name of the Editran/P applications through which the files will be transmitted.

Local environment screen:

Its parameters are described in the section 4.5.1 Local environment.



Remote entity screen:

Its parameters are described in the section 4.5.2 Remote entity profile.

Application screen:

Its parameters are described in the section 4.5.3 Application profile.



Files screen:

Presentation Transmission Files (Ficheros de Emisión de la Presentación)

It has the following fields:

− Transmission source (Origen de Emisión)

It describes the file path, whose content is the final result of the transmission

upload from the EDITRAN transfer.

We can define absolute or relative paths, UNC and network units. We can also use

metacharacters (* and ?).

− Zipping (Compresión)

Yes (Sí) LZW zipping.

No (No) Without LZW zipping.

If we specify Yes (Sí), zipping is performed when uploading.

In reception, the system acts not according to the profile, but to the content of

what it received.

− Application File Format (Formato de Fichero de Aplicación)

It refers to the format of the file we want to send. It can have the following

values:

F Fixed (Fijo): The application files are read as fixed length records. It removes

delimiters.

V Variable (Variable): The application files are read line by line, and line delimiter

are characters CR-LF for PC´s and CR for UNIX machines. These delimitation

characters are not sent to the remote system. During the remote conversion

process, the reverse operation is performed, inserting the line delimitation

characters that fit the receptor system.

H Hybrid (Híbrido): Fixed or variable length, with delimiters.

It makes it fixed using blanks. It removes delimiters.

B Binary (Binario): Transparent mode (without transformations).

Only for homogeneous environments, if the remote version is higher than 4.1.



− Alphabet (Alfabeto)

It is the original language of the data to be uploaded. Initially, it will be A (ASCII). It

is used to specify this language at the beggining of the file. (00:ASCII, 01:EBCDIC,

02:BINARY).

A ASCII. The file(s) data are ASCII.

E EBCDIC. The file(s) data are EBCDIC.

− ASCII/EBCDIC Translation (Traducción ASCII/EBCDIC)

It indicates whether we want to translate, and into which language.

Yes (Sí) Translate application data into EBCDIC.

No (No) Do not translate application data.

− Delimiter (Delimitador)

It indicates whether the file(s) to be sent use delimiters or not:

DOS: DOS delimiters (used in Windows systems)

UNIX: UNIX delimiter (used in UNIX systems)

NONE (NINGUNO): No delimiter

Reception target (Destino de recepción)

Name of the folder and/or file where we want to download the file.

During the downloading, the names of the files are transformed one by one, applying

the given format. It is not possible to define characters not admitted by the operating

system (\, /, :, ?, *, “, <, >, etc.).

We can define absolute and relative paths, UNC and network units.

We can use wildcards in the reception. See the section 5.1 WILDCARDS USED FOR

RECEPTION TARGET in the manual.

4.5.5. PROFILES GENERIC MONITORING

The possible values to monitor are:

− Presentation (Presentación)

− Remote entity (Entidad remota)

− Application (Aplicación)

Presentation

We obtain a list of presentations and their description.



Remote entity

We obtain a list of remote entities and their description.

Application

We obtain a list of applications and their description.

EDITRAN/G Windows/Unix User manual 5.ANNEXES


5. ANNEXES

5.1. WILDCARDS USED FOR RECEPTION TARGET

Wildcards that can be specified are:

+ If the file exists, add to the previous one

- If the file exists, destroy the previous one

%o Original name of the downloaded file (incluided its

extension)

%D Date (DD)

%M Month (MM)

%Y Year (YYYY)

%h Time (hh)

%m Minutes (mm)

%s Seconds (ss)

%c File counter (c)

For the wildcards %Y and %c we can define the accuracy of the digits to be defined,

adding a number before the wildcard letter. For example, if we define %4c, 4 digits

will be typed.

Examples of reception target

In the following examples, the remote entity sends us 4 files.

Case 1

We set the following reception target:

../target_path or ../target_path/%o

Sent files Downloaded files

a.txt ../target_path/a.txt

b.txt ../ target_path /b.txt

c.txt ../ target_path /c.txt

d.txt ../ target_path /d.txt

If any of the files existed before they are downloaded, they would be destroyed and

replaced by the new ones.

Case 2


../target_path/+bank_%D-%M-%Y_%h-%m-%s


a.txt ../target_path/bank_17-10-2014_14-00-01

b.txt ../target_path/bank_17-10-2014_14-00-02

c.txt ../target_path/bank/banco_17-10-2014_14-00-03

d.txt ../target_path/bank_17-10-2014_14-00-03

Several files are downloaded, and we define for them the day, month, year, hour,

minute and second. In the case of files c.txt and d.txt, as they both are downloaded in

the same second, the content of bank_17-10-2014_14-00-03 would be the one from

both.



Case 3


../target_path/bank-%D-%M-%Y_%4c


a.txt ../target_path/bank_17-10-2014-0000

b.txt ../target_path/bank_17-10-2014-0001

c.txt ../target_path/bank_17-10-2014-0002

d.txt ../target_path/bank_17-10-2014-0003

Several files are downloaded during the same session. For each of them are defined

day, month, year and a 4 characters counter (%4c).

Case 4


../target_path/bank_%o


a.txt ../target_path/bank_a.txt

b.txt ../target_path/bank_b.txt

c.txt ../targeto_path/bank_c.txt

d.txt ../target_path/bank_d.txt

The downloaded files will have their defined name, plus the original name (including

their extension).

Case 5


../target_path/+single_file


a.txt ../target_path/single_file

b.txt ../target_path/single_file

c.txt ../target_path/single_file

d.txt ../target_path/single_file

The content of the downloaded file will be the one resulting of files a + b + c, due to

+.

Case 6


../target_path/single_file


a.txt ../target_path/single_file

b.txt ../target_path/single_file

c.txt ../target_path/single_file

d.txt ../target_path/single_file

As we don’t make any difference among files, they will be overwritten as they are

downloaded. The final content will be the one from the file c.txt.



Case 7


../target-path/%o_%D-%M-%Y


a.txt ../target_path/a.txt_17-10-2014

b.txt ../target_path/b.txt_17-10-2014

c.txt ../target_path/c.txt_17-10-2014

d.txt ../target_path/d.txt_17-10-2014

Several files are downloaded per session, and for each of them is defined an original

name (defined by the remote node, including the extensión), day, month and year.

5.2. COMMANDS

5.2.1. editrang

This process interacts with the EDITRAN/P system and with the EDITRAN/G user. It is

launched in background when booting the EDITRAN system.

5.2.2. conver[40|41|50]

Description

Command used to process application files in compatible mode with lower versions.

Processing is to transform application files in a temporary file internal to EDITRAN/G.

The application files are specified in the presentation profile of EDITRAN/G. This

command is invoked by the process editrang when the profile remote version is lower

than 5.1.

Syntax

conver[40|41|50] -l|u <presentation>

<Commands>

-l : CSB load.

-u : CSB download.

<Options>

<presentation> : Presentation identity.

5.2.3. conver51

Description

Command used to process application files in native mode (EDITRAN/G V5.1).

Syntax

conver51 -l|u <presentation>

<Commands>

-l : CSB load.

-u : CSB download.

<Options>

<presentation> : Presentation identity.



5.2.4. traduct

Description

This command allows translating files from ASCII-EBCDIC and from EBCDIC-ASCII.

If we wish to change certain characters from the standard tables, we must generate the

following tables:

Modifications in the table ASCII->EBCDIC must be written in the file toebcdic.tbl.

Modifications in the table EBCDIC->ASCII must be written in the file toascii.tbl.

Modifiable characters are not alphanumeric ones (a-z, A-Z, 0-9).

The characters specified in the text files must be written in hexadecimal format.

Each modification must be written in a different line.

In each line we must write the character to be translated, and then the translated

character, both separated with a blank.

Example:

To modify the translation of the following characters: Ñ ñ Ç ç (hexadecimal [decimal] in ASCII: A5[165], A4[164], 80[128] y 87[135] respectivamente), traducidos actualmente

a EBCDIC por: AC, 8F, 66 y 8E respectivelly, if we wish the translation to be: 7B, 6A, 68 y

67.

We must write in the file "toebcdic.tbl” the following:

A5 7B

A4 6A

80 68

87 67

In the 5.0 version, the standard ASCII/EBCDIC tables used by EDITRAN have been

changed. To make updating easier, in the cases where we need to use local conversiont

tables, it has been included the new option –m. With this option, if we specify the name

of the file that stores the current modifications, updating is performed with the

appropriate values for the new tables.

Example:

Let’s suppose that an entity had the following ASCII table in reception (tablaA) to adapt

the characters Ñ ñ to its environment:

A4 F1

A5 D1

When executing the command:

traduct –m r tablaA tabla5A

A -> E(41) -> A(50) A

==========================

a4 -> 6a -> f1 = f1

a5 -> 7b -> d1 = d1

Each output line is interpreted like this: the character ASCII 0xA4, that according to the

old translation tables is the result from the character EBCDIC 0x6A, would be received as

0xF1 in the version 50. This means it is equal to the final character of the local table.

In the case the new received character is the one we expect, as it happens here, the line

will be deleted from the new local table tabla5A.

Syntax

traduct. Translation utility ASCII-EBCDIC.

V2.0 R0 - Apr 30 2013



Copyright (C) 1991-2011 INDRA

Use : traduct -a|e source target

Use : traduct -t a -t e -c -d -o -x

Use : traduct -v

Use : traduct -m [e|r] tablaIn [tablaOut]

Being :

-a : Translation to ASCII.

-e : Translation to EBCDIC.

source : File to be translated (stdin by default)

target: Translated file (stdout by default)

-t a : Print of the table ASCII.

-t e : Print of the table EBCDIC (default).

-c : Character.

-d : Decimal.

-o : Octal.

-x : Hexadecimal (default).

-v : Verification

-m [e|r]: Migration of local conversion table (transmission/reception)

tablaIn : File containing the table to be migrated

tablaOut: File containing the table already migrated

5.2.5. igacmd

Description

This command establishes a mechanism of communication among applications or user

programs and EDITRAN/G, allowing invoking operations unattended and automatically.

This command is equivalent to the EDITRAN/G manager menug interactive.

It allows building procedures associated to send and/or receive, with concatenation of

new transmissions or receptiones.

Syntax

igacmd. EDItran/G petitioner in command mode.

V2.0 R0 - Apr 30 2013


Use : igacmd -o <operation> -p <presentation> [-v] [-w]

Being :

-o <operation> : Operacion to perform.

InitE - Initialize transmission

LoadE - Load transmission

Send - Transmit

EndE - Interrupt transmission

InitR - Initialize reception

UnloadR - Download reception

Recv - Receive

EndR - Interrupt reception

-p <presentation#> : Presentation identificator

-v : Verb mode

-w : Waiting for request end

Example:

At the end of a certain presentation, we wish the system to generate a transmission to

the remote EDITRAN system whose presentation is PRUEBA.

For this, the user file after reception will include the following call: ...

igacmd –o Send –p PRUEBA -v

...

When EDITRAN/G invoques the automatism associated to the end of reception (previous

command), igacmd will send a signal to EDITRAN/G indicating that the user has

requested a transmission start operation for the presentation PRUEBA.



Return codes

Usually, the return codes of the command are listed in the section 5.3.2 EDITRAN/G

result codes and they correspond to the result of the operation performed by

EDITRAN/G when the request is made using the option –w. There are also other values

to indicate communication problems with EDITRAN/G.

0 Correct result

60 Correct syntax

61 EDITRAN/G system not initiated

62 Error when communicating with EDITRAN/G while sending

request(send)

63 Error when communicating with EDITRAN/G to receive

result(receive)

5.2.6. menug

Description

This command allows direct access to EDITRAN/G manager menu.

5.2.7. estcmd

Description

This command is used to know the status of an EDITRAN/G presentation.

Syntax

estcmd. Print utility for EDItran/G presentation status.

V1.0 R0 - Apr 30 2013


Use : estcmd E|R [presentation]

<Options>

E|R : Transmission or reception.

[presentation#] : Presentation identificator.

Return codes:

Numeric value, from 0 to 6, corresponding to the following statuses:

PRES_NOT_UPLOADED 0

PRES_CSB_UPLOADED 1

PRES_BUFFER_UPLOADED 2

PRES_TRANSMITTING 3

PRES_TRANSMITTED 4

PRES_ENDED 5

PRES_INTERRUPTED 6



5.2.8. igaperfi

Description

This command is used to manage EDITRAN/G profiles in command mode. There is

detailed information about this utility in the document “EDITRAN/P and EDITRAN/G user profiles. User manual”.

Syntax

Use: igaperfi: Command for unattended introduction of k/G profiles.

V1.0 R1 - Apr 14 2009


Use: igaperfi [-h] [-f<inputfile>]

[-r {[-a [-V<v>] [-R<r>]] | [-s<presentation>]} [-o<outputfile>]]

-h: help (this)

-f<inputfile>: name of the file with commands for

Profile modification. (default=stdin)

-r: EDItran/G presentations are dumped to a file.

-s<presentation>: EDItran/G presentation to be dumped.

-a: all presentations are dumped to a file.

-R<r>: Release of the file to be dumped.

Valid values from <r> 2..8

-V<v>: Version of the file to be dumped.

Valid values from <v> 22, 30, 31, 40 y 41

-o<outputfile>: name of the file to which the session

will be dumped. (default=stdout)

5.2.9. modiperfi

Description

This command is used to modify or to delete EDITRAN/P and EDITRAN/G profiles, for

one session/presentation as well as for several of them simultaneously.

Syntax

modiperfi. Utility for modifying and deleting profiles.

V1.0 R0 - Apr 30 2013


Use: modiperfi [-h] | {-o<P|G|F [-c]> [-r<remote>] [-a<aplication>] [-l<local>]

[-s<session>|-p<presentation>] -m<-Exx=yy ...|-Ixx=yy ...>}

| {-b -o<P|G> -s<session|-p<presentation>}

<Options>

-h: Help information.

-o<P|G|F>: Option identifier for the profiles to be modified

'P' to modify EDItran/P profiles,

'G' for EDItran/G profiles, and 'F' for file modifications.

-c: Compatible only with option "-oF". If the file to be modified does not exist,

it will be created.

-r<remote>: Identificator of the remote. It allows writing only

significant numbers.

-a<application>: Application identificator. It allows using

metacharacters '*' and '?' as wildcards.

-l<local>: Identificator of the local. It allows writing only

significant numbers.

-s<session>|-p<presentation>: Identificators for the session and

presentation. They allow using

metacharacters '*' and '?' as wildcards.

-m<-Exx=yy ...|-Ixx=yy ...>: Identificator for modifications. It changes

the parameter(s) of EDITRAN/P or

EDItran/G profile from 'xx' to 'yy' (see the

manual for cfgupt command or execute "cfgupt -H").

-b: Identifies we are going to delete a session or a presentation.



5.2.10. histcmd

Description

This command is used to monitor the history file, completed or limited, of EDITRAN/G

presentations, as well as the last transmission of a specific presentation.

Once the command is executed, the screen shows a list of presentations, if they

exist, with an informative header about the performed requested. After that, the

following data of each presentation are displayed:

− Name of the presentation

− Direction of the transmission

− Date and time of the transmission start

− Date and time of the transmission end

− Status

Further, for each presentation is displayed its list of transmission files, when they

exist, with the following data:

− Source path

− Date and time of creation

− Number of bytes

Syntax

histcmd: Incorrect syntax, incompatible search parameters

histcmd. EDItran presentations history and monitoring of a presentation

last transmission.

V1.0 R0 - Apr 30 2013


Uses:

histcmd -h | {[-s<E|R>] [-p<presentation>] [-i<ddmmaaaa-hhmmss>]

[-f<ddmmaaaa-hhmmss>]} | {-u -s<E|R> -p<presentation>}

<Options>

-h: Identificator to obtain help information.

-s<E|R>: Identificator of the direction (transmission or reception).

-p<presentacion>: Identificator of the presentation. It allows the

metacharacter '*' as a wildcard.

-i<ddmmaaaa-hhmmss>: Identificator of the starting date and time.

-f<ddmmaaaa-hhmmss>: Identificator of the finishing date and time.

-u: Request identificator of the last transmission.

Examples:

In the following examples we can see how, for using the command in history monitoring

mode, all arguments are optional. We also can use filters to narrow our search. So, if we don’t

specify any filter, the complete history will be displayed. If we specify the direction, will

appear in the list only those whose direction matchs the one specified, etc.

Nevertheless, in case we use the command to monitor the last transmission of a specific

presentation, is mandatory to use the three arguments (-u –s<E|R> -p<presentation>), and no

other one but them will be admitted.



− histcmd

It will show the complete history of EDITRAN/G presentations.

− histcmd –pAMP* –f17102014-120314

It will show all those presentations whose name begins with ‘AMP’ and whose end

of transmission date and time are equal to or later than 17/10/2014 and 12:03:14

respectivelly.

− histcmd -sE -pAM* –i01031999-003000 –f01031999-003205 >historico.txt

It will send the list, obtained from the command of the previous example, to the

file historico.txt. If the file does not exist, it will be created when executing the

command.

− histcmd –u –sE –p”EDITRAN-TCP1”

It will show the last transmission of the presentation EDITRAN-TCP1.

5.2.11. igacode

Description

This command is used to show the description of an EDITRAN/G result code.

Syntax

Description of the EDItranG result codes.

V51.0 R0 - Apr 19 2013


Use : igacode <rc#>

Being :

<rc#> : result code.

5.2.12. USER PROGRAMS

Description

These programs will be provided by the user and they will be called during the

presentation processes.

Syntax

All user programs are invoked using the following arguments:

0 Name of the program

1 Presentation

2 Indicates transmission (E) or reception (R)

3 Result of the operation just performed

4 Local code

5 Remote code

6 Application



Examples:

The distributions of EDITRAN/G products include orientative examples of how to write

the commands performed by EDITRAN/G automatism.

− UNIX

#!/bin/sh

#

#

EXIT_STATUS=""

echo "################################################################################"

echo "SCRIPT DE USUARIO PREVIO A EMISION: $0."

echo "`date`"

echo "PRESENTACION : $2-$1 ($4-$5-$6)"

echo "RESULTADO : $2-$3"

EXIT_STATUS="$?"

echo "EXIT CODE DEL PREVIO : ${EXIT_STATUS}"

echo "################################################################################"

exit ${EXIT_STATUS}

− WINDOWS

@echo off

rem

rem

echo ################################################################################

echo SCRIPT DE USUARIO PREVIO A EMISION: %0.

timestamp

echo PRESENTACION : %2-%1 (%4-%5-%6)

echo RESULTADO : %2-%3

echo ################################################################################

5.2.12.1. List of transmitted or received files

Every time a presentation transmits or receives, a file with the list of transmitted files is

generated. This file is the recommended one to use from user programs, when we want to

treat the files after transmission. As the rest of temporary files, this one can be found from

the EDITRAN installation folder, in the subfolders tree <clocal>\<cremoto>, and named under

<aplicación>[E|R].ficheros.

For example, assuming that the product was installed in C:\EDITRAN, the file

C:\EDITRAN\00009999.0\00001234.0\TEXTOSR.ficheros would store the files received in

the entity 00009999.0, that came from the entity 00001234.0 and were received by the

application TEXTOS.



5.2.13. editrang.out

File in which are stored all the exits performed by EDITRAN/G, as well as the procedures

and commands launched by it. For example:

********************************************************

TRANSMISSION RESULT OF THE PRESENTATION EPRUEBA

Presentation number : 0001

Remote download confirmation : Not required

Date and time of transmission start : 17/10/2014 16:24:06

Date and time of transmission end : 17/10/2014 16:24:07

# Transmitted Name

--- ------- ------

1 100% C:\Test\Prueba1.txt









********************************************************

################################################################################

USER SCRIPT AFTER TRANSMISSION: U_PSTEMI.

Fri Oct 17 16:24:07 2014

PRESENTATION : E-"PRUEBA" (000001230-000003210-PRUEBA)

RESULT : E-0000

################################################################################

5.2.13.1. EDITRAN/G output differentiated by presentation

In SOs Unix 5.0.2 version or higher, there is the possibility of having the previous

information distributed in files by presentation and day. For this, the user must only

uncomment the following lines of the EDITRAN script and create the folder we indicate.

#################

#GOUT PATH: Uncomment if we wish information about EDItran/G by presentation

#GOUT_PATH=./GOut

#export GOUT_PATH

In this case, in the folder ./GOut will be created files whose name matchs the

presentation and the transmission date, for example 007778PRUEBA.171014. Unlike what

happens with the file editrang.out, these files can be moved or deleted without stopping

EDITRAN.



5.2.14. editrang.cfg

EDITRAN/G setting file. It stores the local profile and the EDITRAN/G remote entities,

applications and presentations profiles. It is used exclusively by EDITRAN/G.

5.2.15. editrang.hlp

File in which are stored the help texts of the interactive command menug. It is used

exclusively by EDITRAN/G Unix.

5.2.16. editrang.msg

File in which are stored the messages that EDITRAN/G presents to EDITRAN/G operator.

It is used exclusively by EDITRAN/G.

5.2.17. editrang.sts

File of EDITRAN/G statuses. It is used exclusively by EDITRAN/G.

5.2.18. editrang.log

File created by the command makelog. It stores cyclically a summary of the operations

performed by EDITRAN/G. Once it reaches the maximum number of entries, it overwrites the

oldest one.

It can be monitored from the EDITRAN/G menus or using the command printlog,

described in the manual EDITRAN/P.



5.3. CODES AND MESSAGES FOR THE OPERATOR

5.3.1. EDITRAN/G messages

These codes remain stored in the file editrang.log to indicate the different statuses

of a presentation. In the EDITRAN/G operator screen they appear as messages.

We will detail now these codes and messages, along with a brief explanation of

recommended action, as appropriate:

CODE MESSAGE EXPLANATION/RECOMMENDED ACTION

01 Request for transmission

load

A request for transmission presentation load has been made.

02 Request for transmission A request for presentation transmission has been received.

03 Request for dynamic

transmission

Option not implemented

04 Request for transmission end A request for presentation transmission end has been made.

05 Request for reception start A request for reception presentation start has been made.

06 Request for reception

dowload

A request for reception presentation download has been made.

07 Request for reception A request for presentation reception has been made.

08 Request for reception end A request for presentation reception end has been made.

09 Presentation is initialized A request for presentation initializacion has been made for an

already initialized presentation.

10 Presentation is transmitting A request for presentation transmission/reception has been made

for an already transmitting presentation.

11 Status of presentation

incompatible with the

request

A request incompatible with the status of the presentation has been

made. For example: request for transmission presentation

initialization, for an already transmitting presentation.

12 Emission initialization correct

and ended

A request for transmission presentation initialization has been

processed correctly.

13 Transmission conversión

correct and ended

The transmisson conversión process has been executed correctly.

14 Transmission conversor does

not exist in the profile

The conversor suitable for the remote EDITRAN/G presentation

session profile does not exist or can not be found.

15 Presentation profile does not

exist

We must register the corresponding presentation profile in the

EDITRAN/G administrator.

16 Session profile does not exist We must register the corresponding session profile in the EDITRAN/P

administrator.

17 Transmission request to

EDITRAN (A1R)

A request for transmission has been made.

18 Inform EDITRAN (A8R) of a

buffer upload

The buffer file has been uploaded and is ready to be sent.

19 Option not yet implemented We have chosen some of the options that are not implemented in

this version.

20 Request EDITRAN (EDP) for

end of transmission

A request to interrupt a current transmission has been made.

21 End of transmission correct

and finished

A request for end of transmission has been processed correctly.

22 Reception initialization

correct and finished

A request for reception initialization has been processed correctly.

23 Reception converter does not

exist in the profile

The converter program necessary to process the received data does

not exist or cannot be found.

24 Error in the transmission

conversión process

The conversion before uploading the transmission presentation

cannot be done. Consult the file editrang.out to determine the cause

of the error.



25 Error in the reception

conversion process

The conversion before uploading the reception presentation cannot

be done. Consult the file editrang.out to determine the cause of the

error.

26 Reception conversion correct

and finished

The process of reception conversion has been executed correctly.

27 Ask EDITRAN (A2R) for

reception

A request for reception has been made.

28 Ask EDITRAN (EDR) for end

of reception

A request for interrupting the current reception has been made.

29 End of reception correct and

finished

A request for end of reception has been processed correctly.

30 Request for EDITRAN (A1P)

transmission

A request for transmission has been received. The upload of the

transmission buffer (if it is not ready) is ordered.

31 Request for EDITRAN (A2P)

reception

A request for reception has been received. The download of the

reception buffer is ordered.

32 EDITRAN session transmitted

(A3P)

The transmission of an EDTRAN session has been completed.

33 EDITRAN session received

(A4P)

The reception of an EDITRAN session has been completed.

34 EDITRAN session interrupted

(A7I)

An EDITRAN session that was transmitting or receiving has been

interrupted.

35 End after EDITRAN (A3R)

session transmission

EDITRAN is indicated that the process after transmission has ended

correctly.

36 End after EDITRAN (A4R)

session reception

EDITRAN is indicated that the process after reception has ended

correctly.

37 Presentation is interrupted All the transmission sessions that comprise the presentation are

interrupted.

38 Informs about buffer not

loaded to EDITRAN (A1R)

A transmission request has been received while the corresponding

buffer was not ready yet.

39 Launches user process

before transmission

The user process indicated in the profiles has been launched.

40 User process before

transmission is finished

The user process indicated in the profiles has ended correctly.

41 Error in the user process

before transmission

The user process indicated in the profiles has ended with an error.

Consult the cause in the file editrang.out.

42 Launches user process

before reception


43 User process before

transmission is finished



before reception



45 Launches user process after

transmission


46 User process after

transmission is ended



after transmission



48 Launches user process after

reception


49 User process after reception

is ended



after reception



51 Launches exception user

process




52 Exception user process is

ended


53 Error in the exception user

process



54 Error in the download. There

are no full received buffers

The download of an interrupted presentation has been requested.

55 Request for transmission

initialization

A request for initialization of a transmission presentation has been

made.

56 Informs EDITRAN (A2R)

about buffer not ready

EDITRAN/P is notified about an error while preparing the receptor

buffer.

57 Previous request executing Concurrent requests have been made for the same presentation and

direction.

58 Error in accessing the status

file

Error while accessing the file editrang.sts. This can cause a

malfunction of EDITRAN/G.

59 The remote EDITRAN/G is

modified

In version 5.0 and higher, the remote version of the presentation

profile is automatically updated.

60 Waiting for confirmation of

remote download

The emission is TRANSMITTED but the system is waiting for the

result of the remote download to be terminated.

61 Remote download confirmed The result of the remote dowlonad has been received.

62 Waiting for remote download

is cancelled

The user has decided to initialize a transmission that was waiting to

receive the remote download confirmation.



5.3.2. EDITRAN/G result codes

In this table are documented the different error codes that can occur during the

transformation of application files into temporary buffer files and viceversa.

The table will show:

COD is the numeric value passed as parameter to the user scripts, and the value

returned by the API EDITRAN/G.

ID is the alias that identifies the error in the messages recorded in the log file.

MESSAGE is a brief description of the cause of the error.

COD ID MESSAGE

0 The result is correct.

59 SCRIPT_EXEC Invalid option in the converter command.

64 OPEN_IN Error when opening the emitted application file.

65 OPEN_OUT Error when opening the received application file.

66 READ_CTRL Error when Reading control information in BUFFER or CSB.

67 WRITE_CTRL Error when writing control information in BUFFER or CSB.

68 WRITE_DATA Error when writing data in BUFFER or CSB.

69 ZERO_REC BUFFER file without uploaded records.

70 ALLOC_ERROR Internal error: memory management.

71 OPEN_REL Error when opening temporary file .rel.

72 WRITE_REL Error when writing on temporary file .rel.

73 WRITE_OUT Error when writing on the received application file.

74 SEQUENCE_CSB CSB wrong file: sequence error.

75 TOTAL_FILES CSB wrong file: error in the total number of files.

76 TYPE_FILE Unknown file format.

77 LENGTH_CSBREC CSB wrong file: error in the length of the files.

79 SIZE_FILERECS Mismatch in the number of records of the application file. The total number of

records indicated in control fields of the CSB does not match the downloaded

ones.

80 TOTAL_CSBRECS CSB wrong file: error in the total number of records.

81 SIZE_FILEBYTES Mismatch in the total of bytes of the application file. The number of bytes

indicated in the control fields of the CSB does not match the downloaded ones.

82 SYNCS_CSB Mismatch in the number of synchronisms of the CSB.

83 CFG_LENGTH Application file with a record lower than the one given in the profile. Check the

features of the files to be transmitted.

84 OPEN_STS Error when opening the EDITRAN/G status file.

85 OPEN_CSB Error when opening/creating CSB file.

86 NO_PERFILG_LOCAL The EDITRAN/G local profile does not exist.

87 NO_PERFILG The presentation profile does not exist.

88 EXEC_CONVER Generic error when converting into CSB.

89 EXEC_CARGADOR Error when loading/downloading BUFFER.

90 CFG_NO_FILES None of the files specified in the profile as transmission files exist, or they

cannot be found.

91 USER_SCRIPT Error when executing user script.

92 PREVIOUS_REQ There is a previous request pending.

93 PROFILES The presentation profile is uncompatible with the upload/download process.

94 CANCELED_REQ Request cancelled.

95 PROC_ERROR Internal error: process creation.

96 SYNC_ERROR Internal error: synchronization among processes.

97 NO_LICENSE There is a license problema to execute some of the required functions.

98 CRYPT_ERROR Error in the chryptographic treatment of the data.



99 HDRFILE Internal error: invalid control headers.

200 NO_ACK The remote download could not be confirmed.

104 EXCEPT_P Exception: abort.

110 EXCEPT_P Exception: operator.

120 EXCEPT_P Exception: incorrect remote buffer. Launchs previous.

121 EXCEPT_P Exception: incorrect remote buffer. Previous does not exist.

122 EXCEPT_P Exception: incorrect remote buffer. Previous is possibly executing.

123 EXCEPT_P Exception: incorrect remote buffer. Number of exchange session incorrect.

124 EXCEPT_P Exception: incorrect remote buffer. Number of total records.

130 EXCEPT_P Exception: release.

140 EXCEPT_P Exception: excess of retries to transmit.

160 EXCEPT_P Exception: mismatch of totals.

170 EXCEPT_P Exception: excess of synchronism retries.

190 EXCEPT_P Exception: excess of retries to end transmission.

240 EXCEPT_P Exception: profiles.

250 EXCEPT_P Exception: file not ready.

5.3.3. Exception codes

These codes are passed as argument to the exception user procedure (procedimiento de usuario de excepción) to indicate the cause of the presentation interruption.

CODE CAUSE EXPLANATION

004 Abort Interruption because the link failed, or due to unknown causes.

010 Operator Interruption requested by the operator.

020 Incorrect remote buffer.

Launches previous

The remote entity doesn’t have its Buffer File available. The remote

EDITRAN will start, automatically, the process that prepares the Buffer File

and will request the transmission if the profile allows it. This code only

occurs when the remote entities are zOS or iSeries.


There is no previous

The remote entity doesn’t have its Buffer File available. The remote

EDITRAN is not set to launch automatically the process that prepares it, so

this situation won’t be solved until the remote operator proceeds.


Previous possibly

executing

The remote entity doesn’t have its Buffer File available because it is still in

use. In many cases, it can occur because the remote EDITRAN is still

downloading.


Incorrect Exchange

session number

The remote buffer is in a wrong state. The exchange number doesn’t

match.


Total number of logs

The remote buffer is in a wrong state. The total number of logs doesn’t

match.

030 Release Interruption due to a release sent by the remote node.

040 Excess of transmission

retries

060 Protocol error when

requesting synchronism

070 Excess of synchronism

retries

090 Excess of end of

emission retries

140 Profiles The transmission is interrupted because some of the parameters of the

session profile are incompatible with the Buffer File or it doesn’t allow it.

For example, if the Buffer is ciphered and the session is set to zip during

the transmission.

150 File not ready The transmission is interrupted because the local Buffer File is in a wrong

state. In these cases, is advisable to initialize the presentation.



5.4. TABLE OF A7I CODES (TO RETRY – NOT TO RETRY)

A7I codes are listed according to whether they can be retried or not by the application.

The codes that cannot be retried are the following:

004, 020, 022, 023, 024, 100, 110, 140

(Note: 020 and 022 only if the EXTREME-CALLER="X" or "R" from the involved session).

The codes for which we can retry for a finite number of times (otherwise there can be a

loop situation) are:

020, 022, 025, 030, 040, 050, 060, 070, 080, 090,150

(Note: 020 and 022 only if the EXTREME-CALLER="L" from the involved session).

5.5. A7I CODES TABLE (ALARM GENERATION)

If we hired the module Statistics and Alarms (EDITRAN/EA) (Estadísticas y Alarmas

(EDITRAN/EA)), the errors that occur while uploading and downloading, as well as while

interrupting transmission, can be notified through an alarm (external, SMS or e-mail). All A7I

codes but 020 are processed as exceptions to be notified.

For further information about how works EDITRAN/EA module, see the corresponding manual.


Centros de Competencia

eCommerce

Avda. de Bruselas 35

28108 Alcobendas.

Madrid, España

T. +34 91 480 80 80

T. +34 91 480 50 00

www.indracompany.com

Documents

EDITRAN/G - Indraeditran.indra.es/EN/doc/win_unix/editran/EDITRAN_G_EN.pdf · EDITRAN/G Application Generic Interface Windows/Unix User manual INDRA 17/03/2017