DIN CWA 14050-9-2001 Extensions for Financial Services (XFS) interface specification - Release 3 0 - Part 9 Text terminal unit device class interface (English Version CWA 14050-9 2.pdf

1、April 2001Extensions for Financial Services (XFS)interface specification Release 3.0 Part 9: Text Terminal Unit Device Class InterfaceCWA 14050-9Englische Fassung CWA 14050-9:2000ICS 35.200; 35.240.40Erweiterungen fr die Schnittstellenspezifikation fr Finanzdienst-leistungen (XFS) Version 3.0 Teil 9

2、: Schnittstelle fr die Gerteklasse “Textterminals“Nationales VorwortDieses CEN Workshop Agreement CWA 14050-9, das vom CEN/ISSS XFS Workshop erarbeitet wurde,wird ausschlielich in englischer Sprache zur Verfgung gestellt.CEN Workshop Agreements werden im Rahmen eines Konsortiums entwickelt. Sie unte

3、rscheiden sich vonEuropischen Normen dadurch, dass sie grundstzlich kein ffentliches Einspruchsverfahren durchlaufenund dass auch keine nationale Meinungsbildung stattfindet. Im Gegensatz zu Europischen Normen, dieden Konsens aller interessierten Kreise darstellen, haben CEN Workshop Agreements ledi

4、glich dieZustimmung der unmittelbar beteiligten Mitglieder des Konsortiums gefunden.Fr den Inhalt sind ausschlielich die Mitglieder des Konsortiums verantwortlich (siehe ergnzendeHinweise im CWA-Vorwort). Weder das CEN-Zentralsekretariat, noch die CEN-Mitglieder haben den Inhaltauf eventuelle Fehler

5、 oder Widersprche zu Normen und Rechtsvorschriften geprft.Fortsetzung 37 Seiten CWA Beuth Verlag GmbH, 2001 .Jede Art der Vervielfltigung, auch auszugsweise, Ref. Nr. DIN CWA 14050-9:2001-04nur mit Genehmigung des Beuth Verlages gestattet. RW DIN CWA Preisgr. 05Alleinverkauf der Normen durch Beuth V

6、erlag GmbH, 10772 BerlinB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Leerseite B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Rue de Stassart, 36 B-1050 BruxellesTel : +32 2 550 08 11 Fax : +32 2 550 08 19EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EURO

7、PEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG WORKSHOPCWA 14050-9AGREEMENTNovember 2000ICS 35.200; 35.240.40Extensions for Financial Services (XFS) interface specification -Release 3.0 - Part 9: Text Terminal Unit Device Class Interface 2000 CEN All rights of exploitation in any form and by an

8、y means reserved world-wide forCEN National MembersRef. No CWA 14050-9:2000 EThis CEN Workshop Agreement can in no way be held as being an official standardas developed by CEN National Members.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 2CWA 14050-9:2000Table of Content

9、sForeword. 41. Introduction. 61.1 Background to Release 3.0 61.2 XFS Service-Specific Programming 62. Text Terminal Unit 83. References 94. Info Commands 104.1 WFS_INF_TTU_STATUS . 104.2 WFS_INF_TTU_CAPABILITIES. 114.3 WFS_INF_TTU_FORM_LIST. 124.4 WFS_INF_TTU_QUERY_FORM 134.5 WFS_INF_TTU_QUERY_FIELD

10、 144.6 WFS_INF_TTU_KEY_DETAIL . 155. Execute Commands . 185.1 WFS_CMD_TTU_BEEP . 185.2 WFS_CMD_TTU_CLEARSCREEN 185.3 WFS_CMD_TTU_DISPLIGHT 195.4 WFS_CMD_TTU_SET_LED. 195.5 WFS_CMD_TTU_SET_RESOLUTION 205.6 WFS_CMD_TTU_WRITE_FORM. 205.7 WFS_CMD_TTU_READ_FORM 215.8 WFS_CMD_TTU_WRITE . 225.9 WFS_CMD_TTU

11、_READ. 235.10 WFS_CMD_TTU _RESET 266. Events 276.1 WFS_EXEE_TTU_FIELDERROR 276.2 WFS_EXEE_TTU_FIELDWARNING 276.3 WFS_EXEE_TTU_KEY 277. Form and Field Definitions 297.1 Definition Syntax . 297.2 XFS form/media definition files in multi-vendor environments 297.3 Form Definition . 30B55EB1B3E14C22109E9

12、18E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 3CWA 14050-9:20007.4 Field Definition . 318. C - Header file 32B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 4CWA 14050-9:2000ForewordThis CWA is revision 3.0 of the XFS interface specification.The move from an XFS 2.

13、0 specification (CWA 13449) to a 3.0 specification has been prompted by a series of factors.Initially, there has been a technical imperative to extend the scope of the existing specification of the XFS Manager toinclude new devices, such as the Card Embossing Unit.Similarly, there has also been pres

14、sure, through implementation experience and the advance of the Microsofttechnology, to extend the functionality and capabilities of the existing devices covered by the specification.Finally, it is also clear that our customers and the market are asking for an update to a specification, which is now

15、over 2years old. Increasing market acceptance and the need to meet this demand is driving the Workshop towards this release.The clear direction of the CEN/ISSS XFS Workshop, therefore, is the delivery of a new Release 3.0 specification basedon a C API. It will be delivered with the promise of the pr

16、otection of technical investment for existing applications andthe design to safeguard future developments.The CEN/ISSS XFS Workshop gathers suppliers as well as banks and other financial service companies. A list ofcompanies participating in this Workshop and in support of this CWA is available from

17、 the CEN/ISSS Secretariat.This CWA was formally approved by the XFS Workshop meeting on 2000-10-18. The specification is continuouslyreviewed and commented in the CEN/ISSS Workshop on XFS. It is therefore expected that an update of thespecification will be published in due time as a CWA, superseding

18、 this revision 3.0.The CWA is published as a multi-part document, consisting of:Part 1: Application Programming Interface (API) - Service Provider Interface (SPI); Programmers ReferencePart 2: Service Classes Definition; Programmers ReferencePart 3: Printer Device Class Interface - Programmers Refer

19、encePart 4: Identification Card Device Class Interface - Programmers ReferencePart 5: Cash Dispenser Device Class Interface - Programmers ReferencePart 6: PIN Keypad Device Class Interface - Programmers ReferencePart 7: Check Reader/Scanner Device Class Interface - Programmers ReferencePart 8: Depos

20、itory Device Class Interface - Programmers ReferencePart 9: Text Terminal Unit Device Class Interface - Programmers ReferencePart 10: Sensors and Indicators Unit Device Class Interface - Programmers ReferencePart 11: Vendor Dependent Mode Device Class Interface - Programmers ReferencePart 12: Camera

21、 Device Class Interface - Programmers ReferencePart 13: Alarm Device Class Interface - Programmers ReferencePart 14: Card Embossing Unit Class Interface - Programmers ReferencePart 15: Cash In Module Device Class Interface- Programmers ReferencePart 16: Application Programming Interface (API) - Serv

22、ice Provider Interface (SPI) - Migration from Version 2.0 (seeCWA 13449) to Version 3.0 (this CWA) - Programmers ReferencePart 17: Printer Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA) -Programmers ReferenceB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD

