Another hectic day today.
I had to fight with ClearCase this morning for a few people. One of my co-worker's laptops had the wrong domain in the HKEY_LOCAL_MACHINE\SOFTWARE\Atria\ClearCase\CurrentVersion\ClearCaseGroupName entry in the registry and the Atria Location Broker was using the wrong login as well. I don't know why this happens, but these settings seem to keep getting reset to point to our old domain. One of these days I'll figure out why.
We talked to the team working with DataStage to consolidate some files here about some problems they were having when trying to call out to some stored procedures to validate some VINs for vehicles we have in our system. This call is slowing down the DataStage transfer jobs to something like 25 rows per which is pretty slow for our needs. The stored procedure interfaces with a piece of software on our iSeries called VINA provided by Polk Software. This program seems very ineffecient according to my boss, so we suggested that the DataStage team re-implement it. They didn't like that idea very much, so I continue to look...
We have some problems with people being able to view document images in our eBusiness portal application, but I haven't even had a chance to look at those things yet. The code for viewing images has not been as stable as I would have liked. Mostly because it is trying to convert an asynchronous conversion process into a synchronous one.
We continue to have problems with our build quality for the eBusiness portal as well. I have a task to improve this process, so I'm trying to pass off some of my other tasks so that I can focus on the build process. I'll try and detail that effort later.
I had to fight with ClearCase this morning for a few people. One of my co-worker's laptops had the wrong domain in the HKEY_LOCAL_MACHINE\SOFTWARE\Atria\ClearCase\CurrentVersion\ClearCaseGroupName entry in the registry and the Atria Location Broker was using the wrong login as well. I don't know why this happens, but these settings seem to keep getting reset to point to our old domain. One of these days I'll figure out why.
We talked to the team working with DataStage to consolidate some files here about some problems they were having when trying to call out to some stored procedures to validate some VINs for vehicles we have in our system. This call is slowing down the DataStage transfer jobs to something like 25 rows per which is pretty slow for our needs. The stored procedure interfaces with a piece of software on our iSeries called VINA provided by Polk Software. This program seems very ineffecient according to my boss, so we suggested that the DataStage team re-implement it. They didn't like that idea very much, so I continue to look...
We have some problems with people being able to view document images in our eBusiness portal application, but I haven't even had a chance to look at those things yet. The code for viewing images has not been as stable as I would have liked. Mostly because it is trying to convert an asynchronous conversion process into a synchronous one.
We continue to have problems with our build quality for the eBusiness portal as well. I have a task to improve this process, so I'm trying to pass off some of my other tasks so that I can focus on the build process. I'll try and detail that effort later.