EDITRAN/GT
Transmissions manager
OS/400
User manual
julio de 2019
EDITRAN/GT
ÍNDICE
1. INTRODUCTION ...................................................................................................................................... 1
2. MAIN MENU ............................................................................................................................................ 2
2.1 Starting EDItrangt................................................................................................................................................... 2
2.2 Stopping EDITRANGT subsystem .......................................................................................................................... 2
3. ADMINISTRATOR ................................................................................................................................... 3
3.1 Local environment ................................................................................................................................................... 4
3.2. Transmissions planner ........................................................................................................................................... 5
3.3. Transmissions manager ......................................................................................................................................... 9
4. TRANSMISSION CONTROL ................................................................................................................... 15
4.1 Consulting status ................................................................................................................................................... 16
4.2 Consulting log ........................................................................................................................................................ 19
EDITRAN/GT 1
1.INTRODUCTION
1. INTRODUCTION
The present document describes the functional specification of the Transmission Management System -hereinafter EDItranGT- version 1.0 of the communications platform
EDItran OS400.
The goal of EDItranGT v1.0 if providing a mechanism that allows the administrator or EDItran
user planning the transmissions of the application files (for both transmission or reception), so
that we can choose the periodicity of sends/receptions automatically, as well as determine the
action to be performed when there are failed attempts of transmission or reception.
The parameterization of temporality is performed by scheduling the sends and receptions by
associating each session to a date or a set of dates. The management of this system is made
by means of menu options detailed below.
To access EDItran/GT, we must execute the command EDIGT. Then, will be displayed the
EDItran/GT main menu.
EDITRAN/GT 2
2.MAIN MENU
2. MAIN MENU
The product is managed with this menu. Once EDItran/GT is installed, we need to define the
parameters for the local installation (local environment) and for the SESSIONS that are going to
be used.
2.1 Starting EDItrangt
To boot the planner, we have to type the option 0 in EDItranGT main menu. As a result of
this, in the EDItran subsystem is submitted a job named PFTAMSCDE.
The function of this job is periodically scanning the defined profiles file, and performing the
planned execution.
2.2 Stopping EDITRANGT subsystem
We can stop the planner typing the option 4 in the EDItran/GT main menu.
EDITRAN/GT 3
3.ADMINISTRATOR
3. ADMINISTRATOR
From this screen we can manage the parameters of the local environment, and also the
transmission planner and the transmission manager.
EDITRAN/GT 4
3.ADMINISTRATOR
3.1 Local environment
With the option 1 of the administrator, we will display the screen that allows the
management of the local environment.
EDITRAN/GT 5
3.ADMINISTRATOR
LOCAL ENVIRONMENT PARAMETERS
Where the fields have the following meaning:
LOCAL CODE (CÓDIGO-LOCAL): identification number of the EDItran user entity.
LOCAL NAME (NOMBRE LOCAL): literal that refers to the name of the EDItran user entity.
CYCLE INTERVAL (INTERVALO DEL CICLO): delay of the planner (in seconds). This is the
time between each revisión of the planned sessions table.
3.2. Transmissions planner
We can not plan if EDIgt is running.
With the option 2 of the administrator, we will display the screen that allows managing the
sessions.
EDITRAN/GT 6
3.ADMINISTRATOR
We have to specify the parameters that identify the EDItran session (local code, remote code
and application), and the desired option (Registration (Alta), Consultation (Consulta),
Unsubscription (Baja) or Modification (Modificación)). The meaning of the fields is the following:
LOCAL CODE (CÓDIGO-LOCAL): identification number of the EDItran user entity. With this
code, it will be recognized by all the entities interconnected to EDItran (if there are blanks,
the local environment is the general one).
REMOTE CODE (CÓDIGO-REMOTO): identification of the remote EDItran installation (for
example NIF number of the entity).
APPLICATION (APLICACIÓN): code of the EDItran application of the session.
CAR/EMI/INIC/REC: request for uploading, transmitting, initializating and receiving.
If we specify a generic option, will be displayed all the registered sessions.
EDITRAN/GT 7
3.ADMINISTRATOR
With “S”, we will select the one to be consulted, and then will appear the parameters for that session.
EDITRAN/GT 8
3.ADMINISTRATOR
c
Where we have the data of the planned date:
Day (Día): table with the week days during which will be executed the planned work. We
use 3 characters: Monday (LUN), Tuesday (MAR), Wednesday (MIE), Thursday (JUE), Friday
(VIE), Saturday (SAB), Sunday (DOM).
Week (Semana): table with the month weeks (1 2 3 4 5) in which will be executed the
planned work.
Month (Mes): table with the months of the year (1 2 3 4 5 6 7 8 9 10 11 12) in which
will be executed the planned work.
Time (Hora(HHMM)): momento when the planned work will begin to be executed.
EDITRAN/GT 9
3.ADMINISTRATOR
Excluding days (Excluir Días(ddmm)): table with 50 elements, to include the days that
are planned but don’t need execution. For example autonomic holidays, etc. In this case,
January 1st, December 25th and May 1st.
Including days (Incluir Días(ddmm)): table with 50 elements to include the days that
are not planned but need execution. In this case, April 3rd and July 11th.
3.3. Transmissions manager
With the option 3 of the administrator, appears the screen that allows managing the
transmissions.
EDITRAN/GT 10
3.ADMINISTRATOR
EDITRAN/GT 11
3.ADMINISTRATOR
We select the one we want to manage, and its parameters will appear.
EDITRAN/GT 12
3.ADMINISTRATOR
Transmission options (Opciones de Emisión)
File format (Formato de fichero):
Log (R-Registro): files with fixed length logs, in this case 72.
Hybrid (H-Híbrido): files without log format, but segmented to fit the indicated length.
This causes in the remote node a downloading of a file with fixed format and with the
specified length (in this case 72).
Binary (B-Binario): files with no log format, they don’t need length.
Transmit EDItran/G files (Emitir Ficheros EDItran/G (S/N)):
Indicates whether are used or not the files defined in the profiles of EDItran/g.
If we choose “S”, EditranGT will be used only as a planner for the date/time of send.
Option “N” allows choosing the following options:
By library/folder (Por Librería/Directorio): Library containing the files to be sent.
By creation date (Por fecha de creación) (only for native files systems AS/400): The files from the library indicated in the previous field, created from the entered date,
are transmitted.
By authorized user (Por usuario autorizado) (only for native files systems AS/400):
EDITRAN/GT 13
3.ADMINISTRATOR
Are transmitted the files created by the specified user.
By authorizations list (Por Lista de autorizaciones) (only for native files systems
AS/400): Are transmitted the files that have authorization in the specified authorization list.
By name (wildcard *) (Por nombre (comodín *)) (only for native files systems
AS/400): Name of the file to be transmitted. We use * as a wildcard to enter the names.
Time -Out (hhmm):
Time interval between requests.
Number of retries (Nro-Reintentos):
Number of times to retry.
Time-Out-Exc (hhmm):
Time interval between requests, if there are incidences.
Number of retries-Exc (Nro-Reintentos-Exc):
Number of times to retry the sends, in case there are incidences.
Reception options
Time-Out (hhmm):
EDITRAN/GT 14
3.ADMINISTRATOR
Time interval between requests.
Number of retries (Nro-Reintentos):
Number of times to retry sending.
Time-Out-Exc (hhmm):
Time interval between requests, if there are incidences.
Number of retries-Exc (Nro-Reintentos-Exc):
Number of times sendings will be retried, in case there are incidences.
Warn user (Avisar a usuario):
When the downloading of the received files is finished, a message to the specified user
is sent.
Warn list of users (Avisar a Lista de usuarios):
When the downloading of the received files is finished, a message to the specified list
of users is sent.
Message (Mensaje):
Text sent to the users we previously specified in the fields.
EDITRAN/GT 15
4.TRANSMISSION CONTROL
4. TRANSMISSION CONTROL
With the option 2 in the main menú, we enter the transmissions control, that consists of two
options for consulting status and consulting log.
EDITRAN/GT 16
4.TRANSMISSION CONTROL
4.1 Consulting status
EDITRAN/GT 17
4.TRANSMISSION CONTROL
We select the option we want to consult.
EDITRAN/GT 18
4.TRANSMISSION CONTROL
Starting date (Fecha Inicio):
Date of the first execution.
Starting time (Hora Inicio):
Time of the first execution.
End date (Fecha Fin):
Date of the last execution.
End time (Hora Fin):
Time of the last execution.
Timeout :
Time interval between requests.
Number of retries (Nro-Reintentos):
Number of times to retry sendings.
Retries counter (Contador de Reintentos):
Number of times the sendings have been retried.
Last retry time (Hora Ultimo Reintento):
Time of the last retry of the execution.
Time-Out-Exc:
EDITRAN/GT 19
4.TRANSMISSION CONTROL
Time interval between requests, if there are incidences.
Numer of retries-Exc (Nro-Reintentos-Exc):
Number of times the sendings will be retried, in case there are incidences.
Counter of exception retries (Contador de Reintentos de Excepción):
Number of times the sendings have been retried, in case there were incidences.
Time of the last exception retry (Hora Ultimo Reintento Excep):
Time when it was performed the last try of an exception.
Session status (Estado Sesión):
Status of the session in the planner process.
The possible status are:
00 .- INITIALIZED (INICIALIZADO)
01 .- WAITING FOR BEING ENDED (EN ESPERA DE FINALIZACIÓN)
02 .- ENDED (FINALIZADO)
03 .- INTERRUPTION RECEIVED (RECIBIDA INTERRUPCIÓN)
04 .- RETRYING (REINTENTANDO)
05 .- END OF INTERRUPTION RETRIES (FIN REINTENTOS INTERRUPCIÓN)
06 .- ONGOING PROCESS (PROCESO EN CURSO)
07 .- RETRYING FOR EXCEPTION (REINTENTANDO POR EXCEPCIÓN)
4.2 Consulting log
EDITRAN/GT 20
4.TRANSMISSION CONTROL
EDITRAN/GT 21
4.TRANSMISSION CONTROL
We select the session to consult.
EDITRAN/GT 22
4.TRANSMISSION CONTROL
EDITRAN/GT 1
4.TRANSMISSION CONTROL
Contact
T +34 91 480 80 80
Avda. de Bruselas 35
28108 Alcobendas,
Madrid, España
T +34 91 480 50 00
F +34 91 480 50 80
www.minsait.com