quickfix-developers — QuickFIX developers forum

Re: [Quickfix-developers] Config files

[Caleb E. <cal...@gm...>]

On 10/6/05, Shankar Krishnan <skr...@jw...> wrote:
>
>  For the session to start, I need to know the counterparty's IP address
> and the port he wants me to connect to. Where do these entries go ? It
> seems I should add them to my config file, but I have not seen an relevan=
t
> tag for these entries, what tags should I use.
>

These are not tags. They are entries in the configuration file. See:

http://quickfixengine.org/quickfix/doc/html/configuration.html

Specifially SocketConnectHost and SocketConnectPort.


--
Caleb Epstein
caleb dot epstein at gmail dot com

[Quickfix-developers] Config files

[Shankar K. <skr...@jw...>]

 

 

Very basic question:

 

For the session to start, I need to know the counterparty's IP address and
the port he wants me to connect to.

Where do these entries go ? It seems I should add them to my config file,
but I have not seen an relevant tags

For these entries, what tags should I use.

 

In the FIX session - is the Logon method - doing the connection to the IP
address and Port ?

 

Thanks for any help.

 

-

S



 

RE: [Quickfix-developers] Fix Sessions

[Shankar K. <skr...@jw...>]

 

Thanks Dale.

 

  _____  

From: Dale Wilson [mailto:wil...@oc...] 
Sent: Thursday, October 06, 2005 11:09 AM
To: Shankar Krishnan
Cc: qui...@li...
Subject: Re: [Quickfix-developers] Fix Sessions

 

Hi Shankar,

Shankar Krishnan wrote: 

 

A FIX session consists of  logon/message exchange/logout. 

Some terminology we use here at OCI to help keep things straight:
   A trading day at the exchange is called a Session. (For some exchanges
trading Sessions last a week or other time period.)
   A logon/.../logout interval is called a connection (I'm not sure this
term is formalized by the FIX standard)
   A QuickFIX SessionID represents an agreement between counterparties to
allow connections to sessions.  It consists of protocol version, sending
computer ID and receiving computer ID all of which must be agreed upon
beforehand.  This agreement and therefore the SessionID is valid for many
trading sessions.




Document mentions that a single FIX session can exist

Across multiple physical connections, what does this mean ? Thanks for any
help understanding this.

That means an application can connect (logon...logout) multiple times using
the same SessionID during a given trading Session.
These connections are sequential, not parallel -- only one connection can be
active per SessionID at any particular time.

Things that are there to confuse you include:

  The layer of the protocol that handles logon,logout,retransmit, etc. is
sometimes called the Session layer in the standards document.   We don't use
that terminology.  We call it the Administrative layer of the protocol.

  The FIX::Session object (defined within QuickFIX)  lives for the lifetime
of your application.  It is identified by a SessionID.  The application can
use the same FIX::Session object to connect (logon/logout)  multiple times
sequentially during the life of the application.  Thus the FIX::Session
object corresponds very well (but not completely) to the exchange's Trading
Session.

HTH,

Dale





 

 






-- 
-----------------------------------------------------
  Dale Wilson, Senior Software Engineer      
  Object Computing, Inc. (OCI)
  http://www.ociweb.com/ <http://www.ociweb.com/>
http://www.theaceorb.com/ <http://www.theaceorb.com/> 
----------------------------------------------------

Re: [Quickfix-developers] Fix Sessions

[Dale W. <wil...@oc...>]

Hi Shankar,

Shankar Krishnan wrote:

>  
>
> A FIX session consists of  logon/message exchange/logout.
>
Some terminology we use here at OCI to help keep things straight:
   A trading day at the exchange is called a Session. (For some 
exchanges trading Sessions last a week or other time period.)
   A logon/.../logout interval is called a connection (I'm not sure this 
term is formalized by the FIX standard)
   A QuickFIX SessionID represents an agreement between counterparties 
to allow connections to sessions.  It consists of protocol version, 
sending computer ID and receiving computer ID all of which must be 
agreed upon beforehand.  This agreement and therefore the SessionID is 
valid for many trading sessions.

