Part 7: ThruPut Manager integration with Strobe


This topic describes how to get strobe measurement using /*STROBE Card

BMC ThruPut Manager is now capable of understanding Strobe measurement requests made from the batch job. The requests are made in the JCL by the addition of one or more /*STROBE JECL statements in the JCL of the job to be measured.

The JECL statements can be inserted anywhere in the job's JCL except in an instream PROC.

The strobe card is coded as follows:

/*STROBE [stepname],[program],[duration],[samples],[email-address]

Note that all parameters are optional.

For detailed information, see JECL-Reference-Guide.

Sample of a job using /*STROBE statements

An example of a JOBSTREAM containing /*STROBE statements:

//TSTROBE7 JOB (RSI),’STROBE TESTING’
/*JOBPARM L=999,ROOM=MVSS,S=*
/*STROBE   GTP0.STEP0,DTMGTP,1,30000,JOHN.SMITH@BMC.
COM
/*STROBE   GTP1.STEP0,DTMGTP,1,30000,JOHN.SMITH@BMC.
COM
/*STROBE   GTP2.STEP0,DTMGTP,1,30000,JOHN.SMITH@BMC.
COM
/*STROBE   GTP0.STEP1,DTMGTP,1,30000,JOHN.SMITH@BMC.
COM
/*STROBE   GTP1.STEP1,DTMGTP,1,30000,JOHN.SMITH@BMC.
COM
/*STROBE   GTP2.STEP1,DTMGTP,1,30000,JOHN.SMITH@BMC.
COM
/*STROBE STEP2,DTMGTP,1,30000,JOHN.SMITH@BMC.COM
//*
//XGP PROC
//GTP0 EXEC PGM=DTMGTP,REGION=64M,TIME=1439,
// PARM=’1X50C60S50C’
//TEMPDS DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUDUMP DD SYSOUT=*
//*
//GTP1 EXEC PGM=DTMGTP,REGION=64M,TIME=1439,
// PARM=’1X50C60S50C’
//TEMPDS DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUDUMP DD SYSOUT=*
//*
//GTP2 EXEC PGM=DTMGTP,REGION=64M,TIME=1439,
// PARM=’1X50C60S50C’
//TEMPDS DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUDUMP DD SYSOUT=*
// PEND
//*
//*
//STEP0 EXEC XGP
//STEP1 EXEC XGP
//STEP2 EXEC PGM=DTMGTP,REGION=64M,TIME=1439,
// PARM=’5C6S5C’

Output from sample program in the log of the job

The /*STROBE statements are converted by BMC ThruPut Manager and passed to the program STRBGM50. STRBGM50 does the actual queuing of the measurement requests.

Using the STRBADD1 proc in your job would create similar output but it would go to SYSPRINT. When using /*STROBE statements there is no SYSPRINT so it is captured in the job's LOG.

Output messages are produced in the JES joblog of the job. For the sample JCL the output would look like this:

REQUEST=ADD
TYPE=Q
JOBNAME=TSTROBE7
STEPNAME=STEP0
PROCSTEP=GTP0
PROGRAM=DTMGTP
DURATION=1
SAMPLES=30000
EMAIL=JOHN.SMITH@BMC.COM
END
STRGM1005 DEFAULTS LOADED FROM STROBE PARMLIB FOR:
       ENVIRONMENT, HOST, PORT, JOBCARD, NOTIFY, LOADLIB,
OVERWRITE, CODEPAGE
STR6300I Input = ADD TSTROBE7,STEP=STEP0.GTP0,PROGRAM=DTMGTP,
GOMIN=1,SAMPLES=30000,LIMIT=(1,QUIT),
  RJCLFILE=(_YES_),INITBY=AD
STR6261I 0342 TSTROBE7 QUEUED STEP=STEP0.GTP0 PGM=DTMGTP
CREATED=(17:25:02 08/22/2017) GOMIN=1 SAMPLES=30000
  LIMIT=(1,QUIT)
STR6261I EXPIRATION=(08/29/2017) INITBY=AD
STR6130I ADD operation completed

For information on the error messages produced by the Strobe program ,see STRBGM50: DTMSTRB00 and DTMSTRB02.

 

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