WMCPA iCON2025

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.

What happens if you try to delete everything in the IFS? Can I IPL my host partition while a guest is still running? How much damage can a limited user really do? All the questions you’ve wanted to know the answers to but were afraid to try on your own system. We’ve gathered questions, legends, and urban myths from around to community and tested them to see what happens when you do something unexpected to IBM i. Join us and see how much you really know about your system…and bring popcorn, because we might even try out some audience suggestions live.

TBD

Need a new environment for testing, development, or sandboxing? Creating a separate partition for these activities can ease administration by keeping your production environment clean and isolated. We will go over how to configure a new partition, install IBM i, and restore data so you can get that new project started fast.

• Ever wonder why your penetration tests never yield a failure on IBM i? It's because security generalists don't know how to test it properly. Steve has successfully breached many systems in less than five minutes and will show you how to stop him.
• Worse Practices in System Security: This session will explore the bad, ugly and ugliest of IBM i security misconfigurations so you can learn from others’ misfortunes.

Deploying IBM i Access Client Solutions to a large user base is far easier than doing the same with old Access for Windows, but it still takes some forethought and planning. There really is no “one size fits all” approach to this topic, so this session will cover what you’ll need to know when planning for your own ACS deployment and how do determine the best method for your environment.

TBD