iSeries Monitoring Bot

Description:
The software at my company consists of various subsystems running on the IBM System i. These subsystems handle tasks such as batch and interactive jobs, which can have different statuses. For example, a batch job might block others due to errors, leading to delays and reducing work efficiency. Additionally, system overloads—such as reaching memory capacity or uncontrolled data growth—often go unnoticed because there are no automated warnings. This can result in data loss or system shutdowns, disrupting operations. Hardware failures are another risk, as they might remain undetected without manual checks, potentially causing interruptions. Currently, employees or service providers must manually identify these issues via command line. To address these challenges, I developed a standalone monitoring bot for systematic tracking of system parameters. The bot helps detect and resolve potential problems early, ensuring smoother and more efficient workflows. I also authored a comprehensive documentation for customers, enabling them to easily configure the bot via a simple configuration file.

Challenges faced:
Using an unfamiliar environment and database (IBM Session, DB2) was a significant challenge. Translating the IBM data and mapping it into Java code was particularly difficult due to the niche nature of the system and the lack of readily available information or resources.

What I learned:
- Gained familiarity with the IBM iSeries environment.
- Developed skills in working with limited information and resources.
- Improved my ability to communicate and collaborate with experienced niche developers.