EDITRAN/PX - montilla.indra.esmontilla.indra.es/EN/doc/IMS/actual/EPR52USIA_EN.pdf · In the following diagram, a basic design of IP connections in EDITRAN is presented, with accesses

EDITRAN/PX

EDITRAN Gateway

CICS-IMS

User Manual.

INDRA May 2018

EDITRAN/PX CICS-IMS Manual de usuario. CONTENTS

INDRA. All rights reserved. EDITRAN/PX

1. INTRODUCTION AND REQUIREMENTS .............................................................................................. 1-1

2. MAIN FEATURES ................................................................................................................................. 2-1

3. DEFINITIONS AND CHANGES (OS/390 – Z/OS) ................................................................................. 3-1

3.1. CICS Version ................................................................................................................................................... 3-1 3.1.1. DEFINITIONs ............................................................................................................................................................................................................................. 3-1 3.1.2. EDITRAN/P FIELDS (profiles). ........................................................................................................................................................................................... 3-2 3.1.3. TRACE QUERY .......................................................................................................................................................................................................................... 3-3 3.1.4. BACKUP. ..................................................................................................................................................................................................................................... 3-5 3.1.5. Error messages x’20’ and release x’13’ ........................................................................................................................................................................ 3-5

3.2. IMS version ..................................................................................................................................................... 3-6

4. EDITRAN/PX IN UNIX AND WINDOWS .............................................................................................. 4-1

EDITRAN/PX CICS-IMS Manual de usuario. ‎1.INTRODUCTION AND REQUIREMENTS

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

1. INTRODUCTION AND REQUIREMENTS

EDITRAN/PX is a software utility that is implemented together with EDITRAN/TCP, and it is

used to provide the latter with greater security and control.

In the following diagram, a basic design of IP connections in EDITRAN is presented, with

accesses controlled by two firewalls, normally of a different technology. However, in this

diagram there are "two different operating situations" (both with EDITRAN running under

TCP/IP in the teleprocessing monitor):

All EDITRAN data, including connections, should take the "normal" path, i.e., in both

directions the path would be: remote EDITRAN-Router-Firewall-Firewall-IP network.

This would be the normal situation with EDITRAN/TCP.

All EDITRAN data, including connections, should take the EDITRAN-Router - Firewall -

EDITRAN/PX - Firewall – remote - IP network path in both directions. This would be

the situation with EDITRAN/TCP including EDITRAN/PX (software running on

EDITRAN Proxy). EDITRAN Proxy is a Windows, UNIX or Linux machine that is

located in the entity's DMZ.

In the first situation, when working without EDITRAN/PX, a number of inconveniences

arise:

The host is not isolated from the outside. Somehow, it is "seen directly" from the end

nodes.

The firewall-router must be managed constantly. When a remote entity gives us its

IP address, we should normally enable it. When that entity changes its IP, we must

"refresh" it. The same applies to the remote ports (if controlled). In turn, when the

internal IPs change, it requires "refreshing" those changes. This whole maintenance

situation is complicated by the widespread use of NAT.

Internal network

DMZ

Router Nat

Firewall

Firewall

INTERNET

External

Web Server SMTP

Server

PROXY

EDITRAN

EDITRAN

Mail

Gateway



In the second situation, when working with EDITRAN/PX, the above uncertainties are

resolved:

The host is isolated from the outside. Its only possible data connection and

transmission is relegated to a two-way data exchange between EDITRAN-router-

firewall-EDITRAN Proxy. In order for this data to reach the remote entity or to be

received from the remote entity, a second option is enabled via a remote Server-proxy-

firewall-IP network. This is not a double data transmission, as will be explained later.

The router-firewall management and maintenance are minimal. The end nodes are

provided with the IP and listening port of the EDITRAN Proxy, so they only know the IP.

This allows "enabling" the entire external network so that only the proxy is accessed.

EDITRAN/PX will only enable a connection to the host if we are sure that in the end

node EDITRAN dialogues.

The features and elements of EDITRAN that is working with EDITRAN/PX are as follows:

