2.2. Bases teóricas
2.2.6. Dimensiones del desempeño docente 38
enquiry output
OF S
stands for “Open financial service” though it’s not a service – just a script language (though without programming capabilities) to ma- nipulate records in T24 application. And it’s a must for a techie to know. Manuals give quite comprehensive explanation of OFS syntax so I will not go deeper into it here. Instead let’s try to use it to create or update T24 applications.Firstly let’s create an appropriate record in OFS.SOURCE application. Log in into T24 and type OFS.SOURCE, I TEST at AWAITING APPLICATION prompt. “I” is the function used to input a record.
What I can say now about functions? In brief the rules are:
• Use function I in “pure” application or in regular VERSION to in- put an unauthorised record (use F3 after I to have id assigned by T24 automatically).
• Use function I in “zero-authorisation” VERSION to input an autho- rised record.
• Unauthorised record can be deleted (function D), authorised (func- tion A) or (depending on application) put to “HOLD” (type IHLD to do it).
• Authorised record can (depending on application) be amended (again function I; not all fields can be amended – there are so-called “NOCHANGE” ones) – with or without further authorisation – or reversed (function R) – again authorisation might or might not be required. Reversed records go to “history” file – for those applications which support history (see above FILE.CONTROL, field suffixes). To history file also go “LIVE” records after each change (we saw it above with ACCOUNT) or after their retention period expires (e.g. for FUNDS.TRANSFER it happens every day after close
of business – COB).
• Use function S to see a record. If you’re not going to edit a record, better use this function intead of I to avoid locks but keep in mind that all fields that are empty will not be shown.
• All records can be printed (function P) though it is mainly used for output to flat file.
• Use function C to copy a record (wherever the application allows that). • Authorised records can be listed using function L. “L L” is used to search authorised file, “L -something” allows to jump to a record starting with something, e.g. “EB.ERROR L -D” allows to list EB.ERROR records starting from DC-999.NOT.ALLOWED.
• Unauthorised records can be listed using function E. “E E” is used to search unauthorised file, “E -something” also works the same way as “L -something”.
So – command is “OFS.SOURCE, I TEST”. Why the comma after appli- cation name? Answer – to create the record in one step. VERSION (read – input screen) name consists of name of application followed by comma and a suffix. This suffix may be absent so we get just application name and a comma. Don’t think that comma itself means zero-authorisation – it’s an internal agreement that “comma-versions” are simple VERSION records that are setup for zero authorisation with no additional features like selective fields display, tabbed view and so on:
R10 Model Bank VERSION SEE PGM.NAME.VERSION.. OFS.SOURCE, --- 2 RECORDS.PER.PAGE.. 1 3 FIELDS.PER.LINE... 1 46 NO.OF.AUTH... 0 55. 1. 1 VAL.ASSOC... LOGIN.ID 55. 1. 2 VAL.ASSOC... EB.PHANT.ID 57 LOCAL.REF.FIELD... LOCAL.REF 65 REPORT.LOCKS... YES 103 CURR.NO... 1
104. 1 INPUTTER... 6 WOODY-00 OFS BROWSERTC 105. 1 DATE.TIME... 02 APR 10 17:40
106 AUTHORISER... 6 WOODY-00 OFS BROWSERTC
107 CO.CODE... GB-001-0001 R10 Model Bank 108 DEPT.CODE... 4 Retail Banking User 4
--- 15 OCT 2010 13:29:32 USER (05 JAN) VLADIMIR.K PAGE 1 ACTION
AWAITING PAGE INSTRUCTIONS
It’s a good idea never to amend any comma version and leave them for the purpose they were designed for.
Under “appropriate” OFS.SOURCE record I mean the one with the fol- lowing field values:
R10 Model Bank OFS SOURCE, INPUT SOURCE.NAME... TEST
--- 1 DESCRIPTION... TEST ONE
2 SOURCE.TYPE... TELNET 3. 1 LOGIN.ID... any 4. 1 EB.PHANT.ID... 5 MAX.CONNECTIONS... 6 RESTRICT.LINK... 7 INITIAL.ROUTINE... 8 CLOSE.ROUTINE... 9 IN.MSG.RTN... 10 OUT.MSG.RTN... 11 MSG.PRE.RTN... 12 MSG.POST.RTN... 13 LOG.FILE.DIR... 14 LOG.DETAIL.LEVEL. NONE 15 OFFLINE.QUEUE.... 16 MAINT.MSG.DETS... --- 16 OCT 2010 09:12:16 USER (05 JAN) VLAD.K PAGE 1 >>>4>>> ACTION
Note that field log.detail.level was automatically set to “NONE” – this is business logic we were talking about earlier.
R10 Model Bank OFS SOURCE, INPUT SOURCE.NAME... TEST --- 17 DET.PREFIX... 18 IN.QUEUE.DIR... 19 IN.QUEUE.NAME... 20 OUT.QUEUE.DIR... 21 OUT.QUEUE.NAME.... 22 QUEUE.INIT.RTN.... 23 QUEUE.CLOSE.RTN... 24 SYNTAX.TYPE... OFS 25. 1 LOCAL.REF... 26 GENERIC.USER... INPUTTER 27 IN.DIR.RTN... 28 VERSION... 29 IB.USER.CHECK... 30 EOD.VALIDATE... 31 FIELD.VAL... 32. 1 ATTRIBUTES.... --- 16 OCT 2010 09:12:16 USER (05 JAN) VLAD.K PAGE 2 >>>4>>> ACTION
To jump to particular field just type its number. E.g. after typing “any” on the first page you can go directy to the second one using F4 F3 and then type 24 to jump directly to the field syntax.type. Note that you can’t jump to so-called “NOINPUT” fields – try, for example, to type 25.1.
Having populated fields syntax.type and generic.user, use F5 to commit the record.
This is the required minimum we can proceed with; we’ll add then some additional features to see how they work.
Log out of T24 to jsh. Then launch the program that represents another point of entry into T24 using our OFS.SOURCE record id as a parameter:
jsh mb10 ~-->tSS TEST ←-
<tSS version="1.1"><t24version>R10.000</t24version> <t24pid>556</t24pid><t24ofssource>TEST</t24ofssource> <clientIP/></tSS>
Then type an OFS message. The simplest one looks like:
ENQUIRY.SELECT,,INPUTT/123456,%USER ←-
,@ID::@ID/USER.NAME::USER.NAME/SIGN.ON.NAME
::SIGN.ON.NAME/LANGUAGE::LANGUAGE/DEPARTMENT.CODE ::DEPARTMENT.CODE,"ACCTEXEC " " Account Executive "
"ACCTEXEC1 " "1 " "1 ","ARCUSER " "TFOFFICER " "TFOFFICER " "1 " "1 ","AUTHORISER " "AUTHORISER " "AUTHOR " "1 " "1 ","BTOOLSUSER " "BUSINESS TOOLS USER " "BTOOLS " "1 " "1 ","BU0
etc
This was output from so-called “percent enquiry”. These enquiries are called whenever you use L function for an application. So it’s a good idea never to amend such enquiries (exactly the same advice as for comma versions – see above).
To exit from tSS type EXIT.
Note: though tSS is a part of older connectivity scheme used in R08 and below, it’s still around and useful for such purposes as one described above.