UnderlyingPutOrCall (FIX tag 315)

intFIX 4.4FIX 4.2

UnderlyingPutOrCall (tag 315) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 59 message types, always optionally.

At a glance

Tag
315
Name
UnderlyingPutOrCall
Datatype
int
Dialects
FIX 4.4 and FIX 4.2
Messages
59

What the specification says

Underlying security’s PutOrCall. See PutOrCall field for description

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

A real message using tag 315

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength153
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
711NoUnderlyings2 entries2repeating group
311UnderlyingSymbolEXAMPLE
315UnderlyingPutOrCall1
311UnderlyingSymbolEXAMPLE
315UnderlyingPutOrCall1
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum205
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 315 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.

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
Advertisement7Optionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationInstructionJOptionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationReportASOptionalinside UndInstrmtGrp › UnderlyingInstrument
AssignmentReportAWOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralAssignmentAYOptionalinside UndInstrmtCollGrp › UnderlyingInstrument
CollateralInquiryBBOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralInquiryAckBGOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralReportBAOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralRequestAXOptionalinside UndInstrmtCollGrp › UnderlyingInstrument
CollateralResponseAZOptionalinside UndInstrmtCollGrp › UnderlyingInstrument
ConfirmationAKOptionalinside UndInstrmtGrp › UnderlyingInstrument
CrossOrderCancelReplaceRequesttOptionalinside UndInstrmtGrp › UnderlyingInstrument
CrossOrderCancelRequestuOptionalinside UndInstrmtGrp › UnderlyingInstrument
DerivativeSecurityListAAOptionalinside the UnderlyingInstrument component
DerivativeSecurityListRequestzOptionalinside the UnderlyingInstrument component
DontKnowTradeQOptionalinside UndInstrmtGrp › UnderlyingInstrument
EmailCOptionalinside UndInstrmtGrp › UnderlyingInstrument
ExecutionReport8Optionalinside UndInstrmtGrp › UnderlyingInstrument
IOI6Optionalinside UndInstrmtGrp › UnderlyingInstrument
ListStrikePricemOptionalinside UndInstrmtStrkPxGrp › UnderlyingInstrument
MarketDataIncrementalRefreshXOptionalinside MDIncGrp › UndInstrmtGrp › UnderlyingInstrument
MarketDataRequestVOptionalinside InstrmtMDReqGrp › UndInstrmtGrp › UnderlyingInstrument
MarketDataSnapshotFullRefreshWOptionalinside UndInstrmtGrp › UnderlyingInstrument
MassQuoteiOptionalOptionalinside QuotSetGrp › UnderlyingInstrument
MassQuoteAcknowledgementbOptionalOptionalinside QuotSetAckGrp › UnderlyingInstrument
MultilegOrderCancelReplaceACOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderCrosssOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderListEOptionalinside ListOrdGrp › UndInstrmtGrp › UnderlyingInstrument
NewOrderMultilegABOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderSingleDOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewsBOptionalinside UndInstrmtGrp › UnderlyingInstrument
OrderCancelReplaceRequestGOptionalinside UndInstrmtGrp › UnderlyingInstrument
OrderCancelRequestFOptionalinside UndInstrmtGrp › UnderlyingInstrument
OrderMassCancelReportrOptionalinside the UnderlyingInstrument component
OrderMassCancelRequestqOptionalinside the UnderlyingInstrument component
OrderMassStatusRequestAFOptionalinside the UnderlyingInstrument component
OrderStatusRequestHOptionalinside UndInstrmtGrp › UnderlyingInstrument
PositionMaintenanceReportAMOptionalinside UndInstrmtGrp › UnderlyingInstrument
PositionMaintenanceRequestALOptionalinside UndInstrmtGrp › UnderlyingInstrument
PositionReportAPOptionalinside PosUndInstrmtGrp › UnderlyingInstrument
QuoteSOptionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteCancelZOptionalinside QuotCxlEntriesGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteRequestROptionalinside QuotReqGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteResponseAJOptionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteStatusReportAIOptionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteStatusRequestaOptionalinside UndInstrmtGrp › UnderlyingInstrument
RFQRequestAHOptionalinside RFQReqGrp › UndInstrmtGrp › UnderlyingInstrument
RequestForPositionsANOptionalinside UndInstrmtGrp › UnderlyingInstrument
RequestForPositionsAckAOOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitiondOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitionRequestcOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityListyOptionalinside SecListGrp › UndInstrmtGrp › UnderlyingInstrument
SecurityListRequestxOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityStatusfOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityStatusRequesteOptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportAEOptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportRequestADOptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportRequestAckAQOptionalinside UndInstrmtGrp › UnderlyingInstrument

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 315 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[315];field?.name;   // "UnderlyingPutOrCall"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