Thanks everyone . It turned out that a faulty msgid was used to mark this task as up and that was not happening ....
On Mon, Mar 10, 2014 at 7:01 PM, Lizette Koehler <[email protected]>wrote: > If you have not done so, you might want to send an email to > [email protected] > > This is an OPS/MVS Newsgroup. > > Second, you should join the CA Community for OPS/MVS as well > > Now my questions. > > Do you have an STC Table entry and an STC Action table? > > I ran into something like this when I had both of these misconfigured for > my > task. I opened a case with the OPS/MVS Support at CA and they helped me > figure out what was wrong and how to correct it. It took some digging to > figure that out. > > Due to the infinite way OPS/MVS can be configured, it will be a challenge > for a list to really examine this issue. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of baby eklavya > > Sent: Sunday, March 09, 2014 8:57 PM > > To: [email protected] > > Subject: Timing issue with Automation product (CA OPSMVS) > > > > We are running z/os 1.11 and also have SAS 8.2 in our shop .Each time > after IPL > > ,automation issues the start command for SAS server3 started task > repeatedly ( > > more than 100 times).But the fun part is that , the task is actually > started with one of > > the start commands issued initially . But automation still keeps issuing > the start > > command for this task and eventually gives up saying the task cannot be > started . > > > > Is this a timing issue ? or a communication problem between the task and > > automation product ( CA OPSMVS) . How can i fix this ? > > > > Regards, > > Baby > > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
