EDITRAN/XML SEPA 5.X. User Manual. Converter of modern format flat files into XML and vice versa CICS-IMS

Transcription

1 EDITRAN/XML SEPA 5.X Converter of modern format flat files into XML and vice versa CICS-IMS User Manual INDRA May 2018

2 CONTENTS 1. INTRODUCTION REQUIREMENTS AND INSTALLATION Requirements License file Regulation and restrictions To take into account Installation: CICS ZOS IMS COMMON ZOS (USER FILE) COMMON ZOS (JAVA) Software download Insert the package in the zos UNIX services Package installation FUNCTIONALITY DESCRIPTION Use of file lists by EDITRAN EDITRAN Setting Converter use cases Input-output data for converters Data passed to the converter through PARM Data passed to the converter through user file (ZTBGFDAT) XML to flat file Flat file to XML ADAPTATION OF TGSS ONLINE PAYMENTS File reception Confirmation sending JCLS AND PROCEDURES JCLS Procedures Before transmission After reception OTHERS Call to Java in command mode ANNEX Transformation with Warnings Server result codes INDRA. All rights reserved. EDITRAN/XML SEPA 5.X

3 1.INTRODUCTION 1. INTRODUCTION The SEPA regulation requires the following standards to be exchanged in XML format: SEPA Direct Debits in electronic file - Basic Scheme (19.14) SEPA Direct Debits in electronic file - B2B Scheme (19.44) Orders in file for sending transfers and cheques in euros (34.14) Some converters have been developed that allow: o Transforming the files in modern flat file format (record length 600) into XML o Transforming XML into files in modern flat file format (record length 600) o o Generating confirmation or rejection xml from a received xml (SCT and SDD) Sending a new version of CustomerDirectDebitInitiationV02 (pain ) and generating a version of C published by CECA. o XML SEPARATOR o Flat file SEPARATOR These converters can be called: In the procedure before transmission, with a new procedure (ZTBGP1CX) leading to a new step, before the step A1P. In the procedure after reception, with a new procedure (ZTBGP4CX) leading to a new step, following the step A4P and ZTBGLFE. In a jcl provided for this purpose: ZTBGJXML (valid for clients who wish to launch the converter for files not sent/received by EDITRAN). The converters (ZTBXBXBXML program), call a TCP client program (ZTBXBITS), which connects against the java server, residing on the UNIX services of the zos. They indicate: 1. Data for connection to the server a. IP and port of the java server b. Timeout of answers of the java server 2. Request data a. Function (X) flat file to xml, (P) xml to flat file b. Dsname of input file c. Dsname of output file d. Translation table (only if necessary) INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 1-1

4 2.Requirements and installation. 2. Requirements and installation Requirements. 1. The user must create a file (or n), with certain parameters to go to the converter (detailed in this document). 2. EDITRAN or higher version available. 3. License. To have contracted the EDITRAN/XML product for SEPA. 4. JAVA. a. At least, IBM 31-bit SDK for z/os, Java Technology Edition, V6 must be installed and there must have access to JZOS for access to MVS files. For this, the files are in $JAVA_HOME/lib/ext. b. A TCP java server of the UNIX services, which must have an address and a port to listen to the requests made from the EDITRAN in MVS. c. Access to the UNIX services of the ZOS EDITRAN does not validate the application files; it only does the conversion from flat file to XML or from XML to flat file License file The EDITRAN/SEPA program needs a license file called licenciasepa.dat to work. It must be located in the SEPA root folder. This license file must be requested to the EDITRAN Support indicating the hostid and the operating system of the machine, which is obtained in two different ways: 2.3. Regulation and restrictions. Executing the checklic.bat/checklic.sh file in the SEPA/scripts folder of your Operating System. You must run this command file from the folder where it is located and return the result of checking the license on the screen. If an attempt is made to run the EDITRAN/SEPA program without a license, the program will fail due to an incorrect license and the hostid and operating system of the machine will remain in the log. Depending on their format, flat file or XML, the files processed by EDITRAN/SEPA (both the one with the source data and the file resulting from the transformation) will comply with one of the following standards: Flat files: SEPA 14 (new format with length records 600) Orders in file for issuing transfers and cheques in euros Document. Set of Banking Rules and Procedures Nr , November 2012 version. "SEPA Direct Debits in electronic format - Basic Framework" Document, Set of Banking Rules and Procedures Nr , November 2012 version. "SEPA Direct Debits in electronic format - B2B scheme" Document, Set of Banking Rules and Procedures Nr , November 2012 version. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-1

5 2.Requirements and installation. XML files: orders in ISO format Document: Orders in ISO format for issuing transfers and cheques in Euros. Set of Banking Rules and Procedures. Implementation Guide v1.0, November Follow the pain xsd scheme. Document: Orders in ISO format for issuing SEPA Direct Debits - Basic Scheme. Set of Banking Rules and Procedures. Implementation Guide, November It contains four different messages: Presentation of debits, it follows the pain scheme Operation rejection, it follows the pain scheme Refund, it also follows the pain scheme Return of funds, it follows the pain scheme Document: Orders in ISO format for issuing SEPA Direct Debits - B2B Scheme. Set of Banking Rules and Procedures. Implementation Guide, November It contains the same four messages as the previous one and follows the same schemes. To take into account When using EDITRAN/SEPA the user must know: In the case of flat files and XML files, the program does not validate the consistency of their content (sum of the total of the amounts, etc.). However, it does validate the format in both cases: correct sequence of records in flat file format and validation against the corresponding scheme in XML format. As for the content, the definitions of the new flat standards are not completely symmetrical with respect to the XML standards, so there will be concepts and fields that will be lost when making the conversions in both directions. This particularity should not be understood as a limitation or defect of EDITRAN/SEPA, but it is a characteristic of the standards themselves. This "loss of data" does not in any case refer to essential or mandatory concepts, but to extra information that is included in the XML standards. Taking into account this asymmetry between the formats, EDITRAN/SEPA always seeks to preserve the maximum amount of information when transferring data from one format to another. For example, if a certain field is optional in the XML format, as long as the information is contained in the source flat file format, the converter will include it in the destination. Some entities have defined particularities when generating their files, both the flat files and the XML. As long as these restrictions refer to the content and do not fail to comply with formatting factors (structure, lengths, etc.), they will have no impact on the use of the converter. In the XML format, there is a message for the payment status information (according to the pain scheme) for which SEPA has not defined a standard in flat file format; therefore, EDITRAN/SEPA will not be able to transform this message. There are still entities that continue to send the formats of the old AEB notebooks, with lengths 72 (AEB 34) and 162 (AEB 19). They will be able to do INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-2

6 2.Requirements and installation. so until February 2014, although these files will not be processed by EDITRAN/SEPA. As an example, EDITRAN will transmit: o pain Direct Debit Start (received by EDITRAN from business applications) o pain Status Communication In the pain format Transfer Status Communication (sent to business applications), there is no flat standard, therefore, EDITRAN will not transform this content. o pain Cancellation Request o pain Refund Communication (sent to business applications) o pain Transfer start (received by EDITRAN from business applications) o Version UPGRADE of C published by CECA. It consists of adapting the Sepa xml debit converter to include new labels that allow extended concepts to be completed (up to 640 characters) to generate a new C notebook that differs from the current one in that it incorporates a new type of record to include concepts with more than 140 characters that are currently allowed. There will therefore be a converter (licensed) capable of processing a new version of CustomerDirectDebitInitiationV02 (pain ) and generating a version of C published by CECA. o XML** SEPARATOR This functionality is an addition to EDITRAN/SEPA. Therefore, this functionality also requires an additional license. If you do not have this additional license and you are interested, please contact the EDITRAN Support. The Xml files are not intended to be nested within a single file, as the resulting file is not a valid file. In response to some clients, a new functionality has been added that converts these files with several nested Xml files into a file with their corresponding nested flat files. o FLAT FILE SEPARATOR** Analogous to the above functionality, the converter can process flat format input files that include several logical files. In this case, the result of the conversion will be a file whose content may be a single logical XML file or several, depending on how the param.juntar.xml parameter described in section or in the ZTBGFDAT parameter file has been set. First, it looks at the parameter file ZTBGFDAT; if it is not completed, it looks at Configuracion.properties. If it does not appear either, a defect appears. To use the separator functionalities that require specific licenses, instead of starting EDITRAN/SEPA using the start.sh and stop.sh scripts, the alternative scripts included in the /scripts folder; startseparador.sh and stopseparador.sh must be used. These scripts replace the previous ones. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-3

7 2.Requirements and installation. Before these scripts can be used, they must be set up first. The way to configure them is exactly the same as in the scripts for EDITRAN/SEPA (section step d) and e)). **These two functionalities need to generate some temporary auxiliary files in the UNIX part that are deleted at the end of the process. The name of the auxiliary file is always created with the input name followed by timestamp. As for the temporary directory, if nothing is indicated, it will take by default the /tmp directory from the machine. If another one is required, it is passed with the java.io.tmpdir variable in the call to JAVA (at the start or by command). o Automatic reply message This field is used to generate response messages when certain SEPA standards are received, although it can only be used for XML to flat file conversions of the 3414 and 19 Presentation type standards where this file is generated. The code returned in <StsRsnInf> informs if the conversion (ACCP) has been possible or not (RJCT). The value of this field is the name of the automatic reply file. By default, the response file is not created. EDITRAN does not convert the standard 57 (bank teller payments) either. EDITRAN, with the converters, always processes flat files in "modern" format, with record lengths of 600. There are still entities that use the old format, with length 72 or 162, and these files are not processed in the converters described. Some entities enter "particularities" in the XML or flat files. In principle, these adaptations should be technically assessed, whether they are possible with the distributed software, and if not, whether they should be economically assessed. If they refer to the content of xml files, to the data, but they do not affect the structure required by the scheme, field lengths, etc., in principle, the converter could be used as it is. The entities follow their own regulations when creating the files, although certain aspects must be taken into account: One is that we must be aware that the information collected by the xml is a little more extensive than the information that can host the flat file. Therefore, these data (few) are lost when the transformation is in that direction, or they do not appear when they are in the opposite direction. Another aspect is the opposite. For example, some regulations may indicate that the <CtrlSum> label will not be used in the xml file header. This label gathers the sum of the amounts of all the file operations. In fact, according to the scheme is not mandatory to fill it in, however our converter always adds it, since in the flat file this data is mandatory and the guideline we are following, for the moment, is to lose the minimum possible information in both directions. Another example. The priority of the instruction is not in the flat file. Therefore, the xml that we generate do not include that data, so the defect that is the normal priority is assumed, and therefore if the xml that we process has got it, it is lost in the flat file. In general, the xml file is prepared to collect more information than that specified in the flat standards. For example, in the xml standard of standard 34 there is a message identifier that is lost when taking it to the flat file. In the xml, the creation date and time are also collected, while in the flat file it is only possible to store the date. The flat standard does not include the role of the INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-4

8 2.Requirements and installation. presenter, although in the xml standard it is possible to give information. The payment method that is included in the payment balance record of the flat standard cannot be transferred to the xml standard. In the flat standard, there is no field in which to report on the BIC of the ordering entity. This data is specified in the xml standard. Functionality upgrade: To generate a c version published by CECA. It allows converting SEPA format flat files (record length 600) into XML ISO and vice versa. This upgrade consists of adapting the Sepa xml debit converter in order to include new labels that allow extended concepts to be completed (up to 640 characters) to generate a new C notebook that differs from the current one in that it incorporates a new type of record to include concepts with more than 140 characters that are currently allowed. There will therefore be a converter capable of processing a new version of CustomerDirectDebitInitiationV02 (pain ) and generating a version of C published by CECA. XML Separator This functionality is an extension to EDITRAN/SEPA that converts files with several nested Xml files into a file with their corresponding nested flat files. Flat files separator This functionality is an extension to EDITRAN/SEPA that converts files with several nested flat files into a file with their corresponding nested XML files. Adaptations for TGSS signed files This functionality is an extension to EDITRAN/SEPA that converts files with the peculiarities of the Social Security Treasury. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-5

