EDITRAN/E 5.2. User Manual. Statistics and Monitoring CICS

Transcription

1 EDITRAN/E 5.2 Statistics and Monitoring CICS User Manual INDRA April 2018

2 EDITRAN/E 5.2 CICS Manual de usuario CONTENTS 1. INTRODUCTION INSTALLATION UPDATING LIBRARIES CICS DEFINITIONS FILE DEFINITION EDITRAN/P PROFILE MODIFICATION MODIFICATION OF EDITRAN/G PROCEDURES INSTALLATION TESTS ON-LINE QUERY BATCH UTILITIES OBTAINING THE STATISTICS SUMMARY FILE (ZTBEJFLM) ALARM MANAGEMENT FILE DEFINITION MODIFICATION OF EDITRAN/G PROCEDURES INSTALLATION TESTS ERROR MESSAGES SMTP SETTING ALARM ON-LINE QUERY MONITORING OF LOCAL COMMUNICATION LINES Definitions Process description Errors Example: ANNEX PRESENTATION STATUSES TRANSMISSION STATUSES PRESENTATION SUMMARY FILE (ZTBEFMR) SELECTION RECORD PRESENTATION RECORD FILE RECORD PRESENTATION TOTALS RECORD TRANSMISSION RECORD TRANSMISSION TOTALS RECORD INDRA. All rights reserved. EDITRAN/E 5.2

3 EDITRAN/E 5.2 CICS Manual de usuario 1.INTRODUCTION. 1. INTRODUCTION. The purpose of the Monitoring and Statistics subsystem is to facilitate the detection of problems that cause the interruption of the normal development of the processes of the EDITRAN platform in each of the phases of data presentation and transmission, and to obtain information about incidences that, without giving rise to the process interruption, delay them or cause undesired effects. In addition, information is collected on the amount of data and the processing to which they are subjected, before and after their transmission. It is not about obtaining exhaustive information on all the steps of a session for this, EDITRAN/P trace and log, and EDITRAN/G log queries are available but obtaining a list of the interrupted sessions in order to act quickly on them and to correct the incidences detected in the correct transmissions to further refine their operation. This document describes the management and possibilities that the subsystem offers to the user. There are two ways to obtain information on the situation of the sessions: the On-line query mode by means of a transaction executed in the teleprocessing and the batch mode by means of lists and the operation of a file with the data resulting from the activity of the sessions. To see the on-line graphical interface, refer to the manual ED52USUC (Chapters 4 and 5) In addition to this, the statistics system includes the alarm management. INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page1-1

4 EDITRAN/E 5.2 CICS Manual de usuario 2.INSTALLATION. 2. INSTALLATION. This section specifies the steps to follow to install EDITRAN/E. Obviously, both EDITRAN/P and EDITRAN/G must be installed. The process is carried out in a set of steps as follows: - Updating libraries - CICS Definitions - EDITRAN/P profile modification - Incorporation of the Monitoring files to the EDITRAN/G procedures - Installation tests 2.1. UPDATING LIBRARIES. The libraries to use are those of executables and JCLs that exist for EDITRAN. The subsystem consists of a set of executable members, definitions of CICS tables and resource definitions specified below. These modules will be received via tape, cartridge or with the EDITRAN product Download Application. The executables will be included in the EDITRAN executable library and the rest in the JCL library CICS DEFINITIONS FCTCEDAE PCTCEDAE PPTCEDAE 2.3. FILE DEFINITION. The definition of the files ZTBEFMH, ZTBEFMP, ZTBEFMT, ZTBEFAL and ZTBEFPE will be performed with the ZTBEJIMH, ZTBEJIMP, ZTBEJIMT, ZTBEJIAL and ZTBEJIPE JCLs respectively EDITRAN/P PROFILE MODIFICATION. By means of the EDITRAN/P operator transaction, the "ZTBE" and "ZTB3" transactions in the fields reserved for "C.ESTADIST" and 'G. ESTADIST. will be incorporated into the profile of its main environment, respectively MODIFICATION OF EDITRAN/G PROCEDURES. In the procedures before and after transmission and reception, as well as in the initialization procedure (p1, p2, p3, p4 and p6), the file cards ZTBEFMH, ZTBEFMP, ZTBEFMT, ZTBEFMT, ZTBEFAL and ZTBEFPE must be added and the file ZTBEFMP in the incidences procedure (p5). This can be performed using the supplied macro (ZTXINSES). To execute this macro, type TSO EX 'librería.jcls.editran(ztxinst)'. The following information will be displayed: ******************************************************* * TECLEAR EL NOMBRE DE LA LIBRERIA DONDE SE ENCUENTRA * * ESTA CLIST, EL PANEL Y LA MACRO A EJECUTAR * ******************************************************* (TECLEAR FIN PARA CANCELAR) : Type name of JCL library of EDITRAN 5.2 INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page2-1

5 EDITRAN/E 5.2 CICS Manual de usuario 2.INSTALLATION. ********************************************* * TECLEAR EL NOMBRE DE LA MACRO A EJECUTAR * ********************************************* (TECLEAR FIN PARA CANCELAR) : Type ZTXINSES. The following panel will appear: /12/97 I N D R A (DEPARTAMENTO PRODUCTOS) KI0D978 13:47:09 EJECUTA UNA MACRO PARA CAMBIOS MASIVOS EN UNA LIBRERIA Libr. a cambiar : LIBRERÍA DONDE SE ENCUENTRAN PROCEDIMIENTOS MIEMBRO PROCESADO : PULSAR PF3 PARA SALIR NUMERO DE MIEMBROS: INSTALLATION TESTS. Once the product has been installed, the tests will consist in the transmission and reception of data batches through an EDITRAN session with INDRA SSI and the subsequent query of the statistical data through the ZTBE transaction, and the obtaining and listing of the summary file through the ZTBJLFR jcl. Another part of tests consists in the alarm management. INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page2-2

6 EDITRAN/E 5.2 CICS Manual de usuario 3.ON-LINE QUERY. 3. ON-LINE QUERY. In the graphical interface we can select: o According to a specific string or using masks (sessions or groups of sessions) o Depending on the action (sending or reception) o By dates o Presentations or Transmissions o According to status (finished, in progress, interrupted, etc.) In each option, we can query: o Statistics o Application files o Incidences. To see the entire graphical interface, refer to the manual ED52USUC, chapter 4 (statistics) and chapter 5 (alarms). INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page3-1