> Document mentions that a single FIX session can exist
>
> Across multiple physical connections, what does this mean ? Thanks for 
> any help understanding this.
>
That means an application can connect (logon...logout) multiple times 
using the same SessionID during a given trading Session.
These connections are sequential, not parallel -- only one connection 
can be active per SessionID at any particular time.

Things that are there to confuse you include:

  The layer of the protocol that handles logon,logout,retransmit, etc. 
is sometimes called the Session layer in the standards document.   We 
don't use that terminology.  We call it the Administrative layer of the 
protocol.

  The FIX::Session object (defined within QuickFIX)  lives for the 
lifetime of your application.  It is identified by a SessionID.  The 
application can use the same FIX::Session object to connect 
(logon/logout)  multiple times sequentially during the life of the 
application.  Thus the FIX::Session object corresponds very well (but 
not completely) to the exchange's Trading Session.

HTH,

Dale


>  
>
>  
>


-- 
-----------------------------------------------------
  Dale Wilson, Senior Software Engineer      
  Object Computing, Inc. (OCI)
  http://www.ociweb.com/  http://www.theaceorb.com/
----------------------------------------------------

[Quickfix-developers] QFJ: Acceptors and SessionQualifiers

[Shepheard, T. (London) <Tob...@ml...>]

NB:  This is using QuickFIX/J (1.0.0-beta1) with a minor fix from CVS
for FileLog.java

I came across a problem when running as an Acceptor with the JDBC
message store (JDBCStore.java), and the fact that the SessionQualifier
is null for Acceptors, but is required in the database tables. See
http://www.quickfixengine.org/bugtracker/bug.php?op=3Dshow&bugid=3D115

Am I missing something here or is this a problem with QFJ - and are
SessionQualifiers really needed? From what I can see they look like
they're meant to be optional for initiators, and meaningless for
acceptors, but I'm not at all sure.

As far as I can see I've got two options - either add a session
qualifier to the acceptor config, or alter the DB and JDBCStore code to
not require a session qualifier (which has a rather large impact due to
the primary key changes that would entail). I hope someone can advise!

Many thanks,
Toby
--------------------------------------------------------

If you are not an intended recipient of this e-mail, please notify the =
sender, delete it and do not read, act upon, print, disclose, copy, =
retain or redistribute it. Click here for important additional terms =
relating to this e-mail.     http://www.ml.com/email_terms/
--------------------------------------------------------

[Quickfix-developers] Fix Dictionaries

[Shankar K. <skr...@jw...>]

 

Hi,

 

Since additional tags have been added in each version, should I reference
the Dictionary I am using in the application.

Is this needed ?

 

Thanks

 

 

  _____  

From: Shankar Krishnan 
Sent: Thursday, October 06, 2005 9:53 AM
To: Shankar Krishnan
Cc: qui...@li...
Subject: RE: [Quickfix-developers] SendercompID and targetCompID

 

 

Thanks, I misread, in fact heartbeats are sent only in periods of
inactivity.

 

  _____  

From: Caleb Epstein [mailto:cal...@gm...] 
Sent: Wednesday, October 05, 2005 4:37 PM
To: Shankar Krishnan
Cc: qui...@li...
Subject: Re: [Quickfix-developers] SendercompID and targetCompID

 

 

On 10/5/05, Shankar Krishnan <skr...@jw... <mailto:skr...@jw...> >
wrote:

QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
<http://www.quickfixengine.org/quickfix/doc/html/index.html> 
QuickFIX Support: http://www.quickfixengine.org/services.html
<http://www.quickfixengine.org/services.html> 



Hi,

Just to be sure (since I donot have the broker connection enabled yet),
The SenderCompId and TargetCompId, can be IP addresses right ?


In pure FIX terms, they can be anything, but when you setup a connection
with a broker, they will generally assign you IDs to use. 

 

I am planning to use the 'Heartbeat messages', Would you normally use these
Messages and show this as a status In the client application.


Show what status?  FYI, Heartbeat messages are only sent when the connection
has been idle for some amount of time.  If you have a connection that is
busy all day with order- or quote-flow, no heartbeats will be sent.