EDITRAN/PX is a software that runs in the DMZ, specifically in EDITRAN Proxy (in

addition, there is a software that also runs in the teleprocessing monitor). This is not

a second intermediate EDITRAN. This software acts as a controller and as a data

gateway.

EDITRAN/PX requires EDITRAN/TCP on the host. It is contracted independently from

the latter, and it is a software-hardware that adds security to the EDITRAN

transmissions. In this sense, if EDITRAN/PX receives an external call (EDI or non-EDI

remote node), it must also receive EDITRAN user data with recognized format. If

they do not arrive or they are not recognized, EDITRAN/PX closes the socket that

was opened from the outside, without the EDITRAN of the teleprocessing monitor

"noticing or feeling anything".

The features of the EDITRAN/PX transmission are:

EDITRAN host (also z/OS) dialogues over TCP/IP with EDITRAN/PX software,

running on WINDOWS (2003, XP, 7...), UNIX machines. (SOLARIS, AIX, HP) and

Linux.

EDITRAN/PX dialogues with the end nodes in a connection different from the

previous one, but in the same data transmission (not in a second transmission).

In outgoing calls from the teleprocessing monitor, it provides EDITRAN/PX with

the TCP/IP information needed to connect to the remote node (IP address and

destination port). EDITRAN/PX keeps the host socket open and connects a

second socket to the remote node. From then on, it routes the data from one

socket to another.

In incoming calls to the teleprocessing monitor, the end nodes call the IP

address and port enabled in EDITRAN/PX (through a socket), and send some

EDITRAN user data. If EDITRAN/PX recognizes their format, it opens a second

socket with the teleprocessing monitor (IP address and EDITRAN port), and it

passes the user data and the IP and remote port information to it. From then

on, it routes the data from one socket to another.

EDITRAN/PX, if it detects TCP/IP errors, provides the diagnostic elements

(errno and retcode) to the teleprocessing monitor to inform it.



Using EDITRAN/TCP + EDITRAN/PX locally, the remote nodes can have any of the

following configurations:

EDITRAN/TCP

EDITRAN/TCP + EDITRAN/PX

Up to 999 EDITRAN/PX can exist in the DMZ; for this, up to 999 IP addresses of the

Proxy server will be indicated in EDITRAN/P of the z/OS. In this way, the backups are

possible in case of outgoing calls (for example, if any of the proxy servers are down),

the load balancing (some sessions will have one as first proxy, others will have

another one, etc.), or by means of a group 1 of nodes to call the Proxy server 1, and a

group 2 to call the Proxy server 2, etc.

It requires EDITRAN/P remote version greater than 4.0 (both nodes must have at

least EDITRAN 4.1).

Gateway 1-n

EDITRAN TCP/IP

TCP/IP LAN

EDITRAN

TCP/IP WAN

EDITRAN

Remote gateway

EDITRAN/PX CICS-IMS Manual de usuario. ‎2.MAIN FEATURES


2. MAIN FEATURES

The increasing implementation of the TCP/IP protocol in EDITRAN is associated with new

needs arising from the use of the Internet. The Internet brings a number of communication

advantages between nodes, but it also adds a number of uncertainties such as the

communication security.

Here the need arises to use products such as firewalls that allow us to control security

uncertainties as much as possible and other products such as EDITRANPX, specifically

developed for EDITRAN that will avoid most DoS (Denial of Service) attacks, bombing, etc.,

thus protecting the HOST from the possible dangers of placing it in the demilitarized zone.

Here are some of the features that make EDITRANPX an essential element in a public

TCP/IP network.

Multiplatform

EDITRANPX is available for Microsoft Windows operating systems and UNIX operating

systems, such as Solaris, Linux..., thus allowing us to choose the right platform for each

need.

Optimization (Multi-Threading)

One of the main concerns when designing EDITRANPX has been the search for the

highest possible efficiency. In this way, EDITRANPX is built in such a way that it creates

a runtime thread for each connected client, allowing both one connection not to affect

