Scribd
Upload
14 views1 page

OFS Subroutines and Connection Management

The document outlines key functionalities of OFS, including the requirement for subroutines to handle incoming and outgoing parameters. It discusses the impact of open OFS connections on licensing and the queuing of requests in the OFS.MESSAGE.QUEUE. Additionally, it explains the use of GLOBUS mode for updating concat files and the types of routines involved in processing messages.

Uploaded by

Krishna Tejap6
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
14 views1 page

OFS Subroutines and Connection Management

The document outlines key functionalities of OFS, including the requirement for subroutines to handle incoming and outgoing parameters. It discusses the impact of open OFS connections on licensing and the queuing of requests in the OFS.MESSAGE.QUEUE. Additionally, it explains the use of GLOBUS mode for updating concat files and the types of routines involved in processing messages.

Uploaded by

Krishna Tejap6
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd

Day 8: OFS -

SLIDE6:
Subroutines must take an incoming parameter and an outgoing parameter

SLIDE8:
Batch Mode used for processing files (example –recovery)

SLIDE10:
The number of open OFS connections impact the number of licences bought (if not
unlimited)

Each connection processes one request at a time. Other requests queue up in the
[Link].

Every request has a corresponding response.

SLIDE11:
To update concat files then use GLOBUS mode. But it has a delay associated with it.
Eg BP processing.
Globus mode is two way – post a transaction and forget about it – OFS Message
queue
Or you need a feedback for that transaction – OFS [Link]
OFS will never update concat files – this has to be done explicitly through routines –
thus using [Link].

In [Link], eg ALLIANCE record, the [Link] = Session. This is for


browser.

SLIDE13;
Initial Routine – for eg when the request is started to stop/start services
Close routine - for eg kickoff a service
In Msg Rtn – get executed before message gets to T24
Out Msg Rtn – get executed after message returns from OFS.

Two types of OFS - process or validate

You might also like