version routines and api.doc

8/21/2019 VERSION ROUTINES AND API.doc

1/25

T24 Technical Training

APPLICATIONPROGRAMMING

INTERFACES

Application Program Interfaces Page 1 of 25


2/25


APPLICATION PROGRAM INTERFACES

1.1 Introduction

This chapter describes the available options for developers who wish to enhance

the operation of the current GLOBUS system, where there are insufficient optionsprovided by the Standard GLOBUS utilities. Within specific applications thesystem allows universe subroutines or Uni!erse commands in some cases" tobe defined, which will then be invo#ed when runnin$ the applications. Thisprovides a powerful tool to allow customisation of the GLOBUS to meet re$ionalor customer specific re%uirements.

1.2 APPLICATION CUSTOMISATION

1.2.1 Introduction

This section is concerned with the options available in customisin$ the operationand content of GLOBUS applications.

1.2.2 VERSION APPLICATION - USER DEFINED SUBROUTINES

The VERSION application allows user defined subroutines to be specified in thefollowin$ fields&

'(UT.)*W.+O)T*)T

!(L-(TO).T)

')/UT.OUT)*

(UT0.OUT)*

1.2.2.1 AUT.NEW.CONTENT (Fi!d "".1#

This field would normally be used to automatically enter a value into a fieldspecified in the associated (UTO1.2*L-.)O.The automatic contents are onlyused if the e3istin$ content of the field matches that defined in the associated

(UT.OL-.+O)T*)T. This field may also contain a sub4routine used to performconditional defaultin$ that cannot be defined in !ersion, or defaultin$ from relatedfiles.



3/25


The followin$ steps must be followed&

(UTO1.2*L-.)O The name of the field that has to be automatically defaulted.

(UT.)*W.+O)T*)T @user-deined su!routine

