Daynote ,Svenson

Sjon
 
-- Home -- Links -- To do -- Calendar -- The Gang -- The Undeniables --

  -- Yesterday -- Week view -- Tomorrow  

MM-clxxxviii     Thursday

 

2000-07-06

 


Unlike yesterday it starts out dry. For the rest it an exact copy, dry and sunny but cool for summer (14 to 21°C).

I lost yesterday. I am sure I did put it in its place on Monday but some how I lost it and I just cannot find it anywhere.

 

One thing I remember, a new problem. Not that I needed such a thing but ... well.
All orders remain in status VAL in the Integration test environment, which sits between the development/test environment (programmers playground) and the production environment (from which distributions are made). In theory the managers must test in this (and the system test) environment. Of course Jan, when he tests does that in the development env.
I spent time yesterday on it and the whole morning today. Stepping trough the source with a debugger (which is all but simple for a process that gets submitted from another system) did not turn up any clue. After sifting trough several hexadecimal dumps I finally succeeded to reproduce the problem in the development environment. And solve it in 15 seconds.
In the new release, where the error occurs occurred :) the order header file is two bytes longer than in the old release. The program running in the Integration environment was compiled with this new length but an internal buffer was still defined with the old length.
I started on a redesign of the program some time ago but this got pushed down on my priority to do list. The redesigned program works correctly but is not yet usable (it has an endless loop somewhere else) so I made a temporal fix (copy source, change buffer from 251 to 253, compile and walk the distribution carrousel).

After finishing that Iwan, from Norway, reported a problem with activating of contracts. Well actually the activating of a specific contract.
Standard procedure.

  • First I try to recreate the problem here. Doesn't go, I mean it goes. Well the problem doesn't show up and the program does work as expected.
  • Next I ask my manager. Oeps, he is on holiday for three weeks.
  • Third, because the program works over here, I check the remote system. Do they have local adaptations in our programs? Did they cancel jobs? Do they have the defaults sensibly? that sort of things. Oeps, I haven't got a user profile/password on their system.
  • ...
This is going to take some time.


Adios
-- Yesterday -- This week -- Tomorrow --

Swijsen © 2000
Of course life is a game without an undo and where failure is not an option.