9 2.Requirements and installation Installation: CICS. If an EDITRAN/CICS license is received: License (if this functionality is contracted). To install it, the ZTBLJG02 jcl must pass. CICS Executables: ZTBPOIF5 Batch Executables: ZTBXBXML, ZTBXBITS, ZTBGBGPG and ZTBLBLLI Procedures: ZTBGP1CX and ZTBGP4CX Jcls: ZTBGJXML ZOS IMS. If an EDITRAN/IMS license is received. License (if this functionality is contracted). To install it, the ZTBLJG02 jcl must pass. Batch Executables: ZTBXBXML, ZTBXBITS and ZTBGBGPG Procedures: ZTBGP1X and ZTBGP4X Jcls: ZTBGJXML COMMON ZOS (USER FILE) The user must create a ZTBGFDAT file (or n files), with certain parameters to go to the converter (detailed in this document). INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-6

10 2.Requirements and installation COMMON ZOS (JAVA) To install it, the following actions will be carried out: Software download. Go to the website and select SOFTWARE User: indra, psw: EDITRAN Select zos and download the XML software Insert the package in the zos UNIX services Sending the EDITRANSepaXml.rar package to the USS in binary mode. You can use any file transfer utility, such as ftp. Example of uploading: 1- We enter it in USS through the commands (example of uploading EDITRANSepaXml.rar): a. cmd b. ftp ip destination (it will ask for tso user and password) c. cd /u/editranxsepa (destination directory where we will upload the application). d. binary (ftp in binary) e. lcd c:\ (source directory where the.rar is) f. put EDITRANSepaXml.rar quit 3.- We see what remains in the USS directory. /u/ EDITRANxsepa: >ls -l total rw-r KI10139 KISNCE Jun 25 17:07 EDITRANSepaXml.jar INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-7

11 2.Requirements and installation Package installation. a) Unzip the EDITRANSepaXml.tar file in the installation folder created for this purpose, e.g. / EDITRANxsepa, leaving the following directory structure from this one: SEPA --conf --doc --lib --logs --scripts b) The EDITRAN/SEPA scripts are located in the scripts/zos folder. First, we should check that the checklic.sh, start.sh and stop.sh files have execution permissions. c) The checklic.sh programme is executed from the directory where this file is located. It asks us if we have a license file. If it is correct and we do not have a file, it indicates the hostid and the name of the OS with which we must request an EDITRAN support license. Once the license file is received, it must be sent, in binary mode, to the USS. d) Next, the start.sh file is edited and the following variables get their value: PWD=/ EDITRANsepaxml (installation path, where it has been unzipped) IP=" " (IP where the server boots) PORT="7774" (PORT where the server is listening) JAVA_HOME="/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit" (Java installation path) e) Then, the stop.sh file is edited and the following variables get their value: PWD=/ EDITRANsepaxml (installation path, where it has been unzipped) f) Once this has been completed, it is already possible to boot the application by running the command:./start.sh g) To check that the Server has started correctly after executing the command, we edit the logs/out.log file. It should include the following traces (the ones we have configured in the file should appear in the port and the IP): 17/04/ :16:40, INFO [main] servers.threadpooledserver main - Starting Server 17/04/ :16:40, INFO [Thread-3] servers.threadpooledserver openserversocket - Port: /04/ :16:40, INFO [Thread-3] servers.threadpooledserver openserversocket - LocalSocketAddress:/ : /04/ :16:40, INFO [Thread-3] servers.threadpooledserver openserversocket - InetAddress:/ h) To stop the process:./stop.sh i) There are Z/OS files: EDITRANSepaXml.tar to test a possible installation from scratch. j) There is a server log file where we can see the evolution of the error requests, etc. (logs/out.log). k) There are 3 files in the conf directory: Configuracion.properties (Optional) defines certain optional parameters of the EDITRAN/SEPA program. In z/os this file is not used because they are JCL parameters. If the JAVA is called directly, at least the language of the machine must be completed. The different parameters that can be set up are: INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-8

12 2.Requirements and installation. Machine language: It can be A (ASCII) or E' (EBCDIC). It must be deactivated by default, and the EDITRAN/SEPA converter must calculate it automatically. Alphabet: The flat file of the conversion is written or will be written with this alphabet. The possible values are those charset values that allow Java (for example for Java 1.6 the allowed encodings come in your web page). By default, it uses the alphabet of the machine where it is executed. Validate Xml: it is used to indicate if you want to validate XML against its scheme, being its possible values S (always validate), P (validate only in conversions from XML to Flat File), X (validate only from Flat File to XML) or N (Never validate). The default value is S. Attention: if this validation is deactivated, the files obtained may include errors. Information in the free field: In an Xml conversion to Flat File there are certain non-convertible fields. This field is used to include this information in the free zone of the flat file. The information written in the free zone is explained in another section of the manual. Its value can be S (Yes) or N' (No), by default not typing in the free field. To maintain output file in case of error: In an incorrect conversion, the output file is not created because its value is invalid. This field indicates if we want to keep the output file even if the conversion was incorrect, being its possible values "S" to keep it and "N" to delete it. By default, the output file is deleted. Automatic reply message: This field is used to generate response messages when certain SEPA standards are received, although it can only be used for Xml to Flat File conversions of the 3414 and 19 Presentation type standards, where this file is generated. The value of this field is the name of the automatic reply file. By default, the response file is not created. Remove validations: To use this parameter there must be a license to do it, as it is a field specially developed on request. It is used to ignore mandatory Xml validations that are not imposed by the XSD scheme, but by the SEPA Spain standard. The field can be validated as "S" to ignore the Xml mandatory validations by SEPA Spain, and as "N" to validate the SEPA Spain standard. It does not ignore them by default. param.juntar.xml (Join XML): This parameter allows defining the behaviour of the converter in transformations of flat file format input files that include more than one logical file. There are two possibilities: a) whenever possible (the date of creation is the same for all of them, the payer/creditor identification, etc.), unify all the information of each input logic in a single logical and physical XML output file. For this option, the value S will be set. b) to obtain an output file with as many logical XML documents as flat file format logical files has the original. The value N will be indicated for this option. The default value for this option is S. Attention: to set the parameter to N, the corresponding license is required (see section of this manual). param.cabecera (Transmission Header): For XML conversions to flat file of the standard, this parameter indicates whether an additional header is to be included at the beginning of the resulting file. The possible values of the parameter are T for writing the header of the Social Security General Treasury (see section 10 of this manual) and N for not doing so, this being the default value. When this INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-9

13 2.Requirements and installation. parameter has a T value, the converter ignores the param.resp.auto parameter for XML files. Entidades.properties(optional) is the Template of entities. The use of this file is optional and it configures an extra data source necessary for the conversion from the flat file format to XML to be complete and correct. When this file is not defined, or the data searched for is not found, the corresponding labels of the XML formats will be empty or with the literal "NOTPROVIDED" as allowed by the standard in each case. In particular, it enables to complete the BIC of the payer's entity of the ISO transfer standard as well as the BIC of the creditor's entity of the ISO debit standard. As many entities as necessary can be added to the list. The file shall contain only relationships between BIC codes and the pair of "entity + office" numbers to which they correspond. For Spanish entities, the number "entity + office" indicated will be searched in the positions from 4 to 11, starting with 0, of the IBAN accounts (starting with "ES") corresponding to the figure of the BIC you wish to complete (creditor for debits and payer for transfers) in the corresponding records of the file in flat format. Location example: ES Initial content of the file: #Ejemplo #bic.0=abcdefghxxx #entyof.0= bic.1= entyof.1= bic.2= entyof.2= The four digits of the office can be replaced with the'*' mask to associate all the offices of an entity to the same BIC. #entyof.0= O #entyof.0=0123* -- EntidadOficina -- Entidad* The file can also be used with Portuguese accounts. log4j.properties is the information of the log characteristics. By default, the log is configured in such a way that for each file conversion, two pieces of log information are generated in the logs folder, one in the general log of EDITRAN/SEPA called out.log, and another specific log for each file with the same name as its input file. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-10

14 2.Requirements and installation. This file is editable to adjust it to what the client may request. For example, if we want to perform the following operations: - To deactivate some log: Delete its name (EDISEPAGENERAL or EDISEPAFICHERO) from the log properties (log4j.logger, log4j.logger.iaik, log4j.logger.javax, log4j.logger.com.indra.mmdd o log4j.logger.com.indra.mmdd.editran.parser). - To edit the general log: From the log name we can modify (log4j.appender.edisepageneral.file) its maximum size (log4j.appender.edisepageneral.maxfilesize) or the number of historical files that are saved (log4j.appender.edisepageneral.maxbackupindex). - To add some more logs: If you want to perform this task, you must follow the log4j log configuration at your discretion. Initial content of the file: # To deactivate any of the logs you must delete its name (EDISEPAGENERAL o EDISEPAFICHERO) in the log properties log4j.logger, log4j.logger.iaik, log4j.logger.javax, log4j.logger.com.indra.mmdd or #log4j.logger.com.indra.mmdd.editran.parser log4j.logger = INFO, EDISEPAGENERAL log4j.logger.iaik = INFO, EDISEPAGENERAL log4j.logger.javax = INFO, EDISEPAGENERAL log4j.logger.com.indra.mmdd = INFO, EDISEPAGENERAL log4j.logger.com.indra.mmdd.editran.parser = INFO, EDISEPAFICHERO log4j.additivity.com.indra.mmdd =false # General program log. It includes all file conversions. If you want to modify the log size you must #modify the log4j.appender.maxfilesize property. If you want to modify the number of saved historical log files #of log modify the log4j.appender.maxbackupindex #property. log4j.appender.edisepageneral=org.apache.log4j.rollingfileappender log4j.appender.edisepageneral.file=logs/out.log log4j.appender.edisepageneral.maxfilesize=2000kb log4j.appender.edisepageneral.maxbackupindex=5 log4j.appender.edisepageneral.append=true log4j.appender.edisepageneral.layout=org.apache.log4j.patternlayout log4j.appender.edisepageneral.layout.conversionpattern=%d{dd/mm/yyyy HH:mm:ss,SSS} %5r %-5p [%t] %c{2} %M - %m%n # Log specific to the conversion of each file. The final name is "nombredeficherodeentrada.log", located in the #logs folder. log4j.appender.edisepafichero=org.apache.log4j.rollingfileappender log4j.appender.edisepafichero.append=false log4j.appender.edisepafichero.layout=org.apache.log4j.patternlayout log4j.appender.edisepafichero.layout.conversionpattern=%d{dd/mm/yyyy HH:mm:ss,SSS} %-5p - %m%n INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 2-11

