Welcome at the SAP on IBM i weekly update! This time I’d like to share my thoughts about our kernel tool APYSIDKRN.
Every admin dealing with SAP on IBM i knows that kernel maintenance is a topic which is special for our platform. The main reason for this is the hybrid nature of our setup:
- Conventional IBM i objects like commands and menues live in libraries and offer all the pleasant aspects like prompting, online help, implicit syntax checks, execution on lists and many more.
- On the other hand, SAP kernels originate from a thinking that circles around binaries in a file system.
It is our platform team’s job, to bring this two worlds into a balance. Admins are assumed to prefer the conventional IBM i view, whilst the kernel’s core runs in the file system. In kernel releases newer than 7.00, APYSIDKRN is one central tool for this purpose. It is taking care of the admin’s environment to be in sync with objects in the file system. In addition, it helps to deploy those file system objects. Whilst admins on other platform need to extract every archive manually with SAPCAR into the correct location, APYSIDKRN knows the proper location and does this job for an arbitrary set of archives.
In short words, APYSIDKRN moves the complexity of kernel logistics from the admin to the code.
Here is a set of notes regarding APYSIDKRN that transport knowledge in opposition to the ones describing problems. It is not meant to be complete but to give an entry point for further reading and background information (SMP login needed):
As the development team intends to maintain a consistent format, editions of the series will continue to be published on my name. Set feeds accordingly if you are interested in following the series.