7 EDITRAN/E 5.2 CICS Manual de usuario 4.BATCH UTILITIES. 4. BATCH UTILITIES. This section describes the way to obtain both a summary file of the presentation monitoring and the lists of that file OBTAINING THE STATISTICS SUMMARY FILE (ZTBEJFLM). The statistics summary file contains the information, stored in the Monitoring history, of the sessions completed in the time interval required by the user. It can also select by source, remote node, or application (see jcl FSYSIN). If any of these fields are zeros-coded, the selection is generic. The desired interval is specified by indicating in the JCL input file that generates that file, the start and end moments in yyyymmdd-hhmmss format. The "ZTBEJFLM" JCL used to obtain the file is described in the following section. The immediate use of that file is to obtain a list that reflects these data and totals them by local and remote entity and application. The jcl used to obtain it is the same as the one used to generate the summary file. It is as follows: //KI10671L JOB (EGTC,KIT,,99),ZTBEFMT,MSGCLASS=H,CLASS=A, // MSGLEVEL=1,NOTIFY=&SYSUID //********************************************************************+ //** INDRA S.A. 09/1997 //** EDITRAN/E-V3.0 - CICS //** CREACION Y LISTADO DEL FICHERO RESUMEN DE ESTADISTICAS ZTBEFMNR //********************************************************************+ //** DESCRIPCION DEL REGISTRO DE SELECCION DEL INTERVALO DE //** FINALIZACION DE LAS SESIONES DE PRESENTACION //** CONSTA DE LOS SIGUIENTES CAMPOS SEPARADOS POR GUIONES //**.- FECHA-INICIO //** FECHA DEL MARGEN INFERIOR DE LA SELECCION EN (AAAAMMDD) //**.- HORA-INICIO //** HORA DEL MARGEN INFERIOR DE LA SELECCION EN (HHMMSS) //**.- FECHA-FIN //** FECHA DEL MARGEN SUPERIOR DE LA SELECCION EN (AAAAMMDD) //**.- HORA-FIN //** HORA DEL MARGEN SUPERIOR DE LA SELECCION EN (HHMMSS) //** //* //* BORRADO DEL FICHERO RESUMEN DE ESTADISTICAS ZTBEFMR //* //DELMONR EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE (KI.EITC.ZTBE.ZTBEFMR) PURGE NONVSAM //* //* //* OBTENCION DEL RESUMEN ESTADISTICO DEL INTERVALO ESPECIFICADO EN //* EL FICHERO FSYSIN //* //ZTBEB002 EXEC PGM=ZTBEB002,COND=(8,LT,DELMONR) //STEPLIB DD DSN=KI.EITC.ZTBG.LOAD,DISP=SHR //IGALIST DD SYSOUT=* //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSDBOUT DD SYSOUT=* //ABENDAID DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSABOUT DD SYSOUT=* //ZTBEFMR DD DSN=&&RESUMEN,DISP=(NEW,PASS,DELETE), // UNIT=SYSDA,SPACE=(TRK,(10,10),RLSE), // DCB=(RECFM=FB,LRECL=253,BLKSIZE=6072) //ZTBEFMH DD DSN=KI.EGTC.ZTBE.ZTBEFMH,DISP=SHR //ZTBGFPER DD DSN=KI.EITC.ZTBG.ZTBGFPER,DISP=SHR //FSYSIN DD * /* INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page4-1

8 EDITRAN/E 5.2 CICS Manual de usuario 4.BATCH UTILITIES. //* //** DELETE-DEFINE DEL FICHERO AUXILIAR DE TOTALES ZTBEFMTR KSDS //* //DEFTOT EXEC PGM=IDCAMS,COND=(0,NE,ZTBEB002) //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSDBOUT DD SYSOUT=* //ABENDAID DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSABOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE (KI.EITC.ZTBE.ZTBEFMTR) CLUSTER PURGE DEFINE CLUSTER - (NAME(KI.EITC.ZTBE.ZTBEFMTR) - VOL(DES802) - REC ( ) - FREESPACE(25 25) - RECORDSIZE( ) - SHAREOPTIONS(2 3) - KEYS(30 0) - INDEXED ) - DATA - (NAME(KI.EITC.ZTBE.ZTBEFMTR.DATA)) - INDEX - (NAME(KI.EITC.ZTBE.ZTBEFMTR.INDEX)) /* //* * //* CLASIFICACION DEL FICHERO RESUMEN //* * //SORMONR EXEC PGM=SORT, // COND=((8,LT,DEFTOT),(0,NE,ZTBEB002)) //SYSOUT DD SYSOUT=* //SORTIN DD DSN=&&RESUMEN,DISP=(OLD,PASS,DELETE) //SORTOUT DD DSN=KI.EITC.ZTBE.ZTBEFMR,DISP=(,CATLG,DELETE), // UNIT=SYSDA,SPACE=(TRK,(10,10),RLSE), // DCB=(RECFM=FB,LRECL=253,BLKSIZE=6072) //SYSIN DD * SORT FIELDS=(1,9,A,33,1,A,10,23,A,34,20,A),FORMAT=BI /* //* //*** LISTADO DEL FICHERO RESUMEN DE ESTADISTICAS (ZTBEFMR) //* //ZTBEB003 EXEC PGM=ZTBEB003, // COND=((8,LT,DEFTOT),(0,NE,ZTBEB002),(0,NE,SORMONR)) //STEPLIB DD DSN=KI.EITC.ZTBG.LOAD,DISP=SHR //ZTBEFMR DD DSN=KI.EITC.ZTBE.ZTBEFMR,DISP=SHR //ZTBEFMTR DD DSN=KI.EITC.ZTBE.ZTBEFMTR,DISP=SHR //ZTBEFL01 DD SYSOUT=* //ZTBEFL02 DD SYSOUT=* //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSDBOUT DD SYSOUT=* //ABENDAID DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSABOUT DD SYSOUT=* That execution will result in the two following lists: INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page4-2

