Defining access methods for agents
- Extended agents (applies only to IBM Workload Scheduler)
- They are logical workstations related to an access method hosted by a physical IBM Workload Scheduler workstation (not another
extended agent). More than one extended agent workstation can be hosted by the same IBM Workload Scheduler workstation and use the
same access method. The extended agent runs on fault-tolerant agents defined using a standard
IBM Workload Scheduler workstation
definition, which gives the extended agent a name and identifies the access method. The access
method is a program that is run by the hosting workstation whenever IBM Workload Scheduler submits a job to an
external system.
Jobs are defined for an extended agent in the same manner as for other IBM Workload Scheduler workstations, except that job attributes are dictated by the external system or application.
Information about job running execution is sent to IBM Workload Scheduler from an extended agent using the job stdlist file. A method options file can specify alternate logins to launch jobs and check opens file dependencies. For more information, see the User's Guide and Reference.
A physical workstation can host a maximum of 255 extended agents.
- dynamic agents and IBM Z Workload Scheduler agents (z-centric)
- They communicate with external systems to start the job and return the status of the job. To run access methods on external applications using dynamic agents, you define a job of type access method.
- SAP
- z/OS
- Custom methods
- unixssh
- unixrsh
The UNIX™ access methods included with IBM Workload Scheduler, are described in UNIX access methods.
If you are working with dynamic agents, for information about defining IBM Workload Scheduler workstations, see the section that explains how to define workstations in the database, Workstation definition. For information about writing access methods, see Access method interface.
More information about access methods is found in Scheduling Job Integrations with IBM Workload Automation.