Manage binding agents


The Job Binding Services (JBS) of BMC AMI Ops Automation for Batch ThruPut provide control of job routing by binding jobs to needed resources, ensuring they run where and when resources are available. Users do not need to change their JCL to route jobs appropriately.

A binding agent must be defined before it can be activated. It can be activated in the JECL of a started task, or by operator command. (Jobs are binded to agents in JAL) In general once you have defined an agent it remains in the system until you explicitly remove it. You are much more likely to activate and deactivate binding agents on a regular basis.

Commands

To display...

Key...

define a binding agent

/JBS DEFINE agent-name PERM

display all binding agents and list all the jobs that are bound to them

/JBS Display AGENTS

display a specific binding agent and list all the jobs that are bound to it

/JBS Display AGENT agent-name

activate a binding agent

/JBS ACTIVATE binding-agentactivates the agent on the system where the command is issued

activate a binding agent on a specific system

/JBS ACTIVATE binding-agent SYS(member)

deactivate a binding agent

/JBS DEACTIVATE binding-agent only deactivates the agent on the system where the command is issued

deactivate a binding agent on a specific system

/JBS DEACTIVATE binding-agent SYS member

activate binding agents on all but one member

/JBS ACTIVATE binding-agent SYS(ALL) /JBS DEACTIVATE binding-agent SYS (member)

list jobs bound to any binding agent

/JBS Display JOBS

list jobs that are in JBS hold status, along with their associated Agents

/JBS Display HELD

display the Job Binding dependencies for a job

/JBS Display JOB job-id

unconditionally remove the specified job from Job Binding Services control

/JBS ABANDon job-idAll activate and deactivate requests no
longer apply to the job.

Example 1

Information
Example

/JBS DEFINE BIND.TEST PERMANENT
DTM6410I JBS DEFINE COMMAND SUCCESSFUL
DTM6420I JBS BINDING DISPLAY
BIND.TEST - STATUS=(INACTIVE)
SCOPE=(PERM,MULTIPLE)

Example 2

Information
Example

/JBS ACTIVATE BIND.TEST SYS(DOCT)
DTM6420I JBS BINDING DISPLAY
BIND.TEST - STATUS=(ACTIVE)
SCOPE=(PERM,MULTIPLE)
ACTIVE ON ALL

Example 3

Information
Example

/JBS DISPLAY AGENTS
DTM6420I JBS BINDING DISPLAY
APPL.AP - ACTIVE ON ALL
APPL.BK - ACTIVE ON ALL
APPL.MK - ACTIVE ON ALL
APPL.MKRPT - ACTIVE ON ALL
APPL.SI - ACTIVE ON ALL
BIND.TEST - ACTIVE ON DOCT

Example 4

Information
Example

/JBS DEACTIVATE BIND.TEST
DTM6420I JBS BINDING DISPLAY
BIND.TEST - STATUS=(INACTIVE)
SCOPE=(PERM,MULTIPLE)

Example 5

Information
Example

/JBS DISPLAY HELD
DTM6420I JBS BINDING DISPLAY
JOB07647 WLDC901 HELD BY JBS SYS=ANY
BIND.TEST - STATUS=(INACTIVE)
JOB07705 CLDX903 HELD BY JBS SYS=DOCT
BIND.TEST - STATUS=(INACTIVE)
JOB07707 BRDI872 HELD BY JBS SYS=DOCT
BIND.TEST - STATUS=(INACTIVE)
JOB07723 BRDX907 HELD BY JBS SYS=DOCT
BIND.TEST - STATUS=(INACTIVE)

Here you can see that four jobs are held because they are bound to agent BIND.TEST which is inactive.

Example 6

Information
Example

/JBS DISPLAY JOBS
DTM6420I JBS BINDING DISPLAY
JOB07634 HRDI8531 EXECUTING SYS=ANY
JOB07642 CRDC867 EXECUTING SYS=ANY
JOB07643 WLDI867 EXECUTING SYS=ANY
JOB07646 CRDX901 EXECUTING SYS=ANY
JOB07647 WLDC901 AWAITING EXEC SYS=ANY
JOB07705 CLDX903 AWAITING EXEC SYS=ANY
JOB07707 BRDI872 AWAITING EXEC SYS=ANY
JOB07708 CLDC872 AWAITING EXEC SYS=ANY
JOB07723 BRDX907 AWAITING EXEC SYS=ANY

All of these jobs are bound to binding agents, though not necessarily held by them.

Warning

Important

Jobs might be held by more than one binding agent; all of them need to be satisfied before BMC AMI Ops Automation for Batch ThruPut releases it.

ABANDON is recommended only if a binding agent is incorrectly applied in the first place, or no longer applies.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation for Batch ThruPut 22.4