15 3.Functionality description. 3. Functionality description Use of file lists by EDITRAN. EDITRAN allows the transmission of several files by the same session. To send: To receive: Some clients use a list of files (ZTBGFCAR, see TABLE 1 format) to upload them, as their files have different names in each of them. Therefore, they create a daily list of files of each presentation to be sent. This list is passed on to the step prior to transmission. Normally, to be able to use a single procedure with all the nodes, the dsname of the file list is made up of variables recognizable by the procedure (source, node and application). Other customers always use the same dsnames of files to be sent (each transmission has a different content), so they decide to indicate the dsname of the files to be sent in their own product profiles. If nothing is indicated in the EDITRAN profiles, EDITRAN downloads the received files with a default name. If something is indicated in the EDITRAN profiles, EDITRAN downloads the files received with the name indicated. In all cases, the procedure after reception, step ZTBGGLFE, provides the user with a file that is a list of files received and downloaded (ZTBGFLFE, see TABLE 2 format). Table 1. Content of the ZTBGFCAR file, fixed file 80 in length, which contains the transmission application files and their characteristics. The content is as follows (one record per file): Level Name Length Type Description 1 Physical name 44 Alph. Physical name of the application file 1 Filler 1 Alph. Separation hyphen 1 File format 1 Alph. Application file format: R : Record, M : Modified 1 Filler 1 Alph. Separation hyphen 1 Source data 1 Alph. Original data language: language A : Ascii, E : Ebcdic, B :Binary 1 Filler 1 Alph. Separation hyphen 1 Translate in 1 Alph. Language in which the data are sent: transmission A : Ascii, E : Ebcdic, N :No translation 1 Filler 1 Alph. Separation hyphen 1 Compression 1 Alph. Compression: F Compressed, N Uncompressed 1 Rest of record 28 Alph. Reservation area INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-1

16 3.Functionality description. Table 2. Content of the ZTBGFLFE file (list of files received, currently left by the procedure after reception), fixed file 130 in length. The content is as follows (one record per file): Level Name Length Type Description 1 File Area 130 Alph. 2 Physical name 44 Alph. Physical name of the downloaded application file 2 Filler 1 Alph. Separation hyphen 2 Presentation-enddate 14 Nr. Date-time of presentation end in AAAAMMDDHHMMSS format 2 Uploaded file- Type- 4 Nr. Type of output or uploaded file FIJO VBLE VEXP BINA 2 Uploaded-datalanguage 1 Alph. Language of uploaded data: A : Ascii, E : Ebcdic, B :Binary 2 Compression 1 Alph. Indicates whether the file was uploaded with compression: F Compressed, N Uncompressed 2 Filler 1 Alph. Reservation area 2 Source physical 44 Alph. Physical name of the source application file name 2 Applic.file bytes 12 Nr. Application file bytes 2 Rec. length 6 Nr. Lrec 2 Filler 1 Alph. Reservation area 3.2. EDITRAN Setting. When transmitting SEPA files (XML), these files are in UTF-8 and they cannot be translated, so in the EDITRAN sessions that use this type of files, it is required to indicate: o Original data language: Binary o Translate in transmission: No o Translate in reception: No o Transmission conversion table: Spaces. o Reception conversion table: Spaces o Before transmission (a new procedure is provided) o After reception (a new procedure is provided) INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-2

17 3.Functionality description. EDITRAN allows receiving several files and putting them together in a single file. In case of SEPA transformation, it is not possible to do this, and therefore, Single file in reception NO must be specified (and adapt the outgoing DSNAME, if any). In addition, in the case of receptions, it is recommended to do the following: EDITRAN allows receiving n files in each transmission. The user has several options to act on the field RECEPTION APPLICATION FILE PHYSICAL NAME of EDITRAN/G profiles: 1.- Do not indicate anything. In this case, if n files are received, EDITRAN downloads them with a default name. Example of receiving 2 files: Prefijo.lll.Rxnnnnnn.Rnnx.Aaaaaaa.Rmmmmnn Prefix : File Installation Prefix (EDITRAN/G General local environment) lll : Alias (EDITRAN/P General local or secondary environment) Rxnnnnnn : One R and the first 7 characters of the remote code. Rnnx : One R and the last 3 characters of the remote code. Aaaaaaa : One R and the presentation application name Rmmmmnn : One R and 4 digits of the Exchange Session number and two digits of the order number of the application file. In this case, it is recommended to indicate in PHYSICAL NAME the following (to differentiate several files in the same transmission and so that the final flat files end up without the last pointer, XML): Prefijo.lll.R%R.nnx.A%A.R%N%C.XML 2.- The user should indicate a fixed dsname (note the above mentioned limitation stating that several files were received and downloaded to a fixed dsname). In this case, it is recommended to indicate dsname-fijo.xml 3.- The user should indicate a dsname with variables. In this case, it is recommended to indicate dsname-con-variables.xml Note that in all cases, the name received so far +.XML has been indicated. Note also that the files downloaded by EDITRAN are now XML, and the converter will convert them to fixed files to be processed by your application. Therefore, we will try to leave in your application the same dsnames as what you received until now. In the ZTBGFDAT file (explained later), if nothing is indicated in the output DSNAME, it means that the file downloaded by EDITRAN was called xx.xml and the one transformed into flat file will be called xx, so the user application will process the same files it processed until now (identical dsnames). INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-3

18 3.Functionality description Converter use cases. There are three use cases to call the converters: 1. Procedures before transmission (A1P). In this case, it is proposed to use the converter in a previous step to A1P, so that a solution can be provided with a single new procedure (ZTBGP1X) to all the EDITRAN presentation sessions that require sending XML files. In addition, a solution is provided to make this converter transparent to the user with respect to its previous load operation (flat files). 2. Procedures after reception (A4P). In this case, it is proposed to use the converter in a step after A4P and LFE, so that a solution can be provided to all the EDITRAN presentation sessions that require receiving XML files and want to convert them into FLAT FILES. In addition, a solution is provided to make this converter transparent to the user with respect to its previous download operation (flat files). 3. JCL. In this case, a specific ZTBGJXML jcl can be used, to pass any file from the entity to XML or FLAT FILE. In short, the converters from flat files to XML and from XML to flat files have been developed: So that they can be used for files transmitted by EDITRAN. In this case, the most common will be to use 2 new standard product procedures: one before transmission (ZTBGP1CX) and one after reception (ZTBGP4CX). So that they can be used to process any other file of the installation in this way. In this case, the most common is to use a supplied ZTBGGJXML jcl Input-output data for converters. Output data In all cases, a DD will be indicated. This list corresponds to the output files generated by the converter (not to be confused with the list of input files that the user has been able to create and that could even reach the A1P before). This list of output files will be the one that must be in step A1P (in addition to pointing to the variable LF=S). To see the format of the ZTBGFCAR refer to table 1. //ZTBGFCAR DD DSN= KI.PMED.&L0..R&R1..R&R2..A&AP..LISTFICX,DISP=SHR In case of procedure after reception or jcl, this list contains the final DSNAME of the generated flat files. Therefore, if the user until now indicated a list of files to the A1P step, it will be included as input data to the converter. The converter generates a list of files (different from the previous one), which will be the one that reaches the A1P. In addition, the converter can generate a ZTBXFSAL with the result of the files passed to the converter (see table 3). If you do not want to include the card or enter SYSOUT *. //ZTBXFSAL DD DSN= KI.PMED.&L0..R&R1..R&R2..A&AP..ZTBXFSAL,DISP=SHR INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-4

19 3.Functionality description. If the converter is being used integrated to EDITRAN, you can obtain the messages in the LOG of EDITRAN/G with the previous and subsequent procedures, including in the converter step its DD card. If you do not want this functionality, do not include the DD card. //ZTBGFLOG DD DSN=PUNTERO.INDRA.ZTBGFLOG,DISP=SHR LOG Example: U ZTB CARGAC 05/02/ :29:29 KI0F6AEA ERROR LLAMANDO ZTBXBITS TRANSFORMACION FICH. U ZTB CARGAC 05/02/ :29:30 KI0F6AEA Error en el marshaller del xml Table 3. Content of the ZTBXFSAL file, fixed file 252 in length, whose contents are the files that pass through the converter, and the conversion result. The content is as follows: Level Name Length Type Description 1 Input physical name 44 Alph. Physical name of the application file entering the converter 1 Filler 1 Alph. Separation hyphen 1 Output physical 44 Alph. Physical name of the application file name generated by the converter 1 Filler 1 Alph. Separation hyphen 1 Converter result 4 Nr. Result returned by the converter code 1 Filler 1 Alph. Separation hyphen 1 Error text 80 Alph. Text of the error message returned by the converter 1 Rest of record 77 Alph. Reservation area Input data To call the converters, we will use: Data via parm Data entered in a user file, (which can always be the same for everything or if it is not valid, it can be built with variables). This ZTBGFDAT file can be different for each session. In that case, in the procedure, we will specify a DSNAME with variables, for example source, node, application, etc. Example: //ZTBGFDAT DD DSN=KI.PEPE.&L0..R&R1..R&R2..A&AP..ZTBGFDAT,DISP=SHR INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-5

20 3.Functionality description Data passed to the converter through PARM. The following data must be passed to the converter via PARM: a. Source. Source Rbe. In case of non EDITRAN JCLS, the entity code is entered. Otherwise, the input variable is passed to the procedure (&L1&L2). b. Destination. Destination Rbe. In case of non EDITRAN JCLS, the code of some example destination entity is entered. Otherwise, the input variable is passed to the procedure (&R1&R2). c. Application. EDITRAN/G Application. In case of non EDITRAN JCLS, the code of some example application/g is entered. Otherwise, the input variable is passed to the procedure (&AP). d. Function: (X)- Flat file to XML, (P)- XML to flat file e. Type of input file (in function X it refers to the FLAT FILE. In function P, it refers to XML): i. (F) File. The JCL or procedure includes an input file with DSNAME. ii. (L) List. The JCL or procedure includes a list of input files. 1. In procedures before transmission (flat file X function to xml). If you use file lists in the upload, it is recommended to use this option. 2. In procedures after reception (xml P function to flat file). The standard EDITRAN procedure leaves a list of received files, so it is recommended to use this option as input data to the XML to flat file converter step. iii. (P) Profiles. The jcl or procedure does not contain a file or a list of input files. The transmission application files are taken from what is in EDITRAN profiles. 1. In procedures before transmission. If you use EDITRAN profiles in the upload, it is recommended to use this option. 2. In procedures after reception (P function, xml to flat file), this option does not make sense. f. DSNAME of the input file (it cannot be a partitioned member) i. If input file type is P, nothing will be indicated. ii. If input file type is F, a file name (directly or with variables) is entered here. iii. If input file type is L, a list of the files to be transformed (see table 1) is displayed here. If the user already used a list of files, this name will be indicated here. Example of PARM, in a procedure before transmission with file list: // PROC ORIGEN=,FUNCION=,L0=, // L1=,L2=,R1=,R2=,AP=,LF=,FU=,TI=,FI= // SET LF=S INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-6

