Running a job

A job can be executed as follows:

  • Using the LN job daemon rc.startjobdm. You do not need to be logged on to LN to execute the job.
  • Using the rc.startjob shell command (UNIX platform). You do not need to be logged on to LN to execute the job.
  • Using the startjob.bat batch file (Windows platform). You do not need to be logged on to LN to execute the job.
  • Running in your own user environment. You must stay logged on to LN until the job is completed.

For more information, refer to Job execution and Job handling procedure.

Using the job daemon

A daemon is a program that permanently runs in the background. A daemon handles requests that are issued by other programs and is activated only when needed.

  1. Start the Job Data (ttaad5500m000) session and select the job.
  2. On the appropriate menu, click Queue Job. The job's status changes to In Queue.

If you cleared the Use External Sched check box in the Job Data (ttaad5100s000) session, the job is started at the scheduled date and time.

If you selected the Use External Sched check box in the Job Data (ttaad5100s000) session, you can start the job in one of the following ways:

  • Through an external job scheduler such as Maestro from UNISON, or through an external program such as a UNIX crontab.
  • In the Activate Job (ttaad5203m000) session.
  • Through the rc.startjob shell command (UNIX platform)
  • Through the startjob.bat batch file (Windows platform)

For more information, refer to Job execution and Job handling procedure.

Running the job in your own user environment (bshell)
  1. Start the Job Data (ttaad5500m000) session and select the job.
  2. On the appropriate menu, click Activate Job. The Activate Job (ttaad5203m000) session starts.
  3. Check the job data and click Activate to start the job.

If you scheduled the job for a specific date and time, the job starts at the specified time. The job's status changes to Waiting.

If you did not specify a time, the job starts immediately. The job's status changes to Running.

In both cases, you can close the Activate Job (ttaad5203m000) session only when the job is finished.

Related topics