23、9NormCD - Stand 2007-03 Page 5CWA 14050-9:2000Part 18: Identification Card Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers ReferencePart 19: Cash Dispenser Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (t

24、hisCWA) - Programmers ReferencePart 20: PIN Keypad Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA)- Programmers ReferencePart 21: Depository Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA) -Programmers Refere

25、ncePart 22: Text Terminal Unit Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers ReferencePart 23: Sensors and Indicators Unit Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version3.0 (this CWA) - Programmers Reference

26、Part 24: Camera Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA) -Programmers ReferencePart 25: Identification Card Device Class Interface - PC/SC Integration GuidelinesIn addition to these Programmers Reference specifications, the reader of this CWA is a

27、lso referred to a complementarydocument, called Release Notes. The Release Notes contain clarifications and explanations on the CWA specifications,which are not requiring functional changes. The current version of the Release Notes is available online fromhttp:/www.cenorm.be/isss/Workshop/XFS.The in

28、formation in this document represents the Workshops current views on the issues discussed as of the date ofpublication. It is furnished for informational purposes only and is subject to change without notice. CEN/ISSS makesno warranty, express or implied, with respect to this document.Revision Histo

29、ry:1.0 May 24, 1993 Initial release of API and SPI specification1.11 February 3, 1995 Separation of specification into separate documents for API/SPI andservice class definitions2.00 November 11, 1996 Update release encompassing the self-service environment3.00 October 18, 2000 Addition of the reset

