[ts-gen] Re: status update -- on the g++4 road; also x86_64

[R P Herrold]

On Fri, 10 Nov 2006, our Debian correspondent wrote:

> Glad I was of some help pointing you to the right version.

> We use the [Debian] 'testing' dist on our dev box and 
> [Debian] 'stable' on production, so that may give us 
> problems later if we get round to using this for real.

<smile> -- I am certain the sender meant 'when' rather than 
'if'

> Then again it wouldn't be the 
> first production app to run on the development box for this 
> reason. :-) Database set up and tws connectivity ran fine 
> with './shim --data'.

Great -- you are very very close then; that means you have 
solved database setup and userid keying issues.  The 
regression scripts are for our testing; some simplified 
testing can be done thus [*** REMEMBER -- using a 'paper' test 
account only ***]:

Here are a couple of really straightforward command sets to 
feed into the shim via a 'shell' HERE document;  test 1 does 
some Market Data and History operations; [the output stream 
should appear in /var/log/messages if you have not set up an 
additional logging stream into a pipe (I think I have 
documented how to do that, but will check)].

Test 2 builds an order locally, but cancels it pre-upstream 
transmission, and then does a market buy and a sell (it starts 
the buy as a LMT buy, and then converts it to MKT).  This is 
somewhat complex order management, but trivial market orders 
are clearly working well, and we are developing, and therefore 
testing at the edges of our comfort zone.

Test 1 - subscription, history on AIG and YM:

cat - << END | ./shim --risk
ping this is a test;
verb 2 Detail;
tick add   5 1;
book add   5 1;
past add 166 1;
wait 1;
quit;
END


Test 2 -- buy and sell AIG:

cat - << END | ./shim --risk
ping buysell;
verb 2 Detail;
tick add 5 1;
order(1,MKT,Create,100,0.0,0.0,0);
order(1,MKT,Cancel,100,0.0,0.0,0);
order(3,LMT,Create,100,0.0,0.0,0);
order(3,MKT,Submit,100,0.0,0.0,0);
order(4,MKT,Submit,100,0.0,0.0,0);
tick del 5 1;
quit;
END


Logging into a pipe:

add the following line, ane restart the syslogd;

[herrold at centos-4 feed]$ grep pip /etc/syslog.conf
local0.*                |/var/tmp/pipe

and set up the pipe to exist and to be world readible:
$ sudo mkfifo -m 755 /var/tmp/pipe

Then you may read it thus:

$cat /var/tmp/pipe


> I'm now trying to get a handle on how 
> to actually make it do something. I had some syntatic errors 
> when trying to run the regresion test script, and will try 
> and work out what's going on there, first, on Monday.

I suspect that these arise from running from within the bin/ 
directory, rather than up a level, in the directory where the 
./shim  executable sits.  There are a number of path 
sensitivities in the 'included' file in ./bin/ scripts which 
anticipate being run from the directory above.

> Again, I think it's probably the difference in enviroments. 
> I'll report back my results (if I get it working) or the 
> errors (if I don't). Have a good weekend.

Thanks again; I look forward to the next report.

-- Russ Herrold