Trigger Structures:
To stop cross triggering we use the schedule ID (SCHID) facility on CA-7. Using this, jobs can have up to 255  versions. We divide all the applications into groups. Each contains applications which share common jobs. We then allocate a different schedule ID number to each application to ensure they are insulated from each other.

On CA-7 you can define a trigger so it will only continue the chain if it is requested for one specific schedule ID. We do this to guarantee that cross triggering will not occur.  If the same job is needed twice within the same application, it is renamed to stop triggering loops. While this renaming is a pain, the User defines the rules governing the name changes so the new name can follow any site standards. Also the renamed job will point to the original JCL so only one member needed to be maintained.

PGM50-70:
Here we can see the three programs used to split the applications into groups and do any renaming.  The files PGM50REN and PGM70REN provide lists of any rename that occur.

I will talk about general work stations on the next page.