Setting up access to target servers

Because the Job Scheduler agent runs outside of Adaptive Server, target servers consider it a remote user. Consequently, you must define each target server (even when the target server is the server where the Job Scheduler is installed) and login to the local server, which is where Job Scheduler is installed.

StepsSetting up access to target servers

  1. Create a directory services entry for each target server using dscp, dsedit or a text editor as appropriate to your directory services setup:

    target_servername�
       master tcp ether targetserver_machine port_number�
       query tcp  ether targetserver_machine port_number
    

    where:

    See the System Administration Guide, Volume 1, for more information on directory services.

  2. On the Adaptive Server running Job Scheduler, create an entry in the sysservers table for each target server on which you want to run a job. A target server can be remote or it can be the Job Scheduler server itself. In both cases, you must add an remote entry for the target server in the sysservers table.

    where:

  3. Add logins for Job Scheduler users using sp_addexternlogin:

    sp_addexternlogin target_servername, localname, remotename, remotepwd�
    go�
    

    where:

    NoteYou must add external logins for all users for all target servers, even if the target server is the server where Job Scheduler is installed.

    You can now create jobs, schedules, and scheduled jobs using stored procedures from the command line or using the Sybase Central ASE plug-in. See Chapter 5, “Command Reference,” for more information on Job Scheduler stored procedures. See Chapter 6, “Managing Job Scheduler in the Sybase Central ASE Plug-in,” for more information on using Job Scheduler with Sybase Central.