U$r-d%ind $u&routin must be defined in /G1.2L* as a type S application.The field (//L.2O.SUB contains the applications allowed to use thesubroutine.

*3ample&

The followin$ e3ample demonstrates a routine, which will automatically assi$nthe industry code and industry name in the file T).S0(*.1(ST*.

Figure 1.1 PGM.FILE For V.INDUSTRY.NAME

Figure 1.2 VERSION Automati !e"au#ti$g !e"i$itio$



4/25


To default the )-UST5.+O-* and )-UST5.)(1* field usin$ the routine!.)-UST5.)(1*.

Program %

0001: SUBROUTINE V.INUSTR!.N"#E0002: $ S%&ro%'ine 'o (efa%l' 'he )al%e of in(%*'r+ co(e an( in(%*'r+ na,e in0003: $ 'he a--lica'ion TRN.S"RE.#"STER0004: $0005: /INSERT IO##ON000: /INSERT IEU"TE000: /INSERT I.INUSTR!0006: /INSERT I.TRN.S"RE.#"STER0007: $0010: TE#P 8 IE9I.NE;=


5/25


*3ample &

0001: $S%&ro%'ine 'o checA he'her 'he 'ra(ing %ni' i* a ,%l'i-le0002: $ of 120003: $

0004: SUBROUTINE V.TR"E.UNIT.V"90005: $000: /INSERT IO##ON000: /INSERT IEU"TE0006: /INSERT I.TRN.S"RE.#"STER0007: /INSERT I.TRN.S.TR"NS"TION0010: $0011: "99 BRCTRN.S"RE.#"STERD:#:TRS#.TR"IN.UNITS


6/25


E%&'()e *

0001: $S%&ro%'ine 'o %-(a'e 'he TRN.S"RE.O9IN a' a%'horiGa'ion *'age0002: $0003: SUBROUTINE V.UP"TE.S"RE.O9IN0004: $

0005: /INSERT IO##ON000: /INSERT IEU"TE000: /INSERT I.TRN.S"RE.O9IN0006: /INSERT I.TRN.S.TR"NS"TION0007: $0010: OSUB INITI"9ISE0011: OSUB PROESS0012: RETURN0013: $0014: INITI"9ISE:0015: N.TRN.S"RE.O9IN 8 @.TRN.S"RE.O9IN@001: "99 OPN.TRN.S"RE.O9IN


7/25


1.2.2.' INPUT ROUTINE (Fi!d ''.1#

( subroutine may be e3ecuted at the unauthori


8/25


FIELD NO Specifies a$ainst which field the condition is to be met. E%N&tion&)it, 1/

DATA.OMPARISON Specifies the type of comparison to be made between thecontents of the field indicated in 2*L-.)Oand the values

specified in -(T(.2O1and -(T(.TO. E%. E0

DATA.FROM Specifies the value, or start of a ran$e of values, with whichthe contents of the field indicated in 2*L- )O are to becompared with. E% US

DATA.TO Specifies the end of a ran$e of values with which thecontents of the field indicated in 2*L- )O are to becompared with.

The version +USTO1*,T*ST limits the user to listin$ and seein$ only thoserecords of the customer application where the nationality is US.

1.2." OVERRIDE.CLASS.DETAILS

OVERRIDE.CLASS.DETAILS allows a subroutine to be defined to manipulate anoverride messa$e so that the conditions defined in this table may be applied to it.2or e3ample, an overdraft messa$e could be converted into local currency forallocatin$ an override class dependin$ on the amount.

1.2. PGM.FILEThe PGM.FILE has several uses for developers wishin$ to customise GLOBUS.

-efinition of Subroutines to be used in applications

-efinition of new applications to be run on4line

'-efinition of routines which may be run in the batch

1.2..1 PROGRAM I"/2or on4line applications the #ey to this record must be the same as the pro$ramto be run.

For'&t* Subroutine nameSubroutine name is the name of the application, which can be invo#ed. The field

T5/* indicates the application type to be e3ecuted. 2or on4line use this may0,U,L,T,W or 1. This is invo#ed from U).(//L+(TO)

(ny application of types 0,U,L,T or W are used to maintain a file and mustconform to the standard T*1/L(T* application type.

Type 1 routines are used to e3ecute a specific main line pro$ram where there isno standard file maintenance re%uired, for e3ample a conversion pro$ram, or



9/25


pro$ram to print a report. Where a history is re%uired of a pro$ram bein$ run, atype W pro$ram should be used.

When a type 1 pro$ram is written, it 'ust contain a SUBOUT)* statement atthe start in order to return to GLOBUS once e3ecuted.

*3ample& The type 1 pro$ram SB.LST.LO+7s allows an operator to list theactive system loc#s.

The pro$ram for SB.LST.LO+7S is as follows&

???@& SUBOUT)* SB.LST.LO+7S???6& A???& A This pro$ram performs the LST.*(-U command???C& A???D& *E*+UT* F+SF ; A +lear Screen???& *E*+UT* FLST.*(-UF???H& +T F/ress eturn TO eturn to GLOBUSF&???I& )/UT W(T???J& *TU)??@?& A??@@& *)-

The /G1.2L* record for SB.LST.LO+7S is as follows&

The result of e3ecution of SB.LST.LO+7S subroutine at GLOBUS (ction promptis as follows&



10/25


1.2..2 ATC3.4OThis field is used to define the names of subroutines, or Uni!erse commands,which may be e3ecuted from the GLOBUS BATCH.CONTROL process. To bee3ecuted durin$ the end of day the B(T+0.KOB must be defined on a BATCHrecord.

For'&t* Subroutine name or !niVer"e Comman#

Subroutine name is the name of the application, which can be invo#ed.!ni$er"e Comman# i" the name of the item defined in the local !O+ file to bee3ecuted.

This is a multi4valued field, and several subroutines and or commands may bee3ecuted se%uentially. This is invo#ed from B.)T(T*./O+*SS. ( subroutinemay be written to perform specific end of day processin$. This may have avariety of functions, such as maintenance of local files8applications, production ofreports, interface file production etc.

( Uni!erse command, or para$raph can also be e3ecuted from this option. (ny

item reco$nised in the !O+ file of the correct type may be e3ecuted.



11/25


1.2. ATC3.CONTROL

(/ calls li#e subroutine, script, crystal report or en%uiry can be run at the prebatch sta$e. 1ultiple calls may be defined by e3pandin$ the multi4values.

For'&t* Subroutine name

t has to be defined in !O+SPT S%ri&t Name

t has to be defined in 2.S+/T.-*SG)*RPT Re&ort Name

t has to be defined in 2.*/OT.+O)TOL and it has to be a crystal report.EN' En(uir) Name

t has to be defined in 2.*)U5This is a multi4valued field and several (/ calls may be e3ecuted se%uentially.

This is invo#ed from B(T+0.+O)TOL. This routine is called Must before controlpasses to the batch menu.

1.5 S#STEM MANAGEMENT CUSTOMISATION

1.5.1 IntroductionThis section contains details of options available to users for customisation of

system mana$ement. This includes the ability to be able to define commands ore3ecutable pro$rams" to perform system bac#ups as part of the end of dayprocess.

1.5.2 SPFThe SPF file allows definition of the commands" used to perform the systembac#up and restore at end of day.

1.5.2.1 UNI$ AC6UP &nd UNI$ RESTOREThese fields allow definition of the U)E bac#up and restore commands to bee3ecuted when the end of day process is run.

For'&t* !NI* %omman# name!NI* %omman# name may contain any U)E commands" to be e3ecuted. tmay also contain a shell script. This is invo#ed from S5ST*1.B(+7U/ andS5ST*1.*STO*

1. REPORTING 7 EN0UIR# CUSTOMISATION



12/25


1..1 Introduction

The GLOBUS utilities REPGEN and EN'!IR+ provide several (/s for userswho wish to perform operations on data outside the delivered functionality.

GLOBUS also provides options for users to redirect output from reports or micro4fiches, which could include definition of their own subroutines.

1..2 EN0UIR#

The EN'!IR+ application provides three main areas where local routines maybe added to provide additional functionality. These are&

'Selection of data where criteria cannot be easily specified within the

e3istin$ application this will be covered under STANDARD.SELECTION"

'+O)!*SO) routines to manipulate8enhance data to re%uired format

BUL-.OUT)* to build initial data to base en%uiry.

