T24 Ofs
T24 Ofs
T24 Ofs
21 September 2022
Contents
• Why OFS
• Features
• T24 OFS Architecture
• Request Types
Transaction request
Enquiry request
Subroutine request
• Modes of Processing
BATCH mode
ONLINE mode
GLOBUS mode
• OFS.POST.MESSAGE service
• OFS Applications
OFS.SOURCE
EB.PHANTOM
OFS.REQUEST.DETAIL
• OFS Message
Types
Syntax
Examples
21 September 2022
What is OFS
21 September 2022
Why OFS
21 September 2022
Features
21 September 2022
T24 OFS Architecture
21 September 2022
Request types
21 September 2022
Request types
Transaction requests
– To execute a T24 application or version
– Should contain all (mandatory) transaction related field data.
Enquiry requests
– To execute a T24 enquiry.
– Query the T24 database using built-in enquiries
– Should contain all possible actions for running a enquiry like
specifying selection conditons(s), operand(s), fields ..etc.
Subroutine requests
– To execute a subroutine in T24 environment
– OFS just calls the routine and by itself doesn't do any processing
– Used when multiple files have to updated.
21 September 2022
Modes of Processing
21 September 2022
OFS Batch mode
21 September 2022
OFS Online mode
21 September 2022
OFS Globus mode
21 September 2022
OFS.POST.MESSAGE service
OFS.GLOBUS.MANAGER
– should not be used within Online-Applications (e.g versions)
– should not be used in INPUT.ROUTINE, BEFORE.AUTH.RTN, AUTH.ROUTINE
levels from G15
– Fatal out with error “SENSITIVE ROUTINES CALLED IN LOCAL RTNS”
OFS.POST.MESSAGE
• Create a mainline routine and invoke OFS.POST.MESSAGE as follows
– CALL OFS.POST.MESSAGE(Y.OFS.MESSAGE,OFS.MSG.ID,OFS.SOURCE.ID,OPTIONS)
– SOURCE.TYPE of OFS.SOURCE used should be GLOBUS
• OFS message will get written on to a file named F.OFS.MESSAGE.QUEUE
• Run OFS.MESSAGE.SERVICE
– multi threaded service
– processes requests in F.OFS.MESSAGE.QUEUE
• Once the message is processed, the response is written to an out queue
named F.OFS.RESPONSE.QUEUE.
• OFS.RESPONSE.QUEUE – service to purge F.OFS.RESPONSE.QUEUE
21 September 2022
OFS Applications
• OFS.SOURCE
• OFS.REQUEST.DETAIL
– OFS.REQUEST.DETAILS referred to as ORD in T24 is used to
OFS to maintain an audit of OFS requests.
– Audit info is recorded per message
– To enable OFS audit the field MAINT.MSG.DETS in OFS.SOURCE
record needs to be se to "Y".
• EB.PHANTOM record
– EB.PHANTOM control phantom & interactive jobs.
– Processing done by the routine set in the RUN.ROUTINE field
– OFS.QUEUE.MANAGER - standard T24 routine specified in
RUN.ROUTINE field for BATCH mode.
21 September 2022
OFS.SOURCE record
SOURCE.TYPE Defines whether you will be using this OFS.SURCE record for For BATCH: select BATCH
BATCH or TELNET processing.
LOGIN.ID Specifies the Unix or NT login that will automatically initiate the For BATCH: leave blank.
communication with the external source.
EB.PHANT.ID Specifies the EB.PHANTOM record to be used for processing For BATCH processing, select the
batch jobs. EB.PHANTOM record to be used.
MAX.CONNECTIONS Specifies the maximum number of OFS connections for the Number must be less than the maximum
specified service, which can be active at any one time. number of users defined in the SPF
record,
21 September 2022
OFS.SOURCE record
LOG.FILE.DIR Defines the name of the directory used to store the log files Either refer to an existing pre-defined
created when running OFS. directory, otherwise the directory will be
created at authorisation.
LOG.DETAIL.LEVEL Specifies the type of OFS message logging to be performed by Can select as much or as little logging as
OFS. required – does not affect OFS
processing.
IN.QUEUE.DIR For batch processing, the directory where batches will be placed OFS Batch processing: Enter name of
for processing. directory to be used for batch
processing.
SYNTAX.TYPE Specifies the syntax type of the messages. For Batch processing may be either GTS or
OFS.
GENERIC.USER The generic user is the T24 user that will be used to access the Must be a valid record on the USER file and
T24 server. For external users it determines the SMS have the authority to use
options. Generic user must have the authority to use EB.PHANTOM.PH
EB.PHANTOM.PH
IB.USER.CHECK Specifies whether transactions supplied to T24 using this service For batch processing leave null
require the sign on name and password to be validated for
the external user.
21 September 2022
OFS.SOURCE record(samples)
21 September 2022
EB.PHANTHOM record(sample)
21 September 2022
OFS.REQUEST.DETAIL sample
21 September 2022
Message Types and syntax
21 September 2022
OFS Message Structure
Options
User information
21 September 2022
OFS Message Structure
• Transaction ID
• Message Data
• Field Data
21 September 2022
Message Data -Returned
Transaction ID Returned
21 September 2022
Enquiry Request & Response
• Enquiry Request
• Message Data
• Enquiry Response
21 September 2022
Subroutine Request & Response
• Subroutine Request
• Subroutine Response
21 September 2022
OFS message examples
Sample 1
– SECTOR,/I/PROCESS,MALAR01/123456,7719,DESCRIPTION::=OFS
DESCRIPTION DATA,SHORT.NAME::=OFS DATA
– 7719/TST0036400015/1,DESCRIPTION:1:1=OFS DESCRIPTION
DATA,SHORT.NAME:1:1=OFS
DATA,RECORD.STATUS:1:1=INAU,CURR.NO:1:1=1,INPUTTER:1:1=14
2_MALAR.1___OFS_TELNET,DATE.TIME:1:1=0711161601,CO.CODE:1
:1=US0010001,DEPT.CODE:1:1=1
21 September 2022
THANK
YOU
21 September 2022