SI
SI
discoversearch

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 : Y2K (Year 2000) Stocks: An Investment Discussion -- Ignore unavailable to you. Want to Upgrade?


To: TEDennis who wrote (8988)1/16/1998 3:09:00 PM
From: John Mansfield  Read Replies (1) | Respond to of 13949
 
Re: Vertex 2000: Post 2 of 2

TED,

This sounds more convincing than all previous posts and other info I have read! Up till now I thought this was just another silver bullit; now I am starting to wonder...

Question:

- did you discuss the possible performance impacts of the solution? I guess some performance penalty might be there; especially in some routines inside loops performance penalties might be a problem!?

- <<couple of nitty-gritty questions I asked regarding situations that the 'Enabler' might not be able to handle (like non-character display data),>>
What is that; non character display data - what does it have to do with windowing date fields?

<<1) It is relatively easy to 'phase in' (you can intermix bigitized and non-bigitized data and programs)>>
I suppose on a per program base; not on a per-source module base?

<<
I would also expect this technique to have problems with programs that have been 'CA-OPTIMIZER'd. Again, simply turning off optimization should alleviate the problem>>
turning of speed-optimizing also has a performance penalty; but in many cases that might not be a problem, i guess.

Good report, I liked it!

Regards,

John



To: TEDennis who wrote (8988)1/16/1998 3:31:00 PM
From: Jeffrey S. Mitchell  Read Replies (1) | Respond to of 13949
 
Re: Questions for/about BMR

1. TED, if Vertex only supports COBOL II, what percent of the COBOL out there on mainframes does that cover?

2. The 50 year window you mentioned-- can that be applied to different sets of variables or just as a blanket. Also, does the user have a way to choose the window or does the software figure it out for you?

3. What plan does BMR have to support third-party databases? What percent of all COBOL II systems use them?

I think it boils down to the fact that Vertex does work "as advertised" but that the potential market it would serve is obviously not nearly as large as that covered by a "traditional" Y2K vendor. Nevertheless, Y2K is such a pervasive problem that you can't have enough solutions. (gg)

- Jeff



To: TEDennis who wrote (8988)1/16/1998 5:46:00 PM
From: ThirdEye  Read Replies (1) | Respond to of 13949
 
TED: If you were in charge of modifying V2K to support the other versions of COBOL that are in development, how long would it take you?

I understand that COBOL II may be the most obvious or largest COBOL market that is requiring a fix. Given the modifications that you believe would be necessary to support other versions, what real chance does BMR have to become attractive to a wider market? Are they shooting themselves in the foot by even trying?



To: TEDennis who wrote (8988)1/16/1998 9:03:00 PM
From: Ed Mulhall  Read Replies (1) | Respond to of 13949
 
Ted,

Super job!

What would cause CA et al to rewrite their debuggers/testers. How difficult?

Is it fair or accurate to say that "bigitizing"your code breaks the link between source and object?

Is "bigitized" code supportable code? What kind of training would be required to upgrade application support staff/operators/production control personnel?

I realize they are only going into beta but did they give you a feel for how thoroughly this approach has been tested / stressed?

Finally, given your background if you were in charge of a large blue shop with a typical mix of products, versions, Db's, apps, etc. Would you bigitize? BotLine how tough a sell will this be into that environment?
Again Thanks,

Regards,
Ed