|
4.1 Changes
< Previous Next >
Re: Length of ClOrdID - tag 11 - URGENT?
Hari R / Covansys <>
24 May 2005 9:26PM ETIs this length based on FIX version. Did it have any limitations for FIX 4.1 and that now it has been relaxed?
In FIX 4.1 it says Clorid as char but in 4.2 it is a string. Initially we had created a mapping based on our customers requirement, which was 12 characters. We had it as 16. Now we get 20 as the length. We need to change this but if we know what the maximum size we could have that as final instead of changing every now and then.
Regards.
Hari.
> > Daniel, You are right on that FIX does not put any limitation on the
> > size. Altough it is wise to point out that FIX _implementations_ (I
> > mean FIX egnines) may have limitations coming from a lousy
> > implementation. (Such as using C strings, with hardcoded size...)
> >
> > I am using 17 chars long ClOrdIDs with no problems.
> >
> > -gabor
>
> Our current systems are limited to a maximum of 40 characters for
> ClOrdIDs. We definitely have several customers who use more than 17
> characters.
>
> Most FIX engines or applications have hardcoded limitations on the size
> of many string fields such as ClOrdIDs, ExecIDs, CompIDs etc,. The ones
> that have the bigger size limits are putting less constraints upon their
> users/customers. Implementors, please be generous.
>
> We even have one customer who forces us to use an 8 character ExecID
> which is a fairly unpleasant restriction and has caused us to create
> more software specifically to handle mapping from/to our longer ExecIDs
> to live with this restriction.
>
> JohnP
Re: Length of ClOrdID - tag 11 - URGENT?
Hari R / Covansys 24 May 2005 9:26PM ET
|