30、 commandUNICODE supportAddition of the command WFS_INF_TTU_KEY_DETAILEnhancement of the WFS_CMD_TTU_READ commandAddition of the events WFS_EXEE_TTU_FIELDWARNING,WFS_EXEE_TTU_FIELDERROR, and WFS_EXEE_TTU_KEYFor a detailed description see CWA 14050-22TTU Migration from Version 2.00 to Version 3.00, Re

31、vision 1.00,October 18, 2000.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 6CWA 14050-9:20001. Introduction1.1 Background to Release 3.0The CEN XFS Workshop is a continuation of the Banking Solution Vendors Council workshop and maintains atechnical commitment to the Win 3

32、2 API. However, the XFS Workshop has extended the franchise of multi vendorsoftware by encouraging the participation of both banks and vendors to take part in the deliberations of the creation ofan industry standard. This move towards opening the participation beyond the BSVCs original membership ha

33、s beenvery succesful with a current membership level of more than 20 companies.The fundamental aims of the XFS Workshop are to promote a clear and unambiguous specification for both serviceproviders and application developers. This has been achieved to date by sub groups working electronically and q

34、uarterlymeetings.The move from an XFS 2.0 specification to a 3.0 specification has been prompted by a series of factors. Initially, therehas been a technical imperative to extend the scope of the existing specification of the XFS Manager to include newdevices, such as the Card Embossing Unit.Similar

35、ly, there has also been pressure, through implementation experience and the advance of the Microsofttechnology, to extend the functionality and capabilities of the existing devices covered by the specification.Finally, it is also clear that our customers and the market are asking for an update to a

36、specification, which is now over 2years old. Increasing market acceptance and the need to meet this demand is driving the Workshop towards this release.The clear direction of the XFS Workshop, therefore, is the delivery of a new Release 3.0 specification based on a C API.It will be delivered with th

37、e promise of the protection of technical investment for existing applications and the design tosafeguard future developments.1.2 XFS Service-Specific ProgrammingThe service classes are defined by their service-specific commands and the associated data structures, error codes,messages, etc. These com

38、mands are used to request functions that are specific to one or more classes of serviceproviders, but not all of them, and therefore are not included in the common API for basic or administration functions.When a service-specific command is common among two or more classes of service providers, the

39、syntax of thecommand is as similar as possible across all services, since a major objective of the Extensions for Financial Services isto standardize command codes and structures for the broadest variety of services. For example, using the WFSExecutefunction, the commands to read data from various s

40、ervices are as similar as possible to each other in their syntax anddata structures.In general, the specific command set for a service class is defined as the union of the sets of specific capabilities likely tobe provided by the developers of the services of that class; thus any particular device w

41、ill normally support only a subsetof the command set defined for the class.There are three cases in which a service provider may receive a service-specific command that it does not support:The requested capability is defined for the class of service providers by the XFS specification, the particular

42、 vendorimplementation of that service does not support it, and the unsupported capability is not considered to befundamental to the service. In this case, the service provider returns a successful completion, but does no operation.An example would be a request from an application to turn on a contro

43、l indicator on a passbook printer; the serviceprovider recognizes the command, but since the passbook printer it is managing does not include that indicator, theservice provider does no operation and returns a successful completion to the application.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9Nor

44、mCD - Stand 2007-03 Page 7CWA 14050-9:2000The requested capability is defined for the class of service providers by the XFS specification, the particular vendorimplementation of that service does not support it, and the unsupported capability is considered to be fundamentalto the service. In this ca

45、se, a WFS_ERR_UNSUPP_COMMAND error is returned to the calling application. Anexample would be a request from an application to a cash dispenser to dispense coins; the service providerrecognizes the command but, since the cash dispenser it is managing dispenses only notes, returns this error.The requested capability is not defined for the class of service providers by the XFS specification. In this case, aWFS_ERR_INVALID_COMMAND error is returned to the calling