9 EDITRAN/E 5.2 CICS Manual de usuario 4.BATCH UTILITIES. 1 ZTBEFL01 DETALLE DE LOS DATOS ESTADISTICOS DE PRESENTACIONES FINALIZADAS FECHA : 01/12/2004 EDITRAN ENTRE LAS 00:00:01 DEL 01/11/2004 Y LAS 23:59:59 DEL 25/11/2004 PAGINA : 1 SESIONES SEL:(ORIGEN: ,DESTINO: ,APLIC.:TE9998) OBTENIDAS EL 01/12/2004 A LAS 10:53:50 0 PRESENTACION DE EMISION DEL CENTRO LOCAL S00DI 0 CENTRO REMOTO : IMS 0 APLICACION : TE FINALIZADA A LAS 08:56:34 DEL 19/11/2004 CON 0000 INCIDENCIAS DE PRESENTACION 0 NOMBRE FICHERO FMT LONG. N.REGTROS. NUMERO BYTES BYTES COMPRIM. % CPR F-H-CREACION ================================================= ==== ====== =========== =============== =============== ====== =============== 01 - KI.SGDC.ZTB.R R980.ATE9998.EMISION FIJO TOT.PRESENTACION TE9998 : DATOS TRANSMISION - SESION TRANSMISION INICIO FIN DURACION PERMANENCIA INCIDENCIAS ================================ =============== =============== ========== =========== ============ TE :00:05 0:00:06 0 TOT.TRANSMISION : 0:00:05 0:00:06 0 APLICACION : TE FINALIZADA A LAS 09:44:44 DEL 19/11/2004 CON 0000 INCIDENCIAS DE PRESENTACION 0 NOMBRE FICHERO FMT LONG. N.REGTROS. NUMERO BYTES BYTES COMPRIM. % CPR F-H-CREACION ================================================= ==== ====== =========== =============== =============== ====== =============== 01 - KI.SGDC.ZTB.R R980.ATE9998.EMISION FIJO TOT.PRESENTACION TE9998 : DATOS TRANSMISION - SESION TRANSMISION INICIO FIN DURACION PERMANENCIA INCIDENCIAS ================================ =============== =============== ========== =========== ============ TE :00:06 0:00:06 0 TOT.TRANSMISION : 0:00:06 0:00:06 0 APLICACION : TE FINALIZADA A LAS 10:15:17 DEL 23/11/2004 CON 0000 INCIDENCIAS DE PRESENTACION 0 NOMBRE FICHERO FMT LONG. N.REGTROS. NUMERO BYTES BYTES COMPRIM. % CPR F-H-CREACION ================================================= ==== ====== =========== =============== =============== ====== =============== 01 - KI.SGDC.ZTB.R R980.ATE9998.EMISION FIJO TOT.PRESENTACION TE9998 : DATOS TRANSMISION - SESION TRANSMISION INICIO FIN DURACION PERMANENCIA INCIDENCIAS ================================ =============== =============== ========== =========== ============ TE :00:06 0:00:06 0 TOT.TRANSMISION : 0:00:06 0:00:06 0 PRESENTACION DE EMISION DEL CENTRO LOCAL S00DI 0 CENTRO REMOTO : IMS 0 APLICACION : TE FINALIZADA A LAS 15:29:19 DEL 23/11/2004 CON 0000 INCIDENCIAS DE PRESENTACION 0 NOMBRE FICHERO FMT LONG. N.REGTROS. NUMERO BYTES BYTES COMPRIM. % CPR F-H-CREACION ================================================= ==== ====== =========== =============== =============== ====== =============== 01 - KI.SGDC.ZTB.R R980.ATE9998.EMISION FIJO TOT.PRESENTACION TE9998 : DATOS TRANSMISION - SESION TRANSMISION INICIO FIN DURACION PERMANENCIA INCIDENCIAS ================================ =============== =============== ========== =========== ============ TE :00:06 0:00:07 0 TOT.TRANSMISION : 0:00:06 0:00:07 0 PRESENTACION DE RECEPCION DEL CENTRO LOCAL S00DI 0 CENTRO REMOTO : IMS 0 APLICACION : TE FINALIZADA A LAS 08:55:36 DEL 19/11/2004 CON 0000 INCIDENCIAS DE PRESENTACION 0 NOMBRE FICHERO FMT LONG. N.REGTROS. NUMERO BYTES BYTES COMPRIM. % CPR F-H-CREACION ================================================= ==== ====== =========== =============== =============== ====== =============== 01 - KI.SGDC.ZTB.L00.R R980.ATE9998.R FIJO TOT.PRESENTACION TE9998 : DATOS TRANSMISION - SESION TRANSMISION INICIO FIN DURACION PERMANENCIA INCIDENCIAS ================================ =============== =============== ========== =========== ============ TE :00:11 0:00:11 0 TOT.TRANSMISION : 0:00:11 0:00:11 0 APLICACION : TE FINALIZADA A LAS 09:43:47 DEL 19/11/2004 CON 0000 INCIDENCIAS DE PRESENTACION 0 NOMBRE FICHERO FMT LONG. N.REGTROS. NUMERO BYTES BYTES COMPRIM. % CPR F-H-CREACION ================================================= ==== ====== =========== =============== =============== ====== =============== 01 - KI.SGDC.ZTB.L00.R R980.ATE9998.R FIJO TOT.PRESENTACION TE9998 : DATOS TRANSMISION - SESION TRANSMISION INICIO FIN DURACION PERMANENCIA INCIDENCIAS ================================ =============== =============== ========== =========== ============ TE :00:12 0:00:13 0 TOT.TRANSMISION : 0:00:12 0:00:13 0 APLICACION : TE FINALIZADA A LAS 10:14:11 DEL 23/11/2004 CON 0000 INCIDENCIAS DE PRESENTACION 0 NOMBRE FICHERO FMT LONG. N.REGTROS. NUMERO BYTES BYTES COMPRIM. % CPR F-H-CREACION ================================================= ==== ====== =========== =============== =============== ====== =============== 01 - KI.SGDC.ZTB.L00.R R980.ATE9998.R FIJO TOT.PRESENTACION TE9998 : DATOS TRANSMISION - SESION TRANSMISION INICIO FIN DURACION PERMANENCIA INCIDENCIAS ================================ =============== =============== ========== =========== ============ TE :00:24 0:00: TOT.TRANSMISION : 0:00:24 0:00: PRESENTACION DE RECEPCION DEL CENTRO LOCAL S00DI 0 CENTRO REMOTO : IMS 0 APLICACION : TE FINALIZADA A LAS 15:27:47 DEL 23/11/2004 CON 0000 INCIDENCIAS DE PRESENTACION 0 NOMBRE FICHERO FMT LONG. N.REGTROS. NUMERO BYTES BYTES COMPRIM. % CPR F-H-CREACION ================================================= ==== ====== =========== =============== =============== ====== =============== 01 - KI.SGDC.ZTB.L00.R R980.ATE9998.R FIJO TOT.PRESENTACION TE9998 : DATOS TRANSMISION - SESION TRANSMISION INICIO FIN DURACION PERMANENCIA INCIDENCIAS ================================ =============== =============== ========== =========== ============ TE :02:03 0:02:07 0 TOT.TRANSMISION : 0:02:03 0:02:07 INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page4-3