-- 
Caleb Epstein
caleb dot epstein at gmail dot com 

[Quickfix-developers] Fix Sessions

[Shankar K. <skr...@jw...>]

 

A FIX session consists of  logon/message exchange/logout. Document mentions
that a single FIX session can exist

Across multiple physical connections, what does this mean ? Thanks for any
help understanding this.

 

 

RE: [Quickfix-developers] SendercompID and targetCompID

[Shankar K. <skr...@jw...>]

 

Thanks, I misread, in fact heartbeats are sent only in periods of
inactivity.

 

  _____  

From: Caleb Epstein [mailto:cal...@gm...] 
Sent: Wednesday, October 05, 2005 4:37 PM
To: Shankar Krishnan
Cc: qui...@li...
Subject: Re: [Quickfix-developers] SendercompID and targetCompID

 

 

On 10/5/05, Shankar Krishnan <skr...@jw... <mailto:skr...@jw...> >
wrote:

QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
<http://www.quickfixengine.org/quickfix/doc/html/index.html> 
QuickFIX Support: http://www.quickfixengine.org/services.html
<http://www.quickfixengine.org/services.html> 



Hi,

Just to be sure (since I donot have the broker connection enabled yet),
The SenderCompId and TargetCompId, can be IP addresses right ?


In pure FIX terms, they can be anything, but when you setup a connection
with a broker, they will generally assign you IDs to use. 

 

I am planning to use the 'Heartbeat messages', Would you normally use these
Messages and show this as a status In the client application.


Show what status?  FYI, Heartbeat messages are only sent when the connection
has been idle for some amount of time.  If you have a connection that is
busy all day with order- or quote-flow, no heartbeats will be sent.


-- 
Caleb Epstein
caleb dot epstein at gmail dot com 

Re: [Quickfix-developers] SendercompID and targetCompID

[Caleb E. <cal...@gm...>]

On 10/5/05, Shankar Krishnan <skr...@jw...> wrote:
>
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
>
> Hi,
>
> Just to be sure (since I donot have the broker connection enabled yet),
> The SenderCompId and TargetCompId, can be IP addresses right ?


In pure FIX terms, they can be anything, but when you setup a connection
with a broker, they will generally assign you IDs to use.

I am planning to use the 'Heartbeat messages', Would you normally use these
> Messages and show this as a status In the client application.


Show what status? FYI, Heartbeat messages are only sent when the connection
has been idle for some amount of time. If you have a connection that is bus=
y
all day with order- or quote-flow, no heartbeats will be sent.

--
Caleb Epstein
caleb dot epstein at gmail dot com

[Quickfix-developers] SendercompID and targetCompID

[Shankar K. <skr...@jw...>]

Hi,

Just to be sure (since I donot have the broker connection enabled yet), 
The SenderCompId and TargetCompId, can be IP addresses right ?

I am planning to use the 'Heartbeat messages', Would you normally use these
Messages and show this as a status In the client application.

Thanks
Shankar


-----Original Message-----
From: Oren Miller [mailto:or...@qu...] 
Sent: Wednesday, October 05, 2005 10:37 AM
To: Caleb Epstein
Cc: Shankar Krishnan; qui...@li...
Subject: Re: [Quickfix-developers] Order Types/ FIX Codes

A convenient solution for most systems, if you don't want to put a  
lot of effort into it, is to use the value of the MsgSeqNum.  If you  
are worried about sequence resets, pair it with a time value.

--oren

On Oct 5, 2005, at 9:25 AM, Caleb Epstein wrote:

> On 10/5/05, Shankar Krishnan <skr...@jw...> wrote:
> What is the normal method used to generate ClOrdID, is using the  
> random number gen valid or should I use something
> More robust.
>
> Most exchanges and sell-side systems expect every ClOrdID to be  
> unique for a given session and will reject or ignore duplicates.   
> Using a random number generator isn't a very good idea unless you  
> can be sure it doesn't repeat.  Most systems use either a simple  
> increasing sequence number or something like the NYSE DOT system's  
> branch code + sequence number convention (AAA 0001, AAA 0002, ...  
> ZZZ 9999).
>
> -- 
> Caleb Epstein
> caleb dot epstein at gmail dot com