21 3.Functionality description. // SET FU=X // SET TI=L // SET FI= KI.EGDC.&L0.R&R1.R&R2.A&AP.LCAR //PASO01 EXEC PGM=ZTBXBXML, // PARM='&L1&L2&R1&R2&AP&FU&TI&FI/CBLQDA(ON)' //ZTBGFDAT DD DSN=KI.EIDC.ZTBG.ZTBGFDAT,DISP=SHR //ZTBGFCAR DD DSN=KI.PMED.R&R1..R&R2..A&AP..LISTFICX, //ZTBXFSAL DD DSN=KI.PMED.R&R1..R&R2..A&AP..ZTBXFSAL, We are indicating that the session is L1+L2 (source), R1+R2 (destination), AP (application), (FU)nction X (flat file to xml), (TY)pe:(L)ist of files and FI (dsname of the list is KI.EGDC.xxx.Ryyyyy.Ryyyyyy.Ryyyyyy.Azzzzzzz.LCAR) (where xxx is the local environment alias, yyyyyyyyyy is the remote code, zzzzzz is the application). Also, the variable LF = S is entered, because the step A1P will require it. For loads, in ALL cases (LIST (L), FILE (F), PROFILES (P)) the DD ZTBGFCAR must be indicated. In turn, it must be in the step A1P. In addition, it must be indicated to delete it before (or later) and the variable LF=S must be entered in the procedures. This ZTBGFCAR is the list that contains the XML that EDITRAN will load (not to be confused with the list of files that the user can provide to the converter) or the list of TRANSFORMED files (in case of launching JCL or after reception). In downloads a list of ZTBGFLFE files is received from the step A4P (created by EDITRAN). Therefore, PL&&LFE should be always indicated. The converter step will create a new list of transformed ZTBGFCAR files in all cases. When this converter is launched outside of EDITRAN, (in a separate JCL), it is normal to use F input file type (&TI=F), as a file name can be included directly (&FI). When this converter is launched inside EDITRAN (embedded in the procedures before transmission and after reception): o In procedures before transmission (uploads): If the user is already creating a list of files, e.g. KI.EGDC.xxx.Ryyy.Ryyyyyy.Azzzzzz.LCAR, he should continue to do so as follows, indicating the name in the &FI variable and indicating &TI=L : If the user uses EDITRAN profiles for the loads, he should continue to do so normally, indicating &TI=P. Normally, option F will not be used, as this will probably involve generating a different procedure for each presentation session. In all cases, the converter generates a new list of files that will be passed to step A1P. This list of files is generated with the name that we have entered in the DD //ZTBGFCAR DD xxxxx. o In procedures after reception (downloads): INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-7

22 3.Functionality description. The converter step will create a new list of transformed ZTBGFCAR files in all cases Data passed to the converter through user file (ZTBGFDAT). In all cases, it is necessary for the user to create a file (or n) with certain parameters that will normally always be the same. This file is called ZTBGFDAT and it is a flat file of lrecl 86. The content of this file is as follows: Lev el Name Type Lengt h Position Use Description 1 Record Type Nr. 1 1 Mandatory Type of record: 0-Java server connection data 1-Transformation data for FLAT FILE to XML 2-Transformation data for XML to FLAT FILE 3- Record of confirmation-refusal of debits and transfers *-Commented registration 2 Records Type 0 Java server connection data 3 Separator hyphen Alph 1 2 Optional Hyphen 3 IP or DNS of the Java server Alph Mandatory Ip xxx.xxx.xxx.xxx or dns of the Java server. Adjusted to the right. 3 Separator hyphen Alph 1 67 Optional Hyphen 3 Java server port Nr Mandatory Java server listening port a Separator hyphen Alph 1 73 Optional Hyphen 3 Server standby seconds Nr Mandatory Maximum seconds ( ) in which the tcp client waits for a response from the java server. If 999 is specified, the TCP client waits for no set time. 3 Separator hyphen Alph 1 77 Optional Hyphen 3 Free information Alph 1 78 Optional Value: S Enter values in the free area of the flat file N Do not incorporate values Defect N 3 Separator hyphen Alph 1 79 Optional Hyphen 3 To maintain output F. Alph 1 80 Optional To maintain the output file if error Value: S the output file is not deleted N the output file is deleted Defect N 3 Separator hyphen Alph 1 81 Optional Hyphen 3 Remove XML Alph 1 82 Optional Optional. If this field is not included, the Spain SEPA default option is N Validations Value: S It removes SEPA Spain validations N Puts the validations of SEPA Spain 3 Separator hyphen Alph 1 83 Optional Hyphen 3 Validate XML Alph 1 84 Optional Optional. If this field is not included, the default option is S Value: X Validates the XML generated by the converter P Validates the XML that enters the converter S Validates the XML in both directions N Does not validate XML under any INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-8

23 3.Functionality description. circumstances Attention: if you deactivate this validation, the files obtained may contain errors. 3 Separator hyphen Alph 1 85 Optional Hyphen 3 TGSS Header Alph 1 86 Optional Optional. If this field is not included, the default option is N Value: T It is a TGSS conversion with FF N SEPA normal conversion (non TGSS) Attention: by activating this parameter all the that enter the converter will be considered TGSS and will try to set the header. No automatic confirmation will be generated even though it is indicated in this rec type 3 file. 2 Records type 1 Transformation data from FLAT FILE to XML 3 Separator hyphen Alph 1 2 Optional Hyphen 3 Output file DSNAME (XML DSNAME ) Alph Mandatory -optional 3 Separator hyphen Alph 1 47 Optional Hyphen 3 Character table of the source application file Dsname of the transformed XML file. In this case, as there may be several transformed files: 1.-The use of variables known by EDITRAN is admitted, for example, Source, Destination, Application, YEAR, MONTH, DAY, SOURCE DSNAME, etc. (See table 3). 2.-A fixed name can be entered 3.-If nothing is indicated (spaces), EDITRAN creates output files with the name: DSN- ENTRADA.XML. This is the recommended option, because the converter will automatically create a list of files that will be loaded by EDITRAN, so there is no need to modify profiles. Alph Optional Name of the table of characters in which the source file is located. If nothing is specified, the zos table where we are running is taken by default (usually ISO ). The supported tables appear in the following link: cs/technotes/guides/intl/encoding.do c.html l 3 Separator hyphen Alph 1 66 Optional Hyphen 3 Output file size Nr Optional Size of the output file in bytes. If nothing is specified, EDITRAN creates by default an output file of 99,999 bytes. If any value is specified, EDITRAN calculates the space to allocate the output file in the following way: it takes the value specified in number of bytes and divides it by the maximum record length of a variable (32752), in which the xml will remain. 3 Separator hyphen Alph 1 79 Optional Hyphen 3 Join XML Nr Optional Value: S.- Whenever possible (the creation date, identification of the buyer/creditor, etc., coincide in all cases), unify all the information of each input logic file in a single output logical and physical XML file. N.- Obtain an output file with as many logical XML documents as logical files of flat format has the original. The default value is S. 3 Separator hyphen Alph 1 81 Optional Hyphen INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-9

24 3.Functionality description. 3 Record length of output XML Nr Optional Value: Size of the record we want to give to the XML file generated by the converter. Zeros, spaces or low-values as before defect Records type 2 XML transformation data to FLAT FILE 3 Separator hyphen Alph 1 2 Optional Hyphen 3 Output file DSNAME (DNSNAME of the FLAT FILE) Alph Mandatory -optional Dsname of the transformed FLAT file. In this case, as there may be several transformed files: 1.-The use of variables known by EDITRAN is admitted, for example, Source, Destination, Application, YEAR, MONTH, DAY, SOURCE DSNAME, etc. (See table 3). 2.-A fixed name can be entered 3.-If nothing is indicated (spaces), and the input file is called DSNAME.A.XML, an output flat file called DSNAME.A is created. In case you are used in EDITRAN to enter the DSNAME.A, change it to DSNAME.A.XML, because the final result will be the one you had until now. RECOMMENDED OPTION 4.-If nothing is indicated (spaces) and the input file is called DSNAME.XML, the DSNAME.PLN file is created by default. 3 Separator hyphen Alph 1 47 Optional Hyphen 3 Table of characters in which the flat file is to be transformed Alph Optional Name of the character table in which the flat file is to be transformed. If nothing is specified, the zos table where we are running is taken by default (usually ISO ). The supported tables appear in the following link: cs/technotes/guides/intl/encoding.do c.html l 3 Separator hyphen Alph 1 66 Optional Hyphen 3 Output file size Nr Optional Size of the output file in bytes. If nothing is specified, EDITRAN checks that it is a list of files (usual option when downloading, such as INPUT FILE OPTION = L, VIA PARM). There, the bytes of the downloaded file are included. If the PARM option has INPUT FILE=F (P OPTION not allowed for downloads), EDITRAN creates by default an output file of 99,999 bytes. If any value is specified, this prevails. 3 Separator hyphen Alph 1 79 Optional Hyphen 3 Reserved space Alph 1 80 Optional 2 Records type 3 XML generation data with acceptance or rejection (debits-transfers) 3 Separator hyphen Alph 1 2 Optional Hyphen 3 Create XML CONF (Acc-Rej) Alph 1 3 Mandatory -optional Create XML CONF (S/N) (YES/NO) of acceptance or rejection (debits and transfers), depending on the XML received. If you enter N, a confirmation file is never created: If you enter S, a confirmation file ** is created. (see DSNAME of the XML ACC/REJ) 3 Separator hyphen Alph 1 4 Optional Hyphen 3 Output file DSNAME (XML DSNAME of ACC/REJ) Alph Mandatory -optional Dsname of the XML file containing the acceptance or rejection. 1.- If CREATE XML CONF = 'N' is indicated, what is in this field is ignored 2.- If CREATE XML CONF = 'S' is indicated INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-10

25 3.Functionality description If DSNAME of the XML ACC/REJ = spaces, a confirmation XML is created, whose DSNAME = XML-entry.CNF 2.2- If DSNAME of the XML ACc/REJ contains a DSNAME, a confirmation XML is created with the DSNAME. If CREATE XML CONF='S'. The responsibility of the user is to upload and to send the resulting confirmation file: Either by creating a list of files with it (that matches what is indicated here). Alternatively, indicating it in the session profile as a file to be sent. The user is also responsible for linking a loading procedure if this is the case. 3 Separator hyphen Alph 1 49 Optional Hyphen Example of content in ZTBGFDAT: ***************************** Top of Data ******************************************** S-S-S-S-T *0- pepito.es %O.XML - - -N S-%O.XML.CNF ***************************** Bottom of Data ***************************************** In the previous case: There is a type 0 record (Java server connection data). The ip of the java server (zos USS) is , port 994. The tcp client waits a maximum of 5 minutes (300 seconds) for the server to resolve the process. It incorporates values in the free zone of the flat file. It maintains the output file if error. It removes SEPA Spain validations. It validates XML in both directions. It is a TGSS conversion with FF (it is recommended to create a special ZTBGFDAT for the conversion of the TGSS). There is the same record of type 0 (commented), but in this case, a dns is used. There is a type 1 record (transformation data for FLAT FILE to XML). It indicates (as it does not enter the output dsname). If the flat file is called, for example, KI.PEPE, the XML file will be called KI.PEPE.XML. In addition, it is in the system language, so no character table is indicated. It also indicates that EDITRAN should calculate the default size of the output file. There is a type 2 record (transformation data for XML to FLAT FILE). As it does not specify anything in the name of the transformed file, if for example the XML is called KI.PEPE.XML, the output flat file will be called KI.PEPE (it removes.xml from it). If the XML is called KI.PEPE, the output flat file is called KI.PEPE.PLN. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-11