10 EDITRAN/E 5.2 CICS Manual de usuario 4.BATCH UTILITIES. 1 ZTBEFL02 TOTALES DE LOS DATOS ESTADISTICOS DE PRESENTACIONES FINALIZADAS FECHA : 01/12/2004 EDITRAN ENTRE LAS 00:00:01 DEL 01/11/2004 Y LAS 23:59:59 DEL 25/11/2004 PAGINA : 1 SESIONES SEL:(ORIGEN: ,DESTINO: ,APLIC.:TE9998) OBTENIDAS EL 01/12/2004 A LAS 10:53:50 0 TOTALES DE EMISION POR PRESENTACION DEL CENTRO LOCAL S00DI 0 PRESENTACION NRO. REGISTROS BYTES FICH.ORIGEN BYTES COMPRIM. % COMPRESION NRO.TRANSMISIONES DURACION MEDIA TE :00:05 0 TOTALES DE EMISION POR CENTRO REMOTO PARA EL CENTRO LOCAL S00DI 0 REMOTO NRO. REGISTROS BYTES FICH.ORIGEN BYTES COMPRIM. % COMPRESION NRO.TRANSMISIONES DURACION MEDIA :00:05 0 TOTALES DE EMISION POR APLICACION PARA EL CENTRO LOCAL S00DI 0 APLIC. NRO. REGISTROS BYTES FICH.ORIGEN BYTES COMPRIM. % COMPRESION NRO.TRANSMISIONES DURACION MEDIA TE :00:05 0 TOTALES DE EMISION GENERALES PARA EL CENTRO LOCAL S00DI 0 NRO. REGISTROS BYTES FICH.ORIGEN BYTES COMPRIM. % COMPRESION NRO. TRANSMISIONES DURACION TOTAL DURACION MEDIA :00:23 0:00:05 0 TOTALES DE RECEPCION POR PRESENTACION DEL CENTRO LOCAL S00DI 0 PRESENTACION NRO. REGISTROS BYTES FICH.ORIGEN BYTES COMPRIM. % COMPRESION NRO.TRANSMISIONES DURACION MEDIA TE :00:42 0 TOTALES DE RECEPCION POR CENTRO REMOTO PARA EL CENTRO LOCAL S00DI 0 REMOTO NRO. REGISTROS BYTES FICH.ORIGEN BYTES COMPRIM. % COMPRESION NRO.TRANSMISIONES DURACION MEDIA :00:42 0 TOTALES DE RECEPCION POR APLICACION PARA EL CENTRO LOCAL S00DI 0 APLIC. NRO. REGISTROS BYTES FICH.ORIGEN BYTES COMPRIM. % COMPRESION NRO.TRANSMISIONES DURACION MEDIA TE :00:42 0 TOTALES DE RECEPCION GENERALES PARA EL CENTRO LOCAL S00DI 0 NRO. REGISTROS BYTES FICH.ORIGEN BYTES COMPRIM. % COMPRESION NRO. TRANSMISIONES DURACION TOTAL DURACION MEDIA :02:50 0:00:42 INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page4-4

11 EDITRAN/E 5.2 CICS Manual de usuario 5.ALARM MANAGEMENT. 5. ALARM MANAGEMENT. The objective of the Alarm Management subsystem is to control the normal evolution of the processes of the EDITRAN platform in each phase of data presentation and transmission. In such a way that, if any type of incidence occurs, it will be possible to send immediate notification of these problems to different partners (via , SMS, notification to an external manager, etc.), and to keep this information on the incidence in a log. The alarms can also appear when the processes after transmission or reception are successfully completed. The alarm types can be: 1. Alarms to external manager. An example program is provided, ZTBEBA10, which makes displays and records in the system log. 2. Alarms to . They can be of three types: 2.1. Alarms through the zos SMTP server Alarms through the sendmail program of the Zos UNIX partition 2.3. Alarms through an external manager. In this case, an IP connection is established between the host and a unix-pc-windows server, which manages the sending. To implement the program on the server, contact INDRA. 3. Alarms to mobiles through an external manager. In this case, an IP connection is established between the host and a unix-pc-windows server, which manages the sending. To implement the program on the server, contact INDRA. A standard modem must be installed on the server at with a maximum speed of The telephone must be configured with a speed of 58600, and data (fax/data) must be exchanged with the fax/dat reception option checked. The operation is as follows: 1.- The user defines and registers sessions in a profile file (with generic or specific criteria), indicating how to make notifications when the transmission-reception process fails, either in a previous or a subsequent procedure, or if there has been an interruption with specific codes (to see them, check EDITRAN/P A7I codes). This can also be performed as the subsequent procedure works properly. 2.- The user defines a log file that contains the data of the sessions that have failed, the reason, and whether the error was reported to anyone. 3.- Once a failure occurs, the system logs and reports this incidence, if instructed to do so FILE DEFINITION. The ZTBEFAL, ZTBEFPE files will be defined with the ZTBEJIAL, ZTBEJIPE JCLs respectively. It is important to note that ZTBEFAL has shr (3,3) MODIFICATION OF EDITRAN/G PROCEDURES. The ZTBEFAL, ZTBEFPE file cards must be added both in the procedures before and after transmission and reception, and in the interruption procedure (ZTBGP**). //ZTBEFPE DD DSN=puntero.ZTBEFPE,DISP=SHR INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page5-1

