We also have Nimbus in house and also noticed it didn't have any mainframe
capabilities. So, after looking at it's possibilities, I mentioned it might be
possible to send some data to Nimbus. Little did I to know what that statement
would cause me... So, I wound up with the honor of finding some way to
incorporate the mainframe into Nimbus (and not just using NetConnect to ping
it). I wasn't unhappy about it though. It's few and far between the chances
where I get to do some programming.
I accomplished this in several phases.
Phase One;
I started out simple and created a company MIB with what I thought I'd like to
get alerts on. I found an SNMP trap command and used the OSHELL command to
issue it. I found this command (awtrap) in the base Unicenter file system that
comes with any CA product (I think. We only have CA-1). For example, OSHELL
/cai/agent/ro/awtrap ...< parameters>
This gave me simple alerting. I wrote a started task that would periodically
run the active task chain and if it found an STC that wasn't running (i.e.
CICS, DB2, HSM, etc) that should have been, it would issue this command. We
used this method to give us alerting on critical tasks. It was crude, but it
got the job done. It had some drawbacks and advantages. One advantage was the
ability to put systems (i.e. these started tasks) into 'maintenance' mode. This
was useful for scheduled down times when we didn't want Nimbus alerting us.
Phase Two:
Using a sample console program that I found in SYS1.SAMPLIB, I created another
started task that monitors the system log. I used this program to look for
specific messages (i.e. CICS short on storage, DB2 archive log issues, etc).
When one of these messages was detected, an SNMP trap was issued with the
message id and message content using the Phase One method. This gave us
alerting for critical system issues.
Phase Three:
This phase was the most challenging because I went ahead and created a true
snmp sub-agent. Not knowing anything about SNMP, my learning curve was a tad
bit long. This sub-agent replaced the started task in Phase one with another
started task. This new started task loaded several sub-tasks at start up. Each
sub-task dealt with one system/sub-system (i.e. JES2, HSM, SYSTEM, etc). The
sole function of each of these sub-tasks was to collect data at regular
intervals. Then, I used Nimbus to do SNMPGets. The sub-agent would receive the
GET request from Nimbus, extract the appropriate data from a central location
and send the results back to Nimbus. Alerting was done based on the contents of
the variables returned.
This is a brief overview of how I incorporated the mainframe into Nimbus.
mike
>>> "Leitner, Timothy" <[EMAIL PROTECTED]> 10/3/2008 4:33 PM >>>
All,
Has anyone had experience that they can share with sending
syslog or snmp traps to outside products? We have Nimbus in-house from
Nimsoft. It is a central messaging system for thresholds and alerts. It
accepts SNMP traps or SYSLOG routing. We have worked on send alerts from
AIX, Intel, network and others but we need to send from our zOS systems
also.
Any ideas, examples, thoughts would be greatly appreciated.
Thank you in advance.
Tim Leitner
OSF Healthcare System
Manager, Technical Services
309-655-4883
==============================================================================
The information in this message is confidential and may be legally privileged.
Access to this message by anyone other than the addressee is not authorized. If
you are not the intended recipient, or an agent of the intended recipient, any
disclosure, copying, or distribution of the message or any action or omission
taken by you in reliance on it, is prohibited and may be unlawful. If you have
received this message in error, please contact the sender immediately and
permanently delete the original e-mail, attachment(s), and any copies.
==============================================================================
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
