Use this command to display a summary of the backlog of jobs on the work queue at your BDT subsystem. This command also displays the number of active jobs on the work queue at your BDT subsystem, and BDT’s use of sessions. The jobs displayed are file-to-file jobs for which your file-to-file node is the global node, and outbound NJE jobs. This command will not display complete information for inbound NJE jobs.

                            .-----------------------------.   
                            V                             |   
>>-prefix--+-INQUIRY-+--,B----+-------------------------+-+----><
           '-I-------'        +-+-,ORIGIN-+--=node-name-+     
                              | '-,ORG----'             |     
                              +-,TO=node-name-----------+     
                              '-,FROM=node-name---------'     

prefix

is the prefix that is appropriate for your console or terminal. Do not use a prefix when submitting commands in a batch job.

B

specifies that the backlog of jobs is to be displayed.

ORIGIN=node-name or ORG=node-name

displays the backlog of jobs submitted at node-name for which your BDT subsystem is the source or destination node. Do not use more than one node name.

TO=node-name

displays the backlog of jobs that transfer data to node-name from your BDT subsystem. The job can have been submitted at your BDT subsystem or at node-name. If you specify your node for node-name, this displays jobs transferring data to that node from any other node. Do not use more than one node name with this parameter.

FROM=node-name

displays the backlog of jobs that transfer data from node-name to your BDT subsystem. The job can have been submitted at either node. If you specify your node for node-name, this displays jobs transferring data from that node to any other node. Do not use more than one node name with this parameter.

If you do not specify ORIGIN, TO, or FROM, this command displays all jobs backlogged at your work queue.

1. To see the backlog of file-to-file jobs for which your file-to-file node is the local node, use SEND to send the I,B command to the nodes that are global to your file-to-file node. Use the name of your file-to-file node for node-name.
2. The list below shows various combinations of the TO, FROM, and ORIGIN keywords. For each set of keywords, there is a description of the jobs whose statistics will be included in the totals displayed in the messages.
   You do not need to use the keywords shown in [ ]: these are defaults forced by the combination of the other keywords. For example, in the first item, you would need to use only the TO= keyword.

   TO=your-node [FROM=any] [ORIGIN=either]

   specifies that the jobs transferring data to your node from any other nodes be displayed. The jobs can have been submitted at any node.

   [TO=any] FROM=your-node [ORIGIN=either]

   specifies that the jobs transferring data from your node to any other nodes be displayed. The jobs can have been submitted at any node.

   [TO=any] [FROM=any] ORIGIN=your-node

   specifies that the jobs submitted at your node be displayed. The jobs can transfer data either to or from your node.

   TO=your-node FROM=other-node [ORIGIN=either]

   specifies that the jobs transferring data to your node from another node be displayed. The jobs can have been submitted at either node.

   TO=other-node [FROM=your-node] [ORIGIN=either]

   specifies that the jobs transferring data to another node from your node be displayed. The jobs can have been submitted at either node.

   TO=your-node [FROM=any] ORIGIN=your-node

   specifies that the jobs submitted at your node, and transferring data to your node from any other node, be displayed.

   [TO=any] FROM=your-node ORIGIN=your-node

   specifies that the jobs submitted at your node, and transferring data from your node to any other node, be displayed.

   TO=your-node FROM=your-node [ORIGIN=your-node]

   specifies that the jobs that transfer data within your node, (internal transfer jobs), be displayed.

   Note: If you want to display a summary of all jobs transferring data to a node at your BDT subsystem and also a summary of all jobs transferring data from a node at your BDT subsystem, you must use two separate commands: I,B,TO=your-node and I,B,FROM=your-node.

   TO=your-node FROM=other-node ORIGIN=your-node

   specifies that the jobs submitted at your node, and transferring data from another node to your node, be displayed.

   TO=your-node FROM=other-node ORIGIN=other-node

   specifies that the jobs submitted at another node, and transferring data from that node to your node, be displayed.

   TO=other-node FROM=your-node ORIGIN=your-node

   specifies that the jobs submitted at your node, and transferring data from your node to another node, be displayed.

   TO=other-node FROM=your-node ORIGIN=other-node

   specifies that the jobs submitted at another node, and transferring data from your node to that node, be displayed.

1. Using an F id prefix, display the backlog of jobs submitted at node OTHER and going either to or from your BDT subsystem. The identifier of BDT (for use in the prefix) is A1.

   F A1 I,B,ORG=OTHER

   Result:

   BDT8697  ORIGIN  FROM  TO   OPER  URS   DTC  ACTIVE  QUEUED  TOTAL
   BDT8697  OTHER              0001  0000  0007  0014    0003    0025
   BDT8696  SESSIONS=0100  LIMIT=0150

2. Using a prefix of *S,BDT, display the backlog of jobs being sent to your BDT subsystem from node ELSE1.

   *S,BDT,I,B,FROM=ELSE1

   Result:

   BDT8697  ORIGIN  FROM  TO   OPER  URS   DTC  ACTIVE  QUEUED  TOTAL
   BDT8697          ELSE1      0002  0000  0004  0030    0012    0048
   BDT8696  SESSIONS=0100  LIMIT=0150

3. Using an F id prefix, display the backlog of jobs waiting to be sent to node THEM2 from your BDT subsystem. The identifier of BDT (for use in the prefix) is A1.

   F A1 INQUIRY,B,TO=THEM2

   Result:

   BDT8697  ORIGIN  FROM  TO   OPER  URS   DTC  ACTIVE  QUEUED  TOTAL
   BDT8697               THEM2 0000  0001  0003  0010    0009    0023
   BDT8696  SESSIONS=0080  LIMIT=0100

4. Using a prefix of *S,BDT, display the backlog of jobs being sent to your BDT subsystem from node THERE, which were submitted at node THERE.

   *S,BDT,I,B,ORIGIN=THERE,FROM=THERE

   Result:

   BDT8697  ORIGIN  FROM  TO   OPER  URS   DTC  ACTIVE  QUEUED  TOTAL
   BDT8697  THERE   THERE      0002  0000  0003  0008    0002    0015
   BDT8696  SESSIONS=0100  LIMIT=0120

5. Using a prefix of BDT, display the backlog of jobs waiting to be sent from the node in your BDT subsystem named MYNOD, to any other node, that were submitted at MYNOD.

   BDT,I,B,FROM=MYNOD,ORIGIN=MYNOD

   Result:

   BDT8697  ORIGIN  FROM  TO   OPER  URS   DTC  ACTIVE  QUEUED  TOTAL
   BDT8697  MYNOD   MYNOD      0003  0000  0012  0010    0008    0033
   BDT8696  SESSIONS=0106  LIMIT=0150

6. Using a prefix of *S,BDT, display the backlog of internal transfer jobs waiting. (Internal transfer jobs transfer data from one data set at your node to another data set at a node in your BDT subsystem.) Your node is HERE0.

   *S,BDT,INQUIRY,B,FROM=HERE0,TO=HERE0

   Result:

   BDT8697  ORIGIN  FROM  TO    OPER  URS   DTC  ACTIVE  QUEUED  TOTAL
   BDT8697          HERE0 HERE0 0000  0000  0000  0002    0000    0002
   BDT8696  SESSIONS=0106  LIMIT=0150