EDITRAN/G 5montilla.indra.es/EN/doc/CICS/actual/EG52USUA_EN.pdfwhere EDITRAN/P is executed, indicating whether its execution is correct or incorrect. Depending on the case, this may

EDITRAN/G 5.2

Application Generic Interface

CICS-IMS

User Manual

July 2019

EDITRAN/G 5.2

CONTENTS

1. INTRODUCTION ...................................................................................................................................... 1

2. GENERALIZATIONS ABOUT EDITRAN AND INTERFACES .................................................................... 2

2.1. COMMUNICATION BETWEEN EDITRAN AND INTERFACES .............................................................................. 2 2.1.1. FROM AN INTERFACE TO EDITRAN.................................................................................................................................................................................... 2 2.1.2. FROM EDITRAN TO AN INTERFACE.................................................................................................................................................................................... 2

3. EDITRAN/G FUNCTIONAL FEATURES ................................................................................................... 4

3.1. INTRODUCTION TO THE FUNCTIONAL FEATURES ........................................................................................... 4

3.2. EDITRAN/G GENERAL FEATURES ..................................................................................................................... 5

3.3. GENERAL FEATURES ......................................................................................................................................... 6

3.4. MACRO FILES ..................................................................................................................................................... 7

4. FUNCTIONS INVOKED FROM APPLICATION JCL ................................................................................... 8

4.1. EDITRAN/G PROCEDURES LAUNCHED FROM JCL............................................................................................. 8

4.2. REGISTRATION – CANCELLATION – MODIFICATION OF PROFILE BATCHES .................................................... 9

4.3. STATUS QUERYING (CRITICAL TRANSMISSION) .............................................................................................. 9

4.4. Processing of application files before-after upload-download .................................................................. 10

4.5. EDITRAN/G GENERIC REQUESTS .................................................................................................................... 11

5. SERVICE JCL .......................................................................................................................................... 14

5.1. FILE OF SENT AND RECEIVED FILES ............................................................................................................... 14

5.2. LIST OF PRESENTATION STATUSES ............................................................................................................... 17

6. ANNEX A. EDITRAN/G MESSAGES ...................................................................................................... 18

7. ANNEX B. USER PROGRAMS AND EXIT .............................................................................................. 35

7.1. USER PROGRAMS ............................................................................................................................................ 35 7.1.1. GENERAL DESCRIPTION ........................................................................................................................................................................................................35 7.1.2. INPUT / OUTPUT ELEMENTS ...............................................................................................................................................................................................35 7.1.3. CALL CONDITIONS....................................................................................................................................................................................................................35

7.2. BATCH SELF-OPERATOR ................................................................................................................................. 46 7.2.1. GENERAL DESCRIPTION ........................................................................................................................................................................................................46 7.2.2. INPUT / OUTPUT ELEMENTS ...............................................................................................................................................................................................46 7.2.3. CALL CONDITIONS....................................................................................................................................................................................................................49

7.3. USER EXIT. ....................................................................................................................................................... 51 7.3.1. GENERAL DESCRIPTION ........................................................................................................................................................................................................51 7.3.2. INPUT / OUTPUT ELEMENTS ...............................................................................................................................................................................................51 7.3.3. CALL CONDITIONS....................................................................................................................................................................................................................51

8. ANNEX C. MACRO FILES ...................................................................................................................... 60

8.1. DETAIL OF THE MACRO FILE PROCESS ........................................................................................................... 60 8.1.1. GENERALIZATIONS..................................................................................................................................................................................................................60 8.1.2. PROCESS OF ONLY ONE PRESENTATION SESSION. ..................................................................................................................................................61 8.1.3. PROCESS OF SEVERAL PRESENTATION SESSIONS. .................................................................................................................................................61

8.2. GENERIC INITIALIZATION OF TRANSMISSION STATUSES. ............................................................................ 62 8.2.1. GENERALIZATIONS..................................................................................................................................................................................................................62 8.2.2. INITIALIZATION PROCESS. ...................................................................................................................................................................................................62

9. ANNEX D. GENERATIONAL FILES ........................................................................................................ 64

9.1. GENERATION FILES OF TRANSMISSION APPLICATION ................................................................................. 64

9.2. GENERATION FILES OF RECEPTION APPLICATION ........................................................................................ 64 9.2.1. IMPORTANT NOTE ...................................................................................................................................................................................................................64

10. ANNEX F. TABLES (TRANSLATION AND CONVERSION) .................................................................... 65

11. ANNEX G. ERROR CODES AND CAUSES OF EDITRAN/CD .................................................................. 75

EDITRAN/G 5.2 1

1.INTRODUCTION

1. INTRODUCTION

EDITRAN/P transfers files, with a certain structure, from a local node to a remote node.

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 and download

programs that, altogether, are called application interface, or EDITRAN/G.

EDITRAN/G 5.2 2

2.GENERALIZATIONS ABOUT EDITRAN AND INTERFACES

2. GENERALIZATIONS ABOUT EDITRAN AND INTERFACES

2.1. COMMUNICATION BETWEEN EDITRAN AND INTERFACES

2.1.1. FROM AN INTERFACE TO EDITRAN

Broadly speaking, it could be said that this is about sending messages from batch programs

to CICS where EDITRAN/P is running.

In the EDITRAN installation JCL is provided, ZTBPJBAT for CICS, with which A5P messages

of types 1 to 4, 8 and A can be sent to a given transmission session, meaning as follows:

Type 1: Order of transmission upload and transmission start.

Type 2: Order of reception initialization and reception start.

Type 3: Order of process after transmission.

Type 4: Order of reception download.

Type 8: Order of transmission upload.

Type A: Order of reception initialization.

The A5P messages (P = 1 to 4) can also be sent, through mailing lists, to several

transmission sessions.

These orders make EDITRAN/P to launch the processes before and after

transmission/reception. From these processes, EDITRAN/P will be informed of their correct or

incorrect completion by means of the AnR(+) or AnR(-) messages, where n is from 1 to 4, 8

and A, corresponding to the A5P types mentioned above. Specifically:

A1R(+) : It orders EDITRAN/P to start the transmission.

A8R : It notifies EDITRAN/P the transmission upload.

A2R(+) : It orders EDITRAN/P to start the reception.

AAR : It notifies EDITRAN/P the reception initialization.

From the start-up of EDITRAN/G, EDITRAN/P can receive the following messages from the

interfaces:

EDP: Transmission interruption.

EDR: Reception interruption.

2.1.2. FROM EDITRAN TO AN INTERFACE

In the cases in question, it is not really about sending messages from EDITRAN/P to

another region where a process is being run, but of launching Jobs invoking procedures before

and after transmission/reception, with the contribution of certain values passed as

parameters.

These procedures will be launched only if they are specified in the corresponding

transmission session profile. In this case, an A5P always determines that the procedure

corresponding to its type has been launched, as we have seen above. However, the

procedures are also launched in other circumstances:

The procedure before transmission is launched when a transmission request is

received from the local operator or from a remote EDITRAN and the transmission

buffer is:

EDITRAN/G 5.2 3

2.GENERALIZATIONS ABOUT EDITRAN AND INTERFACES

Empty.

Not totally sent, but all records have been confirmed by the receiver, who

rejects the transmission.

Marked as "Interrupted".

The procedure before reception is launched when the reception buffer is in situations

similar to those we have just seen for the transmission.

The procedure after transmission is launched when this one finishes.

The procedure after reception is launched when this one finishes.

EDITRAN/P with EDITRAN/G will also launch the procedures before transmission or

reception when the corresponding buffer is closed to CICS. However, they will not be launched

if it is marked as "Not available". In this case, it will mean that there may be an earlier

procedure running.

EDITRAN/P may launch a procedure of exception or transmission interruption, A7I with a

reference code, according to which EDITRAN/G will change or not the status of the

transmission session to "Interrupted".

EDITRAN/G 5.2 4

3.EDITRAN/G FUNCTIONAL FEATURES

3. EDITRAN/G FUNCTIONAL FEATURES

Below are described the concepts that allow us to understand the operation of EDITRAN/G,

but without going into excessive operational details that correspond to the next chapters.

3.1. INTRODUCTION TO THE FUNCTIONAL FEATURES

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

General local environment: We define a set of parameters within the product, which

allow knowing the installation where the product is going to run. It also allows

identifying the local EDITRAN/G installation.

Secondary local environment (Sub-environment): It is optional and it allows

registering as many secondary environments as desired. With the Sub-environments,

they can be presented to the remote ones as if they were another Entity.

Remote entity: We have to define all the remote clients EDITRAN is going to

interconnect with.

Presentation application: Six alphanumeric characters identify it. Not to be

confused with those of EDITRAN/P that are called as if they were of transmission.

The nature of the information to be exchanged is defined somehow.

Presentation session: 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 three previous profiles that correspond to it.

A presentation session may comprise up to 20 EDITRAN/P transmission sessions,

depending on the 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

“loaded”, the transmission is ordered right away.

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

components. This file can be queried and listed applying different selection criteria.

EDITRAN/G has an interactive component to update and query the profiles, to give

operator commands and to query the log and the status of the presentation sessions. An

operator command of EDITRAN/G for a presentation session makes a JOB to be launched

invoking one of the EDITRAN/G procedures, ZTBGP1, ZTBGP2, ZTBGP3, ZTBGP4 or ZTBGP6,

or the name given to them during the installation, and specified in the corresponding

presentation session profile. These procedures can also be launched with a batch JCL or by

EDITRAN/P. The exception procedure, ZTBGP5 that is being installed, is only launched from

EDITRAN/P.

With batch JCLs provided during the installation, we can invoke the same functions we

invoke with the interactive operator. In EDITRAN/P, these procedures must be specified in the

transmission session profiles to be controlled by EDITRAN/G.

EDITRAN/G 5.2 5


In these procedures, we invoke directly some major programs that can call others and so

on. These programs can perform general functions of EDITRAN/G, or they can perform specific

functions. In the latter case, they are called "converters". At the end of the processes

before/after transmission/reception and exception, specified user programs can also be

invoked in the presentation session profile.

3.2. EDITRAN/G GENERAL FEATURES

The EDITRAN/G procedures include the DD of the following files:

EDITRAN/G (CICS) profiles.

EDITRAN/G (CICS) states.

EDITRAN/G log. It can be omitted if we do not wish to record messages in it.

ZTBGFLIS: Lists obtained in the execution of the procedure.

ZTBGFPRI: Extended messages referred to dynamic reservations of application files,

intermediate statuses and buffer files, and messages sent by the programs taking

part in the process, if they are not extracted from the system log.

ZTBGFINT: Internal reader that enables the execution of another job started by a user

program.

ZTBGFMSJ: If specified, extended messages referred to dynamic file reservations will

be listed in ZTBGFPRI. If not specified, these messages will not be listed.

In addition, for the CICS environment, EDITRAN/P profiles: Data are taken from the

transmission sessions that make up the presentation session. It ensures the

communication with a specific copy of EDITRAN (remember that the local

environment profile includes the CICS name and that of the interface transaction,

ZTBI by default).

For more information about cryptography, signature, alarms, statistics, key

management, file queues and other functionalities, etc., check the corresponding

manuals.

At the end of a procedure execution, a message is sent to the data interchange monitor

where EDITRAN/P is executed, indicating whether its execution is correct or incorrect.

Depending on the case, this may lead to a transmission or reception request. The completion

of a subsequent procedure invoked by the EDITRAN/G operator or by the application JCL is not

notified to EDITRAN/P.

When the processes after transmission or reception finish, the buffers can be optionally

deleted. If we choose not to delete the buffers in subsequent processes, we should take into

account that no remote request will be accepted to start a new presentation session until a

request for upload/transmission or initialization/reception is made from the local EDITRAN/G,

since a remote request would make the data we want to keep disappear from the previous

session.

Notes about buffers for CICS environment:

In the process of transmission upload or reception initialization we can DELETE/DEFINE

CLUSTER of buffers by taking data from the corresponding presentation session and

transmission session profiles.

EDITRAN/G 5.2 6


Specific buffers are always deleted/defined. Therefore, they must be specified to the CICS

as CLOSE, ENABLED. EDITRAN/P is responsible for opening them to the CICS when it receives

the control from EDITRAN/G, and closing them when it returns it.

There are two possible operating modes for matrix buffers:

Non-simultaneous update of EDITRAN/G and EDITRAN/P. It is defined by the user

with SHAREOPTION (2,3). The size of the control interval will be that of the maximum

use of the disk track, thus reducing the number of accesses to the disk and therefore

increasing the loading speed of the sessions. All the presentation sessions must be

loaded before the transmission start of any of them. Automatism must not be used

before the transmission.

Simultaneous update of EDITRAN/G and EDITRAN/P. The file definition is made by

EDITRAN/G with SHAREOPTION (3,3), the concurrency control system has been

changed in the update of matrix buffers, so that they are defined without CISIZE, and

this is taken by default.

Matrix buffers are defined automatically only if they don’t exist. If they already exist, the

records of the previous session are deleted where appropriate. We recommend using EXCII

buffers.

3.3. GENERAL FEATURES

There are general features and specific functions determined by the converters we used.

The following ones, among others, are general functions:

Possibility to process 999999 transmission and/or reception application files with

logs of fixed or variable length residing on MVS or USS.

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

identification of the presentation application does not correspond with the

transmission application defined in EDITRAN/P.

The information of a transmission application can be subjected to several

presentation optional functions: Cryptography, compression, EBCDIC/ASCII translation

and language table conversion, and it can be uploaded to a unique buffer or 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 the

remote EDITRAN/G to perform presentation operations conversely. The functions

described are performed in each file.

The system counts the presentation session number between two 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 node to another. There is a parameter in

the presentation session profile that allows us to specify if we want to increase the

presentation session number or not.

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

local EDITRAN/G. 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, cryptography, compression and/or CRC with certain

EDITRAN/G 5.2 7


limitations, but it does not make sense if they have already been made to the

interface.

In the 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

sender are coherent with the ones of the receiver, and so that it can check the

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

buffers is downloaded to one single application reception file or to as many

application files as they have been used during the transmission upload in the other

node, after having performed the presentation functions conversely.

3.4. MACRO FILES

Macro files refer to a sequential application file that contains data to be uploaded to

multiple presentation sessions, all their logs having an identification by which it is possible to

determine which session they correspond to.

The process detail of these files can be found in the Annexes.

EDITRAN/G 5.2 8

4.FUNCTIONS INVOKED FROM APPLICATION JCL

4. FUNCTIONS INVOKED FROM APPLICATION JCL

4.1. EDITRAN/G PROCEDURES LAUNCHED FROM JCL

There are a series of JCLs that can be executed the way we want (SUB, Planner, etc.). They

will make the same requests as from the EDITRAN/G Operator. These JCLs have a single step

that executes the corresponding procedure (before/after the transmission/reception) by

passing the following parameters:

SOURCE Mandatory ‘A’. It indicates that the request has been made by JCL.

FUNCTION Required function indicating the operation to be performed. The possible

values are commented in the JCL.

L0 indicates the Alias coded in the EDITRAN/P profiles. It is used to generate both

temporary files and reception application files generated by EDITRAN/G.

L1 They are the first 6 characters of the Local Code (General or Secondary).

L2 They are the last 3 characters of the Local Code (General or Secondary).

R1 They are the first 6 characters of the Code of the Remote Entity.

R2 They are the last 3 characters of the Code of the Remote Entity.

AP The name of the Presentation Application of EDITRAN/G.

DATA This parameter is only passed to the procedure of Status modification

(ZTBGJP6). It has the following format :

Xnnnmmmm Being:

X ==> E (Transmission)

R (Reception)

nnn ==> 999 (The Status is initialized)

000 (The Status is not initialized)

mmmm ==> Presentation Session Number

LF It is an optional parameter. It is used only for the procedure before transmission

(ZTBGP1). It has the values S/N (YES/NO) or null.

○ ‘S’ (YES) indicates that we want to upload a list of application files, even though

