Considerations For Large Number TSS Commands In A Batch Job
search cancel

Considerations For Large Number TSS Commands In A Batch Job


Article ID: 252723


Updated On:


Top Secret


Is there an impact on Top Secret if a batch job is run to issue 83,000 TSS commands? Is there a limit or guidance on how many TSS commands can be put in a batch job so that Top Secret is not affected (or minimally impacted)?


Release : 16.0


- If you are using CPF, be sure the commands are issued with TARGET(=) so  they are only executed on the local system. To make the changes on the other systems, it is better to run the same job on all the systems with TARGET(=) for each command. Otherwise, with that many commands being CPF'd all at once, it could bring CPF to a halt. (Not to mention overflow the CPF recovery file.)                                                  

- If you are not using CPF (or specifying TARGET(=) on each command if you are using CPF), then, as far as we know, there are no recommended limitations for number of TSS commands issued in a batch job, but here are some things to watch out for. If the commands affect any in-core tables (PIE resources, RIE resources, ACID index, SDT, digital certs, ...) the job may take much longer than expected. Each command that changes a table content causes a new table to be created and the old table gets put on a freedom queue to be deleted after several timer cycles. Since much of the table storage is in the CSA we have throttles to keep us from taking over too much CSA, so if those throttles kick in then the job waits the appropriate timer cycles until enough storage can be freed to put us under our throttle limit. This depends on the mix of commands. It is recommended, if possible, to run the job during off peak hours.