BULKDISC

Purpose

The BULKDISC command is used to initiate a bulk discovery request. You can request a bulk discovery by issuing the BULKDISC command from your TSO session or from within a batch job. You can run a complete job discovery manually or each time a planning activity is performed (create, extend or replan), by setting the MONOPTS runtime option for the controller.

A request generated by the BULKDISC command is communicated to the controller as an event record processed by the event writer task of a tracker. The BULKDISC command can be issued from any z/OS® system that runs a controller from HCL Workload Automation for Z Release 3, or later. The command initiates a bulk discovery. While the bulk discovery is in progress, the current plan backup resource is locked to prevent other HCL Workload Automation for Z tasks from updating the same file concurrently.

Usage

You can invoke the BULKDISC command as a TSO command or by using a batch job that runs program EQQEVPGM. If you invoke BULKDISC as a TSO command, you must allocate the EQQMLIB data set to the address space of the TSO user, either by adding DD statements to the logon procedure, or by using the ALLOC command after TSO logon. In the TSO environment, error messages and trace records are sent directly to the terminal user. Messages are not delivered to indicate successful command completion.

Use of the BULKDISC command can be restricted with the fixed resource code BUL. The authority of the requester is verified by the subsystem name identified in the command if an AUTHDEF statement is defined for that subsystem. When SUBSYS(MSTR) is specified, all subsystems defined on the z/OS® system to which the command is directed attempt to verify the authority of the requester before an event is generated. It is possible to be rejected by one subsystem and accepted by another.

You must be defined with update authority to the BUL resource to use the BULKDISC command. Resource codes are described in Customization and Tuning. Check with your administrator to confirm that you have this authority before you use BULKDISC.

If the subsystem to which you direct the command is not active when the command is issued, an event is generated and queued in CSA together with other job-tracking events. In this case, the authority of the requester is verified using the class name specified in the AUTHDEF statement when the subsystem was last started. If the subsystem has not been started since a z/OS® IPL, no authority verification can be performed. For the bulk discovery to run successfully, the monitoring task must be active when the BULKDISC command is issued.

Format


1  BULKDISC?  TRACE (
2.1! 0
2.1 trace level
1 )?  SUBSYS (
2.1! OPCA
2.1 MSTR
2.1 subsystem name
1 )?  CRITJ

Parameters

CRITJ
If you work with IBM® Tivoli® Monitoring and specified the CRITICAL value in the MONPOL initialization statement, use this parameter to obtain all the available information about the critical jobs or the jobs in a critical path.
SUBSYS (MSTR | subsystem name | OPCA)
The name of the controller that the BULKDISC command is directed to. The name can be up to four characters long. The first character must be alphabetic; the remaining characters must be alphanumeric. All lowercase characters are converted to uppercase. If the SUBSYS keyword is omitted, the on-request BULKDISC command is directed to a subsystem called OPCA.

If you specify MSTR, the BULKDISC command is directed to all controller subsystems on the z/OS® system that the BULKDISC command was directed to.

Note: Specifying MSTR causes multiple bulk discoveries to occur, if more than one controller subsystem is active on the system.

Subsystem name is the name of the subsystem that the BULKDISC command is directed to. If the tracker and controller run in separate address spaces in your HCL Workload Automation for Z configuration, specify the name of the tracker subsystem in this parameter.

TRACE (level | 0)
Event tracing indicator. When a positive number is specified, a trace entry is created for each event generated by the BULKDISC command. The trace record is written to the message log file identified by ddname EQQMLOG. The record identifies the name of each receiving subsystem. The default value 0 does not generate trace records.

Examples

These two examples demonstrate how you can use the BULKDISC command in TSO, or in a batch job (using the batch program EQQEVPGM).

BULKDISC
Example 1 - TSO command 
ALLOC F(EQQMLIB) DA('OPC.MESSAGE.LIBRARY') SHR REUSE
 
BULKDISC SUBSYS(OPCA)
Example 2 - Batch job 
//BULKJOB  JOB (ACCOUNT),'Bulkdisc',CLASS=A
//STEP1    EXEC PGM=EQQEVPGM
//STEPLIB  DD DSN=OPC.LOAD.MODULE.LIBRARY,DISP=SHR
//EQQMLIB  DD DSN=OPC.MESSAGE.LIBRARY,DISP=SHR
//EQQMLOG  DD SYSOUT=A
//SYSIN    DD *
BULKDISC SUBSYS(OPCA)
/*