NSK Jobs

Use NSK Jobs to run scripts on NSK platforms. NSK Jobs can run independently or they can be added to a Job Group (JOBG) or to a Workflow. For more information about the integration between the Automation Engine and NSK, see AE and NSK.

Defining NSK Jobs

An NSK Job definition is made up of the following pages:

• Standard pages that are always available, no matter what type of object you are defining:
  • General Page
  • Version Management Page
  • Documentation Page
• Additional pages that are always available for executable objects:
  • Process Pages
  • Attributes Page
  • Output Pages
  • Variables Page
  • Prompt Sets Page
  • Rollback Page
• The NSK page described here.

General Settings Section

• Job Type

  There are three types of NSK jobs:

  • Guardian - TACL commands
  • OSS - UNIX commands (osh shell)
  • NetBatch - NBEXEC scripts

• Priority

  The priority with which the job should be executed. It is a value between 1 and 199, where 1 is the highest and 199 the lowest priority.

  Note: The priority does not affect the processing order of tasks, it only serves to define their starting order. The task with the higher priority is started first. For tasks with the same priority, the Fist In/First Out (FIFO) principle applies.

• CPU

  Number of the CPU on which the job will run. You can select a value between -1 and 15. If you select -1, the system selects a CPU.

• Virtual Terminal

  Name of the HP NonStop Server.

  It can contain up to 26 alphanumeric characters and the separators \ $ . # and -.

  Inputs and outputs can be made on this device, therefore it is not possible to specify a disk file because this might cause error messages. Physical or virtual terminals or the corresponding processes (e.g. subtype 30 processes) can be used instead.

  Use the keyword "none" to suppress the values defined in the INI file.

Job Report Section

For information on the Job Report section, see Job Reports.

See also:

Jobs (JOBS)