Unicenter JMO Workload Agent 3.1 on RH Linux to submit jobs to TNG 2.4 Workload Agent box

Products

• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu
• Unicenter Job Management Option

Issue/Introduction

Description

1. Is there a way to have Unicenter JMO Workload Agent 3.1 be able to communication with TNG 2.4 Workload Agent to run jobs in addition to the already scheduled processes?
   
   
2. Is it possible to have Unicenter JMO Workload Agent 3.1 run TNG 2.4 Workload Agent jobs and have TNG 2.4 continue processing on its own?

Solution

Unicenter JMO Workload can not distinguish between 2.4 and 3.1 jobs. It is the matter of what you submit on that box and if that job is defined correctly and eligible to run then it will run.

You can have Unicenter Workload Agent, where Workload jobs run, can be lower or at the same level of CA Unicenter version as that of Workload server but can not be higher than that of it's Workload server.

For example, on a Workload server you can have NSM 3.1 and on Workload Agent you can have TNG 2.4, NSM 3.0 or NSM 3.1. But when you have NSM 3.0 on Workload server then you can have TNG 2.4 and NSM 3.0 on Workload Agent box, but not NSM 3.1.

1. How do I set it up so that the 3.1 on Linux can tell 2.4 on HP-UX run a job?
   
   All you need to do is to define a station for your workload 2.4 box, define workload joset/job on your workload server box and include that station id of your TNG 2.4 workload agent box and then submit that job.
   
   Workload alone is unable to determine the differences between 3.1 Job or 2.4 Job.
   
   
2. Is it possible to have Unicenter JMO Workload Agent 3.1 run TNG 2.4 Workload Agent jobs and have TNG 2.4 continue processing on its own?
   
   That will be the case where a box is Workload Server and Agent for itself and for other remote Workload Servers as well.
   
   It is possible because when you install Workload Server; that box can not only run jobs on itself but can submit jobs onto remote box(s). The box is not only Workload Server, but also a Workload Agent. In this case, you can have a box run TNG 2.4 jobs and can accept NSM 3.1 jobs from a remote box where there is NSM 3.1 Workload Server is submitting jobs to that box.
   
   
3. Later, how do I tell 2.4 to stop doing work itself, but still listen for 3.1 to dispatch jobs to it?
   
   There are a couple of ways to accomplish this:
   
   DO NOT submit TNG 2.4 jobs on that box by purging/deleting those jobs which you have defined on that (2.4) box. You can also shutdown CASHDB on that box to stop db processing by running the following command:
   
   'caidb stop CASHDB'
   
   You can move $CAIGLBL000/sche/log/$HOSTNAME/MAIN_SH_NODE file to other place and then recycle TNG on that box.
   
   This is not a supported way of configuring Workload Agent box.

The best case scenario will be to de-install what you have on your box and then install what you want on that box .

Environment

Release:
Component: CA90S