FIX TAG 935
NetworkRequestType
Definition
Indicates the type and level of details required for a Network Status Request Message Boolean logic applies EG If you want to subscribe for changes to certain id's then UserRequestType =0 (8+2), Snapshot for certain ID's = 9 (8+1)
Compare versions
Differences between the selected source snapshots, including wording and errata; not a migration guide.
FIX 4.4 FIX 5.0 SP2
Definition text changed
FIX 4.4
Indicates the type and level of details required for a Network Status Request Message Boolean logic applies EG If you want to subscribe for changes to certain id’s then UserRequestType =0 (8+2), Snapshot for certain ID’s = 9 (8+)
FIX 5.0 SP2
Indicates the type and level of details required for a Network Status Request Message Boolean logic applies EG If you want to subscribe for changes to certain id's then UserRequestType =0 (8+2), Snapshot for certain ID's = 9 (8+1)
Value text or deprecation changed 2
| Value | FIX 4.4 | FIX 5.0 SP2 |
|---|---|---|
4 | Stop subscribing | Stop Subscribing |
8 | Level of detail, then NoCompID’s becomes required | Level of Detail, then NoCompID's becomes required |
Values 4
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.
35=BCNetworkCounterpartySystemStatusRequestMessage body