System documentation is one of the most overlooked processes by many organizations leveraging AS400. Most CTOs/CIOs don’t pay attention to complete system documentation because they don’t see moving away from the iSeries technology anytime soon due to sturdiness. Typically, documentation yields unfathomable results at the time of IT disasters.
What Needs Documenting?
General System Documentation: System data includes the hardware of the iSeries systems and its configurations, along with the server model and the operating system that is currently in use. Documentation on these can be crucial during IT disasters or technology upgrades.
DevOps: Documenting system components isn’t enough. Documenting the process is needed to make sure IT operations and development will continue to work in harmony. This includes documenting changes done to codes and other artifacts, user roles and responsibilities, network configurations, and deployment methodologies like shadow deployment, A/B testing deployment, etc.
Process Documentation: Documenting system manuals, task flows, user journey mapping, and workflow navigations information for new users during training.
Integration: Another major aspect that requires documentation is the integrations that have been implemented into the iSeries system. These include custom adaptors, integration standards, and types of integration (EDI, API, Webhooks, etc) that are used.
What are the benefits of AS400 Documentation?
Aid during Technology or Data Migration: One of the biggest advantages of having system documentation is reaped during technology or data migration. Integration details, code details, and network configuration among other things need to be documented for a successful migration. Since AS400/iSeries are reliable systems, most organizations don’t move away from them. But what companies don’t realize is most of the time applications run better on modern systems and the cloud has better security and applications run smoother and have better performance than on DB2. But when that time comes, migration isn’t a cakewalk due to lack of documentation.
Disaster Recovery: IT team of any organization must have a disaster recovery plan set up in case of an IT disaster. Most companies have a rudimentary backup setup in the event of an emergency. Since AS400 developers are on the verge of retiring or enjoying retirement and modern day developers don’t fully understand the legacy technology, it is imperative to document the entire system to avoid crises during IT disasters.
Staff Training:AS400 documentation is required when you hire new developers to manage the system, since the old ones are retired and the newer generations aren’t savvy with iSeries technology, a lack of documentation will be like handing a car over to a child.
Above are the reasons why CTOs/CIOs need to start paying attention to documenting their iSeries system.
How Nalashaa can help you?
Nalashaa has been working in the IBM i space for over a decade now and has a pool of IBM i skilled developers to deploy. Varying from basic support expertise to migration and modernization, Nalashaa helps you at every step. If your 2022 IT Roadmap involves iSeries documentation, drop us a note at firstname.lastname@example.org. We will take care of the rest.