Financial Institutes. Deutsche Börse Systems. XONTRO Order Xentric Order S.W.I.F.T. Technical connection. Banking connection using LU 6.

Transcription

1 Deutsche Börse Systems XONTRO Order Xentric Order S.W.I.F.T. Financial Institutes Technical connection Version: 3.00

2 Deutsche Börse Systems AG Page: 1 Table of content page 1 Introduction 1 2 Hard and Software 2 3 Prerequisites 3 4 Naming conventions Deutsche Börse Systems AG --- VTAM definitions Deutsche Börse Systems AG --- MVS/APPC definitions Deutsche Börse Systems AG --- IMS definitions Customer s system --- APPC applications Customer system --- IMS application 9 5 Appendix A: Asynchronous transaction processing between customer s system and IMS 10

3 Deutsche Börse Systems AG Page: 1 1 Introduction Customer s connection to XONTRO using a LU 6.2 (diagram): Deutsche Börse Systems AG IBM RS/6000 Windows MVS Sun Solaris IBM AS/400 NCP VTAM MVS APPC IMS Control Region IMS MPP IMS MPP IMS MPP For those connection options presented in the diagram above, informations and hints for the connection set up via LU6.2 connection (APPC = Advanced Program to Program Communication) will be presented in this chapter. As the communication partner system (on the customer s side), a system is assumed to exist which is configurated and capable to communicate using APPC, and whose communication software supports LU6.2 protocol types. In addition to the preparing measures concerning the LU 6.2 connection, a dedicated leased line and the appendant modems are needed, as well as the expanded network definitions for both systems (IMS, VTAM resp. APPC controlling software of the financial institute), and the implementation of the APPC adress space within the Deutsche Börse Systems AG production environment. The conection to the bank using APPC will be handled using LU62 parallel sessions as a standard procedure, whereas a maximum of 4 sending sessions per bank s CBF account number are permitted. The distribution among those 4 sessions will be done automatically by the application. Thus, the parallel usage of the available sessions is supported by the Deutsche Börse Systems AG. Up to 4 messages may be sent simultanuously at the same time (e.g. order entry confirmations, execution confirmations, etc.). Deutsche Börse Systems AG will perform all necessary connection definitions at certain networks / IMS generation dates (these dates may be retrieved from our homepage This applies specifically to the naming conventions of the APPC LU names at the customer s site that have to be defined and agreed upon. These names have to be declared within the customer s systems, too.

4 Deutsche Börse Systems AG Page: 2 2 Hard and Software Within the Deutsche Börse Systems AG, an IBM host has been set up as the production computer, using the following operating system software: OS/390 VTAM NCP IMS

5 Deutsche Börse Systems AG Page: 3 3 Prerequisites The financial institute which is to be connected must have a PU Type 2.1 capable connection to the Deutsche Börse Systems AG installed. Furthermore, the VTAM Application ID must not be equal to DEBDZA11 (= VTAM APPL ID Deutsche Börse Systems AG production IMS/APPC), or DEBDZA29 (= VTAM APPL ID Deutsche Börse Systems AG test IMS/APPC), or DEBDZA27 (= VTAM APPL ID Deutsche Börse Systems AG simulation IMS/APPC). Care should be taken so that the VTAM APPL IDs of the connecting financial institutes will be different to the names mentioned above.

6 Deutsche Börse Systems AG Page: 4 4 Naming conventions The naming conventions for LU6.2 connections within Deutsche Börse Systems AG are defined as follows: IMS/APPC LU name production system IMS1: DEBDZA11 IMS/APPC LU name simulation system IMS27: DEBDZA27 IMS/APPC LU name test system IMS29: DEBDZA29 TPname (=transaction) in all three systems : BCSnnnnA (nnnn=cbf account number of the financial institute) Note: BCSnnnnA will be mapped to BC$nnnnA within the exchange applications The following naming conventions for LU6.2 connections should be adhered to by the customer : LU Name production system : LU Name simulation system : LU Name test system : Innnn000 (nnnn=customer s CBF account number) Innnn100 (nnnn= customer s CBF account number) Innnn200 (nnnn= customer s CBF account number) TPName in all systems : BC01 BC04 (resp. only BC01)

7 Deutsche Börse Systems AG Page: Deutsche Börse Systems AG --- VTAM definitions The computer/computer coupling device between the customer s system and the IBM mainframe of the Deutsche Börse Systems AG will be handled using SNA, MVS/APPC to the IMS. The set up / input necessary for the system generation at the Deutsche Börse Systems AG s side will not be given in detail in this section. The VTAM definitions of Deutsche Börse Systems AG describe: - the ACB names (=LU names) of the customer s systems - the VTAM logmode entry IMS adaptor as the communication partner of the financial institute ACB definitions DEBDZAxx APPL ACBNAME=DEBDZAxx, (11=prod., 27=simulation, 29=test) OPERCNOS=ALLOW, DDRAINL=NALLOW, DSESLIM=16, EAS=509, MODETAB=#MODTABX, DLOGMOD=APPCMODE, PARSESS=YES, SECACPT=CONV, SRBEXIT=YES, VPACING=10 VTAM logmode entry LU62APPC MODEENT LOGMODE=LU62APPC, COS=ROUTM001, TYPE=X 00, FMPROF=X'13', TSPROF=X'07', PRIPROT=X'B0', SECPROT=X'B0' COMPROT=X'50B5', RUSIZES=X'8585', PSERVIC=X' F00'

8 Deutsche Börse Systems AG Page: Deutsche Börse Systems AG --- MVS/APPC definitions The transaction name within the IMS system of the Deutsche Börse Systems AG is BC$nnnnA. As this may causes mapping errors within certain platforms (in this case the $ symbol), the customer should initiate the process/program BCSnnnnA. The mapping to the correct transaction name will then be done using the APPC TP profile. The maintenance of the TP profiles may be done using the following job (jcl): //TPKL EXEC PGM=ATBSDFMU, // COND=EVEN //STEPLIB DD DISP=SHR, // DSN=IMS.xx.RESLIB //SYSSDLIB DD DSN=SYS1.xxxx.APPCTP,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSSDOUT DD SYSOUT=* //SYSIN DD DATA,DLM=XX TPADD TPSCHED_EXIT(DFSTPPE0) TPNAME(BCSnnnnA) SYSTEM ACTIVE(YES) TPSCHED_DELIMITER(END_IMS_DATEN) TRANCODE=BC$nnnnA CLASS=1 MAXRGN=1 RACF=NONE END_IMS_DATEN XX //* //TPLS EXEC PGM=ATBSDFMU, // COND=EVEN //SYSSDLIB DD DSN=SYS1.xxxx.APPCTP,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSSDOUT DD SYSOUT=* //SYSIN DD DATA TPRETRIEVE TPNAME(BCSnnnnA) /*

9 Deutsche Börse Systems AG Page: Deutsche Börse Systems AG --- IMS definitions The transmission of messages (execution confirmations etc.) to the customer systems from the IMS applications will generally be done using the alternate PCB. The INSERT is done onto a so-called DESCRIPTOR AnnnnX11 X14, which behaves similar to a LTERM from the customer s site view. Within the DESCRIPTOR, the LU- and the TP- name of the customer s system, as well as the VTAM mode table entry LU62APPC, the SYNCLEVEL CONFIRM and the CONVERSATIONTYPE MAPPED are deposited. All DESCRIPTOR entries are located in the PROCLIB Member DFS62DTx (x=nucleus SUFFIX): U AnnnnX11 LUNAME=Innnn000 MODE=LU62APPC TPNAME=BC01 U AnnnnX11 SYNCLEVEL=C CONVTYPE=M U AnnnnX12 LUNAME=Innnn000 MODE=LU62APPC TPNAME=BC01 U AnnnnX12 SYNCLEVEL=C CONVTYPE=M U AnnnnX13 LUNAME=Innnn000 MODE=LU62APPC TPNAME=BC01 U AnnnnX13 SYNCLEVEL=C CONVTYPE=M U AnnnnX14 LUNAME=Innnn000 MODE=LU62APPC TPNAME=BC01 U AnnnnX14 SYNCLEVEL=C CONVTYPE=M

10 Deutsche Börse Systems AG Page: Customer s system --- APPC applications The declaration of the IMS transaction code will be done in the ALLOCATE statement, normally using the parameter TPN. If, within the ALLOCATE statement, the parameter TPN="other partner LU" (e.g. Innnn000) is inserted, then a "Message Switch" occurs after the conversation set up within IMS. The message sent will be sent back asynchronously to the LU (customer s system) immediately after the performed "IMS Message Switch". A 4-byte header (2-byte length, 2-byte ID field = low value) hast to be prefixed to each of the logical data records to be transmitted by the APPC application. This rule is valid for the usage of the MAPPED CONVERSATION verbs.

11 Deutsche Börse Systems AG Page: Customer system --- IMS application An APPC application is only capable to communicate with an IMS application in the asynchronous mode. The asynchronous processing mode is indicated by the following APPC verbs within the processing sequence: ALLOCATE TPN(BCSnnnnA) SEND_DATA 'data to transmit' DEALLOCATE The requested IMS application hast to be generated as a NON RESPONSE (non conversational) transaction in this case. That way, the asynchronous processing mode allows the transfer of data, IMS commands, or the execution of a "message switch". For the operational sequence shown above, the transaction has to be generated with the option SINGLE SEGMENT included. The data records transferred will be handed over within the IMS in single message segments, and they will be assigned to the processing unit using one single read operation (GU = Get Unique) each: 'data to transmit' (GU call) Configuration of messages ('data to transmit'): bank Deutsche Börse Systems AG: beginning with the 1st digit: data (SWIFT Message) Deutsche Börse Systems AG bank: beginning with the 1st digit: data (SWIFT Message) Note: The IMS transaction will only be initiated after the transfer of the DEALLOCATE. This results in that: By using a NON RESPONSE transaction, the processing of the IMS application will only be started after the data transfer has been accomplished including the trailing DEALLOCATE statement.

12 Deutsche Börse Systems AG Page: 10 5 Appendix A: Asynchronous transaction processing between customer s system and IMS IMS MVS / APPC Bank (Kundensystem) session does not exist session / conversation allocated APPC Anwendung A - ATTACH LU6.2 - ALLOCATE TPN = BCSnnnnA Sync_level = CONFIRM - Return_Code = OK Transaction queued data received - SEND_DATA Return_Code = OK positive SNA response Transaction scheduled Transaction: BC$xxxxA conversation deallocated - DEALLOCATE TYPE (LOCAL Return_Code = - DETACH LU 6.2 OK positive response Sync_Level = CONFIRM BC$xxxxA Empfangsprogramm Kunde - GU I/O-PCB Return_Code = 'QC' Goback - CHNG ALT-PCB (AnnnnX11) ISRT ALT-PCB next record conversation allocated data received data converted to APPC format SEND_DATA request CONFIRM - ATTACHLU RECEIVE_AND_WAIT Return_Code = OK What_received = DATA_COMPLETE - RECEIVE_AND_WAIT Return_Code = OK What_received = CONF_DEALLOCATED positive response - CONFIRMED conversation deallocated - DEALLOCATED TYPE (LOCAL) BC$xxxxA output dequeued session does not terminate - DETACHLU 6.2