PegSecurityID (FIX tag 1097)

StringFIX 5.0 SP2

PegSecurityID (tag 1097) is a String field defined in FIX 5.0 SP2. It appears in 8 message types, always optionally.

At a glance

Tag
1097
Name
PegSecurityID
Datatype
String
Dialects
FIX 5.0 SP2
Messages
8

What the specification says

Defines the identity of the security off whose prices the order will peg.

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

A real message using tag 1097

NewOrderSingle · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength124
35MsgTypeDNewOrderSingle
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
1097PegSecurityIDEXAMPLE
10CheckSum093
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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1097 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
CrossOrderCancelReplaceRequesttOptionalinside the PegInstructions component
ExecutionReport8Optionalinside the PegInstructions component
MultilegOrderCancelReplaceACOptionalinside the PegInstructions component
NewOrderCrosssOptionalinside the PegInstructions component
NewOrderListEOptionalinside ListOrdGrp › PegInstructions
NewOrderMultilegABOptionalinside the PegInstructions component
NewOrderSingleDOptionalinside the PegInstructions component
OrderCancelReplaceRequestGOptionalinside the PegInstructions component

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 1097 in TypeScript

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

Other String 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-fix50sp2