Need improved SMS initialization message for IPL automation

During an IPL, SMS issues the IGD020I message indicating that SMS has completed initializtion. Unfortunately, the SMS intialization does not include all of the SMS subfunctions (such as compression services, SMS VSM, etc.) since those subfunctions initialize asynchronously to the SMS kernel. As a result, there have been times when our IPL automation has failed because we rely on the IGD020I message to know when to start the primary sub-system (in our case, JES3). When JES3 starts prior to one or more of these SMS subfunctions and (usually in our case) a started task gets started, SMS will cause the started task to fail with a JCL error becasue one or more of these SMS subfunctions is not availaleble on the system where the started task is starting. We have been using a hard-coded wait time in order to allow what we think is enough time for all SMS subfunctions to initialize, but that is still an imperfect solution and there have been cases where we still have had failures because the wait time was insufficient. On the flip side, we are most likely causing a wait in our IPL sequence when it is not necessary.

In order to correct this deficiency, there should be a way to know when all SMS subfunctions are available (a new IGD* message), if not a seprate message for each subfunction and a list of what those subfunctions are in order to allow for proper automation of our IPL sequence. I cannot think of an alternative to a new message, but suggestions or alternate implementations are welcome--even something like an internal sub-system communication to tell JES3 (and JES2) that *all* of SMS has been intialized and is available.