In days gone by the IBM Supplied program QSTRUP combined with a couple options on CHGIPLA was good enough for most IBM i shops. It started what seemed to be needed and anything else we stumbled through after each IPL. When it was time to shut down a PWRDWNSYS or ENDSBS command took down whatever was running. We were happy.
Today though we often see dozens of subsytems running many web servers, other needed batch jobs and services. We see monitors and queue processing jobs and many writers. For security purposes we should be starting only the TCP servers that we need, not all of them. Likely we should not start IPV6 and start things in sequence as well.
Further considerations may be needed in an HA environment. These include not starting jobs until iASPS are available and starting different IP interfaces and services depending on production or backup mode of the server. We may want to handle special startup modes while doing PTFs, backups or other system maintenance.
In this session we will work with customizing that startup. We’ll discuss staring PASE jobs with QSH, web server jobs and more. We’ll discuss prestart jobs and autostart jobs. And finally we will also work with sequencing the shutdown of the system. As part of this we’ll discuss some simple ways to know what needs to be shut down and smoothly handling that.
1) Learn how to control which startup program will run on your IBM i.
2) Examine the various servers to start and how to control them.
2) Learn options for starting different services.
3) Consider ways to control the startup of your server in different operting modes.
4) Understanding an orderly shutdown of your IBM i server.
IBM i System Administrators