Imported from previous forum
[ original email was from Jason Vinton - jvinton@neonsoft.com ]
In the Mass Quote message, fields 435 and 436 are listed as UnderlyingContractMultiplier and UnderlyingCouponRate respectively. In the Field Definition section of the 4.2 specification, fields 435 and 436 are listed as UnderlyingCouponRate and UnderlyingContractMultiplier respectively. Since order is important within repeating groups, are the field names out of order, or are the field numbers out of order?
Thanks,
Jason S. Vinton
New Era of Networks
[ original email was from Jason Vinton - jvinton@neonsoft.com ]
> In the Mass Quote message, fields 435 and 436 are listed as UnderlyingContractMultiplier and UnderlyingCouponRate respectively. In the Field Definition section of the 4.2 specification, fields 435 and 436 are listed as UnderlyingCouponRate and UnderlyingContractMultiplier respectively. Since order is important within repeating groups, are the field names out of order, or are the field numbers out of order?
>
> Thanks,
> Jason S. Vinton
> New Era of Networks
>
The same problem exists in the Quote Acknowledgement, Security Definition Request and Security Definition messages.
Jason S. Vinton
New Era of Networks
The Field Reference should take precedence over a particular message definition section as to the tag number of the field. Thus UnderlyingCouponRate is tag 435 and UnderlyingContractMultiplier is tag 436. We will correct this in the next 4.2 Errata. Thanks.
> > In the Mass Quote message, fields 435 and 436 are listed as UnderlyingContractMultiplier and UnderlyingCouponRate respectively. In the Field Definition section of the 4.2 specification, fields 435 and 436 are listed as UnderlyingCouponRate and UnderlyingContractMultiplier respectively. Since order is important within repeating groups, are the field names out of order, or are the field numbers out of order?
> >
> > Thanks,
> > Jason S. Vinton
> > New Era of Networks
> >
>
> The same problem exists in the Quote Acknowledgement, Security Definition Request and Security Definition messages.
>
> Jason S. Vinton
> New Era of Networks
>
[ original email was from John Hardman - yiq12@dial.pipex.com ]
The previous reply confirmed that 435=UnderlyingCouponRate and 436=UnderlyingContractMultiplier. However, the question about whether the tags are in the correct order in the message definitions or whether the field names are in the correct order in the message definitions has not been answered. In each message where fields 435 and 436 occur should they be in the order 435 then 436, or 436 then 435 ?
> The Field Reference should take precedence over a particular message definition section as to the tag number of the field. Thus UnderlyingCouponRate is tag 435 and UnderlyingContractMultiplier is tag 436. We will correct this in the next 4.2 Errata. Thanks.
>
> > > In the Mass Quote message, fields 435 and 436 are listed as UnderlyingContractMultiplier and UnderlyingCouponRate respectively. In the Field Definition section of the 4.2 specification, fields 435 and 436 are listed as UnderlyingCouponRate and UnderlyingContractMultiplier respectively. Since order is important within repeating groups, are the field names out of order, or are the field numbers out of order?
> > >
> > > Thanks,
> > > Jason S. Vinton
> > > New Era of Networks
> > >
> >
> > The same problem exists in the Quote Acknowledgement, Security Definition Request and Security Definition messages.
> >
> > Jason S. Vinton
> > New Era of Networks
> >
>