26 3.Functionality description. It also indicates to validate the XML against the Scheme since no value has been included in the XML Validate field and the default value is S. In addition, it is in the system language, so no character table is indicated. It also indicates (if nothing is entered), that if TYPE=FILE, &TI=F, EDITRAN should calculate the default size of the output file. Use of the free zone of the records. In the example, it makes use of this functionality since `S' is indicated in the Free information parameter. Use of the record size for the XML file generated by the converter. In this case LRECL Keep the output file if error. In the example, in case of error in the converter, the generated output file will not be deleted. A confirmation (acceptance or rejection) file will be generated automatically. If a name is entered that follows the same mechanics as records 1 and 2. Use of the free record zone It has been agreed with certain clients to use some positions in the free zones of certain flat file format records. The purpose is to host in them certain information that, being in the source XML file, it is lost in the conversion because a field is not defined for it in the corresponding standard. This information is processed exclusively by client applications that only process flat file formats and are generally used to generate confirmation files directly in XML format from them. To make use of this functionality, indicate S in the Free information parameter of the ZTBGFDAT file of the program call, because by default the converter does not make it. The following describes the values transferred from the XML format file and the records and position where they are left in the flat file format resulting from the transformation. XML to flat file The following describes the values transferred from the XML format file and the records and position where they are left in the flat file format. All positions in the free zones that are not used with this functionality will still include blanks. Issuing transfers and cheques: The following content is transferred: <GrpHdr><MsgId> to position 290 of the payer header record. <PmtInf><DbtrAcct><DbtrAcct><Ccy> to position 325 of the payer header record, if the value is different from "EUR". <PmtInf><PmtInfId> to position 23 of the SEPA transfer header records, other transfers or cheques, depending on the type of block of the three from which was the data comes. The value of the Ccy attribute of <PmtInf><CdtTrfTxInf><Amt> <InstdAmt Ccy="XXX"> or <PmtInf><CdtTrfTxInf><Amt> <EqvAmt><Amt Ccy="XXX">, if different from "EUR", in position 502 of the first mandatory beneficiary record if the INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-12

27 3.Functionality description. source block is a SEPA Transfer or in position 333 of the same record if the source block is of the Other Transfers type. <PmtInf><CdtTrfTxInf><Amt><EqvAmt><CcyOfTrf>> to position 505 of the first mandatory beneficiary record if the source block is SEPA Transfer or to position 336 of the same record if the source block is of the Other Transfers type. <PmtInf><CdtTrfTxInf><XchgRateInf><XchRate>>XchRate> to position 508 of the first mandatory beneficiary record if the source block is SEPA Transfer or to position 339 of the same record if the source block is of the Other Transfers type. <PmtInf><CdtTrfTxInf><XchgRateInf><RateTp>> to position 521 of the first mandatory beneficiary record if the source block is SEPA Transfer or to position 350 of the same record if the source block is of the Other Transfers type. <PmtInf><CdtTrfTxInf><XchgRateInf><CtrctId> to position 525 of the first mandatory beneficiary record if the source block is SEPA Transfer or 354 of the same record if the source block is of the Other Transfers type. XML is written in position 598 of the payer header record. GrpHdr><GrpHdr><CtrlSum> to position 41 from the [General total record] if it contains 18 digits. GrpHdr>><NbOfTxs> to position 59 from the [General total record] if it contains more than 8 digits. <PmtInfId><CtrlSum>> to position 41 from the [SEPA Total Transfer Record],[Other Transfers total Record] or [Check total Record] as appropriate by block type, when it contains 18 digits. <PmtInfId><NbOfTxs>> to position 59 from the [SEPA Total Transfer Record], [Other Transfers total Record] or [Check total Record] as appropriate by block type, when more than 8 digits. Direct debits (basic schemes and B2B): XML is written in position 598 of the presenter header record. Presentations, the content of the <PmtInfId> field is moved to position 300 from the [Vendor Header by Collection Date] record. Returns, the content of <OrgnlPmtInfAndSts><OrgnlPmtInfId> is transferred to position 335 from the [Vendor Header by Return Date] record. Rejections, payer information. 11 positions of the content of the first of the following tags in the file is transferred: <OrgnlGrpInfAndSts><StsRsnInf><Orgtr> <Id><OrgId><BICorBEI> or <OrgnlGrpInfAndSts><StsRsnInf><Orgtr><Nm> or <OrgnlPmtInfAndSts><StsRsnInf><Orgtr><Id><OrgId><BICorBEI> or <OrgnlPmtInfAndSts><StsRsnInf><Orgtr><Nm> or <OrgnlPmtInfAndSts><TxInfAndSts><StsRsnInf><Orgtr><Id><OrgId><BICorBEI> or <OrgnlPmtInfAndSts><TxInfAndSts><StsRsnInf><Orgtr><Nm> To the 586th position of each [First individual record]. Presentations and refunds, the following content is transferred: INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-13

28 3.Functionality description. GrpHdr><NbOfTxs> to position 48 from the [General total record] if the quantity exceeds the 8 digits of the flat file format. GrpHdr><CtrlSum> to position 38 from the [General Total Record]. It will be used to collect a total of 18 digits (flat file format standard includes up to 17 digits). Presentations, the following content is transferred: <PmtInf><NbOfTxs> to position 99 from the [Vendor total record by collection date]. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. <PmtInf><CtrlSum> to position 81 from the [Vendor total record by collection date]. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). Rejections and refunds, the following content is transferred: <OrgnlGrpInfAndSts><OrgnlNbOfTxs> to position 48 from the [General total record]. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. <OrgnlGrpInfAndSts><OrgnlCtrlSum> to position 38 from the [General total record]. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). Rejections, the following content is transferred: <OrgnlPmtInfAndSts><OrgnlNbOfTx> to position 99 from the [Vendor total record by collection date]. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. <OrgnlPmtInfAndSts><OrgnlNbOfTx> to position 81 from the [Vendor total record by collection date]. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). Refunds, the following content is transferred: <OrgnlPmtInfAndSts><OrgnlNbOfTx> to position 91 from the [Vendor total record]. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. <OrgnlPmtInfAndSts><OrgnlNbOfTx> to position 73 from the [Vendor total record]. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). Returns, the following content is transferred: <OrgnlPmtInfAndRvsl><OrgnlNbOfTx> to position 91 from the [Vendor total record]. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. <OrgnlPmtInfAndRvsl><OrgnlNbOfTx> to position 73 from the [Vendor total record]. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-14

29 3.Functionality description. Flat file to XML When the client generates the flat file format files, he can make use of certain free zones to store information in them that would otherwise be impossible to transfer to the XML file resulting in the conversion. These are the following: Issuing transfers and cheques: The following content will be transferred: 70 positions, starting at 290, from the Payer Header to <InitgPty><Nm>. This functionality is used to transform into a single XML file, several logical flat files whose payer names do not match. 4 positions, starting at 360, from the Payer Header to as many elements <PmtInf><PmtInfId>> as must be built in the resulting XML file. This mapping makes it possible to inform and keep this concept (which is not included in either of the two formats) so that it can be returned in the bank statements sent by La Caixa Bank (AEB 43). 12 positions, starting at 364, from the Payer Header to <InitgPty><Id><OrgId> or <InitgPty><Id><PrvtId>, as appropriate. This functionality is used to convert into a single XML file, several logical flat files whose payer identifiers do not match, this being the Presenter ID to be completed. When in position 23 from the [Record of SEPA Transfer Header] the value H is found, <PmtInf><PmtTpInf><InstrPtry> will be completed with the HIGH code in the resulting XML file. 18 positions, starting at 41 from the [General total record], to <GrpHdr><CtrlSum>. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). 15 positions, starting at 59 from the [General total record], to <GrpHdr><NbOfTxs>. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. 18 positions, starting at 41 from the [Total record of SEPA transfers], [Total record of Other transfers] or [Total record of Cheques] as appropriate, by block type to <PmtInfId><CtrlSum>. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). 15 positions, starting at 59 from the [Total record of SEPA transfers], [Total record of Other transfers] or [Total record of Cheques as appropriate, by block type to <PmtInfId><NbOfTxs>. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. Direct debits (basic schemes and B2B): Rejections and returns, 35 positions, starting at 335, of the [Creditor header by collection date] record to <OrgnlPmtInfAndSts><OrgnlPmtInfId>. Rejections, the following content is transferred: 11 positions, starting at 167 from the [Presenter Header] record to <OrgnlGrpInfAndSts><StsRsnInf><Orgtr> <Id><OrgId><BICorBEI> if it is BIC, or <OrgnlGrpInfAndSts><StsRsnInf><Orgtr><Nm> if it is not. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-15

30 3.Functionality description. 4 positions, starting at 177, from the [Presenter Header] record to <OrgnlGrpInfAndSts><StsRsnInf><Rsn><Cd> 11 positions, starting at 369 from the [Vendor header by collection date] record to <OrgnlPmtInfAndSts><StsRsnInf><Orgtr><Id><OrgId><BICorBEI> if it is BIC, or <OrgnlPmtInfAndSts><StsRsnInf><Orgtr><Nm> if it is not. 4 positions, starting at 379 from the [Vendor header by collection date] record to <OrgnlPmtInfAndSts><StsRsnInf><Rsn><Cd> 11 positions, starting at 586, of the [First individual record] to <OrgnlPmtInfAndSts><TxInfAndSts><StsRsnInf><Orgtr><Id><OrgId><BICorBEI> if it is BIC, or <OrgnlPmtInfAndSts> <TxInfAndSts><StsRsnInf> <Orgtr><Nm> if it is not. Presentations and refunds, the following content is transferred: 15 positions, starting at 48 from the [General total record] to <GrpHdr><NbOfTxs>. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. 18 positions, starting at 38 from the [General total record] to <GrpHdr><CtrlSum>. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). Presentations, the following content is transferred: 15 positions, starting at 99 from the [Vendor total record by collection date] to <PmtInf><NbOfTxs>. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. 18 positions, starting at 81 from the [Vendor total record by collection date] to <PmtInf><CtrlSum>. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). Rejections and returns, the following content is transferred: 15 positions, starting at 48 from the [General total record] to <OrgnlGrpInfAndSts><OrgnlNbOfTxs>. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. 18 positions, starting at 38 from the [General total record] to <OrgnlGrpInfAndSts><OrgnlCtrlSum>. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). Rejections, the following content is transferred: 15 positions, starting at 99 from the [Vendor total record by collection date] to <OrgnlPmtInfAndSts><OrgnlNbOfTx>. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. 18 positions, starting at 81 from the [Vendor total record by collection date] to <OrgnlPmtInfAndSts><OrgnlNbOfTx>. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). Returns, the following content is transferred: 15 positions, starting at 91 from the [Vendor total record] to <OrgnlPmtInfAndSts><OrgnlNbOfTx>. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-16

31 3.Functionality description. 18 positions, starting at 73 from the [Vendor total record] to <OrgnlPmtInfAndSts><OrgnlNbOfTx>. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). Refunds, the following content is transferred: 15 positions, starting at 91 from the [Vendor total record] to <OrgnlPmtInfAndRvsl><OrgnlNbOfTx>. It will be used to collect individual record numbers whose value exceeds the 8 digits of the flat file format. 18 positions, starting at 73 from the [Vendor total record] to <OrgnlPmtInfAndRvsl><OrgnlNbOfTx>. It will be used to collect amounts of 18 digits in total (the flat file format standard includes up to 17). The converter will first search for this information in the free fields and, if not, it will map them as it usually does for each of those fields. Record of confirmation or rejection of debits and transfers: If the user indicates so, (type 3 record), when downloading the xml, a confirmation or rejection xml file is generated in certain cases, which can be automatically linked with an EDITRAN procedure to generate the automatic response (Xml to Flat file conversions of the 3414 and 19 Presentations type standards). If it is possible to download the xml, an acceptance file is generated (even if there is a warning in the xml download). If it is not possible to download the xml, a rejection file is generated. Example: PAIN002. An xml would be generated starting from the flat file data or 01 and 99 record xml. (ACCP RECEPTION AND CORRECT VALIDATION or RJCT REJECTED) with certain data that were included in the original xml: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain "> <CstmrPmtStsRpt> <GrpHdr> <MsgId>B0081.S0901.F P </MsgId> <CreDtTm> T11:30:00</CreDtTm> <InitgPty> <Nm>TELEFONICA DE ESPANA, S.A.</Nm> </InitgPty> </GrpHdr> <OrgnlGrpInfAndSts> <OrgnlMsgId>B0081.S0901.F P </OrgnlMsgId> <OrgnlNbOfTxs> </OrgnlNbOfTxs> <OrgnlCtrlSum> </OrgnlCtrlSum> <GrpSts>ACCP</GrpSts> </OrgnlGrpInfAndSts> </CstmrPmtStsRpt> </Document> INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-17

32 3.Functionality description. Variable Meaning The list of variables known by EDITRAN is as follows (Table 3): %O DSN at source %E Decade %Y Last digit of the year %A Last two digits of the year (yy) %M Month in two digits (mm) %X Month in a character (1,2,3,4,5,6,7,8,9,O,N,D) %D Day of the month (dd) %H Time (hhmmss) %C Order number of the file received (nn) %K Order number of the file received (nnnn) %R The last 7 characters of the node code %P Application code Example of content in ZTBGFDAT: ***************************** Top of Data ******************************************** S-S- *0- pepito.es %O.XML S-%O.XML.CNF ***************************** Bottom of Data ***************************************** In the previous case: There is a type 0 record (Java server connection data). The ip of the java server (zos USS) is , port 994. The tcp client waits a maximum of 5 minutes (300 seconds) for the server to resolve the process. There is the same record of type 0 (commented), but in this case, a dns is used. There is a type 1 record (transformation data for FLAT FILE to XML). It indicates (as it does not enter the output dsname) that if the flat file is called for example KI.PEPE, the XML file will be called KI.PEPE.XML. In addition, it is in the system language, so no character table is indicated. It also indicates that EDITRAN should calculate the default size of the output file. There is a type 2 record (transformation data for XML to FLAT FILE. As it does not specify anything in the name of the transformed file, if for example the XML is called KI.PEPE.XML, the output flat file will be called KI.PEPE (it removes.xml from it). If the XML is called KI.PEPE, the output flat file is called KI.PEPE.PLN. It also indicates to validate XML against the Scheme, since no value has been included in the XML Validate field and the default value is S. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 3-18

33 4.Adaptation of TGSS Online Payments In addition, it is in the system language, so no character table is indicated. It also indicates (if nothing is entered), that if TYPE=FILE, &TI=F, EDITRAN should calculate the default size of the output file. Use of the free zone of the records. In the example, it makes use of this functionality since `S' is indicated in the Free information parameter. Use of the record size for the XML file generated by the converter. In this case, LRECL Keep the output file if error. In the example, in case of error in the converter, the generated output file will not be deleted. A confirmation (acceptance or rejection) file will be generated automatically. If a name is entered that follows the same mechanics as records 1 and Adaptation of TGSS Online Payments To make it easier for our customers to integrate the complete TGSS Online Payments protocol with the SEPA converter, the two additional maps detailed in this document have been implemented File reception The entities will receive from the TGSS the XML format files, according to the pain xsd scheme of ISO XML(pain ) Converter Flat file format: TGSS header record + SEPA file The content of the <MsgId> tag of these XML files is: Sending type (2 positions): File creation date, 6 positions (AAMMDD) NRBE of payment financial entity (4 positions) Reference (20 positions) Attention: Under the specific indication of the parameter in record 0 of ZTBGFDAT position 86 - TGSS Header (see XML5XUSUA manual. It can also be completed in the Configuracion.properties file). When these files pass through the Converter, they will be translated into flat file format. The use of this parameter ignores any value given to the parameter of record 3 Create XML CONF (Acc-Rej), automatic reply if the file to be converted is of the standard. The content of the resulting file will be the TGSS header record that was defined accordingly, whose structure is detailed below, followed by the SEPA file. TRANSMISSION HEADER RECORD (flat file format) FIELD A Header Record Code. Two-position numeric field. Its value will be 01 FIELD B Standard Code. Two-position numeric field. Its value will be 34 INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 4-19