1..2.1 CON8ERSIONLocal conversion routines may be written to manipulate e3tracted data.

For'&t* "ubroutine name

Subroutine name is the name of the Universe subroutine to be e3ecuted. )otethe re%uired space between N and the name. This is invo#ed from*).BUL-./(G* for each item the conversion is associated with.

The en%uiry system has its own common area I9EN0UIR#.COMMON which

must be inserted at the start of all conversion routines. This allows access to thevariables controllin$ the en%uiry processin$.

The followin$ variables are the most li#ely ones to be re%uired when writin$ aconversion routine&- +urrent id of the record bein$ processed.*+O- The current record bein$ processedO.-(T( The current incomin$ data bein$ processed. This is also the

returned data.!+ The current multi4value number bein$ processedS The current sub4value number

!1.+OU)T The ma3imum number of multi4values within the current recordS1.+OU)T The ma3imum number of sub4values within the current record



13/25


E%&'()e*The followin$ e3ample shows a routine, which displays either the actual maturitydate of an L-811 deal, or displays the number of days notice&

1..2.2 UIL".ROUTINE

( routine may be called prior to the selection phase of the en%uiry when runnin$the en%uiry. This routine should be used to manipulate the data prior to selection,

for instance it could be used to build a wor# file.

For'&t* Subroutine name

Subroutine name is the name of the Universe subroutine to be e3ecuted. 1orethan one routine may be specified. This is invo#ed from T.*)U5.S*L*+T andS.*)U5.S*L+TO). t uses one ar$ument 4 EN', -here EN' is a dynamicarray containin$ the entered selection criteria as follows&

EN'/0 )ame of en%uiryEN'1,20 Selection field names

EN'3,20 (ssociated OperandsEN'4,2,)0 -ata List

The data passed in EN' should be used within the subroutine to determine theaction to be ta#en. )o data is re%uired to be returned to the en%uiry system.

1..2.5 E$TERNAL LIN6 TO EN0UIRIES



14/25


The en%uiry system is not dependent on bein$ invo#ed by the selection screen*). t can be invo#ed from applications providin$ they are runnin$ underGLOBUS" usin$ the followin$ ar$ument synta3&

+(LL *)U5.-S/L(5 '''"

where ''' is a dynamic array with the format&'''/0 *n%uiry name #ey to 2.*)U5"'''1,20 Selection field names'''3,20 (ssociated selection operands'''4,2,)0(ssociated selection data'''5,60 1ulti valued list of sort re%uirements'''/70 -isplay mode t can be&

OUT/UT /rint in report format)ull -isplay to screen/ /rint of screen format

1..5 STAN"AR" SELECTION

