OK, TED, you "boxed" me into a corner. But you have to understand that to us PC programmers, anything more powerful is considered a mainframe, and mainframe programmers are collectively referred to as "dinosaurs"... unless they are Y2K code remediators, of course. (gg)
Technically speaking, from what I understand, ALYD mostly uses Sun SPARC workstations running Unix, which is where SmartCode resides. Code is usually delivered via tape which is then put on some sort of MVS box that compiles it. Logic would dictate there would be all sorts of errors for missing library files, but the important part is whether the post-compile (after the code is modified) generates any more or less errors. Yes, I had heard that library files are often compressed, but I can't imagine why you would want to compress source code, unless it's precompiled or something(?).
I do remember asking ALYD a while back about EBCDIC to ASCII conversion and if/how they flag special characters, and I was told this is not a problem. I also recall that for very special circumstances they do have immediate access to a mainframe. The good thing about ALYD's "we-do-it-for-you" set-up is that if they ever do run into some strange scenarios they could jump through hoops and no one would be the wiser (gg). I suppose you could say that while other Y2K vendors are offering tools, ALYD is offering a toolbox replete with carpenters.
If there are any particular situations you are wondering if ALYD can handle, I can always run them by ALYD in hopes I could get an answer. My guess, though, is that all we'd get in response is a "yes we can do it" and not anything more elaborate. Judging by the recent contracts, so far it doesn't look like there's a chink in the armor, knock on metal (g).
- Jeff |