34 4.Adaptation of TGSS Online Payments FIELD C Operation Type. Two-position numeric field. Its value will be 14 FIELD D Sending type I. Two-position numeric field. Its possible values are: 50 - R03 transfer files, signed electronically. FIELD E Sending type II. Two-position numeric field. Its values will be the following: 01 For all types of previous sending (Possibility of including 06 in a particular case in later versions) FIELD F Client Reference. F1 File creation date. Six-position numeric field F2 File Creation time. Four-position numeric field F3 Code of the Financial Entity. Six-position numeric field FIELD G Customer Reference Extension. Twenty-position alphanumeric field. It will include the R number and the Payment Teller FIELD H Field of variable length up to 600. The mapping performed by the Converter is as follows: TGSS header record: two first characters of the tag <MsgId> six following characters of <MsgId> twenty four remaining characters of <MsgId> blanks Confirmation sending The TGSS will receive an XML confirmation file from the entities, according to pain xsd. TGSS Confirmation Converter XML (pain ) Users who have generated them in their flat file format applications can obtain them with the Converter according to the following structure: CONFIRMATION RESPONSE FILE (flat file format) FIELD A Notebook identification and CSB Operation Type. Its value will be 3414 FIELD B Identification of the transmitted file. B1 It corresponds to FIELD F1 of the Transmission Header Record B2 It corresponds to FIELD F2 of the Transmission Header Record B3 It corresponds to FIELD F3 of the Transmission Header Record FIELD C Identification of the Transmission Entities C1 Reserved. Twelve-position field C2 Entity Identification. Forty-position alphanumeric field FIELD D Identification of the Financial Entity. D1 NRBE of the Entity. Four-position numeric field D2 Reserved. Four-position field FIELD E Data for the Quadrant E1 Total Number of Records in the Queue Record of the logical file. Ten-position numeric field E2 Total Amount in the Queue Record of the logical file. Seventeen-position numeric field INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 4-20

35 4.Adaptation of TGSS Online Payments E3 Number of Records of the Received File. Ten-position numeric field E4 Total Amount of the Received File. Seventeen-position numeric field Note: In the first version, where there is one single physical file, the E1 and E2 fields will appear with zeros. FIELD F Control codes. F1 Code resulting from the Transmission. Two-position numeric field. F2 Reserved for future codes. Two-position numeric field. Its value will be 00 FIELD G Additional information of Client Checking G1 It corresponds to FIELD D of the Transmission Header Record G2 It corresponds to FIELD E of the Transmission Header Record G3 It corresponds to FIELD G of the Transmission Header Record G4 Reserved. Eight-position field. The mapping performed by the Converter is as follows: <CstmrPmtStsRpt><GrpHdr><MsgId>: G1 + B1 + positions from 2 to 5 of B3 + G3 <CstmrPmtStsRpt><GrpHdr><CreDtTm>: in ISODateTime YYYY-MM- DDThh:mm:ss format. First and second digit of B1, formatted as YYYY third and fourth digit of B fifth and sixth digit of B1 + T00:00:00 <CstmrPmtStsRpt><OrgnlGrpInfAndSts><OrgnlMsgId>: same content as <CstmrCdtTrfInitn><GrpHdr><MsgId> <CstmrPmtStsRpt><OrgnlGrpInfAndSts><OrgnlMsgNmId>: pain <CstmrPmtStsRpt><OrgnlGrpInfAndSts><OrgnlCtrlSum>: E4 (two digits to the right separated by. ). <CstmrPmtStsRpt><OrgnlGrpInfAndSts><GrpsSts>: ACTC if F1 is 00, RJCT for another value. <CstmrPmtStsRpt><OrgnlGrpInfAndSts><GrpsSts><StsRsnInf><Rsn><Cd>: depending on the F1 content and as long as it is different from 00. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 4-21

36 5.JCLS and PROCEDURES. 5. JCLS and PROCEDURES JCLS. The ZTBGJXML jcl will be provided: //XXXXXXXX JOB (XXXX,XXX,,XX),ZTBXXML,MSGCLASS=X,CLASS=X, // MSGLEVEL=X,NOTIFY=&SYSUID //********************************************************************+ //* JCL PARA CONVERTIR UN FICHERO PLANO SEPA A XML Ó A LA INVERSA *+ //********************************************************************+ //* 1.-DEBE APUNTAR (SET) LAS SIGUIENTES VARIABLES: *+ //* 1.1.SESION: L1+L2+R1+R2+AP: INDICAR UNA SESION DE EDITRAN/G *+ //* 1.2.FUNCION: FU. ADMITE VALORES X=PLANO A XML, P=XML A PLANO *+ //* 1.3.TIPO: TI. ADMITE VALORES:F=FICHERO (EL INDICADO EN &FI=XX) *+ //* TI=F INDICA FICHERO. EN &FI VA EL DSNAME DEL FICHERO DE *+ //* APLICACION DE ENTRADA (XML O PLANO SEGUN &FU) *+ //* TI=L INDICA LISTA DE FICHEROS. EN &FI VA DSNAME DE UN FILE *+ //* CREADO POR USUARIO, CUYO CONTENIDO SON LOS DSNAMES DE *+ //* LOS FICHEROS DE ENTRADA (XML O PLANOS SEGUN &FU) *+ //* PARA VER FORMATO DE LA LISTA, REVISE DOCUMENTACION *+ //* TI=P INDICA PERFILES. EN ESTE CASO, EDITRAN TIRA DE PERFIL *+ //* EDITRAN/G PARA COGER NOMBRES DE FICHEROS ENTRADA. *+ //* 1.4.FICHERO: FI. INDICAR EL DSNAME (DE 40 MAXIMO) &FI=XXXX *+ //* SI &TI=F ES EL DSNAME DEL FICHERO DE ENTRADA *+ //* SI &TI=L ES EL DSNAME DE LA LISTA, CUYO CONTENIDO SON LOS *+ //* DSNAMES DE LOS FICHEROS DE ENTRADA *+ //* SI &TI=P INDIQUE ESPACIOS. EL JOB COGE LOS FILES DEL PERFIL*+ //* 2.-DEBE EXISTIR EL FICHERO DD ZTBGFDAT, PUES EN SU CONTENIDO HAY *+ //* TAMBIEN OTROS PARAMETROS NECESARIOS, IP-PORT, FICHERO SALIDA, *+ //* SEGUNDOS ESPERA, ETC. (REVISE DOCUMENTACION DE PRODUCTO) *+ //* CON &FU=X, SI EN ZTBGFDAT NO SE ESPECIFICA DSNAME DE SALIDA, *+ //* EL PROGRAMA CREA UN FILE DE SALIDA LLAMADO DSNAME.XML *+ //* CON &FU=P, SI EN ZTBGFDAT NO SE ESPECIFICA DSNAME DE SALIDA, *+ //* EL PROGRAMA CREA UN FILE DE SALIDA LLAMADO: *+ //* DSNAME (si el fich. entrada es DSNAME.XML) *+ //* DSNAME.PLN(si el fich. entrada es DSNAME) *+ //* 3.-SACA UNA LISTA CON LOS FICHEROS PROCESADOS, DD ZTBGFCAR *+ //********************************************************************+ // SET L1= // SET L2=940 // SET R1= // SET R2=990 // SET AP=CARGAC // SET FU=X // SET TI=F INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 5-22