RE: [Quickfix-developers] Order Types/ FIX Codes

[Jo J. <jo...@tr...>]

The system I use is a combination of date and sequence number generated
by my database. i.e. 20051004-0000001

I feel like this is a pretty good guarantee of uniqueness, and I can
reset the sequence in the DB each night. The only trick is to make sure
the id isn't too long for your broker/exchange's system to handle.

Jo Janssens
Telluride Asset Management
952.653.6456


-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Oren Miller
Sent: Wednesday, October 05, 2005 09:37
To: Caleb Epstein
Cc: Shankar Krishnan; qui...@li...
Subject: Re: [Quickfix-developers] Order Types/ FIX Codes

QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

A convenient solution for most systems, if you don't want to put a  
lot of effort into it, is to use the value of the MsgSeqNum.  If you  
are worried about sequence resets, pair it with a time value.

--oren

On Oct 5, 2005, at 9:25 AM, Caleb Epstein wrote:

> On 10/5/05, Shankar Krishnan <skr...@jw...> wrote:
> What is the normal method used to generate ClOrdID, is using the  
> random number gen valid or should I use something
> More robust.
>
> Most exchanges and sell-side systems expect every ClOrdID to be  
> unique for a given session and will reject or ignore duplicates.   
> Using a random number generator isn't a very good idea unless you  
> can be sure it doesn't repeat.  Most systems use either a simple  
> increasing sequence number or something like the NYSE DOT system's  
> branch code + sequence number convention (AAA 0001, AAA 0002, ...  
> ZZZ 9999).
>
> -- 
> Caleb Epstein
> caleb dot epstein at gmail dot com



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,
discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

Re: [Quickfix-developers] Order Types/ FIX Codes

[Oren M. <or...@qu...>]

A convenient solution for most systems, if you don't want to put a  
lot of effort into it, is to use the value of the MsgSeqNum.  If you  
are worried about sequence resets, pair it with a time value.

--oren

On Oct 5, 2005, at 9:25 AM, Caleb Epstein wrote:

> On 10/5/05, Shankar Krishnan <skr...@jw...> wrote:
> What is the normal method used to generate ClOrdID, is using the  
> random number gen valid or should I use something
> More robust.
>
> Most exchanges and sell-side systems expect every ClOrdID to be  
> unique for a given session and will reject or ignore duplicates.   
> Using a random number generator isn't a very good idea unless you  
> can be sure it doesn't repeat.  Most systems use either a simple  
> increasing sequence number or something like the NYSE DOT system's  
> branch code + sequence number convention (AAA 0001, AAA 0002, ...  
> ZZZ 9999).
>
> -- 
> Caleb Epstein
> caleb dot epstein at gmail dot com

Re: [Quickfix-developers] Order Types/ FIX Codes

[Caleb E. <cal...@gm...>]

On 10/5/05, Shankar Krishnan <skr...@jw...> wrote:
>
>  What is the normal method used to generate ClOrdID, is using the random
> number gen valid or should I use something
> More robust.
>
Most exchanges and sell-side systems expect every ClOrdID to be unique for =
a
given session and will reject or ignore duplicates. Using a random number
generator isn't a very good idea unless you can be sure it doesn't repeat.
Most systems use either a simple increasing sequence number or something
like the NYSE DOT system's branch code + sequence number convention (AAA
0001, AAA 0002, ... ZZZ 9999).

--
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] Order Types/ FIX Codes

[Rich H. <rh...@ql...>]

Usually it depends on the exchange you are connected to.

Cheers,
Rich


Shankar Krishnan wrote:

>  
>
> Thanks,
>
>  
>
> What is the normal method used to generate ClOrdID, is using the 
> random number gen valid or should I use something
>
> More robust.
>
>  
>
> Thanks
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* Fanshteyn, Timur [mailto:tfa...@bo...]
> *Sent:* Wednesday, October 05, 2005 9:17 AM
> *To:* Shankar Krishnan; qui...@li...
> *Subject:* RE: [Quickfix-developers] Order Types/ FIX Codes
>
>  
>
> check out http://www.fixprotocol.org
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* qui...@li... 
> [mailto:qui...@li...] *On Behalf Of 
> *Shankar Krishnan
> *Sent:* Wednesday, October 05, 2005 8:59 AM
> *To:* qui...@li...
> *Subject:* [Quickfix-developers] Order Types/ FIX Codes
>
>  
>
> Hi,
>
>  
>
> I am working on a front end for a simple stock and futures trading 
> application. Where can I find a doc
>
> On various order types and the associated codes for these.  Are these 
> part of the "ROE" that my execution
>
> Broker would give me.
>
>  
>
> Regards
>
>  
>

RE: [Quickfix-developers] Order Types/ FIX Codes

[Shankar K. <skr...@jw...>]

 

Thanks, 

 

What is the normal method used to generate ClOrdID, is using the random
number gen valid or should I use something

More robust.

 

Thanks

 

  _____  

From: Fanshteyn, Timur [mailto:tfa...@bo...] 
Sent: Wednesday, October 05, 2005 9:17 AM
To: Shankar Krishnan; qui...@li...
Subject: RE: [Quickfix-developers] Order Types/ FIX Codes

 

check out http://www.fixprotocol.org <http://www.fixprotocol.org> 

 

  _____  

From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Shankar Krishnan
Sent: Wednesday, October 05, 2005 8:59 AM
To: qui...@li...
Subject: [Quickfix-developers] Order Types/ FIX Codes

 

Hi,

 

I am working on a front end for a simple stock and futures trading
application. Where can I find a doc

On various order types and the associated codes for these.  Are these part
of the "ROE" that my execution

Broker would give me.

 

Regards

 

RE: [Quickfix-developers] Order Types/ FIX Codes

[Fanshteyn, T. <tfa...@bo...>]

check out http://www.fixprotocol.org

________________________________

From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Shankar Krishnan
Sent: Wednesday, October 05, 2005 8:59 AM
To: qui...@li...
Subject: [Quickfix-developers] Order Types/ FIX Codes



 

Hi,

 

I am working on a front end for a simple stock and futures trading
application. Where can I find a doc

On various order types and the associated codes for these.  Are these
part of the "ROE" that my execution

Broker would give me.

 

Regards

 

[Quickfix-developers] Order Types/ FIX Codes

[Shankar K. <skr...@jw...>]

 

Hi,

 

I am working on a front end for a simple stock and futures trading
application. Where can I find a doc

On various order types and the associated codes for these.  Are these part
of the "ROE" that my execution

Broker would give me.

 

Regards

 

[Quickfix-developers] Problem with hanging call to initiator.stop()

[<ec...@fi...>]

All,
=20
I am having a problem when calling initiator.stop().  My application
simply hangs.  This tends to occur when I attempt to stop my application
after a call to Session.sendToTarget(msg, sessionid) returns with a
SessionNotFound exception.  I am not sure why the session cannot be
found, as I am not logging out of it or otherwise doing anything
intentional.  I can handle this exception and recover; my big concern is
the hanging call to initiator.stop().  I have seen previous posts about
this, but no real solution.  This has occurred with a couple of
different builds - 1.9.4 and 1.10.2.  I have both built the .dlls and
use the binaries from the quickfixengine.org site.  My application is in
C#.  Any patches, fixes, or workarounds would be greatly appreciated.
Thanks!
=20
Everett
=20

Re: [Quickfix-developers] username / password in logon msg?

[Oren M. <or...@qu...>]

You would add that tag just like the password tag, in the toAdmin =
callback.

--oren
  ----- Original Message -----=20
  From: Alvin Wang=20
  To: Francis Gingras=20
  Cc: qui...@li...=20
  Sent: Tuesday, October 04, 2005 7:25 PM
  Subject: RE: [Quickfix-developers] username / password in logon msg?



  I am talking abuot tag 553.=20

  thx=20



       Francis Gingras <fr...@at...>=20
        10/04/2005 05:45 PM=20

              =20
                To:        'Alvin Wang' <AW...@FF...>=20
                cc:        qui...@li...=20
                bcc:        =20
                Subject:        RE: [Quickfix-developers] username / =
