No. In fact nothing went into SSMBEGUX. All we did was set the IPL_STATE in the STCTBL to 'UP' for each resource we wanted to be in the "BASE" system. Every other task we set the IPL_STATE to 'DOWN'. At IPL the sequence goes as follows:
1. Stateman initializes and copies IPL State to Desired State. This ends up with Base system tasks with a Desired State of UP and non-base system tasks with a desired state of IPL.
2. Anything with desired state of IPL is set to the current state which should be down.
3. The base system tasks start based on STCTBL_ACT.
4. Once the final task in the base system is UP the operators then issue the command SSM STARTSYS. This pause in the startup will allow you to perform maintenance tasks, etc. before the rest of the system comes up.
5. STARTSYS sets ALL desired states to UP. Since the base system tasks were already up, no harm no foul. All the tasks still listed as DOWN are now set to desired state of UP and follow the normal Stateman method.
6. Once all of the additional tasks are UP, the system is UP and ready to use.
Now, this is a two stage IPL with a Base System and Secondary System. If you want, you can create more commands similar to STARTSYS for each group of resources you wish to start. STARTDB2 would start your DB2 regions. STARTCICS would start the CICS regions*. If you use the TYPE column to categorize your resources these start commands could be as varied as the TYPE and could really multi stage an IPL.
*Note - do not confuse these with the REXX samples provided by CA for use with Stateman.