AS9 Manager abends if job highlighted after SP1

[flightrisk1]

Hello
I recently started with a new company and inherited an AS9 on NT4.0. Alerts were not going out properly and I noticed that the s/w had never been patched. I layered on each patch up to and including SP1 and we are now at build 2100. However since SP1 went on we can no longer click on the backup jobs that existed before the SP. If we click on the job the manager instantly closes which means we cannot edit or delete the jobs. Tried CA support and it took them 5 minutes to say we don't know, just create new jobs. We can't create new jobs if we can't delete the old ones. Anyone experience this? We need help.
Tks!

 

[pakilaci]

Jobs are stored in the 00000001.QSD directory. Stop all engines, move that directory (or delete if you want), start engines. The system creates a new directory and you have to manually add jobs.

 

[flightrisk1]

Thanks for the response Pakilaci!
That's the weird thing about this. I renamed that file to .old but when I do the old jobs still show in the listing but they now show as corrupt.
I also ran a dbfix and a keybuild as well but they found no errors. I hate to have to uninstall and reinstall and all the horror that entails...

 

[vschumpy]

I spoke to CA about a similar problem last week, and as far as I know they are working on a fix, so watch out for a patch.

 

[pakilaci]

Here is the "solution" from CA...
Title: MGR CRASHES WHEN LOAD SCRIPT WHICH WAS CREATED BEFORE SP1

BAB v9.01 w/SP1 applied:

After applying SP1 to BAB v9.01 you might encounter the following problem(s):
1. Job scripts will not run correctly after applying SP1. For example Pr
e/Post processing might not work.
2. Manager might GP or crash after SP1

It is important to note that if you do encounter these problems after applyin
g SP1 that you DO NOT recreate the job script. Please contact Computer Assoc
iates Technical Support for assistance.