Unattended Playback: Submitting the Job (MQ)

Once the job is prepared, submit it in one of the following ways:

  • Submit the job from the ISPF Edit session to execute it immediately. Type SUB on the Command line and press Enter.
  • Schedule the job to run at a specific time. Refer to your job scheduler’s documentation for help.

After the job has completed, review the return codes to see if playback completed successfully or to determine the cause of failure.

Review playback return codes

Performance Test for WebSphere MQ reports an MVS return code for each step of a playback job. The return code is a numeric value that indicates whether the job step completed successfully and to what degree. See Playback Return Code Descriptions for a complete list of MQ playback return codes.

Important

For more definitive playback results, you can add REXX logic to a script to return a specific value based on criteria you supply. This is called a “custom” return code. Refer to the Scripting-Reference to learn how to define custom return codes.

The location of your return codes is dependent on your system configuration. On some systems, with the correct job statement parameter, return codes appear in the user’s TSO session. On others, they are written to a job log. If you need help locating your return codes, see your system administrator.

Performance Test for WebSphere MQ also writes the following informational messages to the SYSPRINT upon job completion.

TCPSRPL-0051I    Play complete for Replay=1 - Return Code=xxxx.

TCPPBMN-0007I    Maximum return code=xxxx

Message TCPSRPL-0051I reports the return code from the indicated playback session (Replay). Performance Test for WebSphere MQ produces one of these messages for each playback session in the job step. For example, the following playback statements result in six playback sessions (Playback Sessions for a MQGROUP Statement with COUNT(2) REPEAT(3)) and therefore, six TCPSRPL-0051I messages:

MQGROUP COUNT(2) REPEAT(3)
SCRIPT(TEST)

Playback sessions for a MQGROUP statement with COUNT(2) REPEAT(3)

Repeat

Count 1

Count 2

1

Replay=1

Replay=2

2

Replay=3

Replay=4

3

Replay=5

Replay=6

Message TCPPBMN-0007I reports the maximum return code from all of the playback sessions in the job step. This is the value that Performance Test for WebSphere MQ returns as the job step completion code.

Important

The job step completion code can be tested with the COND parameter on a JCL EXEC or JOB statement.

If the MQGROUP statement contains multiple scripts, Performance Test for WebSphere MQ returns the value set by the last script processed. Incidentally, playback terminates MQGROUP processing if it encounters a non-zero return code. For example, Performance Test for WebSphere MQ reports the return code from the LOGOFF script in the following MQGROUP, unless LOGON or TEST produce a non-zero return code.

MQGROUP
   SCRIPT(LOGON)
   SCRIPT(TEST)
   SCRIPT(LOGOFF)

Playback return code descriptions

Performance Test for WebSphere MQ writes the following information to SYSPRINT:

  • A return code message for each playback session in the job step.
  • A message indicating the maximum return code for the job step.
  • Playback status, warning, and error messages.

Important

It also writes a Playback Error Summary report to the location specified on the ERRORLOG DD in the playback JCL. See Troubleshooting with the Playback Error Summary for detailed information.

If you receive a non-zero return code, review the return code description provided in the following table. Then review the warning and error messages to determine the cause of the problem. Refer to Messages-and-Codes for help with error resolution.

Performance Test for WebSphere MQ internal return codes

Code

Description

0

All scripts ran successfully without errors.

4

Playback ended due to one of the following:

  • An invalid script record was encountered. Review the playback errors to determine which record caused the issue, then edit the script record.
  • An invalid CONNECTION_ID was encountered. Edit the script to repair the incorrect connection ID.
  • A REXX initialization error was encountered. Refer to your REXX documentation for help with initialization errors.

8

Playback ended due to one of the following:

  • A file allocation error occurred. Review the allocation parameters in the playback job. If they are correct, contact your systems administrator.
  • A file could not be opened. Make sure you have authority to access all of the files specified in the job and that the files are not in use.
  • A file could not be read. Maker sure you have authority to read all of the files specified in the job.
  • A file could not be written. Make sure you have authority to write to all of the files specified in the job.
  • A script file was not found. Make sure the member names specified on the SCRIPT statements are accurate and exist and that the DSN provided on the SYSLIB DD parameter is accurate.

  • Performance Test

     for WebSphere MQ was unable to access or read the internal cache. This could happen for a variety of reasons. For example, if the memory was corrupted. Contact your system administrator. Note: Removing the CACHON parameter from the CONTROL statement may resolve the error, but it will not correct any system issues.

  • Performance Test

     for WebSphere MQ was unable to write to the internal cache. This could happen for a variety of reasons. For example, the cache is full. Contact your system administrator. Note: Reducing the size of the job may resolve the issue, but it will not correct any system issues.

  • An invalid control card was encountered. Correct the job SYSIN.

12

Playback is terminated due to a system failure. For example, if you are not licensed to use Performance Test for WebSphere MQ, or no OMVS segment is available. Contact your system administrator.

100

Playback is terminated because the playback job does not include an ERRORLOG DD statement. Insert an ERRORLOG DD statement before the SYSOUT DD in the playback JCL.


Important

You can add REXX logic to a script to return a specific value based on criteria you supply. For example, add logic to evaluate application message content and return a specific value if the content is incorrect. Refer to the Scripting-Reference to learn how to define custom return codes.


 

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