Thanks. So other than training issues, there really wasn't much from a conversion point of view - except for setting up the DB2 and the access to DB2. No other real problem areas? Is that correct?
Myron -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ernie Takeuchi Sent: Monday, February 04, 2008 10:42 AM To: [email protected] Subject: Re: Conversion of CA scheduler to IBM Scheduler Myron, We have done this. The setup of TWS is not difficult but the scheduling of jobs may be difficult and require staff to be trained to work with TWS. Also, I don't know if this has been done yet or not but the version of TWS we were working with required DB2 for historical reporting online whereas CA-Scheduler would show the jobs. It was on Tivoli's agenda to create a schedule outside of using DB2. Ernie. "Myron Miller" <[EMAIL PROTECTED]> wrote in message news: <[EMAIL PROTECTED]>... > We're being forced to convert from the CA scheduler to the IBM scheduler > system. Has anyone done this? Are there any IGOTCHA's that we should > worry about? > > Any comments for the conversion would be helpful. Understand that the > conversion will happen. It's not an option to consider other items. > > Myron > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
