Which OFS tool should I use for a complete response?

Use the OFS Response Parser when you have the complete returned message. Use the Error Decoder when you only have a short error code or fragment.

Can I paste production OFS messages into these tools?

Use synthetic or redacted data. Remove credentials, customer information, account identifiers, tokens, and other sensitive values before using any diagnostic tool or sharing output.

Does an OFS timeout mean the transaction failed?

No. A timeout means the caller did not receive a response in time. Prove whether the request arrived and whether posting committed before retrying.

Tools / OFS

Choose the right tool for your OFS problem.

Start with what you have: a request to build, an existing message to understand, a short error to decode, or a complete response to investigate. These browser-based tools do not connect to T24; use synthetic or redacted input.

Jump to the OFS message quick reference

Free web resource

OFS message quick reference

Keep this section open while you build or diagnose a message. It is deliberately concise and uses the same operation-specific ID terminology as the OFS article and tools. Exact syntax can vary by operation, interface, and release, so verify locally before using a message outside controlled testing.

Section	What it represents	Check first
`OPERATION`	Application or action, such as a transaction application or `ENQUIRY.SELECT`.	Correct application/action for the request type.
`OPTIONS`	Version, function, and processing mode such as PROCESS or VALIDATE.	Do not assume one option shape applies to every operation.
`USER`	Sign-on/security context used by the channel.	Use synthetic credentials in examples; check real access only in the approved environment.
`ID INFORMATION`	Operation-specific record key, transaction reference, enquiry context, or blank.	This is not a universal OFS.SOURCE field.
`DATA`	Fields, multi-values, sub-values, or enquiry criteria.	Field names, separators, multi-value positions, and required values.

Which OFS tool should I use?

I have...	Use...	Purpose
No request yet	OFS Generator	Build a synthetic request without hand-counting separators.
An existing request string	Message Parser	Break the request into its sections and fields.
A short error fragment	Error Decoder	Classify the likely failure stage and next evidence.
A complete response	Response Parser	Separate status, returned fields, errors, and overrides.

Five checks before retrying or escalating

Structure: verify the request parses into the expected operation, options, sign-on context, ID information, and data.
Security: distinguish authentication/authorisation failure from message-format failure.
Validation: where supported, use VALIDATE in an approved non-production test path before PROCESS.
Outcome: if the caller timed out, prove whether T24 committed before sending a retry.
Evidence: retain redacted timestamps, correlation/reference values, request stage, and response stage before changing state.

Need the full explanation? Read OFS in T24: message format, examples and how it works. This quick reference is public; no email address, pasted OFS content, or marketing consent is required.

What are you trying to do?

Integration tool

I need to build a new OFS request

Choose the application, operation, operation-specific ID information, and fields, then generate a structured request for controlled testing.

Build an OFS request

Debugging tool

I need to understand an existing request

Break a request into operation, options, user context, ID information, and data fields before changing or replaying it.

Parse an OFS request

Debugging tool

I have a short error code or message

Classify a compact OFS error fragment and review likely causes and the next evidence to collect.

Decode an OFS error

Debugging tool

I have a complete OFS response

Separate status, returned fields, errors, overrides, and practical next steps from a full response captured in a log or test.

Parse an OFS response

Recommended OFS troubleshooting flow

Preserve the original evidence. Capture timestamps, source, operation, record reference, request, and response before changing state.
Parse the request. Verify structure and fields before treating a later error as an application problem.
Parse or decode the response. Identify the earliest processing stage reached.
Trace the missing stage. Use application-server, TAFJ, service, database, and transport evidence only where the journey requires it.
Prove outcome before retry. A missing response can hide a committed transaction.

OFS guides and deeper troubleshooting

What is OFS in T24?

Understand the request structure, processing model, and where OFS fits in T24 integration.

Diagnose OFS response errors by processing stage

Separate transport, authentication, syntax, validation, posting, and response-delivery failures.

Trace a failed OFS request through TAFJ and JBoss

Follow one request across application-server, TAFJ runtime, service, database, and response evidence.

OFS vs API vs batch interfaces

Choose the right integration pattern and understand the operational trade-offs.

Frequently asked questions

Should I use the Error Decoder or Response Parser?

Use the Error Decoder for a short code or fragment. Use the Response Parser when you have the complete OFS response and need status, returned fields, overrides, and errors separated.

Are these tools connected to my T24 environment?

No. They are diagnostic and development aids. Validate results in an approved non-production environment and follow local change procedures.

Can I retry after a timeout?

Only after proving whether the original request committed. A timeout or missing response does not prove failure.