37 5.JCLS and PROCEDURES. // SET FI=KI.EIDA.FF06 //********************************************************************+ //INBORR1 EXEC PGM=IEFBR14 //LPASO00 DD DSN=KI.PMED.R&R1..R&R2..A&AP..LISTFICX, // DISP=(OLD,DELETE,DELETE) //* //PASO01 EXEC PGM=ZTBXBXML, // PARM='&L1&L2&R1&R2&AP&FU&TI&FI/CBLQDA(ON)' //STEPLIB DD //SYSTCPD DD //ZTBGFPRI DD //ZTBGFPER DD //ZTBGFLOG DD //ZTBGFDAT DD DSN=KI.EIDC.ZTBG.LOAD,DISP=SHR DSN=SW.TCPIP.SEZAPARM(TCPDATAB),DISP=SHR SYSOUT=*,DCB=(BLKSIZE=105) DSN=KI.EIDC.ZTBG.ZTBGFPER,DISP=SHR DSN=KI.EIDC.ZTBG.ZTBGFLOG,DISP=SHR DSN=KI.EIDC.ZTBG.ZTBGFDAT,DISP=SHR //ZTBGFCAR DD DSN=KI.PMED.R&R1..R&R2..A&AP..LISTFICX, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(500,50),RLSE), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=0,DSORG=PS) //ZTBXFSAL DD DSN=KI.PMED.R&R1..R&R2..A&AP.. ZTBXFSAL, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(500,50),RLSE), // DCB=(RECFM=FB,LRECL=252,BLKSIZE=0,DSORG=PS) //SYSOUT DD SYSOUT=* //SYSPRINT DD //SYSDBOUT DD //ABENDAID DD //SYSCOUNT DD //SYSUDUMP DD //SYSABOUT DD SYSOUT=* SYSOUT=* SYSOUT=* DUMMY SYSOUT=* SYSOUT=* As an example, we have indicated source ( ) destination ( ), application (CARGAC), X Function (flat file to xml), type F (file), DSNAME of the input file = KI.FILE.INPUT.FILE In the ZTBGFDAT file we will indicate a type 1 record without the output file name. If nothing is indicated, (see the content of ZTBGFDAT), the file KI.FILE.INPUT.XML will be created. ********************************* Top of Data **************************************** N S ******************************** Bottom of Data ************************************** In turn, as an example of P Function (xml to flat file), if we encode in PARM PEPITAPFKI.FICHERO.ENTRADA.XML In the ZTBGFDAT file we have specified a type 2 record, without output file name. The KI.FICHERO.ENTRADA FLAT FILE will be created. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 5-23

38 5.JCLS and PROCEDURES Procedures Before transmission. The previous ZTBGP1CX is provided. Currently, the standard procedure before transmission (ZTBGP1C) includes: // PROC ORIGEN=,FUNCION=,L0=, // L1=,L2=,R1=,R2=,AP=,LF= //A1P EXEC PGM=ZTBGB110, // PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&AP&LF/CBLQDA(ON)', // REGION=0M,TIME=1440. //ZTBGFCAR DD DSN=KI.PMED.&L0..R&R1..R&R2..A&AP..ZTBGFCAR,DISP=SHR (ZTBGFCAR puede que el usuario no lo use, ó lo haya llamado de otra forma) Compared to the standard, the new procedure that has been provided includes: A previous step to A1P (flat file to xml converter) A SET to the LF variable New variables A change in the ZTBGFCAR list (if the user already used it) The previous ZTBGP1X is provided (the changes or what is no new are shown in yellow): // PROC ORIGEN=,FUNCION=,L0=, // L1=,L2=,R1=,R2=,AP=,LF=,FU=,TI=,FI= // SET LF=S // SET FU=X // SET TI=P //* SET FI=XX.XXXX.XXX //********************************************************************* //* PROCEDIMIENTO PREVIO A LA EMISION EDITRAN/G * //* INCLUYE UN PASO PREVIO A LA CARGA, QUE CONSISTE EN NORMA SEPA * //* PASO DE FICHEROS DE APLICACION PLANOS A XML * //********************************************************************* //* DATOS: * //* ORIGEN (O=OPERADOR,E=EDITRAN,A=JCL APLICACION) ----> 1 BYTE * //* FUNCION (01=CARGA DE EMISION DE PRESENTACION, * //* 03=EMISION DE PRESENTACION, * //* 04=EMISION DINAMICA DE PRESENTACION) -----> 2 BYTES * //* SESION-PRESENTACION >24 BYTES * //* LISTA FICHEROS (S) > 1 BYTE * //* INDEPENDIENTEMENTE DE QUE EL USUARIO INDIQUE QUE USA UNA * //* LISTA DE FICHEROS EN LA CARGA, EL PASO01 LE PASA AL PASO A1P * //* UNA NUEVA LISTA DE FICHEROS A CARGAR (LOS XML), POR LO QUE * //* EL VALOR DE ESTA VARIABLE, DEBE APUNTARSE SIEMPRE A S. * //* EL USUARIO, SI USA LISTA DE FICHEROS, INDICA LA MISMA EN &FI * //* FUNCION (X) (CONVERTIR PLANO A XML EN PASO01) -----> 1 BYTE * INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 5-24

39 5.JCLS and PROCEDURES. //* TIPO FICHERO APLICACION (P/L/F) > 1 BYTE * //* INDICA DE DONDE TIRAR PARA SACAR LOS XML: * //* SI P (PERFIL) : PASO01, TIRA DE PERFILES DE EDITRAN/G * //* SI F (FICHERO): EL XML ESTA INDICADO EN LA VARIABLE &FI * //* SI L (LISTA) : LA LISTA DE LOS XML ESTA INDICADA EN VBLE &FI * //* FICHERO APLICACION: DSNAME DEL FICHERO DE APLICACION (DEL XML) * //* O DSNAME DE LA LISTA QUE CONTIENE LOS FICHEROS APL-> 0-44 BYTES * //* SI &TI=P, NO SE USA &FI, POR LO QUE PUEDE PONER SPACES * //* SI &TI=F, &FI=DSNAME.FILE.APLIC.XML * //* SI &TI=L, &FI=DSNAME.LISTA.FILES.APLIC.XML * //********************************************************************* //INBORR1 EXEC PGM=IEFBR14 //LPASO00 DD DSN=KI.PMED.R&R1..R&R2..A&AP..LISTFICX, // DISP=(OLD,DELETE,DELETE) //PASO01 EXEC PGM=ZTBXBXML, // PARM='&L1&L2&R1&R2&AP&FU&TI&FI/CBLQDA(ON)' //STEPLIB DD DSN=KI.EIDC.ZTBG.LOAD,DISP=SHR //SYSTCPD DD DSN=SW.TCPIP.SEZAPARM(TCPDATAB),DISP=SHR //ZTBGFPRI DD SYSOUT=*,DCB=(BLKSIZE=105) //ZTBGFPER DD DSN=KI.EIDC.ZTBG.ZTBGFPER,DISP=SHR //ZTBGFLOG DD DSN=KI.EIDC.ZTBG.ZTBGFLOG,DISP=SHR //ZTBGFDAT DD DSN=KI.EIDC.ZTBG.ZTBGFDAT,DISP=SHR //ZTBGFCAR DD DSN=KI.PMED.R&R1..R&R2..A&AP..LISTFICX, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(500,50),RLSE), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=0,DSORG=PS) //ZTXGFSAL DD DSN=KI.PMED.R&R1..R&R2..A&AP..ZTBXFSAL, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(500,50),RLSE), // DCB=(RECFM=FB,LRECL=252,BLKSIZE=0,DSORG=PS) //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSDBOUT DD SYSOUT=* //ABENDAID DD SYSOUT=* //SYSCOUNT DD DUMMY //SYSUDUMP DD SYSOUT=* //SYSABOUT DD SYSOUT=* /* //A1P EXEC PGM=ZTBGB110,,COND=(0,NE,PASO01), // PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&AP&LF/CBLQDA(ON)', // REGION=0M,TIME=1440. //ZTBGFCAR DD DSN=KI.PMED.R&R1..R&R2..A&AP..LISTFICX,DISP=SHR INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 5-25

40 5.JCLS and PROCEDURES. The LF=S variable has been entered (the step a1p takes a list of files created in PASO01, named KI.PMED.R&R1..R&R2..A&AP..LISTFICX) The FU=X variable has been entered (pass FLAT FILE TO XML) The TI=P variable has been entered (the user wants us to remove the dsnames of application flat files from the session profile). Note. If for example, the user has created a list of application files to load, for example, KI.PMED.R&R1..R&R2..A&AP..ZTBGFLFE, we should set the variable SET FI=KI.PMED.R&R1..R&R2..A&AP..ZTBGFLFE. The content of this file is described in Table 1. The ZTBGFDAT file created by the user must exist. Example: ***************************** Top of Data ******************************************** %O.XML S ***************************** Bottom of Data ***************************************** In a first XML step, EDITRAN will transfer the files indicated in EDITRAN/G PROFILE (TI=P), to XML format. It will create a new list, KI KI.PMED.R&R1..R&R2..A&AP..LISTFICX whose content is a list of files with the names of the XML generated (which will be DSNAME-FILE-APPLICATION.XML, for having specified %O.XML in ZTBGFDAT). Next, the A1P step will use the new list of files KI.PMED.R&R1..R&R2..A&AP..LISTFICX (because the LF=S variable was entered) and it will upload them. If, for example, we have used a list of files (TI=L), called KI.EGDC.L00.R123.R APEPITA.ZTBGFCAR and its content is: ********************************* Top of Data **************** KI.EIDA.FF01 KI.EIDA.FF02 -R-E-A-F -R-E-A-F ******************************** Bottom of Data ************** The content of the file KI.PMED.R&R1..R&R2..A&AP..LISTFICX will be: ********************************* Top of Data **************** KI.EIDA.FF01.XML -B-N-N-F KI.EIDA.FF02.XML -B-N-N-F ******************************** Bottom of Data ************** After reception. The subsequent ZTBGP4CX is provided. Currently, the standard procedure after transmission (ZTBGP4C) includes: // PROC ORIGEN=,FUNCION=,L0=, // L1=,L2=,R1=,R2=,AP= //A4P EXEC PGM=ZTBGB140, // PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&AP/CBLQDA(ON)',. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 5-26

41 5.JCLS and PROCEDURES. //ZTBGLFE EXEC PGM=ZTBGBLFE,COND=(0,NE,A4P), // PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&AP', //ZTBGFLFE DD DSN=KI.PMED.&L0..R&R1..R&R2..A&AP..ZTBGFLFE,DISP=SHR Compared to the standard, the new procedure that has been provided includes: // PROC ORIGEN=,FUNCION=,L0=, // L1=,L2=,R1=,R2=,AP=,FU=,TI=,FI= // SET FU=P // SET TI=L // SET FI=KI.PMED.R&R1..R&R2..A&AP..ZTBGFLFE //********************************************************************* //* PROCEDIMIENTO POSTERIOR A LA RECEPCION EDITRAN/G * //* NOTA: SI PASO ZTBGB140 ACABA CON RC=01 ES PORQUE NO ES LA ULTIMA* //* SESION DE TRANSMISION. IGNORAR DICHO WARNING * //* INCLUYE UN PASO POSERIOR A DESCARGA, QUE CONSISTE EN NORMA SEPA * //* PASO DE FICHEROS DESCARGADOS XML A PLANOS * //********************************************************************* //* DATOS: * //* ORIGEN (O=OPERADOR,E=EDITRAN,A=JCL APLICACION) ----> 1 BYTE * //* FUNCION (07=DESCARGA DE RECEPCION DE PRESENTACION, * //* 09=FIN DE RECEPCION DE PRESENTACION) -----> 2 BYTES * //* SESION-PRESENTACION >24 BYTES * //* FUNCION (P) (CONVERTIR XML A PLANO EN PASO02) -----> 1 BYTE * //* TIPO FICHERO APLICACION (L) (LISTA) > 1 BYTE * //* EL PASO LFE SACA UNA LISTA, ZTBGFLFE CON LOS XML DESCARGADOS * //* EL PASO02, TIRA DE ESA LISTA &FI PARA PASAR LOS XML A PLANO * //* FICHERO APLICACION: &FI, SE APUNTA CON EL NOMBRE DE LA LISTA * //* QUE SACA EL PASO ZTBGLFE * //********************************************************************* //A4P EXEC PGM=ZTBGB140, // PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&AP/CBLQDA(ON)', // REGION=0M,TIME= //********************************************************************* //*PASO PARA GENERAR LISTA DE FICHEROS RECIBIDOS EN LA PRESENTACION //********************************************************************* //INBORR1 EXEC PGM=IEFBR14 //LPASO00 DD DSN=KI.PMED.R&R1..R&R2..A&AP..ZTBGFLFE, // DISP=(OLD,DELETE,DELETE) //* //ZTBGLFE EXEC PGM=ZTBGBLFE,COND=(0,NE,A4P), // PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&AP', // REGION=0M,TIME=25 INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 5-27

