Deleting the AutoMeasure Template


To delete the AutoMeasure template that is used to used to specify the AutoMeasure measurement session parameters, use the following DELETE syntax:

DELETE {rrr|AUTOMEAS},TYPE=AUTOMEASURE|AUTOMEAS
TYPE

TYPE specifies the type of requests to be listed:

  • QUEUED for all queued requests
  • ACTIVE for all active requests
  • COMPLETE for all completed requests
  • ALL for all requests of any status
  • AutoStrobe only: DEFERRED for all deferred requests
  • AutoStrobe only: AutoStrobe for all AutoStrobe requests
  • AutoStrobe only: AUTOMEASURE or AUTOMEAS for the AutoMeasure template used to specify the parameters for the AutoMeasure measurement session

Important

When deleting measurement requests by job name, note that the DELETE command is system-wide in a multisystem environment. For example, the following DELETE command deletes all requests with the job name MYJOB on all active systems in the sysplex:

DELETE MYJOB

To delete Auto requests, you must use /ISPF, not the  command language. See Managing Requests from the AutoStrobe Status Panel.

The next time Strobe is initialized, if the AUTOMEASURE installation parameter is set to YES, Strobe will create a new AutoMeasure template, if AutoStrobe is licensed for the system on which Strobe is initialized and the AUTOMONITOR installation parameter is set to YES.

To delete the AutoMeasure template that has a request number of 123:

DELETE 123,TYPE=AUTOMEASURE

To delete the AutoMeasure template that has a request number of 456:

DELETE AUTOMEAS,TYPE=AUTOMEAS

Controlling the Measurement Session

Once Strobe has begun measuring a program, you can issue the SEND command to control the activity of the measurement session.

For example, specifying the SUSPEND operand for the SEND command allows you to momentarily stop a measurement session. Using the SWITCH operand you can switch to a new sample data set and release the previous data set. Then, using the START operand, you can resume the measurement session.

The following is the syntax for the SEND command:

SEND {jobname|rrr|*},

{STATUS|
STOP|
SUSPEND|
START|
SWITCH


QUIT}

[,GOMIN=gggg]
[,SAMPLES=ssssss]
[,{LIMIT={({nn,}{QUIT|STOP})}|NOLIMIT}]|

Specifying Operands for the SEND Command

You can issue the following Strobe operands for the SEND command:

STATUS

Displays the current status of sampling (active, suspended, or completed), the name of the current sample data set, and the current counts of total and execution samples.

STOP

Closes the current sample data set, making it available for report processing, and suspends the request. You can restart sampling later with a START operand.

SUSPEND

Stops the sampling process until you issue a START or SWITCH operand. The sample data set remains open so that additional samples can be appended to those already collected. Thus, the sample data set is not available for report processing.

START

Restarts the sampling process following a SUSPEND or STOP operand. When START follows a STOP operand, a new sample data set is allocated and opened. When START follows a SUSPEND operand, samples are written to the open sample data set. You can specify only new GOMIN, SAMPLES, and LIMIT operands for the new sample data set.

SWITCH

Closes the current sample data set so that it can be processed to produce a Performance Profile, and continues sampling, opening a new sample data set. You can specify new GOMIN, SAMPLES, and LIMIT operands for the new sample data set. (For more information, see Specifying New Sampling Control Operands below.) If you previously suspended the request, the SWITCH operand causes Strobe to begin sampling, opening a new sample data set.

QUIT

Terminates sampling, closes the current sample data set, and terminates the measurement task. To restart the measurement, issue an ADD command.

Specifying New Sampling Control Operands

When you use the SWITCH or START operand to begin a new measurement session, you can specify the GOMIN, SAMPLES, and LIMIT | NOLIMIT operands for the new measurement session. These operands are discussed in Specifying Sampling Controls.

Examples of the SEND Command

To close the current sample data set and suspend the measurement session for the job named MYJOB, code:

SEND MYJOB,STOP

For request 23, you want to close the current sample data set and begin sampling, saving the data into a new data set. The next session should be about 15 minutes long, and you want to conduct two more measurement sessions, then terminate the measurement request when the final target sample size is reached. Code:

SEND 23,SWITCH,GOMIN=15,LIMIT=(2,QUIT)

To suspend the sampling session, leaving the sample data set open, code:

SEND MYJOB,SUSPEND

Ending Strobe Command Language Operations

To signal the end of Strobe command language operations, use the END command. This command serves the same purpose as coding “/*“ in TSO and batch environments.

END

Example of the END Command

This example TSO session adds a request to measure a currently active job, lists all active requests, and terminates Strobe processing:

ADD MYJOB,STEP=*
LIST T=A
END

Submitting Commands with Strobe/ISPF

On any Strobe/ISPF panel displaying a command or option line, you can enter one of the following types of commands:

Issuing Operational Operations

To issue commands directly to Strobe, enter a period (.) followed by the command; for example:

.LIST 29

displays information about measurement request 29.

Displaying Message Text

To view the text of a message currently displayed on a Strobe/ISPF panel or menu, type “.M” in the panel’s COMMAND or OPTION field. To view the text of any Strobe message, type “.M” followed by a space and the message key in the panel’s COMMAND or OPTION field. For example:

.M 0109

displays the text associated with message STR0109.

To view all the messages produced in response to your last interaction with Strobe, type “.CVM”. Strobe displays the messages associated with the request.

 

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