12 EDITRAN/E 5.2 CICS Manual de usuario 5.ALARM MANAGEMENT. //ZTBEFAL DD DSN=puntero.ZTBEFAL,DISP=SHR It is also possible (recommended) to include a second step in the procedure, following the step of loading, downloading, exception, etc., so that if this step is abended, it enters and the alarm is notified. If this step is not included and the previous one is abended, the alarm will not be notified. If the alarm is notified, the previous step is usually not abended (it will end with rc xx), so this step will not enter. // SET AB='ERROR ABEND CODE. CONSULTE SALIDA DEL JCL' //PASOERR EXEC PGM=ZTBEBA00,COND=(ONLY), // PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&AP&AB', // REGION=8M,TIME=25 //STEPLIB DD DSN=puntero.LOAD,DISP=SHR //ZTBEFPE DD DSN=puntero.ZTBEFPE,DISP=SHR //ZTBEFAL DD DSN=puntero.ZTBEFAL,DISP=SHR //ZTBPFPE DD DSN=puntero.ZTBPFPE,DISP=SHR //ZTBGFPER DD DSN=puntero.ZTBGFPER,DISP=SHR //ZTBGFLOG DD DSN=puntero.ZTBGFLOG,DISP=SHR //ZTBGFPRI DD SYSOUT=*,DCB=(BLKSIZE=105) //* (INTERNAL READER DE LA IGA. PONGASE CLASE DE SALIDA DE TRABAJOS ) //ZTBGFINT DD SYSOUT=(H,INTRDR),DCB=(BLKSIZE=80) //SYSOUT DD SYSOUT=*,OUTLIM= //SYSPRINT DD SYSOUT=*,OUTLIM= //SYSDBOUT DD SYSOUT=*,OUTLIM= //ABENDAID DD SYSOUT=*,OUTLIM= //SYSUDUMP DD SYSOUT=*,OUTLIM= //SYSABOUT DD SYSOUT=*,OUTLIM= //CEEDUMP DD SYSOUT=*,OUTLIM= INSTALLATION TESTS. Once the product has been installed, the tests will consist of defining a suitable profile and loading it with the wrong parameters ERROR MESSAGES. If an external or sms manager is used and the sending has not been achieved, we can find displays in the procedure with more detailed information about the problem. * ERRORES DEVUELTOS EN EL PROGRAMA ZTBEBITS * * ================================ * * RESULTADO RAZON DESCRIPCION * * * * 91 ERROR EN EL SERVIDOR (FUNC. 301 ENVIAR ) * * 92 ERROR EN EL SERVIDOR (FUNC. 302 ENVIAR SMS) * * 99 ERROR PROCESO REMOTO. ERROR PROGRAMA. ERROR CONEXION * * A SERVIDOR. ERROR MACROS TCP * * 1X-3X ERRORES DE AREAS DE LLAMADA AL PROGRAMA ZTBEBITS * * 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 ERRONEA * * 99/12 A ENVIAR ERRONEO * * 99/15 LONGITUD DE SMS DE PERFIL ERRONEO * * 99/16 SMS DE PERFIL ERRONEO * * 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) * INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page5-2

13 EDITRAN/E 5.2 CICS Manual de usuario 5.ALARM MANAGEMENT. * 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 * ****************************************************************** For example, the following display will be shown in the procedure, in case the server is not active: ************************************************* *ERRORES DETECTADOS EN PROCESO TCP/IP EDITRAN/E* ERROR MACRO WRITE. ERRNO: CODIGO DE RETORNO : CODIGO DE RAZON : ************************************************* Following the previous example, the following error will appear in the alarm log: <----- RESULTADOS -----> EXT. <-- --> SMS SESION FECHA HORA R-01 R-02 R-03 R-04 R-05 ======================== ========== ======== ==== ==== ==== ==== ==== XXXXXXXXXXXXXXXXXXXXXXXX DD/MM/AAAA HH:MM:SS ZTBGXXXX: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX * ERRORES DEVUELTOS EN EL PROGRAMA ZTBEBA00 * * ================================ * * RESULTADO RAZON DESCRIPCION * * * * 81 ERROR EN APERTURA ZTBGFINT * * 82 ERROR EN ESCRITURA ZTBGFINT * * 83 ERROR EN CIERRE ZTBGFINT * * 84 ERROR AL ALOCAR FCOSMTP * * 85 ERROR AL ABRIR FCOSMTP * * 86 ERROR AL ESCRIBIR FCOSMTP * * 87 ERROR AL CERRAR FCOSMTP * * 88 ERROR AL DESALOCAR FCOSMTP * INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page5-3

14 EDITRAN/E 5.2 CICS Manual de usuario 5.ALARM MANAGEMENT SMTP SETTING. In the EDITRAN/E profiles, two related parameters will be requested: Domain name of the SMTP machine. It is the value specified in NJENODENAME Name of the startup procedure. It is set as follows (example): *********************************************************************** Defaults that normally aren't changed: PORT 25 Port to accept incoming mail BADSPOOLFILEID tcpmaint Mailbox where unreadable spool files and looping mail are transferred. LOG Log all SMTP mail delivered INACTIVE 180 Time-out for inactive connections FINISHOPEN 120 Time-out for opening TCP connections RETRYAGE 3 WARNINGAGE 3 RETRYINT 2 ETRYINT 120 MAXMAILBYTES RESOLVERRETRYINT 20 RCPTRESPONSEDELAY 60 TEMPERRORRETRIES 0 SPOOLPOLLINTERVAL 30 TIMEZONE EST DEBUG Keep retrying mail delivery for 3 days Warn sender that mail has been undeliverable for 1 day, but that attempts to deliver the mail will continue for another 2 days. Retry mail delivery every 2 horas Retry mail delivery every 2 horas Largest mail to accept over a TCP connection Retry pending name resolutions every 20 minutes How long to delay RCPT TO: response when waiting for an address resolution. How many times to retry temporary delivery errors. The default, 0, means retry for RETRYAGE days otherwise the mail is returned after this number of deliver attempts. Amount of time in seconds between spool polling Specifies the printable 3-letter name of the local time zone. Remember to change this for daylight saving time. Normally not used, causes debug information to be written to the SMTP DEBUG file. NJENODENAME NODOMVSB *********************************************************************** The following statements tell SMTP where incoming mail is stored while it is being queued for delivery. MAILFILEDSPREFIX SMTP Data set prefix name for queued mail files MAILFILEUNIT SYSDA MVS unit name for new file allocations MAILFILEVOLUME volume MVS volume name for new file allocations *********************************************************************** The POSTMASTER statement specifies the mailboxes where mail addressed to postmaster is spooled. Multiple POSTMASTER statements can be specified when not running in SECURE mode. POSTMASTER tcpmaint *********************************************************************** Use the SMSGAUTHLIST statement to specify the addresses of local users authorized to issue privileged SMTP SMSG commands. SMSGAUTHLIST TCPMAINT SWTJLAM ENDSMSGAUTHLIST *********************************************************************** The OUTBOUNDOPENLIMIT statement specifies the maximum number of simultaneous TCP connections over which SMTP will actively deliver mail. OUTBOUNDOPENLIMIT 10 INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page5-4

15 EDITRAN/E 5.2 CICS Manual de usuario 5.ALARM MANAGEMENT. *********************************************************************** The REWRITE822HEADER statement specifies whether SMTP will rewrite the RFC822 headers on all mail passing from NJE to TCP through the mail gateway. The SMTP.RULES data set specifies how the server is to rewrite the headers. The PRINT NOPRINT options specify whether SMTP will print the rules to the SMTP output when SMTP starts. REWRITE822HEADER YES PRINT *********************************************************************** IPMAILERADDRESS INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page5-5

16 EDITRAN/E 5.2 CICS Manual de usuario 6.ALARM ON-LINE QUERY. 6. ALARM ON-LINE QUERY. In alarms: A log with errors is displayed Alarms can be activated and deactivated A local environment is defined. Session masks are defined to notify alarms. To see the entire graphical interface, refer to the manual ED52USUC, chapter 4 (statistics) and chapter 5 (alarms). INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page6-1