42 5.JCLS and PROCEDURES. //ZTBGFLFE DD DSN=KI.PMED.R&R1..R&R2..A&AP..ZTBGFLFE, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(500,50),RLSE), // DCB=(RECFM=FB,LRECL=130,BLKSIZE=0,DSORG=PS).. //********************************************************************* //*PASO PARA CONVERTIR LOS XML A PLANOS //********************************************************************* //PASO02 EXEC PGM=ZTBXBXML,,COND=(0,NE,ZTBGLFE), // PARM='&L1&L2&R1&R2&AP&FU&TI&FI/CBLQDA(ON)' //STEPLIB DD DSN=KI.EIDC.ZTBG.LOAD,DISP=SHR //SYSTCPD DD DSN=SW.TCPIP.SEZAPARM(TCPDATAB),DISP=SHR //ZTBGFPRI DD SYSOUT=*,DCB=(BLKSIZE=105) //ZTBGFPER DD DSN=KI.EIDC.ZTBG.ZTBGFPER,DISP=SHR //ZTBGFLOG DD DSN=KI.EIDC.ZTBG.ZTBGFLOG,DISP=SHR //ZTBGFDAT DD DSN=KI.EIDC.ZTBG.ZTBGFDAT,DISP=SHR //ZTBGFCAR DD DSN=KI.PMED.R&R1..R&R2..A&AP..ZTBGFLF2, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(500,50),RLSE), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=0,DSORG=PS) //ZTXGFSAL DD DSN=KI.PMED.R&R1..R&R2..A&AP..ZTBXFSAL, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(500,50),RLSE), // DCB=(RECFM=FB,LRECL=252,BLKSIZE=0,DSORG=PS) //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSDBOUT DD SYSOUT=* //ABENDAID DD SYSOUT=* //SYSCOUNT DD DUMMY //SYSUDUMP DD SYSOUT=* //SYSABOUT DD SYSOUT=* /* An intermediate step between A4P-ZTBGGLFE (which deletes the list of input files that the ZTBGGLFE step will create) One step after A4P-ZTBGLFE (xml to flat file converter). The step A4P downloads XML. The step ZTBGLFE creates a list containing the dsnames of the downloaded files (see table-2). The PAS002 uses that list (by entering TI=L and FI=KI.PMED.R&R1..R&R2..A&AP..ZTBGFLFE ZTBGLFE) and converts it to flat file (by entering FU=P. This PAS002 also uses a KI.PMED.R&R1..R&R2..A&AP..ZTBGFLF2 list containing the dsnames of the final flat files to be processed by the application. The ZTBGFDAT file created by the user must exist. Example: ***************************** Top of Data ******************************************** INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 5-28

43 5.JCLS and PROCEDURES. 1-%O.XML - - -N ***************************** Bottom of Data ***************************************** If, for example, the content of KI.PMED.R&R1..R&R2..A&AP..ZTBGFLFE is: ********************************* Top of Data **************** KI.EIDA.FF01.XML FIJOEN PAGO E1 KI.EIDA.FF02.XML FIJOEN PAGO E2 ******************************** Bottom of Data ************** The content of the file KI.PMED.R&R1..R&R2..A&AP..ZTBGFLF2 will be: ********************************* Top of Data **************** KI.EIDA.FF01 -B-N-N-F KI.EIDA.FF02 -B-N-N-F ******************************** Bottom of Data ************** INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 5-29

44 6.OTHERS. 6. OTHERS Call to Java in command mode. The IBM JZOS JCL is used to run java in command mode: //******************************************************************** //JAVA EXEC PROC=JVMPRC60, // JAVACLS='-jar EDITRANSepaXml.jar', // ARGS='//''''FICHERO.ENTRADA.XML''''' //STDENV DD * # This is a shell script which configures # any environment variables for the Java JVM. # Variables must be exported to be seen by the launcher.. /etc/profile export JAVA_HOME=/usr/lpp/JAVA/J6.0 export PATH=/bin:"${JAVA_HOME}"/bin LIBPATH=/lib:/usr/lib:"${JAVA_HOME}"/bin LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/j9vm LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib/s390/classic LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib/s390/default LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib/s390/j9vm #LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib/s390 #LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic export LIBPATH="$LIBPATH": # Customize your CLASSPATH here # APP_HOME=$JAVA_HOME APP_HOME=/u/ki10628 CLASSPATH=$APP_HOME:"${JAVA_HOME}"/lib:"${JAVA_HOME}"/lib/ext Add Application required jars to end of CLASSPATH for i in "${APP_HOME}"/*.jar; do CLASSPATH="$CLASSPATH":"$i" done export CLASSPATH="$CLASSPATH": # Set JZOS specific options # Use this variable to specify encoding for DD STDOUT and STDERR #export JZOS_OUTPUT_ENCODING=Cp1047 # Use this variable to prevent JZOS from handling MVS operator commands #export JZOS_ENABLE_MVS_COMMANDS=false INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 6-1

45 6.OTHERS. # Use this variable to supply additional arguments to main #export JZOS_MAIN_ARGS="" # Configure JVM options IJO="-Xms16m -Xmx128m" # Uncomment the following to aid in debugging "Class Not Found" problems IJO="$IJO -verbose:class" # Uncomment the following if you want to run with Ascii file encoding.. #IJO="$IJO -Dfile.encoding=ISO8859-1" export IBM_JAVA_OPTIONS="$IJO " /* If we use this option, it will be necessary to set the file: conf/configuracion.properties. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 6-2

46 7.ANNEX. 7. ANNEX Transformation with Warnings. Given the asymmetry between the standards of the XML and the flat file formats in terms of the obligatory nature and content of the fields in each case, sometimes the converter generates files that do not strictly comply with the final format standard (mandatory fields that remain empty, values different from those indicated in the standard, etc.) even though they comply with the initial format. This result will be more common in XML to flat file transformations because, given the transience of the latter, priority has been given to meeting the requirements of the XML format. As the initial file is correct, the solution given by EDITRAN is to generate these files but giving a special Warning result (see Result codes) to be able to differentiate it from a file that follows the standard strictly. By default, the files thus generated are saved as correct in the ZTBGFCAR output list. When the file that reaches the converter is empty, the converter gives a code 28, the execution ends with 04 and in the ZTBGFCAR output list the name of the empty file is saved as it enters the converter (if it is in the procedure before transmission, the empty file would be loaded) Server result codes. The possible results are: 00 Correct transformation of the file The execution will end with RC = 00 Warning Message 28 Empty file The execution will end with RC = 04 Errors of communications and file management The execution will end with RC = Error when reading the socket 02 - Error in the input parameters 03 - The Request function parameter is not found or has an invalid value 04 - Input file parameter not found 05 - Output file parameter not found 06 - The Request language parameter is not found or has an invalid value 07 - The Validate Xml parameter has an invalid value. It can be [S] (YES) or [N] 08 - The "Information in the free field" parameter has an invalid value. It can be [S] (Yes) or [N] (No) 09 - The value of Alphabet parameter is not recognized or is invalid INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 7-1

47 7.ANNEX Number of invalid parameters 11 - Error when converting 12 - Error when writing the answer 13 - Input file not found 14 - Error when opening the output file 15 - Error when closing files 16 - Error in the files 17 - Error when deleting the output file Errors in the flat file converter to xml The execution will end with RC = Error in the flat file. The type of standard to which the file belongs is not recognized 19 - Error when reading the flat file 20 - Error in the flat file (*) unmarshaller 21 - Error in the conversion between flat file objects to xml 22 - xml marshaller error(**) 23 - Error in the order of the blocks of the flat file. The order has to be SEPA Transfers, Other Transfers and Checks and only one block of each Error when including several logical files. They cannot be grouped into a single XML 25 - The values in the [Return Date] field in the [Creditor Header by Date] records do not match. Information cannot be grouped together in a single XML file. Errors in the xml converter to flat file The execution will end with RC = Error in the xml file. The type of standard to which the file belongs is not recognized 29 - Error when reading the xml 30 - Error when validating the xml 31 - xml(*) unmarshaller error 32 - Error in the conversion between objects from xml to flat file 33 - Error in the flat file marshaller(**) 34 - Error, the amount value is invalid INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 7-2

48 7.ANNEX Error when writing the XML file. It is not possible to write PmtInf blocks that do not follow the order: SEPA Transfers, Other Transfers and Checks License error The execution will end with RC = Incorrect license Warnings The execution will end with RC = Transformation with file Warnings The execution will end with RC = Empty input file ERRORS RETURNED IN THE ZTBXBITS PROGRAMME ================================ REASON RESULT DESCRIPTION SERVER ERROR XX SERVER RESULT 99 REMOTE PROCESS ERROR. PROGRAM ERROR. CONNECTION ERROR TO SERVER. TCP MACRO ERROR 0X ZTBXBITS PROGRAM CALL AREA ERRORS 99/01 FUNCTION UNKNOWN 99/02 WRONG ALPHABET 99/03 WRONG INPUT FILE 99/04 WRONG OUTPUT FILE 99/05 TABLE OF ERRONEOUS CHARACTERS 99/06 WRONG TCPNAME 99/07 WRONG SERVER IP ADDRESS 99/08 WRONG SERVER PORT 99/09 WRONG SERVER ACTIVATION SECONDS 5X SERVER ELAPSED TIME ERRORS 99/53 NO DATA HAS BEEN SENT (NOT EVEN 1 OCTET) 99/54 NO DATA HAS BEEN SENT (SOME OCTET) 99/55 NO DATA HAS BEEN RECEIVED (NOT EVEN 1 OCTET) * INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 7-3

49 7.ANNEX. 99/56 NO DATA HAS BEEN RECEIVED (SOME OCTET)* 6X-7X TCP/IP ERRORS IN CONNECTION WITH THE SERVER * 99/61 INITAPI MACRO ERROR * 99/62 ERROR IN SOCKET MACRO * 99/63 GETHOSTBYNAME MACRO ERROR * 99/64 ERROR IN SETSOCKOPT MACRO ERROR * 99/65 ERROR IN FCNTL MACRO * 99/66 ERROR IN CONNECT MACRO * 99/67 ERROR IN WRITE SELECT MACRO * 99/68 ERROR IN READ MACRO * 99/69 ERROR IN READ MACRO SELECT * 99/70 ERROR IN WRITE MACRO * 99/71 ERROR IN EZACIC08 MACRO * 99/72 ERROR IN EZACIC06 MACRO * 8X ERRORS IN THE DATA RETURNED BY THE SERVER * 99/81 INVALID DATA LENGTH * 99/82 ERRONEOUS DATA * (*) Unmarshalling: JAVA object generation from a data file. (**) Marshalling: generation of a data file from JAVA objects. INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 7-4

50 ecommerce Competence Center Avda. de Bruselas Alcobendas. Madrid, Spain T T INDRA. All rights reserved. EDITRAN/XML SEPA 5.X Page 7-1