> SHUTTRAP could be easily modified to run as a CMS MT root child > process. > The new code would run as a separate process within CMS and not interfere > with concurrent processes. I use the "root child" trick to run CMS > commmands > as "background tasks". There are some restrictions for "background > tasks", > but SHUTTRAP could be coded to avoid them.
Neat. That would probably handle the CMS-based WWW servers, or other CMS MT widgets nicely. > No modification to CMS needed. GCS would be another story, however. Since GCS is derived from MVT, does anyone know what the MVS world does with the shutdown signal? I wonder if any of that code could be "borrowed". -- db
