Scope: JES2 Node

Duration: Until redefined or the Control File is reformatted.

JBS DEFINE
JBS DEF

[? | HELP]
category INCOMPAT(incompat-list)
category NAME(cat-name)
category INCOMPAT(incompat-list) NAME(cat-name)

? | HELP

Requests the command syntax from HELP.

category

Is either a single decimal digit from the range 1-9 or a Category name, indicating the Incompatibility Category that is being defined.

INCOMPAT(incompat-list)

Specifies one or more incompatibility definitions for this Category.

  • incompat-list - Is one or more incompatibility definitions, separated by commas, using the following form:

  • n[n...]type

    n[n...]Is up to ten digits, each digit representing an Incompatibility Category.
    typeIs a single character code indicating how the preceding Incompatibility Categories are to be handled, and must be one of:

NAME(cat-name)

Indicates that you want to give this Incompatibility Category a name.

  • cat-name - Is a name consisting of 1-8 alphabetic, numeric, or national characters, identifying the Incompatibility Category.

Examples:

JBS DEFINE 1 INCOMPAT(4F)
JBS DEFINE 3 INCOMPAT(12N,5W,78F)

Notes:

  • Category 0 is the default Category for Agents that have not been assigned a Category. It cannot be defined or named. You can, however, use Category 0 in an INCOMPAT keyword.
  • All Categories are compatible with all other Categories until defined otherwise.
  • When two conflicting definitions are given, the last one encountered prevails. For example:
    JBS DEFINE 3 INCOMPAT(4W)
    JBS DEFINE 4 INCOMPAT(3F)
    results in jobs being failed if they attempt to bind to Agents from both Category 3 and Category 4.
  • A Category can be defined as incompatible with itself. This has the effect of limiting a job to only one Agent of that Category.
  • Altering a Category for an existing Agent affects only jobs that are analyzed after the change is made. Jobs already awaiting execution or being held for execution are not affected.