The STANDARD.SELECTION application allows definition of local subroutines,which can be used as selection items in the *n%uiry system. These can be usedwithin en%uiry to perform selections of data not possible throu$h the e3istin$system. They can also be used to build virtual records containin$ data fromdifferent files; this can be achieved usin$ a )O2L* record type.

1..5.1 S#S.FIEL".NO &nd USR.FIEL".NOThese fields are used to hold the routine name when the associated S5S.T5/*

or US.T5/* is a type .

For'&t* Subroutine nameSubroutine name is the name of the subroutine to be e3ecuted. This is invo#edfrom +O)+(T.LST./O+*SSO

Ar:u'ents* RTN.LISTwhere RTN.LIST is a dynamic array containin$ the selected #eys to be returnedto the en%uiry system, separated by field mar#ers N21".

The main purpose of usin$ a routine at this point is to return a list of #eys for theen%uiry process to use. /ossible reasons for usin$ a routine may be, theselection re%uired mi$ht not be possible to enter directly in the en%uiry system;re%uire additional chec#s are re%uired; the selection may simply be too slow andre%uires an alternative access method.

Since the routine will need to use the common en%uiry variables, the insertI9EN0UIR#.COMMON should always be inserted at the top of the subroutine.The main variables li#ely to be re%uired are&



15/25


-.2*L-SPEQ +ontains a list of the Selection 2ield )ames-.LOG+(L.O/*()-SPEQ +ontains a list of the associated operands

entered in numeric form. The followin$ valuesare used&

@ *6 G LTC GTD )* L7H ULI L*J G*@? )@@

-.()G*.()-.!(LU*PE,5Q (ssociated entered values.

The routine must perform the re%uired processin$ to build the RTN.LIST. )otethat if this routine is bein$ used to 9pre4select: data ready for a further selectionwithin the en%uiry system, if no records are returned, the en%uiry system willattempt to select the whole file. This may have performance implications.

1..5.2 NOFILE St&nd&rd Se)ection Records

f the information that needs to be presented in an en%uiry does not e3ists in thesin$le file, then the en%uiry can be made to ta#e information form routines. To do

this first let us understand the way in which en%uiry subsystem wor#s.

The en%uiry subsystem first builds up list of -s, then pic#up each - andconstructs a record and then displays the records. f the information needs topresent does not e3ists in a file then subroutine can be written to do the tas#.Basically 6 routines needs to be written 4 One which will construct the list of -sand one which will accept the - and build the record based on -.f the field is specified in an en%uiry the type and position of the field is retrievedfrom the standard selection record of the file mentioned in the 2L*.)(1*.

Standard selection is an application that basically stores the dictionary for a file.5ou could have data fields and lo$ical fields i.e. the information is a calculatedvalue for e.$. from a subroutine". 0owever $enerally when you try to input astandard selection record it will validate if a 2L*.+O)TOL record e3ists for thefile. The only e3ception to this is if the SS record id be$ins with =)O2L*>. So forour above re%uirement we will need to create an SS record with - startin$ with=)O2L*>. n the record for the - field ma#e it an type field and attach aroutine that would build a dynamic array of ids that need to be displayed in theen%uiry.



16/25


R*)U5.+O11O), a common file that is used in en%uires defines avariable called O.-(T( which contains the - of the record that is currently $oin$to be displayed. (nother common variable called .*+O- a dynamic array"is used by the en%uiry subsystem to display the record. So you need to write a

routine that would use the id defined in O.-(T( and populate .*+O-.

Ste(1* ;rite t


17/25


* IF Y.OPERAND = 1 T#EN Y.I = Y.I = 1 Y.CUST.ID = Y.C#&.'ALUE


18/25


IF R.RECORD T#EN TOT = TOT R.RECORD


19/25


Ste(* Cre&te enuir, =it< t


20/25


The 1O-2+(TO) field allows a sub4routine to be called to manipulate thee3tracted data.

For'&t* N Subroutine name9nSubroutine name is the name of the Universe subroutine to be e3ecuted. 9n

denotes the ar$ument number in the call to the subroutine. The subroutine mustbe defined in PGM.FILE as a type routine, to$ether with the re%uired numberof parameters in field (--TO)(L.)2O as

./(33, ..33".

The actual name of the sub4routine must be defined in the PGM.FILE record inthe field B(T+0./O+*SS prefi3ed by a N. This is invo#ed from GS....pro$ram $enerated.t uses the ar$uments 4 Par/, Parn -here Parn may be anynumber of parameters at least one" as per the definition in PGM.FILE.

(ll details re%uired in the subroutine from the rep$en must be passed into the

subroutine as separate ar$uments. ( sin$le value may be returned.

1.. PRINTER.I"(llows definition of a command or routine" which can be used to create a file ofprinted output. This means that whenever GLOBUS output is directed to thisprinter id the command will be invo#ed.

1...1 COMMAN"(ny Uni!erse command or subroutine may be specified here. Usually a U)E catcommand will be used to build a file.

For'&t* Comman#Comman# may be any e3ecutable command from Universe. t is invo#ed from*E*+UT*.+O11()-.

The routine is driven from 2.0OL-.+O)TOL, and will be able to pass the id inthe command line. This can then be accessed within any re%uired routine usin$the system variable NS*)T*)+*.

2or e3ample, the command specified could be&

LO+(L./)T.LO(- 0OL-.+O)TOLQN-

The routine would then have to chec# NS*)T*)+*9 9,6,@ in order to e3tractthe -.



21/25


1. "ELI8ER# S#STEM1..1 IntroductionThe GLOBUS delivery system provides the ability for user defined routines formappin$ messa$es, control of disposition, processin$ SW2T interfaces, and for

formattin$ inward and outward Swift messa$es. The -elivery system has beenfurther opened up to enable users to define their own formattin$ rules formessa$es and to write interface routines, usin$ the Generic -elivery nterface.

1..2 "E.FORMAT.S;IFTThe DE.FORMAT.S:IFT application allows a subroutine to be called for aparticular Swift 2ield when processin$ incomin$ Swift messa$es

1..5 "E.;OR"SThis application allows a user routine to be defined for a $iven lan$ua$e to allowtranslation of numbers to words.

1.. "E."ISP.CONTROL( user4defined routine may be called to provide enhanced selection fordisposition control.

1.. "E.MAPPINGThe DE.MAPPING application allows a user subroutine to modify the informationpassed to (//L+(TO).0()-O22 by the callin$ application and hence to mapadditional data which is not normally available for the messa$e type.

1.. "E.CARRIER

The delivery carrier file, DE.CARRIE, contains details of all the carriersavailable in -elivery. To enable a carrier, it must be specified on the -elivery/arameter file, DE.PAR1.

The - of this file is the name of the carrier, as used in DE.PROD!CT. *achrecord contains the address type to be used for the carrier i.e. when accessin$DE.ADDRESS", the formattin$ rules ;DE.FORMAT.%arrier" and the carriermodule e.$. -*.O.++.SW2T". f the carrier module is G*)*+, i.e. themessa$es are handled by the $eneric pro$ram DE.CC.GENERI+, interface mustbe specified. The interface must reference a record on DE.INTERFAC*, whichcontains details of the protocol for all $eneric interfaces non4$eneric interfacedetails are stored on the parameter file, DE.PAR1".

When the record is authorised, formattin$ and carrier files are created if they donot already e3ist. These files are 2.-*.O.1SG.format4module and2.-*.O./.format4module for the formattin$ files and 2.-*.O.1SG.interface and2.-*..1SG.interface for the interface files.

1..B "E.INTERFACE



22/25


This file contains details of the protocols for all interfaces which use the Generic-elivery nterface. The protocols for interfaces written prior to the introduction ofthe Generic -elivery nterface are either stored on DE.PARM or are hard4codedin the pro$ram. Se%uence numbers for e3istin$ interfaces are stored on2.LO+7)G.

The id of the file is the interface as defined in the interface field on -*.+(*.There is little validation of the fields on DE.INTERFAC*. This is to allow forma3imum fle3ibility when new interfaces are written. *ach field can be used tocontrol how the interface is defined and used and more information can be foundin the 0elpte3t.

1.. "E.MESSAGE( routine can be defined to process inward messa$es to $enerate 2undsTransfers usin$ the O2S module.

1..D F".ACTI8IT#The 2iduciary application allows subroutines to be called to modify the contentsof data passed to delivery from the application.

1..1 MG.ACTI8IT#The mort$a$e application allows subroutines to be called to modify the contentsof data passed to delivery from the application.

1. INTERFACES - LOCAL CLEARING

1..1 IntroductionGLOBUS provides options for allowin$ the re%uired additional functionality to beadded to the 2unds Transfer module in order to allow local clearin$ transactionsto be entered accordin$ to the local rules. This functionality is provided by theparameter file FT.BC.PARAMETER for the local clearin$ transaction types, B+,B and B-. The parameter allows subroutines to be added to perform specificlocal validation, and update of cross4reference files and production ofadditional8new delivery messa$es.

( further option allows a sub4routine to be invo#ed from the delivery processin$,which can allow diversion of messa$es with different carriers into the localclearin$ system accordin$ to the coded rules.



23/25


1..2 FT.C.PARAMETERThis application allows customisation of e3istin$ field level validation for the B+2unds Transaction type. (dditionally subroutines may be defined to performspecific local validation within the 2T module in the followin$ fields&

2T.!(L-(TO).T) 2T.-*L!*5.T)

STO.!(L-(TO).T)

BUL7.STO.!(L-.T)

(dditionally the ability to define subroutines called from the C!STOMER andACCO!NT applications is provided in the fields&

(++OU)T.U/-.T)

+USTO1*.U/-.T)

( subroutine to allow diversion of messa$es into the local clearin$ system withinthe delivery system may be defined in&

-!*SO).T)

1..5 FT.TAPE.PARAMSThe FT.TAPE.PARAMS application mana$es import and e3port of data for thelocal clearin$ systems" installed. -ata is typically downloaded or uploaded ontotapes, or directly to a specified file. Subroutines and commands may be definedfor each type of interface which are used for&

LO(-.+1-

LO(-.OUT)*

U/-(T*.OUT)*

+*(T*.+1-

+*(T*.OUT)*

G*)*(T*.OUT)*

*)./UG*.OUT)*

1.. AC.ENTR#.PARAMTheAC.ENTR+.PARAM application controls the Generic (ccountin$ nterface. tcontains boo#in$ details of entries supplied in an e3ternal (S+ file, and thelayout of the file. The standard routine (+.)W(-.2L* should be used as theU/-(T* routine in FT.TAPES to run the $eneric interface. (dditional validation ispossible by callin$ user routines.



24/25


1.B LOCAL STATUTOR# REPORTING

1.B.1 IntroductionGLOBUS allows subroutines to be called at input time for the applications

F!NDS.TRANSFE. DATA.CAPT!R*, TELLER and DRA:INGS, which canvalidate and default local reference values used in local reportin$. Typically anactivity code will be allocated accordin$ to the type of contract entered.

1.B.2 AN6.RETURN.PARAMSThis application allows definition of subroutines to be called from the T*LL*,2U)-S.T()S2*, -(T(.+(/TU* and -(W)GS applications at inputtime to allow defaultin$ and validation of local reference items. The recordapplicable to the company is defined in LO+(L./O+*SS in the COMPAN+record.

1. TA6EO8ER 7 INSTALLATION CUSTOMISATION

1..1 Introductionn order to assist the ta#eover of e3istin$ systems when installin$ GLOBUS, thesystem allows lin#a$e of subroutines. Subroutines will usually be re%uired toperform processin$ which allows e3istin$ file structures to be mapped into theappropriate GLOBUS data files.

1..2 ALT.ACCT.PARAMETERThe application ALT.ACCT.PARAMETE, allows definition of the details of theaccount number structure in the e3istin$ system. The old account number is

stored in a cross4reference table lin#in$ it to the new GLOBUS account number,calledALTERNATE.ACCO!NT.

1..5 ES.AUTO.FUNCTIONThe system allows a subroutine to be inserted when buildin$ the input bufferwhen contents need to be calculated, and when maintainin$ totals for the recordsprocessed.

1.. TA6EO8ER.MAPPINGSubroutines may be defined in TA


25/25


1.D LIMITS

1.D.1 Introductionn order to allow comple3 calculations of ris# factors to be applied to limit

products or sub4products, the L1T.*2**)+* application allows definition ofa subroutine, which may be invo#ed. The subroutine will return the amount of a$iven transaction to be recorded in the limits system.

1.1 COMPAN# CUSTOMISATION

1.1.1 Introductionn order to allow for different account number structures and chec#di$itcalculations, the chec#di$it type may be defined as a user routine, which willperform the desired formattin$ and chec#di$it validation. This routine should alsoreturn the ne3t available id if called from the (++OU)T application with 2 or 26

entered at awaitin$ id. The routine is specified in the COMPAN+ record.

version routines and api.doc

Documents