Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : CSGI ...READY FOR TAKE-OFF! -- Ignore unavailable to you. Want to Upgrade?

To: TEDennis who wrote (1356)	11/23/1997 3:05:00 PM
From: tom rusnak	Respond to of 3391

Re: Motorola If Motorola had 480 files (i'm guessing file layouts or copybooks) missing the first time they sent source to Consygen, it tells me that Motorola has not compiled and tested the source before it was sent, so now they have no real basis for comparing post conversion test results except against what they are running in production. This certainly leaves them open to finding a whole slew of problems, not necessarily related to the conversion effort, but highlights the difficulties in the client having to try and package their code, find the right levels of source, find the right copybooks........ My guess is that their will be errors discovered during testing which the client is going to have to 'debug' to determine if it was because of incorrect levels of source that was sent out. The old GIGO (Garbage In/Garbage Out). 8 days to convert 500,000 lines??? that does not sound fully automated. I thought the millenium project of over 1 million lines was done overnight?

To: TEDennis who wrote (1356)	11/23/1997 3:17:00 PM
From: tom rusnak	Respond to of 3391

Re: Source code managers (Panvalet, Librarian, Endeavor, ) I would guess that the customer has to expand all the source library 'include' statements inline before sending it off to Consygen. And then what happens when after the source is converted? Looks like the customer would then have to manually put the expanded code back into their respective 'include' members. A very manual and tedious process. I've been through a conversion where the client had source in panvalet and the 'new' system did not have panvalet. Subsets and member names greater than 8 characters made it difficult to just convert the stuff to 'copybooks'.

To: TEDennis who wrote (1356)	11/23/1997 3:23:00 PM
From: tom rusnak	Respond to of 3391

Re: Languages supported Besides no mention of SAS, RPG, C, PASCAL, ...... they do not support ASSEMBLER in their 2000 change process. I worked at a Phoenix area bank that was 100% assembler in the applications. I currently work at a large financial institution that is about 40% ASSEMBLER. (The rest is COBOL stored on LIBRARIAN...mmmm...there is that source library problem again....) But then, any solution provider that depends on source code is going to run into many languages that they do not support.