there are different ones in the profiles (in this case, if there is no list, the

procedure is interrupted.

○ ‘N’ or null indicates that the application files specified in profiles must be loaded.

If there are no files in the profiles, search the list ZTBGFCAR.

These JCL are listed below:

ZTBGJAPL JCL executing any requests of the EDITRAN/G operator.

ZTBGJMCR JCL executing the Macro file procedure before transmission.

ZTBGJP1 JCL executing the procedure before transmission.

ZTBGJFF1 JCL executing the procedure before transmission with EDITRAN/FF.

ZTBGJP2 JCL executing the procedure before reception.

ZTBGJP3 JCL executing the procedure after transmission.

ZTBGJP4 JCL executing the procedure after reception.

ZTBGJP6 JCL executing the Status modification procedure.

EDITRAN/G 5.2 9


4.2. REGISTRATION – CANCELLATION – MODIFICATION OF PROFILE BATCHES

See the manual EG52GPEA

4.3. STATUS QUERYING (CRITICAL TRANSMISSION)

This function allows controlling the completion-interruption of a presentation (for

transmission or reception). It consists of a JCL step, which does not end until the presentation

is passed to these statuses or until an interval imposed by parameters for this function is

fulfilled (for more information, see the manual EG51APIA). JCL is presented as follows:

//PASOTC EXEC PGM=ZTBGBUTC,

// PARM=’parm1parm2parm3parm4parm5parm6’

The meaning of parm* is the following:

1. Parameters that will finally pass as communication area with API:

1.1. Parm1- Function (01, 02, 03, 04) With function 01: Queries until meeting maximum

interval. Function 02: Queries until meeting time limit. Function 03: Immediate

queries. Function 04: see if it can be loaded

1.2. Parm2- Direction (E/R) (TRANSMISSION-RECEPTION)

1.3. Parm3- Presentation session

1.4. Parm4- Wait interval (hhmmss) between each query.

1.5. Parm5- Maximum interval or maximum time limit during which the process is to be

restarted if the status exploration criterion is not met.

2. Parameters only for ZTBGBUTC:

2.1. Parm6- Save list at the end of the process (S/N) (YES/NO) with the obtained results.

Example : PARM=’01E000099990000099940TELECA010422815324S’

1. Parm1 (Function 01) –Verify interrupted and finished status depending on the time

intervals.

2. Parm2 (Direction E) – Direction of the TRANSMISSION presentation

3. Parm3 (Presentation session): Origin: 000099990, Destination: 000099940, Application:

TELECA

4. Parm4 (Wait interval) – If the Presentation session does not find the statuses described in

TRANSMISSION, it will remain in WAIT for 1 hour, 4 minutes and 22 seconds, until it asks

again for these statuses. The maximum number of wait intervals to be carried out depends

on the parm5. The last wait interval is calculated according to the maximum interval, so if

the wait interval is 3862 seconds (1 hour, 4 minutes and 22 seconds), and the maximum

interval is 294804 seconds (81 hours, 53 minutes, 24 seconds), the formula will be

applied; 294804 /3862 = 76 wait intervals and the last interval is the rest (1292

seconds), although to this we must subtract the time in which there has been process

execution.

EDITRAN/G 5.2 10


5. Parm5 (Maximum process interval): If the requested statuses are not fulfilled, the process

will remain started for 81 hours, 53 minutes and 24 seconds. If zeros are specified in this

parameter, the control is immediately returned to the application.

6. Parm6 (Record-list S): If we want the ZTBGBUTC program to record a list with the obtained

results.

4.4. Processing of application files before-after upload-download

It incorporates the possibility that once the presentation file has been downloaded

correctly, it can be adapted to another format, it can be translated and converted, and the

carriage returns from an environment that uses them can be removed. This possibility covers

the transmission application files before loading them (adapt, translate and convert them

outside EDITRAN/G). This process is performed through the JCL ZTBGJFF4. It consists of the

following:

1. PARM. Three different parameters are passed, separated by commas:

1.1. Separators in hexadecimal to be removed. Usually UNIX send 2 x0A-x0D characters at

the end of each line. There may be 3 cases:

1.1.1. There are no separators. Four octets are indicated to spaces.

1.1.2. There is one x’YZ’ separator. In octet 1, Y is indicated; in octet 2, Z is indicated,

and in the two last octets, spaces are indicated.

1.1.3. There are two separators, x’AB’ x’CD’. In octet 1, A is indicated, in octet 2, B is

indicated, in octet 3, C is indicated, and in octet 4, D is indicated.

1.2. Translation. It admits the values: E (translate from ASCII to EBCDIC), A (translate from

EBCDIC to ASCII) and N (do not translate).

1.3. Conversion table. Name of the table of conversion table file. If we don’t want to

convert it, spaces will be indicated.

2. Input. It is the name of the application file, as it was left by EDITRAN/G when passing that

after reception.

3. Output. It is the name of the output application file, once the changes have been made. Its

format will depend on its definition.

4. ZTBGFTCO. It is the name of the conversion table file.

5. PASO002. Optional. It would delete the source application file if its adaptation is not

correct.

//KI0F6AEA JOB (EGDC,KIT,,99),'EDITRAN-V40',MSGCLASS=H,CLASS=A,

// NOTIFY=&SYSUID

//*********************************************************************

//* ADAPTACION DE FICHEROS EDITRAN. TRADUCCION Y CONVERSION INCLUIDOS.

//* NOTA PARA FICHEROS FIJOS DE SALIDA: SI LRECL ES MAYOR QUE REGISTRO

//* A GRABAR, SE RELLENA A SPACES POR LA DERECHA.

//* NOTA PARA FIJOS DE ENTRADA Y VBLES DE SALIDA. PROBABLEMENTE, EL

//* VBLE DEBE SER DEFINIDO 4 OCTETOS MAYOR QUE LRECL DE FIJO.

//*********************************************************************

//* VALORES DE PARM:(XXXX,Y,ZZZZZZZZ) SEPARADOS POR COMAS:

//* XX = CARACTERES HEXADECIMALES A ELIMINAR (SALTO DE CARRO):

//* - CUATRO OCTETOS A SPACES: NO HAY CARACTERES A ELIMINAR

//* - DOS OCTETOS INDICANDO UN CARACTER HEXADECIMAL Y OTROS DOS

//* A SPACES. ELIMINA EL CARACTER DETERMINADO EN HEXA

//* - CUATRO OCTETOS INDICANDO DOS CARACTERES HEXADECIMALES.

//* POR EJEMPLO 0D0A): ELIMINA LOS DOS HEXADECIMALES X0D-X0A

//* Y = 1 OCTETO INDICANDO SI SE VA A TRADUCIR LENGUAJE DE FICHERO

EDITRAN/G 5.2 11


//* ORIGEN. VALORES POSIBLES:

//* A(ASCII), E(EBCDIC), N(NO TRADUCIR)

//* ZZ = 9 OCTETOS INDICANDO NOMBRE DE LA TABLA DE CONVERSION (QUE

//* SE APLICA TRAS TRADUCIR).CON SPACES NO HAY TABLA CONVERSION

//* SI OCTETO 9 ES ‘A’ SE CONVIERTE A ASCII.

//* SI OCTETO 9 ES ‘E’ SE CONVIERTE A EBCDIC.

//*********************************************************************

//PASO001 EXEC PGM=ZTBGBGFF4,PARM='0D0A,E,TABCVXNCE'

//STEPLIB DD DSN=KI.EIDC.ZTBG.LOAD,DISP=SHR

//ZTBGFTCO DD DSN=KI.PMED.CZTB.ZTBGFTCO,DISP=SHR

//ENTRADA DD DSN=PUNTERO.FICHERO.ORIGEN,DISP=SHR

//SALIDA DD DSN=PUNTERO.FICHERO.FIJO244.DESTINO,

// DCB=(RECFM=FB,LRECL=256,BLKSIZE=0,DSORG=PS),

//* DCB=(RECFM=VB,LRECL=260,BLKSIZE=0,DSORG=PS)

//* DCB=(RECFM=VS,LRECL=260,BLKSIZE=0,DSORG=PS)

// DISP=(NEW,CATLG,DELETE),

// SPACE=(TRK,(500,50),RLSE)

//SYSOUT DD SYSOUT=*

//SYSPRINT DD SYSOUT=*

//SYSDBOUT DD SYSOUT=*

//ABENDAID DD SYSOUT=*

//SYSUDUMP DD SYSOUT=*

//SYSABOUT DD SYSOUT=*

//*

//PASO002 EXEC PGM=IDCAMS,COND=(0,NE,PASO001)


//SYSIN DD *

DELETE (PUNTERO.FICHERO.ORIGEN) PURGE

//*

//

4.5. EDITRAN/G GENERIC REQUESTS

It incorporates the possibility that through a single JCL, generic requests can be launched

against multiple sessions, so that this JCL can be chained to the installation planners and

perform the usual operations of the EDITRAN/G operators. The requests can be made from a

previously created request file or through SYSIN in the JCL.

The JCL provided is ZTBGJPET, which calls the program ZTBGBPET, which acts by reading

TABLES, where it finds the necessary parameters. These are:

Level Name Length Type Description

1 Parameters 80

2 Filler 1 Alph. Spaces. If its value is * is ignored.

2 Function 2 Num. Function:

01- Upload

02- Process presentation after transmission.

03- Send presentation

05- Interrupt transmission presentation.

06- Initialize reception presentation.

07- Download reception presentation.

08- Receive presentation.

09- Interrupt reception presentation.

10- Status initialization.

2 Filler 1 Alph. Dash

2 Resource 1 Alph. Resource from which the program gets the sessions

F – File

J – JCL.


2 Direction 1 Alph. (Only necessary with function 10):

E – Transmission.

R – Reception.

2 Filler 73 Alph. Space reservation area

EDITRAN/G 5.2 12


The sessions can be specified after this card (if Resource J was indicated), or in the

REQUEST file (fixed of 80 positions) if Resource F was indicated. The following will be

specified:


1 Session 80

2 Filler 1 Alph. Spaces. If its value is * is ignored.

2 Presentation source 9 Alph. Presentation source (zeros, so that the request can

be made against all possible source codes).


2 Presentation

destination

9 Alph. Presentation destination (zeros, so that the request

can be made against all the remote codes).


2 Application 6 Alph. Application (zeros for any application).


2 Use list of files 1 Alph. S/N (YES/NO. Optional in the upload (ZTBGB110).

It indicates whether we want to use list of files

(ZTBGFCAR), to upload the application files.

If S (YES) is entered, the file list will be loaded

instead of what is entered in the profiles. If there is

nothing in the profiles, it crashes.

If N or nothing, it is loaded what has been entered

in the profile. If it has nothing, the file list is loaded.

2 Filler 51 Alph. Space reservation area

The JCL would remain as follows: //KI0EEC03 JOB (EGDC,KIT,,99),'PET-MASIVAS',MSGCLASS=H,CLASS=A,

// NOTIFY=&SYSUID

//*********************************************************************

//* INDRA, S.A.- SOL. COMUNICACIONES JUN. 2001 *

//*********************************************************************

//*********************************************************************

//* PETICIONES GENERICAS.

//**********************************************************************

//*FORMATO DE PRIMERA FICHA DEL JCL (SEPARADOS POR GUIONES).

//*

//*FF-R-S : FF -> FUNCION : 01 CARGA

//* 02 PROCESAR PRESENTACION POSTERIOR EMISION

//* 03 EMITIR PRESENTACION

//* 05 INTERRUMPIR PRESENTACION DE EMISION

//* 06 INICIALIZAR PRESENTACION RECEPCION

//* 07 DESCARGAR PRESENTACION DE RECEPCION

//* 08 RECIBIR PRESENTACION

//* 09 INTERRUMPIR PRESENTACION DE RECEPCION

//* 10 INICIALIZACION DE ESTADOS

//*

//* : R -> RECURSO : ( DE DONDE TOMA EL PROGRAMA LAS SESIONES)

//* F FICHERO

//* J JCL

//*

//* : S -> SENTIDO : (SOLO CUANDO LA FUNCION SEA = 10)

//* E EMISION

//* R RECEPCION

//*FORMATO DE LAS SIGUIENTES FICHAS DEL JCL (SEPARADOS POR GUIONES)

//* : ORIGEN (9 OCTETOS)

//* : DESTINO(9 OCTETOS)

//* : APLICACION (6 OCTETOS)

//* LISTA FICHEROS (S/N) (OPTATIVO) (1 OCTETO)

//* -INDICA SI SE DESEA UTILIZAR PARA LA CARGA UNA LISTA QUE

//* CONTIENE LOS FICHEROS DE APLICACION (ZTBGFCAR).

//* -SI NO LE LLEGA EL PARM AL PROG ZTBGB110,O LE LLEGA A N,

//* EL PROGRAMA DE CARGA, SACA LOS FICH.APLICACION DE PERFILES.

//* SI NO EXISTEN FICH. EN PERFILES,BUSCA LOS MISMOS EN UNA

//* LISTA DE FICHEROS YA CREADA (ZTBGFCAR)

EDITRAN/G 5.2 13


//* -SI LF=S, EL PROGRAMA DE CARGA, SACA LOS FICH.APLICACION DE

//* UNA LISTA DE FICHEROS YA CREADA (ZTBGFCAR). SI NO EXISTE

//* DICHA LISTA, CASCA.

//**********************************************************************

//ZTBGPET EXEC PGM=ZTBGBPET,REGION=8M


// DD DSN=KI.GCDA.CIFRADO.LOAD,DISP=SHR

//*

//ZTBGFPER DD DSN=KI.EIDC.ZTBG.ZTBGFPER,DISP=SHR

//ZTBPFPE DD DSN=KI.EGDC.ZTBP.ZTBPFPE,DISP=SHR

//NXFDCLA DD DSN=KI.SGDC.SSASST.NXFDCLA,DISP=SHR

//ZTBGFLOG DD DSN=KI.EIDC.ZTBG.ZTBGFLOG,DISP=SHR

//ZTBGFEST DD DSN=KI.EIDC.ZTBG.ZTBGFEST,DISP=SHR

//ZTBEFMP DD DSN=KI.EGDC.ZTBE.ZTBEFMP,DISP=SHR

//ZTBEFMH DD DSN=KI.EGDC.ZTBE.ZTBEFMH,DISP=SHR

//ZTBEFMT DD DSN=KI.EGDC.ZTBE.ZTBEFMT,DISP=SHR







//PETICION DD DSN=KI.EIDC.ZTBG.PETICION,DISP=SHR

//LISTADO DD SYSOUT=H,DCB=(BLKSIZE=132)

//FICHAS DD *

10-J-R

*

000000000-A0009997A-PRUEBA-N

000000000-000000000-GENERI-S

000000000-A0009997A-APLICA

*

//*

EDITRAN/G 5.2 14

5.SERVICE JCL

5. SERVICE JCL

During the installation, a set of service JCLs are provided. They are the following:

CICS Version

ZTBGJIPE DELETE/DEFINE and initialization of the EDITRAN/G profile file. Usually, it

is only executed in installation.

ZTBGJILO DELETE/DEFINE and initialization of the EDITRAN/G log file. Since it is a

cyclic file, it would not be necessary to initialize it other than in the installation. We

must specify the number of logs we want to keep when initializing the control log.

ZTBGJIES DELETE/DEFINE and initialization of the EDITRAN/G status file. Usually, it

is only executed during the installation.

IMS Version

ZTBGJCPE DELETE/DEFINE and initialization of the database of the EDITRAN/G

profiles.

ZTBGJCLO DELETE/DEFINE and initialization of the database of the EDITRAN/G log.

We must specify the number of logs we want to keep when initializing the control log.

ZTBGJCES DELETE/DEFINE and initialization of the database of EDITRAN/G statuses.

Common

ZTBGJLLO It lists the EDITRAN/G log file, taking it to the LISLOG instal.prefix file in

the LISTEDI step, and to printer in the LIST step. In the invocation of the "in-stream"

procedure at the end of the JCL, parameters are provided for the selection of the date

and time listing mode or for local date and time of the application node, with zeros if

we want to search generically by any of these fields. The file obtained could

eventually be sent to INDRA via EDITRAN to specify the problems. If we do not want to

get the file, we can delete the LISTEDI step. An example of the output of this

execution would be:

LOCAL PRESENTACION : LISTADO DEL FICHERO DE LOG DE EDITRAN/G VERSION 4.1 PAGINA : 1

CODIGO PRESENTACION : ===================================================== FECHA : 26/05/1998

APLICACION PRESENTACION :

FECHA ( SELECCIONADA ) : 10/05/1998

ORG TIP SESION PRESENTACION APL.TRAN FECHA HORA MENSAJE

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

APL E 000099990-000099970-FUENTE 11/05/1998 09:04:29 0019 PETICION DE CARGA DE PRESENTACION DE EMISION

IGA I 000099990-000099970-FUENTE 11/05/1998 09:04:34 0142 COMPRESION DE FICHERO CORRECTA Y FINALIZADA

IGA I 000099990-000099970-FUENTE 11/05/1998 09:04:35 0046 FIN DE CARGA DEL FICHERO DE APLICACION NUMORD01

IGA I 000099990-000099970-FUENTE 11/05/1998 09:04:35 0013 FINALIZADA CARGA EMISION DEL CONVERSOR ZTBGBG10. R-C: 00000

IGA I 000099990-000099970-FUENTE 11/05/1998 09:04:35 0087 CARGA DEL FICHERO CSB NORMALIZADO FINALIZADA CORRECTAMENTE

IGA I 000099990-000099970-FUENTE FUENTE 11/05/1998 09:04:39 0083 FIN CARGA DE SESION TRASMISION: TAMPON E000000

IGA I 000099990-000099970-FUENTE 11/05/1998 09:04:39 0014 CARGA DE PRESENTACION CORRECTA Y FINALIZADA

IGA S 000099990-000099970-FUENTE FUENTE 11/05/1998 09:04:41 0113 NOTIFICACION A EDITRAN DE TAMPON EMISOR PREPARADO (A8R)

EDI E 000099990-000099970-FUENTE FUENTE 11/05/1998 09:06:39 0018 PETICION PARA PROCESAR PRESENTACION POSTERIOR A EMISION

EDI I 000099990-000099970-FUENTE FUENTE 11/05/1998 09:06:42 0069 DESCARGA DE EMISION DE PRESENTACION CORRECTA Y FINALIZADA

IGA S 000099990-000099970-FUENTE FUENTE 11/05/1998 09:06:43 0061 SE COMUNICA A EDITRAN FINAL POSTERIOR A EMISION (A3R)

OPE E 000099990-000099970-FUENTE 11/05/1998 09:12:34 0023 PETICION DE INICIALIZACION DE RECEPCION

OPE I 000099990-000099970-FUENTE 11/05/1998 09:12:42 0067 INICIALIZACION DE RECEPCION CORRECTA Y FINALIZADA

IGA I 000099990-000099970-FUENTE FUENTE 11/05/1998 09:12:44 0114 NOTIFICACION A EDITRAN DE TAMPON RECEPTOR PREPARADO (AAR)

EDI E 000099990-000099970-FUENTE FUENTE 11/05/1998 09:14:11 0024 PETICION DE DESCARGA DE RECEPCION DE PRESENTACION

IGA I 000099990-000099970-FUENTE FUENTE 11/05/1998 09:14:19 0090 DESCARGA DEL FICH. CSB NORMALIZADO FINALIZADA CORRECTAMENTE

5.1. FILE OF SENT AND RECEIVED FILES

In the procedure after transmission, ZTBGP3, of after reception, ZTBGP4, the operator has

entered a second step that, invoking a new program (ZTBGBLFE), would generate a file whose

contents are the files sent or received.

//ZTBGLFE EXEC PGM=ZTBGBLFE,

// PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&AP',

// REGION=4M


EDITRAN/G 5.2 15

5.SERVICE JCL



//ZTBGFLFE DD SYSOUT=*

//ZTBGFPRI DD SYSOUT=*,DCB=(BLKSIZE=105)







//*

A procedure-independent JCL has also been created, ZTBGJFLE:

//KI0F6AE3 JOB (EGDC,KIT,,99),'IGA-EDITRAN',MSGCLASS=H,CLASS=A,

// NOTIFY=&SYSUID

//*********************************************************************

//* JCL PARA SACAR LISTA DE FICHEROS EMITIDOS - RECIBIDOS *

//*********************************************************************

//* DATOS: *

//* ORIGEN --------------------------------------------> 1 BYTE *

//* A - PETICION CON SESION DE TRANSMISION INCLUIDA *

//* E-O- PETICION CON SESION DE PRESENTACION INCLUIDA *

//* FUNCION -------------------------------------------> 2 BYTES *

//* 00 - SACA LA LISTA INDEPENDIENTEMENTE DE ESTADO PRESENTACION*

//* 02 - SACA LA LISTA SI EL EST.EMI DE PRESENTACION ES FINALIZ. *

//* 07 - SACA LA LISTA SI EL EST.REC DE PRESENTACION ES FINALIZ. *

//* SES. PRESENT. O SES. TRANSM.(DEPENDIENDO DE ORIGEN)> 24 BYTES *

//* LOCAL0 -------------------------------------------> 3 BYTES *

//* LOCAL1 -------------------------------------------> 6 BYTES *

//* LOCAL2 -------------------------------------------> 3 BYTES *

//* REMOTO1-------------------------------------------> 6 BYTES *

//* REMOTO2-------------------------------------------> 3 BYTES *

//* APLICA -------------------------------------------> 6 BYTES *

//*********************************************************************

//PASO01 EXEC PGM=ZTBGBLFE,

// PARM='A02000099940000099990MARIAJ',

// REGION=4M


//*



//ZTBGFLFE DD SYSOUT=*

//ZTBGFPRI DD SYSOUT=*,DCB=(BLKSIZE=105)







//*

The contents of the fields is: Source = ‘x’, Function = ‘yy’, L1 + L2 = ‘Local code’, R1 + R2 =

‘Remote code’, AP = ‘Application’.

Source can have the following values:

‘A’ : The request comes from the application. In this case, the session (L1-L2-R1-R2-AP) is

the Presentation session.

‘O’ : The request comes from operator. In this case, the session (L1-L2-R1-R2-AP) is the

Presentation session.

EDITRAN/G 5.2 16

5.SERVICE JCL

‘E’ : The request comes from EDITRAN/P. In this case, the session (L1-L2-R1-R2-AP) is one

of the transmission sessions associated with the presentation.

Function can have the following values:

‘00’: If we want to take a file regardless of the presentation status.

‘02’: Processing after transmission. It will only create the file if the presentation status is

005 (Finished)

‘05’: Interrupt transmission presentation. No file is created.

‘07’: Processing after reception. It will only create the file if the presentation status is 104

(Finished)

‘09’: Interrupt reception presentation. No file is created.

Examples:

1.- Take all the files associated with the presentation 00009994000009990TELECA,

PARM='A00000099940000099990TELECA'

PARM='O00000099940000099990TELECA'

2.- Take all the files associated with the transmission 00009994000009990PRUEBA

PARM='E00000099940000099990PRUEBA'

3.- Take all the files associated with the presentation 00009994000009990TELECA,

provided that the presentation status is FINISHED:

PARM='A02000099940000099990TELECA'

PARM='O02000099940000099990TELECA'

4.- Take all the files associated with the transmission 00009994000009990PRUEBA,

provided that the presentation status to which that transmission session belongs is FINISHED

PARM='E02000099940000099990PRUEBA'

The contents of the ZTBGFLFE file is as follows:


1 File Area 130 Alph.

2 Physical Name 44 Alph. Physical name of the application file


2 Presentation-end-

date

14 Num. Date-time of presentation end, format

AAAAMMDDHHMMSS

2 Loaded file-type 4 Num. Type of loaded or output file

‘FIJO’ (FIXED)

‘VBLE’ (VARIABLE LENGTH)

‘VEXP’

‘BINA’

2 Loaded data-

language

1 Alph. Language of loaded data:

‘A’: Ascii, ‘E’: Ebcdic, ‘B’: Binary

2 Compression 1 Alph. It indicates if the file was loaded with

compression:

‘F’ Compressed, ‘N’ Not compressed

2 Filler 1 Alph. Reservation area

2 Source physical

name

44 Alph. Physical name of the source application file

2 Applic.file bytes 12 Num Application file bytes

2 Log length 6 Num Log L.

EDITRAN/G 5.2 17

5.SERVICE JCL


5.2. LIST OF PRESENTATION STATUSES

From JCL ZTBGJCEP the statuses of all the presentation sessions are displayed.

EDITRAN/G 5.2 18

6.ANNEX A. EDITRAN/G MESSAGES

6. ANNEX A. EDITRAN/G MESSAGES

Messages recorded in the LOG during the execution of the EDITRAN/G procedures.

They are specified in ascending order of the message code with an explanation in some of

them, if their meaning is not evident.

The messages contain variable lengths whose meaning is as follows:

xxxxxxxx: Program generating the message

yyyyyyyy: Resource related to the message

zz: File-status obtained in accesses to files

zzzz: Resulting return code that generates the notification

The File-status (F-S) returned in accesses to VSAM files can be queried in the COBOL

manuals of the constructor.

ZTG0013: TRANSMISSION UPLOAD CONVERTER COMPLETED YYYYYYY R-C: ZZZZ.

ZTG0014: SUCCESSFUL AND COMPLETED PRESENTATION UPLOAD.

ZTG0015: TRANSMISSION REQUEST REQUESTED TO EDITRAN/P (A1R)

ZTG0016: RECEPTION REQUEST REQUESTED TO EDITRAN/P (A2R)

ZTG0017: XXXXXXXX: ERROR IN CONVERTER PROCESS YYYYYYYY. R-C: ZZZZ

Another more specific error message must exist.

ZTG0018: REQUEST FOR PROCESSING PRESENTATION AFTER TRANSMISSION

ZTG0019: REQUEST FOR TRANSMISSION PRESENTATION UPLOAD

ZTG0020: REQUEST FOR PRESENTATION TRANSMISSION

ZTG0021: REQUEST FOR PRESENTATION CUMULATIVE TRANSMISSION.

The transmission for a session with cumulative upload type has been requested.

ZTG0022: REQUEST FOR PRESENTATION TRANSMISSION END

ZTG0023: REQUEST FOR RECEPTION INITIALIZATION

ZTG0024: REQUEST FOR PRESENTATION RECEPTION DOWNLOADING

ZTG0025: REQUEST FOR PRESENTATION RECEPTION

ZTG0026: REQUEST FOR PRESENTATION RECEPTION END

ZTG0027: XXXXXXX: INCONSISTENCY IN PRESENTATION STATUSES

An attempt is made to find out the status of the presentation session by querying the

transmission sessions it consists of, and they are not consistent with each other. There

may have been a manipulation of the transmission session statuses, outside EDITRAN/G.

EDITRAN/G 5.2 19


ZTG0028: RECEPTION DOWNLOAD END OF YYYYYYYY CONVERTER. R-C: ZZZZ

ZTG0029: XXXXXXXX: READING ERROR REC-0, BUFFER YYYYYYYY. F-S: ZZ

This type of error should not occur. It occurs when we try to process a certain log that must

exist and an error occurs. This case refers to the control log of a buffer.

ZTG0030: XXXXXXXX: READING ERROR REC-1, BUFFER YYYYYYYY. F-S: ZZ

It is of the same type as ZTGOO29, but referred to the second buffer log, that can have a

special meaning, as the case may be.

ZTG0031: XXXXXXXX: APP RECORD LENGTH INCOMPATIBLE WITH TRANSMISSION. In

compatibility mode, the length of the application log should not exceed that of the

transmission data.

ZTG0032: XXXXXXXX: ERROR ACCESSING THE DB. YYYYYYYY. R-C: ZZ

Not applicable to the CICS version.

ZTG0033: XXXXXXXX: ERROR ACCESSING THE FILE YYYYYYYY. R-C: ZZ


ZTG0034: PRESENTATION STATUS NOT COMPATIBLE WITH THE REQUEST.

EDITRAN/G checks if the presentation status is compatible with the request made by the

operator, interactive or batch, before launching the corresponding procedure. This

circumstance is also verified in the execution of the procedures, taking out this message in

case of error, since these have been able to be launched directly by JCL, by EDITRAN/P or

even by the operator of EDITRAN/G in a repetitive way before the status is modified by the

previous execution.

ZTG0035: XXXXXXXX: ERROR MAKING CHKP R-C: ZZ


ZTG0036: XXXXXXXX: ERROR WRITING REC-0 BUFFER YYYYYYYY. F-S: ZZ

This message and the following three are type ZTG0029 and 30.

ZTG0037: XXXXXXXX: ERROR WRITING REC-1 BUFFER YYYYYYYY. F-S: ZZ

ZTG0038: XXXXXXXX: ERROR REWRITING REC-0 BUFFER YYYYYYYY. F-S: ZZ

ZTG0039: XXXXXXXX: ERROR REWRITING REC-1 BUFFER YYYYYYYY. F-S: ZZ

ZTG0040: XXXXXXXX: CATALOG. ERROR (WITHOUT SPACE, OR A FILE ALREADY EXISTS).

Error in allocation of reception application files. An extended message must exist in

ZTGPRINT.

ZTG0041: XXXXXXXX: ERROR IN PROCESS. THERE IS NO CONVERTER IN PROFILE. The

converter programs before transmission and after reception are mandatory for both the

uploading and downloading.

ZTG0042: XXXXXXXX: ERROR INSERTING/RETRIEVING MESSAGE R-C: ZZ

EDITRAN/G 5.2 20



ZTG0043: XXXXXXXX: ERROR IN PROCESS. THERE IS NO PROCEDURE IN PROFILE.

This message only appears in the execution of the batch operator.

ZTG0044: XXXXXXXX: ERROR IN PROCESS. THERE IS NO SESSION-EDI IN PROFILES

The same as the previous one.

ZTG0045: XXXXXXXX: ERROR IN PROCESS. THERE IS NO SESSION-IGA IN PROFILES. It

can occur in the execution of the batch operator and in the execution of procedures

triggered directly (a wrong PARM has been set) or by EDITRAN/P (the transmission session

is not included in any presentation).

ZTG0046: END OF UPLOAD OF THE APPLICATION FILE YYYYYYYY

ZTG0047: REQUEST FOR PROCESSING PRESENTATION AFTER TRANSMISSION

ZTG0048: REQUEST FOR TRANSMISSION PRESENTATION UPLOAD

ZTG0049: REQUEST FOR PRESENTATION TRANSMISSION

ZTG0050: REQUEST FOR PRESENTATION DYNAMIC TRANSMISSION

ZTG0051: REQUEST FOR PRESENTATION TRANSMISSION END

ZTG0052: REQUEST FOR RECEPTION INITIALIZATION

ZTG0053: REQUEST FOR PRESENTATION RECEPTION DOWNLOADING

ZTG0054: REQUEST FOR PRESENTATION RECEPTION

ZTG0055: REQUEST FOR PRESENTATION RECEPTION END

ZTG0056: APPLICATION FILE NOT CATALOGUED YYYYYYYY

It does not find the file specified in the profiles. The upload continues with other

application files, if any.

ZTG0057: TRANSMISSION APPLICATION FILE IS EMPTY YYYYYYYY

ZTG0058: INVALID TRANSMISSION LENGTH DETECTED FOR EDITRAN/G 2.0 : ZZZZ

In compatible mode the transmission length must be 252 or 4050. Not used

ZTG0059: REQUEST FOR TRANSMISSION END TO EDITRAN.

ZTG0060: REQUEST FOR RECEPTION END TO EDITRAN.

ZTG0061: EDITRAN IS INFORMED ABOUT END AFTER TRANSMISSION (A3R)

ZTG0062: EDITRAN IS INFORMED ABOUT RECEPTION DOWNLOAD END (A4R)

EDITRAN/G 5.2 21


ZTG0063: EDITRAN IS INFORMED ABOUT ERROR LOADING TRANSMISSION (A1R)

ZTG0064: EDITRAN IS INFORMED ABOUT ERROR WHEN START RECEPTION (A2R)

ZTG0065: EDITRAN IS INFORMED ABOUT ERROR AFTER TRANSMISSION (A3R)

ZTG0066: EDITRAN IS INFORMED ABOUT ERROR IN RECEPTION DOWNLOAD (A4R)

ZTG0067: CORRECT AND COMPLETED RECEPTION INITIALIZATION

ZTG0068: XXXXXXXX: DEFINITION OF BUFFER INCOMPATIBLE WITH TRANSM. LENGTH.

A matrix buffer is used with a recording length lower than the transmission length + 36.

ZTG0069: CORRECT AND COMPLETED PRESENTATION TRANSMISSION DOWNLOAD

ZTG0070: CORRECT AND COMPLETED PRESENTATION RECEPTION DOWNLOAD

ZTG0071: XXXXXXXX: RECEPTION APPLICATION FILE YYYYYYYY ALREADY EXISTS.

When downloading reception, it has been found that one of the application files already

exists and it has been specified in the profile "Delete if they exist" = N.

ZTG0072: XXXXXXXX: THERE IS NO SESSION IN STATUS RECORD

Possible inconsistency in the transmission sessions defined in local and remote

presentation sessions.

ZTG0073: APPLICATION FILE NOT RECEIVED YYYYYYYY

In compatibility mode 2.0, there is no file in the index record of the reception buffer with

the identifier defined in the reception files of the presentation session profile. Not used

ZTG0074: EMPTY APPLICATION FILE RECEIVED YYYYYYYY

ZTG0075: APPLICATION FILE RECEIVED YYYYYYYY

ZTG0076: RECEPTION APPLICATION FILE DELETED YYYYYYYY

ZTG0077: FILE DOWNLOAD NOT COMPLETED YYYYYYYY

In compatibility mode 2.0, possible difference in the number of transmission files of the

remote node, and reception of the local node. Not used

ZTG0078: DECOMPACTION ERROR. RECORD NUMBER. YYYYYYYY R-C: ZZ

ZTG0079: INCOMPATIBLE REQUEST FOR REMOTE EDITRAN/G < 2.1

ZTG0080: XXXXXXXX: NO APPLICATION FILE EXISTS IN PROFILES

It can happen in transmission upload and in reception download in compatibility mode.

ZTG0081: XXXXXXXX: RECOVERY ERROR. INVALID FILE YYYYYYYY


EDITRAN/G 5.2 22


ZTG0082: USER APPLICATION PROGRAM IS INVOKED YYYYYYYY

ZTG0083: TRANS. SESSION UPLOAD FINISHED: BUFFER YYYYYYYY

ZTG0084: APPLICATION FILE NOT DOWNLOADED: YYYYYYYY


ZTG0085: DOWNLOAD IN FILE RECOVERY: YYYYYYYY


ZTG0086: XXXXXXXX: FEATURES OF APPLICATION FILE NOT KNOWN

EDITRAN/G can only upload application files types F, FB, V, VB.

ZTG0087: UPLOAD OF THE STANDARDIZED CSB FILE CORRECTLY COMPLETED

ZTG0088: TRANSMISSION SESSION INITIALIZED:BUFFER YYYYYYYY

ZTG0089: TRANSMISSION SESSION DOWNLOAD: BUFFER YYYYYYYY

ZTG0090: DOWNLOAD OF THE STANDARDIZED CSB FILE CORRECTLY COMPLETED

ZTG0091: RECEP. BUFFER WITHOUT EDITRAN/G HEADER: YYYYYYYY (EMPTY)

This may occur if the remote node uploads an empty file in compatible mode and the local

node tries to download it in native mode. Check the remote EDITRAN/G version of

uploading and downloading.

ZTG0092: XXXXXXXX: EDITRAN/G HEADER WITH INCORRECT TRANSMISSION SESSION

It usually occurs if the remote EDITRAN/G is from an ASCII platform and EBCDIC has not

been specified as a remote alphabet. Also, if the presentation transmission sessions do not

coincide locally and remotely.

ZTG0093: XXXXXXXX: EDITRAN/G HEADER NOT FOUND IN TRANSMISSION SESSIONS

Usually this is because the remote node has uploaded in compatible mode and the local

node tries to download in native mode (check the remote EDITRAN/G version of uploading

and downloading). It is also because a remote ASCII indicates in its presentation session

profiles that it is going to transmit against an ASCII (the remote node has indicated ASCII-

EBCDIC=A). This error has also occurred if after initializing the reception with a

transmission length, it increases before the reception. In addition, if the reception has

started and without receiving anything, it is interrupted and downloaded. Another situation

is that the remote (Windows-Unix environment) has loaded a file as binary, with

EDITRAN/G compression, and it has version 3.1 installed. In this case, the version must be

updated or sent without lzw compression. (EDITRAN/G).

ZTG0094: STANDARDIZED UNCOMPLETED CSB FILE OF RECEPTION DETECTED.

It can only be due to an incident in EDITRAN/G. x files are received in the header and when

downloading, it is detected that less files are to be downloaded.

ZTG0095: XXXXXXXX: NO COMPLETE DATA BATCH HAS BEEN RECEIVED.

EDITRAN/G 5.2 23


ZTG0096: XXXXXXXX: INCOMPLETE PROFILE PARAMETERS FOR RECEPTION.

No data has been specified in the 5th screen of the presentation session, reception files,

and there is a try to download.

ZTG0097: XXXXXXXX: INCONSISTENT SESSIONS BETWEEN PROFILE & STATUSES.

The transmission sessions have been modified in the presentation profile and the statuses

have not been initialized.

ZTG0098: XXXXXXXX: APPLICATION REC. DETECTED WITH INCORRECT LENGTH.

It can only happen due to an incident in the reception download product.

ZTG0099: XXXXXXXX: DETECTED BUFFER WITH WRONG EDITRAN/G HEADER.

This error should not occur under normal circumstances. After loading the buffer(s) one of

them is detected with an incorrect header.

ZTG0100: WRONG PARAMETER IN EDITRAN/G PROFILE: YYYYYYYY

The remote EDITRAN/G version specified in the profile of the presentation session is not

consistent with the converters used.

ZTG0101: REQUEST NOT IMPLEMENTED FOR REMOTE EDITRAN/G VERSION 2.1

It refers to the dynamic transmission.

ZTG0102: XXXXXXXX: EDITRAN SESSIONS MUST HAVE THE SAME MATRIX BUFFER.

ZTG0103: XXXXXXXX: THERE ARE NOT JCL CARDS IN PROFILES TO SUBMIT.

ZTG0104: XXXXXXXX: RECOVERY. SESSION PREVIOUSLY PROCESSED.


ZTG0105: XXXXXXXX: RECOVERY. SESSION CORRECTLY PROCESSED.


ZTG0106: XXXXXXXX: KEY LENGTH OF EDITRAN PROFILES UNKNOWN.

This may be due to the specification in the procedure of an EDITRAN profile file from a

previous version.

ZTG0107: XXXXXXXX: WRONG LOCAL EDITRAN VERSION.

ZTG0108: INTERRUPTION NOTIFICATION, CODE: YYYY

In an exception procedure launched by EDITRAN/P the reason for that exception is

communicated. For more information, see the manual EP51USUC.

ZTG0109: THE USER APPLICATION PROGRAM YYYYYYYY IS CALLED.

ZTG0110: USER PROCESS CORRECTLY COMPLETED.

ZTG0111: XXXXXXXX: ERROR IN USER PROCESS YYYYYYYY. R-C: ZZZZ

EDITRAN/G 5.2 24


ZTG0112: XXXXXXXX: TYPE OF BUFFER FILE UNKNOWN FOR EDITRAN/G

EDITRAN/G cannot process public buffers.

ZTG0113: NOTIFICATION TO EDITRAN OF PREPARED TRANSM. BUFFER (A8R)

ZTG0114: NOTIFICATION TO EDITRAN OF PREPARED RECEPTION BUFFER (AAR)

ZTG0115: COMMUNICATION TO EDITRAN TRANSMISSION SESSION NOT UPLOADED.

This occurs when the presentation session consists of several transmission sessions, but

one of the associated buffers is not loaded because the amount of information to be

loaded does not exceed the minimum amount established per session.

ZTG0116: XXXXXXXX: ERROR IN PROCESS. WRONG FIELD YYYYYYYY.

Internal error.

ZTG0117: Static external allocation of application file detected.

ZTG0118: XXXXXXXX: INCORRECT DCB (CSB-N: RECFM=YYYYYYYY LRECL=ZZZZZ)

ZTG0119: REQUEST FOR STATUS MODIFICATION. PARM=YYYYYYYY.

ZTG0120: XXXXXXXX: THE STATUS TRANSMISSION SESSION IS NOT IN PROFILES.

ZTG0121: XXXXXXXX: BYTES IN ZIPPED FILE DIFFERENT FROM THE SENDER.

It is detected that the number of bytes obtained by the LZW expander of the local node do

not coincide with the theoretical ones stated by the remote node.

ZTG0122: XXXXXXXX: INPUT FILE HAS NO COMPRESSED FORMAT.

The local expander detects that the file received is not compressed.

ZTG0123: XXXXXXXX: ERROR RETURNED BY THE MODULE YYYYYYYY ERR=ZZZZZ

Error returned by the compressor or the expander. ERR refers to the codes specified in "C

370 Programming Guide" of the constructor.

ZTG0124: XXXXXXXX: APPLICATION FILE BYTES OTHER THAN THE SENDER. It is usually

due to a bad loading. Another situation is that the remote node (Windows-Unix

environment) has loaded a file as binary, with EDITRAN/G compression, and it has version

3.1 installed. In this case, update the version or send without LZW compression

(EDITRAN/G).

ZTG0125: DOWNLOAD IN FINISHED STATUS HAS BEEN DETECTED.

ZTG0126: REQUEST FOR PRESENTATION STATUS CANCELLATION.

ZTG0127: CORRECT AND COMPLETED STATUS MODIFICATION.

ZTG0128: CORRECT AND COMPLETED STATUS CANCELLATION.

ZTG0129: XXXXXXXX: THERE IS NO BUFFER FILE IN EDITRAN/P SESSION PROFILE.

EDITRAN/G 5.2 25


ZTG0130: THE SESSIONS MUST HAVE THE SAME TRANSMISSION LENGTH.

This message and the next two messages refer to the transmission sessions of which

there is a particular presentation.

ZTG0131: THE SESSIONS MUST HAVE SPECIFIC FILES OR THE SAME MATRIX.

ZTG0132: SESSIONS MUST HAVE THE SAME JCL CARDS, OR NOT TO HAVE THEM.

ZTG0133: INTERRUPTION IN FINISHED STATUS HAS BEEN DETECTED.

ZTG0134: WITH CRYPTOGRAPHY V2.2, IT MUST BE AUTHENTICATED IN EDITRAN.

If we want to use batch cryptography in EDITRAN/G, it must be also specified in the

EDITRAN/P profile.

ZTG0135: WITH CRYPTOGRAPHY BATCH, THE KEY CHANGE MUST BE "N"

If we use batch cryptography, the key cannot be changed before completing the

transmission.

ZTG0136: XXXXXXXX: ERROR IN DATA ENCRYPTION. RC=YYYYY REASON=ZZZZZ

Error returned by the specific cryptography interface the user has installed.

ZTG0137: XXXXXXXX: ERROR DECIPHERING DATA. RC=YYYYY REASON=ZZZZZ

The same as ZTG0136

ZTG0138: XXXXXXXX: ERROR WHEN GENERATING KEY. RC=YYYYY REASON=ZZZZZ

The same as ZTG0136

ZTG0139: XXXXXXXX: ERROR WHEN RECIPHERING KEY. RC=YYYYY REASON=ZZZZZ

The same as ZTG0136

ZTG0140: XXXXXXXX: KEY ENCRYPTION ERROR. RC=YYYYY REASON=ZZZZZ

The same as ZTG0136

ZTG0141: WITH BATCH COMPRESSION, NOT POSSIBLE EDITRAN/P COMPRESSION'

ZTG0142: CORRECT AND COMPLETED FILE COMPRESSION

ZTG0143: CORRECT AND COMPLETED FILE DECOMPRESSION

ZTG0144: BUFFER ENCRYPTION CORRECTLY COMPLETED

ZTG0145: Buffer decryption correctly completed

ZTG0146: XXXXXXXX: ERROR WRITING THE COMPRESSED FILE: ZZZZZ

It is usually a problem of space because the allocation of a file is too short. It is usually

solved by increasing the number of records in the presentation session.

ZTG0147: INTERRUPTION NO PERMITTED IN "FINISHED" WITH DELETE-BUFFER=S

EDITRAN/G 5.2 26


ZTG0148: XXXXXXXX: LAST CHARACTER PARAMETER IS NOT A SEPARATOR.

It refers to the macro file upload process.

ZTG0149: XXXXXXXX: PARAMETER LENGTH AND IDENTIFIER ARE NOT THE SAME.

It occurs in the macro file loading process if the length of the identifier field, under

Presentation Session Parameter, does not match the number of characters between

separators in that identifying field.

ZTG0150: XXXXXXXX: ERROR WHEN VERIFYING CHECK.

ZTG0151: ERROR CHECKING THE FILE HASH

Sender-receiver don’t match.

ZTG0152: XXXXXXXX: ERROR CHECKING SIGNATURE

Aauthentication.

ZTG0153: CSB FILE LOADED IN PREVIOUS PROCESS HAS BEEN DETECTED.

The standardized CSB file is an intermediate file that is used, both in upload and download,

and is deleted after a normal process. If a process fails and this file has been loaded

correctly, the query of the transmission or reception status would indicate it as "loaded". In

this situation, a new request for the process would be based on the above-mentioned

standard CSB file. This message informs that in the normal process of loading or

downloading, this intermediate file obtained in a previous execution has been found.

ZTG0154: XXXXXXXX: ERROR LOCKING MATRIX FILE. RC = ZZZZZ

Applicable to VSE version.

ZTG0155: XXXXXXXX: ERROR UNLOCKING MATRIX FILE. RC = ZZZZZ

Applicable to VSE version.

ZTG0156: CRYPTOGRAPHIC VERSION 3.0. RSA KEY LENGTH MUST BE 1024.

ZTG0157: EDITRAN/P SESSIONS WITH A DIFFERENT CRYPTOGRAPHIC VERSION.

This error occurs in two cases: when even if there are more than one transmission session,

they don’t have the same cryptography version, and when the cryptography version in

EDITRAN/P is 4.0 and the remote EDITRAN/G version is below 5.2.

ZTG0158: ERROR WHEN CALCULATING THE HASH OF THE APPLICATION FILE

ZTG0159: THE FILE TO SEND IS A DIRECTORY.

ZTG0160: NOT USED.

ZTG0161: XXXXXXXX: INVALID APPLICATION PARAMETERS

In the macro file loading process the Presentation Session Parameter contains a position or

length of identifier, or length or data position with non-numeric values, zeroes or greater

than 32752. It also occurs if the position and length of the data or identifier, when added

together, exceed the actual record length of the macro file.

EDITRAN/G 5.2 27


ZTG0162: XXXXXXXX: FILE ZTBGFSES EMPTY.

In the macro file process by means of the JCL ZTBGJMCR for several presentation sessions,

the ZTBGFSES file must contain a list of the sessions to be uploaded.

ZTG0163: XXXXXXXX: ERROR WHEN WRITING THE EXPANDED FILE:ZZZZZ

It is usually a problem of space by SMS management.

ZTG0164: THE RECEPTION EXIT YYYYYYYY IS INVOKED.

ZTG0165: USER EXIT CORRECTLY COMPLETED.

ZTG0166: XXXXXXXX: ERROR IN USER EXIT YYYYYYYY. R-C: ZZZZ

This message is displayed if the Reception Exit returns to EDITRAN/G a non-zero return

code. The process is stopped.

ZTG0167: EDITRAN SESSION WITH TRANS. BUFFER NOT PRESENT IN PREVIOUS.

This Error message is displayed when, in an EDITRAN/G presentation session with several

EDITRAN/P transmission sessions, it is detected that some of these sessions do not have a

transmission buffer and another one (the next one in profile order) does it.

ZTG0168: RECEPTION BUFFER FILE MANDATORY IN EDITRAN SESSIONS.

This Error message is displayed when a request for reception is made in an EDITRAN/G

presentation session that does not have a receiver buffer in one of its associated

transmission sessions.

ZTG0169: LACK OF KEYS INTERFACE OR AUTH. ALG. IN CRYPTO VERS. > 2.2

All the transmission sessions of EDITRAN/P associated with the presentation that is going

to encrypt/decrypt information according to an external Keys Management Interface must

have the same Keys Interface (online program, batch program and parameters).

ZTG0170: EDITRAN SESSION PROFILE NOT COMPATIBLE WITH KEYS INTERFACE

It is detected in profiles of EDITRAN/P which, having specified an external keys

management interface, does not have the parameters CRYPTHOGRAPHY='S' and CHANGE-

KEY='N'. The authentication of EDITRAN/P nodes is mandatory and there must be no

change of key when there is a batch encryption/decryption according to a Key Interface.

ZTG0171: CORRECT BUFFER ENCRYPTION. KEY-ID: XXXXXXXX.

The presentation data for the current transmission buffer has been successfully encrypted,

using the Local Exchange key/"exporter" with "Label" XXXXXXXX (8 last different octets

of "blank" spaces among 64 on the label identifying the key), as stated by the External

Keys Interface specified in the profiles.

ZTG0172: CORRECT BUFFER DECRYPTION. KEY-ID: XXXXXXXX.

The presentation data for the current reception buffer has been successfully decrypted,

using the Remote Exchange key/"importer" with "Label" XXXXXXXX (8 last different octets

of "blank" spaces among 64 from the label identifying the key), as stated by the External

Keys Interface specified in the profiles.

EDITRAN/G 5.2 28


ZTG0173: XXXXXXXX: KEY INTERFACE ERROR. RC=YYYYY, REASON=ZZZZZ.

The interface "XXXXXXXXXX" of external keys management returns an error with return

code "yyyyy", for the reason "zzzzzz". Refer to these codes in the documentation for the

key interface used.

ZTG0174: XXXXXXXX: PROFILES NOT COMPATIBLE TO DECIPHER BUFFER.

A buffer has been received from the node, which is encrypted according to the

cryptographic system defined by an external keys management interface. This Interface

has not been specified in the profiles of the EDITRAN/P session associated with this

presentation. These profiles would most likely have been modified once the presentation

has been received.

ZTG0175: XXXXXXXX: ERROR WHEN CIPHERING THE APPLICATION FILE.

ZTG0176: XXXXXXXX: ERROR WHEN DECIPHERING THE APPLICATION FILE.

ZTG0177: CORRECT AND COMPLETED APPLICATION FILE ENCRYPTION.

ZTG0178: CORRECT AND COMPLETED APPLICATION FILE DECRYPTION.

ZTG0179: EDITRAN SESSIONS MUST HAVE THE SAME ENCRYPTION VERSIONS.

In an EDITRAN/G presentation session with multiple EDITRAN/P transmission sessions, the

Cryptography version does not match in all the EDITRAN/P sessions.

ZTG0180: REMOTE EDITRAN/G VERSION EXPECTED IS NOT RECEIVED: ZZZZ.

Check that the remote EDITRAN/G version is the right one.

ZTG0181: XXXXXXXX: PROFILE CHANGE AFTER LOADING CSB.

It is not allowed changing profiles once the data has been loaded. If necessary, the

statuses should be initialized, the profiles modified and the data reloaded.

ZTG0182: Possible error when defining Profiles: Generational file.

ZTG0183: INCONSISTENT MONITORING STATUS IN THE PRESENTATION.

ZTG0184: NUMBER OF RECORDS TO WRITE EXCEEDS THE HIST. FILE CAPACITY.

ZTG0185: MONITORING ERROR IN PROC. AFTER SESSION END IN PREV. PROC.

ZTG0186: PRESENTATION SESSION NOT UPLOADED.

ZTG0187: NOT ENCRYPTED PRESENTATION RECEIVED.

The profile of the presentation session indicates that the information must be received

encrypted and it is clear.

If desired, the data can be downloaded by modifying the profile of the reception session.

ZTG0188: PROFILE NOT COMPATIBLE WITH ENCRYPTION V2.2 OF THE BUFFER

The cryptography of the presentation session profile is different from that used by the

sender.

EDITRAN/G 5.2 29



ZTG0189: PROFILE NOT COMPATIBLE WITH ENCRYPTION V4.0 OF APP. FILE


sender.


ZTG0190: PROFILE NOT COMPATIBLE WITH ENCRYPTION V3.0 OF APP. FILE


sender.


ZTG0191: XXXXXXXX: LOCKING ERROR IN THE STATUS FILE RC =ZZZZZ

ZTG0192:XXXXXXXX: UNLOCKING ERROR IN THE STATUS FILE RC =ZZZZZ

ZTG0193: UNATTENDED BUFFER NOT SPECIFIED IN THE PROCEDURE

The buffer file with ddname “BUFFER01” is not specified in the procedure.

ZTG0194: UNATTENDED BUFFER DIFFERENT FROM THAT SPECIFIED IN PROFILE

The dsname file of the procedure buffer does not match that of the EDITRAN/P profile.

ZTG0195: ERROR IN THE FEATURES OF THE UNATTENDED BUFFER

The procedure buffer file is not a KSDS, it does not have the correct key length, or the

length of its record is wrong.

ZTG0196: ERROR EXCI.RES: RRRRR RAZ.: SSSSS ABEN:YYYY FUNC.:ZZZZZ

Error when accessing the EXCI interface of buffer file management of “C” type.

For each of the interface functions, the meaning of Response, Reason and Sub-reason

values are contained in the External CICS Interface Manual. (SC33-1390-01)

ZTG0197: ERROR EXCI.RES: RRRRR RAZ.: SSSSS ABEN:YYYY FUNC.:ZZZZZ

Error when accessing the EXCI interface of buffer file management of “C” type, or error

occurred when accessing the EXCI interface to notify the messages to the CICS.

For each of the interface functions, the meaning of the values: Response, Reason and

Abend code are contained in the External CICS Interface Manual (SC33-1390-01)

ZTG0198: ERROR CICS.RES: RRRRR RES2: SSSSS FND.:YYYY FUNC.:ZZZZZ

Error in the CICS module of buffer file management of type “C”.

FUNC is the function used to invoke

FND corresponds to the CICS command that gives the error.

RES and RES2 are the RESP and RESP2 values resulting from the CICS command.

ZTG0199: XXXXXXXX: DETECTED ABEND : SSSS MOD.:YYYYYYYY FUNC.:ZZZZZ

ABEND in the CICS module of buffer file management, type “C”.

FUNC is the function used to invoke

MOD the module in which the abend occurs.

ABEND the abend code.

EDITRAN/G 5.2 30


ZTG0200: ERROR GENERATING SIGNATURE RC=YYYYY REASON=ZZZZZ

ZTG0201: XXXXXXXX: ERROR WHEN OPENING THE FILE YYYYYYYY. F-S: ZZ

ZTG0202: XXXXXXXX: ERROR WHEN CLOSING THE FILE YYYYYYYY. F-S: ZZ

ZTG0203: XXXXXXXX: ERROR WHEN READING IN THE FILE YYYYYYYY. F-S: ZZ

ZTG0204: XXXXXXXX: ERROR WHEN WRITING IN FILE YYYYYYYY. F-S: ZZ

ZTG0205: XXXXXXXX: ERROR WHEN REWRITING FILE YYYYYYYY. F-S: ZZ

ZTG0206: XXXXXXXX: ERROR WHEN DELETING IN FILE YYYYYYYY. F-S: ZZ

ZTG0207: XXXXXXXX: ERROR ALLOCATING THE FILE YYYYYYYY. R-C: ZZZZ

There must be an extended message in ZTBGFPRI concerning a dynamic allocation, whose

codes can be checked in the "Requesting SVC 99 Functions" manual of the builder. The

most common cause is that there is not enough space in the volume to meet the one

requested.

ZTG0208: XXXXXXXX: ERROR DEALLOCATING THE FILE YYYYYYYY. R-C: ZZZZ

The same as the previous one for a deallocation.

ZTG0209: XXXXXXXX: ERROR IN DCB FILE REQUEST YYYYYYYY. R-C: ZZZZ

The file features are requested to the program ZTBGB002 that returns an error return

code.

ZTG0210: XXXXXXXX: INVALID INPUT PARAMETERS YYYYYYYY.

The main program of the procedure receives incorrect parameters. The most common cause

is that wrong procedures have been included in the profiles of EDITRAN/P and/or

EDITRAN/G; for example, one before reception, instead of one after transmission.

ZTG0211: xxxxxxxx: There is no catalogued application file.

In a presentation transmission upload, none of the specified application files are found.

ZTG0212: XXXXXXXX: ERROR RETURNED BY UTILLTY YYYYYYY R-C:ZZZZ

In the list of the execution of the procedure we can find the execution part of the specific

utility. It is usually IDCAMS due to lack of space when defining buffers or because they are

open to the CICS.

ZTG0213: XXXXXXXX: NO CSB RECORD EXISTS IN YYYYYYYY. NREC = ZZZZZ

ZTG0214: XXXXXXXX: BUFFER DEFINITION NOT COMPATIBLE WITH LOAD TYPE.

Specific files are not allowed with cumulative upload type.

ZTG0215: XXXXXXXX: REQUEST FOR CUMULATIVE UPLOAD OF PRESENTATION SESSION.

The loading for a session with cumulative upload type has been requested.

ZTG0216: XXXXXXXX: LOADING ERROR DUE TO A TRANSMISSION IN PROGRESS.

EDITRAN/G 5.2 31


A buffer reload (cumulative upload type) has been requested, but the transmission had

already started. Wait for the transmission to finish to reload the buffer.

ZTG0217: XXXXXXXX: WRONG FEATURES OF APPLICATION FILE.

The application file format specified in the ZTBGFCAR or the fields that define it (format,

language, compression, translation) do not have a valid format.

ZTG0218: XXXXXXXX: APP. FILE NUMBER EXCEEDS THE MAXIMUM ALLOWED

There is a try to upload more than 99 files. Check the (cumulative) load type and those that

are uploaded.

ZTG0219: XXXXXXXX: KEY CHANGE WITH LOADED BUFFER FILE. With cumulative load

type there is a try to upload new files and the keys have been modified.

ZTG0220: XXXXXXXX: DUPLICATE RECEPTION APPLICATION FILE. There is a try to

download several reception files on different application files, but two repeated names are

generated. Check the name of the reception application file and the single file parameter in

reception and restart the download. Download on a single file or provide a name with

enough '% variables'.

ZTG0221: XXXXXXXX: INVALID RECEPTION APPLICATION FILE NAME. The name

generated for an application file during reception does not match the syntax of a DSNAME

in the MVS. Check the name of the reception application file and restart the download.

ZTG0222: XXXXXXXX: THERE IS NO CONVERSION TABLE IN ZTBGFTCO. A conversion

table has been specified in EDITRAN/G profiles and no table exists in the ZTBGFTCO file.

ZTG0223: CONVERSION TABLE APPLIED TO APPLICATION FILE. A conversion table has

been applied to the application file before loading.

ZTG0224: CONVERSION TABLE TO APPLY ACCORDING TO LANGUAGE NOT EXIST. A

conversion table has been specified in EDITRAN/G profiles and it has not been applied since

the original data language (in transmission) or the data language in the file once it has

been translated (in reception) do not match.

ZTG0225: XXXXXXXX: NEEDED START/END VARIABLE.

ZTG0226: NOT USED.

ZTG0227: NOT USED.

ZTG0228: NOT USED.

ZTG0229: XXXXXXXX: EMPTY LIST OF TRANSMISSION FILES. The list of files to be

included in the file of transmission application files for uploading is empty.

ZTG0230: LICENSE ERRORS XXXXXXXXXXXXXXXXXXXXXXXXXXXX. Text of the error

indicated by the license control. Contact INDRA to update your license.

EDITRAN/G 5.2 32


ZTG0231: THERE ARE NO DATA FOR THE PRESENTATION SESSION. Text of the

error in administrator cases.

ZTG0232: CORRECT AND COMPLETED FILE ADAPTATION. Informative text that is displayed

if remote EDITRAN/G version > 4.0, passing through the translator-converter.

ZTG0233: ERROR IN DATA FILE NUMBER, SMALLER THAN REQUIRED. Error in EDITRAN/FF

when loading. Not as many files have been found to be loaded as specified in INPUT.

ZTG0234: NOT USED.

ZTG0235: NOT USED.

ZTG0236: NOT USED.

ZTG0237: NOT USED.

ZTG0238: NOT USED.

ZTG0239: NOT USED

ZTG0240: FILES NUMBER TO UPLOAD GREATER THAN 99. Error in EDITRAN/FF. There are

more than 99 files to upload.

ZTG0241: WRONG INPUT PARAMETERS. Error in EDITRAN/FF. Wrong procedure input

parameters.

ZTG0242: THERE ARE TRANSMISSION FILES IN PROFILES. Error in EDITRAN/FF. Not used.

ZTG0243: ERROR WHEN SENDING ALARM. CHECK ALARM LOG. There was a try to send an

alarm (external manager, e-mail or sms) and it failed. Check alarm log.

ZTG0244: ERROR IN EDITRAN/FF. CHECK JCL OUTPUT. Verify the job output.

ZTG0245: ERROR IN DOWNLOAD. FILES NUMBER RECEIVED > 99. More than 99 files have

been received. Communicate with the remote node to load a maximum of 99 in the current

presentation.

ZTG0246: NOT USED.

ZTG0247: NOT USED

ZTG0248: NOT USED

ZTG0249: NOT USED.

ZTG0250: NOT USED

ZTG0251: NOT USED

EDITRAN/G 5.2 33


ZTG0252: NOT USED

ZTG0253: NOT USED

ZTG0254: NOT USED.

ZTG0255 NOT USED.

ZTG0256: NOT USED.

ZTG0257: NOT USED.

ZTG0258: NOT USED.

ZTG0259: NOT USED.

ZTG0260: NOT USED

ZTG0261: NOT USED

ZTG0262: NOT USED.

ZTG0263: NOT USED.

ZTG0264: NOT USED.

ZTG0265: NOT USED.

ZTG0266: START UP PROCEDURE OR JCL: XXXXXXXX. This is an informative message that

is triggered from batch self-operator (ZTBGBUOP), when in the request file it has been

specified that a procedure-JCL is triggered. It is used to know the name of the JCL procedure

launched.

ZTG0267: NOT USED.

ZTG0268: APPLICATION WITH UPLOAD BY FILE QUEUES IS INACTIVE Check the file queue

profile whose activity is “active”.

ZTG0269: FAILED TO PERFORM THE LOADING. THERE ARE FILES IN TRANSM. Wait for the

end of the current transmission.

ZTG0270: THERE IS NO PROFILE TO TREAT BY FILE QUEUES. You must register the record

in file queues.

ZTG0271: THE PRESENTATION SESSION DOES NOT HAVE LOAD TYPE "Q". Check the

presentation profile.

EDITRAN/G 5.2 34


ZTG0272: FILE PREVIOUSLY RECORDED AND PENDING TRANSMISSION: zzzz. There is a try

to load a file previously uploaded.

ZTG0273: ENCRYPTED SUBS. DIFFERENT FROM PROFILE: YYYYYYYY. The version of the

exchanged keys or subsystem is different between the file received and the presentation

profile.

ZTG0274: CANNOT LOAD, IT DOES NOT MEET DEPTH CRITERIA.

ZTG0275: REMOTE DOWNLOAD COMPLETED. The node download has been confirmed.

ZTG0276: REQUEST FOR DOWNLOAD CONFIRMATION. The node download confirmation is

requested.

ZTG0277: CONFIRMATION NOT ALLOWED BY PROFILES. The remote node asks for the

download confirmation, but the local profile does not allow it.

EDITRAN/G 5.2 35

7.ANNEX B. USER PROGRAMS AND EXIT

7. ANNEX B. USER PROGRAMS AND EXIT

7.1. USER PROGRAMS

7.1.1. GENERAL DESCRIPTION

These programs performed by the user carry out specific functions according to the needs

of each installation and application.

They are executed at the end of the procedure that initializes/ends the process

before/after the presentation and when EDITRAN/P indicates an interruption by means of an

A7I (exception procedure), if they have been specified in the presentation session profile.

7.1.2. INPUT / OUTPUT ELEMENTS

Communication area: passed through the EDITRAN/G invoking programs. It consists of the

information contained in the profiles of local, remote entity, application and presentation

session of EDITRAN/G, the information contained in the profiles of all the associated

transmission sessions of EDITRAN/P, and particular data necessary for processing, and not

contained in profiles.

Files used in the program, whose DD must be specified in the EDITRAN/G procedures.

These files must not have names such as INPUT, OUTPUT, OUTPUTV, BUFFER, ORDNUM01,

02....

7.1.3. CALL CONDITIONS

The program runs when required by the main program of the procedure, or by the user

program already created, once the entire treatment of the process has been completed.

The input conditions of the program vary depending on the process:

Before transmission: It is invoked after loading the transmission buffers, regardless of

whether or not it has been achieved (result code = 0 or # 0).

Before reception: After initializing the buffers.

After transmission: At the end of the process of the last transmission session.

After reception: After the data downloading that is triggered at the end of the last

transmission session.

Exception. The program is invoked in any case.

Attached is an example of user program after transmission. Its purpose is to launch a JOB

when the presentation is finished, or in other words, when the procedure after transmission

of the last transmission session of the presentation is finished.

EDITRAN/G 5.2 36


000100 IDENTIFICATION DIVISION.

000200*************************

000300 PROGRAM-ID. ZTBGBU30.

000400 AUTHOR. ERITEL-5466.

000500*

000600******************************************************************

000700* OBJETO: *

000800* --> *

000900* - EJEMPLO DE PROGRAMA DE USUARIO DEL PROCEDIMIENTO POSTERIOR

001000* A EMISION

001100* - SI EL PROCESO POSTERIOR A EMISION FINALIZO CORRECTAMENTE

001200* SE REALIZA UNA NUEVA PETICION DE EMISION

001300* - EN CASO CONTRARIO SE EJECUTA OTRO PROCEDIMIENTO PARA MAR-

001400* CAR LA INCIDENCIA *

001500* *

001600******************************************************************

001700*

001800 ENVIRONMENT DIVISION.

001900**********************

002000 CONFIGURATION SECTION.

002100*----------------------

002200 SOURCE-COMPUTER. IBM-4331.

002300 OBJECT-COMPUTER. IBM-4331.

002400*

002500 INPUT-OUTPUT SECTION.

002600*---------------------

002700*

002800 FILE-CONTROL.

002900*

003000 SELECT ZTBGFINT ASSIGN TO ZTBGFINT

003100 FILE STATUS IS FS-ZTBGFINT.

003200*

003300 DATA DIVISION.

003400***************

003500*

003600 FILE SECTION.

003700*-------------

003800*

003900 FD ZTBGFINT

004000 LABEL RECORD STANDARD

004100 RECORDING MODE IS F

004200 BLOCK CONTAINS 0 RECORDS.

004300*

004400 01 REGISTRO-ZTBGFINT.

004500 05 FILLER PIC X(80).

004600/

004700 WORKING-STORAGE SECTION.

004800*------------------------

004900*----------------------------------------------------------------*

005000* CAMPOS ESPECIFICOS DEL PROGRAMA *

005100*----------------------------------------------------------------*

005200 77 FS-ZTBGFINT PIC XX VALUE '00'.

005300 77 SEGUIR PIC XX VALUE SPACES.

005400 77 I PIC 9(4) COMP VALUE 0.

005500 77 J PIC 9(4) COMP VALUE 0.

005600 77 K PIC 9(4) COMP VALUE 0.

005700 77 L PIC 9(4) COMP VALUE 0.

005800*

005900 01 LINEA PIC X(80) VALUE SPACES.

006000*

006100 01 LINEA-PROC.

006200 05 FILLER PIC X(16) VALUE '//PASO1 EXEC '.

006300 05 FICH1-PROC PIC X(32) VALUE SPACES.

006400 05 FILLER PIC X(32) VALUE SPACES.

006500*

006600*

006700*-----> CAMPOS PARA LA IGA

006800*

006900 01 WCOMIEN-JCL-IGA PIC X(16) VALUE '//PASO1 EXEC '.

007000 01 WCOMIEN2-JCL-IGA PIC X(11) VALUE '// '.

007100 01 NOMBRE-PROC PIC X(8) VALUE SPACES.

007200 01 ORIGEN-PROC PIC X(08) VALUE ',ORIGEN='.

007300 01 ORIGEN-PROC-2 PIC X(1) VALUE SPACES.

007400 01 FUNCION-PROC-2 PIC X(2) VALUE SPACES.

007500 01 WCOMILLA PIC X(1) VALUE ''''.

007600 01 WE PIC X(1) VALUE 'E'.

007700 01 WCOMA PIC X(1) VALUE ','.

007800 01 FUNCION-PROC PIC X(09) VALUE ',FUNCION='.

007900 01 WPET-IGA PIC X(02) VALUE SPACES.

EDITRAN/G 5.2 37


008000 01 LOCAL0-PROC PIC X(04) VALUE ',L0='.

008100 01 LOCAL1-PROC PIC X(03) VALUE 'L1='.

008200 01 LOCAL2-PROC PIC X(04) VALUE ',L2='.

008300 01 REMOTO1-PROC PIC X(04) VALUE ',R1='.

008400 01 REMOTO2-PROC PIC X(04) VALUE ',R2='.

008500 01 APLICA-PROC PIC X(03) VALUE 'AP='.

008600*

008700 01 LOCAL0-PROC-2 PIC X(03) VALUE SPACES.

008800*

008900 01 SESION-PROC.



009200 05 REMOTO1-PROC-2 PIC X(06) VALUE SPACES.

009300 05 REMOTO2-PROC-2 PIC X(03) VALUE SPACES.

009400 05 APLICA-PROC-2 PIC X(06) VALUE SPACES.

009500*

009600*

009700*---> INCLUDE DEL AREA DE COMUNICACION COMUN

009800**** EXPANSION DE /INCLUDEC ZTBGCCOM

*---------------------------------------------------------------* 00010000

* AREA DE COMUNICACION COMUN PARA CONVERSORES. 00020000

* CONTIENE EL REGISTRO DE PREFILES DE LA IGA 00030000

* Y EL REGISTRO DE PREFILES DE EDITRAN. 00040000

* 00050000

* 00060005

* 00070005

* 23-3-93 00080005

* LA LONGITUD TOTAL DEL AREA = 10400 BYTES. 00090007

*---------------------------------------------------------------* 00100000

* 00110000

01 AREA-COMUN. 00120000

*EXPANSION DE LA COPY ZTBGCRPE

******************************************************************

* CONTIENE LA PARTE DE DATOS DE LOS PERFILES DE LA IGA. *

* EL NIVEL 01 DEL REGISTRO ESTA EN EL LIBRO (LWREGIGA). *

******************************************************************

*

03 REGISTRO-PERFILES-IGA.

05 CLAVE-PERFIGA.

10 PREFIJO PIC X.

10 SESION.

12 CODIGO-LOCAL PIC X(9).

12 CODIGO-REMOTO PIC X(9).

12 APLICACION PIC X(6).

10 NUMERO-ORDEN PIC X(2).

05 REGISTRO-PERFIGA PIC X(2973).

*

* PREFIJO DEL REG. ENTORNO: E. RESTO DE LA CLAVE A CEROS

*

05 ENTORNO-IGA REDEFINES REGISTRO-PERFIGA.

10 CODIGO-LOCAL-IGA-ENTORNO PIC X(9).

10 VERSION-IGA-LOCAL-ENTORNO PIC X(4).

10 VERSION-EDITRAN-LOCAL-ENTORNO PIC X(4).

10 PREFIJO-INSTALACION-ENTORNO PIC X(44).

10 MONITOR-ENTORNO PIC X(4).

10 TIPO-UNIDAD-ENTORNO PIC X(8).

10 LOG-ENTORNO PIC X(1).

10 PROC-PREV-EMISION-ENTORNO PIC X(8).

10 PROC-PREV-RECEPCION-ENTORNO PIC X(8).

10 PROC-POST-EMISION-ENTORNO PIC X(8).

10 PROC-POST-RECEPCION-ENTORNO PIC X(8).

10 PROC-EXCEPCION-ENTORNO PIC X(8).

10 FICHA-JOB-ENTORNO.

12 LINEA-JOB-ENTORNO OCCURS 5 PIC X(59).

10 PROC-ESTADOS-ENTORNO PIC X(8).

10 NOMBRE-ENTORNO PIC X(20).

10 VOL-O-POOL-ENTORNO PIC X(01).

10 VOL-TRABAJ-ENTORNO PIC X(08).

10 ALIAS-ENTORNO PIC X(3).

10 FILLER PIC X(2524).

*

*

* PREFIJO DEL REG. SUBENTORNO: E. CODIGO Y RESTO DE CLAVE A CEROS

*

05 SUBENTORNO-IGA REDEFINES REGISTRO-PERFIGA.

10 DESCRIPCION-SUBENTORNO PIC X(44).

10 ALIAS-SUBENTORNO PIC X(03).


*

EDITRAN/G 5.2 38


* PREFIJO DEL REG. REMOTO : R

*

05 C-REMOTO-IGA REDEFINES REGISTRO-PERFIGA.

10 DESCRIPCION-REMOTO PIC X(20).

10 VERSION-IGA-REMOTO PIC X(4).

10 ASCII-EBCDIC-REMOTO PIC X.

10 COMPRESION-REMOTO PIC X.

10 CRIPTOGRAFIA-REMOTO PIC X.

10 CRC-REMOTO PIC X.

10 ALGORITMO-CONF-REMOTO PIC X(4).

10 ALGORITMO-AUT-REMOTO PIC X(4).

10 INTERFAZ-CLAVES-REMOTO PIC X(8).

10 PARAMETROS-REMOTO PIC X(30).

10 CLAVE-LOC-REMOTO PIC X(64).

10 CLAVE-REM-REMOTO PIC X(64).

*

10 LONG-PSS-REMOTO PIC 9(03).

10 PSS-EBDC-REMOTO PIC X(64).

10 LONG-DN-REMOTO PIC 9(03).

10 DN-EBDC-REMOTO PIC X(64).

10 LONG-PIN-REMOTO PIC 9(03).

10 PIN-EBDC-REMOTO PIC X(64).

*


*

*

* PREFIJO DEL REG. APLICACION: A

*

05 APLICACION-IGA REDEFINES REGISTRO-PERFIGA.

10 DESCRIPCION-APLICACION PIC X(20).

10 CONVERSOR1-EMI-APLICACION PIC X(8).

10 CONVERSOR2-REC-APLICACION PIC X(8).

10 CONVERSOR3-EMI-APLICACION PIC X(8).

10 CONVERSOR4-REC-APLICACION PIC X(8).

10 PROG-PREVIO-EMI-APLICACION PIC X(8).

10 PROG-PREVIO-REC-APLICACION PIC X(8).

10 PROG-POST-EMI-APLICACION PIC X(8).

10 PROG-POST-REC-APLICACION PIC X(8).

10 PROG-EXCEPCION-APLICACION PIC X(8).

10 TRAD-EMI-APLICACION PIC X.

10 BORRAR-F-E-APLICACION PIC X.

10 BORRAR-F-R-APLICACION PIC X.

10 CRITERIO-DIVISION-APLICACION PIC X(2).

10 PARAMETRO-APLICACION PIC X(60).

10 TIPO-CARGA-APLICACION PIC X.

10 TIPO-DESCARGA-APLICACION PIC X.

10 EXIT-PREV-EMI-ANT-APLICACION PIC X(8).

10 EXIT-PREV-EMI-POS-APLICACION PIC X(8).

10 EXIT-POST-REC-ANT-APLICACION PIC X(8).

10 EXIT-POST-REC-POS-APLICACION PIC X(8).

10 LENG-DATOS-ORG-APLICACION PIC X.

10 TRAD-REC-APLICACION PIC X.

10 TABLA-CONV-EMI-APLICACION PIC X(8).

10 TABLA-CONV-REC-APLICACION PIC X(8).


*

* PREFIJO DEL REG. SESION PRESENTACION: P

*

05 SESION-IGA REDEFINES REGISTRO-PERFIGA.

07 PARAM-ENTORNO PIC X(500).

07 FILLER REDEFINES PARAM-ENTORNO.

10 CODIGO-LOCAL-IGA-SESION PIC X(9).

10 VERSION-IGA-LOCAL-SESION PIC X(4).

10 VERSION-EDITRAN-LOCAL-SESION PIC X(4).

10 PREFIJO-INSTALACION-SESION PIC X(44).

10 MONITOR-SESION PIC X(4).

10 TIPO-UNIDAD-SESION PIC X(8).

10 LOG-SESION PIC X(1).

10 PROC-PREV-EMISION-SESION PIC X(8).

10 PROC-PREV-RECEPCION-SESION PIC X(8).

10 PROC-POST-EMISION-SESION PIC X(8).

10 PROC-POST-RECEPCION-SESION PIC X(8).

10 PROC-EXCEPCION-SESION PIC X(8).

10 FICHA-JOB-SESION.

12 LINEA-JOB-SESION OCCURS 5 PIC X(59).

10 PROC-ESTADOS-SESION PIC X(8).

10 NOMBRE-ENT-SUBENTORNO-SESION PIC X(20).

10 VOLUMEN-O-POOL-TRABAJ-SESION PIC X.

10 VOLUMEN-TRABAJO-SESION PIC X(8).

EDITRAN/G 5.2 39


10 ALIAS-SESION PIC X(3).



07 PARAM-REMOTO PIC X(403).

07 FILLER REDEFINES PARAM-REMOTO.

10 DESCRIPCION-REMOTO-SESION PIC X(20).

10 VERSION-IGA-SESION PIC X(4).

10 ASCII-EBCDIC-SESION PIC X.

10 COMPRESION-SESION PIC X.

10 CRIPTOGRAFIA-SESION PIC X.

10 CRC-SESION PIC X.

10 ALGORITMO-CONF-SESION PIC X(4).

10 ALGORITMO-AUT-SESION PIC X(4).

10 INTERFAZ-CLAVES-SESION PIC X(8).

10 PARAMETROS-SESION PIC X(30).

10 CLAVE-LOC-SESION PIC X(64).

10 CLAVE-REM-SESION PIC X(64).

10 LONG-PSS-SESION PIC 9(03).

10 PSS-EBDC-SESION PIC X(64).

10 LONG-DN-SESION PIC 9(03).

10 DN-EBDC-SESION PIC X(64).

10 LONG-PIN-SESION PIC 9(03).

10 PIN-EBDC-SESION PIC X(64).

*


07 PARAM-APLICACION PIC X(250).

07 FILLER REDEFINES PARAM-APLICACION.

10 DESCRIPCION-APL-SESION PIC X(20).

10 CONVERSOR1-EMI-APL-SESION PIC X(8).

10 CONVERSOR2-REC-APL-SESION PIC X(8).

10 CONVERSOR3-EMI-APL-SESION PIC X(8).

10 CONVERSOR4-REC-APL-SESION PIC X(8).

10 PROG-PREVIO-EMI-APL-SESION PIC X(8).

10 PROG-PREVIO-REC-APL-SESION PIC X(8).

10 PROG-POST-EMI-APL-SESION PIC X(8).

10 PROG-POST-REC-APL-SESION PIC X(8).

10 PROG-EXCEPCION-APL-SESION PIC X(8).

10 TRAD-EMI-APL-SESION PIC X.

10 BORRAR-F-E-APL-SESION PIC X.

10 BORRAR-F-R-APL-SESION PIC X.

10 CRITERIO-DIVISION-APL-SESION PIC X(2).

10 PARAMETRO-APL-SESION PIC X(60).

10 TIPO-CARGA-APL-SESION PIC X(1).

10 TIPO-DESCARGA-APL-SESION PIC X(1).

10 EXIT-PREV-EMI-ANT-APL-SESION PIC X(8).

10 EXIT-PREV-EMI-POS-APL-SESION PIC X(8).

10 EXIT-POST-REC-ANT-APL-SESION PIC X(8).

10 EXIT-POST-REC-POS-APL-SESION PIC X(8).

10 LENG-DATOS-ORG-APL-SESION PIC X(01).

10 TRAD-REC-APL-SESION PIC X(01).

10 TABLA-CONV-EMI-APL-SESION PIC X(08).

10 TABLA-CONV-REC-APL-SESION PIC X(08).



07 PARAM-PRESENTACION PIC X(1129).

07 FILLER REDEFINES PARAM-PRESENTACION.

10 DESCRIPCION-SESION PIC X(20).

10 NUMERO-SESIONES-TRANSMISION PIC 99.

10 TABLA-SESIONES.

12 ELEMENTO OCCURS 20.

14 SESION-TRANSMISION.

16 REMOTO-TRANSMISION PIC X(9).

16 APLICA-TRANSMISION PIC X(6).

14 VOLUMEN-FICHERO-TAMP-E PIC X(8).

14 FILLER REDEFINES VOLUMEN-FICHERO-TAMP-E.

16 STOCL-FICHERO-TAMP-E PIC X(8).

14 NUMERO-REGISTROS-TAMPON PIC 9(5).

*--> TABLA NO SE UTILIZA A PARTIR DE VERSION-EDI-G-41

10 TABLA-FICHEROS-RECEPCION.

12 ELEMENTO2 OCCURS 5.

14 NOMBRE-FISICO-R-OLD PIC X(44).

14 VOLUMEN-R PIC X(8).

14 FILLER REDEFINES VOLUMEN-R.

16 STOCL-R PIC X(8).

14 IDENTIFICADOR-R PIC X(8).

14 LRECL-R PIC 9(5).

10 FILLER REDEFINES TABLA-FICHEROS-RECEPCION.

12 NOMBRE-FISICO-R PIC X(44).


EDITRAN/G 5.2 40


10 BORRAR-FA-SI-EXISTE PIC X.

10 VOLSER-O-UNIT PIC X(1).

10 VOLSER-RECEP-V21 PIC X(8).

10 FILLER REDEFINES VOLSER-RECEP-V21.

12 STOCL-RECEP-V21 PIC X(8).

10 UNIT-DE-VOLSER-V21 PIC X(8).

*--> TABLA NO SE UTILIZA A PARTIR DE VERSION-EDI-G-41

10 TABLA-UNIT-V20.

12 ELEMENTO3 OCCURS 5.

14 UNIT-DE-VOLSER-V20 PIC X(8).

10 INCREMENTAR-SESION PIC X(1).

10 FORMATO-FICH-DESCARGA PIC X(1).

10 FICHERO-UNICO-RECEPCION PIC X(1).

10 VOLUMEN-POOL-TAMPONES PIC X(1).

10 TABLA-VOL-TAM-FICH-R.

12 ELEMENTO-TABLA-VOL-TAM-R OCCURS 20.

14 VOLUMEN-FICHERO-TAMP-R PIC X(8).

14 FILLER REDEFINES VOLUMEN-FICHERO-TAMP-R.

16 STOCL-FICHERO-TAMP-R PIC X(8).


*

* PREFIJO DEL REG. SESION TRANSMISION : T

*

05 SESION-TRANSMISION-IGA REDEFINES REGISTRO-PERFIGA.

10 SESION-ASOCIADA.

15 CODIGO-LOCAL-P PIC X(9).

15 CODIGO-REMOTO-P PIC X(9).

15 APLICACION-P PIC X(6).


*

* PREFIJO DEL REG. FICHERO DE APLICACION : F

*

05 FICHERO-APLICACION-IGA REDEFINES REGISTRO-PERFIGA.

10 NOMBRE-FISICO-E PIC X(44).

*--> CAMPO NO SE UTILIZA A PARTIR DE VERSION-EDI-G-41

10 IDENTIFICADOR-E PIC X(8).

10 FORMATO-FICHERO-E PIC X.

10 LENG-DATOS-ORG-E PIC X.

10 TRAD-EMI-E PIC X.

10 COMPRESION-E PIC X.


*

* PREFIJO DEL REG. LICENCIAS: Z. CODIGO Y RESTO DE CLAVE A CEROS

*

05 REG-LIC-ZTBGFPE REDEFINES REGISTRO-PERFIGA.

10 IDENTIF-ORIGEN-LIC-ZTBGFPE PIC X(15).

10 TIPO-REGISTRO-LIC-ZTBGFPE PIC X(01).

10 DATOS-A-ENMAS-LIC-ZTBGFPE.

15 COD-ENT-LIC-ZTBGFPE.

20 COD1-ENT-LIC-ZTBGFPE PIC X.

20 CODX-ENT-LIC-ZTBGFPE PIC X(3).

20 COD9-ENT-LIC-ZTBGFPE PIC X.

15 CADUC-ENT-LIC-ZTBGFPE PIC X(4).

15 ID-CODIGO-LIC-ZTBGFPE PIC X(15).

15 VERSION-LIC-ZTBGFPE PIC X(4).

15 TIPO-LIC-ZTBGFPE PIC X.

15 TABLA-PRODUCTOS-LIC-ZTBGFPE OCCURS 20.

20 CADUC-PRO-LIC-ZTBGFPE PIC X(4).

20 TIPO-PRO-LIC-ZTBGFPE PIC X.

15 FILLER PIC X.

10 DATOS-ENMASCAR-LIC-ZTBGFPE PIC X(130).


* EXPANSION DE LA COPY ZTBGC004. 00140117

*----------------------------------------------------------------*

*-- PARTE DE DATOS DEL PROGRAMA ZTBGB004... *

* LONGITUD : 4850 BYTES (20/08/97)

*

*-- CODIGOS DE RESULTADO DEL ZTBGB004

* CODIGO-RDO DESCRIPCION

* ---------- --------------------------------------------------

* 00 NO SE HA DETECTADO INCIDENCIAS

* OTROS COINCIDEN CON LOS CODIGOS DE LOS MENSAJES DE

* EDITRAN/G

*

*-- CODIGOS INFORMATIVOS DE LOS PARAMETOS DE LAS S-T

* RDO-LONG-TRANS DESCRIPCION

* -------------- ----------------------------------------------

* 00 LONGITUDES DE TRANSMISION CORRECTAS

* 01 S-T CON LONGITUDES DE TRANSMISION DIFERENTES

EDITRAN/G 5.2 41


*

* RDO-COMPRESION DESCRIPCION

* -------------- ----------------------------------------------

* 00 SESIONES DE TRANSMISION SIN COMPRESION

* 01 AL MENOS UNA SESION UTILIZA COMPRESION

*

* RDO-CIFRADO DESCRIPCION

* -------------- ----------------------------------------------

* 01 S-T CON VERSIONES DE CRIPTOGRAFIA DIFERENTES

* 02 VERSIONES DE CRIPTOGRAFIA NO CUMPLIMENTADAS

* (TODAS CON ESPACIOS O LOW-VALUES)

* 03 VERSION-EDI-S-220 SIN CRIPTOGRAFIA

* 04 VERSION-EDI-S-220 CON AUTENTICACI. Y CAMBIO DE

* CLAVE

*

* RDO-TAMPON-E/R DESCRIPCION

* -------------- ----------------------------------------------

* 01 S-T CON TIPO (M/E) DE TAMPONES (E/R) DISTINTOS

* 02 S-T TAMPONES MATRICIALES (E/R) DIFERENTES

* 03 TAMPONES DE EMISION NO CONSECUTIVOS

* 04 NIGUN TAMPON DE EMISION CUMPLIMENTADO

* O ALGUN TAMPON DE RECEPCION NO CUMPLIMENTADO

* 05 TIPO DE TAMPON DESCONOCIDO PARA EDITRAN/G

*----------------------------------------------------------------*

*

03 RESTO-AREA-ZTBGB004.

05 PROCESO-LLAMANTE-ZTBGB004 PIC X(1).

05 SESION-PRES-ZTBGB004 PIC X(32).

05 LOG-SESION-ZTBGB004 PIC X(01).

05 CODIGO-RDO-ZTBGB004 PIC 9(4).

05 FILE-STATUS-ZTBGB004 PIC X(2).

05 ERRCOD-ZTBGB004 PIC 9(5).

05 TABLA-FICHAS-ZTBGB004.

10 ELEMENTO-FICHA-ZTBGB004 PIC X(59) OCCURS 5.

05 TABLA-SESIONES-ZTBGB004 PIC X(3520).

05 FILLER REDEFINES TABLA-SESIONES-ZTBGB004 OCCURS 20.

10 ELEMENTO-SESION-ZTBGB004.

15 RDO-TRANSMISION-ZTBGB004 PIC 9(4).

15 SESION-TRANSMISION-ZTBGB004.

20 ORIGEN-ZTBGB004 PIC X(9).

20 REMOTO-ZTBGB004 PIC X(9).

20 APLICACION-ZTBGB004 PIC X(6).

15 FICHERO-EMISION-ZTBGB004.

20 LOGICO-EMISION-ZTBGB004 PIC X(7).

20 FISICO-EMISION-ZTBGB004 PIC X(44).

15 FICHERO-RECEPCION-ZTBGB004.

20 LOGICO-RECEPCION-ZTBGB004 PIC X(7).

20 FISICO-RECEPCION-ZTBGB004 PIC X(44).

15 LONGITUD-FICHERO-ZTBGB004 PIC 9(04).

15 VERSION-EDI-REMOTO-ZTBGB004 PIC 9(02).

15 TIPO-TAMPON-EMIS-ZTBGB004 PIC X(1).

15 TIPO-TAMPON-RECEP-ZTBGB004 PIC X(1).

15 COMPRESION-ZTBGB004 PIC X(1).

15 CRIPTOGRAFIA-ZTBGB004 PIC X(1).

15 CAMBIO-CLAVE-ZTBGB004 PIC X(1).

15 CLAVE-EMK-BAJO-AK-ZTBGB004 PIC X(8).

15 CLAVE-TKE-BAJO-EMK-ZTBGB004 PIC X(8).

15 CLAVE-TKR-BAJO-EMK-ZTBGB004 PIC X(8).

15 VERSION-CRIP-ZTBGB004.

17 VERSION-2-CRIP-ZTBGB004 PIC X(2).

17 FILLER PIC X(1).

15 ALGORITMO-CONF-ZTBGB004 PIC X(4).

15 ALGORITMO-AUT-ZTBGB004 PIC X(4).

05 DATOS-ENTORNO-ZTBGB004.

10 NOMBRE-CICS-ZTBGB004 PIC X(08).

10 TRANSACCION-ZTBGB004 PIC X(04).

10 TRANS-EXCI-ZTBGB004 PIC X(04).

* EN PRINCIPIO, VERSION Y CODIGO LOCAL EDITRAN, SON DATOS ENTRADA

10 CODIGO-LOCAL-ZTBGB004 PIC X(09).

10 VERSION-EDITRAN-LOCAL-ZTBGB004 PIC X(4).

10 ALIAS-ENT-SUBENT-ZTBGB004 PIC X(3).

05 DSNAME-ZTBGFEST-ZTBGB004 PIC X(44).

05 LABEL-LOCAL-ZTBGB004 PIC X(8).

05 LABEL-REMOTO-ZTBGB004 PIC X(8).

05 CODIGO-LOCAL-V22-ZTBGB004 PIC 9(6).

05 CODIGO-REMOTO-V22-ZTBGB004 PIC 9(6).

05 NOMBRE-CPU-ZTBGB004 PIC X(8).

05 NETNAME-EXCI-ZTBGB004 PIC X(08).

05 DSNAME-ZTBEFMP-ZTBGB004 PIC X(44).

EDITRAN/G 5.2 42


05 TABLA-SES-INTERNAS-ZTBGB004 PIC X(640).

05 FILLER REDEFINES TABLA-SES-INTERNAS-ZTBGB004 OCCURS 20.

10 SESION-INTERNA-ZTBGB004 PIC X(32).

* CODIGOS DE RESULTADO INFORMATIVOS SOBRE PARAMETROS DE LAS S-T

05 RDO-LONG-TRANS-ZTBGB004 PIC X(2).

05 IND-LONG-TRANS-ZTBGB004 PIC 9(2).

05 RDO-COMPRESION-ZTBGB004 PIC X(2).

05 IND-COMPRESION-ZTBGB004 PIC 9(2).

05 RDO-CIFRADO-ZTBGB004 PIC X(2).

05 IND-CIFRADO-ZTBGB004 PIC 9(2).

05 RDO-TAMPON-E-ZTBGB004 PIC X(2).

05 IND-TAMPON-E-ZTBGB004 PIC 9(2).

05 RDO-TAMPON-R-ZTBGB004 PIC X(2).

05 IND-TAMPON-R-ZTBGB004 PIC 9(2).

05 RDO-JCLS-IGUALES-ZTBGB004 PIC X(2).

05 IND-JCLS-IGUALES-ZTBGB004 PIC 9(2).

05 NBRE-APL-CICS-ZTBGB004 PIC X(8).

05 IDENTIF-JCLS-ENT-ZTBGB004 PIC X(01).

05 SERV-CERTIF-ZTBGB004.

10 TCPNAME-ZTBGB004 PIC X(8).

10 DIR-IP-ZTBGB004.


20 IP1-ZTBGB004 PIC 9(03).

20 PUNTO1-ZTBGB004 PIC X(01).

20 IP2-ZTBGB004 PIC 9(03).


20 IP3-ZTBGB004 PIC 9(03).


20 IP4-ZTBGB004 PIC 9(03).

10 PUERTO-RED-SERV-ZTBGB004 PIC 9(4) COMP.

10 SEG-ACT-SERV-ZTBGB004 PIC 9(3).


03 VBLES-PROC-COMUN PIC X(150). 00160008

03 FILLER REDEFINES VBLES-PROC-COMUN. 00170008

05 NRO-SESION-COMUN PIC 9(4). 00180008

05 SENTIDO-COMUN PIC X(1). 00181016

05 ESTADO-PRESENTACION-COMUN PIC 9(3). 00182018

05 DATOS-CIF-COMUN. 00182121

07 IND-CLAVE-PRES-COMUN PIC X(1). 00182219

07 CLAVE-PRES-EMK-COMUN PIC X(8). 00182319

07 CLAVE-PRES-HMK-COMUN PIC X(8). 00182419

07 EMK-AK-COMUN PIC X(8). 00183019

05 FILLER PIC X(117). 00190019

03 RESTO-AREA-COMUN PIC X(2400). 00200008

**** EXPANSION DE /INCLUDEC ZTBGCU30

/---------------------------------------------------------------* 00010000

*- -* 00020000

*- AREA DE COMUNICACION CON LOS PROGRAMAS DE USUARIO -* 00030004

*- -* 00040000

*---------------------------------------------------------------* 00050000

*- -* 00060000

01 WPROG-USUARIO PIC X(08) VALUE SPACES. 00070005

01 AREA-U0V30000. 00072007

03 RESTO-AREA-U0V30000. 00080007

05 CODIGO-RDO-U0V30000 PIC 9(4). 00090007

05 CODIGO-RET-U0V30000 PIC 9(4). 00091007

05 MENSAJE-U0V30000 PIC X(100). 00092007

05 FILLER REDEFINES MENSAJE-U0V30000. 00093007

10 LONGITUD-U0V30000 PIC 9(4) COMP. 00098507

10 ORIGEN-U0V30000 PIC X(01). 00098607

10 FUNCION-U0V30000 PIC X(02). 00098707

10 SESION-PRESENTACION-U0V30000. 00098807

15 LOCAL-U0V30000 PIC X(9). 00098910

15 REMOTO-U0V30000 PIC X(9). 00099010

15 APLICACION-U0V30000 PIC X(6). 00099107

*-REDEFINICION DE LA SESION DE PRESENTACION (SOLO SI ORIGEN E)

*-LLEGA AQUI LA SESION DE TRANSMISION

*-LA SESION DE PRESENTACION ESTA EN PERFILES, CAMPO SESION

10 FILLER REDEFINES SESION-PRESENTACION-U0V30000.

15 SESION-TRANS-U0V30000 PIC X(24).

10 REFERENCIA-A7I-U0V30000 PIC X(04). 00099207

10 FILLER PIC X(67). 00099311

05 RESTO2-AREA-U0V30000 PIC X(1294). 00100007

*- -* 00110000

044400*- -*

044500*

044600 LINKAGE SECTION.

044700*----------------

EDITRAN/G 5.2 43


044800*

044900 01 AREA-ENTRADA PIC X(10400).

045000*

045100 PROCEDURE DIVISION USING AREA-ENTRADA.

045200*--------------------------------------

045300*

045400 N1-P-PROGRAMA.

045500*--------------

045600*

045700*

045800 MOVE AREA-ENTRADA TO AREA-COMUN

045900 MOVE RESTO-AREA-COMUN TO RESTO-AREA-U0V30000

046000 MOVE ZEROS TO CODIGO-RDO-U0V30000

046100*

046200 PERFORM N2-P-PROCESO

046300 THRU N2-F-PROCESO.

046400*

046500* ----- SI SE HA PRODUCIDO UN ERROR O INCIDENCIA, SEGUIR = 'NO' Y

046600* ----- SE GRABA LA INCIDENCIA EN EL LOG Y FINALIZA EL PROCESO.

046700*

046800*

046900 MOVE RESTO-AREA-U0V30000 TO RESTO-AREA-COMUN

047000 MOVE AREA-COMUN TO AREA-ENTRADA.

047100*

047200 N1-F-PROGRAMA.

047300*--------------

047400 GOBACK.

047500/

047600*NIVEL II.

047700*

047800 N2-P-PROCESO.

047900*--------------*

048000*

048100 PERFORM N4-P-ABRIR-ZTBGFINT

048200 THRU N4-F-ABRIR-ZTBGFINT.

048300*

048400*--- SE ESCRIBEN LAS 5 PRIMERAS FICHAS DEL JCL

048500*

048600 PERFORM R-P-ESCRIBE-FICHA-JOB

048700 THRU R-F-ESCRIBE-FICHA-JOB

048800 VARYING I FROM 1 BY 1

048900 UNTIL I > 5 OR SEGUIR = 'NO'.

049000*

049100*--- SE ESCRIBE LA FICHA DEL EXEC DEL PROCEDIMIENTO

049200*

049300 IF SEGUIR = 'SI'

049400 PERFORM R-P-ESCRIBE-PROCEDIMIENTO

049500 THRU R-F-ESCRIBE-PROCEDIMIENTO.

049600*

049700*--- SE ESCRIBE LA FICHA DE FIN DE JCL

049800*

049900 IF SEGUIR = 'SI'

050000 MOVE '//' TO LINEA

050100 PERFORM R-P-ESCRIBE

050200 THRU R-F-ESCRIBE.

050300*

050400*--- AL CERRAR LA INTERNAL-READER SE SUBMITE EL PROCEDIMIENTO.

050500*

050600 PERFORM N4-P-CERRAR-ZTBGFINT

050700 THRU N4-F-CERRAR-ZTBGFINT.

050800*

050900 N2-F-PROCESO.

051000*--------------*

051100 EXIT.

051200*

051300*NIVEL IV.

051400*

051500 N4-P-ABRIR-ZTBGFINT.

051600*-----------------*

051700*

051800 OPEN OUTPUT ZTBGFINT.

051900*

052000 IF FS-ZTBGFINT = '00'

052100 MOVE 'SI' TO SEGUIR

052200 ELSE

052300 MOVE 'NO' TO SEGUIR

052400 MOVE 1 TO CODIGO-RDO-U0V30000.

052500*

052600 N4-F-ABRIR-ZTBGFINT.

EDITRAN/G 5.2 44


052700*-----------------*

052800 EXIT.

052900*

053000 N4-P-CERRAR-ZTBGFINT.

053100*-------------------*

053200*

053300*---- EN ESTE MOMENTO SE SUBMITE EL PROCEDIMIENTO.

053400*

053500 CLOSE ZTBGFINT.

053600*

053700 IF SEGUIR = 'SI' AND FS-ZTBGFINT NOT = '00'



054000*

054100 N4-F-CERRAR-ZTBGFINT.

054200*-------------------*

054300 EXIT.

054400/

054500*

054600 R-P-ESCRIBE-FICHA-JOB.

054700*----------------------*

054800*

054900 MOVE ELEMENTO-FICHA-ZTBGB004 (I) TO LINEA.

055000*



055300*

055400 R-F-ESCRIBE-FICHA-JOB.

055500*----------------------*

055600 EXIT.

055700*

055800 R-P-ESCRIBE-PROCEDIMIENTO.

055900*--------------------------*

056000*

056100 MOVE 'A' TO ORIGEN-PROC-2

056200 MOVE FUNCION-U0V30000 TO FUNCION-PROC-2

*

IF ORIGEN-U0V30000 = 'E'

MOVE SESION TO SESION-PROC

ELSE

MOVE SESION-PRESENTACION-U0V30000 TO SESION-PROC.

*

056400 MOVE ALIAS-ENT-SUBENT-ZTBGB004 TO LOCAL0-PROC-2

056500*

056600 IF CODIGO-RET-U0V30000 = ZEROS

056700 IF FUNCION-U0V30000 = '07'

056800 MOVE '06' TO FUNCION-PROC-2

056900 MOVE PROC-PREV-RECEPCION-SESION TO NOMBRE-PROC

057000 MOVE SESION TO SESION-PROC

057100 ELSE

057200 MOVE '01' TO FUNCION-PROC-2

057300 MOVE PROC-PREV-EMISION-SESION TO NOMBRE-PROC

057400 MOVE SESION TO SESION-PROC

057500 ELSE

057600 MOVE 'D3ZTBGLU' TO NOMBRE-PROC.

057700*

057800 STRING WCOMIEN-JCL-IGA DELIMITED BY SIZE

057900 NOMBRE-PROC DELIMITED BY SPACE

058000 ORIGEN-PROC DELIMITED BY SIZE

058100 WCOMILLA DELIMITED BY SIZE

058200 ORIGEN-PROC-2 DELIMITED BY SIZE


058400 FUNCION-PROC DELIMITED BY SIZE


058600 FUNCION-PROC-2 DELIMITED BY SIZE


058800 LOCAL0-PROC DELIMITED BY SIZE


059000 LOCAL0-PROC-2 DELIMITED BY SIZE


059200 WCOMA DELIMITED BY SIZE

059300 INTO LINEA.

059400*



059700*

059800 STRING WCOMIEN2-JCL-IGA DELIMITED BY SIZE



EDITRAN/G 5.2 45








060700 REMOTO1-PROC DELIMITED BY SIZE


060900 REMOTO1-PROC-2 DELIMITED BY SIZE


061100 REMOTO2-PROC DELIMITED BY SIZE


061300 REMOTO2-PROC-2 DELIMITED BY SIZE


061500 WCOMA DELIMITED BY SIZE

061600 INTO LINEA.

061700*



062000*

062100 STRING WCOMIEN2-JCL-IGA DELIMITED BY SIZE

062200 APLICA-PROC DELIMITED BY SIZE


062400 APLICA-PROC-2 DELIMITED BY SIZE


062600 INTO LINEA.

062700*



063000*

063100 R-F-ESCRIBE-PROCEDIMIENTO.

063200*-------------------------*

063300 EXIT.

063400*

063500*

063600 R-P-ESCRIBE.

063700*------------*

063800*

063900 WRITE REGISTRO-ZTBGFINT FROM LINEA.

064000*

064100 IF FS-ZTBGFINT = '00'

064200 MOVE SPACES TO LINEA

064300 MOVE 'SI' TO SEGUIR

064400 ELSE



064700*

064800 R-F-ESCRIBE.

064900*------------*

065000 EXIT.

065100*

EDITRAN/G 5.2 46


7.2. BATCH SELF-OPERATOR


A user program has been created, which can be included in profiles or called from within

the user programs. It allows linking with the entity planners and triggering JCLs or procedures.

Due to the incorporation of this new functionality, the transition area to the user program has

been modified in the case of A7I, so that the presentation session is passed instead of the


This program is the ZTBGBUOP, which uses a file containing the list of requests, called

Installation prefix-ZTBGFUSU, 200 plane.


Communication Area: passed through the EDITRAN/G invoking programs. Its content was

specified in the user program.

File used in the program (ZTBGFUSU), created by the user, whose format is specified

below:

01 REG-FUSU.

03 REG-200-FUSU PIC X(200).

03 REG-CGO-A7I-FUSU REDEFINES REG-200-FUSU.

05 EMI-REC-FUSU PIC X(3).

05 FILLER PIC X.

05 CGOS-FUSU OCCURS 36.

10 CGO-A7I-FUSU PIC X(3).

10 FILLER PIC X.


03 REG-PETICIONES-FUSU REDEFINES REG-200-FUSU.

05 PETICION-E-FUSU PIC X(40).

05 FILLER REDEFINES PETICION-E-FUSU.

10 FUNCION-E-FUSU PIC X(02).

10 SESION-PRES-E-FUSU.

15 LOCAL-E-FUSU PIC X(9).

15 REMOTO-E-FUSU PIC X(9).

15 APLICACION-E-FUSU PIC X(6).

10 REFERENCIA-A7I-E-FUSU.

15 EMI-REC-A7I-E-FUSU PIC X.

15 CGO-A7I-E-FUSU PIC X(03).


05 PETICION-S-FUSU PIC X(160).

05 FILLER REDEFINES PETICION-S-FUSU.

10 FUNCION-S-FUSU PIC X(02).

10 SESION-PRES-S-FUSU.

15 LOCAL-S-FUSU PIC X(9).

15 REMOTO-S-FUSU PIC X(9).

15 APLICACION-S-FUSU PIC X(6).

10 HORA-INI-FUSU PIC X(4).

10 HORA-FIN-FUSU PIC X(4).

10 COD-RET-S-FUSU PIC 9(4).

10 FILLER REDEFINES COD-RET-S-FUSU.

15 NRO-REINT-FUSU PIC 9(4).

10 NFUNCION-S-FUSU PIC X(02).

10 UBICACION-S-FUSU PIC X(44).

10 FILLER REDEFINES UBICACION-S-FUSU.

15 TIEMPO-WAIT-FUSU PIC 9(8).




1 Record of processable A7I

codes.

200 Alph. Record of A7I reference codes that will be

processed by the program.

Several records of this type can be established.

EDITRAN/G 5.2 47


2 A7I type 3 Alph. ‘EMI’. The codes included in the record are

transmission codes

REC' The codes included in the record are

reception codes

2 Filler 1 Alph. Separation space

2 Table of A7I codes 144 Alph. Table of A7I references of transmission or

reception OCCURS 36 (the last 2 octets are

ignored)

3 A7I reference 3 Num. A7I Reference

3 Filler 1 Alph. Separation space


1 Record of input

actions-output

actions

200 Alph. Record where the causative action and the

action to be taken are entered

2 Causative action 40 Alph. Report of data reserved to the causative action

3 Causative function 2 Num. Spaces: any action

01: Transmission load

02: After transmission

03: Presentation transmission

05: Transmission exception (interrupt

transmission)

06: Reception initialization

07: After reception

08: Presentation reception

09: Reception exception (interrupt recep.)

3 Causative

presentation session

24 Alph. Presentation session code.

4 Origin of causative

presentation

9 Alph. Origin code of the causative presentation

session

Spaces: Any code is valid

4 Destination of

causative

presentation

9 Alph. Destination code of the causative presentation

session


4 Causative

presentation

application

6 Alph. Causative presentation application


3 Source A7I reference 4 Alph. Specific A7I reference to be treated in the

request (in case of function 05 and 09).

Spaces: Search in the A7I record.

4 Source A7I ref. type 1 Alph. A7I Reference Type (E:Transmission,

R:Reception).

4 Source A7I ref. code 3 Num. A7I Reference Code.

3 Filler 10 Alph. Reservation area of the source request

2 Actions to be taken 160 Alph. Data report reserved to the actions to be taken

3 Function of actions

to be taken

2 Num. 01: Transmission load

02: After transmission

03: Presentation transmission

05: Transmission exception (interrupt

transmission)

06: Reception initialization

07: After reception

08: Presentation reception

09: Reception exception (interrupt recep.)

21: Return code of return

22: Submit procedure

23: Submit JCL

EDITRAN/G 5.2 48


24: Control of number of retries in A7I

25: Wait a while (WAIT), before continuing to

perform the specified tasks.

3 Presentation session

of actions to be

taken

24 Alph. Presentation session code

4 Presentation origin

of actions to be

taken

9 Alph. Source code of the presentation session of the

actions to be taken.

4 Presentation

destination of

actions to be taken

9 Alph. Destination of the presentation session of the


4 Presentation

application of actions

to be taken

6 Alph. Application of the presentation session of the


3 Start time of actions

to be taken

4 Num Spaces or zeros: It does not validate the start

time.

HHMM: It will be validated that the actions to

take will be after the action start time

3 End time of actions

to be taken

4 Num Spaces or zeros: It does not validate the start

time.

HHMM: It will be validated that the actions to

take will be before the action end time

3 Return code of

actions to be taken

4 Num Return code returned by the program. It is only

used if the action to be taken is equal to 21

3 REDEFINITION

4 Number of retries 4 Num Number of retries (0001-9999).

It is only used if the action to take is equal to

24 and it is an A7I

3 New function to take 2 Num New action to take (see action to take), if

action to take = 22.

It can take the value chosen by the user for its

procedure

3 JCL location of the

actions to be taken

44 Alph. Field with variables to run a JCL-procedure (as

specified in the corresponding table). It is only

used if the action to take is equal to 22 or 23.

If the action is 23, only the name of the

procedure, which may be a variable name (up

to 8 positions), is given.

3 REDEFINITION

4 Wait time 8 Num Timeout or WAIT time before continuing

(HHMMSSDC).

It is only used if the action to take is equal to

25 and it is an A7I

4 Filler 36

3 Filler 86 Alph. Reservation area of the source request

Within the location, the job name will have 8 characters. If not, a character is generated

at the end that will be the digit of the incoming request.

To give the location of the procedure or JCL, follow the rules to enter variable pointers,

used to choose the name of the reception application file, in particular:

EDITRAN/G 5.2 49


% variables allowed. If the input variable does not contain a valid value, the default

value is applied (as the allowed variables are more numerous, ZTBGBUOP shall check that only

those specified below are applied):

Var Meaning Valid value. Default

value

%Y Last digit of the year

%A Two last digits of the year

(aa)

%M Month in two digits (mm)

%X Month in one character

(1,2,3,4,5,6,7,8,9,O,N,D)

%D Day of the month (dd)

%H Time (hhmmss)

%R The last 7 characters of the

node code

Different from spaces or

x’00’

Zeros

%P Application code Different from spaces or

x’00’

Zeros


The program runs when required by the main program of the procedure, or by the user

program already created, once the entire treatment of the process has been completed.

The input conditions of the program vary depending on the process:

Before transmission: It is invoked after loading the transmission buffers, regardless of

whether or not it has been achieved (result code = 0 or # 0).

Before reception: After initializing the buffers.

After transmission: At the end of the process of the last transmission session.

After reception: After the data downloading that is triggered at the end of the last


Exception. The program is invoked in any case.

Below is an example specifying the contents of the ZTBGFUSU file:

EMI-010-020-021-022-023-024-150

REC-030-040-050-060-070-080-090

09000099980000099940PRUEBA ----------08000099980000099940PRUEBA00002359

E230----------01000099980000099940PARAMI10301130

09 000099960PRUEBAR100----------21 0029

01000099980000099940PRUEBXR100----------22000099980000099940PARAMI 03J%R

01000099980000099940PRUEBAR100----------23000099980000099940PARAMI KI.L%A(J%R)

Their meaning would be:

Card 01: Transmission A7I reference codes that will be processed by program.

Card 02: Reception A7I reference codes that will be processed by program.

EDITRAN/G 5.2 50


Card 03: When a reception A7I of the described session arrives,

000099980000099940PRUEBA, if the A7I code belongs to those of the card 02, the

presentation reception (function 08) of that session is requested.

Card 04: When any message with a transmission A7I with E230 code arrives (even if it is

not in the card 02), a message before transmission will be launched, if the system time is

between 10:30 and 11:30.

Card 05: When a transmission load of the reception A7I session with reference R100 of the

node-application described above arrives, with any of the multi-environment codes of my

entity, the job that is being executed with return code 29 will be finished.

Card 06: When a request for transmission load of session 000099980000099940PRUEBX,

arrives, a procedure called J0099940 will be generated. The following will be passed as PARM:

ORIGIN='A', FUNCTION='03', L0='alias of the local sub-environment', L01='000098', L2='980',

R1='000094', R2='980', AP=' PARAMI'.

Card 07: When a request for transmission load of session

000099980000099999940PRUEBA arrives, a JCL will be generated that is located in the

library KI.LPRUEBA, which will be called J0099940.

EDITRAN/G 5.2 51


7.3. USER EXIT.


An Exit is a user program that performs specific functions according to the needs of each

installation and application and it only affects the download process by obtaining the

reception application files.

It is executed after the reservation of each reception file and before the call to the

Converter that opens them to store the received data. The name of the Exit should be

included in the corresponding Application profile and therefore in the Presentation Session

profile.

An Exit will normally be used to record one or more user records before those obtained in

the download. It is assumed that the Exit knows the characteristics of the application files

received, fixed or variable file type, and record length. The external file name in the Exit

should be OUTPUT or OUTPUTV depending on whether the records are fixed or variable

length respectively.

The Exit will receive a communication area with sufficient information to distinguish

whether or not it is the first file to be downloaded, or whether it is a single file, in which all

the files to be received are downloaded, together with various data from the record of the

reception buffer containing the application file being obtained.


Communication area: passed through the EDITRAN/G invoking programs. It consists of the

information contained in the profiles of local, remote entity, application and presentation

session of EDITRAN/G, the information contained in the profiles of all the associated

transmission sessions of EDITRAN/P, and particular data necessary for processing, and not

contained in profiles.

Files used in the program, whose DDs must be specified in the EDITRAN/G procedures.

These files must not have names such as INPUT, OUTPUT, OUTPUTV, BUFFER, ORDNUM01,

02....


The program is invoked after the reservation ("alloc") of the reception application file,

before calling the Converter after the reception, and before including the data in the current

file.

Attached is an example of a user exit that aims to save a record in the reception file with

the transmission date and time.

EDITRAN/G 5.2 52


000100 IDENTIFICATION DIVISION.

000200*************************

000300 PROGRAM-ID. ZTBGBE40

000400 AUTHOR. RAE.

000500*

000600******************************************************************

000700* OBJETO: *

000800* PROGRAMA QUE GRABA UN REGISTRO EN UN FICHERO *

000900* SECUENCIAL. *

001000* *

001100******************************************************************

001200*

001300 ENVIRONMENT DIVISION.

001400**********************

001500 CONFIGURATION SECTION.

001600*----------------------

001700 SOURCE-COMPUTER. IBM-4331.

001800 OBJECT-COMPUTER. IBM-4331.

001900*

002000 INPUT-OUTPUT SECTION.

002100*---------------------

002200*

002300 FILE-CONTROL.

002400*

002500 SELECT SALIDA ASSIGN TO S-SALIDA

002600 ORGANIZATION IS SEQUENTIAL

002700 ACCESS MODE IS SEQUENTIAL

002800 FILE STATUS IS FS-SALIDA.

002900*

003000 DATA DIVISION.

003100***************

003200*

003300 FILE SECTION.

003400*-------------

003500*

003600 FD SALIDA

003700 BLOCK 0 RECORDS

003800 LABEL RECORD STANDARD.

003900*

004000 01 REG-SALIDA.

004100 02 FILLER PIC X(80).

004200*

004300 WORKING-STORAGE SECTION.

004400/*****************************************************************

004500****** WORKING ESPECIFICA DEL PROGRAMA ******

004600******************************************************************

004700*

004800 77 WRETORNO PIC S9(4) COMP VALUE +0.

004900 77 SALIDA-ABIERTO PIC XX VALUE 'NO'.

005000 77 FS-SALIDA PIC XX VALUE '00'.

005100*

005200 01 WFECHA.

005300 05 WDIA PIC 99 VALUE ZEROS.

005400 05 WMES PIC 99 VALUE ZEROS.

005500 05 WAAAA PIC 99 VALUE ZEROS.

005600*

005700 01 WREGISTRO-SALIDA.

005800 05 FILLER PIC 9 VALUE 0.

005900 05 SIGLO-SALIDA PIC 99 VALUE ZEROS.

006000 05 FECHA-SALIDA.

006100 10 AAAA-SALIDA PIC 99 VALUE ZEROS.

006200 10 MES-SALIDA PIC 99 VALUE ZEROS.

006300 10 DIA-SALIDA PIC 99 VALUE ZEROS.

006400 05 HORA-SALIDA PIC 9(6) VALUE ZEROS.

006500*

006600*

006700*---> INCLUDE DEL AREA DE COMUNICACION COMUN

006800**** EXPANSION DE /INCLUDEC ZTBGCCOM

006900*---------------------------------------------------------------*

007000* AREA DE COMUNICACION COMUN PARA CONVERSORES.

007100* CONTIENE EL REGISTRO DE PREFILES DE LA IGA

007200* Y EL REGISTRO DE PREFILES DE EDITRAN.

007300*

007400*

007500*

007600* 23-3-93

007700* LA LONGITUD TOTAL DEL AREA = 10400 BYTES.

007800*---------------------------------------------------------------*

007900*

EDITRAN/G 5.2 53


008000 01 AREA-COMUN.

008100*

008200**** EXPANSION DE /INCLUDEC ZTBGCRPE

008300******************************************************************

008400* IGA 3.0 *

008500* CONTIENE LA PARTE DE DATOS DE LOS PERFILES DE LA IGA. *

008600* EL NIVEL 01 DEL REGISTRO ESTA EN EL LIBRO (LWREGIGA). *

008700******************************************************************

008800*

008900 03 REGISTRO-PERFILES-IGA.

009000 05 CLAVE-PERFIGA.

009100 10 PREFIJO PIC X.

009200 10 SESION.

009300 12 CODIGO-LOCAL PIC X(9).

009400 12 CODIGO-REMOTO PIC X(9).

009500 12 APLICACION PIC X(6).

009600 10 NUMERO-ORDEN PIC X(2).

009700 05 REGISTRO-PERFIGA PIC X(2973).

009800*

009900* PREFIJO DEL REG. ENTORNO: E. RESTO DE LA CLAVE A CEROS

010000*

010100 05 ENTORNO-IGA REDEFINES REGISTRO-PERFIGA.

010200 10 CODIGO-LOCAL-IGA-ENTORNO PIC X(9).

010300 10 VERSION-IGA-LOCAL-ENTORNO PIC X(4).

010400 10 VERSION-EDITRAN-LOCAL-ENTORNO PIC X(4).

010500 10 PREFIJO-INSTALACION-ENTORNO PIC X(44).

010600 10 MONITOR-ENTORNO PIC X(4).

010700 10 TIPO-UNIDAD-ENTORNO PIC X(8).

010800 10 LOG-ENTORNO PIC X(1).

010900 10 PROC-PREV-EMISION-ENTORNO PIC X(8).

011000 10 PROC-PREV-RECEPCION-ENTORNO PIC X(8).

011100 10 PROC-POST-EMISION-ENTORNO PIC X(8).

011200 10 PROC-POST-RECEPCION-ENTORNO PIC X(8).

011300 10 PROC-EXCEPCION-ENTORNO PIC X(8).

011400 10 FICHA-JOB-ENTORNO.

011500 12 LINEA-JOB-ENTORNO OCCURS 5 PIC X(59).

011600 10 PROC-ESTADOS-ENTORNO PIC X(8).

011700 10 NOMBRE-ENTORNO PIC X(20).

011800 10 FILLER PIC X(2536).

011900*

012000*

012100* PREFIJO DEL REG. SUBENTORNO: E. RESTO DE LA CLAVE A CEROS

012200*

012300 05 SUBENTORNO-IGA REDEFINES REGISTRO-PERFIGA.

012400 10 DESCRIPCION-SUBENTORNO PIC X(44).

012500 10 FILLER PIC X(2929).

012600*

012700* PREFIJO DEL REG. REMOTO : R

012800*

012900 05 C-REMOTO-IGA REDEFINES REGISTRO-PERFIGA.

013000 10 DESCRIPCION-REMOTO PIC X(20).

013100 10 VERSION-IGA-REMOTO PIC X(4).

013200 10 ASCII-EBCDIC-REMOTO PIC X.

013300 10 COMPRESION-REMOTO PIC X.

013400 10 CRIPTOGRAFIA-REMOTO PIC X.

013500 10 CRC-REMOTO PIC X.

013600 10 ALGORITMO-CONF-REMOTO PIC X(4).

013700 10 ALGORITMO-AUT-REMOTO PIC X(4).

013800 10 INTERFAZ-CLAVES-REMOTO PIC X(8).

013900 10 PARAMETROS-REMOTO PIC X(30).

014000 10 CLAVE-LOC-REMOTO PIC X(64).

014100 10 CLAVE-REM-REMOTO PIC X(64).

014200 10 FILLER PIC X(2771).

014300*

014400* PREFIJO DEL REG. APLICACION: A

014500*

014600 05 APLICACION-IGA REDEFINES REGISTRO-PERFIGA.

014700 10 DESCRIPCION-APLICACION PIC X(20).

014800 10 CONVERSOR1-EMI-APLICACION PIC X(8).

014900 10 CONVERSOR2-REC-APLICACION PIC X(8).

015000 10 CONVERSOR3-EMI-APLICACION PIC X(8).

015100 10 CONVERSOR4-REC-APLICACION PIC X(8).

015200 10 PROG-PREVIO-EMI-APLICACION PIC X(8).

015300 10 PROG-PREVIO-REC-APLICACION PIC X(8).

015400 10 PROG-POST-EMI-APLICACION PIC X(8).

015500 10 PROG-POST-REC-APLICACION PIC X(8).

015600 10 PROG-EXCEPCION-APLICACION PIC X(8).

015700 10 TRADUCCION-A-E-APLICACION PIC X.

015800 10 BORRAR-F-E-APLICACION PIC X.

EDITRAN/G 5.2 54


015900 10 BORRAR-F-R-APLICACION PIC X.

016000 10 CRITERIO-DIVISION-APLICACION PIC X(2).

016100 10 PARAMETRO-APLICACION PIC X(60).

016200 10 TIPO-CARGA-APLICACION PIC X(01).

016300 10 TIPO-DESCARGA-APLICACION PIC X(01).

016400 10 EXIT-PREV-EMI-ANT-APLICACION PIC X(8).

016500 10 EXIT-PREV-EMI-POS-APLICACION PIC X(8).

016600 10 EXIT-POST-REC-ANT-APLICACION PIC X(8).

016700 10 EXIT-POST-REC-POS-APLICACION PIC X(8).

008500 10 EXIT-POST-REC-POS-APLICACION PIC X(8).

008600 10 LENG-DATOS-ORG-APLICACION PIC X.

008700 10 TRAD-REC-APLICACION PIC X.

008800 10 TABLA-CONV-EMI-APLICACION PIC X(8).

016800 10 FILLER PIC X(2764).

016900*

017000* PREFIJO DEL REG. SESION PRESENTACION: P

017100*

017200 05 SESION-IGA REDEFINES REGISTRO-PERFIGA.

017300 07 PARAM-ENTORNO PIC X(500).

017400 07 FILLER REDEFINES PARAM-ENTORNO.

017500 10 CODIGO-LOCAL-IGA-SESION PIC X(9).

017600 10 VERSION-IGA-LOCAL-SESION PIC X(4).

017700 10 VERSION-EDITRAN-LOCAL-SESION PIC X(4).

017800 10 PREFIJO-INSTALACION-SESION PIC X(44).

017900 10 MONITOR-SESION PIC X(4).

018000 10 TIPO-UNIDAD-SESION PIC X(8).

018100 10 LOG-SESION PIC X(1).

018200 10 PROC-PREV-EMISION-SESION PIC X(8).

018300 10 PROC-PREV-RECEPCION-SESION PIC X(8).

018400 10 PROC-POST-EMISION-SESION PIC X(8).

018500 10 PROC-POST-RECEPCION-SESION PIC X(8).

018600 10 PROC-EXCEPCION-SESION PIC X(8).

018700 10 FICHA-JOB-SESION.

018800 12 LINEA-JOB-SESION OCCURS 5 PIC X(59).

018900 10 PROC-ESTADOS-SESION PIC X(8).

019000 10 NOMBRE-ENT-SUBENTORNO-SESION PIC X(20).

019100 10 FILLER PIC X(63).

019200 07 FILLER PIC X(250).

019300 07 PARAM-REMOTO PIC X(212).

019400 07 FILLER REDEFINES PARAM-REMOTO.

019500 10 DESCRIPCION-REMOTO-SESION PIC X(20).

019600 10 VERSION-IGA-SESION PIC X(4).

019700 10 ASCII-EBCDIC-SESION PIC X.

019800 10 COMPRESION-SESION PIC X.

019900 10 CRIPTOGRAFIA-SESION PIC X.

020000 10 CRC-SESION PIC X.

020100 10 ALGORITMO-CONF-SESION PIC X(4).

020200 10 ALGORITMO-AUT-SESION PIC X(4).

020300 10 INTERFAZ-CLAVES-SESION PIC X(8).

020400 10 PARAMETROS-SESION PIC X(30).

020500 10 CLAVE-LOC-SESION PIC X(64).

020600 10 CLAVE-REM-SESION PIC X(64).

020700 10 FILLER PIC X(10).

020800 07 FILLER PIC X(250).

020900 07 PARAM-APLICACION PIC X(250).

021000 07 FILLER REDEFINES PARAM-APLICACION.

021100 10 DESCRIPCION-APL-SESION PIC X(20).

021200 10 CONVERSOR1-EMI-APL-SESION PIC X(8).

021300 10 CONVERSOR2-REC-APL-SESION PIC X(8).

021400 10 CONVERSOR3-EMI-APL-SESION PIC X(8).

021500 10 CONVERSOR4-REC-APL-SESION PIC X(8).

021600 10 PROG-PREVIO-EMI-APL-SESION PIC X(8).

021700 10 PROG-PREVIO-REC-APL-SESION PIC X(8).

021800 10 PROG-POST-EMI-APL-SESION PIC X(8).

021900 10 PROG-POST-REC-APL-SESION PIC X(8).

022000 10 PROG-EXCEPCION-APL-SESION PIC X(8).

022100 10 TRADUCCION-A-E-APL-SESION PIC X.

022200 10 BORRAR-F-E-APL-SESION PIC X.

022300 10 BORRAR-F-R-APL-SESION PIC X.

022400 10 CRITERIO-DIVISION-APL-SESION PIC X(2).

022500 10 PARAMETRO-APL-SESION PIC X(60).

022600 10 TIPO-CARGA-APL-SESION PIC X(1).

022700 10 TIPO-DESCARGA-APL-SESION PIC X(1).

022800 10 EXIT-PREV-EMI-ANT-APL-SESION PIC X(8).

022900 10 EXIT-PREV-EMI-POS-APL-SESION PIC X(8).

023000 10 EXIT-POST-REC-ANT-APL-SESION PIC X(8).

023100 10 EXIT-POST-REC-POS-APL-SESION PIC X(8).

015400 10 LENG-DATOS-ORG-APL-SESION PIC X(01).

015500 10 TRAD-REC-APL-SESION PIC X(01).

EDITRAN/G 5.2 55


015600 10 TABLA-CONV-EMI-APL-SESION PIC X(08).

015700 10 TABLA-CONV-REC-APL-SESION PIC X(08).

015800 10 FILLER PIC X(41).

023300 07 FILLER PIC X(250).

023400 07 PARAM-PRESENTACION PIC X(1000).

023500 07 FILLER REDEFINES PARAM-PRESENTACION.

023600 10 DESCRIPCION-SESION PIC X(20).

023700 10 NUMERO-SESIONES-TRANSMISION PIC 99.

023800 10 TABLA-SESIONES.

023900 12 ELEMENTO OCCURS 20.

024000 14 SESION-TRANSMISION.

024100 16 REMOTO-TRANSMISION PIC X(9).

024200 16 APLICA-TRANSMISION PIC X(6).

024300 14 VOLUMEN-FICHERO-TAMPON PIC X(8).

024400 14 NUMERO-REGISTROS-TAMPON PIC 9(5).

024500 10 TABLA-FICHEROS-RECEPCION.

024600 12 ELEMENTO2 OCCURS 5.

024700 14 NOMBRE-FISICO-R PIC X(44).

024800 14 VOLUMEN-R PIC X(8).

024900 14 IDENTIFICADOR-R PIC X(8).

025000 14 LRECL-R PIC 9(5).

025100 10 BORRAR-FA-SI-EXISTE PIC X.

025200 10 VOLSER-O-UNIT PIC X(1).

025300 10 VOLSER-RECEP-V21 PIC X(8).

025400 10 UNIT-DE-VOLSER-V21 PIC X(8).

025500 10 TABLA-UNIT-V20.

025600 12 ELEMENTO3 OCCURS 5.

025700 14 UNIT-DE-VOLSER-V20 PIC X(8).

025800 10 INCREMENTAR-SESION PIC X(1).

018410 10 FORMATO-FICH-DESCARGA PIC X(1).

018420 10 FICHERO-UNICO-RECEPCION PIC X(1).

018500 10 VOLUMEN-POOL-TAMPONES PIC X(1).

018510 10 FILLER PIC X(31).

026000 07 FILLER PIC X(261).

026100*

026200* PREFIJO DEL REG. SESION TRANSMISION : T

026300*

026400 05 SESION-TRANSMISION-IGA REDEFINES REGISTRO-PERFIGA.

026500 10 SESION-ASOCIADA.

026600 15 CODIGO-LOCAL-P PIC X(9).

026700 15 CODIGO-REMOTO-P PIC X(9).

026800 15 APLICACION-P PIC X(6).

026900 10 FILLER PIC X(2949).

027000*

027100* PREFIJO DEL REG. FICHERO DE APLICACION : F

027200*

019900 05 FICHERO-APLICACION-IGA REDEFINES REGISTRO-PERFIGA.

020000 10 NOMBRE-FISICO-E PIC X(44).

020100 10 IDENTIFICADOR-E PIC X(8).

020101 10 FORMATO-FICHERO-E PIC X.

020102 10 LENG-DATOS-ORG-E PIC X.

020103 10 TRAD-EMI-E PIC X.

020110 10 COMPRESION-E PIC X.

020200 10 FILLER PIC X(2917).

027700*

027800**** EXPANSION DE /INCLUDEC ZTBGC004

027900*----------------------------------------------------------------*

028000*-- PARTE DE DATOS DEL PROGRAMA ZTBGB004... *

028100*-- EL NIVEL 01 DE ESTE AREA ESTA EN LA INCLUDE 'LWIGG004. *

028200*

028300* LONGITUD DE LA INCLUDE 4850 BYTES (20/08/97)

028400*-- CODIGOS INFORMATIVOS DE LOS PARAMETOS DE LAS S-T

028500* RDO-LONG-TRANS DESCRIPCION

028600* -------------- ----------------------------------------------

028700* 00 LONGITUDES DE TRANSMISION CORRECTAS

028800* 01 S-T CON LONGITUDES DE TRANSMISION DIFERENTES

028900*

029000* RDO-COMPRESION DESCRIPCION

029100* -------------- ----------------------------------------------

029200* 00 SESIONES DE TRANSMISION SIN COMPRESION

029300* 01 AL MENOS UNA SESION UTILIZA COMPRESION

029400*

029500* RDO-CIFRADO DESCRIPCION

029600* -------------- ----------------------------------------------

029700* 01 S-T CON VERSIONES DE CRIPTOGRAFIA DIFERENTES

029800* 02 VERSIONES DE CRIPTOGRAFIA NO CUMPLIMENTADAS

029900* (TODAS CON ESPACIOS O LOW-VALUES)

030000* 03 VERSION 2.20 SIN CRIPTOGRAFIA

030100* 04 VERSION 2.20 CON AUTENTICACION Y CAMBIO DE

EDITRAN/G 5.2 56


030200* CLAVE

030300*

030400* RDO-TAMPON-E/R DESCRIPCION

030500* -------------- ----------------------------------------------

030600* 01 S-T CON TIPO (M/E) DE TAMPONES (E/R) DISTINTOS

030700* 02 S-T TAMPONES MATRICIALES (E/R) DIFERENTES

030800* 03 TAMPONES DE EMISION NO CONSECUTIVOS

030900* 04 NIGUN TAMPON DE EMISION CUMPLIMENTADO

031000* O ALGUN TAMPON DE RECEPCION NO CUMPLIMENTADO

031100*----------------------------------------------------------------*

031200*

000800 03 RESTO-AREA-ZTBGB004.

000801 05 PROCESO-LLAMANTE-ZTBGB004 PIC X(1).

000810 05 SESION-PRES-ZTBGB004 PIC X(32).

000820 05 LOG-SESION-ZTBGB004 PIC X(01).

000900 05 CODIGO-RDO-ZTBGB004 PIC 9(4).

001000 05 FILE-STATUS-ZTBGB004 PIC X(2).

001010 05 ERRCOD-ZTBGB004 PIC 9(5).

001100 05 TABLA-FICHAS-ZTBGB004.

001200 10 ELEMENTO-FICHA-ZTBGB004 PIC X(59) OCCURS 5.

001300 05 TABLA-SESIONES-ZTBGB004 PIC X(3520).

001400 05 FILLER REDEFINES TABLA-SESIONES-ZTBGB004 OCCURS 20.

001500 10 ELEMENTO-SESION-ZTBGB004.

001600 15 RDO-TRANSMISION-ZTBGB004 PIC 9(4).

001700 15 SESION-TRANSMISION-ZTBGB004.

001800 20 ORIGEN-ZTBGB004 PIC X(9).

001900 20 REMOTO-ZTBGB004 PIC X(9).

002000 20 APLICACION-ZTBGB004 PIC X(6).

002100 15 FICHERO-EMISION-ZTBGB004.

002200 20 LOGICO-EMISION-ZTBGB004 PIC X(7).

002300 20 FISICO-EMISION-ZTBGB004 PIC X(44).

002400 15 FICHERO-RECEPCION-ZTBGB004.

002500 20 LOGICO-RECEPCION-ZTBGB004 PIC X(7).

002600 20 FISICO-RECEPCION-ZTBGB004 PIC X(44).

002700 15 LONGITUD-FICHERO-ZTBGB004 PIC 9(04).

002800 15 VERSION-EDI-REMOTO-ZTBGB004 PIC 9(02).

002810 15 TIPO-TAMPON-EMIS-ZTBGB004 PIC X(1).

002900 15 TIPO-TAMPON-RECEP-ZTBGB004 PIC X(1).

003100 15 COMPRESION-ZTBGB004 PIC X(1).

003200 15 CRIPTOGRAFIA-ZTBGB004 PIC X(1).

003300 15 CAMBIO-CLAVE-ZTBGB004 PIC X(1).

003400 15 CLAVE-EMK-BAJO-AK-ZTBGB004 PIC X(8).

003500 15 CLAVE-TKE-BAJO-EMK-ZTBGB004 PIC X(8).

003600 15 CLAVE-TKR-BAJO-EMK-ZTBGB004 PIC X(8).

003700 15 VERSION-CRIP-ZTBGB004.

003800 17 VERSION-2-CRIP-ZTBGB004 PIC X(2).

003900 17 FILLER PIC X(1).

004000 15 ALGORITMO-CONF-ZTBGB004 PIC X(4).

004100 15 ALGORITMO-AUT-ZTBGB004 PIC X(4).

004200 05 DATOS-ENTORNO-ZTBGB004.

004300 10 NOMBRE-CICS-ZTBGB004 PIC X(08).

004400 10 TRANSACCION-ZTBGB004 PIC X(04).

004410 10 TRANS-EXCI-ZTBGB004 PIC X(04).

004500 * EN PRINCIPIO, VERSION Y CODIGO LOCAL EDITRAN, SON DATOS ENTRADA

004600 10 CODIGO-LOCAL-ZTBGB004 PIC X(09).

004700 10 VERSION-EDITRAN-LOCAL-ZTBGB004 PIC X(4).

004800 10 ALIAS-ENT-SUBENT-ZTBGB004 PIC X(3).

005200 05 DSNAME-ZTBGFEST-ZTBGB004 PIC X(44).

005300 05 LABEL-LOCAL-ZTBGB004 PIC X(8).

005400 05 LABEL-REMOTO-ZTBGB004 PIC X(8).

005500 05 CODIGO-LOCAL-V22-ZTBGB004 PIC 9(6).

005600 05 CODIGO-REMOTO-V22-ZTBGB004 PIC 9(6).

006100 05 NOMBRE-CPU-ZTBGB004 PIC X(8).

006110 05 NETNAME-EXCI-ZTBGB004 PIC X(08).

006200 05 DSNAME-ZTBEFMP-ZTBGB004 PIC X(44).

006300 05 TABLA-SES-INTERNAS-ZTBGB004 PIC X(640).

006400 05 FILLER REDEFINES TABLA-SES-INTERNAS-ZTBGB004 OCCURS 20.

006500 10 SESION-INTERNA-ZTBGB004 PIC X(32).

006600 * CODIGOS DE RESULTADO INFORMATIVOS SOBRE PARAMETROS DE LAS S-T

006610 05 RDO-LONG-TRANS-ZTBGB004 PIC X(2).

006611 05 IND-LONG-TRANS-ZTBGB004 PIC 9(2).

006620 05 RDO-COMPRESION-ZTBGB004 PIC X(2).

006621 05 IND-COMPRESION-ZTBGB004 PIC 9(2).

006630 05 RDO-CIFRADO-ZTBGB004 PIC X(2).

006631 05 IND-CIFRADO-ZTBGB004 PIC 9(2).

006640 05 RDO-TAMPON-E-ZTBGB004 PIC X(2).

006641 05 IND-TAMPON-E-ZTBGB004 PIC 9(2).

006650 05 RDO-TAMPON-R-ZTBGB004 PIC X(2).

006660 05 IND-TAMPON-R-ZTBGB004 PIC 9(2).

EDITRAN/G 5.2 57


006670 05 RDO-JCLS-IGUALES-ZTBGB004 PIC X(2).

006680 05 IND-JCLS-IGUALES-ZTBGB004 PIC 9(2).

006800 05 FILLER PIC X(162).

041200 03 VBLES-PROC-COMUN PIC X(150).

041300 03 FILLER REDEFINES VBLES-PROC-COMUN.

041400 05 NRO-SESION-COMUN PIC 9(4).

05 SENTIDO-COMUN PIC X(1).

041500 05 FILLER PIC X(145).

041600 03 RESTO-AREA-COMUN PIC X(2400).

041700*

038800*---> INCLUDE DEL AREA DE COMUNICACION ESPECIFICA.

038900**** EXPANSION DE /INCLUDEC ZTBGCE40

039000*---------------------------------------------------------------*

039100* AREA ESPECIFICA DEL PROGRAMA DE EXIT. ZTBGBE40.

039200*---------------------------------------------------------------*

039300*

039400 01 AREA-ZTBGBE40.

039500 05 CODIGO-RDO-ZTBGBE40 PIC 9(4).

039600 05 FICHERO-UNICO-ZTBGBE40 PIC X.

039700 05 PRIMER-FICHERO-ZTBGBE40 PIC X.

039800 05 REG-CONTROL-TAMPON-ZTBGBE40.

039900 07 NRO-REG-ENVIADOS-ZTBGBE40 PIC 9(12).

040000 07 NRO-REG-TOTALES-ZTBGBE40 PIC 9(12).

040100 07 NRO-REG-CONFIRMADOS-ZTBGBE40 PIC 9(12).

040200 07 TRANSMITIDO-COMPL-ZTBGBE40 PIC X.

040300 07 CODIGO-RESULTADO-ZTBGBE40 PIC XX.

040400 07 FECHA-TRANSMISION-ZTBGBE40 PIC 9(6).

040500 07 HORA-TRANSMISION-ZTBGBE40 PIC 9(6).

040600 07 FECHA-ULT-CONF-ZTBGBE40 PIC 9(6).

040700 07 HORA-ULT-CONF-ZTBGBE40 PIC 9(6).

040800 07 EST-ZTBGBE40 PIC X.

040900 07 FECHA-CREACION-ZTBGBE40 PIC 9(6).

041000 07 HORA-CREACION-ZTBGBE40 PIC 9(6).

041100 07 FECHA-ULT-INSERCION-ZTBGBE40 PIC 9(6).

041200 07 HORA-ULT-INSERCION-ZTBGBE40 PIC 9(6).

041300 07 CLAVE-ULTREG-ENV-ZTBGBE40 PIC 9(12).

041400 07 CLAVE-ULTREG-CON-ZTBGBE40 PIC 9(12).

041500 07 CLAVE-ULTREG-INT-ZTBGBE40 PIC 9(12).

041600 07 SIGLO-TRANSMISION-ZTBGBE40 PIC X(2).

041700 07 SIGLO-ULT-CONF-ZTBGBE40 PIC X(2).

041800 07 SIGLO-CREACION-ZTBGBE40 PIC X(2).

041900 07 SIGLO-ULT-INSERCION-ZTBGBE40 PIC X(2).

042000 07 FILLER PIC X(18).

042100*

042200*

042300 LINKAGE SECTION.

042400*----------------

042500*

042600 01 AREA-ENTRADA PIC X(10400).

042700*

042800*

042900 PROCEDURE DIVISION USING AREA-ENTRADA.

043000***************************************

043100*

043200 N1-P-PROGRAMA.

043300*--------------

043400*

043500 MOVE AREA-ENTRADA TO AREA-COMUN.

043600 MOVE RESTO-AREA-COMUN TO AREA-ZTBGBE40.

043700 MOVE ZEROS TO CODIGO-RDO-ZTBGBE40

043800 WRETORNO.

043900*

044000 IF ( FICHERO-UNICO-ZTBGBE40 = 'S' AND

044100 PRIMER-FICHERO-ZTBGBE40 = 'S' ) OR

044200 FICHERO-UNICO-ZTBGBE40 = 'N'

044300*

044400 PERFORM N2-P-10-ABRIR-FICHEROS

044500 THRU N2-F-10-ABRIR-FICHEROS

044600*

044700 IF WRETORNO = 0

044800 PERFORM N2-P-20-PROCESO

044900 THRU N2-F-20-PROCESO

045000 PERFORM N2-P-30-CERRAR-FICHEROS

045100 THRU N2-F-30-CERRAR-FICHEROS

045200 ELSE

045300 PERFORM N2-P-30-CERRAR-FICHEROS

045400 THRU N2-F-30-CERRAR-FICHEROS.

045500*

045600 MOVE WRETORNO TO CODIGO-RDO-ZTBGBE40.

EDITRAN/G 5.2 58


045700 MOVE AREA-ZTBGBE40 TO RESTO-AREA-COMUN.

045800 MOVE AREA-COMUN TO AREA-ENTRADA.

045900*

046000 N1-F-PROGRAMA.

046100*--------------

046200 GOBACK.

046300*

046400/*****************************************************************

046500****** - NIVEL 2 - ******

046600******************************************************************

046700*

046800*

046900 N2-P-10-ABRIR-FICHEROS.

047000*-----------------------

047100*

047200* -----> ABRE EL FICHERO DE APLICACION.

047300*

047400 OPEN OUTPUT SALIDA.

047500 IF FS-SALIDA NOT = '00'

047600 MOVE 12 TO WRETORNO

047700 DISPLAY '* ZTBGBE40 - ERROR OPEN OUTPUT DE SALIDA. FILE

047800- 'STATUS: ' FS-SALIDA

047900 ELSE

048000 MOVE 'SI' TO SALIDA-ABIERTO.

048100*

048200 N2-F-10-ABRIR-FICHEROS.

048300*-----------------------

048400 EXIT.

048500*

048600*

048700*

048800 N2-P-20-PROCESO.

048900*-----------------

049000*

049100* ---> MUEVE LOS CAMPOS AL REGISTRO DEL FICHERO DE APLICACION

049200*

049300 PERFORM N3-P-MOVER-DATOS-SALIDA

049400 THRU N3-F-MOVER-DATOS-SALIDA

049500*

049600* ---> ACTUALIZA EL FICHERO DE APLICACION

049700*

049800 PERFORM N3-P-ACTUALIZAR-SALIDA

049900 THRU N3-F-ACTUALIZAR-SALIDA.

050000*

050100 N2-F-20-PROCESO.

050200*-----------------

050300 EXIT.

050400*

050500*

050600 N2-P-30-CERRAR-FICHEROS.

050700*-----------------------

050800*

050900* ---- SI HA PODIDO ABRIR EL FICHERO DE APLICACION LO CIERRA.

051000*

051100 IF SALIDA-ABIERTO = 'SI'

051200 CLOSE SALIDA


051400 IF WRETORNO = 0


051600 DISPLAY '* ZTBGBE40 - ERROR CLOSE DE SALIDA. FILE S

051700- 'TATUS: ' FS-SALIDA

051800 ELSE

051900 NEXT SENTENCE

052000 ELSE

052100 NEXT SENTENCE.

052200*

052300 N2-F-30-CERRAR-FICHEROS.

052400*-----------------------

052500 EXIT.

052600*

052700/*****************************************************************

052800****** - NIVEL 3 - ******

052900******************************************************************

053000*

053100 N3-P-MOVER-DATOS-SALIDA.

053200*-------------------------*

053300*

053400* ---- SE MUEVEN LOS CAMPOS :

053500* ---- FECHA-ULT-CONFIRMACION-TAMPON

EDITRAN/G 5.2 59


053600* ---- HORA-ULT-CONFIRMACION-TAMPON

053700* ---- AL AREA PARA FORMAR EL REGISTO DEL FICHERO DE APLICACION

053800* ---- CON EL SIGUIENTE FORMATO '0AAAAMMDDHHMISS'

053900*

054000 MOVE FECHA-ULT-CONF-ZTBGBE40 TO WFECHA.

054100 MOVE SIGLO-ULT-CONF-ZTBGBE40 TO SIGLO-SALIDA.

054200 MOVE WAAAA TO AAAA-SALIDA.

054300 MOVE WMES TO MES-SALIDA.

054400 MOVE WDIA TO DIA-SALIDA.

054500 MOVE HORA-ULT-CONF-ZTBGBE40 TO HORA-SALIDA.

054600*

054700 IF (WFECHA IS NOT NUMERIC) OR

054800 (WFECHA = ZEROS)

054900 MOVE ZEROS TO SIGLO-SALIDA

055000 ELSE

055100 IF (SIGLO-SALIDA = SPACES OR LOW-VALUES OR ZEROS) OR

055200 (SIGLO-SALIDA IS NOT NUMERIC)

055300 IF AAAA-SALIDA < 95

055400 MOVE 20 TO SIGLO-SALIDA

055500 ELSE

055600 MOVE 19 TO SIGLO-SALIDA.

055700*

055800 N3-F-MOVER-DATOS-SALIDA.

055900*-------------------------*

056000 EXIT.

056100*

056200*

056300 N3-P-ACTUALIZAR-SALIDA.

056400*------------------------

056500*

056600*--- ESCRIBE EL REGISTRO EN EL FICHERO DE APLICACION.

056700*

056800 WRITE REG-SALIDA FROM WREGISTRO-SALIDA.

056900*



057200 DISPLAY '* ZTBGBE40 - ERROR EN WRITE DE SALIDA. FILE STA

057300- 'TUS: ' FS-SALIDA

057400 ELSE

057500 NEXT SENTENCE.

057600*

057700 N3-F-ACTUALIZAR-SALIDA.

057800*-----------------------

057900 EXIT.

058000*

EDITRAN/G 5.2 60

8.ANNEX C. MACRO FILES

8. ANNEX C. MACRO FILES

8.1. DETAIL OF THE MACRO FILE PROCESS

8.1.1. GENERALIZATIONS.

As we have already said, a macro file contains data that can be loaded in different

presentation sessions depending on an identifier, included in all the records, which determines

which specific session they are associated to.

To define this identifier, the "Parameters" field has been added to the Application and

Presentation Session profiles. This field, with a maximum of 60 characters, consists of the

following data:

Separator value: 1 character.

Start of the identifier field: 1 to 6 digits.

Separator: 1 character.

Length of the identifier field: 1 to 2 digits.


Value of the identifier field: 0 to 48 characters.


Start of the data field to upload: 1 to 6 digits.


Length of the data field to upload: 1 to 6 digits.


If we use in all the data their maximum lengths, they would not fit into the 60 characters

of "Parameters". However, this is highly unlikely to happen in practice.

The example below can conveniently illustrate these concepts:

*7*12*XXX/FACTURAS*54*162*

According to this value, the positions 54 to 215 (162) of the records with XXX/INVOICES in

positions 7 to 18 (12) would be selected to be loaded in the presentation session in whose

profile it is specified. The identifier field can be embedded in the data field to be loaded.

The macro file process is performed by the ZTBGPMCR procedure in installation, which

invokes the program ZTBGBMCR, and contains all the DDs of the usual EDITRAN/G procedures

plus those of ZTBGFMAC, the macro file to be processed, ZTBGFSES, list of sessions to be

loaded, and ZTBGFERR, list of sessions not loaded or with errors. It can receive a PARM with

Xnn....... where nn=01 or 51 only for load, and 03 or 53 for transmission that would normally

include the associated load. With 01 and 03 the application file will be deleted after loading,

while with 51 or 53 it will be kept.

It is possible to upload and/or to send one or more presentation sessions as described

below. In any case, for a particular session, the corresponding records are selected from the

macro file according to the "Parameters" field, and saved in the transmission application file

specified in the session profile that must be unique. From this point on, the macro file process

invokes the standard before the transmission of EDITRAN/G.

EDITRAN/G 5.2 61


The transmission application sequential file is automatically reserved before the macro file

records are selected and, if option 01 or 03 are selected, it is deleted after the loading or after

the standard process before EDITRAN/G transmission has finished and the control has

returned to the macro file process.

The macro file process can use any operating mode of EDITRAN/G. It is not allowed with

cumulative uploads.

8.1.2. PROCESS OF ONLY ONE PRESENTATION SESSION.

It can be performed as follows:

From EDITRAN/P, for which the ZTBGPMCR procedure must be specified as a

procedure before transmission in the transmission session profile.

From the interactive or batch EDITRAN/G operator, for which the ZTBGPMCR

procedure must be specified in the presentation session profile and an upload (01) or

a transmission (03) shall be requested.

From the ZTBGJMJMCR JCL which invokes the ZTBGPMCR procedure by setting the

PARM "Annlllllllllrrrrrrrrraaaaaa" where nn=01 or 51 (load), or 03 or 53 (transmission)

and lllllllllrrrrrrrrraaaaaa being the presentation session. In this case, the session list

file ZTBGFSES is not used.

The process is as follows:

Depending on the case, through the transmission or presentation session, we access

the profile of the latter, and we take and validate the “Parameters” and “Transmission

application file” fields. The last one should be unique.

The presentation session process is as follows:

If the session is in a load-compatible status, i. e., it is finished or not loaded, the

macro file is tracked until finding a record that meets the identifier contained in

"Parameters", whose part of data to be loaded is recorded in the transmission

application file. The same will be performed with the subsequent records, until

finding one of them that does not comply it. If no record is found, an empty file

is generated.

If it was not possible to load the session because it is in a non-compatible

status (e.g., it is sending) it will be notified with the corresponding result code.

If transmission or upload were requested and this one could be carried out, the

main program before EDITRAN/G transmission is invoked and it performs the

conventional process of load and/or transmission. Upon completion, the control

is returned to the macro file process that deletes or catalogues the transmission

application file according to the selected option.

If its upload was requested and it was not carried out, the previous program is

not invoked.

If there was an error, the JCL will get the corresponding code. If there is no error, but

the session wasn’t uploaded, it will get the code 04.

8.1.3. PROCESS OF SEVERAL PRESENTATION SESSIONS.

It can only be performed from the ZTBGJMCR JCL which invokes the ZTBGPMCR procedure

by setting the PARM "Ann " being nn=01 or 51 (load), or 03 or 53

(transmission) followed by 24 blank spaces.

EDITRAN/G 5.2 62


The sessions to be uploaded and/or sent are taken from the ZTBGFSES file, record length

80, so you can create with an editor, which contains a presentation session to be processed in

the first 24 positions of each record. The list of presentation sessions should be in the same

order as the different data portions associated with the macro file. The data of a session must

create a single set of contiguous records. If the data are in a different order than the

sessions, it is not guaranteed that all the sessions are uploaded, since the macro file is

tracked sequentially, according to the order of the list. If it is known that there are no data in

the macro file for any session, it is recommended to remove it from the session list to avoid

reading the entire file.


A presentation session is taken from the ZTBGFSES file. We access its profile, and we

take and validate the “Parameters” and “Transmission application file” fields. The last

one should be unique.

The process of a presentation session described above is performed. If the session

could not be loaded or an error occurred during the process, apart from reporting it, it

will be included in the session list with error ZTBGFERR.

A new presentation session of ZTBGFSES is taken and it is processed again until the

list of sessions is completed. Note that the macro file is not tracked from the

beginning for each session by searching for corresponding records, but it is the object

of a single reading in sequence, hence the importance that the records associated

with each session are arranged, in the macro file, in the same order as the ZTBGFSES

sessions, as mentioned above.

The macro file process is not interrupted if an error occurs during the processing of a

session. If more than one error occurs, the first one prevails, and the JCL ends with

that code. If no error occurs, but some session was not loaded, it ends with code 04.

The ZTBGFERR file will contain the sessions with error or not uploaded.

8.2. GENERIC INITIALIZATION OF TRANSMISSION STATUSES.

8.2.1. GENERALIZATIONS.

The macro file process can also be used to unconditionally initialize the transmission status

of a session list. The result will be equivalent to the status initialization made from option 2.1

of the operator menu or through the JCL of status modification.

8.2.2. INITIALIZATION PROCESS.

This is carried out from the ZTBGJMCR JCL which invokes the ZTBGPMCR procedure by

setting the PARM "Ann " being nn=10 (start transmission) followed by 24

blank spaces.

The sessions to be processed are taken from the ZTBGFSES file, record length 80, so it can

be created with an editor, which contains in the first 24 positions of each record a

presentation session to be processed.


A presentation session is taken from the ZTBGFSES file, accessing its profile and

validating its status.

EDITRAN/G 5.2 63


The status modification process for the session is carried out by calling the standard

program ZTBGB160 with the input parameters E9990001 (unconditional

modification of transmission statuses with session number 1) as the ZTBGJ6 JCL

would do it.

A new presentation session of ZTBGFSES is taken and it is processed again until the

list of sessions is completed.

The macro file process is not interrupted if an error occurs during the processing of a

session. If more than one error occurs, the first one prevails, and the JCL ends with that code.

EDITRAN/G 5.2 64

9.ANNEX D. GENERATIONAL FILES

9. ANNEX D. GENERATIONAL FILES

EDITRAN/G incorporates the facility to use generational files of transmission and/or

reception.

For this, define these files in the EDITRAN/G profiles as specified below:

9.1. GENERATION FILES OF TRANSMISSION APPLICATION

The DSN corresponding to the generation group will be specified as transmission

application file. If nothing else is specified or if zero is added in brackets, "DSN (0)", the most

modern generation file will be sent. If we want to send a previous generation, "DSN(-n)” will

be specified, being "n" the difference between the last generation and the one we want to

send.

The specification of the physical name of the transmission generation files is the same.

9.2. GENERATION FILES OF RECEPTION APPLICATION

If we want the received files to remain as generation files, we must indicate the reception

file not to be deleted, if it exists. (Borrar_si_existe = "N").

In order to keep the received files in a generation group, the DSN of the generation group

to which "(+n)" is added is defined in the place corresponding to the reception file, being n

from 1 to 255, i. e., "DSN(+1)", for example.

Depending on whether it is received in a single file (single file in reception) one or several

generations may be created in the same download, to host the files received.

9.2.1. IMPORTANT NOTE

It is important to note that if the profile parameter "Borrar_si_existe" has the value "S" and

the DSN of the generation group without parentheses is specified instead of the single file,

EDITRAN/G assumes that it is a non-generation file, and therefore, all the group

generations are deleted along with their definition. In this case, when trying to catalog

the reception file created in the process, an error is detected and recorded in the LOG by

EDITRAN/G, with the message "ZTG0182. - Possible error in profile definition: generation file".

Obviously, the generation group model has to be in line with the characteristics of the

received files.

EDITRAN/G 5.2 65

10.ANNEX F. TABLES (TRANSLATION AND CONVERSION)

10. ANNEX F. TABLES (TRANSLATION AND CONVERSION)

Depending on the EDITRAN version installed or the node version, different translation

tables are applied. The first node translated is the one that imposes the table to use. There

are different cases:

1. If the node that translates is CICS or IMS and it has version 5.0 phase 2 or higher, or if the

node that translates is any other environment and it has version 5.0 phase 0 or higher, a

translation table is applied based on Codepage 1145 EBCDIC Spanish and ASCII ISO 8859

Latin-1.

The EBCDIC translation into ASCII (between Codepage 1145 ebcdic Spanish and ASCII ISO

8859 Latin-1) is the following (example in bold, character x’FA’ EBCDIC becomes character

x’B3’ in ASCII):

| x0| x1| x2| x3| x4| x5| x6| x7| x8| x9| xA| xB| xC| xD| xE| xF|

0x|x00|x01|x02|x03|x9C|x09|x86|x7F|x97|x8D|x8E|x0B|x0C|x0D|x0E|x0F|

1x|x10|x11|x12|x13|x9D|x85|x08|x87|x18|x19|x92|x8F|x1C|x1D|x1E|x1F|

2x|x80|x81|x82|x83|x84|x0A|x17|x1B|x88|x89|x8A|x8B|x8C|x05|x06|x07|

3x|x90|x91|x16|x93|x94|x95|x96|x04|x98|x99|x9A|x9B|x14|x15|x9E|x1A|

4x|x20|xA0|xE2|xE4|xE0|xE1|xE3|xE5|xE7|xA6|x5B|x2E|x3C|x28|x2B|x7C|

5x|x26|xE9|xEA|xEB|xE8|xED|xEE|xEF|xEC|xDF|x5D|x24|x2A|x29|x3B|xAC|

6x|x2D|x2F|xC2|xC4|xC0|xC1|xC3|xC5|xC7|x23|xF1|x2C|x25|x5F|x3E|x3F|

7x|xF8|xC9|xCA|xCB|xC8|xCD|xCE|xCF|xCC|x60|x3A|xD1|x40|x27|x3D|x22|

8x|xD8|x61|x62|x63|x64|x65|x66|x67|x68|x69|xAB|xBB|xF0|xFD|xFE|xB1|

9x|xB0|x6A|x6B|x6C|x6D|x6E|x6F|x70|x71|x72|xAA|xBA|xE6|xB8|xC6|xA4|

Ax|xB5|xA8|x73|x74|x75|x76|x77|x78|x79|x7A|xA1|xBF|xD0|xDD|xDE|xAE|

Bx|xA2|xA3|xA5|xB7|xA9|xA7|xB6|xBC|xBD|xBE|x5E|x21|xAF|x7E|xB4|xD7|

Cx|x7B|x41|x42|x43|x44|x45|x46|x47|x48|x49|xAD|xF4|xF6|xF2|xF3|xF5|

Dx|x7D|x4A|x4B|x4C|x4D|x4E|x4F|x50|x51|x52|xB9|xFB|xFC|xF9|xFA|xFF|

Ex|x5C|xF7|x53|x54|x55|x56|x57|x58|x59|x5A|xB2|xD4|xD6|xD2|xD3|xD5|

Fx|x30|x31|x32|x33|x34|x35|x36|x37|x38|x39|xB3|xDB|xDC|xD9|xDA|x9F|

The ASCII translation into EBCDIC (between ASCII ISO 8859 Latin-1 and Codepage 1145

ebcdic Spanish) is as follows (example in bold, character x’BE’ ASCII becomes character x’FA’ in

EBCDICI) :

| x0| x1| x2| x3| x4| x5| x6| x7| x8| x9| xA| xB| xC| xD| xE| xF|

0x|x00|x01|x02|x03|x37|x2D|x2E|x2F|x16|x05|x25|x0B|x0C|x0D|x0E|x0F|

1x|x10|x11|x12|x13|x3C|x3D|x32|x26|x18|x19|x3F|x27|x1C|x1D|x1E|x1F|

2x|x40|xBB|x7F|x69|x5B|x6C|x50|x7D|x4D|x5D|x5C|x4E|x6B|x60|x4B|x61|

3x|xF0|xF1|xF2|xF3|xF4|xF5|xF6|xF7|xF8|xF9|x7A|x5E|x4C|x7E|x6E|x6F|

4x|x7C|xC1|xC2|xC3|xC4|xC5|xC6|xC7|xC8|xC9|xD1|xD2|xD3|xD4|xD5|xD6|

5x|xD7|xD8|xD9|xE2|xE3|xE4|xE5|xE6|xE7|xE8|xE9|x4A|xE0|x5A|xBA|x6D|

6x|x79|x81|x82|x83|x84|x85|x86|x87|x88|x89|x91|x92|x93|x94|x95|x96|

7x|x97|x98|x99|xA2|xA3|xA4|xA5|xA6|xA7|xA8|xA9|xC0|x4F|xD0|xBD|x07|

8x|x20|x21|x22|x23|x24|x15|x06|x17|x28|x29|x2A|x2B|x2C|x09|x0A|x1B|

9x|x30|x31|x1A|x33|x34|x35|x36|x08|x38|x39|x3A|x3B|x04|x14|x3E|xFF|

Ax|x41|xAA|xB0|xB1|x9F|xB2|x49|xB5|xA1|xB4|x9A|x8A|x5F|xCA|xAF|xBC|

Bx|x90|x8F|xEA|xFA|xBE|xA0|xB6|xB3|x9D|xDA|x9B|x8B|xB7|xB8|xB9|xAB|

Cx|x64|x65|x62|x66|x63|x67|x9E|x68|x74|x71|x72|x73|x78|x75|x76|x77|

Dx|xAC|x7B|xED|xEE|xEB|xEF|xEC|xBF|x80|xFD|xFE|xFB|xFC|xAD|xAE|x59|

Ex|x44|x45|x42|x46|x43|x47|x9C|x48|x54|x51|x52|x53|x58|x55|x56|x57|

Fx|x8C|x6A|xCD|xCE|xCB|xCF|xCC|xE1|x70|xDD|xDE|xDB|xDC|x8D|x8E|xDF|

2. If the node that translates has a version lower than 4.0 phase 4, in some cases an

obsolete and non-symmetrical translation table was applied. Those cases were:

2.1. It translated in EDITRAN/G without EDITRAN/G compression

2.2. It translated in EDITRAN/G with EDITRAN/G compression and with remote-iga-version-

< 3.1

2.3. It used EDITRAN/MQ

EDITRAN/G 5.2 66


3. In the other cases (most common in all the entities), an obsolete translation table (of ms-

dos) was applied. In the case of EBCDIC into ASCII (x'FA' by x'FC', different from the table

above, in this and other characters).

x00-x00 x10-x10 x20-xC0 x30-xCC x40-x20 x50-x26 x60-x2D x70-x9B

x01-x01 x11-x11 x21-xC1 x31-xCD x41-xFE x51-x82 x61-x2F x71-x90

x02-x02 x12-x12 x22-xC2 x32-x16 x42-x83 x52-x88 x62-xB6 x72-xD2

x03-x03 x13-x13 x23-xC3 x33-xCE x43-x84 x53-x89 x63-x8E x73-xD3

x04-x9F x14-xB9 x24-xC4 x34-xD5 x44-x85 x54-x8A x64-xB7 x74-xD4

x05-x09 x15-xBA x25-x0A x35-xD9 x45-xA0 x55-xA1 x65-xB5 x75-xD6

x06-xB0 x16-x08 x26-x17 x36-xDA x46-xC6 x56-x8C x66-xC7 x76-xD7

x07-x7F x17-xBB x27-x1B x37-x04 x47-x86 x57-x8B x67-x8F x77-xD8

x08-xB1 x18-x18 x28-xC5 x38-xDB x48-x87 x58-x8D x68-x80 x78-xDE

x09-xB2 x19-x19 x29-xC8 x39-xDC x49-x7C x59-xE1 x69-x23 x79-x60

x0A-xB4 x1A-xBC x2A-xC9 x3A-xDD x4A-x5B x5A-x5D x6A-xA4 x7A-x3A

x0B-x0B x1B-xBF x2B-xCA x3B-xDF x4B-x2E x5B-x24 x6B-x2C x7B-xA5

x0C-x0C x1C-x1C x2C-xCB x3C-x14 x4C-x3C x5C-x2A x6C-x25 x7C-x40

x0D-x0D x1D-x1D x2D-x05 x3D-x15 x4D-x28 x5D-x29 x6D-x5F x7D-x27

x0E-x0E x1E-x1E x2E-x06 x3E-xF2 x4E-x2B x5E-x3B x6E-x3E x7E-x3D

x0F-x0F x1F-x1F x2F-x07 x3F-x1A x4F-xB3 x5F-xAA x6F-x3F x7F-x22

x80-x9D x90-xF8 xA0-xE6 xB0-xBD xC0-x7B xD0-x7D xE0-x5C xF0-x30

x81-x61 x91-x6A xA1-xF9 xB1-x9C xC1-x41 xD1-x4A xE1-xF6 xF1-x31

x82-x62 x92-x6B xA2-x73 xB2-xBE xC2-x42 xD2-x4B xE2-x53 xF2-x32

x83-x63 x93-x6C xA3-x74 xB3-xFA xC3-x43 xD3-x4C xE3-x54 xF3-x33

x84-x64 x94-x6D xA4-x75 xB4-xB8 xC4-x44 xD4-x4D xE4-x55 xF4-x34

x85-x65 x95-x6E xA5-x76 xB5-xF5 xC5-x45 xD5-x4E xE5-x56 xF5-x35

x86-x66 x96-x6F xA6-x77 xB6-xF4 xC6-x46 xD6-x4F xE6-x57 xF6-x36

x87-x67 x97-x70 xA7-x78 xB7-xAC xC7-x47 xD7-x50 xE7-x58 xF7-x37

x88-x68 x98-x71 xA8-x79 xB8-xAB xC8-x48 xD8-x51 xE8-x59 xF8-x38

x89-x69 x99-x72 xA9-x7A xB9-xF3 xC9-x49 xD9-x52 xE9-x5A xF9-x39

x8A-xAE x9A-xA6 xAA-xAD xBA-x5E xCA-xF0 xDA-xFB xEA-xFD xFA-xFC

x8B-xAF x9B-xA7 xAB-xA8 xBB-x21 xCB-x93 xDB-x96 xEB-xE2 xFB-xEA

x8C-xD0 x9C-x91 xAC-xD1 xBC-xEE xCC-x94 xDC-x81 xEC-x99 xFC-x9A

x8D-xEC x9D-xF7 xAD-xED xBD-x7E xCD-x95 xDD-x97 xED-xE3 xFD-xEB

x8E-xE7 x9E-x92 xAE-xE8 xBE-xEF xCE-xA2 xDE-xA3 xEE-xE0 xFE-xE9

x8F-xF1 x9F-xCF xAF-xA9 xBF-x9E xCF-xE4 xDF-x98 xEF-xE5 xFF-xFF

In case of ASCII into EBCDIC (x’FC’ by x’FA’)

x00-x00 x10-x10 x20-x40 x30-xF0 x40-x7C x50-xD7 x60-x79 x70-x97

x01-x01 x11-x11 x21-xBB x31-xF1 x41-xC1 x51-xD8 x61-x81 x71-x98

x02-x02 x12-x12 x22-x7F x32-xF2 x42-xC2 x52-xD9 x62-x82 x72-x99

x03-x03 x13-x13 x23-x69 x33-xF3 x43-xC3 x53-xE2 x63-x83 x73-xA2

x04-x37 x14-x3C x24-x5B x34-xF4 x44-xC4 x54-xE3 x64-x84 x74-xA3

x05-x2D x15-x3D x25-x6C x35-xF5 x45-xC5 x55-xE4 x65-x85 x75-xA4

x06-x2E x16-x32 x26-x50 x36-xF6 x46-xC6 x56-xE5 x66-x86 x76-xA5

x07-x2F x17-x26 x27-x7D x37-xF7 x47-xC7 x57-xE6 x67-x87 x77-xA6

x08-x16 x18-x18 x28-x4D x38-xF8 x48-xC8 x58-xE7 x68-x88 x78-xA7

x09-x05 x19-x19 x29-x5D x39-xF9 x49-xC9 x59-xE8 x69-x89 x79-xA8

x0A-x25 x1A-x3F x2A-x5C x3A-x7A x4A-xD1 x5A-xE9 x6A-x91 x7A-xA9

x0B-x0B x1B-x27 x2B-x4E x3B-x5E x4B-xD2 x5B-x4A x6B-x92 x7B-xC0

x0C-x0C x1C-x1C x2C-x6B x3C-x4C x4C-xD3 x5C-xE0 x6C-x93 x7C-x49

x0D-x0D x1D-x1D x2D-x60 x3D-x7E x4D-xD4 x5D-x5A x6D-x94 x7D-xD0

x0E-x0E x1E-x1E x2E-x4B x3E-x6E x4E-xD5 x5E-xBA x6E-x95 x7E-xBD

x0F-x0F x1F-x1F x2F-x61 x3F-x6F x4F-xD6 x5F-x6D x6F-x96 x7F-x07

x80-x68 x90-x71 xA0-x45 xB0-x06 xC0-x20 xD0-x8C xE0-xEE xF0-xCA

x81-xDC x91-x9C xA1-x55 xB1-x08 xC1-x21 xD1-xAC xE1-x59 xF1-x8F

x82-x51 x92-x9E xA2-xCE xB2-x09 xC2-x22 xD2-x72 xE2-xEB xF2-x3E

x83-x42 x93-xCB xA3-xDE xB3-x4F xC3-x23 xD3-x73 xE3-xED xF3-xB9

x84-x43 x94-xCC xA4-x6A xB4-x0A xC4-x24 xD4-x74 xE4-xCF xF4-xB6

x85-x44 x95-xCD xA5-x7B xB5-x65 xC5-x28 xD5-x34 xE5-xEF xF5-xB5

x86-x47 x96-xDB xA6-x9A xB6-x62 xC6-x46 xD6-x75 xE6-xA0 xF6-xE1

x87-x48 x97-xDD xA7-x9B xB7-x64 xC7-x66 xD7-x76 xE7-x8E xF7-x9D

x88-x52 x98-xDF xA8-xAB xB8-xB4 xC8-x29 xD8-x77 xE8-xAE xF8-x90

x89-x53 x99-xEC xA9-xAF xB9-x14 xC9-x2A xD9-x35 xE9-xFE xF9-xA1

x8A-x54 x9A-xFC xAA-x5F xBA-x15 xCA-x2B xDA-x36 xEA-xFB xFA-xB3

x8B-x57 x9B-x70 xAB-xB8 xBB-x17 xCB-x2C xDB-x38 xEB-xFD xFB-xDA

x8C-x56 x9C-xB1 xAC-xB7 xBC-x1A xCC-x30 xDC-x39 xEC-x8D xFC-xFA

x8D-x58 x9D-x80 xAD-xAA xBD-xB0 xCD-x31 xDD-x3A xED-xAD xFD-xEA

x8E-x63 x9E-xBF xAE-x8A xBE-xB2 xCE-x33 xDE-x78 xEE-xBC xFE-x41

x8F-x67 x9F-x04 xAF-x8B xBF-x1B xCF-x9F xDF-x3B xEF-xBE xFF-xFF

All the translation tables used have the same translation in upper and lower case letters

without accents (except Ñ, ñ). In case of accented or special symbols, the translations change.

EDITRAN/G 5.2 67


In principle, the new translation tables 5.0 (or 5.0.2) are "modern" tables that make the

applications correctly understand (accented and unaccented) letters, numbers and symbols.

Normally, the problems that existed so far are solved with this version:

In transmissions, if the node is an ASCII, it can translate in transmission (in that case,

the modern table will be applied regardless of the EDITRAN version that node has

installed).

In receptions, if the node is an ASCII and it has an EDITRAN version installed lower than

5.0, you can instruct it not to translate (EDITRAN/G profile of the ASCII environment).

You can do it yourself during the download in z/OS (thus, the modern table will be

applied, not the obsolete one of the ASCII environment).

In any case, if the translation table is not valid, you can apply the conversion table (in

transmission or reception), or it can also be applied by the node. In these cases, the characters

that appear or reach the expected characters are adapted. The conversion table should be

applied in reception (once the translation is completed, if any).

In the profiles of EDITRAN/G (presentation session), transmission conversion tables or

reception conversion tables can be included. In this case, a table name of 8 positions is

indicated. How and when are they applied?:

1. In case of transmissions. The conversion table is applied, before the translation (if this

field was also marked). In this case, the loading program:

a. If the original language of the data is EBCDIC, it looks for a 9-position table, whose

name is the combination of the 8-position name specified in the profile and the

letter "E" or "F".

i. If the sender has installed the version 5.0.2 or higher, it looks for the letter

“F”

ii. If the sender has installed a lower version, it looks for the letter “E”

b. If the original language of the data is ASCII, it looks for a 9-position table, whose

name is the combination of the 8-position name specified in the profile and the

letter “A” or “B”.

i. If the sender has installed the version 5.0.2 or higher, it looks for the letter

“B”

ii. If the sender has installed a lower version, it looks for the letter “A”

2. In case of receptions, (the reception node ignores in advance that it is the one the

transmission node has made with the translation).

a. If the reception node has installed a version 5.0.2 or higher. It verifies the remote

EDITRAN version (it is not the one it has in its profile, but the one the node has in

the CSB header).

i. It the node has an EDITRAN installed with version > 4.1

1. If the CSB header indicates that the data received are in EBCDIC, and

in the presentation session profile it has the parameter TRANSLATE

in RECEPTION with the values “E” or “N” (in both cases it is not

EDITRAN/G 5.2 68


translated when downloading). In this case, if it has a conversion

table reception in the presentation profile, it looks for a 9-position

table, whose name is the combination of the 8-position name

specified in the profile and the letter “F”.



in RECEPTION with the value “A” (ASCII), it translates with the new

table specified for its version (5.0.2). Once the translation is

completed, if it has a reception conversion table in the presentation

profile, it looks for a 9-position table, whose name is the combination

of the 8-position name specified in the profile and the letter “B”.

3. If the CSB header indicates that the data received are in ASCII, and in

the presentation session profile it has the parameter TRANSLATE in

RECEPTION with the values “A” or “N” (in both cases it is not




specified in the profile and the letter “B”.



RECEPTION with the value “E” (ebcdic), it translates with the new




of the 8-position name specified in the profile and the letter “F”.

ii. If the node has an EDITRAN installed with a version lower than 5.0



in RECEPTION with the values “E” or “N” (in both cases it is not




specified in the profile and the letter “E”.



in RECEPTION with the value “A” (ASCII), it translates with the new




of the 8-position name specified in the profile and the letter “B”.



RECEPTION with the values “A” or “N” (in both cases it is not




specified in the profile and the letter “A”.

EDITRAN/G 5.2 69




RECEPTION with the value “E” (ebcdic), it translates with the new




of the 8-position name specified in the profile and the letter “F”.

b. If the reception node has installed a version lower than 5.0.2, when it downloads,

one it has translated (or not):

i. If the language of the data downloaded at that time is Ebcdic, if it has a

reception conversion table in the presentation profile, it looks for a 9-

position table, whose name is the combination of the 8-position name

specified in the profile and the letter “E”.

ii. If the language of the data downloaded at that time is ASCII, if it has a

reception conversion table in the presentation profile, it looks for a 9-

position table, whose name is the combination of the 8-position name

specified in the profile and the letter “A”.

EDITRAN/G 5.2 70


Conclusions to the conversion table (if you have installed the version > 5.0.1)

Transmissions

o If there’s a translation, apply the conversion table(s) finished in F or B (new)

o If there’s no translation, apply the conversion table(s) finished in E or A (old)

Receptions

o If translation is applied during reception, or if local v.iga (the one of the node

uploaded) in cab.csb is > 4.1, the finished conversion table(s) will be applied in B

or F (new)

o If no translation is applied, and local v.iga (the one of the node uploaded) in CAB

cabo is < 5.0, the old conversion tables are applied.

The conversion tables are generated from JCL and from a program registered by a specific

table:

//KI0F6AEA JOB (EGDC,KIT,,99),MODP.42-43,MSGCLASS=H,CLASS=A,

// MSGLEVEL=1,NOTIFY=&SYSUID

//*********************************************************************

//** EDITRAN/G (ENTORNO CICS - MVS)

//** JCL DE GENERACION-LISTADO DE TABLAS DE CONVERSION EDITRAN/G

//********************************************************************+

//ZTBGBTCO EXEC PGM=ZTBGBTCO,COND=(0,NE)


// DD DSN=KI.EGDC.ZTBP.LOAD31,DISP=SHR

//ZTBGFTCO DD DSN=KI.PMED.CZTB.ZTBGFTCO,DISP=SHR

//* DCB=(RECFM=FB,LRECL=265,BLKSIZE=0),

//* DISP=(NEW,CATLG,DELETE),

//* SPACE=(TRK,(10,10),RLSE)

//ZTBGFLIS DD SYSOUT=*,DEST=H,DCB=(BLKSIZE=132)



//*******************************************************************

//* FICHA 01 : FF-XXXXXXXXY DONDE:

//* F=FUNCION (00-GRABAR, 01-LISTAR, 02-REESCRIBIR)

//* X=NOMBRE TABLA CONVERSION 8 POSICIONES (PERFIL EDITRAN/G)

//* Y=TIPO DE CONVERSION (A,B,E,F)

//* A=ASCII < 5.0

//* EMISION..: SE APLICA CUANDO TRAD-EMI=N

//* RECEPCION: SE APLICA CUANDO TRAD-REC=N Y V.IGA.REM<50

//* B=ASCII > 5.0

//* EMISION..: SE APLICA CUANDO TRAD-EMI=S

//* RECEPCION: SE APLICA CUANDO TRAD-REC=S O V.IGA.REM>41

//* E=EBCDIC < 5.0

//* EMISION..: SE APLICA CUANDO TRAD-EMI=N

//* RECEPCION: SE APLICA CUANDO TRAD-REC=N Y V.IGA.REM<50

//* F=EBCDIC > 5.0

//* EMISION..: SE APLICA CUANDO TRAD-EMI=S

//* RECEPCION: SE APLICA CUANDO TRAD-REC=S O V.IGA.REM>41

//* RESTO FICHAS: (DESDE 1 A 256 FICHAS)

//* VALOR HEXADECIMAL (00-FF) = NUEVO VALOR HEXA (00-FF)

//* (SI AMBOS COINCIDEN NO HACE FALTA ESPECIFICARLOS)

//*******************************************************************

//FICHAS DD *

//FICHAS DD *

FF-XXXXXXXXY

00=04

01=F4

...

The previous JCL program will read the card records. In the first record it will find the

function (00-record, 01-list, 02-rewrite), the name of the profile conversion table

(XXXXXXXX) and a letter (A/B or E/F), indicating whether it is an ASCII or EBCDIC conversion

table. If the function is 01 it will list the contents of the specified table. If the function is 00,

then it will find the original hexadecimal value and the hexadecimal value to which it is going

EDITRAN/G 5.2 71


to be converted (if both are the same it is not necessary to enter them), so that at the end, it

will save a table with all the values (256 values) with the key specified in the ZTBGFTCO file.

Then, a report will be obtained with the result of the table contents. If the function is 02, it

will rewrite the new characters indicated, and it will keep the characters changed in previous

scripts.

The list that appears with any option is as follows:

NOMBRE DE LA TABLA DE CONVERSION : TABCVXNCA

OBJETO : CONTIENE VALORES : ASCII

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

| ORIGINAL | CONVERTIDA || ORIGINAL | CONVERTIDA || ORIGINAL | CONVERTIDA || ORIGINAL | CONVERTIDA|

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

| X'21' = X'32' || X'23' = X'A5' || X'5E' = X'AA' || X'7C' = X'A4' |

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

| X'80' = X'C0' || X'81' = X'C1' || X'82' = X'C2' || X'83' = X'C3' |

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

| X'84' = X'C4' || X'85' = X'BA' || X'86' = X'B0' || X'87' = X'BB' |

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

And so on, until completing the changing hexadecimal characters.

To avoid problems, we propose the following scheme:

The conversion table is usually applied by the receiver.

The translation is usually applied by the receiver.

As in the version lower than 5.0.2, it will be possible only to create conversion tables

finished in ‘A’ or ‘E’. In 5.0.2 the following is provided:

Software to create tables finished in ‘B’ or ‘F’

Migration programs, which from the conversion tables ALREADY CREATED by the

user, finished in' A' and' E', create new conversion tables finished in' B' or' F' to

avoid as much as possible the user to create them again. If the migration program

detects that the application of a conversion table is not necessary (because the

new translation solves the problem), it removes it from the presentation session.

EDITRAN/G 5.2 72


Example of use:

You have installed EDITRAN 5.0.2 and you want to send, but you know that you see the Ñ

character of your EBCDIC in hexadecimal as x'7B'. The node to which you are sending is an

ASCII that understands the Ñ as an hexadecimal understood as x' 2B'. There are several

solutions to this problem:

If it is translated in transmission, the new translation table is applied; therefore, EBCDIC

x'7B' would be translated by an ASCII x'D1'. The node wouldn't get its long awaited x'2B'.

In this case there are several solutions:

o A transmission conversion table ending in F could be inserted in transmission,

changing the value x'7B' to x'4E'. The translation in later transmission, would

translate x’4E’ into x’2B’ which is the value expected by the node.

o In transmission, do not insert a transmission conversion table. In this case, the node

gets x’D1’. In that download:

If the receiver has a version < 5.0 installed, it could include a reception

conversion table, ending in 'A', which would change x'D1' to x'2B' which is

the value expected by the node.

If the receiver has a version > 4.1 installed, it could include a reception

conversion table, ending in 'B', which would change x'D1' to x'2B' which is

the value expected by the node.

If it is not translated in transmission:

o If the node has installed a version higher than 4.1.

The sender may include a transmission conversion table ending in 'F' that

changes x'7B' to x'4E'. The receiver applies the translation, and it would


The receiver applies the translation x’7B’ by x’D1’, and then it applies a

conversion table ending in ‘B’ that changes x’D1’ by x’2B’ which is the value

expected by the node.

o If the node has installed a version lower than 5.0

The sender may include a transmission conversion table ending in ‘E’

changing x’7B’ by x’4E’. The sender applies the OLD translation, and it would


The receiver applies the translation x’7B’ by x’A5’ with its old translation

table, and then it applies a conversion table ending in ‘A’ that changes x’A5’

by x’2B’ which is the value expected by the node.

EDITRAN/G 5.2 73


Differences between the old and the new translation tables (EBCDIC into ASCII):

Ebcdic CHARACTERS changing from the old to the new table

Ebcdic Asc-

old

Asc-

new

Ebcdic Asc-

old

Asc-

new

Ebcdic Asc-

old

Asc-

new

Ebcdic Asc-

old

Asc-

new

x04 x9F x9C x43 x84 xE4 x77 xD8 xCF xB8 xAB xBD

x06 xB0 x86 x44 x85 xE0 x78 xDE xCC xB9 xF3 xBE

x08 xB1 x97 x45 xA0 xE1 x7B xA5 xD1 xBC xEE xAF

x09 xB2 x8D x46 xC6 xE3 x80 x9D xD8 xBE xEF xB4

x0A xB4 x8E x47 x86 xE5 x8A xAE xAB xBF x9E xD7

x14 xB9 x9D x48 x87 xE7 x8B xAF xBB xCA xF0 xAD

x15 xBA x85 x49 x7C xA6 x8C xD0 xF0 xCB x93 xF4

x17 xBB x87 x4F xB3 x7C x8D xEC xFD xCC x94 xF6

x1A xBC x92 x51 x82 xE9 x8E xE7 xFE xCD x95 xF2

x1B xBF x8F x52 x88 xEA x8F xF1 xB1 xCE xA2 xF3

x20 xC0 x80 x53 x89 xEB x90 xF8 xB0 xCF xE4 xF5

x21 xC1 x81 x54 x8A xE8 x9A xA6 xAA xDA xFB xB9

x22 xC2 x82 x55 xA1 xED x9B xA7 xBA xDB x96 xFB

x23 xC3 x83 x56 x8C xEE x9C x91 xE6 xDC x81 xFC

x24 xC4 x84 x57 x8B xEF x9D xF7 xB8 xDD x97 xF9

x28 xC5 x88 x58 x8D xEC x9E x92 xC6 xDE xA3 xFA

x29 xC8 x89 x59 xE1 xDF x9F xCF xA4 xDF x98 xFF

x2A xC9 x8A x5F xAA xAC xA0 xE6 xB5 xE1 xF6 xF7

x2B xCA x8B x62 xB6 xC2 xA1 xF9 xA8 xEA xFD xB2

x2C xCB x8C x63 x8E xC4 xAA xAD xA1 xEB xE2 xD4

x30 xCC x90 x64 xB7 xC0 xAB xA8 xBF xEC x99 xD6

x31 xCD x91 x65 xB5 xC1 xAC xD1 xD0 xED xE3 xD2

x33 xCE x93 x66 xC7 xC3 xAD xED xDD xEE xE0 xD3

x34 xD5 x94 x67 x8F xC5 xAE xE8 xDE xEF xE5 xD5

x35 xD9 x95 x68 x80 xC7 xAF xA9 xAE xFA xFC xB3

x36 xDA x96 x6A xA4 xF1 xB0 xBD xA2 xFB xEA xDB

x38 xDB x98 x70 x9B xF8 xB1 x9C xA3 xFC x9A xDC

x39 xDC x99 x71 x90 xC9 xB2 xBE xA5 xFD xEB xD9

x3A xDD x9A x72 xD2 xCA xB3 xFA xB7 xFE xE9 xDA

x3B xDF x9B x73 xD3 xCB xB4 xB8 xA9 xFF xFF x9F

x3E xF2 x9E x74 xD4 xC8 xB5 xF5 xA7

x41 xFE xA0 x75 xD6 xCD xB6 xF4 xB6

x42 x83 xE2 x76 xD7 xCE xB7 xAC xBC

EDITRAN/G 5.2 74


Differences between the old and the new translation tables (ascii to EBCD)

ASCII CHARACTERS changing from the old to the new table

ASCII Ebc-

old

Ebc-

new

ASCII Ebc-

old

Ebc-

new

ASCII Ebc-

old

Ebc-

new

ASCII Ebc-

old

Ebc-

new

x7C x49 x4F xA0 x45 x41 xC1 x21 x65 xE2 xEB x42

x80 x68 x20 xA1 x55 xAA xC2 x22 x62 xE3 xED x46

x81 xDC x21 xA2 xCE xB0 xC3 x23 x66 xE4 xCF x43

x82 x51 x22 xA3 xDE xB1 xC4 x24 x63 xE5 xEF x47

x83 x42 x23 xA4 x6A x9F xC5 x28 x67 xE6 xA0 x9C

x84 x43 x24 xA5 x7B xB2 xC6 x46 x9E xE7 x8E x48

x85 x44 x15 xA6 x9A x49 xC7 x66 x68 xE8 xAE x54

x86 x47 x06 xA7 x9B xB5 xC8 x29 x74 xE9 xFE x51

x87 x48 x17 xA8 xAB xA1 xC9 x2A x71 xEA xFB x52

x88 x52 x28 xA9 xAF xB4 xCA x2B x72 xEB xFD x53

x89 x53 x29 xAA x5F x9A xCB x2C x73 xEC x8D x58

x8A x54 x2A xAB xB8 x8A xCC x30 x78 xED xAD x55

x8B x57 x2B xAC xB7 x5F xCD x31 x75 xEE xBC x56

x8C x56 x2C xAD xAA xCA xCE x33 x76 xEF xBE x57

x8D x58 x09 xAE x8A xAF xCF x9F x77 xF0 xCA x8C

x8E x63 x0A xAF x8B xBC xD0 x8C xAC xF1 x8F x6A

x8F x67 x1B xB0 x06 x90 xD1 xAC x7B xF2 x3E xCD

x90 x71 x30 xB1 x08 x8F xD2 x72 xED xF3 xB9 xCE

x91 x9C x31 xB2 x09 xEA xD3 x73 xEE xF4 xB6 xCB

x92 x9E x1A xB3 x4F xFA xD4 x74 xEB xF5 xB5 xCF

x93 xCB x33 xB4 x0A xBE xD5 x34 xEF xF6 xE1 xCC

x94 xCC x34 xB5 x65 xA0 xD6 x75 xEC xF7 x9D xE1

x95 xCD x35 xB6 x62 xB6 xD7 x76 xBF xF8 x90 x70

x96 xDB x36 xB7 x64 xB3 xD8 x77 x80 xF9 xA1 xDD

x97 xDD x08 xB8 xB4 x9D xD9 x35 xFD xFA xB3 xDE

x98 xDF x38 xB9 x14 xDA xDA x36 xFE xFB xDA xDB

x99 xEC x39 xBA x15 x9B xDB x38 xFB xFC xFA xDC

x9A xFC x3A xBB x17 x8B xDC x39 xFC xFD xEA x8D

x9B x70 x3B xBC x1A xB7 xDD x3A xAD xFE x41 x8E

x9C xB1 x04 xBD xB0 xB8 xDE x78 xAE xFF xFF xDF

x9D x80 x14 xBE xB2 xB9 xDF x3B x59

x9E xBF x3E xBF x1B xAB xE0 xEE x44

x9F x04 xFF xC0 x20 x64 xE1 x59 x45

EDITRAN/G 5.2 75

11.ANNEX G. ERROR CODES AND CAUSES OF EDITRAN/CD

11. ANNEX G. ERROR CODES AND CAUSES OF EDITRAN/CD

The error codes (cause-diagnosis) that the product provides when connected to

EDITRAN/CD (they are shown with display in the execution of the procedures) are the

following:

91 ERROR DEVUELTO POR SERVIDOR EDITRAN/CD (FUNC. FIRMAR TEXTO)

93 ERROR DEVUELTO POR SERVIDOR EDITRAN/CD (FUNC. CIFRAR TEXTO)

97 DN CALCULADO ES DISTINTO A DN DE PERFILES

99 ERROR PROCESO REMOTO. ERROR PROGRAMA. ERROR CONEXION

A SERVIDOR. ERROR MACROS TCP

1X-3X ERRORES DE AREAS DE LLAMADA AL PROGRAMA ZTBGBITS

99/01 FUNCION DESCONOCIDA

99/06 TCPNAME ERRONEO

99/07 DIRECCION IP DEL SERVIDOR ERRONEA

99/08 PUERTO DEL SERVIDOR ERRONEO

99/09 SEGUNDOS ACTIVACION SERVIDOR ERRONEOS

99/11 LONGITUD DE PSS DE PERFIL ERRONEO

99/12 PSS DE PERFIL ERRONEO

99/13 LONGITUD DE DN DE PERFIL ERRONEO

99/14 DN DE PERFIL ERRONEO

99/15 LONGITUD DE PIN DE PERFIL ERRONEO

99/16 PIN DE PERFIL ERRONEO

99/21 LONGITUD FIRMA ERRONEA

99/22 FIRMA ERRONEA

99/23 LONGITUD TEXTO ERRONEA

99/24 TEXTO ERRONEO

5X ERRORES DE TIEMPO TRANSCURRIDO EN SERVER

99/51 NO SE HA CONSEGUIDO ENVIAR EL ON (NI 1 OCTETO)

99/52 NO SE HA CONSEGUIDO ENVIAR EL ON (ALGUN OCTETO)

99/53 NO SE HA CONSEGUIDO ENVIAR DATOS (NI 1 OCTETO)

99/54 NO SE HA CONSEGUIDO ENVIAR DATOS (ALGUN OCTETO)

99/55 NO SE HA CONSEGUIDO RECIBIR DATOS(NI 1 OCTETO)

99/56 NO SE HA CONSEGUIDO RECIBIR DATOS(ALGUN OCTETO)

99/57 NO SE HA CONSEGUIDO ENVIAR EL OFF(NI 1 OCTETO)

99/58 NO SE HA CONSEGUIDO ENVIAR EL OFF(ALGUN OCTETO)

6X-7X ERRORES TCP/IP EN CONEXION CON EL SERVIDOR

99/61 ERROR EN MACRO INITAPI

99/62 ERROR EN MACRO SOCKET

99/63 ERROR EN MACRO GETHOSTBYNAME

99/64 ERROR EN MACRO SETSOCKOPT

99/65 ERROR EN MACRO FCNTL

99/66 ERROR EN MACRO CONNECT

99/67 ERROR EN MACRO SELECT DE ESCRITURA

99/68 ERROR EN MACRO READ

99/69 ERROR EN MACRO SELECT DE LECTURA

99/70 ERROR EN MACRO WRITE

99/71 ERROR EN MACRO EZACIC08

99/72 ERROR EN MACRO EZACIC06

8X ERRORES EN LOS DATOS QUE DEVUELVE EL SERVIDOR

99/81 LONGITUD DE DATOS INVALIDA

Contact

[email protected]

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

mailto:[email protected]

Documents

EDITRAN/G 5montilla.indra.es/EN/doc/CICS/actual/EG52USUA_EN.pdfwhere EDITRAN/P is executed, indicating whether its execution is correct or incorrect. Depending on the case, this may