the others and to achieve maximum efficiency in multi-processor systems.

TimeOut

There is a separate TimeOut prior to the connection with EDITRAN in the HOST that will

close the connection to a client when it connects but does not send any data. This

prevents the HOST from being attacked by a DoS attempt due to a lack of free

connections.

Bombing

In addition to having a TimeOut, EDITRANPX has a system that avoids the attempt of

multiple connections from the same client with the purpose of trying a Dos. These

connections will never reach the internal EDITRAN, avoiding loading it. In addition, when

an attempt of bombing is detected, the connection with the cause is disconnected.

Security

As already mentioned, EDITRANPX avoids having to place EDITRAN in the demilitarized

zone or DMZ, since EDITRANPX will go there; so it increases security, since EDITRANPX

is kept on the internal network, outside the DMZ.

EDITRAN protocol validation

One of the main features of EDITRANPX is that it recognizes the EDITRAN protocol and

in this way, it will prevent connections that do not comply with the protocol from

reaching the internal EDITRAN, thus making a previous job and releasing EDITRAN from

it.

Syslog generation

EDITRANPX has its own log generation system and it uses the system syslog that

allows storing it or sending the same log to another machine.

EDITRAN/PX CICS-IMS Manual de usuario. ‎3.DEFINITIONS AND CHANGES (OS/390 – Z/OS)


3. DEFINITIONS AND CHANGES (OS/390 – Z/OS)

3.1. CICS Version

3.1.1. DEFINITIONs

For the definitions, please, refer to the manual IP52USIC (cics), except:

Definition of the EZACONFG file. When the listener is defined, SECEXIT = EDITR-PR will be

specified, so that it is known that this listener will handle this type of connection. If

EDITRAN/TCP is available, another listener will be defined with SECEXIT = EDITRAN

(associated to another port and another transid with the same program).

EZAC,ALTER,LISTENER

APPLID ===> BMCIDATR APPLID of CICS System

TRANID ===> ZTBA Transaction Name of Listener

PORT ===> 07777 Port Number of Listener

IMMEDIATE ===> NO Immediate Startup Yes|No

BACKLOG ===> 020 Backlog Value for Listener

NUMSOCK ===> 100 Number of Sockets in Listener

MINMSGL ===> 004 Minimum Message Length

ACCTIME ===> 060 Timeout Value for ACCEPT

GIVTIME ===> 010 Timeout Value for GIVESOCKET

REATIME ===> 000 Timeout Value for READ

FASTRD (*) ===> YES Read Immediately Yes|No

TRANTRN ===> NO Translate TRNID Yes|No

TRANUSR ===> NO Translate User Data Yes|No

SECEXIT ===> EDITR-PR Name of Security Exit

(*) FASTRD DISAPPEARS IN ZOS HIGH VERSIONS In CICS, in addition to all the EDITRAN/TCP/IP programs, the ZTBPO203 and ZTBPOTPR programs must be registered. DEFINE PROGRAM(ZTBPO203) GROUP(EDITRAN) LANGUAGE(COBOL) DATALOCATION(ANY)

DEFINE PROGRAM(ZTBPOTPR) GROUP(EDITRAN) LANGUAGE(COBOL) DATALOCATION(ANY)



3.1.2. EDITRAN/P FIELDS (profiles).

For the definitions, please, refer to the manual ED52USUC (chapter 1.3.1, 1.3.2, 1.3.3). See

the local environment, session and line screens.

Environment:

CAMPOS TCP/IP: TCPNAME...: TCPIPB

TIME-OUT USER DATA MAX(MSS)..: 020 NRO.CONEX.SIMULT.LISTENER....: 004

USAR SERVER DNS EN LLAM.ENT..: S TO.MILISEG ENVIOS (001-999)..: 999

PF7 - RETROCEDER

Session:

TIPO CONEXION (X=X25,T=PAD,P=TX-X25,S=TX-PAD,I=TCP/IP,Y=PROXY,2=LU62)..: Y

| 3.- LINEAS LOCALES PROXY: SEL.GENERICA S/N: N |

