"It's stable enough. I haven't noticed any problems since it was installed."
"The documentation is simple, easy to follow, and use. A limited, first-time systems programmer can do it, in that it is out-of-the-box almost functional."
"It's a very stable product. I very much like the SSM stuff in it. The rules engine, it's awesome."
"I can and interrupt what's going on, bring a job down if I need to, and bring it back up."
"OPS/REXX is valuable because it allows us almost unlimited flexibility in automating our system."
"It alerts the operators when it is time to repair the communications and the IPLs."
"With the automation pieces we can bring this region up or take this region down, and it allows us to always meet our time critical requirements."
"It's very secure, because it's a legacy application."
"Valuable features include: SSM, which provides for orderly startup and shutdown; OPSLOG, which enables filtering by message-id, and/or jobname(s); Rules, as OPS/REXX interface streamlines deployment, interfaces easily with JES2 and z/OS."
"It is easy to see if anything is wrong. The queues on the system are fast, and it is very intuitive to locate something."
"When we changed to JES3, the programmers didn't have to know anything. The product provided the same interface with the same look and feel."
"Thresholds with alerts are valuable, enabling us to fix a problem before it has an impact."
"We have not had any major issues in approximately 15 years."
"I use most of the SMS space management extensively, but also the features that enable me to look at dumps and different dataset allocations to the system, and performance data from the queueing and delays."
"I also really appreciated all the work that everybody did to get it functional for JES3, and they continue to do so, even though IBM said they are going to do away with JES3."
"The scalability is absolutely fine."
"Between the tech support and the person I was working with, they have been extraordinary."
"We can't see the percentages to see the percentages of the CPU utilized. We should be able to see how much was used by our part of the system. Now, we have to continuously recalculate that information."
"It definitely needs more web-based interface, to be more mobile-open. More APIs, more open source to it."
"Because of its age, it's a little bit difficult to modernize some of the integrations and some of the functions."
"Some of the command sequences are too long."
"It’s a complex product. The initial installation is easy, but implementing various functions is a constant process."
"Performing a stop/restart of OPS/MVS could be a little smoother. Without special coding, some undesired tasks will be started and some necessary tasks will be stopped if we have to bounce OPS/MVS during the day."
"Scalability is zero. It cannot be scaled because of its age."
"The further expansion of the mainframe teamcenter interface. Also, the web services support is something that I am looking into."
"The reason sometimes it is not stable, we do not have the expertise to write the script."
"It confuses a lot of people because there are so many features, but when they see me bouncing around they say, "I didn't know it did that, I didn't know it did that." It takes a long time to find all the different features that are available."
"The documentation, like installation guides and stuff, put it all in one place."
"The things that I would think about would be in relation to JES3. However, I don't know if they'll be able to do much more with that because I don't know how much longer IBM is going to be supporting JES3. So I can understand not doing additional development. But if I were to suggest something it would be the JES3 initiators, the JES3 queues."
"The documentation format could be better. I noticed with the last release that all of the manuals were bundled into one. It used to have a separate installation guide, user guide, etc."
"If a unit of work ID is associated with a CICS, a DB2, and a MQ transaction, and having that capability correlate to those different technologies via one business application transaction which would be beneficial."
"We are using Datacom as the database system, so maybe a little bit more integration with that."
"They are already working on improvements. One of them is the operational intelligence, which is a lot of stuff I am trying to learn and work on right now, which SYSVIEW reports to that all the system things which are going on."
More SYSVIEW Performance Intelligence Pricing and Cost Advice →