by Blackthorn » Tue Mar 06, 2018 8:02 pm
Are these subordinate systems z/OS or something else, eg; Windows, Unix? If the latter, then the symphony file is a copy of the current plan (jobs to run, dependencies, etc) along with the "JCL", or more accurately the script if they are non-mainframe platforms. That is where the concept of fault tolerance comes from as in running the work on an FTA (Fault Tolerant Agent). Even if the link to the mainframe is lost, the jobs can continue to run on the remote platform.
If on the other hand, these subordinate systems are also z/OS lpars, then typically the JCL would be submitted from the system running the TWS controller. There is no file distributed to those systems, as far as I recall (although it's a while since I've done any TWS configuration work).
TWS does read all the JCL from the PDS job library in to it's own Vsam file prior to submission. This may be done either at the time the job is submitted (the default) or in advance, which can lead to performance gains if many thousands of jobs are involved.
- These users thanked the author Blackthorn for the post:
- scott b (Wed Mar 07, 2018 7:51 am)