LegCoveredOrUncovered (FIX tag 565)

intFIX 4.4

LegCoveredOrUncovered (tag 565) is an int field defined in FIX 4.4. It appears in 5 message types, always optionally.

At a glance

Tag
565
Name
LegCoveredOrUncovered
Datatype
int
Dialects
FIX 4.4
Messages
5

What the specification says

CoveredOrUncovered for leg of a multileg See CoveredOrUncovered (203) field for description

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 565

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength175
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
54Side1Buy
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
555NoLegs2 entries2repeating group
600LegSymbolEXAMPLE
565LegCoveredOrUncovered1
600LegSymbolEXAMPLE
565LegCoveredOrUncovered1
10CheckSum012
Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 565 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

MessageMsgTypeRequirednessWhere in the message
ExecutionReport8Optionalinside the InstrmtLegExecGrp component
MultilegOrderCancelReplaceACOptionalinside the LegOrdGrp component
NewOrderMultilegABOptionalinside the LegOrdGrp component
TradeCaptureReportAEOptionalinside the TrdInstrmtLegGrp component
TradeCaptureReportAckAROptionalinside the TrdInstrmtLegGrp component

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 565 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[565];field?.name;   // "LegCoveredOrUncovered"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other int fields

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44