password in logon msg?=20



  Alvin,

  Yes it's confusing: it's called SenderCompID.  You also need to set
  TargetCompID.

  Francis


  ________________________________

  From: Alvin Wang [mailto:AW...@FF...]=20
  Sent: Tuesday, October 04, 2005 20:15
  To: Francis Gingras
  Cc: qui...@li...;
  qui...@li...
  Subject: RE: [Quickfix-developers] username / password in logon msg?



  Francis, I cannot not find Username in the document:=20
  http://www.quickfixengine.org/quickfix/doc/html/configuration.html=20





  ********************************************************************** =
This e-mail message is intended solely for the use of the addressee. The =
message may contain information that is privileged and confidential. =
Disclosure to anyone other than the intended recipient is prohibited. If =
you are not the intended recipient, please do not disseminate, =
distribute or copy this communication, by e-mail or otherwise. Instead, =
please notify us immediately by return e-mail (including the original =
message with your reply) and then delete and discard all copies of the =
message. We have taken precautions to minimize the risk of transmitting =
software viruses but nevertheless advise you to carry out your own virus =
checks on any attachment to this message. We accept no liability for any =
loss or damage caused by software viruses. =
********************************************************************** 

Re: [Quickfix-developers] username / password in logon msg?

[Scott H. <sco...@fo...>]

Alvin:

You can stuff the special fields into the outgoing Logon message by 
implementing the toAdmin callback.  In Java I do something like this for 
counterparties that use this type of authentication:

     if (message instanceof quickfix.fix43.Logon) {
       quickfix.fix43.Logon logon = (quickfix.fix43.Logon) message;
       try {
         String username = sessionSettings.getString(sessionId, "Username");
         logon.set(new quickfix.field.Username(username));
         String password = sessionSettings.getString(sessionId, "Password");
         logon.set(new quickfix.field.Password(password));
       }
       catch (Exception xx) {
         throw new RuntimeException("Username and Password must be specified in QuickFIX configuration");
       }
     }


On Tue, 4 Oct 2005, Alvin Wang wrote:

> Hi,
>
> How to include username (553) and password (554) in Logon message? Is
> there a way to do it in the configuration? That should be most intuitive
>
> Thanks
> Alvin

RE: [Quickfix-developers] username / password in logon msg?

[Alvin W. <AW...@FF...>]

I am talking abuot tag 553.

thx





Francis Gingras <fr...@at...>
10/04/2005 05:45 PM

 
        To:     'Alvin Wang' <AW...@FF...>
        cc:     qui...@li...
        bcc: 
        Subject:        RE: [Quickfix-developers] username / password in logon msg?


Alvin,

Yes it's confusing: it's called SenderCompID.  You also need to set
TargetCompID.

Francis


________________________________

From: Alvin Wang [mailto:AW...@FF...] 
Sent: Tuesday, October 04, 2005 20:15
To: Francis Gingras
Cc: qui...@li...;
qui...@li...
Subject: RE: [Quickfix-developers] username / password in logon msg?



Francis, I cannot not find Username in the document: 
http://www.quickfixengine.org/quickfix/doc/html/configuration.html 






                                                                                                                                                                                                                                                                                                    **********************************************************************
This e-mail message is intended solely for the use of the addressee.
The message may contain information that is privileged and confidential.  
Disclosure to anyone other than the intended recipient is
prohibited. If you are not the intended recipient, please do not
disseminate, distribute or copy this communication, by e-mail or
otherwise. Instead, please notify us immediately by return e-mail
(including the original message with your reply) and then delete
and discard all copies of the message. We have taken precautions to
minimize the risk of transmitting software viruses but nevertheless
advise you to carry out your own virus checks on any attachment to
this message.  We accept no liability for any loss or damage caused
by software viruses.
**********************************************************************

RE: [Quickfix-developers] username / password in logon msg?

[Francis G. <fr...@at...>]

Alvin,

Yes it's confusing: it's called SenderCompID.  You also need to set
TargetCompID.

Francis


________________________________

