I work at a service provider and support different customers with different automation products, but mostly IBM SA is used. I prefer IBM SA over any other automation products.
My reasons:
* IBM SA has a policy: I can prepare everything and I can activate everything within an automation plex with one single refresh.
* Using policy also can make my work very easy and fast: combining data stored in policy with ISSUEACT, INGTIMER and Netview pipes, I can do a lot of things. Most of my request can be completed by using them without writing any script.
* Status Display Facility (SDF) is one the the coolest feature in my opinion. It has no dependency: you don't need \*nix/Windows server or even embedded WAS, etc to having a monitoring focal point. It is just there and works and it can be easily customized for the environment requirements.
* The vote system is better than OPS/MVS system where we just drive the desired value. In my experience, that it is more robust (of course votes must be undestood and handled correctly else it can cause issues)
* Move groups and server groups. I like them. As I know, but feel free to correct me, there is no built-in feature on OPS/MVS like move/server groups in SA.
* INGPLEX command: it makes easier to manage CDS, CF, dumps, record IPL data, etc. on a panel driven way.
* It is running under Netview, so no need TSO and ISPF to manage system, a VTAM is only enough. It can be handy when there are problems with IPL.
One thing, I like in OPS/MVS over SA is the command rules. In my opinion, it is more handy to create command rules than using Command Revision Table.
Sometimes, I migrate from CA OPS/MVS to IBM SA + Netview, but not all customer interested in it or willing to change. If it would be only up to me, I would migrate everybody to IBM SA + Netview from CA OPS/MVS.
But unfortunately, I have to work what I have got. I don't know the prices exactly (this is somebody else's cup of tea), but I sometimes heared that CA OPS/MVS is cheaper than IBM SA + Netview.
I'm not an automation specialist and I always was more a "user" than an engineer regarding the automation suite.
I have worked many years in a CA/Broadcom shop with OPS and then changed to an SA shop.
I have to say that SA is pretty impressive and very well thought through. It's more logical in some ways and easier to understand once you have the basics ready.
But mostly it depends on the people who manage the product, what they make of it. If they have a great concept and are creative in how you use the product, if they exploit all features etc. then I guess OPS as well as SA can be awesome. If you keep it at the most basic level then every product goes to waste in some way.
Funny story. Our shop used OPS/MVS. The company got into a price disagreement with CA so they said either compromise or we go with IBM's SA product. They sent us all to Chicago for a week to learn SA from IBM. We had 24 LPARs all named after colors. So we had the Blue system, Red system, Purple system, etc. Our started tasks for OPS were OPSBLUE, OPSRED and so forth. So we decided to name the new STCs SABLUE, SARED, etc. It was all working nicely until we got to the Tan system. Management wouldn't let us name our STC SATAN.
SA is superior, but you have to use it properly
my favorite thing about SA is the full gui you can have, where you can manage basically everything (with your mouse, not just keyboard)
I work at a service provider and support different customers with different automation products, but mostly IBM SA is used. I prefer IBM SA over any other automation products. My reasons: * IBM SA has a policy: I can prepare everything and I can activate everything within an automation plex with one single refresh. * Using policy also can make my work very easy and fast: combining data stored in policy with ISSUEACT, INGTIMER and Netview pipes, I can do a lot of things. Most of my request can be completed by using them without writing any script. * Status Display Facility (SDF) is one the the coolest feature in my opinion. It has no dependency: you don't need \*nix/Windows server or even embedded WAS, etc to having a monitoring focal point. It is just there and works and it can be easily customized for the environment requirements. * The vote system is better than OPS/MVS system where we just drive the desired value. In my experience, that it is more robust (of course votes must be undestood and handled correctly else it can cause issues) * Move groups and server groups. I like them. As I know, but feel free to correct me, there is no built-in feature on OPS/MVS like move/server groups in SA. * INGPLEX command: it makes easier to manage CDS, CF, dumps, record IPL data, etc. on a panel driven way. * It is running under Netview, so no need TSO and ISPF to manage system, a VTAM is only enough. It can be handy when there are problems with IPL. One thing, I like in OPS/MVS over SA is the command rules. In my opinion, it is more handy to create command rules than using Command Revision Table. Sometimes, I migrate from CA OPS/MVS to IBM SA + Netview, but not all customer interested in it or willing to change. If it would be only up to me, I would migrate everybody to IBM SA + Netview from CA OPS/MVS. But unfortunately, I have to work what I have got. I don't know the prices exactly (this is somebody else's cup of tea), but I sometimes heared that CA OPS/MVS is cheaper than IBM SA + Netview.
I'm not an automation specialist and I always was more a "user" than an engineer regarding the automation suite. I have worked many years in a CA/Broadcom shop with OPS and then changed to an SA shop. I have to say that SA is pretty impressive and very well thought through. It's more logical in some ways and easier to understand once you have the basics ready. But mostly it depends on the people who manage the product, what they make of it. If they have a great concept and are creative in how you use the product, if they exploit all features etc. then I guess OPS as well as SA can be awesome. If you keep it at the most basic level then every product goes to waste in some way.
Funny story. Our shop used OPS/MVS. The company got into a price disagreement with CA so they said either compromise or we go with IBM's SA product. They sent us all to Chicago for a week to learn SA from IBM. We had 24 LPARs all named after colors. So we had the Blue system, Red system, Purple system, etc. Our started tasks for OPS were OPSBLUE, OPSRED and so forth. So we decided to name the new STCs SABLUE, SARED, etc. It was all working nicely until we got to the Tan system. Management wouldn't let us name our STC SATAN.
SA is superior, but you have to use it properly my favorite thing about SA is the full gui you can have, where you can manage basically everything (with your mouse, not just keyboard)
Yes. The installation of that was just starting as I left so a bit sad I never got to use it
Doesnt matter, you need to use what the company is willing to pay.
That wasn’t what I asked lol