Skip to content
FIXtags

FIX TAG 373

SessionRejectReason

intAdded FIX.4.2

Definition

Code to identify reason for a session-level Reject message

Compare versions

Differences between the selected source snapshots, including wording and errata; not a migration guide.

FIX 4.2 FIX 4.4

Definition text changed

FIX 4.2

Code to identify reason for a session-level Reject message.

FIX 4.4

Code to identify reason for a session-level Reject message

Values only in FIX 4.4 7

  • 12XML Validation error
  • 13Tag appears more than once
  • 14Tag specified out of required order
  • 15Repeating group fields out of order
  • 16Incorrect NumInGroup count for repeating group
  • 17Non "data" value includes field delimiter (SOH character)
  • 99Other

Values 19

ValueMeaning
0

Invalid tag number

1

Required tag missing

2

Tag not defined for this message type

3

Undefined Tag

4

Tag specified without a value

5

Value is incorrect (out of range) for this tag

6

Incorrect data format for value

7

Decryption problem

8

Signature problem

9

CompID problem

10

SendingTime accuracy problem

11

Invalid MsgType

12

XML Validation error

13

Tag appears more than once

14

Tag specified out of required order

15

Repeating group fields out of order

16

Incorrect NumInGroup count for repeating group

17

Non "data" value includes field delimiter (SOH character)

99

Other

About the int data type

Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23"). Examples: 723 in field 21 would be mapped int as |21=723|. -723 in field 12 would be mapped int as |12=-723| The following data types are based on int.

Used in messages 1

Includes nested components and repeating groups. Open a location to see its surrounding requirements.