| REF01: REF02: REF03: REF04: REF05: REF06: |

| |

| 5.- LINEAS REMOTAS TCP/IP (PARA IR CON O SIN PROXY): SEL.GENERICA S/N: N |

| REF01: REF02: REF03: REF04: REF05: REF06: |

LOCAL PX Lines: | PROPIETARIO: L TIPO LINEA.: P NIF........: 0 0000000 0 |

| S PROPIET. TIP NUM CARACTERISTICAS DE LA LINEA |

| - --------- --- --- ------------------------------------------------------- |

| LOCAL PX 001 172.026.130.019 -07779 |

| LOCAL PX 002 DMENENDEZ.INDRA.ES -07779 |

| LOCAL PX 003 GEULOGIO.INDRA.ES -07778 |

REMOTE IP Lines: | PROPIETARIO: R TIPO LINEA.: I NIF........: 0 0009998 0 |

| S PROPIET. TIP NUM CARACTERISTICAS DE LA LINEA |

| - --------- --- --- ------------------------------------------------------- |

| 000099980 IP 001 192.168.172.091 -07777 |

| 000099980 IP 002 172.022.164.071 -07777 |

| 000099980 IP 003 IMSPRUE.COMS.INDRA.ES -08888 |

In the session log, the connection type is indicated (Y = EDITRAN/proxy). If the node does

not have EDITRAN/PX, the connection type in its profile will be I (IP). If the node has an

EDITRAN/PX, both nodes code Y. Local PX lines and IP remote lines are also indicated.



3.1.3. TRACE QUERY

A network message protocol has been implemented that is easily interpretable due to its

similarity to X25, with X0B call request, X0F acceptance and X13 release. The socket is the