17 EDITRAN/E 5.2 CICS Manual de usuario 7.MONITORING OF LOCAL COMMUNICATION LINES. 7. MONITORING OF LOCAL COMMUNICATION LINES. This functionality is another one of those that make up the statistics and alarms module. In some cases, a line or resource may fail in the entity. This may mean that the transmissions do not arrive or cannot leave normally. This situation is difficult to detect, because sometimes these failures leave no trace or alarm. When the entity detects the situation, a good deal of time has passed, and it is because the remote nodes that are not connected indicate the abnormality, or because the local operators detect that the file sending or reception are not completed. This situation is often complicated and lengthened, as no action is carried out directly on the problem. That is to say, the failure or inoperability of the line is usually the last point to analyze. In addition, the product is often 'neglected' with planners and others, which leads to many more exceptions than usual. The monitoring of the local lines solves the above situation. Not because it solves these failures, but because it notifies them by means of an alarm (mail, sms, etc.), as soon as it detects them, so that the operators can investigate and act immediately in the appropriate direction. This functionality allows monitoring all the local lines (to choose which) of the entity, indicating how often we want to monitor them. There are several types of local lines: Proxy and IP Definitions To use it, proceed as follows: 1. Presentation and transmission session. To define an "atypical" or "known" session for local monitoring, e.g., local monlin. The features with which it is defined make no difference. The important thing is that it serves to notify the operators and it contains the jcl cards with which the procedures will be launched (see chapter and or chapter 3 of manual ED52USUC). 2. EDITRAN/P local environment (see chapter of manual ED52USUC ). It must define: 2.1. The monitoring transaction (ZTBC) 2.2. The fields related to the local line monitoring, specifically: Time-out in minutes. How often we want to "test" the local lines. It is not allowed to indicate less than 4 minutes. A continuous testing does not seem appropriate, since the functionality uses resources and it calls the network for verification. Therefore, "it uses momentarily cvcs or sockets". It seems more logical to test for example every hour, every 6 hours, or every 12 hours Monitoring procedure (ZTBGP9C) is the procedure that starts when a downed line is detected (or when it was down and it becomes operational) Lines to monitor. Selection of local lines to monitor (IP and proxies) If we check S (YES) in the 1-IP field, we indicate that we want to monitor ALL the listener that handle EDITRAN transactions and arrive over IP (SECEXIT EDITRAN). INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page7-1

