|
 |
Enhanced monitoring support for USS resources |
SA z/OS 3.2 is used to automatically start and stop applications. Typically these are legacy jobs (started tasks) with unique job names. Within z/OS, there is also a UNIX environment, called UNIX System Services, that is capable of running multiple processes, as is the case in any other UNIX environment. However, the process names are not necessarily unique. In particular, all Java programs have a process name of install_path/java. Without a unique process ID, SA z/OS isn't able to monitor the existence of a particular process, nor is it able to automatically start or stop it. Thus, only unique process names can be monitored out of the box.
With the introduction of a new filter definition in the SA z/OS policy for USS resources, it is now possible to automate as-is Java programs. When SA z/OS 3.2 is configured to automate UNIX processes, it asks for the name of the program that is running within the automated process. In addition, it is also now possible to specify filter information that allows SA z/OS 3.2 to look up UNIX processes that match that filter. The filter can be a list of parameters or the name of a script, with or without parameters, that is to be called upon startup. When the automation product starts a program, it subsequently needs to look up the process table to monitor the new process that was just started. The new filter is used to find that process.
| 