From: Alvin Wang [mailto:AW...@FF...] 
Sent: Tuesday, October 04, 2005 20:15
To: Francis Gingras
Cc: qui...@li...;
qui...@li...
Subject: RE: [Quickfix-developers] username / password in logon msg?



Francis, I cannot not find Username in the document: 
http://www.quickfixengine.org/quickfix/doc/html/configuration.html 

RE: [Quickfix-developers] username / password in logon msg?

[Alvin W. <AW...@FF...>]

Francis, I cannot not find Username in the document:
http://www.quickfixengine.org/quickfix/doc/html/configuration.html





Francis Gingras <fr...@at...>
Sent by: qui...@li...
10/04/2005 05:29 PM

 
        To:     'Alvin Wang' <AW...@FF...>
        cc:     qui...@li...
        bcc: 
        Subject:        RE: [Quickfix-developers] username / password in logon msg?


Alvin,
 
Username is in the config file, password is entered in toAdmin().
Use something like message.set(new QuickFix.RawData(password));
 
Francis

From: Alvin Wang [mailto:AW...@FF...] 
Sent: Tuesday, October 04, 2005 19:59
To: Oren Miller; qui...@li...; 
qui...@li...
Subject: [Quickfix-developers] username / password in logon msg?


Hi, 

How to include username (553) and password (554) in Logon message? Is 
there a way to do it in the configuration? That should be most intuitive 

Thanks 
Alvin 
********************************************************************** 
This e-mail message is intended solely for the use of the addressee. The 
message may contain information that is privileged and confidential. 
Disclosure to anyone other than the intended recipient is prohibited. If 
you are not the intended recipient, please do not disseminate, distribute 
or copy this communication, by e-mail or otherwise. Instead, please notify 
us immediately by return e-mail (including the original message with your 
reply) and then delete and discard all copies of the message. We have 
taken precautions to minimize the risk of transmitting software viruses 
but nevertheless advise you to carry out your own virus checks on any 
attachment to this message. We accept no liability for any loss or damage 
caused by software viruses. 
********************************************************************** 

RE: [Quickfix-developers] username / password in logon msg?

[Francis G. <fr...@at...>]

Alvin,
 
Username is in the config file, password is entered in toAdmin().
Use something like message.set(new QuickFix.RawData(password));
 
Francis

  _____  

From: Alvin Wang [mailto:AW...@FF...] 
Sent: Tuesday, October 04, 2005 19:59
To: Oren Miller; qui...@li...;
qui...@li...
Subject: [Quickfix-developers] username / password in logon msg?



Hi, 

How to include username (553) and password (554) in Logon message? Is there
a way to do it in the configuration? That should be most intuitive 

Thanks 
Alvin **********************************************************************
This e-mail message is intended solely for the use of the addressee. The
message may contain information that is privileged and confidential.
Disclosure to anyone other than the intended recipient is prohibited. If you
are not the intended recipient, please do not disseminate, distribute or
copy this communication, by e-mail or otherwise. Instead, please notify us
immediately by return e-mail (including the original message with your
reply) and then delete and discard all copies of the message. We have taken
precautions to minimize the risk of transmitting software viruses but
nevertheless advise you to carry out your own virus checks on any attachment
to this message. We accept no liability for any loss or damage caused by
software viruses.
********************************************************************** 

[Quickfix-developers] username / password in logon msg?

[Alvin W. <AW...@FF...>]

Hi,

How to include username (553) and password (554) in Logon message? Is 
there a way to do it in the configuration? That should be most intuitive

Thanks
Alvin
                                                                                                                                                                                                                                                                                                    **********************************************************************
This e-mail message is intended solely for the use of the addressee.
The message may contain information that is privileged and confidential.  
Disclosure to anyone other than the intended recipient is
prohibited. If you are not the intended recipient, please do not
disseminate, distribute or copy this communication, by e-mail or
otherwise. Instead, please notify us immediately by return e-mail
(including the original message with your reply) and then delete
and discard all copies of the message. We have taken precautions to
minimize the risk of transmitting software viruses but nevertheless
advise you to carry out your own virus checks on any attachment to
this message.  We accept no liability for any loss or damage caused
by software viruses.
**********************************************************************