18 EDITRAN/E 5.2 CICS Manual de usuario 7.MONITORING OF LOCAL COMMUNICATION LINES If we check S (YES) in the 3-PX field, we indicate that we want to monitor the lines associated with the local proxy and the gateway. We must specify our choice in the option In addition, we are indicating that the listener serving connections of the PX gateway will also be monitored (SECEXIT EDITR-PR) EDITRAN/P notification session for the monitoring before defined (local MONLIN). 3. Local lines to monitor (see chapter of manual ED52USUC). We must select in the local proxies those we want to monitor (in addition, the appropriate field of the type of line to monitor in the local environment must be included). To select it, enter S (YES) in the MONITOR PX field. 4. Alarms (see chapter 5.3 of manual ED52USUC) If we want to send an alarm (mail, sms, etc.) when the line is down (or activated), a mask, appropriate to the notification session (or the same local session monit) must be registered Process description From time to time (time-out indicated in the environment), a process starts and it performs the following: 1. If you checked in the local environment MONITOR IP LINES = S (YES), the listener (transid EDITRAN that handle native IP calls through a port, SECEXIT EDITRAN) is verified to be active (if they aren t, an attempt is made to activate it). In addition, an outgoing call is made to the loopback IP , so that it becomes an incoming call to the different listener. If they answer, it seems clear that they are operational and in session, so that they can answer calls coming from the remote nodes. In addition, outgoing calls (client processes) are also being tested. 2. If you checked in the local environment MONITOR PX LINES = S (YES): a. The local listener are verified with SECEXIT = EDITR-PR in the same way as 1 (by marking MONITOR IP LINES = `S' (YES) with the local listener with SECEXIT = EDITRAN) b. PX gateways with parameter MONITOR = S (YES) are verified by making an outgoing call to a remote node whose IP is the loopback of the Proxy. This one makes the call and at that moment it arrives, so it thinks it is a remote call, and therefore it passes it on to the SECEXIT = EDITR-PR zos listener. This tests the entire circuit: zos client, Proxy listener, Proxy client, and zos listener. In case of acceptance, the complete circuit is tested. Otherwise, it must be specified where the problem is in the whole circuit. The procedure specified in local environment (ZTBGP9C) is started with the jcl files of the monitoring session specified in local environment, in case of: Detecting an incidence on a line (as long as it is not marked as already having an incidence in progress). In this case, the procedure starts with function 98, cause indicating the problem and network diagnosis-cause. Note: If a line has an incidence, it is marked as such and in the next test performed on it, no incidence is sent if it continues in that status. INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page7-2

19 EDITRAN/E 5.2 CICS Manual de usuario 7.MONITORING OF LOCAL COMMUNICATION LINES. Detecting a line in operational or active status, as long as the line was marked as having an incidence in the previous test. In this case, the procedure starts with function 97. If the previous procedure starts: A message is recorded in the alarm log (option 5.1 from the main menu) If there is a suitable mask (option 5.3), with the monitoring session defined in the local environment, an alarm (external, or sms) is sent with the message of the alarm log (either activation or failure) Errors. The following returns can take place: * 00: INICIALIZADO - CORRECTO * * 01: LISTENER NO ACTIVO * * 02: LISTENER NO CONTESTA * * 03: ERROR AL ARRANCAR LISTENER * * 21: PASARELA NO ACTIVA * * 22: PASARELA NO CONTESTA * * 23: ERROR DEVUELTO POR PASARELA * * 41: LU FICTICIA NO ACTIVA * * 42: LINEA X25 NO CONTESTA * * 43: RECHAZO DE ISARD X25 (X0C RECHAZADO) * * 44: LINEA X25 FUERA DE SERVICIO-ERROR PROC LOCAL * For each return, a cause-diagnosis or a more complete reason for the error is displayed. For example, with a return 21, a message similar to the following is displayed: ZTP9999-LIN PX 006( /07779) CAIDA.PASARELA INACT FF-01 Indicating error (ZTP999) on the PROXY 006 line because the gateway is down. The IP of this gateway is and it should listen to us on port The cause of the error and the diagnosis can be found in of the graphical interface. INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page7-3

20 EDITRAN/E 5.2 CICS Manual de usuario 7.MONITORING OF LOCAL COMMUNICATION LINES. Example: To define the transmission and presentation session In local environment: INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page7-4

21 EDITRAN/E 5.2 CICS Manual de usuario 7.MONITORING OF LOCAL COMMUNICATION LINES. Defined in the PROXY lines (number 1) The content of the PX-001 is displayed (Monitor field) INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page7-5

22 EDITRAN/E 5.2 CICS Manual de usuario 7.MONITORING OF LOCAL COMMUNICATION LINES. If, for example, an error is detected on that line and later corrected, the following messages appear in the alarm log (option 5.1). If it were also defined in option 5.3, the corresponding , sms or external would have been sent (see R-02 from the previous screen, indicating that you sent an SMTP sms). INDRA. All rights reserved EE52USIC_Eng.docx 10/04/ :39 Page7-6

23 EDITRAN/E 5.2 CICS Manual de usuario 8.ANNEX. 8. ANNEX PRESENTATION STATUSES. Status Situation Description E00 Initialized The control log of the presentation session doesn t exist or an initialization request has been received. E10 Previous in progress A process before the transmission has been requested and it has not finished. E17 Incident in An incident has occurred in a process before the transmission. before transmission E18 Initialized Initialization request received with previous process interrupted. E20 Previous Process before the transmission correctly ended. finished E27 Interrupted A notification is received from EDITRAN/P (A7I) or a request for interruption from the application or the operator in transmission status (E20). E28 Initialized Request for initialization received from E20 or E27. E30 After Procedure after the transmission in progress transmission in progress E37 Incident in after An incident has occurred in a process after the transmission. transmission E38 Initialized Request for initialization received from E30 or E37. E40 Finished Process after the transmission correctly ended. There are four general statuses in the selection of presentation sessions: Interrupted. It would include statuses 17, 27 and 37. The presentation sessions not completed (statuses 10, 20 and 30) would also be considered as interrupted, but with some transmission session (see annex 5.2) in status 07 or 17. In progress. It would include statuses 10, 20 and 30, as long as there is no transmission session associated with that presentation in status (see annex 5.2) 07 or 17. In transmission. It would include statuses 10, 20 and 30, provided that there is a transmission session associated with that presentation in status (see annex 5.2) 11 or 12. Finished. It would include the statuses 00, 18, 28, 38 and 40. INDRA. All rights reserved. EDITRAN/E 5.2 Page 8-1

24 EDITRAN/E 5.2 CICS Manual de usuario 8.ANNEX TRANSMISSION STATUSES. Status Situation Description E00 Initialized The control log of the transmission session does not exist or an initialization notification of the associated presentation session has been received. E01 Active The session is active because at least it has been referred to at some point in time with a local or remote call request or with some message that does not allow knowing the direction that will be used later (Sol-lla, E00, SAP, etc.). E02 In session Session established. SAP/SAR have been exchanged but no transmission retry has been received in the direction to which the control log is associated. E07 E11 Interrupted without transmission attempt Transmission retry Session released before retrying the transmission in the direction with which the control log is associated. The session is active because at least it has been referred to at some point in time with a transmission retry in the direction the control log is associated to (E00(E/R)), ECP(8), etc.). E12 Transmitting The notification of the transmission start has been received. E13 Ended without process after transmission The transmission has ended, but the procedure after transmission does not exist. E14 E15 E17 Waiting for process after transmission Ended with process after transmission Interrupted with transmission retry The transmission has ended and the procedure after the transmission has been launched. The notification of the correct end of the procedure after transmission has been received. Session interrupted after trying the transmission in the direction the control log is associated to. There are three general statuses in the selection of transmission sessions: Interrupted. It would include the statuses 07 and 17. In progress. It would include the statuses 02, 11, 12, 13 and 14. Finished. It would include the status 15. The statuses 00 (initialized) and 01 (active) are considered in the presentation status query. INDRA. All rights reserved. EDITRAN/E 5.2 Page 8-2

25 EDITRAN/E 5.2 CICS Manual de usuario 8.ANNEX PRESENTATION SUMMARY FILE (ZTBEFMR). Generated from the historical data. It can contain the data corresponding to all the presentations in the history or to those completed in a certain time interval. Its organization is sequential. The user will be in charge of managing and classifying the successive files obtained in each process according to the needs of his/her installation. There will be a first record indicating the selected interval for the file generation. Each presentation is determined by its code, the direction, and the date and time it ends. In a presentation, some records are differentiated from each other by the record type field as follows: Selection. Presentation. File. Totals of the files associated with the presentation. Transmission. Totals of the transmission sessions associated with the presentation. The records of the same type (20) are differentiated by the corresponding serial number. Data types 10, 20 and 30 are direct historical data. The types 21 and 31 are obtained by totaling the types 20 and 30 respectively. The record format is as follows: INDRA. All rights reserved. EDITRAN/E 5.2 Page 8-3

26 EDITRAN/E 5.2 CICS Manual de usuario 8.ANNEX SELECTION RECORD. There is one record per file. It determines the time interval for the end of the presentations used to obtain the file and the time it was obtained. Level Name Length Fmt. Description 1 Presentation 32 Alph. Low values for this type of record Session 1 Direction 1 Alph. Low values for this type of record 1 End Date 8 Alph. Low values for this type of record 1 End Time 6 Alph. Low values for this type of record 1 Record type 2 Alph. 00 : Indicates it is the selection record. 1 Order Number 4 Nr. Low values for this type of record 1 Creation date 8 Alph. Date of the moment when the file is generated yyyymmdd 1 Creation time 6 Alph. File generation time in hhmmss 1 Interval Start Date 8 Alph. Date of the lower margin of the selection in yyyymmdd 1 Interval Start Time 6 Alph. Time of the lower margin of the selection in hhmmss 1 Interval End Date 8 Alph. Date of the upper margin of the selection in yyyymmdd 1 Interval End Time 6 Alph. Time of the upper margin of the selection in hhmmss PRESENTATION RECORD. There is one record per presentation. It contains its general data, indicating whether it ended correctly or it was initialized. Level Name Length Fmt. Description 1 Presentation Session 32 Alph. Made up of Source (9) + Destination (9) + Application (6) + blanks (8). 1 Direction 1 Alph. Specifies the presentation direction. E: Transmission log group. R: Reception log group. 1 End Date 8 Alph. Presentation completion date yyyymmdd 1 End Time 6 Alph. Presentation completion time in hhmmss 1 Record type 2 Alph. 10 : Indicates that it is the presentation record 1 Order Number 4 Nr. Zeros. 1 Local name 20 Alph. Literal of profiles of the local center in EDITRAN/G 1 Remote name 20 Alph. Literal of profiles of the remote center in EDITRAN/G 1 Application name 20 Alph. Literal of profiles for application in EDITRAN/G 1 Incident 4 Nr. Number of presentation incidents 1 Compression 1 Alph. (S/N) (YES/NO) Indicates whether compression was used or not 1 Encryption 1 Alph. (S/N) (YES/NO) Indicates whether compression was used or not. 1 Final status 2 Alph. 00: Correctly ended 01: Ended through Initialization. INDRA. All rights reserved. EDITRAN/E 5.2 Page 8-4

27 EDITRAN/E 5.2 CICS Manual de usuario 8.ANNEX FILE RECORD. Each presentation contains as many records of this type as there are files sent or received in it with a maximum of 99. Each one specifies the characteristics of the associated file. Level Name Length Fmt. Description 1 Presentation Session 32 Alph. Made up of Source (9) + Destination (9) + Application (6) + blanks (8). 1 Direction 1 Alph. Specifies the presentation direction. E: Transmission log group. R: Reception log group. 1 End Date 8 Alph. Presentation completion date yyyymmdd 1 End Time 6 Alph. Presentation completion time in hhmmss 1 Record type 2 Alph. 20 : File record 1 Order Number 4 Nr. Differentiates the different files of the presentation and matches the position of the file in the profiles of the sender. 1 DSN 44 Alph. Physical name of the application file in source for transmission, and in destination for reception. 1 Type of file 2 Alph. Indicates the file format F : Fixed length. V : Variable length. VS: Variable Expanded B : Binary 1 Record length 6 Nr. Record length of the original file. 1 Number of records 12 Nr. Number of records that make up the file. 1 File Bytes 12 Nr. Number of bytes of the original file 1 File compressed 12 Nr. Number of bytes of the file resulting from the compression bytes 1 Compression 4 Nr. % of compression achieved. relationship 1 Creation Date 8 Alph. File creation date in yyyymmdd 1 Creation Time 6 Alph. File creation time in hhmmss 1 Last Modification 8 Alph. Date of the last modification made in the file in yyyymmdd Date 1 Last Modification 6 Alph. Time of the last modification made in the file in hhmmss time INDRA. All rights reserved. EDITRAN/E 5.2 Page 8-5

28 EDITRAN/E 5.2 CICS Manual de usuario 8.ANNEX PRESENTATION TOTALS RECORD. There is one per presentation. It contains the data accumulated of the presentation file records. Level Name Length Fmt. Description 1 Presentation Session 32 Alph. Made up of Source (9) + Destination (9) + Application (6) + blanks (8). 1 Direction 1 Alph. Specifies the presentation direction. E: Transmission log group. R: Reception log group. 1 End Date 8 Alph. Presentation completion date yyyymmdd 1 End Time 6 Alph. Presentation completion time in hhmmss 1 Record type 2 Alph. 21 : Totals of the file records 1 Order Number 4 Nr. Zeros 1 Total Records 12 Nr. Total of records of the presentation files 1 Total Bytes 12 Nr. Total bytes of the presentation files 1 Total Bytes 12 Nr. Total bytes of the compressed files compressed 1 Compression relationship 4 Nr. % of compression achieved. INDRA. All rights reserved. EDITRAN/E 5.2 Page 8-6

29 EDITRAN/E 5.2 CICS Manual de usuario 8.ANNEX TRANSMISSION RECORD. Each presentation has a record for each transmission session used for the data presentation. With a maximum of 20. It contains data relating to the associated transmission session. Level Name Length Fmt. Description 1 Presentation Session 32 Alph. Made up of Source (9) + Destination (9) + Application (6) + blanks (8). 1 Direction 1 Alph. Specifies the presentation direction. E: Transmission log group. R: Reception log group. 1 End Date 8 Alph. Presentation completion date yyyymmdd 1 End Time 6 Alph. Presentation completion time in hhmmss 1 Record type 2 Alph. 30 : Indicates that it is a transmission record 1 Order Number 4 Nr. Zeros. 1 Transmission Session 32 Alph. In the environments where it s possible, the code of the Internal Session will be used. In the rest it will be formed with Source (9) + Destination (9) + Application (6) + blanks (8). 1 Start Date 8 Alph. Start date of the transmission session in yyyymmdd 1 Start Time 6 Alph. Start time of the transmission session in hhmmss 1 End Date 8 Alph. End date of the transmission session in yyyymmdd 1 End Time 6 Alph. End time of the session in hhmmss 1 Duration Difference in hours, minutes and seconds between the transmission end and start 2 Hours 3 Nr. Complete hours of the transmission duration 2 Minutes 2 Nr. Full minutes of the fraction of an hour remaining after subtracting the full hours from the duration of the transmission 2 Seconds 2 Nr. Seconds of the remaining minute fraction. 1 Incident Nr. 4 Nr. Number of incidents detected in the transmission. 1 Real transmission 6 Nr. Specifies the transmission duration in HHMMSS duration INDRA. All rights reserved. EDITRAN/E 5.2 Page 8-7

30 EDITRAN/E 5.2 CICS Manual de usuario 8.ANNEX TRANSMISSION TOTALS RECORD. There is one per presentation. It contains the accumulated data of the presentation transmission records. Level Name Length Fmt. Description 1 Presentation Session 32 Alph. Made up of Source (9) + Destination (9) + Application (6) + blanks (8). 1 Direction 1 Alph. Specifies the presentation direction. E: Transmission log group. R: Reception log group. 1 End Date 8 Alph. Presentation completion date yyyymmdd 1 End Time 6 Alph. Presentation completion time in hhmmss 1 Record type 2 Alph. 31 : Totals of the transmission records 1 Order Number 4 Nr. Zeros. 1 Transmission sessions 2 Nr. Number of transmission sessions used in the presentation number 1 Total duration Sum of the duration of each presentation transmission. 2 Hours 3 Nr. Complete hours of the transmission duration of the complete presentation 2 Minutes 2 Nr. Full minutes of the fraction of an hour remaining after subtracting the full hours from the duration of the presentation transmission. 2 Seconds 2 Nr. Seconds of the remaining minute fraction. 1 Total incidents 4 Nr. Specifies the total number of incidents detected in all the presentation transmission sessions. 1 Total real 6 Nr. Specifies the transmission total duration in HHMMSS transmission duration INDRA. All rights reserved. EDITRAN/E 5.2 Page 8-8

31 ecommerce Competence Centers Avda. de Bruselas Alcobendas. Madrid, Spain T T INDRA. All rights reserved. EDITRAN/E 5.2 Page 8-1