CICS task number and lu is the local or remote port (depending on whether it is an incoming or

outgoing call). An x20 message is included to display errors (refer to the log with cause-

diagnosis. The documentation on ERRNO, RETCODE and error messages in the TCPCICS,

provided by the macros used for EXTENDED SOCKETS is available in Appendix C of the IBM

TCP/IP for MVS manual. CICS TCP/IP Socket Interface Guide and Reference. Document Number

SC31-7131-03. Program number 5655 HAL. File Number S370/4300/30xx-50. See also

Document Number: SC31-8518-00. If the corresponding errno does not appear, the error may

be OS390 V2R5 OPEN EDITION, so that it comes in F1AF9000 IP Planning and Migration

Guide

16/06/2004 CONSULTA DE FICHEROS EDITRAN 5.2

08:33:02 CONSULTA DE TRAZA

SESION : FECHA : 16/06/2004

SEL SESION HORA S MSJE NSM/LU T COMENTARIO

= ============================= ====== = ==== ====== = ===================

S00DI S00TI EDIPR1 083230 S STC T/O DE CONEXION

S00DI S00TI EDIPR1 083230 S ETT 07777 0B 0002

S00DI S00TI EDIPR1 083233 E ETT 07777 0F 00D8 0002

S00DI S00TI EDIPR1 083233 S SAP PET. NOTIFICACION 00

S00DI S00TI EDIPR1 083233 S STN T/O DE NOTIFICACION

S00DI S00TI EDIPR1 083237 E SAR+ RESP. NOTIFICACION 00

S00DI S00TI EDIPR1 083249 E E11 PETICION LIBERACION

S00DI S00TI EDIPR1 083249 S SAB SOL. LIBERACION 02

S00DI S00TI EDIPR1 083249 E ETT 07777 13 00D8 0000 00 0F

S S00DI S00TI EDIPR1 083258 E ETT 03827 0B 00FD

S00DI S00TI EDIPR1 083258 S ETT 03827 0F 00FD

S00DI S00TI EDIPR1 083258 S STS T/O DE ESPERA DE SAP

S00DI S00TI EDIPR1 083302 E SAP IND. NOTIFICACION 00

S00DI S00TI EDIPR1 083302 S SAR+ RESP. NOTIFICACION 00

The meaning of the previous trace, for example for the marked message, is the

following:

1. An incoming message (E) appears in the S and Comment columns. It is an x'0B'

message (call indication).

2. The remote port (3827) appears in the NSM/LU column.

3. The Comment column shows a cvc, x'00FD' or 253 in decimal, which is actually the CICS

(transid ZTBBB) task number that processes the connection indication. It is important

to note that if this number is making very big jumps in a very short time, we will find

that the CICS is very loaded (it is running many tasks simultaneously). If problems are

detected in the CICS, check the local environment (number of connections per listener),

the parameterization of the CICS to VTAM definition, in particular the EAS parameter

(number of active communications simultaneously) and the relationship of the

transaction Tclass parameters with the SIT CMXT parameter (transid can be pointed to

a class, and in the SIT the transid number of each of the classes is limited). In the SIT

the MXT parameter indicates the number of CICS transid.

4. In some cases, some digits appear, which correspond to the CNID (application identifier,

in case of call request, to return the same in accepted call).

5. Other types of messages are x'0F' (accepted call), x'13' (release) and x'20' (error), in

addition to the x'0B' itself which does make sense, S means call request.

6. In case of EDITRAN/Proxy the message key is ETT.



If we select the previous message (expanded trace), we see the complete content of the

incoming call (among other things, the above mentioned x'0B' fields appear):

x'C5E3E340' is the 'ETT' key.

X'0B' indicates sol-lla.

X'0EF3' is the EDITRAN/PROXY port of windows-unix (3827).

X'00FD' is the identifier of the task number (253).

X'E8' Indicates the type of connection (Y).

X'0F' is the length of user data (15)

X'C0....0A' are the user data x25.

X'F1F7....F6' is the ip of EDITRAN/PROXY of windows-unix (172.022.164.076)

X'1E69' is the remote port (7779)

X'D6E2F3F0F0F0C2', in ebcdic OS390B is the DNS associated with the final ip (node).



SESION TRAZA...: S00DI S00TI EDIPR1

FECHA SSAAMMDD.: 20040616 HORA HHMMSS....: 083258 ENTRADA/SALIDA.: E

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....

C5E3E3400B00000EF300FD00000000000000000000D70000000000000000000FC0A3300000

9999304544495458310A000000000000000000000000000000000000000000000000404040

40404040404040404040404040404040404040404040404040404040404040404040404040

404040404040404040F1F7F24BF0F2F24BF1F6F44BF0F7F61E634040404040404040404040

40404040404040404040404040404040404040404040404040404040404040404040404040

40404040404040404040D6E2F3F9F0C2F1F0F0F0F9F9F9F4F0F2F0F0F0F9F9F9F4F0C5C4C9

D7D9F100000000000000000000000000000000000000000000000000000000000000000000

01B34040400000404040F0F8F3F2F5F8404040404040

PF2: SWITCH HEXADECIMAL - CARACTER

If we press PF2, it is displayed in text format, it also includes information about the real

time of the process (it does not have to be the same as the trace time), and about the length

of the processed message (it does not have to be the same as the networked one).



SESION TRAZA...: S00DI S00TI EDIPR1

FECHA SSAAMMDD.: 20040616 HORA HHMMSS....: 083258 ENTRADA/SALIDA.: E

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....

ETT . .3 . P .{t. rr........

172.022.164.076. ...c..

OS390B100099940200099940EDI

PR1

.. 083258

HORA DE PROCESO DE MENSAJE : 083258

LONGITUD DE MENSAJE TRATADO: 000435

PF2: SWITCH HEXADECIMAL - CARACTER

For more detailed traces of INDRA, encode operating-system = EDPR, operating-system-

version = spaces or MULT, and Maximum-cvcs-number = 999. In this case, ts ZTBPEDPR

(MULT) or TS ZTBH+(MMSS) (minutes, seconds) (spaces) queues are created, with data on

writes and readings from the network, to be analysed by INDRA.



3.1.4. BACKUP.

The proxy connection backup system in case a call fails is as follows:

Local-proxy-ip-addr (1) – Ip-remote-addr(1)

....

Local-proxy-ip-addr (1) – Ip-remote-addr (n)

.....

Local-proxy-ip-addr (n) – Ip-remote-addr(1)

....

Local-proxy-ip-addr (n) – Ip-remote-addr (n)

3.1.5. Error messages x’20’ and release x’13’

See the manual IP52USIC. (cics)



3.2. IMS version

The same installation is required as for EDITRAN/TCP. For definitions, refer to the

ED52INSI manual.

The affected parameters of the EDITRAN/P profiles are listed in the above mentioned

manual and are described in the EDITRAN/P user manual. Please, refer to the EP52USUI

manual.

In the trace query, new messages have been entered to identify the sessions that use the

proxy, but are analogous to the messages that appear when using a native TCP.

02/02/17 CONSULTA DE LA TRAZA EDITRAN/P

11:26:48 5.2

s SESION FECHA HORA S CLA C NSM COMENTARIO

-------------------------- ----- -------- - --- - ------ ----------------------

000099980000099940000099 02-02 11:20:38 E X11 * ZTC120 INDIC. LIBERACION TCP

000000000000000000000000 02-02 11:21:50 E CON 1 INDICACION CONEX. TCP

000099980000099940000100 02-02 11:21:50 E TAK 0 ACEPTA CON. TCP(PROXY)

000099980000099940000100 02-02 11:21:50 S X00 ZTCP77 INDIC. CONEXION TCP

000099980000099940000100 02-02 11:21:50 E X00 ZTCP77 INDIC. CONEXION TCP

000099980000099940000100 02-02 11:21:51 E SAP PETICION SESION REMOTA

000099980000099940000100 02-02 11:21:51 S SAR ACEPTACION PET. SESION

000099980000099940000100 02-02 11:21:53 E ECP 8 PET. DE EMISION REMOTA

000099980000099940000100 02-02 11:21:53 S SCP 0 0 PET. INICIO DE EMISION

000099980000099940000100 02-02 11:21:54 E SCR 0 0 RESP. PETICION EMISION

000099980000099940000100 02-02 11:22:22 S SEP 0 1633 FIN DE EMISION LOCAL

000099980000099940000100 02-02 11:22:23 E SER 9 1633 EMISION CORRECTA FINAL

000099980000099940000100 02-02 11:22:23 S A3P SOLICITA POST. EMISION

000099980000099940000100 02-02 11:22:23 S EAB PETICION FIN DE SESION

000099980000099940000100 02-02 11:22:23 E EAB PETICION FIN DE SESION

000099980000099940000100 02-02 11:22:23 S SAB TRASM. CORRECTA Y FIN.

02/02/17 CONSULTA DE LA TRAZA EDITRAN/P

11:25:54 5.2

s SESION FECHA HORA S CLA C NSM COMENTARIO

-------------------------- ----- -------- - --- - ------ ----------------------

000099980000099930000062 02-02 11:23:50 E A4R FINAL. POST. RECEPC.00

000099980000099930000063 02-02 11:23:51 E A2R FINAL. PREVIO RECEPC00

000099980000099930000063 02-02 11:23:51 S EAP PETICION SESION

000099980000099930000063 02-02 11:23:51 E EAP PETICION SESION

000099980000099930000063 02-02 11:23:51 S E00 ZTC1 PETIC. CONEXION TCP

000099980000099930000063 02-02 11:23:52 E E00 ZTC1 PETIC. CONEXION TCP

000099980000099930000063 02-02 11:23:52 S SOC 1 PETICION CONEXION TCP

000099980000099930000063 02-02 11:23:52 S CON 1 PET. CONEX. TCP(PROXY)

000099980000099930000063 02-02 11:23:52 S X00 ZTC118 INDIC. CONEXION TCP

000099980000099930000063 02-02 11:23:52 E X00 ZTC118 INDIC. CONEXION TCP

000099980000099930000063 02-02 11:23:52 S SAP PETICION SESION

000099980000099930000063 02-02 11:23:53 E SAR ACEPTACION PET. SESION

000099980000099930000063 02-02 11:23:53 S ECP 8 PETICION DE RECEPCION

000099980000099930000063 02-02 11:23:53 E SDP 3 0 FICH.INCORRECTO RECEP.

000099980000099930000063 02-02 11:23:53 S A7I R020 INFORMATIVO A APLICAC.

000099980000099930000063 02-02 11:23:53 S EAB PETICION FIN DE SESION

These messages can be selected and will be displayed in extended mode as follows.



Incoming message for proxy session

------------------------------------------------------------------------------

| 02/02/17 GESTOR DEL EDITRAN EDITRAN/P |

| 11:28:48 CONSULTA DE LA TRAZA 5.2 |

------------------------------------------------------------------------------

| |

| CODIGO LOCAL: 000099980 CODIGO REMOTO: 000099940 APLICACION: 000100 |

| |

| 02/02/2017 11:21:50.77 000099980000099940000100 E TAK |

| CALL: TAKESOCKET SOCKET: 00000 NRO ERROR: 000000 |

| TCPNAME: |

| IP ORIGEN: 172.022.241.001 |

| IP PROXY: 172.022.241.001 |

| |

| PULSE <PF3> PARA SALIR |

| |

| |

| |

| |

| |

| |

| |

| |

| |

------------------------------------------------------------------------------

Incoming message for session without proxy

------------------------------------------------------------------------------



------------------------------------------------------------------------------

| |

| CODIGO LOCAL: 000099980 CODIGO REMOTO: 000099940 APLICACION: AESRSA |

| |

| 02/02/2017 11:30:33.26 000099980000099940AESRSA E TAK |

| CALL: TAKESOCKET SOCKET: 00000 NRO ERROR: 000000 |

| TCPNAME: |

| IP ORIGEN: 172.022.242.193 |

| |

| |


| |

| |

| |

| |

| |

| |

| |

| |

| |

------------------------------------------------------------------------------



Outgoing message for proxy session

------------------------------------------------------------------------------



------------------------------------------------------------------------------

| |

| CODIGO LOCAL: 000099980 CODIGO REMOTO: 000099930 APLICACION: 000063 |

| |

| 02/02/2017 11:23:52.08 000099980000099930000063 S CON |

| CALL: CONNECT SOCKET: 00001 NRO ERROR: 000036 |

| TCPNAME: TRAN: ZTC1 |

| IP DESTINO: 172.022.242.196:07777 |

| IP PROXY: 172.022.249.058:07776 |

| |


| |

| |

| |

| |

| |

| |

| |

| |

| |

------------------------------------------------------------------------------

Outgoing message for session without proxy

------------------------------------------------------------------------------



------------------------------------------------------------------------------

| |

| CODIGO LOCAL: 000099980 CODIGO REMOTO: 000099940 APLICACION: AESRSA |

| |

| 02/02/2017 11:31:52.93 000099980000099940AESRSA S CON |

| CALL: CONNECT SOCKET: 00000 NRO ERROR: 000036 |

| TCPNAME: TRAN: ZTCP |

| IP DESTINO: 172.022.242.193:07777 |

| |

| |


| |

| |

| |

| |

| |

| |

| |

| |

| |

------------------------------------------------------------------------------

EDITRAN/PX CICS-IMS Manual de usuario. ‎4.EDITRAN/PX IN UNIX AND WINDOWS


4. EDITRAN/PX IN UNIX AND WINDOWS

To install and set EDITRAN/PX in UNIX-WINDOWS environments see the corresponding

manual.


eCommerce

Competence Centers

Avda. de Bruselas 35

28108 Alcobendas.

Madrid, Spain

T. +34 91 480 80 80

T. +34 91 480 50 00

www.indracompany.com

Documents

EDITRAN/PX - montilla.indra.esmontilla.indra.es/EN/doc/IMS/actual/EPR52USIA_EN.pdf · In the following diagram, a basic design of IP connections in EDITRAN is presented, with accesses