Workload Automation on z/OS allows users to use a single point of control and monitoring of complex workflows.
Thanks to the integration with a Chat Tool, starting from release v10.1, you’ll be able to empower Workload Automation on Z to send notifications about incidents and share information with your DevOps team members on chat platform (such as Slack, Mattermost or Teams).
Collaboration becomes easy, immediate, and effective for promoting teamwork and addressing daily issues.
- Are an administrator, an operator and/or a developer working in a collaboration team.
- Want a single point of communication with all the relevant people seeing the same information.
- Are Looking for real time notification in a chat tool to reduce the time to quickly detect and diagnose any issue.
Did we capture your attention? Let’s explore how it works
At glance any time that specific alert condition occurs on your mainframe automation processes you can receive an incident notification upon a specific chat platform.
Basically, the product detects an issue, then retrieves and sends the incident data to the chat tool service that immediately redirects the information to the bot who manages to post the incident in the final chat platform destination your team is using.
INITIALLY AN ALERT OCCURS, BUT.…..HAS THE INCIDENT TO BE SENT?
If the alert matches the ones in the INCIDENT parameters, the members in the EQQINCID dataset with the information are read.
You can set up to 8 different alert conditions. Which ones?
- DURATION: An operation in the current plan is active for an unexpectedly long time.
- SPECRES: The time that an operation in the current plan is waiting to allocate a given resource exceeds the time specified by the RESOPTS CONTENTIONTIME parameter.
- ERROROPER: An operation in the current plan is set to ended-in-error status.
- WLMOPER: An operation in the current plan is promoted by WLM.
- POTENTRISK: The risk level of a critical operation in the current plan has become Potential.
- OPCERROR: An IBM Z Workload Scheduler subtask or subsystem ends unexpectedly.
- LATEOPER: An operation in the current plan becomes late, which means that it reaches its latest start time and does not have the status started, complete, or deleted.
- HIGHRISK: The risk level of a critical operation in the current plan has become High.
In the EQQINCID dataset you can find:
•The members that contain the text of the incidents.
• A member named RULES that contains the rules. The structure of a rule is:
FILTER(expression1, expression2, …, expressionN)
After taking the information in the INCOPTS statement
To activate this function, you need to ensure that you have followed these steps. For further details you can consult the product documentation (Managing the Workload – Controlling and Monitoring – Chapter: Posting incidents and sharing information through a chat tool, steps 1-4).
- You have to set the INCOPTS statement with the parameters to connect to the incident notifying tool:
- The INCIDENT parameter in the ALERTS statement with the conditions under which the incident is posted to a chat tool:
- The SSL parameters in the HTTPOPTS statement for the SSL communication:
- You have to add the certificates to a key ring and define the EQQINCID dataset with the members.
For the troubleshooting you can set a further level of diagnosis by adding DIAGNOSE MONFLAGS(X’00000200′).
Which are your advantages?
- The integration of the product with a chat tool that improves the reliability, service recovery time and collaboration efficiency.
- A real time notices on the status of the health of the automation processes on Zos.
- Customized key information to solve promptly the problem.