Due to the the death of the sole IT guy, we just picked up a client firm that appears to be running two unlimited user SBT source coded systems with AR/AP/GL/IC/SO/PO on novell 5.0 servers and with MS DOS on dos + win 2K/95/98 workstations. One system is based on 2.5 Pro and the other on 3.0/3.0i pro. As we are not an SBT dealer, we tried to contact SBT resellers and they only seem to want to sell lots of new expensive microsoft software.
That is not an option, as the firm is a Federally regulated broker dealer exchange member entity. In fact we got the job because some of us were once licensed Series 24, 27, 4 on top of the 63 and 7 in the securites buisiness and we have the business expertise to figure out if the outputs make sense from the inputs. In checking out the pile of stuff we can't even determine if it is Y2K complaint, but it runs.
Questions abound.
Is there a real SBT consultant out there who will honestly tell us if the SBT Pro version 2.5 and 3.0/3.0i were Y2K complient, or if they were not, does it make a difference, especially in 2003. We even heard of a "Y2k" kit and yet dealers tell us we have to have our client buy all new software to get it.
If the code is not Y2K complient, can it be fixed to do so.
The customization appears not in the SBT modules but in tons of stand alone dbase + foxpro reporting and front end systems for portfolio risk management and data interchange that read the sbt databases.
The firm likes the system and hates the windows platform (too much maintenance required) and actually is using this project as a beginning to running the code entirely on a Unix Box wih the foxpro for SCO they grabbed on ebay.
We really do not want to yank them off of SBT, unless it is absolutely necessary, becasue if we have to, we will probably recommend that they sub let a system at another firm on a Mainframe as windows products don't survive in the firm's intense environment where a sever crash costs the firm a $10,000 fine.
The old stuff works, it has stayed up for most of a decade with a total of 8 shutdowns (holidays for maintenance)in rougly 10 years.
That is not an option, as the firm is a Federally regulated broker dealer exchange member entity. In fact we got the job because some of us were once licensed Series 24, 27, 4 on top of the 63 and 7 in the securites buisiness and we have the business expertise to figure out if the outputs make sense from the inputs. In checking out the pile of stuff we can't even determine if it is Y2K complaint, but it runs.
Questions abound.
Is there a real SBT consultant out there who will honestly tell us if the SBT Pro version 2.5 and 3.0/3.0i were Y2K complient, or if they were not, does it make a difference, especially in 2003. We even heard of a "Y2k" kit and yet dealers tell us we have to have our client buy all new software to get it.
If the code is not Y2K complient, can it be fixed to do so.
The customization appears not in the SBT modules but in tons of stand alone dbase + foxpro reporting and front end systems for portfolio risk management and data interchange that read the sbt databases.
The firm likes the system and hates the windows platform (too much maintenance required) and actually is using this project as a beginning to running the code entirely on a Unix Box wih the foxpro for SCO they grabbed on ebay.
We really do not want to yank them off of SBT, unless it is absolutely necessary, becasue if we have to, we will probably recommend that they sub let a system at another firm on a Mainframe as windows products don't survive in the firm's intense environment where a sever crash costs the firm a $10,000 fine.
The old stuff works, it has stayed up for most of a decade with a total of 8 shutdowns (holidays for maintenance)in rougly 10 years.
