Invoking the batch interface

OPERTUNE allows you to invoke the batch interface from batch and from a REXX EXEC/CLIST.

Batch

The DDTBATCH member of the OPERTUNE control data set contains sample JCL that you can use to submit commands to OPERTUNE from batch. For example, this might be useful for setting a group of elements before running a workload and resetting them after the workload is complete. The person submitting the job must have the proper OPERTUNE authority to execute the commands.

Batch interface utility JCL

The batch interface checks each input command for the presence of a target specifier. The specifier is optional if only one OPERTUNE is active on the MVS system on which the job is running. If more than one OPERTUNE is active and you omit the target specifier, you will receive an error message

Issue commands as you would from any MVS console:

F opertuneID,command

• opertuneID is the OPERTUNE system profile name (if OPERTUNE is running as a started task) or the job name of the batch job (if OPERTUNE is running as a batch job)
• command is the command you want to issue

When using the batch interface, verify the following conditions:

• The OPERTUNE load libraries are specified in a STEPLIB DD statement, if they are not in the LNKLST.
• The SYSIN ddname contains the commands to be issued. A command in a column can be continued to the next line with a dash (-) designating a continuation of that command.
• The SYSPRINT ddname contains the command responses.

CLIST

The DDTBCLST member of the OPERTUNE CNTL library contains a sample CLIST from which you can execute a REXX/CLIST to invoke the batch interface for OPERTUNE.

Batch REXX/CLIST

Adding an archive log to the active list

The DDTKLOGU member of the OPERTUNE control data set is a utility that you can use to copy the content of an archive log data set to a predefined active log data set. This utility copies an archive log data set recorded in the subsystem BSDS before adding it to the list of active logs.

JCL to invoke the OPERTUNE copy log utility

To add an archive log to the active list, follow these steps:

1. Identify the name of the archive log data set you want to copy by listing the names of the archive logs in the BSDS; select option 6 from the OPERTUNE Operational Assist Menu.
2. Define the target active log data set (define two active log data sets if you are using dual logging). To define the active log data sets, use the Create Log Parameters panel, the CREATLOG command (see  Creating active logs ), or IDCAMS.

3. Run the Copy Log utility (DDTKLOGU) to copy the archive log to the target active log(s).

   Important

   Before copying from the archive log to the active log, you may need to allocate more space to the active log than was originally allocated.

4. Add the newly created active log(s) to the list of active log data sets, using the ADDLOG command (see  Adding-active-logs for command syntax). Use the LIKE keyword to specify the name of the archive data set identified in step 1. The new active log is added in RBA order, next to the current log.

   Important

   To prevent the subsystem from overwriting the active log containing archive data during a log switch, BMC recommends defining and adding a new set of active log data sets by using the ADDLOG command. Insert these new active logs directly after the active log. The new logs are used as a buffer between the current logs and the dearchived logs (added next to the current logs).