Shared job data tables
Typically, each company stores its own basic job data. Therefore, a job runs for a particular company.
In a job, you can also run sessions in more than one company. You can run sessions in multiple companies when the job data tables of the associated companies are physically mapped to a single main company. You can use the session to link these job tables as logical tables to one physical table:
- Job Data (ttaad500)
- Sessions by Job (ttaad501)
- Job Input Variables (ttaad503)
- Job Daemon Indicator (ttaad505)
- Calendars (ttaad506)
- Dates by Calendar (ttaad507)
- Job Scheduling Lines (ttaad508)
- Job History (ttaad510)
- Job Session History (ttaad511)
- Job Session History (ttaad512)
Before you add a session to a job, you must check the company number. If a job applies to more than one company, you must switch to the other companies with the command. Define the job for each company. You can then define the job data for the other companies.