I've been there. Windows and Dos were all I knew, but the Company decided to go Unix. We got a Unix resource to convert some of the major scripts and they ended up being quite clever. Most of the others, I just moved to a Windows PC running Task scheduler. It had Essbase client, Perl and you can use Samba to map a drive to the server and ensure the logins have a server name rather than localhost. It's not necessary to have everything running on the server.
Eventually, the PC became a Windows server managed and supported properly and then all jobs moved into an independantly managed enterprise job scheduler where everything was converted into java and perl (not by me - thank God).
|