You are on page 1of 274

Strobe Messages Guide

Release 4.3

ii

Strobe Messages Guide

Please direct questions about Strobe or comments on this document to: Strobe Customer Support http://go.compuware.com/

This document and the product referenced in it are subject to the following legends: Copyright 1984-2011 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States. U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation. This product contains confidential information and trade secrets of Compuware Corporation. Use, disclosure, or reproduction is prohibited without the prior express written permission of Compuware Corporation. Access is limited to authorized users. Use of this product is subject to the terms and conditions of the users License Agreement with Compuware Corporation. Strobe, AutoStrobe, and iStrobe are trademarks or registered trademarks of Strobe. AD/Cycle, BookManager, CICS, DB2, IBM, IMS/ESA, Language Environment, MQSeries, VisualGen, and VTAM are trademarks of International Business Machines Corporation. Microsoft is a registered trademark of Microsoft Corporation. Windows, Windows NT, and Windows 98 are trademarks of Microsoft Corporation. Adobe Reader is a trademark of Adobe Systems Incorporated in the United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective owners.

Doc. CWSTMX4C November 8, 2011

iii

Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v How This Manual Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v How to Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Strobe Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Strobe Option Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Other Compuware Application Performance Management Products . . . . . . . . . vi iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi SQL Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Compuware Strobe Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Compuware Go Customer Support Website . . . . . . . . . . . . . . . . . . . . . . . . vii Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Corporate Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Compuware APM Service Offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii APM Installation Assurance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii Application Performance Management Consulting . . . . . . . . . . . . . . . . . .viii Application Performance Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Message Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1 Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Message Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Return Codes and Severity Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 ABEND Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Viewing Message Descriptions with Strobe/ISPF . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Error Recovery and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Chapter 2. Messages Produced by the Installation Program . . . . . . . . . . . . . . . . 2-1 Chapter 3. Messages Produced by Strobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Messages Returned by the Measurement Task . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Messages Returned by the Strobe Indexer Programs . . . . . . . . . . . . . . . . . . . . 3-18 Messages Returned by the Strobe History Manager . . . . . . . . . . . . . . . . . . . . . 3-25 Messages Returned by AutoStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31 Messages Returned by the Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43 Online Reporter Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59 Sample Dataset Utility Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60 Messages Returned by Strobe for CA Gen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60 SQL Analysis Messages Returned by the Reporter . . . . . . . . . . . . . . . . . . . . . . 3-61 Messages Returned by the Strobe SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64 Messages Returned by Data Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77 Messages Returned in Response to Sampling Control Commands . . . . . . . . . 3-92 Messages Returned by the Session Management Facility. . . . . . . . . . . . . . . . . 3-93 Additional Strobe Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139 Messages Returned by the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . 3-144 Messages Returned by the Session Management Facility for AutoStrobe . . . 3-149 Messages Returned by Strobe/ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-157

iv

Strobe Messages Guide

Messages Returned by Attribution Data Collectors . . . . . . . . . . . . . . . . . . . 3-221 Messages Returned by Strobe SQL Analysis . . . . . . . . . . . . . . . . . . . . . . . . . 3-236 Chapter 4. Abend Codes Returned by Strobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . Strobe Programmed Terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Function Codes Returned by Strobe Session Manager . . . . . . . . . . . . . . . . . . . ABEND Codes Returned by the Strobe SQL Agent . . . . . . . . . . . . . . . . . . . . . . 4-1 4-1 4-4 4-6

Introduction

Intro

This manual describes the messages and abnormal termination (ABEND) codes produced by the Strobe Application Performance Measurement System, a program product designed for IBM z/OS systems. It lists each message, followed by probable causes, the Strobe system response, and the recommended course of action. For each ABEND code, the manual provides the code number and describes the probable cause of the ABEND.

How This Manual Is Organized


Chapter 1, Overview explains where to find Strobe messages, how to interpret them, and how to act on them. Chapter 2, Messages Produced by the Installation Program lists Strobe installation messages in numerical order by message number. Chapter 3, Messages Produced by Strobe lists the messages in numerical order by message number and groups them by the component of the Strobe system that issued the message. Chapter 4, Abend Codes Returned by Strobe describes abnormal termination (ABEND) codes, lists them numerically by code number, and identifies the reason that the ABEND occurred.

How to Use This Manual


Use this manual to interpret Strobe messages and ABEND codes. You can also view message explanations online with the Strobe/ISPF Online Message Facility, Option M from the Strobe/ISPF Strobe Options menu.

Strobe Library
The Strobe base product manuals include: Strobe Interpretation and Analysis User Guide, document number CWSTGX4C The Strobe Interpretation and Analysis User Guide explains how to decide which programs and online regions to measure, when to measure them, and how to interpret the reports in the Strobe Performance Profile. Strobe Messages Guide, document number CWSTMX4C The Strobe Messages Guide lists all messages and abnormal termination (ABEND) codes, describes how to interpret them, and in many cases suggests a corrective action. Strobe Installation and Customization Guide, document number CWSTIX4C The Strobe Installation and Customization Guide explains how to install and maintain Strobe. Strobe User Guide, document number CWSTUA4C The Strobe User Guide explains how to use Strobe and AutoStrobe to measure application performance.

vi

Strobe Messages Guide

Strobe Option Manuals


The separate Strobe option manuals have been combined into a single Strobe Options Guide, document number CWSTUO4C. This manual describes the optional features of the Strobe Application Performance Measurement System. The manual is divided into parts, with each part describing measurement concepts applicable to, and specific data made available by, each of the following options: Strobe Strobe Strobe Strobe Strobe Strobe Strobe Strobe Strobe Strobe Strobe for Adabas/Natural for Advantage CA-IDMS for CA Gen for CICS for DB2 for IMS Interface for Java for WebSphere Application Server for WebSphere MQ for UNIX System Services.

Online Documentation
Strobe manuals are available in HTML, Adobe Acrobat PDF format, and IBM BookManager format, on CD-ROM and at the Compuware Go customer support Website at http://go.compuware.com.

Online Help
Strobe products provide the following online information: Strobe/ISPF Online Tutorials, Option T from the Strobe/ISPF Strobe Options menu Strobe/ISPF Online Message Facility, Option M from the Strobe/ISPF Strobe Options menu

Other Compuware Application Performance Management Products


The following products work in conjunction with the Strobe Application Performance Measurement System. These tools extend the benefits of application performance management (APM).

iStrobe
iStrobe enables you to view and analyze Strobe Performance Profile data on a workstation using a standard Web browser. Easy to install and easy to use, iStrobe guides you through the performance analysis process and offers recommendations for improving performance. iStrobe simplifies the performance analysis of applications that you measure with Strobe. For more information on iStrobe, see the iStrobe online help.

SQL Analysis
For users of iStrobe and Strobe for DB2, this option provides access path analysis and database and SQL coding recommendations for DB2 applications. SQL Analysis pinpoints the most resource-consumptive static or dynamic SQL statements, explains why these statements might be inefficient, and provides recommendations for improving the

Introduction

vii

performance of the DB2 application. For more information on SQL Analysis, see the Strobe User Guide.

Compuware Strobe Customer Support


Compuware provides a variety of support resources to make it easy for you to find the information you need.

Compuware Go Customer Support Website


You can access online information for Compuware products via our Compuware Go customer support Website at http://go.compuware.com. Compuware Go provides access to critical information about your Compuware products. You can review frequently asked questions, read or download documentation, access product fixes, or e-mail your questions or comments. The first time you access Compuware Go, you are required to register and obtain a password. Registration is free. Compuware now offers User Communities, online forums to collaborate, network, and exchange best practices with other Compuware solution users worldwide. To join, go to http://groups.compuware.com.

Contacting Customer Support


Phone
USA and Canada: 1-800-538-7822 or 1-313-227-5444. All other countries: Contact your local Compuware office. Contact information is available at http://go.compuware.com.

Web
You can report issues via the Quick Link Create & View Support Cases on the Compuware Go home page. Note: Please report all high-priority issues by phone.

Mail
Compuware Customer Support Compuware Corporation One Campus Martius Detroit, MI 48226-5099

Corporate Website
To access Compuwares site on the Web, go to http://www.compuware.com. The Compuware site provides a variety of product and support information.

Compuware APM Service Offerings


For North American customers, for information about current service offerings, please contact your local Compuware sales office or call Compuware Corporate Headquarters at 1-800-compuware (266-7892). You may also visit Compuwares Mainframe Application

viii

Strobe Messages Guide

Performance Management page at http://www.compuware.com/mainframesolutions/mainframe-application-performance.html. For other international customers, please contact your local Compuware office or Strobe supplier for a complete list of Services offerings.

APM Installation Assurance


The APM Installation Assurance service assists you in planning for, installing, customizing and using APM products. The service will help you maximize the value and benefits derived from the APM product family. Consulting engineers work closely with your IT personnel to understand your operating environment and your organizations APM goals. The engineer will assist you in developing a customization and installation plan for Strobe and iStrobe. The engineer will oversee the installation process and verify product readiness. The engineer will also help set up AutoStrobe measurement request schedules, request groups, history records, measurement requests, and will verify the installation of Strobe SQL Analysis. With APM Installation Assurance services, your organization can immediately maximize the value received from your investment in the APM product family. You will also benefit from a fully customized installation that will enhance the product functionality and increase the automation aspects of your APM initiatives.

Application Performance Management Consulting


The Application Performance Management (APM) Consulting services assist you in identifying and resolving specific performance problems in your business-critical applications. Using Strobe and iStrobe, consulting engineers work closely with your IT personnel to measure an applications performance, identify performance improvement opportunities and make recommendations for implementing solutions. With APM Consulting services, your organization cannot only resolve problems quickly and effectively, but also gain the skills necessary to prevent application performance degradation in the future.

Application Performance Assessment


The Application Performance Assessment (APA) service assists you in achieving a higher level of performance for your business-critical applications. Using Strobe and iStrobe, consulting engineers work closely with your IT personnel to evaluate the efficiency of business-critical applications, identify opportunities for improving performance and document the potential savings that can result from implementing recommended solutions. With APA services, you cannot only improve application performance quickly and effectively, but also gain the knowledge and skills necessary to implement and sustain a process-oriented application performance management (APM) program.

1-1

Chapter 1. Overview

Chap 1

Strobe issues messages that report on the status of the components of Strobe. Specifically, these messages are returned from the session management facility, its session manager and session requester components, the measurement facility and its subsystem components, and the reporting facility. These components are described in the Strobe User Guide. Messages fall into six categories depending upon their level of severity. They can be informative messages, License Manager System (LMS) messages, warnings, conditional errors, errors, and severe errors. Informative messages confirm user inputs, present information about the status of a Strobe function, and announce the completion of processing. License Manager System messages provide information about the licenses you have Compuware products. See the License Manager System documentation for more information about these messages. Warnings indicate that Strobe has performed the requested operation but had to use some default options. Conditional errors indicate that Strobe has performed the requested operation, but the information in the Strobe Performance Profile may be incomplete. Errors indicate that Strobe did not perform the operation, but you can correct and resubmit the request. Severe errors cause Strobe to terminate processing. The Strobe User Guide contains system recovery information.

Message Destination
The Strobe session management facility writes its messages to the SYSPRINT dataset and to an operators terminal (if the request originated from the terminal). The session management facility also writes all messages, except those produced in response to measurement session status requests, to the Strobe log dataset. The session management facility writes those messages produced in response to measurement session status requests to an operators terminal. Strobe/ISPF displays its messages at the top of the panel associated with the error. You can view a longer explanation by pressing the Help PF key. When the session management facility performs an operation and returns more than one message, Strobe/ISPF places the messages in a dataset and invokes the ISPF Browse function. Strobe writes messages produced during reporting and indexing to the SYSPRINT dataset. In addition, Strobe writes messages related to iStrobe to the iStrobe Performance Profile PROFILE.XML file. SQL analysis messages are also sent to the SYSTERM DD.

Message Format
Messages consist of an identifier followed by a short description of the condition. Message identifiers have a standard format of STRsnnnx, where:

1-2

Strobe Messages Guide

STR is the Strobe prefix. snnn is a four-digit message key, where s is the Strobe subsystem identification. nnn is the unique message number within the program identified by s. x is a one-letter severity code indicator. The possible values for the severity code and their associated return codes are shown in Return Codes and Severity Codes on page 1-2. Strobe follows the message identifier with a short description of the condition. For example:
STR0200I STROBE MEASUREMENT ENDED

Message Notation
Lowercase italicized words represent the names of variables. Brackets, braces, and vertical bars denote phrases that may or may not appear in the actual message: Brackets [ ] enclose expressions that appear only conditionally. Braces { } enclose alternative expressions (only one of which appears in the message), separated by vertical bars |.

Return Codes and Severity Codes


Unless otherwise indicated, the measurement task sets the job step return code to the value provided by the target program when it terminates. The Strobe session management facility, measurement facility, and the reporting facility set a return code to match the severity code in each message. Note: A return code in a message from a LIST or DELETE command issued through Session Requester reflects the highest return code associated with any of the requests targeted by that command.

Severity codes and the accompanying return codes are as follows: Severity Return Code Code I W 0 4 Meaning Informative message: occurs during normal operation. Warning message: indicates the operation is performed, but some information may be missing or some default options may be used. Conditional error message: indicates a user or system error. The requested action is performed and Strobe continues processing, but information in the Performance Profile reports may not be complete. Error message: indicates a user or system error. The requested action is not performed. If the measurement task issues such a message, it terminates sampling, but the target program execution continues.

Overview

1-3

Severity Return Code Code S 12

Meaning Severe error: indicates a user or system error. Strobe terminates processing.

ABEND Codes
This manual references Strobe abnormal termination (ABEND) codes, which appear when Strobe terminates without completing the measurement session. Chapter 4, Abend Codes Returned by Strobe includes a table of ABEND codes, their reason codes, and an explanation of why the ABEND occurred.

Viewing Message Descriptions with Strobe/ISPF


You can view an explanation of an error message by entering .M in the COMMAND or OPTION field on the panel displaying the message. In addition, you can view an explanation of any message from any panel by entering .M scnn (where scnn is the message key) in the OPTION field on the panel, or by selecting OPTION M from the Strobe Options menu. The messages and the accompanying explanations, system actions, and the recommended response are in Chapter 3, Messages Produced by Strobe. To view all the messages for the current request, enter .CVM in the OPTION field or select OPTION L from the Strobe Options menu. Strobe/ISPF presents all the messages in a dataset for you to browse.

Error Recovery and Reporting


This manual provides a recommended course of action for problems that a user can correct. If the error involves installation defaults, dynamic allocation problems, or other system problems, you should contact the Strobe system programmer. For additional system information, see the Strobe User Guide.

1-4

Strobe Messages Guide

2-1

Chapter 2. Messages Produced by the Installation Program

Chap 2

These messages are issued during Strobe installation by the Compuware JCL Customization Facility. For information about installing Strobe, see the Strobe Installation and Customization Guide.
STRI001E The dataset name this REXX exec STRINST is being invoked from cannot be automatically determined. Please refer to manual dataset name specification. Explanation: The Strobe JCL customization process requires that the STRINST exec be directly invoked from the ISPF command line. System Action: The Strobe JCL customization process does not execute.

User Response: Invoke the Strobe installation exec (STRINST) from the ISPF command line as follows:
TSO EX dsn(STRINST).

where dsn is the dataset name of the Strobe control dataset.


STRI002E Do not invoke this REXX exec STRINST by installing it in your SYSPROC DD. Please execute it via: "TSO EX dsn(STRINST)" Explanation: The Strobe JCL customization process requires that the STRINST exec be directly invoked from the ISPF command line. System Action: The Strobe JCL customization process does not execute.

User Response: Invoke the Strobe installation exec (STRINST) from the ISPF command line as follows:
TSO EX dsn(STRINST).

where dsn is the dataset name of the Strobe control dataset.


STRI003E STRINST. STRINST must be run in an ISPF environment. Please start ISPF prior to running

Explanation: The Strobe customization process requires that the STRINST exec be directly invoked from the ISPF command line. System Action: The Strobe JCL customization process does not execute.

User Response: Invoke the Strobe installation exec (STRINST) from the ISPF command line as follows:
TSO EXEC dsn(STRINST).

where dsn is the dataset name of the Strobe control dataset.


STRI004E The specified installation dataset dsn could not be located ! Please verify the dataset name and try again. Explanation: The dataset name specified in the message returned a status of DATASET NOT FOUND to the REXX function SYSDSN. System Action: User Response: The Strobe JCL customization process does not execute. Ensure that the installation dataset is available.

2-2

Strobe Messages Guide

STRI005E The specified installation dataset dsn does not contain the REXX exec "STRINST". Please verify the dataset name and try again. Explanation: The dataset name specified in the message returned a status of MEMBER NOT FOUND to the REXX function SYSDSN. System Action: User Response: The Strobe JCL customization process does not execute. Ensure that the installation dataset contains the member STRINST.

STRI006E The specified installation dataset dsn is invalid! Reason: <reason text> Please verify the dataset name and try again. Explanation: The dataset name specified in the message returned an error status <reason text> from the REXX function SYSDSN. System Action: The Strobe JCL customization process does not execute.

User Response: Correct the error as denoted by the reason text. For more information on the possible reason text refer to the appropriate IBM REXX Reference manual. STRI007E The specified installation dataset dsn does not contain the REXX exec "STRBUILD". Please verify the dataset name and try again. Explanation: System Action: User Response: STRI020E STRINST. The REXX function SYSDSN returned a status of MEMBER NOT FOUND. The Strobe JCL customization process does not execute. Ensure the installation dataset contains the member STRBUILD.

STRBUILD must be run in an ISPF environment. Please start ISPF prior to running

Explanation: The Strobe JCL customization process requires that the STRINST exec be directly invoked from the ISPF command line. System Action: The Strobe JCL customization process does not execute.

User Response: Invoke the Strobe installation exec (STRINST) from the ISPF command line as follows:
TSO EXEC dsn(STRINST).

where dsn is the dataset name of the Strobe control dataset.


STRI021E A fatal I/O error has occurred. Please correct the problem and try again.

Explanation: The REXX function EXECIO issued a return code = 20 when attempting to access the installation control dataset. System Action: The Strobe JCL customization process does not execute.

User Response: Correct the error as denoted by the return code. For more information on the possible return code refer to the appropriate IBM REXX Reference manual. STRI050E Please select a product for JCL customization. No S in the selection field to select a product for JCL customization. The Strobe JCL customization process does not execute. Place an S in the selection field to select a product for JCL customization.

Explanation: System Action: User Response: STRI051E

A product feature can not be selected without the product base.

Explanation: One or more product features were selected without the product base function also being selected. System Action: The Strobe JCL customization process does not execute.

User Response: Place an S in the selection field for the product base function in addition to any product features that were selected. STRI101E The SMS parameter must be "YES" or "NO". You specified an invalid value for the SMS parameter. The Strobe JCL customization process does not process the request.

Explanation: System Action:

Messages Produced by the Installation Program

2-3

User Response: STRI102E

Enter a value of either YES or NO in the SMS parameter field.

The DASD unit parameter contains an invalid character.

Explanation: The DASD unit parameter you specified contained one or more nonalphanumeric characters. System Action: User Response: characters. STRI103E The Strobe JCL customization process does not process the request. Enter a value in the DASD unit field that contains only alphanumeric

The DASD volser field contains and invalid character.

Explanation: The DASD volser parameter you specified contained one or more nonalphanumeric characters. System Action: User Response: characters. STRI104E The Strobe JCL customization process does not process the request. Enter a value in the DASD volser field that contains only alphanumeric

The SMP/E Work Unit parameter contains an invalid character.

Explanation: The SMP/E work unit parameter you specified contained one or more nonalphanumeric characters. System Action: User Response: characters. STRI105E The Strobe JCL customization process does not process the request. Enter a value in the SMP/E work unit field that contains only alphanumeric

The tape volser is missing, invalid, or less than 6 characters.

Explanation: The tape volser parameter is either missing, contained one or more nonalphanumeric characters, or was less than 6 characters in length. System Action: The Strobe JCL customization process does not process the request.

User Response: Enter a value in the tape volser field that is 6 characters long and contains only alphanumeric characters. STRI106E The tape unit parameter contains an invalid character.

Explanation: The tape unit parameter you specified contained one or more nonalphanumeric characters. System Action: User Response: characters. STRI107E The Strobe JCL customization process does not process the request. Enter a value in the tape unit field that contains only alphanumeric

The TMS parameter must be either "YES" or "NO". The TMS parameter you specified is invalid. The Strobe JCL customization process does not process the request. Enter a value in the TMS field that is either YES or NO.

Explanation: System Action: User Response: STRI108E

The Global High-level qualifier is not a valid dataset name.

Explanation: The Global High-level parameter suffixed with .CSI that you specified is invalid, as reported by the SYSDSN REXX function. System Action: User Response: STRI200E The Strobe JCL customization process does not process the request. Enter a valid value in the Global High-level qualifier field.

At least one SMS parameter must be specified.

Explanation: None of the three possible SMS parameters (STORCLAS, DATACLAS, and MGMTCLAS) must be specified. You must specify at least one. System Action: User Response: The Strobe JCL customization process does not process the request. Enter a value in at least one of the three SMS parameter fields.

2-4

Strobe Messages Guide

STRI201E

SMS <smsparm> parameter contains an invalid character. The SMS parameter <sysparm> contains one or more non-alphanumeric The Strobe JCL customization process does not process the request. Enter a value in the SMS parameter field that contains only alphanumeric

Explanation: characters. System Action: User Response: characters. STRI301E

The Global CSI dataset name is invalid.

Explanation: The Global CSI dataset name you specified is invalid, as reported by the SYSDSN REXX function. System Action: User Response: STRI302E The Strobe JCL customization process does not process the request. Enter a valid value in the Global CSI dataset name field.

It is an SMP/E requirement that this dataset name must end with a .CSI

Explanation: The Global CSI dataset name you specified is invalid because it does not have .CSI as its last qualifier. System Action: User Response: qualifier. STRI303E The Strobe JCL customization process does not process the request. Enter a value in the Global CSI dataset name field that has .CSI as its last

A new Global CSI dataset name cannot be longer than 38 characters.

Explanation: The Global CSI dataset name you specified is too long. The dataset name length cannot exceed 38 characters. System Action: The Strobe JCL customization process does not process the request.

User Response: Enter a value in the Global CSI dataset name field that does not exceed 38 characters in length. STRI304E The CSI set-up field must be "Y" or "N". The value you supplied in the Global CSI set-up field is invalid. The Strobe JCL customization process does not process the request. Enter a value in the Global CSI set-up field that is either Y or N.

Explanation: System Action: User Response: STRI501E

The High-level Qualifier is not valid for a dataset name.

Explanation: The High-level Qualifier you specified is invalid, as reported by the SYSDSN REXX function. System Action: User Response: STRI601E The Strobe JCL customization process does not process the request. Enter a value in the High-level Qualifier field that is valid.

The Distribution Zone Name is invalid.

Explanation: The Distribution Zone name you specified is invalid, it contains one or more non-alphanumeric characters. System Action: The Strobe JCL customization process does not process the request.

User Response: Enter a value in the Distribution Zone name that contains only alphanumeric characters. STRI602E The Distribution Zone CSI dataset name is invalid.

Explanation: The dataset name for the Distribution Zone name you specified is invalid, as reported by the REXX SYSDSN function. System Action: User Response: The Strobe JCL customization process does not process the request. Enter a value in the Distribution Zone dataset name that is valid.

Messages Produced by the Installation Program

2-5

STRI603E

It is an SMP/E requirement that the DZone DSN must end with a .CSI

Explanation: The Distribution Zone CSI dataset name you specified is invalid because it does not have .CSI as its last qualifier. System Action: The Strobe JCL customization process does not process the request.

User Response: Enter a value in the Distribution Zone CSI dataset name field that has CSI as its last qualifier. STRI605E The Target Zone Name is invalid.

Explanation: The Target Zone name you specified is invalid because it contains one or more non-alphanumeric characters. System Action: User Response: characters. STRI606E The Strobe JCL customization process does not process the request. Enter a value in the Target Zone name that contains only alphanumeric

The Target Zone CSI dataset name is invalid.

Explanation: The dataset name for the Target Zone name you specified is invalid, as reported by the REXX SYSDSN function. System Action: User Response: STRI607E The Strobe JCL customization process does not process the request. Enter a valid value for the Target Zone dataset name.

It is an SMP/E requirement that the Target Zone DSN must end with a .CSI

Explanation: The Target Zone CSI dataset name you specified is invalid because it does not have .CSI as its last qualifier. System Action: The Strobe JCL customization process does not process the request.

User Response: Enter a value in the Target Zone CSI dataset name field that has .CSI as its last qualifier.

2-6

Strobe Messages Guide

3-1

Chapter 3. Messages Produced by Strobe


This chapter contains messages issued by various Strobe components.

Chap 3

Messages Returned by the Measurement Task


The measurement task returns the following messages.
STR0115E SAMPLING MODULE modname NOT FOUND - MEASUREMENT SESSION TERMINATED Strobe did not find the sampling routine named modname. The measurement task terminates.

Explanation: System Action:

User Response: Notify the Strobe system programmer. There has probably been an installation error. STR0117E I/O ERROR LOCATING SAMPLING ROUTINES - MEASUREMENT SESSION TERMINATED Strobe encountered an I/O error while issuing a BLDL for the sampling The measurement task terminates. Notify the Strobe system programmer.

Explanation: routines. System Action: User Response: STR0118W

I/O ERROR SEARCHING DCC LIBRARY - DCCLIB OPERAND IGNORED Strobe encountered an I/O error while issuing a BLDL for a data collector.

Explanation:

System Action: Strobe attempts to load the data collectors from either a link list dataset or the library specified by STRMTLIB. User Response: programmer. STR0119W Save the JES log of the measured job and notify the Strobe system

DCC LIBRARY ALLOCATION FAILED - RC=rc; ERC/IRC= erc/irc; dsname

Explanation: Strobe encountered a non-zero return code while attempting to allocate a load library, dsname, for the data collectors. The return code is rc, the error reason code is erc, and the information reason code is irc. System Action: Strobe attempts to load the data collectors from either a link list dataset or the library specified by STRMTLIB. User Response: Specify a valid load library name in the Strobe DCCLIB operand or in the OTHER PARAMETERS field on the Strobe - Add Active or Strobe - Add Queued Request panel. If the library name is valid, notify the Strobe system programmer. STR0120W DCT ENTRY FOR MODULE module HAS BEEN MARKED INVALID - NOT REENTRANT An internal error has occurred. Strobe continues measuring, but measurement data may invalid or Contact Compuware Customer Support.

Explanation: System Action: incomplete. User Response: STR0122W

OPEN FAILED FOR DCC LIBRARY - DEFAULT LIBRARY USED

Explanation: An open has failed for the load library specified on the Strobe DCCLIB operand or on the Strobe - Data Collectors panel.

3-2

Strobe Messages Guide

System Action: Strobe attempts to load the data collectors from either a link list dataset or the library specified by STRMTLIB. User Response: Specify a valid load library name in the Strobe DCCLIB operand or in the OTHER PARAMETERS field on a Strobe - Add Active Request or Strobe - Add Queued Request panel and resubmit the request. If the library name is valid, notify the Strobe system programmer. STR0123E GETMAIN FAILURE FOR block - MEASUREMENT SESSION TERMINATED Virtual storage is not available for the critical control block block. The measurement task terminates.

Explanation: System Action:

User Response: Increase the region size so that Strobe can obtain the necessary virtual storage, and then resubmit the request. Contact the Strobe system programmer to obtain Strobe virtual storage requirements. STR0125E PCMG modname INVALID HEADER Strobe detected an invalid header in PCMG module modname. The measurement task terminates. Contact Customer Support.

Explanation: System Action: User Response: STR0126E

PCMG csectname CSECT NOT FOUND Strobe did not find CSECT csectname. Strobe continues sampling but may issue additional error messages. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR0127E

PCMG cdename CDE NOT FOUND Strobe did not find CDE cdename. Strobe continues sampling but may issue additional error messages. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR0128E

PCMG entryname ENTRY NOT FOUND Strobe did not find the entry point entryname. Strobe continues sampling but may issue additional error messages. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR0129E

STROBE MEASUREMENT MUST BE INVOKED BY THE SESSION MANAGER

Explanation: You attempted to run STRBVPH1 and attach the target program as a subtask. You cannot invoke the measurement facility directly; you must use the session manager. System Action: User Response: Strobe does not accept the measurement request. Resubmit the request through the Strobe session manager.

STR0134E LICENSE VERIFICATION FAILED RETURN CODE= rc REASON CODE= erc MEASUREMENT SESSION TERMINATED Explanation: Strobe base license has expired. The return code is rc and the error reason code is erc. System Action: Strobe does not initialize.

User Response: Refer to additional License Management System messages, and contact Compuware Customer Support. STR0140I MQSERIES COUNTS DISABLED FOR MEASUREMENT Strobe support for MQSeries Counts is not enabled. Strobe continues sampling but will not collect MQSeries counts.

Explanation: System Action:

User Response: For information about enabling Strobe support for MQSeries counts, contact Compuware Customer Support.

Messages Produced by Strobe

3-3

STR0144E STROBE TASKTERM ENDED IN ERROR - RTN xx, RS yy Explanation: The measurement completed, but Strobe did not release all of its resources. RTN xx is the decimal number of the subroutine that encountered the error. RS yy is the hexadecimal reason code for the error. System Action: User Response: Strobe log. STR0188W None. Contact Compuware Customer Support and provide the sample dataset and

NOTIFICATION TO FAULT MANAGER OF reason FAILED, RETCODE=xxx

Explanation: Strobe was unable to notify the Abend-AID Fault Manager about reason, which can be one of the following:

ABNORMAL BEHAVIOR IN PROGRAM pppppppp OF JOB jjjjjjjj - Abnormal behavior detected during AutoStrobe monitoring of the designated program pppppppp COMPLETION OF MEASUREMENT rrrr - The completion of the designated measurement. rrrr is the Strobe request number. xxx is the return code returned by the Fault Manager for the notification request.
System Action: AutoStrobe monitoring or Strobes measurement processing continues. After five occurrences of this message for an AutoStrobe-detected event, AutoStrobe will stop further attempts at fault-manager notification. User Response: STR0189I Notify the Strobe or Abend-AID system programmer.

ABEND-AID FAULT MANAGER NOT AVAILABLE

Explanation: Strobe attempted to notify the Abend-AID Fault Manager about the detection of an event but the Fault Manager is not active. System Action: continues. User Response: AutoStrobe monitoring or Strobes measurement-termination processing Notify the Strobe or Abend-AID system programmer.

STR0190E STROBE abendcode ABNORMAL TERMINATION MODULE=modname CSECT=csectname OFFSET=offset Explanation: An ABEND with code abendcode occurred during execution of the Strobe measurement task. The message identifies the module name modname, control section name csectname, and offset offset (in hexadecimal notation) at the time of termination. Additional information about the ABEND appears in the sample dataset. If Strobe reports modname as SWDA, Strobe was unable to obtain sufficient System Diagnostic Work Area (SDWA) storage and will not report CSECT or OFFSET information. System Action: The measurement session continues or terminates, depending on the site and severity of the error. User Response: STR0191I Notify the Strobe system programmer.

csectname CRITERIA MATCHED

Explanation: Informational message identifying a Strobe csectname that has reached a specific service criteria. System Action: User Response: Measurement session continues. None.

STR0199E INCOMPATIBLE MEASUREMENT SESSION MODULES - STROBE release, modname module_ release Explanation: Strobe attempted to load a measurement session module that has a different release level from that of STRBVPH1, the initial measurement task module. The release level of the initial measurement task module is release, the loaded module is modname, and its release level is module_release. System Action: The data collector terminates, but the measurement task continues. If the problem occurred in a measurement task module, then the measurement task terminates.

3-4

Strobe Messages Guide

User Response: occurred. STR0200I

Notify the Strobe system programmer. An installation error may have

STROBE MEASUREMENT ENDED

Explanation: The measurement session terminated normally. The sample dataset is ready for reporting. System Action: User Response: STR0207E Strobe completes processing. None required.

GETMAIN FAILURE - MEASUREMENT SESSION TERMINATED A measurement task module cannot obtain sufficient storage for its work area. The measurement task terminates. Increase the region size and resubmit the request.

Explanation: System Action: User Response:

STR0208E MEASUREMENT TASK UNABLE TO ISSUE ESTAE - MEASUREMENT SESSION TERMINATED Explanation: System Action: User Response: The measurement task is unable to establish its ABEND protection. The measurement task terminates. Notify the Strobe system programmer.

STR0209W LNKLST SET CHANGED DURING MEASUREMENT - MODULE MAPPING/ATTRIBUTION MAY BE INCORRECT Explanation: While measuring, Strobe detected a change in the Link List Set. The SETPROG LNKLST,UPDATE,JOB=jobname command was issued. System Action: inaccurate. Strobe continues processing but the module mapping or attribution may be

User Response: Resubmit the measurement request. Ensure that the SETPROG LNKLST,UPDATE,JOB=jobname command is not issued while the measurement is active. STR0212I ATTRIBUTION DRIVER DISABLED FOR MEASUREMENT OF THIS ADDRESS SPACE TYPE

Explanation: You requested to measure a DB2 DDF job. Attribution reports are not available for DDF address spaces. System Action: Strobe continues measuring, but no attribution information will be collected. User Response: STR0295E None required.

MEASUREMENT TASK PRIORITY ALTERED - MEASUREMENT SESSION TERMINATED

Explanation: The Strobe measurement is no longer the highest priority task in the measured address space. System Action: The measurement task terminates.

User Response: Resubmit the measurement request. The system will initialize it with the proper priority. If the problem occurs frequently, notify the Strobe system programmer. STR0300I SAMPLE DATA SET sdsname CLOSED, tttttt/eeeeee SAMPLES TAKEN

Explanation: The sample dataset sdsname is closed and can be used to produce a Strobe Performance Profile. sdsname is the low-order qualifier of the sample dataset name. The dataset contains tttttt total samples and eeeeee execution samples. System Action: User Response: STR0301E The measurement task completes processing. None required.

sdsname SAMPLE DATA SET OPEN FAILED

Explanation: Strobe cannot open the sample dataset sdsname. sdsname is the low-order qualifier of the sample dataset name. You may have insufficient storage to obtain buffers for the sample dataset. System Action: The measurement task terminates.

Messages Produced by Strobe

3-5

User Response: STR0302E

Modify the REGION parameter in the JCL, and resubmit the request.

sdsname SAMPLE DATA SET OPEN FAILED FOR UPDATE

Explanation: Strobe cannot open the sample dataset sdsname for update. sdsname is the loworder qualifier for the dataset name. System Action: Strobe continues execution of the target program. The Measurement Session Data report will be incomplete. User Response: STR0303W LOST Notify the Strobe system programmer.

GETMAIN FAILURE FOR CSECT TABLE - SOME ATTRIBUTION INFORMATION MAY BE A measurement task module cannot obtain additional storage. Strobe continues sampling, but some control section mapping detail may be Increase the region size and resubmit the request.

Explanation: System Action: lost. User Response: STR0304W

ddname NOT AVAILABLE

Explanation: Strobe cannot open the named target program load module library whose ddname is ddname. System Action: Strobe continues sampling normally. However, the Strobe Performance Profile produced from the measurement session will be incomplete. The Program Section Usage Summary report will show execution time data for the entire module only, not in detail for its control sections. The Program Usage by Procedure report will show only one unnamed section for the module and no procedure names. User Response: You may have omitted or incorrectly specified the required library data definition statement. Make the appropriate corrections, and resubmit the request. STR0305I UNABLE TO OBTAIN MODULE MAPPING DATA FOR modname

Explanation: Strobe attempted to gather module mapping data for a load module modname, and Strobe cannot find the load module in the library or libraries specified in the load module library data definition statement (for example, STEPLIB, JOBLIB), in a link list dataset, or in the dataset named by the STRBLIB operand. System Action: Strobe continues sampling (unless the operating system could not locate the load module), but the Strobe Performance Profile will have the deficiencies described by message STR0304W. The possible causes include:

The named module is resident in a link pack area and LPALIB searches were disabled at installation. You incorrectly named a library in the STRBLIB operand in the ADD operation.

The library or libraries do not contain the named module.


User Response: STR0306W None required.

LIBRARY ALLOCATION FAILED - RC=rc; ERC/IRC= erc/irc; dsname

Explanation: Strobe encountered a non-zero return code while attempting to allocate a load library, dsname, to search for control section data. The return code is rc, error reason code is erc, and the information reason code is irc. System Action: Strobe cannot collect control section data from this load library.

User Response: Ensure that you have correctly specified the library name. If the name is correct, notify the Strobe system programmer. STR0307W DISCARDED MODULE modname MAPPED SIZE UNEQUAL TO IDENTIFIED SIZE, CSECT DATA

Explanation: The version of module modname referenced for mapping was different from the version executing in the job.

3-6

Strobe Messages Guide

System Action: Strobe deletes the erroneous mapping data and continues measuring. Strobe will produce a Performance Profile but some attribution data in the Profile may be incomplete. User Response: Either remove the incorrect version from the library search path, or use the STRBLIB option to put the correct version at the top of the search path. STR0308W TOO MANY LOAD LIBRARIES SPECIFIED - ONLY 16 USED You specified more than 16 load libraries on the STRBLIB operand. Strobe uses only the first 16 load libraries specified. None required.

Explanation: System Action: User Response: STR0309W

TWO OR MORE ATTACHES IN AN INTERVAL - TASKLIB MAY BE LOST

Explanation: The TASKLIB pointers for ATTACHES became overlaid because either the user program issued ATTACHES rapidly or Strobe used a very long sampling interval. Because Strobe only has storage to record one TASKLIB pointer for an ATTACH during a sampling interval, if multiple ATTACHES occur the latest will overlay the previous one. If an ATTACH that was overlaid specified a unique TASKLIB, reference to it will be lost. In this case some module mapping information may be missing. System Action: Strobe continues processing, but some module mapping information may be missing. User Response: If significant module mapping data is lost, resubmit the measurement with a shorter sampling interval. If this is not successful, you can force the identification of the missing TASKLIB by resubmitting the measurement request and specifying TASKLIB as a STRBLIB parameter. STR0310W MODULE modname HAS SCATTER ATTRIBUTE A load module has the scatter attribute.

Explanation:

System Action: Strobe continues sampling normally. However, the Strobe Performance Profile produced from the measurement session will be incomplete. The Program Section Usage Summary report will show execution time data for the entire module only, not in detail for its control sections. The Program Usage by Procedure report will show only one unnamed section for the module and no procedure names. User Response: Research whether you can relink the module without the scatter attribute. If you can, then remeasure afterwards. STR0311I JSTCB JLB POINTS TO INVALID DCB

Explanation: A STEPLIB, JOBLIB, or TASKLIB DCB was found in other than a valid OPEN status. A sampling interval coincided with task termination. System Action: may be lost. The measurement task completes processing, although some module data

User Response: Resubmit the measurement request. If you are measuring a batch job, increase the sample rate and resubmit the request. STR0312E ADDRESS SPACE NOT AUTHORIZED TO CREATE SAMPLE DATASET

Explanation: This message is followed by message STR6800I. The security subsystem was queried for the authorization level for this name. The level returned would not permit creation of a sample dataset with this name. System Action: The measurement task terminates.

User Response: Either change the Strobe parameters defining how the sample dataset name is generated to adhere to installation conventions, or modify security subsystem rules to allow authorization for the newly defined Strobe convention. STR0313W ADDRESS SPACE NOT AUTHORIZED TO READ LIBRARY

Explanation: This message is followed by message STR6800I. The security subsystem was queried for the authorization level for this name. The level returned would not permit reading of a load module library with this name. The library is removed from the module mapping library search list.

Messages Produced by Strobe

3-7

System Action: some modules. User Response: STR0314W

Strobe continues sampling, but module mapping data may be missing for Modify security subsystem rules to authorize read access to the library.

DATASPACE ALLOCATION FAILURE-- LONGNAMES WILL NOT BE REPORTED An error occurred during the allocation of the long names dataspace.

Explanation:

System Action: Strobe continues measuring without measuring modules with names exceeding eight characters. User Response: STR0320E Notify the Strobe system programer.

OPEN/CLOSE TIME EXCEEDED

Explanation: The Strobe sample dataset open or close processing did not complete within the expected CPU time. System Action: The measurement task stops sampling and terminates with a user ABEND code of 322. The Measurement Session Data report will be incomplete. User Response: STR0330E message Notify the Strobe system programmer.

Explanation: The CA-Panexec interface had difficulty processing a Strobe request. The message displayed is returned by the CA-Panexec interface program. System Action: some modules. User Response: STR0340W Strobe continues sampling, but module mapping data may be missing for Notify the Strobe system programmer.

PANXACCS INTERFACE MODULE NOT AVAILABLE

Explanation: Strobe for AllFusion CA-Panexec is installed but Strobe cannot find the interface module named PANXACCS, which is supplied by the CA-Panexec vendor. This message is accompanied by a system 806-4 ABEND message, but Strobe does not terminate abnormally. System Action: some modules. User Response: STR0341W SUPPORT Strobe continues sampling, but module mapping data may be missing for Notify the Strobe system programmer.

PANXACCS INTERFACE ERROR-- SAVE LOG AND SAMPLE FILE-- CONTACT CUSTOMER Strobe encountered an error in the Strobe CA-Panexec interface.

Explanation:

System Action: Strobe logs the problem in the sample dataset, corrects the error, and continues sampling. User Response: Save a copy of the sample dataset and the Strobe log, and contact Compuware Customer Support. STR0342W BINDER MESSAGE: text Strobe displays text, the Binder API error message. Strobe continues sampling, but module mapping may be incomplete.

Explanation: System Action:

User Response: Refer to IBMs MVS System Messages manual for information on the message issued by the binder. STR0343C FROM BINDER API: FUNCTION=fnct RC=rc RSN=rsnc

Explanation: The binder experienced a failure. The binder function that failed is fnct, the return code is rc, and the reason code from the binder is rsnc. System Action: Strobe continues sampling, but module mapping may be incomplete.

User Response: Notify the Strobe system programmer. Refer to IBMs DFSMS/MVS Program Management manual for the binder API return codes and reason codes.

3-8

Strobe Messages Guide

STR0344C

ACTIVE DEVICE TABLE CORRUPTED Strobe detected an error in the Active Device Table. Strobe will not report DASD model type, VTOC location, and cache status.

Explanation: System Action:

User Response: Save a copy of the sample dataset and the Strobe log, and then contact Compuware Customer Support. STR0345W REPORTED GETMAIN FAILED FOR THE CACHE I/O AREA - CACHE STATUS WILL NOT BE Strobe cannot obtain enough virtual storage in ESQA (subpool 245).

Explanation:

System Action: Strobe continues sampling, but will not report cache status on the Data Set Characteristics Supplement. User Response: STR0346W Notify the Strobe system programmer.

FREEMAIN FAILED FOR THE CACHE I/O AREA, STORAGE ADDRESS addr

Explanation: The FREEMAIN failed for the cache I/O area in ESQA (subpool 245), beginning at address addr. System Action: The measurement task terminates.

User Response: Save a copy of the sample dataset and the Strobe log. Notify the Strobe system programmer. STR0347W FREEMAIN FAILED FOR AN ACTIVE UCB TABLE SEGMENT, STORAGE ADDRESS addr The FREEMAIN failed for a segment of the Active UCB table, beginning at The measurement task terminates.

Explanation: address addr. System Action:

User Response: Save a copy of the sample dataset and the Strobe log, and then contact Compuware Customer Support. STR0348W DEVICE NUMBER MISMATCH FOR DEVICE nnnn

Explanation: During measurement, an I/O configuration change caused a UCB address to be reassigned to another device. System Action: device nnnn. User Response: programmer. STR0349W Strobe will not report DASD model type, VTOC location, or cache status for Save a copy of the sample dataset and Strobe log. Notify the Strobe system

I/O ERROR CODE ec OBTAINING CACHE STATUS FOR DEVICE nnnn

Explanation: Strobe encountered an I/O error with error code ec while attempting to obtain cache status for device nnnn. System Action: Strobe will not report cache status for the device.

User Response: Save a copy of the sample dataset and the Strobe log. Notify the Strobe system programmer. STR0350E GETMAIN FAILED FOR STRVPH3 WORKAREA A critical measurement task failed to obtain sufficient storage for its The measurement task terminates. Increase the region size and resubmit the request.

Explanation: initialization. System Action: User Response: STR0351E

RECURSIVE ENTRY TO STRVPH3 INIT A fatal control error occurred in a measurement task module. The measurement task terminates. Notify the Strobe system programmer.

Explanation: System Action: User Response:

Messages Produced by Strobe

3-9

STR0354W STROBE DETECTS EXECUTION WITHIN GOFF MODULE module CONTAINING LONG NAME SECTIONS Explanation: Strobe encountered a Generalized Object File Format (GOFF) module that contains sections with long names. System Action: For GOFF modules with section names that are greater than 8 characters in length, Strobe reports execution information under the pseudo-section name #LONGnnn, where nnn is a sequence number that Strobe resets to 1 within each new module. Strobe may report information under the #LONGnnn pseudo-section on any of the following Strobe Performance Profile reports: the Program Usage by Procedure, the Wait Time by Module, the Most Intensively Executed Procedures, the Most Extensive Inactive Storage Areas, the Program Section Usage Summary, the Program Usage by Procedure, the Transaction Usage by Control Section, the Attribution of CPU Wait Time, and the Attribution of CPU Execution Time. User Response: None required. To identify the names of the GOFF module sections reported under the pseudo-section #LONGnnn, note the offsets that Strobe reports and use a linkage editor map of the module to determine the section name. STR0355W STROBE ENCOUNTERED RTLS MODULE(S)

Explanation: Strobe encountered a language attribution module loaded by Run Time Library Services (RTLS). System Action: Strobe continues sampling; however, attribution data for that module may be missing or incorrect. User Response: Specify the Run Time Language Library on a STROBLIB parameter and rerun the measurement session. Although Strobe will still issue this message, once the Run Time Language Library is specified on a STROBLIB parameter, the attribution data reported will be correct. STR0356W THRESHOLDS DISABLED - MORE THAN 12 SAMPLING INTERVALS ENCOUNTERED

Explanation: Strobe has been sampling for more than 12 sampling intervals, actively sampling for more than 34 hours. System Action: User Response: STR0358I Strobe continues processing, but all thresholds are disabled. Reduce sampling time and resubmit the request.

MODULE CALLABLE SERVICE service FAILED, RC=rc, RSNC=rsnc

Explanation: The UNIX System Services Callable Service service did not return a full path name. rc is the return code. rsnc is the reason code. System Action: Strobe continues processing with a partial path name. The Data Set Characteristics and Data Set Characteristics Supplement reports will show a partial path name for this file. User Response: None required.

STR0359W SMF RECORDING FOR TYPE 92 RECORDS IS NOT ACTIVE, NO USS FILE SYSTEM I/O COUNTS WILL BE REPORTED Explanation: Strobe does not report I/O counts for OS/390 UNIX System Services Hierarchical File System (HFS) or z/FS files because the SMF recording for Type 92 records is not active. System Action: report. HFS and z/FS I/O counts are not reported on the Data Set Characteristics

User Response: To report I/O counts for HFS or z/FS files, modify a user-exit module in the Strobe control dataset. See Appendix A of the Strobe Installation and Customization Guide for an example of a user-exit module. STR0360W STRBXDS2 CONTROL BLOCK xxx INVALID - NO MATCH ON EYECATCHER Validation of control block xxx failed.

Explanation:

System Action: The data required to build the z/OS Memory Objects report will not be collected and the report will not be produced. Measurement continues.

3-10

Strobe Messages Guide

User Response: STR0401W

None required.

GETMAIN FAILURE - I/O INFORMATION WILL NOT BE REPORTED A measurement task module cannot obtain sufficient storage for its work area.

Explanation:

System Action: Strobe continues sampling, but there are no I/O reports in the Performance Profile; or if produced, the reports contain minimal information. User Response: STR0402W Increase the region size and resubmit the request.

GETMAIN FAILURE - SOME DATA SETS MAY NOT BE MAPPED Strobe cannot obtain enough virtual storage for an internal table.

Explanation:

System Action: Strobe continues sampling, but the I/O reports in the Strobe Performance Profile do not contain information about datasets residing on some units. User Response: STR0403W Increase the region size and resubmit the request.

GETMAIN FAILURE - DATA SET CHARACTERISTICS MAY BE MISSING Strobe cannot obtain enough virtual storage for an extension to its internal

Explanation: dataset table.

System Action: Strobe continues sampling but may not collect dataset characteristics for some datasets active during the measurement session. User Response: STR0404E Increase the region size and resubmit the request.

STRBVIO FAILURE - DATA SET CHARACTERISTICS MAY BE MISSING A measurement task module has encountered a fatal error. Strobe continues sampling but stops taking I/O samples. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR0405W

GETMAIN FAILURE - LSR STATISTICS WILL BE MISSING OR INCOMPLETE

Explanation: The measurement task module STRBLSRS cannot obtain sufficient storage for its work area or its internal tables. System Action: Strobe disabled STRBLSRS. Strobe continues sampling but no longer collects LSR statistical information during this measurement session. User Response: STR0406W The next time you submit this request, increase the region size.

STRBLSRS DISABLED, EXCEEDED MAX GETMAINS An internal error occurred in the measurement task module STRBLSRS.

Explanation:

System Action: Strobe disabled STRBLSRS. Sampling continues, but Strobe will no longer collect LSR statistical information during this measurement session. User Response: STR0407W Notify the Strobe system programmer.

STRBLSRS DISABLED, INTERNAL ERROR error

Explanation: An internal error occurred in the measurement task module STRBLSRS; error is an internal code. System Action: Strobe disables STRBLSRS. Sampling continues, but Strobe no longer collects LSR statistical information during this measurement session. User Response: STR0408W Notify the Strobe system programmer.

GETMAIN FAILURE FOR THE ACTIVE DEVICE TABLE Strobe cannot obtain enough virtual storage for an internal table.

Explanation:

System Action: Strobe continues sampling, but does not report DASD model type, VTOC location, and cache status. User Response: Increase the region size and resubmit the request.

Messages Produced by Strobe

3-11

STR0409W

LOAD FAILED FOR MODULE module ABEND CODE=Sxxx-xx

Explanation: Strobe invoked an MVS service to load a module, but the load request failed. Sxxx-xx is the abend and reason code associated with the failed load. System Action: User Response: STR0410E Strobe continues processing, but there may be some loss of function. Notify the Strobe system programmer.

module FAILURE text

Explanation: A Strobe module encountered an error. The message text names the Strobe module and provides information about the failure. System Action: User Response: STR0411W Strobe continues processing, but there may be some loss of function. Notify the Strobe system programmer.

STORAGE-OBTAIN FAILURE IN module FOR reason

Explanation: A Strobe module invoked a MVS routine to obtain storage, but the storage request failed. The message text names the Strobe module and indicates the reason for the storage request. System Action: User Response: STR0412E Strobe continues processing, but there may be some loss of function. Notify the Strobe system programmer.

MODULE FUNCTION FAILED RC xxxx RSNC xxxxx

Explanation: Strobe unsuccessfully invoked an MVS function. The message text names the Strobe module and the function that was invoked. RC xxxx is the return code and RSNC xxxx is the reason code returned by the function. System Action: User Response: STR0413W Strobe continues processing, but there may be some loss of function. Notify the Strobe system programmer.

MODULE FUNCTION FAILED, RC=rc The specified function failed with the return code of rc. Strobe continues processing. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR0414W

STORAGE OBTAIN FAILED FOR storarea A STORAGE OBTAIN for the area specified by storarea failed. Strobe continues processing. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR0501E

I/O ERROR DURING UPDATE OF SAMPLE DATA SET

Explanation: Strobe encountered a permanent I/O error while updating the first record in a sample dataset. This message follows message STR0507W, which contains the standard SYNAD messages returned by the operating system. System Action: Strobe continues execution of the target program but collects no further samples. The Measurement Session Data report is incomplete. User Response: error. STR0502W Notify the Strobe system programmer. There has probably been a hardware

I/O ERROR READING LOAD LIBRARY

Explanation: Strobe encountered an I/O error while accessing a module from a load module library. This message follows message STR0507W, which contains the standard SYNAD messages returned by the operating system. The SYNAD messages identify the partitioned dataset causing the error. System Action: Strobe continues sampling (unless the operating system has been unable to locate the load module), but the Strobe Performance Profile produced from the measurement session is incomplete.

3-12

Strobe Messages Guide

The Program Section Usage Summary report shows execution time data for the entire module only, not in detail for its control sections, and the Program Usage by Procedure report shows only one unnamed section for the module and no procedure names. User Response: error. STR0503E Notify the Strobe system programmer. There has probably been a hardware

OUT OF SPACE ON SAMPLE DATA SET

Explanation: No more space is available in the sample dataset. The message precedes message STR0505E, which displays the ABEND and return codes.

Your target sample size may be too high. Generally, a target size of 8000 to 32000 is adequate. If you want to retain the sample size, you need a larger sample dataset.
System Action: Strobe continues execution of the target program, but collects no further samples. The Measurement Session Data report is incomplete. In addition, reports will not include module mapping data. User Response: You can allocate a larger sample dataset before the measurement session begins. The name of the sample dataset must correspond to the name that Strobe creates. See the Strobe User Guide for additional information. STR0504E I/O ERROR WRITING TO SAMPLE DATA SET

Explanation: Strobe encountered a permanent I/O error while writing to a sample dataset. This message follows message STR0507W, which contains the standard SYNAD messages returned by the operating system. System Action: samples. User Response: error. Strobe continues execution of the target program but collects no further Notify the Strobe system programmer. There has probably been a hardware

STR0505E ABEND WHILE PROCESSING SAMPLE DATA SET - COMPLETION CODE=abendcode, RETURN CODE=rc Explanation: Strobe encountered an ABEND while opening, writing to, or closing a sample dataset. The ABEND code is abendcode, and the return code is rc. System Action: Strobe continues execution of the target program but collects no further samples. Strobe may produce a Performance Profile, but some reports will be incomplete. User Response: STR0506E Notify the Strobe system programmer.

WRITE ATTEMPTED TO CLOSED SAMPLE FILE The measurement task attempted to write to a closed sample dataset. The measurement task terminates. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR0507W

I/O ERROR synad messages

Explanation: Strobe encountered a permanent I/O error. This message contains the standard SYNAD messages synad returned by the operating system, and it is followed by messages messages describing the I/O error. System Action: User Response: STR0508W CODE=rc The measurement task terminates. Notify the Strobe system programmer.

ABEND WHILE READING LOAD LIBRARY - COMPLETE CODE= abendcode, RETURN

Explanation: Strobe encountered an ABEND while opening, reading, or closing a load library dataset. The ABEND code is abendcode, the return code is rc. System Action: Strobe continues sampling, but obtains no further mapping data from the failing library. Strobe will produce a Performance Profile, but some reports may be incomplete. User Response: Notify the Strobe system programmer.

Messages Produced by Strobe

3-13

STR0509W

DATASPACE API INITIALIZATION FAILED -- FUNCTION DISABLED, RC=rrr, ERC=erc An error occurred during the initialization of the Dataspace Manager API. Strobe continues sampling without Dataspace Manager functions. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR0510W

DATASPACE API DEALLOCATION FAILURE; RC=rrr; ERC=erc An error occurred during the termination of the Dataspace Manager API. Strobe continues terminating Dataspace Manager API. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR0512E

SAMPLE FILE ALLOCATION-OPEN CALL FAILED RC=xx

Explanation: Strobe made a call to the MSAS address space to allocate and open a sample dataset, and the request failed. There are accompanying messages from the MSAS address space that should explain the error. Refer to the Strobe log for the additional messages. System Action: User Response: STR0540W The measurement task terminates. The error may be temporary. Try resubmitting the request.

GETMAIN FAILURE IN STRBSNAP - DIAGNOSTIC SNAPPING DISABLED

Explanation: A GETMAIN failure occurred when a measurement task module tried to obtain storage for a work area. System Action: Strobe continues sampling, but the measurement task cannot use the diagnostic SNAP feature. User Response: STR0550W Notify the Strobe system programmer.

STRBGMIM: USER TCB NOT AVAILABLE FOR CAPTURE

Explanation: Strobe could not complete an internal request to capture user data because Strobe could not find the user target task control block (TCB). System Action: Strobe continues measuring but does not capture the additional user data.

User Response: Resubmit the measurement request. If the problem persists, contact Compuware Customer Support. STR0551W STRBGMIM: STORAGE REQUEST FAILED FOR CB block A Strobe internal storage request for control block block failed. Strobe continues measuring but does not capture the additional user data.

Explanation: System Action:

User Response: Resubmit the measurement request. If the problem persists, contact Compuware Customer Support. STR0552W STRBGMIM: AITE NOT FOUND FOR fnctname REQUEST

Explanation: Strobe could not locate the active table element for function fnctname requested by Strobe internal request REMOVE or FREESTOR. System Action: User Response: STR0553W Strobe continues measuring but does not execute the requested function. Contact Compuware Customer Support.

STRBGMIM: CAPTURE PROCESSING FAILED DURING VECTOR SWAP A Strobe internal request to insert a capture routine failed. Strobe continues measuring, but does not enable the capture routine. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR0554W

STRBGMIM: CAPTURE VECTOR ADDRESS IS INVALID. NOT IN PRIVATE STORAGE

Explanation: Strobe made an internal request for a capture routine with an invalid address not in private storage. System Action: Strobe continues measuring, but does not enable the capture routine.

3-14

Strobe Messages Guide

User Response: STR0555W ADDRESS

Contact Compuware Customer Support.

STRBGMIM: CAPTURE PROCESSING FAILED. MULTIPLE CAPTURES FOR SAME

Explanation: Strobe made an internal request for a capture routine with a vector address that had previously been processed. System Action: User Response: STR0556W Strobe continues measuring but does not enable the capture routine. Contact Compuware Customer Support.

STRBGMIM: CAPTURE PROCESSING FAILED. CAPTURE FACILITY DISABLED A Strobe internal request for a capture routine failed because the facility was Strobe continues measuring with the capture routine disabled. None required.

Explanation: disabled. System Action: User Response: STR0559I

STRBGMIM: <string> Strobe has stored diagnostic data in <string>. Strobe continues processing, but some measurement data may be missing. Contact Compuware Customer Support.

Explanation: System Action: User Response:

STR0601W DATA COLLECTOR modname NOT IN PROPER FORMAT - {NOT A STROBE MODULE | HAS NO PROGRAM LIST |DOESN'T SUPPORT PROGRAM} - NOT USED Explanation: The data collector modname does not meet the requirements specified in the Strobe Interface manual. System Action: Strobe continues sampling without the data collector.

User Response: Revise the data collector to meet Strobe Interface standards and resubmit the request. STR0602W DATA COLLECTOR modname NOT FOUND - OPERAND IGNORED Strobe cannot find the data collector modname. Strobe continues sampling without the data collector.

Explanation: System Action:

User Response: Place the data collector in a link list dataset or in the library named by the DCCLIB operand and resubmit the request. STR0603W DATA COLLECTOR modname RETURN CODE = rc - ROUTINE DISABLED

Explanation: The data collector modname returned a return code, rc, greater than or equal to 16 (severe error). System Action: User Response: STR0604W Strobe continues sampling without the data collector. Notify the Strobe system programmer.

DATA COLLECTOR modname ABENDED - ROUTINE DISABLED

Explanation: The data collector modname terminated abnormally. This message appears with other messages that provide detailed information about the ABEND. System Action: User Response: STR0605W Strobe continues sampling without the data collector. Notify the Strobe system programmer.

GETMAIN FAILURE - SOME MODULES MAY NOT BE MAPPED Strobe cannot obtain sufficient storage for an extension to its internal module Strobe continues sampling without mapping information for some modules. Increase the region size and resubmit the request.

Explanation: table.

System Action: User Response:

Messages Produced by Strobe

3-15

STR0606W

DATA COLLECTION DRIVER STRBVDCC ABENDED - DC INTERFACE DISABLED

Explanation: The Data Collection Interface Driver terminated abnormally. This message appears with other messages that provide detailed information about the ABEND. System Action: User Response: STR0607W Strobe continues sampling without subsystem or attribution data. Notify the Strobe system programmer.

DATA COLLECTION INTERFACE CALLED WITH INVALID FUNCTION CODE (fctcode) The data collection interface was called with an invalid function code fctcode. Strobe continues sampling without some subsystem or attribution data. Examine all user-written data collectors, and then notify the Strobe system

Explanation: System Action: User Response: programmer. STR0608W

DATA COLLECTION INTERFACE CALLED WITH NO PARAMETER LIST The data collection interface was called with no parameter list pointer. Strobe continues sampling without some subsystem or attribution data. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR0609W

DATA COLLECTION INTERFACE INVOKED BY UNKNOWN CALLER

Explanation: The data collection interface was called by a program not recognized by Strobe. System Action: User Response: Strobe continues sampling without some subsystem or attribution data. Notify the Strobe system programmer.

STR0610W GETMAIN FAILURE IN STRBVDCC FOR block - DC INTERFACE DISABLED CSECT csectname sampnumber. Explanation: Virtual storage is not available for the control block described by block, CSECT described by csectname, and sample number described by sampnumber. System Action: Strobe continues sampling without some subsystem or attribution data.

User Response: Increase the region size so that Strobe can obtain the necessary virtual storage, and then resubmit the request. Contact the Strobe system programmer to obtain Strobe virtual storage requirements. STR0611W GETMAIN REFUSED IN STRBVDCC FOR block - DC INTERFACE DISABLED CSECT csectname sampnumber. Explanation: Strobe made excessive requests for virtual storage for the control block described by block, CSECT described by csectname, and sample number described by sampnumber. System Action: Strobe continues sampling without some subsystem or attribution data.

User Response: Increase the region size so that Strobe can obtain the necessary virtual storage, and then resubmit the request. Contact the Strobe system programmer to obtain Strobe virtual storage requirements. STR0612W GETMAIN FAILURE IN STRBVDCC FOR VDCCWORK AREA Virtual storage is not available for the VDCCWORK AREA. Strobe continues sampling without any subsystem or attribution data.

Explanation: System Action:

User Response: Increase the region size so that Strobe can obtain the necessary virtual storage, and then resubmit the request. Contact the Strobe system programmer to obtain Strobe virtual storage requirements. STR0613W DATA COLLECTOR datacollector IGNORED - STROBE INTERFACE NOT LICENSED You attempted to use the Strobe Interface, but your site has not licensed this Strobe will not invoke the user-written data collector datacollector.

Explanation: option. System Action:

User Response: To obtain information about licensing the Strobe Interface, contact Compuware Customer Support.

3-16

Strobe Messages Guide

STR0614E

ERROR IN DATASPACE API FUNCTION xx FOR DATASPACE yy (KEY zz)

Explanation: An error occurred in the dataspace manager API. xx is the function requested. yy is the name of the dataspace. zz is the key of the entry. System Action: User Response: STR0630E The variable returned depends on the caller of the API. Notify the Strobe system programmer.

GETMAIN FAILURE IN modname - MODULE IDENTIFICATION DISABLED

Explanation: Strobe cannot obtain virtual storage for an extension to its internal module table in module modname. System Action: Strobe continues sampling without default module identification information. If the module was identified by a data collector, the Performance Profile contains module mapping information for that module. Otherwise, Strobe attributes module activity to a pseudo-section, resulting in excessive values for all pseudo-sections. User Response: STR0631W Increase the region size and resubmit the request.

BATCHPIPE WAIT DETECTED, FILE CANNOT BE IDENTIFIED Strobe identified BatchPipe wait but is unable to assign this wait to a specific

Explanation: file.

System Action: Strobe continues processing but information for BatchPipes files in the Performance Profile will be incomplete User Response: Check that you have performed the procedure required to collect BatchPipes information that is detailed in the Strobe Installation and Customization Guide. If you have performed the procedure and the problem persists, contact Compuware Customer Support. STR0632E BATCHPIPE CONTROL BLOCK ERROR, block

Explanation: Strobe detected BatchPipes wait, but due to an internal control block change, Strobe cannot assign wait to a specific file. Strobe identifies the control block in block. System Action: Strobe continues processing but the information for BatchPipes files in the Performance Profile will be incomplete. User Response: STR0633W Contact Compuware Customer Support.

MODULEcbid CONTROL BLOCK ERROR DURING USS FILE SYSTEM PROCESSING

Explanation: Strobe encountered a control block error for cbid while attempting to identify a Hierarchical File System (HFS) file or z/FS file. System Action: User Response: Strobe does not identify the HFS or z/FS file. Strobe continues processing. Contact Compuware Customer Support

STR0634W MODULE nn CONTROL BLOCK ERRORS, USS FILE SYSTEM DATA COLLECTION IS SUSPENDED Explanation: Strobe encountered nn control block errors during HFS or z/FS file identification. System Action: User Response: STR0701W Strobe suspends the HFS or z/FS data collection interface. Contact Compuware Customer Support.

GETMAIN FAILURE IN STRBATTR - ATTRIBUTION DATA COLLECTION DISABLED Strobe cannot obtain virtual storage for a work area. Strobe continues sampling without attribution data. Increase the region size and resubmit the request. Notify the Strobe system

Explanation: System Action: User Response: programmer.

STR0702W ATTRIBUTOR modname NOT FOUND - UNABLE TO COLLECT REQUESTED ATTRIBUTION DATA Explanation: System Action: Strobe cannot find the requested attributor modname. Strobe continues sampling without some attribution data.

Messages Produced by Strobe

3-17

User Response: STR0703W

Notify the Strobe system programmer.

ATTRIBUTOR modname RETURN CODE = rc - ROUTINE DISABLED

Explanation: The attributor modname returned a return code, rc, greater than or equal to 16 (severe error). System Action: User Response: STR0704W Strobe continues sampling without the attributor. Notify the Strobe system programmer.

ATTRIBUTOR modname ABENDED - ROUTINE DISABLED The attributor name modname terminated abnormally. Strobe continues sampling without the attributor. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR0705W

ATTRIBUTION DRIVER STRBATTR ABENDED - ATTRIBUTION DISABLED The attribution driver terminated abnormally. Strobe continues sampling without attribution data. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR0707I

STRBXDS1 - CALLABLE SERVICE IXLMG FAILED, RC = rc, RSNC = rsnc

Explanation: The coupling facility service, IXLMG, failed. This service is not required for Strobe measurement. Strobe writes the message to the Strobe log. System Action: Strobe continues processing, but may not collect the coupling facility service information. User Response: None required.

STR0708I STROBE MEASUREMENT SERVICES release CALLED FROM STRT TSK jobname AT time, SYSTEM = system Explanation: The Measurement Services Address Space (MSAS), which includes AutoStrobe, has successfully been initialized. System Action: Session manager successfully started the Measurement Services Address Space (MSAS). User Response: None required.

STR0709I STROBE MEASUREMENT SERVICES release COMPLETED for STRT TSK jobname RC=nn, SYSTEM = system Explanation: The Measurement Services Address Space (MSAS) address space, which includes AutoStrobe, has terminated. System Action: The Measurement Services Address Space (MSAS) terminated due to an operator command or because of an error. User Response: None if required the return code = 0. If the return code is not zero, report the problem to the system programmer. This message can also appear on the operators console. STR0712I STROBE MEASUREMENT SERVICES jobname NOT STARTED - ISSUE A SESSION MANAGER MODIFY/START COMMAND Explanation: The Measurement Services Address Space (MSAS), which includes AutoStrobe, was not started and the message was sent to the operators console. System Action: The Measurement Services Address Space (MSAS) does not start and AutoStrobe is inoperative. User Response: Issue an MVS MODIFY for the session manager to initiate the Measurement Services Address Space (MSAS). STR0713I STROBE MEASUREMENT SERVICES release LICENSE VERIFICATION FAILED. RETURN CODE = nn REASON CODE = nnn -BASE/ASM Explanation: The Measurement Services Address Space (MSAS) was not started because a license verification error occurred when validating the license.

3-18

Strobe Messages Guide

System Action: The Measurement Services Address Space (MSAS), which includes AutoStrobe, was not initialized. User Response: STR0714E Report the problem to the Strobe system programmer.

MSAS NOT INITIALIZED, MODULE VERSION CHARACTER MUST BE "v"

Explanation: The version character (the fourth character of the name of the MSAS load module (STRxMSAS) is not the same of the as the version character of the load module of the session manager that attempted to create this MSAS. The session managers version character is specified in the message. System Action: The MSAS started task cannot be initialized and terminates. The session manager which attempted to start the MSAS started task also terminates because its associated MSAS cannot be initialized. User Response: Notify the Strobe system programmer and ensure that the names of all of the Strobe load modules for this version of Strobe have the same version character. Be sure that the PROC for the MSAS started task specifies the correct MSAS load module name. (There must be a one-to-one correspondence between the session manager and the MSAS started tasks, as determined by the version character in the fourth position of the load module names executed with the process for the two started tasks.) STR0715I console id STROBE MEASUREMENT SERVICES release STOP COMMAND RECEIVED FROM CONSOLE

Explanation: The operator issued an MVS STOP command to stop the Measurement Services Address Space (MSAS). System Action: The Measurement Services Address Space (MSAS), which includes AutoStrobe, has terminated. User Response: None required. The address space can be restarted via an MVS MODIFY command to the session manager. This message can also appear on the operators console. STR0716W 64-BIT FORMATTED SAVE AREA ENCOUNTERED, ATTRIBUTION MAY BE INCOMPLETE

Explanation: During attribution, Strobe encountered an AMODE 64-bit program using 64-bit formatted save areas. System Action: User Response: Attribution for the current sample terminates. Measurement continues. None required.

Messages Returned by the Strobe Indexer Programs


The Strobe Indexer programs return the following messages.
STR1104W COMPILER LISTING NOT IN EXPECTED FORMAT - CONTINUING

Explanation: The Indexer cannot successfully process the compiler listing dataset because it cannot find some of the listing data. System Action: The Strobe Indexer lists on SYSPRINT, the system printer output file, an edited display of the map dataset to the point of the error. It then continues by searching for another program. The Indexer produces an incomplete map dataset. Procedure names may not appear in the Strobe Performance Profile. User Response: Ensure that the compiler is supported by the Indexer in use and that the compilation options required for indexing are in effect. STR1105W CSECT LENGTH NOT FOUND The CA Gen Indexer cannot calculate the length of the load module.

Explanation:

System Action: The CA Gen Indexer will continue processing, but the map dataset created is not valid. User Response: Ensure that the compiler source listing used as input to the Indexer is for an application generated by CA Gen. If it is, notify the Strobe system programmer.

Messages Produced by Strobe

3-19

STR1107W

UNKNOWN RECORD TYPE FOUND IN MAP FILE The CA Gen Indexer encountered an unknown record type while creating the

Explanation: map dataset.

System Action: The CA Gen Indexer will continue processing, but the map dataset produced for this source listing is not valid. User Response: STR1108E Contact Compuware Customer Support.

COMPILER LISTING NOT IN EXPECTED FORMAT - MAP DATA SET EMPTY [text]

Explanation: The Indexer cannot successfully process the compiler listing dataset because it cannot find some data that it requires, such as the program name or the procedure code listing. If this message was produced by the C Indexer, one of the following statements appears in text:

BEGINNING OF OBJECT MISSINGthe C Indexer could not find the beginning of the object listing. COMPILE UNIT BLOCK INCOMPLETEthe C Indexer could not find all the information required to complete the literal or compile unit block. COMPILE UNIT BLOCK OR PROLOG NOT FIRSTthe C Indexer did not find a compile unit block or prolog at the beginning of the dataset. END LITERAL MISSINGthe C Indexer could not find all the information needed to complete a literal record. END OF COMMENT NOT FOUNDthe C Indexer could not find the end of a comment. END OF COMPILATION NOT FOUNDthe C Indexer did not find the end of the compiled listing. END OF OBJECT LISTING MISSINGthe C Indexer could not find the end of the object listing. EPILOG RECORD INCOMPLETEthe C Indexer could not find all the information necessary to complete the epilog record. (The epilog is compilergenerated code that follows the program and handles standard linkage.) NAME IN PROCEDURE INCOMPLETEthe C Indexer could not find all the information needed to complete a procedure name. PROCEDURE RECORD INCOMPLETEthe C Indexer could not find all the information needed to complete the procedure record. PROLOG RECORD INCOMPLETEthe C Indexer could not find all the information necessary to complete the prolog record. (The prolog is compilergenerated code that precedes the program and handles standard linkage.) START OR PRIVATE DEFINITION NOT FOUNDthe C Indexer could not find a start definition (SD) or private definition (PD).
System Action: The Indexer produces a null map dataset. Procedure names will not appear in the Strobe Performance Profile. User Response: Ensure that the compiler is supported by the Indexer in use and that the compilation options required for indexing are in effect. STR1109W IEF MAP FILE HEADER RECORD MISMATCH The CA Gen Indexer encountered an error while processing the source listing

Explanation: file.

System Action: The CA Gen Indexer continues processing, but the map dataset produced for this source listing is not valid. User Response: STR1110E Contact Compuware Customer Support.

GETMAIN FAILURE IN modname [RC=rc] - TERMINATING

Explanation: Strobe cannot obtain enough storage for the work area for module modname. The return code, if given, is rc. System Action: User Response: programmer. The Indexer terminates and produces an empty map dataset. Increase the region size and resubmit the request. Notify the Strobe system

3-20

Strobe Messages Guide

STR1111W

MORE THAN 100 LISTING FILES The CA Gen Indexer exceeded its maximum input of 100 source listing files.

Explanation:

System Action: The CA Gen Indexer will produce valid map datasets for the first 100 source listing files and then terminate normally. User Response: Run the CA Gen Indexer with the source listing files that exceeded the maximum of 100, for which the Indexer has not yet created map datasets. STR1112S COMPILER LISTING NOT IN EXPECTED FORMAT - TERMINATING [text]

Explanation: The Indexer cannot successfully process the compiler listing dataset. If the C Indexer produced this message, one of the following statements appears in text:

BEGINNING OF OBJECT MISSINGthe C Indexer could not find the beginning of the object listing. COMPILE UNIT BLOCK OR PROLOG NOT FIRSTthe C Indexer did not find a compile unit block or prolog at the beginning of the dataset. END LITERAL MISSINGthe C Indexer could not find all the information needed to complete a literal record. END OF COMMENT NOT FOUNDthe C Indexer did not find the end of a comment. END OF COMPILATION NOT FOUNDthe C Indexer did not find the end of the compiled listing. END OF OBJECT LISTING MISSINGthe C Indexer could not find the end of the object listing. EPILOG RECORD INCOMPLETEthe C Indexer could not find all the information necessary to complete the epilog record. (The epilog is compilergenerated code that follows the program and handles standard linkage.) ERROR WHILE PROCESSING NAME IN PROCEDUREthe C Indexer encountered an end-of-program statement while processing detail records. LITERAL OR COMPILE UNIT BLOCK INCOMPLETEthe C Indexer could not find all the information required to complete the literal or compile unit block. NAME IN PROCEDURE INCOMPLETEthe C Indexer could not find all the information needed to complete a procedure name. PROCEDURE RECORD INCOMPLETEthe C Indexer could not find all the information needed to complete the procedure record. SOURCE STATEMENT LINE NOT FOUNDthe C Indexer did not find a source statement following the prolog. (The prolog is compiler-generated code that precedes the program and handles standard linkage.) START OR PRIVATE DEFINITION NOT FOUNDthe C Indexer could not find a start definition (SD) or private definition (PD).
System Action: The Indexer lists on SYSPRINT an edited display of the map dataset to the point of error and terminates. The map dataset will affect the Strobe Performance Profile in an unpredictable manner. User Response: Ensure that the compiler is one supported by the Indexer in use and that the compilation options for indexing are in effect. STR1113S LISTING} {OPEN|CLOSE} ERROR ON {DDNAME ddname|STRMAP|SYSPRINT|

Explanation: The Indexer encountered an I/O error on DDNAME ddname, the map dataset STRMAP, the output report dataset SYSPRINT, or the input dataset LISTING. System Action: If the error is for the map dataset or STRMAP, the Indexer terminates and does not produce a map dataset. Otherwise, the Indexer produces an empty map dataset. User Response: Verify the data definition statement or the dataset name. If it is correct, notify the Strobe system programmer. STR1114W IEF LISTING NOT IN EXPECTED FORMAT RC=rc

Explanation: The CA Gen Indexer detected an error in one of the source listing files. The return code, rc, can have the following values indicating that the Indexer failed to locate:

4 - the literal PROGRAM-ID 8 - the literal TEXAS INSTRUMENTS INC or STERLING SOFTWARE

Messages Produced by Strobe

3-21

12 - the literal NAME 16 - the start of the CA Gen source 20 - any executable CA Gen source
System Action: The CA Gen Indexer will continue processing, but the map dataset produced for this source listing will not be valid. User Response: Ensure that the compiler source listing used as input to the Indexer is for an application generated by CA Gen. If it is, notify the Strobe system programmer. STR1115E lang LISTING DATA SET IS EMPTY - TERMINATING The LISTING dataset for the language named in lang is empty. The Indexer terminates and produces an empty map dataset.

Explanation: System Action:

User Response: Ensure that the dataset specified on the input LISTING data definition statement is a valid dataset. If it is, notify the Strobe system programmer. STR1116S lang LISTING NOT IN EXPECTED FORMAT [RC=rc] - TERMINATING

Explanation: The Indexer cannot successfully process the listing for the language named in lang because it is in an unexpected format. The return code, if given, is rc. System Action: The Strobe Indexer terminates. The Indexer lists on SYSPRINT an edited display of the map dataset to the point of the error. The Strobe Performance Profile will display incomplete indexing information. User Response: Ensure that the dataset specified on the input LISTING data definition statement is a valid dataset. If it is, notify the Strobe system programmer. STR1117S SYNAD ERROR, STRXIO text

Explanation: While concatenating map datasets, the Indexer encountered one with different characteristics. System Action: The Indexer terminates. The Indexer lists on SYSPRINT an edited display of the map dataset to the point of the error. The Strobe Performance Profile will contain incomplete indexing information. User Response: of dataset. STR1118S Index the programs again, specifying a separate indexing step for each type

INVALID FUNCTION PASSED TO STRXIO The C Indexer encountered an invalid function.

Explanation:

System Action: The C Indexer terminates and may produce an incomplete map dataset. The resulting Performance Profile may not contain procedure names. User Response: STR1119S Contact Compuware Customer Support.

RECFM NOT SUPPORTED BY INDEXER--LISTING

Explanation: The Indexer encountered a listing dataset whose record format is not FBA, FBM, VBA, or VBM. System Action: The Indexer terminates. The Indexer lists on SYSPRINT an edited display of the map dataset to the point of the error. The Strobe Performance Profile displays incomplete indexing information. User Response: Recompile the programs using a SYSPRINT dataset formatted as FBA, FBM, VBA, VBM, and resubmit the indexing request. STR1120E DSORG PO WITHOUT MEMBER NAME NOT VALID FOR LISTING [(+nnnn)]

Explanation: The listing dataset specified is partitioned, but you did not include a member name in the request. If specified, (+nnnn) indicates the relative number of the dataset in the error within the LISTING concatenation. System Action: User Response: The Indexer terminates and does not produce a map dataset. Resubmit the indexing request, and specify the member name.

3-22

Strobe Messages Guide

STR1121W

INDEXER SYSPRINT DCB INCORRECT-CONTINUING The SYSPRINT file from the compiler has incorrect DCB parameters. The Indexer terminates and does not produce a map dataset.

Explanation: System Action:

User Response: Refer to the Strobe User Guide for the correct parameters based on language type. Enter the proper parameters and resubmit the request. STR1125E {MAP | LISTING} DATA SET NOT SPECIFIED The Indexer JOB STEP did not specify the STRMAP DD or LISTING DD The Indexer terminates and does not produce a map dataset. Specify the missing data definition statement and resubmit the request.

Explanation: statement. System Action: User Response: STR1126E

LISTING DATA SET MUST BE PARTITIONED OR PHYSICAL SEQUENTIAL [(+nnnn)]

Explanation: The listing dataset specified to the Strobe Indexer has a dataset organization other than partitioned or physical sequential. If specified, (+nnnn) indicates the relative number of the dataset in error within the concatenation. System Action: The Indexer terminates and does not produce a map dataset.

User Response: Specify a listing dataset that is either a member of a partitioned dataset or a sequential dataset, and resubmit the request. STR1127E DSORG PO WITHOUT MEMBER NAME NOT VALID FOR MAP The map dataset was partitioned, but no member name was included in the The Indexer terminates and does not produce a map dataset. Resubmit the indexing request and specify the member name.

Explanation: request. System Action: User Response: STR1128E

MAP FILE CANNOT SPECIFY A CONCATENATION

Explanation: The STRMAP DD statement, which points to the map datasets, specifies a concatenation of datasets. System Action: User Response: statement. STR1129E The Indexer terminates and does not produce a map dataset. Resubmit the request and specify a single map dataset in the STRMAP DD

MEMBER NAME INVALID WITH SEQUENTIAL DATA SET ddname [(+nnnn)]

Explanation: The dataset with ddname ddname had a physical sequential organization but was specified with a member name. If present, (+nnnn) indicates the relative number of the dataset in error within the concatenation. System Action: The Indexer terminates and does not produce a map dataset.

User Response: Specify either the name of a physical sequential dataset, or a partitioned organization dataset with a member name. STR1130I RDJFCB MACRO RETURN CODE = rc REASON CODE = rsncode FOR {LISTING | MAP} Explanation: Strobe encountered an internal error in the Indexer when attempting to verify the listing or map dataset. The RDJFCB macro returned a code of rc for ddname ddname. RDJFCB in the ARL (Allocation Retrieval List) field ARLCODE returned a reason code of rsncode. System Action: The Indexer does not perform any further dataset verification. It will, however, attempt to index the LISTING datasets. User Response: STR1131I Notify the Strobe system programmer.

OBTAIN MACRO RETURN CODE = rc FOR {LISTING | MAP} [(+nnnn)]

Explanation: Strobe encountered an internal error in the Indexer when attempting to verify the listing or map dataset. The OBTAIN macro returned a code of rc. If specified, (+ nnnn) indicates the relative number of the dataset within the concatenation.

Messages Produced by Strobe

3-23

System Action: The Indexer does not perform any further dataset verification. It will, however, attempt to index the listing datasets. User Response: STR1132E Notify the Strobe system programmer.

{LISTING | MAP} NOT FOUND ON VOLUME volume [(ddname +nnnn)]

Explanation: A map or listing dataset was not found on volume volume. If the ddname is concatenated, (ddname +nnnn) indicates the ddname and the datasets relative position in the concatenation. System Action: The Indexer terminates.

User Response: Ensure that the specified dataset name is correct. If the name is correct, and the dataset is cataloged, it may have been deleted from the volume in which it existed. If it is uncataloged, the volume specified may be incorrect. STR1133E MAP DATA SET MUST BE PARTITIONED OR PHYSICAL SEQUENTIAL

Explanation: The map dataset name specified for the STRMAP DD statement has a dataset organization other than physical sequential or partitioned. System Action: The Indexer terminates and does not produce a map dataset.

User Response: Specify a listing dataset that is a physical sequential dataset or a member of a partitioned dataset, and resubmit the request. STR1200E STRXNAT - INTERNAL ERROR The Strobe Natural Indexer has encountered an unknown condition.

Explanation:

System Action: The Strobe Natural Indexer terminates and may not produce a map dataset, or may produce an empty map dataset. User Response: STR1201E Notify the Strobe system programmer.

STRXNAT - ERROR OPENING {LISTING|MAP} DATA SET

Explanation: The Strobe Natural Indexer was unable to open the input listing dataset (the LISTING DD statement), or the output map dataset (the STRMAP DD statement). System Action: The Strobe Natural Indexer terminates and does not produce a map dataset.

User Response: Verify the data definition statement or the dataset name. If it is correct, notify the Strobe system programmer. STR1202E STRXNAT - COULDN'T FIND {DIRECTORY RECORD|SOURCE CODE} IN LISTING

Explanation: The Strobe Natural Indexer has encountered one of three possible conditions. The input listing dataset (the LISTING DD statement) that was produced by Natural and input to the Strobe Natural Indexer was: 1. Empty 2. Incorrectly produced 3. Produced by a version of Natural that the Strobe Natural Indexer does not support at the current maintenance level. System Action: The Strobe Natural Indexer terminates and may not produce a map dataset.

User Response: For conditions 1 and 2, refer to the Strobe for Adabas/Natural option manual for information on procedures available to produce Natural program listings suitable for input to the Strobe Natural Indexer. For condition 3, notify the Strobe system programmer. STR1203E STRXNAT - SOURCE LISTING INCOMPLETE

Explanation: The input listing dataset (the LISTING DD statement) has reached an end-offile condition prior to returning to the main Natural program from a nested (included) program. One (but not the only) possible cause of this is an out-of-space condition that was received while producing the listing dataset (the CMPRINT DD statement in the UNLOAD step of either the STROXN or STROXNAT procedures). System Action: The Strobe Natural Indexer terminates and may produce an incomplete map dataset. The Strobe Performance Profile will display incomplete indexing information. User Response: Verify that the input listing dataset contains the Natural end-of-listing indicator (***** End of List *****) in either the last or next-to-last line of the dataset. If the

3-24

Strobe Messages Guide

listing dataset does not contain this indicator, rerun the UNLOAD step. If the listing dataset does contain this indicator, notify the Strobe system programmer. STR1300E ERROR erc DETECTED BY MODULE STRXVPLI

The PL/I Indexer cannot successfully process the compiler listing dataset because module STRXVPL1 encountered error code erc.
System Action: incomplete. Strobe terminates indexing. If a map dataset is produced, it could be

The following are the possible error codes that can be returned: 001
Explanation: The compiler listing is not complete, the wrong compiler options were specified, the SYSPRINT output from the PL/1 compiler was not specified as the input, Strobe did not recognize the PL/1 compiler or had an internal failure. User Response: If the compiler listing is not complete, then recompile the program. If the wrong compiler options were specified, check that you are using the compiler options in the Strobe User Guide and recompile the program. If the wrong dataset was specified as input, specific the SYSPRINT dataset from the PL/1 compiler and create the map dataset again. If Strobe did not recognize the PL/1 compiler or had an internal failure, contact Compuware Customer Support.

002
Explanation: Strobe did not find the keyword OFFSET in the header of the compiler listing.

User Response: If the SYSPRINT dataset from the PL/1 compiler was not specified as the input, specify the SYSPRINT dataset and create the map dataset again. If the listing is a valid PL/1 compiler listing, contact Compuware Customer Support.

003
Explanation: Strobe did not find the keyword LINE# in the header of the compiler listing.

User Response: If the SYSPRINT dataset from the PL/1 compiler was not specified as the input, specify the SYSPRINT dataset and create the map dataset again. If the listing is a valid PL/1 compiler listing, contact Compuware Customer Support.

004
Explanation: listing. Strobe did not find the keyword OBJECT CODE in the header of the compiler

User Response: If the SYSPRINT dataset from the PL/1 compiler was not specified as the input, specify the SYSPRINT dataset create the map dataset again. If the listing is a valid PL/1 compiler listing, contact Compuware Customer Support.

006
Explanation: Strobe did not find the keyword FILE# in the header of the compiler listing.

User Response: If the SYSPRINT dataset from the PL/1 compiler was not specified as the input, specify the SYSPRINT dataset and create the map dataset again. If the listing is a valid PL/1 compiler listing, contact Compuware Customer Support.

010
Explanation: Strobe found the keyword End of Prologue where it was not expected.

User Response: Because the PL/1 compiler listing is not in the expected format, contact Compuware Customer Support.

014
Explanation: GETMAIN failed to get the required size of the work area.

User Response: Increase the region size on the JOBCARD or on the EXEC statement, and create the map dataset again. If the failure persists, contact Compuware Customer Support.

015
Explanation: The number of entries in the internal table file used by Strobe exceeded 400.

Messages Produced by Strobe

3-25

User Response:

Contact Compuware Customer Support.

016
Explanation: The number of lines of code in the PL/1 compiler listing exceeded 50,000 lines. This number does not count the lines of code from included files. User Response: Contact Compuware Customer Support.

017
Explanation: The number of lines of code in the PL/1 compiler listing exceeded 60,000 lines. This number does count the lines of code from included files. User Response: STR1405E Contact Compuware Customer Support.

GETMAIN FAILURE IN STRXDBRM - TERMINATING

Explanation: Strobe cannot obtain enough storage for the work area for module STRXDBRM. System Action: User Response: STR1408E The Indexer terminates and does not produce a map dataset. Increase the region size and resubmit the request.

DBRM DATA SET IS EMPTY The member of the DBRM partitioned dataset that you specified is empty. The DB2 Indexer terminates and does not produce a map dataset.

Explanation: System Action:

User Response: Ensure that the dataset specified on the input listing data definition statement is a valid DBRM dataset. If it is, notify the Strobe system programmer. STR1412S DBRM MEMBER NOT IN EXPECTED FORMAT - TERMINATING

Explanation: The DB2 Indexer cannot successfully process the DBRM source text because one or more of the DBRMs is in an unexpected format. System Action: The DB2 Indexer terminates. If the DISPLAY MAP option was selected when the ADD request was submitted, the Indexer lists on SYSPRINT an edited display of the map dataset to the point of the error. The Strobe Performance Profile displays incomplete indexing information. User Response: Ensure that the dataset specified on the input listing data definition statement is a valid DBRM dataset. If it is, notify the Strobe system programmer. STR1413S OPEN ERROR ON DDNAME {SYSPRINT|STRMAP|LISTING}

Explanation: The DB2 Indexer encountered an error while attempting to open the report output dataset SYSPRINT, the map dataset STRMAP, or the input dataset listing. A data definition statement may be missing or not valid. System Action: The Indexer terminates and does not produce a map dataset.

User Response: Verify the data definition statement. If it refers to a valid dataset, notify the Strobe system programmer.

Messages Returned by the Strobe History Manager


The Strobe History Manager returns the following messages.
STR1800E SYSTEM SERVICE FAILED (sysserve) ddname - RC=rc ERC=erc

Explanation: The system service sysserve for ddname ddname failed. The return code is rc, and the reason code, if given, is erc. System Action: User Response: STR1801E The history manager may terminate. Notify the Strobe system programmer.

CREATE INTERNAL ERROR - HGWA ALREADY EXISTS A duplicate call was made to build a history global work area (HGWA). The history manager terminates.

Explanation: System Action:

3-26

Strobe Messages Guide

User Response: STR1802E

Contact Compuware Customer Support.

fnctname INTERNAL ERROR - HGWA DOES NOT EXIST

Explanation: A function fnctname failed because Strobe could not find a history global work area (HGWA) control block. System Action: User Response: STR1803E The history manager terminates. Contact Compuware Customer Support.

fnctname - ddname DATA SET NOT OPERATIONAL

Explanation: While executing function fnctname, Strobe found the dataset that ddname ddname refers to is not operational. System Action: User Response: STR1804E The history manager terminates. Contact Compuware Customer Support.

fnctname - ddname ENVIRONMENT NOT ESTABLISHED

Explanation: Strobe attempted to use the dataset referred to by ddname ddname without first building the necessary control blocks. The function name that detected the error is fnctname. System Action: User Response: STR1805E The history manager terminates. Contact Compuware Customer Support.

OPEN - ddname DATA SET ALREADY OPEN

Explanation: Strobe attempted to open the dataset that ddname ddname refers to and found that it was already opened. System Action: User Response: STR1806E The history manager terminates. Notify the Strobe system programmer.

fnctname - ddname HGWA CORRUPTION DETECTED

Explanation: While processing a call for function fnctname and ddname ddname, Strobe detected history global work area (HGWA) corruption. System Action: User Response: STR1807E The history manager terminates. Contact Compuware Customer Support.

fnctname - ddname DATA SET NOT OPEN

Explanation: Strobe function fnctname found that the dataset that ddname ddname refers to was already closed. System Action: User Response: STR1808E The history manager terminates. Contact Compuware Customer Support.

fnctname - ddname PLIST MISSING OR INVALID

Explanation: While processing a call for function fnctname and ddname ddname, Strobe found that the parameter list was missing or invalid. System Action: User Response: STR1809E The history manager terminates. Contact Compuware Customer Support.

fnctname - ddname QPL POINTER INVALID AT address

Explanation: While processing function fnctname for ddname ddname, Strobe found that the history parameter list pointer at address addr was invalid. System Action: User Response: STR1810S The history manager terminates. Contact Compuware Customer Support.

ddname DATA SET NOT ALLOCATED

Explanation: During startup, Strobe determined that the dataset that ddname ddname refers to was missing. Strobe requires that this dataset be allocated.

Messages Produced by Strobe

3-27

System Action:

The history manager terminates.

User Response: Ask the Strobe system programmer to correct the history manager JCL and restart the history manager. STR1811S OSER - ddname RESERVE ALREADY OUTSTANDING

Explanation: Strobe attempted to issue two reserves for the same history dataset that ddname ddname refers to. System Action: User Response: STR1812S The history manager terminates. Contact Compuware Customer Support.

fnctname - ddname RESERVE NOT ISSUED

Explanation: In the function fnctname, Strobe attempted to open the dataset that ddname ddname refers to without first reserving it. System Action: User Response: STR1813W The history manager terminates. Contact Compuware Customer Support.

OPEN - ddname VSAM OPEN STATUS RC=rc RSN=rsn

Explanation: Strobe determined that the dataset that ddname ddname refers to was not properly closed and that VSAM has performed an implicit VERIFY. The VSAM return code is rc, and the VSAM reason code is rsn. System Action: User Response: STR1814E Strobe continues processing normally. Notify the Strobe system programmer.

OPEN - ddname UNABLE TO INITIALIZE DATA SET RC=rc

Explanation: Strobe was unable to complete the initialization of the dataset that ddname ddname refers to. The VSAM return code is rc. System Action: User Response: STR1815E The history manager terminates. Contact Compuware Customer Support.

fnctname - failingfnct ddname STATUS RC=rc RSN=rsn

Explanation: A function, failingfnct, failed for the dataset that ddname ddname refers to. The return code of the failed function is rc, and the reason code of the failed function is rsn. fnctname is the function currently executing. System Action: User Response: STR1816E The history manager terminates. Contact Compuware Customer Support.

DD FIND - ddname DDNAME INVALID The ddname referred to by ddname is invalid. The history manager terminates. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR1817E

DD FIND - ddname DSNAME TABLE POINTER INVALID AT addr

Explanation: Strobe found that the dataset table pointer in the ddname table referred to by ddname is invalid at address addr. System Action: User Response: STR1818E The history manager terminates. Contact Compuware Customer Support.

ddname - DATA SET IS FULL The dataset identified in ddname is full.

Explanation:

System Action: If you receive this message while producing Performance Profile reports, Strobe will produce the reports, but no history information will be added to the history database. If you receive this message while accessing Strobe/ISPF panels to add a measurement session history or cost record, the measurement session history record will not be added to the database.

3-28

Strobe Messages Guide

User Response: Notify the Strobe system programmer. As a temporary measure, you may delete unneeded measurement session history records from the history dataset. The Strobe system programmer can allocate a larger history dataset and use the IDCAMS utility to copy information from the previous history dataset to the newly created history dataset. STR1819I HISTORY DATA SET STRUCTURES REMOVED Strobe disabled the history file processing. Strobe continues processing. None required.

Explanation: System Action: User Response: STR1820E

STRH INTERNAL ERROR. ERROR CODE = erc

Explanation: Strobe encountered an error while attempting to access the history database. The error code is given in erc. System Action: If this error occurred while producing Performance Profile reports, Strobe will produce reports but no history information will be added to the history database. If this error occurred while you were accessing or modifying the history database through Strobe/ISPF, the history database will be disabled. User Response: STR1821E If the problem persists, contact Compuware Customer Support.

DATASTORE ENVIRONMENT NOT ESTABLISHED The system resources required for the history data temporary storage area are

Explanation: not available.

System Action: If this error occurred while producing Performance Profile reports, Strobe will produce reports but no history information will be added to the history database. If this error occurred while you were accessing or modifying the history database using Strobe/ISPF, the history database will be disabled. User Response: STR1822E If the problem persists, contact Compuware Customer Support.

DATASTORE FUNCTION FAILED: errortext

Explanation: Strobe encountered an error accessing a temporary storage area. The reason for the error is described in errortext. System Action: If this error occurred while producing Performance Profile reports, Strobe will produce reports but no history information will be added to the history database. If this error occurred while you were accessing or modifying the history database using Strobe/ISPF, the history database will be disabled. User Response: STR1823W If the problem persists, contact Compuware Customer Support.

STRHLOG NOT ALLOCATED. LOGGING DISABLED

Explanation: The message log file for measurement session history collection and reporting has not been allocated. System Action: Strobe will not write messages to the history log, but all other measurement session history collection and reporting will continue normally. User Response: Allocate a log file for measurement session history collection and reporting and resubmit the request. STR1824W ERROR {OPENING | CLOSING} STRHLOG. LOGGING DISABLED

Explanation: Strobe encountered an error attempting to open or close the log file for measurement session history collection and reporting. System Action: Strobe will not write messages to the history log, but all other measurement session history collection and reporting will continue normally. User Response: STR1825W Notify the Strobe system programmer.

INCORRECT DCB OPTIONS FOR STRHLOG. LOGGING DISABLED The DCB parameters for the history log file are not correct.

Explanation:

System Action: Strobe will not write messages to the history log, but all other measurement session collection and reporting will continue normally.

Messages Produced by Strobe

3-29

User Response: Review the instructions for allocating the history log file described in the Strobe Installation and Customization Guide and reallocate the dataset. STR1826W SWAREQ FAILED. RC=rc. LOGGING DISABLED A call to an MVS service, SWAREQ, failed. Log functions will not operate. Strobe continues processing, but there will be no history log. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR1827W

fnctname FOR STRHLOG FAILED. LOGGING DISABLED Function fnctname for log processing failed. The history log is disabled. Strobe continues processing, but there will be no history log. Notify the Strobe system programmer.

Explanation: System Action: User Response:

STR1828W STRHLOG I/O ERROR ENCOUNTERED. SENSE BYTES: xxx STATUS BYTES yyyy. LOGGING DISABLED Explanation: System Action: User Response: STR1829E An I/O error occurred while processing the history log. Strobe continues processing but will not process history log information. Notify the Strobe system programmer.

STORAGE ALLOCATION FAILED An attempt to obtain storage allocation failed. All Strobe measurement session history collection and reporting is disabled. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR1830W

ABEND IN LOG PROCESSING. LOGGING DISABLED. Strobe experienced an ABEND processing log functions. Strobe continues processing, but there will be no history log. Notify the Strobe system programmer.

Explanation: System Action: User Response:

STR1831E RECOVERY ENVIRONMENT COULD NOT BE ESTABLISHED. RETURN CODE rc. REASON CODE reascode Explanation: System Action: User Response: STR1832E Strobe could not establish a recovery environment. All Strobe measurement session history collection and reporting is disabled. Notify the Strobe system programmer.

STROBE CANNOT WRITE TO {STRHPRNT | STRHEXPT} FILE STATUS ##

Explanation: Strobes attempt to write to either the print file (STRHPRNT) or the export file (STRHEXPT) failed. The file status is ##. System Action: Strobe continues processing but will not print or export the measurement session history record. User Response: STR1833E Contact the Strobe system programmer.

INVALID CALL TO {PRINT | EXPORT}, DATASTORE IS datastore

Explanation: While processing datastore datastore, Strobe received an illegal call to either the print or export function. System Action: Strobe continues processing but the measurement session history record will not be printed or exported. User Response: STR1834E Contact the Strobe system programmer.

EMPTY DATASTORE PASSED TO {EXPORT | PRINT | COMPARE}

Explanation: A call was made to either the export, print, or compare function, but the datastore contained no data.

3-30

Strobe Messages Guide

System Action: Strobe continues processing, but will not export or print the measurement session history record, or compare it to the baseline value. User Response: STR1835S Contact the Strobe system programmer.

ERROR - DEFAULT COST PARM MISSING/INVALID

Explanation: The first parameter in the SYSIN dataset for the cost record installation program was not DEFAULTCOST=( System Action: User Response: STR1836S The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

ERROR - INVALID PARM INPUT

Explanation: Either the last character in the parameter field was not a right parenthesis ) or a blank record was entered in the SYSIN dataset. System Action: User Response: STR1837S The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

ERROR - INCONSISTENT INPUT DATA

Explanation: A service unit parameter was combined with CPU and I/O cost parameters. When you initialize cost records, you can use either service units costs or CPU and I/O costs, but not both. System Action: User Response: STR1838S The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

ERROR LOADING HISTORY MANAGER The cost record installation program was unable to locate the history manager The cost record installation program terminates.

Explanation: component.

System Action:

User Response: Review the Strobe history manager instructions in the Strobe Installation and Customization Guide and verify that the appropriate Strobe libraries are loaded. If the problem persists, contact Compuware Customer Support. STR1839S ERROR - INVALID PRIME CPU COST ENTRY PRIMECPU data is not in the form nnnnn.nn. The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

Explanation: System Action: User Response: STR1840S

ERROR - INVALID PRIME IO COST ENTRY PRIMEIO data is not in the form nnnnnn.nnn. The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

Explanation: System Action: User Response: STR1841S

ERROR - INVALID PRIME SU COST ENTRY PRIMESU data is not in the form nnnnn.nnn. The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

Explanation: System Action: User Response: STR1842S

ERROR - INVALID/MISSING PRIME TIME START ENTRY PRIMESTART data is missing or not in the form nnnn. The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

Explanation: System Action: User Response: STR1843S

ERROR - INVALID/MISSING PRIME TIME END ENTRY PRIMEEND data is missing or not in the form nnnn.

Explanation:

Messages Produced by Strobe

3-31

System Action: User Response: STR1844S

The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

ERROR - INVALID NONPRIME CPU COST ENTRY NONPRIMECPU data is not in the form nnnnn.nn. The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

Explanation: System Action: User Response: STR1845S

ERROR - INVALID NONPRIME IO COST ENTRY NONPRIMEIO data is not in the form nnnnnn.nnn. The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

Explanation: System Action: User Response: STR1846S

ERROR - INVALID NONPRIME SU COST ENTRY NONPRIMESU data is not in the form nnnnn.nnn. The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

Explanation: System Action: User Response: STR1847S

ERROR - INVALID PARM VALUE - parmvalue An invalid parameter value, parmvalue, was entered in the SYSIN dataset. The cost record installation program terminates. Correct the SYSIN dataset and rerun the program.

Explanation: System Action: User Response: STR1848E

DELETE FAILED. RECORD BEING ACCESSED BY ANOTHER USER The DELETE request failed because another user is accessing this record. Strobe does not process the request. Retry the DELETE request when the record is not being used.

Explanation: System Action: User Response:

Messages Returned by AutoStrobe


AutoStrobe returns the following messages.
STR1900I INITIALIZATION OF AUTOSTROBE IN STRxMSAS IN PROCESS

Explanation: Processing in the Measurement Services Address Space (MSAS) has attached the AutoStrobe control task and AutoStrobe initialization processing has started. System Action: User Response: STR1901I AutoStrobe initialization continues. None required.

INITIALIZATION OF AUTOSTROBE IN STRxMSAS IS COMPLETE

Explanation: Initialization of AutoStrobe is complete. Any AutoStrobe requests that existed at the time when AutoStrobe was last operational are reestablished. System Action: User Response: STR1902E AutoStrobe initialization continues. None required. New AutoStrobe requests can be submitted.

AUTOSTROBE INITIALIZATION TERMINATED. text of reason

Explanation: AutoStrobe initialization processing encountered an error that would cause problems in subsequent attempts to perform AutoStrobe processing. The text of reason can be:

UNABLE TO OBTAIN WORKING STORAGE SMF TYPE 30 RECORDS NOT BEING COLLECTED UNABLE TO ATTACH AN AUTOSTROBE SUBTASK, RETCODE=xx

3-32

Strobe Messages Guide

UNABLE TO ADD DYNAMIC EXIT {STRBAUSI|STRBACTR}, RETCODE=xx REASON=yyyy ERROR IN REQUEST PROCESSING xxx STRBAEVT DID NOT INITIALIZE
System Action: AutoStrobe initialization processing is terminated

User Response: Based on the reason indicated, validate the environment in which the Strobe session manager and Measurement Services Address Space (MSAS) are running. STR1903I {MEASUREMENT INITIATED | WARNING STATE APPLIED | FOR AUTOSTROBE REQUEST xxxx, PROGRAM program OF JOB jobname BECAUSE OF condition Explanation: AutoStrobe detected abnormal behavior in the designated job and either initiated a Strobe measurement of that program or defined a warning that can be displayed by the user. The abnormal behavior is described by the condition text listed in the message. This text also appears on the Measurement Session Data report. The conditions for which Strobe will initiate a measurement include:

EXCESSIVE ELAPSED TIME EXCESSIVE TCB TIME ABNORMAL I/O ACTIVITY - EVENT x EXCESSIVE CPU TIME IN TRANSACTION nnnn, THRESHOLD=ssss SECONDS, ACTUALS=ssss SECONDS EXCESSIVE RESPONSE TIME IN TRANSACTION nnnn, THRESHOLD=ssssss SECONDS, ACTUALS=ssssss SECONDS For abnormal I/O activity, the event number designates the I/O threshold event that was exceeded by the monitored program. (See the description of the AUTOIOEVENTx parameters in the Strobe User Guide.)
System Action: AutoStrobe processing continues. AutoStrobe places the measured program into a held state which means that subsequent executions of the job with this name will not be monitored until it is released using Strobe/ISPF. User Response: If a measurement was initiated, generate a Performance Profile, analyze it and make any appropriate corrections to the program code. To enable AutoStrobe to resume monitoring of the program, enter a release to change its status from held to pending. If changes to a batch program invalidate basis data for the measurement, you can delete it and AutoStrobe will collect new basis data for the next ten monitorings of the batch program. STR1904I MEASUREMENT FOR AUTOSTROBE REQ xxxx PGM zzzz jOB yyyy DELETED INSUFFICIENT MEASUREMENT DURATION Explanation: A program measurement initiated by AutoStrobe was discarded because either the elapsed time accumulated after the measurement was initiated was determined to be insufficient for a valid measurement. REQ xxxx identifies the AutoStrobe request associated with this program. System Action: AutoStrobe processing continues and creates ADD QUEUED request to measure the next execution of the program. The status of the AutoStrobe measurement request for this program remains held-ms. User Response: None required.

STR1905E AUTOSTROBE DID NOT MONITOR PROGRAM progname UNDER JOB jobname CODE={ETxx|TTxx|IOxx|TMxx} REQUEST xxxx Explanation: AutoStrobe was unable to either start or complete monitoring of a program covered by the designated AutoStrobe request. The first two characters of CODE identify the AutoStrobe condition that detected the event that caused monitoring to stop. The second two characters are a numeric code that identifies the event. System Action: User Response: STR1906I AutoStrobe processing for other monitored programs continues. Report this message to Compuware Customer Support.

AUTOSTROBE DID NOT MONITOR PROGRAM progname UNDER JOB jobname reason

Explanation: AutoStrobe detected the initiation of a program covered by an existing AutoStrobe request, but did not monitor it for one of the following reasons:

Messages Produced by Strobe

3-33

MAXIMUM NUMBER OF PROGRAMS ARE CURRENTLY BEING MONITORED JOB IS NOT A BATCH JOB OR STARTED TASK ISSUER OF REQUEST NOT AUTHORIZED FOR JOB MAXIMUM NUMBER OF CICS REGIONS ARE ALREADY BEING PROCESSED REGION SPECIFIED ON AN IMMEDIATE REQUEST IS NOT EXECUTING VERIFICATION OF CICS ENVIRONMENT IN REGION FAILED
AutoStrobe processing continues.

System Action:

User Response: If the first or fourth message reason appears, no action is required or you can increase the AUTOMAX parameter value. If the third message reason appears, check the job name specified on the request and consider resubmitting the request by someone with authorization to the job(s) designated in the request. For the sixth message reason, verify that a CICS region was submitted in the request. STR1907I STATUS OF AUTOSTROBE REQUEST xxxx CHANGED TO {MONITOR|PENDING|HELD{MS|WN| AC|US}} Explanation: The initiation or termination of the program associated with the designated request or an action by AutoStrobe or a user has caused the status of the designated request to be changed. System Action: User Response: STR1909E AutoStrobe processing continues. None required.

ERROR PROCESSING DATA FOR REQUEST xxxx, RETCODE=xx, REASON CODE=yyy

Explanation: AutoStrobe encountered an error reading or writing data about the designated request. RETCODE designates the return code from the function that was attempting to access the data. The REASON CODE identifies the data that was being processed. System Action: AutoStrobe processing continues. Reason codes 101, 102, and 106 indicate this execution of the program associated with the request is not monitored. Reason codes 103, 104, and 105 indicate that the data associated with this monitoring cannot be saved. User Response: Report the message to Compuware Customer Support.

STR1910E AUTOSTROBE REQUEST xxxx PROGRAM progname UNDER JOB jobname NOT MONITORED FOR {ELAPSED TIME | TCB TIME | I/O ACTIVITY | TRANSACTION RESPONSE TIME |TRANSACTION CPU TIME CCxx} Explanation: AutoStrobe encountered an event or error in its monitoring that has caused it to stop monitoring the program for the specified condition. This message sometimes reflects an error but is often issued for normal events such as the termination of monitoring for I/O activity when the monitored program has no basis data for I/O. CC identifies the AutoStrobe condition that detected the event that caused monitoring to be stopped. xx is a numeric code that identifies the event. System Action: AutoStrobe stops its monitoring of the designated program for the specified condition. AutoStrobe monitoring for other conditions during the program execution proceeds. User Response: STR1911E Report the message to Compuware Customer Support.

THRESHOLD FOR ERROR, CODE=xxx EXCEEDED, AUTOSTROBE TERMINATED

Explanation: The number of errors designated by CODE=xxx has exceeded a threshold designated by that error type. The AutoStrobe routine that detected these errors initiated the termination of AutoStrobe. The error codes are those found in messages STR1909E and STR1914E. System Action: The Measurement Services Address Space (MSAS) in which this version of AutoStrobe is running will attempt to restart AutoStrobe up to 3 times in a fifteen minute interval. User Response: Report the message to Compuware Customer Support.

STR1912E AUTOSTROBE AUTOMONITOR ENDED FOR JOB <jobnumber> PROGRAM <programname> REQUEST <requestnumber> CODE=<code> Explanation: System Action: AutoStrobe encountered a problem indicated by code. AutoStrobe stops monitoring programname.

3-34

Strobe Messages Guide

User Response: this message.

Contact Compuware Customer Support with the information provided in

STR1913I MONITORING DATA FOR AN EXECUTION OF A PROGRAM zzzzzzz OF JOB yyyyyy WAS DISCARDED - INSUFFICIENT ELAPSED TIME Explanation: AutoStrobe was collecting basis data for the designated program and its monitoring of this execution found only a small amount of elapsed time. If this minimal activity is part of the basis data, it reduces the composite values in the basis data to levels that are far lower than the norm for that program when it is performing its designated function(s). System Action: The data collected during the monitoring of the designated program is not added to that programs basis data. AutoStrobe processing continues. User Response: None required.

STR1914E AUTOSTROBE requesttype REQ xxxx VSAM ERROR, FUNC=cc, VSAM RET/REASON CODES - xxxx yyyy STR1914E AUTOSTROBE requesttype REQ xxxx VSAM ERROR, KEY= xxxxxxxxxxxxxxxx

Explanation: AutoStrobe experienced an error when reading or writing a record to or from the AutoStrobe dataset for request xxxx. Request types include: Transaction monitoring Create Transaction Candidates AutoMeasure Batch monitoring

FUNC=cc specifies the VSAM operation that failed. KEY identifies the record that was be accessed on the AutoStrobe dataset. VSAM RET/REASON CODES specify the VSAM return code and reason code for the failed operation.
System Action: AutoStrobe marks the request as complete. Other Strobe and AutoStrobe processing continues. User Response: Save the Strobe log in which this message appears and contact Compuware Customer Support. STR1915I AUTOSTROBE {MEASUREMENT|WARNING STATUS} FOR REQ xxxx PGM ppppp

Explanation: AutoStrobe detected abnormal behavior in the designated program running under the designated job and either initiated a Strobe measurement of that program or defined a warning that can be displayed by the user. A text description of this condition appears on the Measurement Session Data report for the measurement. The conditions for which AutoStrobe will initiate a measurement include:

EXCESSIVE ELAPSED TIME EXCESSIVE TCB TIME ABNORMAL I/O ACTIVITY.


System Action: AutoStrobe processing continues. AutoStrobe has put the request associated with the measurement in the held-ms (measurement) or held-wn (warning) state. As a result, subsequent executions of the program (under the job and step names in the request) will not be monitored until the user releases the request via Strobe/ISPF User Response: If the measurement was initiated, generate a Performance Profile for it, analyze it, and correct the measured program. To cause AutoStrobe to resume monitoring of the program, release the measurement via Strobe/ISPF to change its status from held to pending. If changes to the measured program invalidate the basis data on which the measurement was based, you many want to delete that basis data. This action causes AutoStrobe to collect new basis data on the first 10 subsequent monitorings of the program. STR1916E AUTOSTROBE HAS BEEN TERMINATED, REASON CODE = xxx

Explanation: An AutoStrobe function has detected an error that is serious enough to cause termination of this version of AutoStrobe. This message is preceded by one or more messages that describe the error(s) that cause the termination. System Action: The Measurement Services Address Space (MSAS) in which this version of AutoStrobe is running will attempt to restart AutoStrobe up to three times after the initial failure in any fifteen minute interval.

Messages Produced by Strobe

3-35

User Response: Check the Strobe log for the AutoStrobe messages that precede this one. They will provide more detail about the error that forced the termination of AutoStrobe. Report this message to Compuware Customer Support. STR1919W LOAD FAILED FOR FAULT-MANAGER STUB ROUTINE, ABEND CODE=Sxxx-xx

Explanation: AutoStrobe-monitoring initialization processing was unable to load Strobes Fault-Manager stub routine (STRBSFMX). Sxxx-xx shows the abend and reason codes that would have been presented if the invocation of the MVS LOAD service had abended. System Action: AutoStrobe-monitoring initialization continues but there will be no notification to the Fault Manager for any abnormal behavior that is subsequently detected by AutoStrobes monitoring. User Response: Notify the Strobe system programmer. Check the library from which this version of Strobe was loaded and ensure that it contains module STRvSFMX, where v is the version character for the instance of Strobe that issued this message. STR1920I AUTOSTROBE HAS BEEN STOPPED The operator issued the MVS MODIFY command to stop AutoStrobe and it

Explanation: worked.

System Action: Session manager and Measurement Services Address Space (MSAS) processing continues. AutoStrobe is inoperative. User Response: STR1921I None required.

AUTOSTROBE HAS BEEN STARTED The operator issued the MVS MODIFY command to start AutoStrobe and it

Explanation: worked.

System Action: Session manager and Measurement Services Address Space (MSAS) processing continues. AutoStrobe is operative. User Response: None required.

STR1922I MODIFY msasname {STOPAUTO|STARTAUTO} COMMAND IGNORED, AUTOSTROBE IS ALREADY {STOPPED|STARTED} Explanation: The operator issued the MVS MODIFY command to start or stop AutoStrobe when it was already in the state specified in the command. System Action: Session Manager and Measurement Services Address Space (MSAS) processing continues. AutoStrobe operational status remains unchanged. User Response: STR1923I None required.

MODIFY jobname text COMMAND REJECTED reason

Explanation: The operator issued the MVS MODIFY command to the Measurement Services Address Space (MSAS), but the command failed. The possible reasons for failure include: AUTOSTROBE MONITORING IS NOT ACTIVE ACTION SPECIFIED IN TEXT IS NOT SUPPORTED AUTOMEASURE UTILITY IS UPDATING THE LOAD-MODULE LIST AUTOSTROBE INSTALLATION PARAMETER NOT SPECIFIED INVALID PARAMETER TEXT

System Action: Session Manager and Measurement Services Address Space (MSAS) processing continues. User Response: If AutoStrobe monitoring is not active, verify that your installation is licensed for AutoStrobe and the Strobe installation parameter, AUTOMONITOR, is set to YES. If the action specified is not supported, verify the spelling and syntax of the MODIFY command and reissue it. If the AutoMeasure load module list is being updated, reissue the MODIFY LMLISTREF command after the AutoMeasure program list utility completes. 1924I AUTOCANDIDATE FUNCTION HAS BEEN STARTED Explanation: The console operator issued the MVS MODIFY command to the MSAS address space in order to initiate the AutoStrobe AutoCandidate function (during this run of the MSAS only).

3-36

Strobe Messages Guide

System Action: User Response:

Session manager, MSAS, and AutoStrobe continue to process. None required.

1925I AUTOCANDIDATE FUNCTION HAS BEEN STOPPED Explanation: The console operator issued the MVS MODIFY command to the MSAS address space in order to terminate the AutoStrobe AutoCandidate function (during this run of the MSAS only). System Action: User Response: STR1926I ACTIVE Session manager, MSAS, and AutoStrobe continue to process. None required.

MODIFY msasname STOPACND COMMAND REJECTED, AUTOCANDIDATE IS NOT

Explanation: The console operator issued the MVS MODIFY command to the MSAS address space in order to terminate the AutoStrobe AutoCandidate function, but the AutoCandidate function was not active at the time. System Action: User Response: Session manager, MSAS, and AutoStrobe continue to process. None required.

STR1927I MODIFY msasname STRTACND COMMAND REJECTED, { AUTOSTROBE IS NOT ACTIVE | AUTOCANDIDATE IS ALREADY ACTIVE} Explanation: The console operator issued the MVS MODIFY command to the MSAS address space to start the AutoStrobe AutoCandidate function, but either AutoStrobe was not active, or the AutoCandidate function was already active. System Action: Session manager, MSAS, and AutoStrobe continue to process.

User Response: To start AutoStrobe, issue the MVS MODIFY command to the MSAS started task, specifying STARTAUTO. Next, if you want to start the AutoStrobe AutoCandidate function, and AUTOCANDIDATE=YES is not specified in the Strobe parameter dataset, issue the MVS MODIFY command to the MSAS started task, specifying STRTCAND. STR1940I INITIALIZATION OF STROBE FOR WEBSPHERE IN msasname { IN PROCESS | COMPLETE}

Explanation: Initialization of Strobe for WebSphere Application Server in the MSAS msasname is in process or complete. System Action: User Response: STR1941I Strobe for WebSphere Application Server proceeds normally. None required.

STROBE FOR WEBSPHERE HAS BEEN TERMINATED Strobe for WebSphere Application Server has ended. Strobe for WebSphere Application Server has terminated.

Explanation: System Action:

User Response: If Strobe for WebSphere Application Server terminated abnormally, proceed based on the content of any related error messages. Otherwise, none required. STR1942E INIT OF STR FOR WEBSPHERE IN msasname TERMINATED ---<text>

Explanation: Initialization of Strobe for WebSphere Application Server terminated for the reason shown in text:

CSVDYNEX ADD FOR STRvWU83 FAILED - The Strobe module, STRvWU83, could not be dynamically added to the SMF IEFU83 exit chain. UNABLE TO OBTAIN PRIVATE WORKING STORAGE - The region for the MSAS Address Space is not large enough. The Strobe system programmer may need to increase the region size for the MSAS by changing the proc named by the MSASPROCNAME parameter in the Strobe parameter dataset. SMF RECORD TYPE 120 NOT BEING COLLECTED -- The current LPAR does not specify that SMF type 120 records be collected. Strobe for WebSphere Application Server requires that SMF type 120 records be created. SAST IS INVALID -- Session manager and/or MSAS is passing an incorrect value to Strobe for WebSphere Application Server. The Strobe system programmer may choose to recycle Strobe for WebSphere by issuing MODIFY commands to MSAS

Messages Produced by Strobe

3-37

to STOPWAS and then STARTWAS. If the problem persists, the system programmer may choose to recycle the related Session Manager Address Space. LOAD OF STRvWU83 FAILED, ABEND CODE=Sxxx-xx - The load module STRvWU83 cannot be located. UNABLE TO OBTAIN COMMON STORAGE FOR WAST - Common storage could not be obtained for the WAST control block. The Strobe system programmer may need to investigate why common storage is unavailable.
System Action: Strobe for WebSphere Application Server cannot be initialized.

User Response: Notify the Strobe system programmer. Follow any additional suggestions noted above for text. STR1944S STRvWU83 HAS ENCOUNTERED SEVERE ERROR AND WILL TERMINATE ---<text> See the following explanations for text:

Explanation:

SMF EXIT DELETED BY SYSTEM - Program STRvWU83 has abended. Strobe for WebSphere Application Server cannot continue, but will be automatically restarted up to three times per WebSphere session per MSAS session. STRBWDRV IS ABENDING - Program STRvWDRV has abended. Strobe for WebSphere Application Server cannot continue, but will be automatically restarted up to three times per WebSphere session per MSAS session. INVALID WAST AREA - Either STRvWDRV passed an incorrect value to STRvWU83, or common storage has become corrupted. The Strobe system programmer may choose to recycle Strobe for WebSphere Application Server by issuing MODIFY commands to MSAS to STOPWAS and then STARTWAS. If the problem persists, consider recycling the related Session Manager Address Space.
System Action: Strobe for WebSphere Application Server cannot continue. See any additional system action in the description of text. User Response: Notify the Strobe system programmer, who may choose to obtain a dump and send to Compuware for analysis. Follow any additional suggestions noted above for text. STR1945E STRvWU83 WILL TERMINATE WAS { IN SINGLE REQUEST text | IN REQUEST rrrr text}

The following reasons exist when scope is IN SINGLE REQUEST text STORAGE OBTAIN OF LWA FAILED
Explanation: The region for the measured Address Space, or the region for the associated WebSphere Control Address Space if you are measuring a WebSphere Server Address Space, is not large enough. This may be due to measuring several Server Address Spaces within one Control Address Space concurrently. System Action: only. Strobe for WebSphere Application Server cannot continue for this request

User Response: The WebSphere system programmer may need to increase the region size for the affected WebSphere Address Space.

INVALID SAST CHAIN OR AREA


Explanation: The internal Strobe SAST chain or one of its related areas is invalid. Strobe for WebSphere Application Server cannot continue for this request only. Notify the Strobe system programmer, who may choose to recycle the related Session Manager Address Space.

The following reasons exist when scope is IN REQUEST rrrr text. rrrr is the number of the Strobe request. ALESERV ADD FAILED
Explanation: The Strobe for WebSphere Application Server SMF exit could not obtain access rights to the dataspace obtained on its behalf by the WebSphere Application Server data collector. This is theoretically possible when there have been over 509 Strobe measurements on WebSphere Server Address Spaces within a single WebSphere Control Address Space. System Action: Strobe for WebSphere Application Server cannot continue for this request only, or for subsequent requests for WebSphere Server Address Spaces within this related WebSphere Control Address Space.

3-38

Strobe Messages Guide

User Response: Notify the WebSphere system programmer, who may chose to recycle the associated WebSphere Control Address Space.

TEN INVALID SMF RECORDS TYPE 120, SUBTYPE 1


Explanation: records. The SMF exit, STRBWU83, has recognized 10 invalid type 120, subtype 1, SMF

System Action: The Strobe for WebSphere Application Server data collector will cease processing SMF records for this measurement only. It will continue the measurement for all other events. User Response: Notify the Strobe system programmer, who may wish to work with your sites SMF system programmer for a solution.

TEN INVALID SMF RECORDS TYPE 120, SUBTYPE 5


Explanation: records. The SMF exit, STRBWU83, has recognized 10 invalid type 120, subtype 5, SMF

System Action: The Strobe for WebSphere Application Server data collector will cease processing SMF records for this measurement only. It will continue the measurement for all other events. User Response: Notify the Strobe system programmer, who may wish to work with your sites SMF system programmer for a solution.

TEN INVALID SMF RECORDS TYPE 120, SUBTYPE 7


Explanation: records. The SMF exit, STRBWU83, has recognized 10 invalid type 120, subtype 7, SMF

System Action: The Strobe for WebSphere Application Server data collector will cease processing SMF records for this measurement only. It will continue the measurement for all other events. User Response: Notify the Strobe system programmer, who may wish to work with your SMF system programmer for a solution.

ONE THOUSAND SMF RECORDS LOST DURING MEASUREMENT


Explanation: The SMF exit, STRBWU83, has recognized that 1,000 SMF records have been lost during this measurement due to timing issues on the dataspace it shares with the Strobe WebSphere data collector. System Action: The Strobe for WebSphere Application Server data collector will cease processing SMF records for WebSphere (type 120) for this measurement only. It will continue the measurement for all other events. User Response: STR1950E Notify the Strobe system programmer.

LOAD-MODULE LIST PROCESSING TERMINATED - reason

Explanation: The AutoMeasure utility was unable to completely build or update the AutoMeasure load module list for the indicated reason. The possible reasons include: HISTORY INITIALIZATION FAILED UNABLE TO OPEN SYSIN DATA SET UNABLE TO READ SYSIN DATA SET NO DATE RECORD IN SYSIN DATA SET INVALID DATE RECORD IN SYSIN DATA SET SYSIN DATA CONTAINED AN INVALID RECORD TYPE UNABLE TO DELETE AN OLD LOAD-MODULE LIST NO NAME OR PREFIX SPECIFIED ON EXCLUDE RECORD UNABLE TO ALLOCATE LOAD LIBRARY - load library name ERROR WHILE READING DIR BLOCK FROM LOAD LIBRARY - load library name ERROR WHILE READING MEMBER FROM LOAD LIBRARY - load library name UNABLE TO WRITE LOAD-MODULE-LIST ENTRY UNABLE TO WRITE LOAD-MODULE-LIST HEADER UNABLE TO READ LOAD-MODULE-LIST HEADER UNABLE TO OPEN PDS DIRECTORY DCB - load library name UNABLE TO OPEN PDS MEMBER DCB - load library name NO LOAD LIBRARY DESIGNATED IN THE SYSIN DATA NUMBER OF EXCLUDE RECORDS EXCEEDS MAXIMUM

Messages Produced by Strobe

3-39

UNABLE TO DELETE A LOAD-MODULE LIST ENTRY UNABLE TO OBTAIN STORAGE FOR LOAD-LIBRARY DATA System Action: The AutoMeasure utility terminates. When the reason indicates a problem with the reading, writing, or deleting of the AutoMeasure list or one of its entries, this message is preceded by diagnostic data that specifies the return and reason codes from VSAM.

Any entries put on the AutoMeasure load module list prior to this error remain intact. These entries are identified in the STR1953I message that precedes this one. Any active Strobe and AutoStrobe processing continues.
User Response: Depending on the reason, either check the input parameters on the STROBE AUTOSTROBE AUTOMEASURE UTILITY panel for submitting an AutoMeasure request or contact Compuware Customer Support. STR1951E NO LOAD-MODULE LIST BUILT FOR AUTOMEASURE FUNCTION - reason

Explanation: During AutoStrobe initialization, Strobe was unable to build a version of the AutoMeasure load module list in storage for this instance of Strobe. The possible reasons include: NO LOAD MODULE LIST ON AUTOSTROBE DATA SET LIST HAS NO ENTRIES SPECIFYING THIS SYSTEM FOR AUTOMEASURE UNABLE TO OBTAIN PRIVATE STORAGE FOR LIST UNABLE TO OBTAIN COMMON STORAGE FOR LIST UNABLE TO READ HEADER RECORD FOR LIST UNABLE TO READ AN ENTRY RECORD FROM LIST INTERNAL ERROR

System Action: AutoStrobe did not build a version of the AutoMeasure load module list in storage, so this instance of Strobe cannot initiate any automatic measurements of new or changed load modules. All other Strobe and AutoStrobe processing continues as usual. User Response: STR1951I Contact Compuware Customer Support.

NO LOAD-MODULE LIST BUILT FOR AUTOMEASURE FUNCTION - reason

Explanation: During AutoStrobe initialization, Strobe was unable to build a version of the AutoMeasure load module list in storage for this instance of Strobe. The possible reasons include: NO LOAD MODULE LIST ON AUTOSTROBE DATA SET LIST HAS NO ENTRIES SPECIFYING THIS SYSTEM FOR AUTOMEASURE UNABLE TO OBTAIN PRIVATE STORAGE FOR LIST UNABLE TO OBTAIN COMMON STORAGE FOR LIST UNABLE TO READ HEADER RECORD FOR LIST UNABLE TO READ AN ENTRY RECORD FROM LIST INTERNAL ERROR

System Action: AutoStrobe did not build a version of the AutoMeasure load module list in storage, so this instance of Strobe cannot initiate any automatic measurements of new or changed load modules. All other Strobe and AutoStrobe processing continues as usual. User Response: Run the AutoMeasure program list utility to build the load module list and issue the MODIFY STRBMSAS, LMLISTREF command. STR1952I AUTOMATIC MEASUREMENT SUPPRESSED FOR PROGRAM - program name

Explanation: The AutoMeasure load module list specified a program name for an automatic measurement, but AutoStrobe did not initiate the measurement for one of the following reasons: ALREADY MEASURED UNDER CURRENT JOB AND STEP MAXIMUM NUMBER OF AUTOMEASURES ALREADY TAKEN AUTOMEASURE TEMPLATE SRE HAS BEEN DELETED System Action: AutoStrobe does not initiate the automatic measurement of the designated program for the specified reason. User Response: None required.

3-40

Strobe Messages Guide

STR1953I

{number of entries ENTRIES | NO ENTRIES} ADDED TO LOAD-MODULE LIST

Explanation: This message appears after AutoStrobe builds the AutoMeasure load module list. The following are possible reasons for this message: The list was not built or updated. To provide the number of load module names placed on the AutoMeasure load module list.

When entries are put on the AutoMeasure load module list, this message is preceded by a list of the load module names that were added and their link-edit dates.
System Action: Processing continues.

User Response: If this message indicates that no entries were placed on the AutoMeasure load module list, check that the correct parameters were used when running the AutoMeasure utility. STR1954I IN-STORAGE VERSION OF AUTOMEASURE LOAD-MODULE LIST {REFRESHED | BUILT} CONTAINS number ENTRIES Explanation: The version of the AutoMeasure load module list in storage that identifies the load modules to be automatically measured on this z/OS system has been successfully built (during Measurement Services Address Space initialization) or refreshed (using the z/OS MODIFY operator command) from the AutoMeasure load module list in the AutoStrobe dataset. System Action: User Response: Strobe and AutoStrobe processing continues normally. None.

STR1960I NO TRANSACTION-CANDIDATE LIST BUILT FOR CICS REGION jobname FOR TIME PERIODS SPECIFIED IN REQUEST xxxx Explanation: The AutoStrobe Create Transaction Candidates request xxxx has completed. AutoStrobe did not build a list of transaction candidates from the CICS region, because either no transactions executed or none of the transactions that executed had enough activity to exceed the minimum thresholds specified in the request. System Action: AutoStrobe processing continues.

User Response: Verify that there is sufficient activity in the CICS region during the time period(s) specified on the AutoStrobe Create Transaction Candidates request. If there is, you should delete this request and submit another one using lower minimum thresholds, lower execution counts, or different time periods. STR1961E AUTOSTROBE REQUEST xxxx FOR JOB jobname MARKED COMPLETE BECAUSE OF AN ERROR - CODE=xx [,SUBCODE=cc] Explanation: An error occurred while AutoStrobe was processing a Create Transaction Candidates request or a transaction monitoring request for a CICS region. CODE=xx identifies the function in which the error occurred and SUBCODE=cc, if present, provides further details. System Action: AutoStrobe marks the request as complete. Other Strobe and AutoStrobe processing continues. User Response: Save the Strobe log in which this error appears and contact Compuware Customer Support. STR1962I AUTOSTROBE MONITORING FOR REQUEST xxxx FOR JOB jobname SUSPENDED FOR A USER-INITIATED MEASUREMENT OF REGION Explanation: A user initiated a measurement for a job in a CICS region monitored by AutoStrobe. AutoStrobe stops monitoring the CICS region, so the measurement can proceed. System Action: When the measurement ends:

For a transaction monitoring request, AutoStrobe resumes monitoring the CICS region. For a Create Transaction Candidates request, no more data is collected during this time period, and any data collected during this time period is discarded. AutoStrobe resumes collecting data at the start of the next time period. User Response: None required.

Messages Produced by Strobe

3-41

STR1963I AUTOSTROBE DATA COLLECTION FOR REQUEST xxxx FOR JOB jobname DEFERRED UNTIL START OF THE NEXT TIME PERIOD Explanation: A Create Transaction Candidates request was submitted during a time period that had already started as specified in the request. Because Create Transaction Candidates requests process data only for complete time periods, data collection for this request is deferred until the start of the next time period. System Action: User Response: STR1969E AutoStrobe processing continues. None required.

Load failed for service provider module modulename. Strobe invoked an MVS service to load a module, but the load request failed. Strobe initiation terminates. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR1980I

Global Monitoring has been started The Global Monitoring task has been attached in the MSAS. Processing continues. None required.

Explanation: System Action: User Response: STR1981I

Strobe Global Monitoring initializing in (msasname)

Explanation: The Global Monitoring task is in the process of initializing in the MSAS. The name of the MSAS procedure is displayed in the message. System Action: User Response: STR1982I Processing continues. None required.

Strobe Global Monitoring initialization complete in (msasname)

Explanation: The Global Monitoring task has completed initializing in the MSAS. The name of the MSAS procedure is displayed in the message. System Action: User Response: STR1983I Processing continues. None required.

Global Monitoring file task has been started The Global Monitoring file task has been attached in the MSAS. Processing continues. None required.

Explanation: System Action: User Response: STR1984I

Strobe Global Monitoring file task initializing in (msasname)

Explanation: The Global Monitoring file task is in the process of initializing in the MSAS. The name of the MSAS procedure is displayed in the message. System Action: User Response: STR1985I Processing continues. None required.

Strobe Global Monitoring file task initialization complete in (msasname)

Explanation: The Global Monitoring file task has completed initializing in the MSAS. The name of the MSAS procedure is displayed in the message. System Action: User Response: STR1986I Processing continues. None required.

Strobe Global Monitoring terminating in (msasname)

Explanation: The Global Monitoring task has started termination processing in the MSAS. The name of the MSAS procedure is displayed in the message. System Action: Processing continues.

3-42

Strobe Messages Guide

User Response: STR1987I

None required.

Strobe Global Monitoring file task terminating in (msasname)

Explanation: The Global Monitoring file task has started termination processing in the MSAS. The name of the MSAS procedure is displayed in the message. System Action: User Response: STR1988I Processing continues. None required.

Strobe Global Monitoring file task has terminated The Global Monitoring file task has completed termination processing in the Processing continues. None required.

Explanation: MSAS. System Action: User Response: STR1989I

Strobe Global Monitoring has terminated The Global Monitoring task has completed termination processing in the Processing continues. None required.

Explanation: MSAS. System Action: User Response: STR1990E

Error allocating Global Monitoring Repository data set

Explanation: The Global Monitoring task has attempted to dynamically allocate the repository data set. The attempt was not successful. System Action: User Response: STR1991I Global Monitoring terminates in the MSAS. See the subsequent STR1991I message for details about this error.

Dynalloc RC=rrrrrrrr. Error=eeee. Reason Code=cccc

Explanation: This message displays the dynamic allocation return code, error code, and reason code. The previous message indicates the file that was being allocated. System Action: Global Monitoring processing continues.

User Response: Using the return code, error code, and reason code, determine the cause of the dynamic allocation failure. STR1992E Error allocating Global Monitoring AUTOHIST data set

Explanation: The Global Monitoring task has attempted to dynamically allocate the Autostrobe history file. The attempt was not successful. System Action: User Response: STR1993I Global Monitoring terminates in the MSAS. See the subsequent STR1993I message for details about this error.

Dynalloc RC=rrrrrrrr. Error=eeee. Reason Code=cccc

Explanation: This message displays the dynamic allocation return code, error code and reason code. The previous message indicates the file that was being allocated. System Action: Global Monitoring processing continues.

User Response: Using the return code, error code, and reason code, determine the cause of the dynamic allocation failure. STR1994I Global Monitoring criteria refreshed

Explanation: This message indicates that the Global Monitoring criteria have been successfully refreshed from the AutoStrobe data set. This occurs when the GMCRITREF option is passed to the MSAS using the MVS MODIFY command. System Action: User Response: Global Monitoring processing continues with the new criteria. None required.

Messages Produced by Strobe

3-43

STR1995E

Global Monitoring criteria refresh failed. RC=rrrrrrrr

Explanation: A request to refresh the Global Monitoring criteria was unsuccessful. The return code is indicated in the message. System Action: User Response: STR1996E Global Monitoring processing continues. Contact Compuware Customer Support.

Invalid Global Monitoring Repository data set name prefix specified.

Explanation: The value specified in the GM_REPOSITORY_DSN Strobe parameter must be a valid data set name prefix. System Action: User Response: parameter. STR1997E Global Monitoring terminates in the MSAS. Specify a valid data set name prefix on the GM_REPOSITORY_DSN Strobe

Global Monitoring Repository data set name prefix greater than 38 characters.

Explanation: The value specified in the GM_REPOSITORY_DSN Strobe parameter cannot be greater than 38 characters in order to allow Strobe to append the system ID low-level qualifier. The system ID low-level qualifier consists of the letter S and the four-character SMF system ID. System Action: Global Monitoring terminates in the MSAS.

User Response: Specify a valid data set name prefix on the GM_REPOSITORY_DSN Strobe parameter that is less than or equal to 38 characters. STR1998E Global Monitoring Repository data set already in use

Explanation: The Global Monitoring repository data set can be used by only one Strobe image running on an LPAR. System Action: User Response: LPAR. STR1999I Global Monitoring terminates in the MSAS. Create a separate repository data set for each image of Strobe running on an

Global Monitoring Repository data set name xxxxxxxxxxxxxx. This message displays the 44-character Global Monitoring Repository data set Global Monitoring initialization continues. None required.

Explanation: name. System Action: User Response:

Messages Returned by the Reporter


The Strobe Reporter program returns the following messages.
STR2000I PARM=parm Strobe detected an error in one or more of the parameters specified.

Explanation:

System Action: Strobe lists one line of the parameters in parm and repeats this message once for each additional line. User Response: Verify that the parameters have been specified correctly. If they have, notify the Strobe system programmer. STR2002W ERROR IN PARAMETER parmname [parmvalue] [explanation]

Explanation: Strobe detected an error in the parameter parmname. If the parameter has a value, that value appears in parmvalue. If further information is available, it appears in explanation. System Action: Strobe continues processing. If the error Strobe encountered is a table overflow error, Strobe processes only as many modules as it can fit in the table.

3-44

Strobe Messages Guide

User Response: Review the input parameters to ensure that they are correct. Refer to Creating Performance Profiles Using Procedures in the Strobe User Guide for more information. STR2003W SQL PARAMETER MAXLEN CHANGED TO new value MAXLEN must be a multiple of 100.

Explanation:

System Action: The Reporter increases the value of MAXLEN to the next highest multiple of 100, which appears as a new value. User Response: STR2004W Change MAXLEN to be a multiple of 100.

CONFLICTING REPORT PARAMETERS: parm1 - parm2 Two conflicting parameters, parm1 - parm2, were supplied to the profiling Strobe ignores the conflicting parameter and uses the default parameters. Remove one of the parameters.

Explanation: request. System Action: User Response:

STR2005W INVALID TRANSACTION FILTER REQUEST. THE FORMAT OF THE TRANSACTION FILTER tran IS NOT VALID Explanation: The specified filter tran is not one to four characters long with a wildcard (*) in the last position. If a set of transactions is filtered, the last significant character must equal an asterisk (*). System Action: Strobe ignores the filter request and does not provide performance information for that set of transactions. User Response: Enter a valid transaction name with a wildcard in the last position. Refer to the IBM CICS Resource Definition Guide for valid CICS transaction names. STR2006W MORE THAN FIVE TRANSACTION FILTER REQUESTS WERE SPECIFIED

Explanation: Strobe can report detailed performance information for only five transactions or sets of transactions. System Action: only. User Response: STR2007W Strobe provides detailed performance information for the first five requests Verify the number of filter requests and remove additional requests.

INVALID {TLIBASE|RLIBASE} PARAMETER You entered a value for TLIBASE or RLIBASE that exceeds the maximum value Strobe uses the default values of 00.005 seconds. Enter a valid value. parm1

Explanation: of 99.999. System Action: User Response: STR2008I

DUPLICATE PARAMETERS ENCOUNTERED-

Explanation: System Action: User Response: STR2009I

You entered the same parameter, parm1, twice. Strobe ignores the second parameter. Remove the duplicate parameter from the Profile request.

DUPLICATE TRANSACTION PROFILE REQUESTS SUBMITTED - tran You requested duplicate performance information for the transaction named Strobe ignores the second transaction. Remove the duplicate transaction from the Profile request.

Explanation: tran. System Action: User Response: STR2050W

HISTORY ALREADY EXISTS FOR jobname/stepname/progname date time reqnumber

Explanation: A measurement session history record already exists for the sample file identified by the job jobname, the step stepname, and the program progname. This measurement session history record was created on date date and time time. The Strobe request number for the sample dataset was reqnumber.

Messages Produced by Strobe

3-45

System Action: Strobe continues creating a Performance Profile, but will not create a new measurement session history record. User Response: None required. If you verify that this sample file is the sample file for which you now want to add information to the history database, you must first delete its existing measurement session history record. You can then create a new measurement session history record for this sample file. STR2051W UNABLE TO LOAD STROBE HISTORY MANAGER Strobe was unable to locate its history manager component. Strobe will not update the history dataset.

Explanation: System Action:

User Response: Review the Strobe history manager installation instructions in the Strobe Installation and Customization Guide and verify that the appropriate Strobe libraries are loaded. If the problem persists, contact Compuware Customer Support. STR2052W UNABLE TO CALCULATE fieldname FOR {TRANSACTION | DBRM} NAME name

Explanation: Strobe encountered either an overflow or an underflow condition and was unable to calculate the statistics given in fieldname for either the transaction or DBRM name identified in name. System Action: Strobe will set the field identified in fieldname to zero. Some information in the history dataset will be incomplete. User Response: STR2053W None required.

COLLECTION OF HISTORY DATA IS TERMINATED The request for a measurement session history record for this measurement Strobe continues processing but no measurement session history record will

Explanation: failed. System Action: be created.

User Response: Follow the response indicated in any accompanying Strobe messages that relate to measurement session history collection and reporting. If you entered the REPJOB or REPSTP parameters, ensure that you used the correct syntax. STR2104W MAP DATA SET CONTAINS AN UNMAPPED CONTROL SECTION NAMED csectname

Explanation: Map dataset information is compiled for the control section csectname, but this control section does not appear in the sample dataset. The following are possible causes:

The control section exhibited less than the baseline percentage of execution samples specified with the BASELINE operand (default 2). A library in the STEPLIB, JOBLIB, or STRBLIB data definition statements does not have the correct name. The named library or libraries do not contain the named module. The named module is resident in the link pack area and your Strobe system programmer has not configured your Strobe system to obtain data from link pack area libraries. The job step was cancelled or timed out, preventing mapping. The control section contained one or more modules that were loaded with the Dynamic LPALIB Facility.
System Action: The Reporter continues execution but does not process Indexer data for the control section. User Response: Check the BASELINE field on the Measurement Session Data report. If the BASELINE field does not appear on the report, Strobe used the default baseline. Check that the map dataset supplied to the Reporter is the proper map of the correct program. It must be the map dataset of the program whose execution samples appear in the sample dataset. Check for error messages produced by the measurement task that may indicate problems processing the load library. If the measurement task is unable to map the load module, the Reporter cannot accept the Indexer data.

3-46

Strobe Messages Guide

STR2105W

ERROR ADDING 4GL PROGRAM program TO CSECT TABLE FOR MODULE modname There is no room in an internal table to add the 4GL program named program. The Reporter continues processing, but some attribution data may be Notify the Strobe system programmer.

Explanation: System Action: incomplete. User Response: STR2106W

TOO MANY USER-SUPPLIED PSEUDO-CSECT NAMES

Explanation: You supplied more than the maximum number of names allowed in the COMPRES parameter. System Action: Strobe does not report as pseudo-procedures activity in other modules with names that have been supplied by a user-written or a Strobe data collector program, or in the COMPRES parameter. It shows them as normal modules or control sections. The number of groups compressed with the COMPRES option and by data collector programs cannot total more than 25. User Response: Review the description of the COMPRES parameter.

STR2108W ADDRESS NOT MAPPED - SAMPLE sampnumber PSW psw modname BASE base SIZE size MAP SIZE mapsize Explanation: The PSW is not in a mapped portion of the module, but the Reporter detected fewer than 100 instances of the problem. The sample number is sampnumber, the PSW is psw, the module is modname, the base is base, the size is size, and the map size is mapsize. System Action: User Response: The Reporter discards the sample and continues processing. Notify the Strobe system programmer.

STR2109S ADDRESS NOT MAPPED - SAMPLE sampnumber PSW psw modname BASE base SIZE size MAP SIZE mapsize Explanation: The PSW is not in a mapped portion of the module, and the Reporter has detected more than 100 instances of the problem. The sample number is sampnumber, the PSW is psw, the module is modname, the base is base, the size is size, and the map size is mapsize. System Action: User Response: STR2110E The Reporter terminates and does not produce a Strobe Performance Profile. Notify the Strobe system programmer.

TOO MANY CONTROL SECTIONS

Explanation: Strobe was unable to acquire sufficient storage to table all control sections for which mapping data may be required. System Action: Strobe produces a Profile but might discard mapping data for some modules if its internal table cannot store all the information. If any mapping data is discarded, this message is followed by one or more occurrences of the message STR2108W, giving the names of the affected modules. User Response: Notify the Strobe system programmer.

STR2111S TOO MANY {MODULES|DD STATEMENTS|I/O UNIT|VOLUME|SEGMENTS|FILE NAME COMBINATIONS} Explanation: Input to the Strobe Reporter exceeded the Reporters capacity. The limits are as follows:

Load modules Segments DD statements Unit/volume/ddname combinations for datasets


System Action: User Response:

3196 255 2119 2500

The Reporter does not produce a Strobe Performance Profile. Notify the Strobe system programmer.

Messages Produced by Strobe

3-47

STR2112W

PROFILE CREATED USING A LOW NUMBER OF EXECUTION SAMPLES

Explanation: The Reporter found fewer than 100 execution samples in the sample dataset. The measurement session was too short or the initial sampling rate was too low. System Action: Strobe produces a Performance Profile but the CPU reports are not statistically significant. User Response: Rerun the measurement session, and specify a smaller estimate of minimum run time or a larger target sample size or both. STR2113E FEWER THAN 100 SAMPLES - NO PROFILE PRODUCED

Explanation: Fewer than 100 samples are in the sample dataset. The measurement session was too short or the initial sampling rate was too low. System Action: Strobe does not produce a Performance Profile.

User Response: Rerun the measurement session, and specify a smaller estimate of minimum run time or a larger target sample size or both. STR2114W TOO MANY SETS OF WORK LOAD MANAGER INFORMATION Insufficient storage was available to build a table of all Workload Manager

Explanation: information.

System Action: Strobe produces a Profile but there will be some Workload Manager information missing. User Response: STR2116S Notify the Strobe system programmer.

UNSUCCESSFUL COMPLETION OF SORT. SORT RETURN CODE=rc

Explanation: The installation-supplied sort/merge program did not complete execution successfully. The return code returned by the sort/merge program is rc. System Action: Strobe does not produce a Performance Profile.

User Response: Review the messages produced by the sort/merge program to determine the cause of the problem. STR2118S SAMPLE DATA SET IMPROPERLY FORMATTED

Explanation: The samples in the sample dataset are out of sequence, probably because the Reporter has been executed before the dataset has been closed by the measurement task. System Action: User Response: STR2120S Strobe does not produce a Performance Profile. Ensure that the dataset is closed and resubmit the job.

INSUFFICIENT SPACE ON WORK FILE The Reporter SYSUT1 dataset used all of its allocated direct access extents. Strobe does not produce a Performance Profile. Rerun the Reporter with a larger space allocation for the SYSUT1 dataset.

Explanation: System Action: User Response: STR2122W NOT AGREE

MAP DATA SET AND LOAD LIBRARY SIZES FOR CONTROL SECTION csectname DO

Explanation: The size of a control section, csectname, as reported by the Indexer in the map dataset, differs from the size the measurement task determined from the load library. System Action: The Reporter uses data in the map dataset, but the assignment of CPU time by procedure in the Strobe Performance Profile may be incorrect. However, some compiler options (such as the COBOL STATE option) extend a control section beyond the length reflected in the object code listing the Indexer processed. When such an option is in effect, this message will appear, but the Performance Profile will still be valid. User Response: Ensure that you compiled and indexed the same source that was compiled to produce the measured program load module for the program. Ensure also that you used the same compiler options. To be sure, compile, index, and link edit the program again, and then perform another measurement session.

3-48

Strobe Messages Guide

STR2124W

TOO MANY TASKS Data for more than 563 tasks was placed in the sample dataset.

Explanation:

System Action: Strobe produces the Performance Profile, but the activity for all tasks will be compressed into one detail line in the Time Distribution of Activity Level and Resource Demand Distribution reports. User Response: Notify the Strobe system programmer.

STR2125W {SUBSYSTEM|MAPPROG LIST|STRBLIB LIST|WAIT EXCLUDE|DATA COLLECTION| REPORT TITLE|DB2 PROCEDURE|QUERY STATEMENT} TABLE OVERFLOW Explanation: System Action: inaccurate. User Response: STR2126W An overflow occurred in an internal table of the Strobe Reporter program. Strobe produces a Performance Profile, but some data may be missing or Notify the Strobe system programmer.

LENGTH ERROR ON {SUBSYSTEM |WAIT EXCLUDE|DATA COLLECTION} TABLE

Explanation: Strobe detected an internal item length error in a Strobe subsystem, mapping list, or library list while processing the Strobe Performance Profile. System Action: Strobe produces a Performance Profile, but the Measurement Session Data report is missing the corresponding data. User Response: Notify the Strobe system programmer.

STR2127W OVERLAY CSECT NOT IN MAIN STORAGE - MODULE modname CSECT csectname COUNT errorcount Explanation: Strobe attempted to sample an overlay segment that maps to module modname and segment csectname errorcount times, but the segment was not in virtual storage. System Action: User Response: Strobe shows activity relative to the module base for the module modname. Notify the Strobe system programmer.

STR2128W OVERLAY CSECT NOT IN MAIN STORAGE - SAMPLE sampnumber PSW psw modname BASE base SIZE size Explanation: No overlay segment that maps the PSW psw was in virtual storage when Strobe collected sample number sampnumber. System Action: Strobe shows activity relative to the module base for the module modname. The base is base, and the size is size. User Response: STR2129C Notify the Strobe system programmer.

MISSING OVERLAY CSECTS MAXIMUM EXCEEDED

Explanation: While sampling, Strobe encountered more than 50 overlay segments that were not in virtual storage. System Action: Strobe produces a Performance Profile, but some data in it may be inaccurate. User Response: Notify the Strobe system programmer.

STR2130S {OPEN|CLOSE|READ|WRITE} ERROR ON DDNAME {STRSAMPL| SYSPRINT|SYSUT1} FILE STATUS = status Explanation: The Reporter encountered an open, close, read, or write error while accessing the sample file STRSAMPL, the report file SYSPRINT, or an internal file SYSUT1. The file status is status. If access to SYSPRINT caused the problem, the Reporter displays this message on SYSOUT. System Action: User Response: programmer. The Reporter terminates and does not produce a Performance Profile. Verify the dataset name. If the name is correct, notify the Strobe system

Messages Produced by Strobe

3-49

STR2131W = status

{OPEN|CLOSE|READ|WRITE} ERROR ON DDNAME {STRMAP|SORTWORK} FILE STATUS

Explanation: The Reporter encountered an open, close, read, or write error while accessing the map dataset STRMAP or the SORTWORK files. The file status is status. System Action: available. The Reporter produces a Performance Profile, but no indexing data is

User Response: Verify the map dataset name. If the name is correct, notify the Strobe system programmer. STR2132I SECTION MAPPING CANNOT BE PERFORMED FOR THESE MODULE(S): module. IF MULTIPLE INSTANCES OF A MODULE HAVE BEEN MEASURED, THEIR ACTIVITY IS COMBINED. Explanation: The Reporter detected an inconsistency between a module found during the sampling process and module mapping information obtained from a load library.

Strobe issues this message if the module that should have been mapped resides in a library that was not the first library in which a different module with the same name was found. For example, Strobe issues this message when third-party software loads modules in a manner other than that specified by IBM standards. The order in which Strobe searches libraries to obtain module mapping data is specified in the Strobe User Guide.
System Action: The Reporter discards all mapping data and shows the locations of activity relative to the base address of the module instead of to the start of individual sections within the module. User Response: If a copy of the module that should have been mapped resides in a library later in the search order than the library in which Strobe found a different module with the same name, then specify the appropriate library in the Strobe request. Otherwise, notify the Strobe system programmer. STR2133S Sample dataset is invalid

Explanation: The Reporter encountered an error while accessing the sample file STRSAMPL. Either the RECFM is fixed, or the measurement session information record is missing. System Action: User Response: programmer. STR2135S The Reporter terminates and does not produce a Performance Profile. Verify the dataset name. If the name is correct, notify the Strobe system

Sample dataset OPEN error. The Reporter encountered an I/O error while opening the sample file The Reporter terminates and does not produce a performance profile. Verify the dataset is a valid Sample Dataset and notify the Strobe system

Explanation: STRSAMPL. System Action: User Response: programmer. STR2137S

Sample dataset is empty.

Explanation: The Reporter encountered an error while accessing the sample file STRSAMPL. There is no data on in the dataset. System Action: User Response: programmer. The Reporter terminates and does not produce a performance profile. Verify the dataset name. If the name is correct, notify the Strobe system

STR2140W INDEX DATA FOR {modname | dialog, process} FROM A MAP DATA SET HAS NO MATCHING SAMPLE DATA Explanation: Strobe produced map dataset information for the module, ADS/O dialog, or DBRM named in modname, dialog, or process, but this information does not appear in the sample dataset. System Action: The Reporter continues execution but does not process Indexer data for the module, dialog, or DBRM.

3-50

Strobe Messages Guide

Check that the map dataset supplied to the Reporter is the proper map of the correct program. It must be the map dataset of the program whose execution samples appear in the sample dataset. Check for errors produced by the measurement task that may indicate problems processing the partitioned dataset. If the measurement task has not gathered sampling data for the module, the Reporter cannot accept the Indexer data.
STR2141W modname MAP DATA SET VERSION DOES NOT MATCH SAMPLE DATA SET VERSION OF

Explanation: The time stamp of module, ADS/O dialog, or DBRM (named in modname) reported by the Indexer in the map dataset differs from the time stamp reported by the measurement task. System Action: The Reporter discards the indexing data for that module, dialog, or DBRM and continues processing. User Response: Check that the map dataset supplied to the Reporter is the proper map of the correct program. It must be the map dataset of the program whose execution samples appear in the sample dataset. STR2142W RECEIVED AN INVALID TITLE FROM {SAMPLE NUMBER samnumber| indexname} TITLE TYPE =type Explanation: The Reporter encountered an invalid title of type type from either the sample dataset with sample number sampnumber or the Indexer program named indexname. System Action: The Reporter produces a Performance Profile and attributes all CPU activity caused by the DBRM with an invalid title to the default title CPU USAGE BY STATEMENT. User Response: STR2143W Notify the Strobe system programmer.

NO ATTRIBUTION DATA FOR SQL IN sqlname

Explanation: Strobe for DB2 identified SQL procedure or query sqlname as executing in the target address space, but it did not attribute any CPU or wait activity to that procedure or query. System Action: Strobe produces a Performance Profile, but information for the procedure or query will be missing. User Response: Rerun the measurement session and specify a larger target sample size.

STR2144W DURING MEASUREMENT THERE WAS AN EXTENDED PERIOD OF TIME DURING WHICH STROBE COULD NOT SAMPLE Explanation: Strobe was unable to sample consistently during the measurement session. Because Strobe runs under a task while measuring, certain events may prevent Strobe from sampling. For example, Strobe may attempt to sample during a non interruptible unit of work, such as a type 1 SVC. Strobe does not report activity during such events, but the rest of the measurement continues to be valid. This message appears when Strobe cannot identify activity for a significant percentage of the time. System Action: Strobe produces a Performance Profile, but it may be incomplete.

User Response: Rerun the measurement session, requesting 10,000 samples. If you continue to receive the message, use other tools such as GTF trace to identify the activity that Strobe cannot. STR2145S ERROR - SAMPLE FILE VERSION (ver) IS NOT CONSISTENT WITH REPORTER LEVEL (lvl) The level (lvl) of the Reporter was lower than the version (ver) of the sample Strobe produces a Performance Profile, but it might be invalid. Rerun the measurement session with the correct level of the Reporter.

Explanation: file. System Action: User Response:

Messages Produced by Strobe

3-51

STR2146E

SAMPLE FILE SEQUENCE ERROR FOLLOWING SAMPLE NUMBER sample

Explanation: The Reporter detected an out-of-sequence condition in the sample dataset following sample sample. System Action: incomplete. User Response: Strobe continues processing and creates a Performance Profile but it will be Notify the Strobe system programmer.

STR2147W ONE OR MORE TRANSACTIONS EXECUTED, BUT STROBE WAS UNABLE TO REPORT ON ASSOCIATED TRANSACTION COUNTS OR SERVICE TIME Explanation: Strobe detected transactions executing but could not report on their transaction counts or service time. This could have been caused by the DL/I capture facility disabling itself. System Action: Strobe continues processing. In the Performance Profile, the Transaction Summary Report includes CPU usage for the transactions but does not include their transaction counts or service time. User Response: programmer. Check the Strobe log for additional messages and notify the Strobe system

STR2148I EXECUTION COUNT DATA FOR TRANSACTION(S) OR DIALOG(S) NOT AVAILABLE. **** INDICATES MISSING DATA Explanation: Strobe could not provide execution counts for one or more transactions or dialogs. The symbol **** appears in the execution count field of any transaction or dialog for which data was unavailable. Possible reasons for the data being unavailable include

a counter rolled over a counter was reset a transaction and its associated counter were dynamically deallocated
System Action: Strobe produces a Performance Profile, but one or more execution count fields are flagged with **** to indicate missing data. User Response: STR2150W None required. To obtain the missing data, rerun the measurement session.

UNDEFINED RESOURCE CLASS ENCOUNTERED -- RESOURCE CLASS=class Strobe encountered an unknown resource class class. Strobe reports statistics for the class under the pseudo-section .NONCICS. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR2151W

UNDEFINED RESOURCE TYPE ENCOUNTERED -- RESOURCE TYPE=type Strobe encountered an unknown resource type, type.

Explanation:

System Action: Strobe reports the statistics for the class under the pseudo-section .NONCICS. User Response: STR2152W Notify the Strobe system programmer.

INVALID TRANSACTION PROFILING SERVICE TIME DATA Strobe did not obtain a transaction count. Strobe substitutes a value of 1 for calculation purposes.

Explanation: System Action:

User Response: Measure the application again. If the problem persists, notify the Strobe system programmer. STR2153W CLASS NOT MAPPED - MODULE modname, CLASS class PSW nnnnnnnn

Explanation: The PSW, nnnnnnnn, does not fall within a mapped method for the class, class, but the class is identified to contain methods. System Action: Activity is reported at the class level.

User Response: Measure the application again. If the problem persists, notify the Strobe system programmer.

3-52

Strobe Messages Guide

STR2154W

UNABLE TO PROCESS TRANSACTION PROFILE REQUEST FOR TRANSACTION- tran

Explanation: Strobe could not capture the necessary data to process the request for transaction, tran. System Action: tran. The Strobe Performance Profile reports are inaccurate for this transaction,

User Response: Measure the application again. If the problem persists, notify the Strobe system programmer. STR2155W LICENSE VERIFICATION FAILED RETURN CODE =rc REASON CODE = erc. INDEXING SUPPRESSED FOR language Explanation: License verification for language failed. The return code is rc and the error reason code is erc. System Action: Strobe creates a Performance Profile, but it does not contain indexing information for language. User Response: STR2156W Contact Compuware Customer Support.

LOAD FAILED FOR MODULE modname Module modname did not load. Strobe creates a Performance Profile but it does not contain indexing Notify the Strobe system programmer.

Explanation: System Action: information. User Response: STR2157W

ISTROBE IS NOT LICENSED iStrobe is not licensed for your site. iStrobe does not initialize. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR2158W

ERROR PROCESSING DDIO FILE. RETURN CODE=xxxx. DDIO REASON CODE = nnnn

Explanation: The Reporter failed to access indexing information from the Compuware Shared Services (CSS) DDIO database. The return code is xxxx. The CSS reason code is nnnn. System Action: Strobe continues creating a Performance Profile but the Profile will not contain indexing information from the DDIO database. User Response: When the return code = 12, the most likely cause is that Strobe could not find the CSS interface module, CWPIDRVB. Ensure that the UI_STRCSS field of the Strobe parmlib member specifies the load library where module CWPIDRVB is located (the load library where CSS was installed). If you are creating the Performance Profile in background, ensure that the CSS load library is concatenated in STEPLIB.

When the return code = 8 and the DDIO reason code = 176, either no DDIO file was provided or the file provided was not in a proper DDIO format. DDIO files are identified in JCL by DD statements in the following format:
//SLSF00n DD DISP=SHR,DSN=DDIO.LISTING.FILE

where n is a number from 1 - 8. For other combinations of return code and reason code values, notify the Strobe system programmer.
STR2159I DDIO LISTING AND LOAD LIBRARY DATE TIME STAMPS FOR CONTROL SECTION xxxxxxxx DO NOT AGREE DDIO DATE = MM/DD/YY-HH:MM:SS LOAD LIBRARY DATE = MM/DD/YY-HH:MM:SS DDIO DDNAME = dddddddd Explanation: The Reporter was unable to find a DDIO listing whose date/time stamp matches the date/time stamp of the observed module. The Reporter found a listing with the same name but a different date/time stamp. The listing was found in the DDIO file of DDNAME dddddddd.

Messages Produced by Strobe

3-53

System Action: Depending on the setting of the DDIODATE parameter, the mis-matched source is either used or not used. See the immediately following message to determine which. User Response: Ensure that all listings that match the measured modules are provided in the DDIO file referenced by the Reporter JCL or that the DDIODATE parameter = N. STR2160W MORE THAN 100 DDIO LISTING AND LOAD LIBRARY DATE TIME STAMPS DO NOT AGREE

Explanation: Strobe has issued message STR2159I 100 times. No more STR2159I messages will be issued. System Action: The Reporter will continue trying to use the best listing available for indexing, but will no longer report mismatch errors. User Response: Ensure that all listings which match the measured modules are provided in the DDIO file referenced by the Reporter JCL. STR2161W CSS RELEASE xxxxxxxx POST-PROCESSOR LISTINGS NOT SUPPORTED WITH STROBE

Explanation: Version xxxxxxxx of Compuware Shared Services (CSS) is not supported by Strobe. To get accurate indexing information from CSS DDIO files, update the version of CSS. System Action: Strobe attempts to index from the DDIO files, but the program listings used may not match the programs measured. User Response: STR2162W Request that your system administrator update to the current release of CSS.

CSS RELEASE xxxxxxxx REQUIRES PTF yyyyyyyy WHEN USED WITH STROBE

Explanation: Version xxxxxxxx of Compuware Shared Services (CSS) requires that PTF yyyyyyyy be applied when used with Strobe. System Action: Strobe attempts to index from the DDIO files, but the program listings used may not match the programs measured. User Response: release. STR2163E Request that your system administrator apply the required maintenance CSS

MEASUREMENT/REPORTER FILTER MISMATCH

Explanation: You entered DDF requester report filters that do not correspond to the DDF requester parameters used for the measurement. System Action: Strobe does not process the request.

User Response: Use the DDF requester report filters that match the DDF requester parameters used for the measurement. STR2164E MAX OF 2 FILTERS ALLOWED You entered more than two DDF requester report filters. Only two filters are Strobe does not process the request. Specify filters that correspond to the DDF requester parameters used for the

Explanation: permitted. System Action: User Response: measurement. STR2166I

INDEXING MAY BE INACCURATE See preceding message STR2159I.

Explanation:

System Action: Strobe uses the listing identified in the message to generate indexing information for the measured program, but the information may be inaccurate. User Response: Ensure that all listings that match the measured modules are provided in the DDIO file referenced by the Reporter JCL STR2167I INDEXING IS DISABLED FOR THIS MODULE See preceding message STR2159I. Indexing is disabled for this module.

Explanation: System Action:

User Response: Ensure that all listings that match the measured modules are provided in the DDIO file referenced by the Reporter JCL or that the DDIODATE parameter = N.

3-54

Strobe Messages Guide

STR2168I

NO SOURCE FOUND IN DDIO FOR CONTROL SECTION xxxxxxxx The Reporter was unable to find a DDIO listing for the observed module. Indexing is disabled for this module.

Explanation: System Action:

User Response: Ensure that listings that match the measured modules are provided in the DDIO file referenced by the Reporter JCL. STR2191W ERROR IN WRITING SORT-OUT FILE IN P11 PASS2

Explanation: Strobe encountered an error while the internal report record from the sort was being written. System Action: incomplete. User Response: STR2192E Strobe continues processing and creates a Performance Profile but it will be Notify the Strobe system programmer.

STORAGE REQUEST FAILED.TYPE=type, RC=rc, REASON=reason A request for additional storage failed.

Explanation:

System Action: Strobe continues processing but the information in the Performance Profile could be incomplete. User Response: STR2200W Notify the Strobe system programmer.

UNDEFINED COMMAND ENCOUNTERED - COMMAND CODE=commandname Strobe encountered an unknown command, commandname. The command does not appear on the reports. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR2300S status

{OPEN|CLOSE|READ|WRITE} ERROR ON DDNAME {SYSUT1|SYSPRINT} FILE STATUS =

Explanation: The Reporter encountered an open, close, read, or write error while accessing SYSUT1 or SYSPRINT. The file status is status. If access to SYSPRINT caused the problem, the Reporter displays this message on SYSOUT. System Action: User Response: programmer. The Reporter terminates and does not produce a Performance Profile. Verify the dataset name. If the name is correct, notify the Strobe system

STR2309S PROFILE DATASET ALREADY IN USE, TRY LATER. DATA SET IS ALLOCATED TO ANOTHER JOB OR USER. Explanation: The Reporter encountered an allocation error while attempting to delete an existing Profile dataset. The file was in use by another job or user. System Action: Strobe stops processing and will not have created a profile data file. User Response: job again. Wait until the other job or user has released the Profile dataset and try this

STR2310S {ALLOCATION|UNALLOCATION} ERROR FOR {XML FILE|XML WORK FILE} REASON CODE=rsncode INFO CODE=infocode RET CODE=rc Explanation: The Reporter encountered an allocation error while attempting to create or delete either the Profile data file or a Profile data workfile for use by iStrobe. The reason code is rsncode, the information code is infocode, and the system return code is rc. System Action: Strobe stops processing and may not have created a Profile data file or a Profile data workfile. User Response: Ensure that the unit name and volume serial number specified on the Strobe - iStrobe Performance Profile Options panel is correct and resubmit the request. STR2320S {OPEN|CLOSE} ERROR ON {XML FILE|XML WORK FILE} STATUS=status

Explanation: The Reporter encountered an I/O error while attempting to access a Profile data file or a Profile data workfile for use with iStrobe and shows the file status status.

Messages Produced by Strobe

3-55

System Action: Strobe stops processing and may not have created a Profile data file or a Profile data workfile. User Response: If the problem is with a Profile data file, ensure that the unit name and volume serial number specified on the Strobe - iStrobe Performance Profile Options panel is correct and resubmit the request. Also verify that the unit name specified with the UI_WORKUNIT parameter in the Strobe parmlib member is correct. If you believe the mainframe has insufficient space for the work file, you may change the parameters for a temporary work file. To do this, see Specifying Parameters for a Temporary Work File for iStrobe in the Strobe User Guide. Otherwise, notify the Strobe system programmer. STR2400S UNSUCCESSFUL COMPLETION OF SORT IN modname - SORT RETURN CODE=sortrc

Explanation: The installation-supplied sort/merge program named in modname did not complete execution successfully and returned a sort return code of sortrc. System Action: Strobe produces a Performance Profile but no attribution data appears in it.

User Response: Review the messages produced by the sort/merge program to determine the cause of the problem. STR2401I ATTRIBUTION REPORT TOTALS WERE BELOW percent %

Explanation: Execution in all modules for which Strobe normally produces Attribution reports is below the specified baseline percentage percent. System Action: Strobe produces a Performance Profile but no attribution data appears in it.

User Response: To generate the Attribution reports, use the Reporter ATTR=nn.n parameter (default 2) to set the baseline percentage below that displayed in the message. STR2402W ATTRIBUTION TABLE OVERFLOW

Explanation: An internal table of the Reporter program overflowed. The maximum number of Reporter-related Strobe errors that can be reported exceeded the maximum of 50. System Action: incomplete. User Response: STR2501I Strobe continues processing, but data in the Attribution reports may be Notify the Strobe system programmer.

ADSO TABLE OVERFLOW An internal table of the Reporter program overflowed. Strobe continues processing, but data in the ADS/O reports may be Notify the Strobe system programmer.

Explanation: System Action: inaccurate. User Response: STR2603I

CICS ITEMS PROCESSED..... nnn SORT RECORDS WRITTEN ..... xxx Indicates nnn number of records processed and xxx number of sort records None required. None required. This information appears for diagnostic purposes.

Explanation: written. System Action: User Response: STR2604I

PERIODS......nnnn LASTPERIOD......xxxx Indicates nnnn number of periods reported and xxxx number of periods None. None required. This information appears for diagnostic purposes.

Explanation: processed. System Action: User Response:

STR2605W COUNTER ROLLOVER OR CICS AUTOMATIC STATISTICS IN OPERATION - VALUES OF RESET COUNTERS HAVE BEEN ESTIMATED Explanation: The CICS counters were reset to zero at least once during the session, for one of these reasons:

The CICS counters rolled over. A user issued a reset command.

3-56

Strobe Messages Guide

This message precedes two lines of data that list the values in the counter fields at the time of the last rollover.
System Action: Strobe estimates the values of the counters that have been set to zero and continues sampling. The CICS statistics in the Performance Profile may be inaccurate. User Response: Determine the interval period from the Strobe system programmer and then remeasure the region with Strobe, knowing that the CICS statistics will be reset at the end of that interval. STR2606E DATA FOR FEWER THAN 100 PERIODS RECEIVED

Explanation: Fewer than 100 periods are represented in the sample dataset because the user issued a STOP, SWITCH, or QUIT command. These commands prevent Strobe from completing the measurement. You do not need to issue these commands because Strobe terminates automatically when it collects the target number of samples. System Action: The reports Strobe produces in the CICS Performance Supplement may not be statistically significant. User Response: STR2611I Rerun the measurement session and do not issue a STOP or QUIT command.

SORT OUTPUT RECORDS PROCESSED nnn INTERMEDIATE RECORDS WRITTEN xxx

Explanation: Indicates that nnn records were produced from the sort process and that xxx sorted records were processed. System Action: User Response: STR2612E None. None required. This information is used for diagnostic purposes.

INVALID REPORT NUMBER nnn time

Explanation: The Reporter encountered an invalid report number nnn at relative time time (beginning, during, or end) in the internal report file for the CICS supplement. System Action: information. User Response: STR2613E Strobe will create a Profile but it will not include CICS supplement Notify the Strobe system programmer.

INVALID REPORT START nnn

Explanation: The Reporter encountered an error in the internal Report file for the CICS supplement. The internal report number is nnn. System Action: Strobe will create a Performance Profile but it will not include CICS supplement information. User Response: STR2614E Notify the Strobe system programmer.

INVALID REPORT END nnn

Explanation: The Reporter encountered an error in the internal Report file for the CICS supplement. The internal report number is nnn. System Action: Strobe will create a Performance Profile but it will not include CICS supplement information. User Response: STR2615E Notify the Strobe system programmer.

INVALID XSU-RECORD-TYPE type time

Explanation: The Reporter encountered an error with record type type at relative time time (beginning, during, or end) in the Transaction Usage Summary report file for the CICS supplement. System Action: Strobe will create a Performance Profile but it will not include CICS supplement information. User Response: Notify the Strobe system programmer.

Messages Produced by Strobe

3-57

STR2616E INVALID DXP-RECORD-TYPE type time PERIOD xxx RESOURCE NAME name RESOURCE TYPE type BEGIN-END v Explanation: The Reporter encountered an error with record type type at time time at period xxx in resource name name with resource type type at beginning and ending at v. The error occurred while processing the Time Distribution of Transactions, Inputs, Processing and Outputs report. System Action: Strobe will create a Performance Profile but it will not include CICS supplement information. User Response: STR2617E Notify the Strobe system programmer.

INVALID TRANSIENT DATA QUEUE TYPE nnnn (INITIALIZATION)

Explanation: The Reporter encountered an error in the internal Report file for the CICS supplement. Transient data queue type is nnnn. System Action: Strobe will create a Performance Profile but the CICS supplement information will be incomplete. The Input - Output Activity report will not include the Number of Output Operations to Transient Data Queues section. User Response: STR2622E Notify the Strobe system programmer.

INVALID REPORT NUMBER nnn

Explanation: The Reporter encountered an error in the internal Report file number for the CICS supplement. The internal report number is nnn. System Action: Strobe will create a Performance Profile but the CICS supplement information will not be accurate. User Response: STR2623E Notify the Strobe system programmer.

NEGATIVE DXA COUNT PERIOD =xxx VALUE = value OCCURRENCE = occurrence

Explanation: The Strobe sample file contains incorrect CICS terminal message count data for recording period xxx. The VALUE value and OCCURRENCE occurrence provide internal diagnostic information. System Action: Strobe creates a Performance Profile; however, the CICS Time Distribution of Activity reports are incomplete. User Response: Save the sample file and contact the Strobe system programmer.

STR2624E NEGATIVE DXS COUNT PERIOD = xxx MSG COUNT = msgcount TRANSIT SAMPLES = samples OCCURRENCE = occurrence Explanation: The Strobe sample file contains incorrect CICS transaction service time data for recording period xxx. The MSG COUNT msgcount, TRANSIT SAMPLES samples, and OCCURRENCE occurrence provide internal diagnostic information. System Action: Strobe creates a Performance Profile, however, the CICS Time Distribution of Transaction Activity reports are incomplete. User Response: STR2625E Notify the Strobe system programmer.

NEGATIVE DDB COUNT PERIOD = xxx DB COUNT= dbcount OCCURRENCE = occurrence

Explanation: The Strobe sample file contains incorrect CICS Data Base Access statistical data for recording period xxx. The DB COUNT dbcount and OCCURRENCE occurrence are internal diagnostic information. System Action: Strobe creates a Performance Profile; however, the CICS Time Distribution of Transaction Activity reports are incomplete. User Response: STR2626W Save the sample file and notify the Strobe system programmer.

COUNTER ROLLOVER OCCURRED DURING THE MEASUREMENT SESSION

Explanation: The CICS counters were reset to zero at least once during the session. This could be caused by the CICS counters rolling over (passing zero) or by a user-initiated reset command. This message precedes two lines of data that list the values in the counter fields at the time of the last rollover.

3-58

Strobe Messages Guide

System Action: Strobe estimates the values of the counters that have been set to zero and continues sampling. The CICS statistics in the Performance Profile might be inaccurate. User Response: STR2627E Save the sample dataset, and contact the Strobe system programmer.

INVALID STATE, nnn

Explanation: Strobe detected an error in the CICS supplement report file. nnn contains diagnostic information. System Action: information. User Response: STR2628E Strobe will produce a Performance Profile, but it will not include CICS Notify the Strobe system programmer.

INVALID ITEM TYPE type

Explanation: The Reporter encountered an invalid record of type type while producing the CICS supplement System Action: information. User Response: STR2650W Strobe will produce a Performance Profile but it will not include CICS Notify the Strobe system programmer.

HISTOGRAM SCALE CHANGED FOR QUERY queryname [PROC procname]

Explanation: Because of a table overflow error while creating the CPU Usage by SQL Statement report, Strobe encountered a Query (queryname) whose CPU usage was greater than the maximum previously calculated and printed. If the Query is part of a Procedure, then Strobe displays the Procedure name as well (procname). System Action: Strobe continues printing the report. The numerical values in the CPU usage column are correct, but the histogram may not accurately depict the CPU usage. User Response: To determine which statement consumed the most CPU time, refer to the numerical values in the CPU Usage column rather than the histogram spikes. STR2651C HEADER RECORD MISSING FOR queryname querytime

Explanation: Strobe could not find the header record for Query queryname, compiled at querytime. This message can appear when you quit the measurement session, not allowing it to terminate normally. The Reporter is attempting to match attribution records with DBRM records that have not yet been written. System Action: Strobe produces the Performance Profile, but the header information for Query queryname might be incomplete. User Response: STR2652C Notify the Strobe system programmer.

SQL STATEMENT NUMBER EXCEEDS MAXIMUM OF 99,999,999

Explanation: The SQL statement number, derived from the program listing, exceeds Strobes maximum capacity of 99,999,999. System Action: Strobe produces the Performance Profile, but the CPU Usage by SQL Statement report will not be able to relate SQL statement activity to its full statement text. iStrobe will be unable to link statement activity to statement text. User Response: If possible, divide very large programs into smaller programs, so that statement numbers greater than 99,999,999 will not be generated. STR2701W libname HISTOGRAM SCALE CHANGED FOR 4GL PROGRAM NAME progname IN LIBRARY

Explanation: An overflow occurred in an internal table of the Strobe Reporter program while processing data for the Natural 4GL program named progname from the library libname. System Action: Strobe continues printing the report. The numerical values in the CPU usage column are correct, but the histogram might not accurately depict the CPU usage. User Response: To determine which statement consumed the most CPU time, refer to the numerical values in the CPU Usage column rather than the histogram spikes.

Messages Produced by Strobe

3-59

STR2702C FNR= fnr

HEADER RECORD MISSING FOR progname LIB= libname TRANID= tranid DBID= dbid

Explanation: Strobe for Adabas/Natural could not locate the header record for the Natural 4GL program progname, from the Natural program library libname, transaction ID tranid (if executed under CICS), Adabas database ID dbid (for the Natural program library), and Adabas file number fnr (for the Natural program library). System Action: Strobe produces the Performance Profile, but the header information for program progname might be incomplete. User Response: Notify the Strobe system programmer.

STR2703W MAP DATA SET VERSION DOES NOT MATCH SAMPLE DATA SET VERSION OF PGM= progname LIB= libname DBID= dbid FNR= fnr Explanation: The Reporter detected a discrepancy between the map dataset and the Natural 4GL program progname, from the Natural program library libname, Adabas database ID dbid (for the Natural program library), and Adabas file number fnr (for the Natural program library). System Action: Strobe produces a Performance Profile, but it does not contain any indexing information for program progname. User Response: STR2705W Create a new map dataset and resubmit the Performance Profile request.

INSUFFICIENT DATA FOR PROGRAM NAME progname

Explanation: Strobe for Adabas/Natural identified Natural 4GL program progname as executing in the target address space, but it did not attribute any CPU or wait activity to that program. System Action: Strobe produces a Performance Profile, but information for the Natural program is missing. User Response: Rerun the measurement session, and specify a larger target sample size.

STR2780W HISTOGRAM SCALE CHANGED FOR DL/I TRANSACTION trans MODULE modname CSECT csectname PSB psb Explanation: An internal table of the Strobe Reporter overflowed while processing data for DL/I (CPU or WAIT), transaction trans, module modname, csect csectname, PSB psb. System Action: Strobe continues printing the report. The numerical values in the CPU usage column are correct, but the histogram might not accurately depict the CPU usage. User Response: To determine which statement consumed the most CPU time, refer to the numerical values in the CPU Usage column rather than the histogram spikes. STR2781W SSA TABLE OVERFLOWED FOR TRANSACTION trans MODULE modname CSECT csectname PSB psb Explanation: An internal table of the Strobe Reporter overflowed while processing data for DL/I, transaction trans, module modname, csect csectname, PSB psb. System Action: User Response: The Reporter writes the SSA table and continues processing. Notify the Strobe system programmer. Online Reporter Messages

Online Reporter Messages


When executed with Strobe/ISPF, the Reporter returns the following messages.
STR2811W SCREEN SIZE PARAMETER ERROR

Explanation: The SCROLL keyword is missing or misspelled, or you have specified an invalid value for this screen size parameter. SCROLL must be a numeric value within the range from 24 through 99. System Action: User Response: request. The online Reporter uses the default value of 24 and continues execution. Ensure that the specified screen size parameter is correct and resubmit the

3-60

Strobe Messages Guide

STR2812E

UNRECOGNIZABLE REPORT TITLE

Explanation: The online Reporter encountered a Performance Profile report title that it does not recognize. System Action: Strobe stops execution and produces an incomplete Performance Profile that includes any reports generated up to the line of error. User Response: Notify the Strobe system programmer.

Sample Dataset Utility Program Messages


The sample dataset utility program STRBDSPY returns the following message.
STR2900S status {OPEN|CLOSE|WRITE} ERROR ON DDNAME {STRSAMPL|SYSPRINT} FILE STATUS =

Explanation: The Sample Dataset Utility Program encountered an open, close, or write error while accessing the sample dataset STRSAMPL or the report file SYSPRINT. The file status is status. If access to SYSPRINT caused the problem, the Reporter displays this message on SYSOUT. System Action: User Response: programmer. The Sample File Display Program terminates. Verify the dataset name. If the name is correct, notify the Strobe system

Messages Returned by Strobe for CA Gen


Strobe for CA Gen returns the following messages.
STR2926C ACTION DIAGRAM SUMMARY REPORT EXCEEDED LIMITS An internal table has overflowed.

Explanation:

System Action: Strobe produces the Action Diagram Summary report; however, the information in the report is incomplete. User Response: STR2927C Notify the Strobe system programmer.

AD-DET-TABLE OVERFLOWED FOR ACTION DIAGRAM action diagram The AD-DET-TABLE table overflowed.

Explanation:

System Action: Strobe does not produce an Action Diagram Statement report for the action diagram action diagram. User Response: STR2928C Notify the Strobe system programmer.

AD-STMT-TABLE OVERFLOWED FOR ACTION DIAGRAM action diagram The AD-STMT-TABLE table overflowed.

Explanation:

System Action: Strobe does not produce an Action Diagram Statement report for the action diagram action diagram. User Response: STR2929C Notify the Strobe system programmer.

NO DIAGRAM SAMPLED OR SCHEMA RELEASE NOT SUPPORTED

Explanation: Strobe for CA Gen did not identify a CA Gen, AllFusion Gen, Advantage Gen, or COOL:Gen generated module containing action diagram statements, or Strobe for CA Gen does not support the release of CA Gen, AllFusion Gen, Advantage Gen, or COOL:Gen that generated the application modules. Schema refers to an internal number that identifies the release level of the software. System Action: Strobe continues sampling but does not create reports for CA Gen.

To determine the Schema Release Level number, see the SUBSYSTEM field on the Measurement Session Data report. If this field identifies a release level that Strobe for

Messages Produced by Strobe

3-61

CA Gen supports, measure a program that is experiencing more activity. If this field does not reflect a schema number, then Strobe for CA Gen could not determine the

release level. If there is no schema number, review the Strobe Program Usage Summary report and the Program Usage by Procedure report to see which modules Strobe identified. Contact Compuware Customer Support to resolve the problem.

SQL Analysis Messages Returned by the Reporter


The Reporter returns the following SQL analysis messages.
STR2950S INVALID SERVICE CALL REQUEST RETURN CODE = rc

Explanation: The Reporter generates this message when an invalid Strobe SQL analysis service call request is coded. The return code is rc. System Action: The Reporter produces Performance Profile data, but it does not include any SQL analysis reports. User Response: STR2951S Contact Compuware Customer Support.

STRANArr MODULE NOT FOUND RET CODE = rc

Explanation: The Reporter generates this message when the Strobe SQL analysis load module for DB2 release rr could not be located. The return code is rc. System Action: The Reporter produces Performance Profile data but it does not include any SQL analysis reports. User Response: STR2952E Notify the Strobe system programmer.

SQL ANALYSIS FILE iotype ERROR OCCURRED

Explanation: Strobe SQL analysis encountered the file error identified by iotype, which is either OPEN, READ, WRITE, or CLOSE. Processing for the current Performance Profile stops. System Action: The Reporter produces Performance Profile data, but it does not include any SQL analysis reports. User Response: If your site does not allow users to allocate temporary datasets to VIO, check that you have uncommented the allocation of the SYSTMPnn datasets and entered valid units for CLIST member Strobe and skeleton STRBPJCL. If the problem persists, contact Compuware Customer Support. STR2953E DB2 RELEASE MISMATCH. SAMPLE IS release1. DSNLOAD IS release2. SQL ANALYSIS NOT EXECUTED Explanation: The release of DB2 in the sample file release1 does not match the release of the DB2 load libraries, release2, provided to the SQL analysis component of the Reporter. System Action: Strobe generates Performance Profile data but does not produce any SQL analysis reports. User Response: Ensure that the DB2 load libraries provided for the Reporter execution are the same release as the load libraries used by the target program when the sample dataset was created. STR2954I MODULE modname AT VERSION ver PTF LEVEL level

Explanation: The Strobe SQL analysis module modname is at version ver and PTF level level. The verification program produces this message. System Action: User Response: STR2955I The verification program continues. None required.

DB2 VERSION FOR THIS EXECUTION IS ver. VERSION OBTAINED FROM DSNHDECP

Explanation: The DSNHDECP module obtained from the DB2 load library in the STEPLIB DD statement was at DB2 version ver.

3-62

Strobe Messages Guide

System Action: User Response: STR2956E

The verification program continues. None required.

UNABLE TO FIND DBRM dbrm IN DBRMLIB. VERIFY THAT THE DBRMLIB IS CORRECT

Explanation: The verification program could not find the Strobe SQL analysis DBRM dbrm specified in the DBRMLIB DD statement. System Action: The verification program continues and will end with a return code of 8.

User Response: Resubmit the job with the CNTL dataset containing the DBRM used to bind the Strobe SQL analysis plan. STR2957I PLAN plan PACKAGE package CONTOKENS MATCH

Explanation: The Strobe SQL analysis plan plan package package contains the DBRM that was shipped in the Strobe CNTL dataset. System Action: User Response: The verification program continues. None required.

STR2958E PLAN plan PACKAGE package CONTOKENS DO NOT MATCH. PLEASE REBIND THE STROBE SQL ANALYSIS PLAN Explanation: The Strobe SQL analysis plan plan package package does not contain the DBRMs that are in the DBRMLIB DD statement. System Action: User Response: CNTL dataset. The verification program continues and will end with a return code of 8. Rebind the Strobe SQL analysis plan using the DBRMs shipped in the Strobe

STR2959E PLAN plan PACKAGE package NOT FOUND IN THE DBRM TABLE. ENSURE THAT THE DBRMLIB IS CORRECT Explanation: The bound Strobe SQL analysis plan plan package package in DB2 does not contain the DBRMs contained in the DBRMLIB DD statement. System Action: User Response: CNTL dataset. STR2960I The verification program continues and will end with a return code of 8. Rebind the Strobe SQL analysis plan using the DBRMs shipped in the Strobe

EXECUTE AUTHORITY ON PLAN plan GRANTED TO user1 BY user2

Explanation: The user identified by user1 can execute the Strobe SQL analysis plan plan. The user identified by user2 granted the authority. System Action: User Response: The verification program continues. None required.

STR2961W MODULE modname AT VERSION ver PTF level IS DOWN LEVEL. PLEASE DELETE FROM THE LOAD LIBRARY Explanation: The Strobe SQL analysis module modname is at a lower version and PTF level than other SQL analysis modules found in the STROBLIB DD dataset. The version is ver and the PTF level is level. System Action: User Response: library. STR2962E INSTALLED The verification program continues and will end with a return code of 4. Compuware suggests that you delete the older modules from the Strobe

UNABLE TO READ STROBLIB DIRECTORY OR STROBE SQL ANALYSIS IS NOT

Explanation: Either Strobe encountered an error while reading the STROBLIB directory or it found no Strobe SQL analysis modules. System Action: User Response: The verification program terminates with a return code of 8. Notify the Strobe system programmer.

Messages Produced by Strobe

3-63

STR2963E

LINK TO STROBE SQL ANALYSIS FOR VERSION FAILED

Explanation: The verification program was unable to link the Strobe SQL analysis modules to obtain version and PTF information. System Action: User Response: STR2964E The verification program continues and will end with a return code of 8. Notify the Strobe system programmer.

NO DSNHDECP MODULE FOUND

Explanation: The verification program was unable to locate the DB2 module DSNHDECP to obtain DB2 version information. System Action: User Response: The verification program terminates with a return code of 8. Supply the correct DSNLOAD dataset in the STEPLIB DD.

STR2965E DB2 RETURNED A NON ZERO RETURN CODE. ABEND U0099 FOLLOWS. CHECK REG 15 AND REG 0 Explanation: Strobe received a nonzero return code from DB2 when attempting to obtain DB2 catalog information about the Strobe SQL analysis plan. System Action: User Response: STR2966S The verification program terminates with a user ABEND of U0099. Determine the cause of the Strobe SQL analysis failure and resubmit the job.

SQLAF PROCESSING STOPPED DUE TO DB2 SYSTEM MODE. RC=xx

Explanation: EXPLAIN information is not available, because of an incompatibility between the DB2 systems on which the sample dataset and the profile were created. The return code can be one of the following:

85 The sample dataset is from a DB2 subsystem running in the new function mode, but the Profile was generated from a DB2 system running in compatibility mode. These two subsystems are incompatible. 86 The sample dataset is from a DB2 subsystem running in the compatibility mode, but the Profile was generated from a DB2 system running in the new function mode. These two subsystems are incompatible. 87 The DB2 system identified by the subsystem ID in the sample dataset is running in the enabling new function mode, which is not supported. 88 The sample dataset is from a DB2 system running in the enabling new function mode, which is not supported. 89 Strobe was unable to determine the mode of the DB2 system from the subsystem ID contained in the sample dataset.
System Action: Strobe produces an iStrobe profile data file, but it does not include any SQL analysis reports. User Response: STR2967I Notify the Strobe system programmer

USERAUTH TRACE = P , MONITOR2 = P granted to EEEEEEEE by OOOOOOOO

Explanation: P is the privilege: blank = not held, G = held with the GRANT option, Y = held without the GRANT option. EEEEEEEEE is the authorization ID (user) who holds the privilege. OOOOOOOO is the authorization ID (user) who granted the privilege. System Action: Installation verification.

User Response: Used to verify the SSA address space has TRACE and MONITOR2 privilege in a DB2 Subsystem.

3-64

Strobe Messages Guide

STR2968S

FATAL ERROR, RC=xx FROM SQLAF function

Explanation: function is INIT, OPEN, CLOSE or TERM. EXPLAIN information is not available because of an internal error in Compuwares SQLAF processor. The return code xx is unpredictable. System Action: Strobe produces an iStrobe profile data file, but it does not include any SQL analysis reports. User Response: Notify the Strobe system programmer.

Messages Returned by the Strobe SQL Agent


The Strobe SQL Agent enables Strobe to keep track of multi-system DB2 environments.
STR3000I smid STROBE SQL AGENT READY.

Explanation: Strobe SQL Agent initialization has concluded and the named agent is ready to provide services. System Action: The Strobe SQL Agent waits for an operator MODIFY command or direction from the Strobe session manager. User Response: STR3001I None required.

smid STROBE SQL AGENT TERMINATION IN PROGRESS. The internal STOP command has been accepted by the named agent.

Explanation:

System Action: Control is given to the termination routine. This message is normally followed by message STR3003I. User Response: STR3002W None required.

SQL Agent detected ******** delay, ********' The Strobe SQL Agent is unable to contact the Strobe Session Manager.

Explanation:

System Action: This message is repeated every 20 seconds until connection is established or 2 minutes is reached. User Response: None required unless the 2-minute threshold is reached, at which time this message will be followed by an error message. At that time, contact Compuware Customer Support. STR3003I smid STROBE SQL AGENT TERMINATION IS COMPLETE. The Strobe SQL Agent termination processing has concluded for the named Control returns to MVS. None required.

Explanation: agent. System Action: User Response: STR3004I

STROBE SQL AGENT OPERATING with / without DB2 IMPLANT.

Explanation: This message is informative only and does not require any action on the part of the user. The message will say WITH when SSADB2HOOK=YES and will say WITHOUT when SSADB2HOOK=NO. This message appears in the Strobe SQL Agent JES2 log. System Action: User Response: STR3005I Processing continues. None required.

STRB RETRIABLE CONDITION: Condition Code / Reason Code, db2ssid

Explanation: An error has occurred in the Strobe SQL Agent during startup. The instructions causing the error will be retried. See additional following messages for more detailed information. System Action: The instructions causing the error are retried.

User Response: None required. This is an informational message for the use of Compuware Customer Support only.

Messages Produced by Strobe

3-65

STR3006W

SQL Agent idle. No DB2 systems found.

Explanation: The Strobe SQL Agent was unable to detect any DB2 subsystems to which it could connect. System Action: The Strobe SQL Agent remains idle.

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR3010I Strobe SQL agent termination - LOST SSIB. The Strobe SQL Agent termination message. Termination processing continues.

Explanation: System Action:

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR3011I Strobe SQL agent termination - 2RM0 left. The Strobe SQL Agent termination message. Termination processing continues.

Explanation: System Action:

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR3012I Strobe SQL agent termination - 2RMD left. The Strobe SQL Agent termination message. Termination processing continues.

Explanation: System Action:

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR3013I Strobe SQL agent termination - SRM0 left. The Strobe SQL Agent termination message. Termination processing continues.

Explanation: System Action:

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR3014I Strobe SQL agent termination - SRMD left. The Strobe SQL Agent termination message. Termination processing continues.

Explanation: System Action:

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR3020I STRv STROBE SQL AGENT version CHECKING FOR ALL ACTIVE DB2 SUBSYSTEMS.

Explanation: Strobe session manager detected that a DB2 system has been activated. STRvis the version of Strobe, usually STRB. System Action: Session manager sends a message to the Strobe SQL Agent to refresh its list of active DB2 systems. User Response: STR3030E None required.

smid FUNCTION ROUTINE xxxxxxxx NOT AVAILABLE. The function routine xxxxxxxx was not found in the load library. The named Strobe SQL Agent issues user ABEND 0300 and terminates.

Explanation: System Action:

User Response: If you are not running the Strobe SQL Agent from the target library specified at installation time, make sure that all of the modules that were installed are available in the new load library. Refer to the discussion of ABEND 0300 in ABEND Codes Returned by the Strobe SQL Agent on page 4-6. Otherwise, contact Compuware Customer Support.

3-66

Strobe Messages Guide

STR3040W

smid UNABLE TO OBTAIN LOCK(1). db2ssid.

Explanation: The Strobe SQL Agent encountered an error while preparing to install the SQL intercept for the DB2 subsystem db2ssid. System Action: intercepted. User Response: STR3041W Processing continues, but SQL for the named DB2 subsystem will not be Contact Compuware Customer Support.

smid UNABLE TO SCHEDULE. db2ssid.

Explanation: The Strobe SQL Agent encountered an error while preparing to install the SQL intercept for the DB2 subsystem db2ssid. The named DB2 subsystem may have been terminating. System Action: Processing continues, but SQL for db2ssid will not be intercepted.

User Response: If the named DB2 subsystem has terminated or is in the process of terminating, no response is required. Otherwise, contact Compuware Customer Support. STR3042W smid ADD FAILED. db2ssid.

Explanation: The Strobe SQL Agent encountered an error while preparing to install the SQL intercept for the DB2 subsystem db2ssid. System Action: User Response: STR3043W Processing continues, but SQL for db2ssid will not be intercepted. Contact Compuware Customer Support.

smid UNABLE TO OBTAIN LOCK(2). db2ssid.

Explanation: The Strobe SQL Agent encountered an error while preparing to install the SQL intercept for the DB2 subsystem db2ssid. System Action: User Response: STR3044W Processing continues, but SQL for db2ssid will not be intercepted. Contact Compuware Customer Support.

smid SQL INTERCEPT NOT INSTALLED. db2ssid.

Explanation: The Strobe SQL Agent encountered an error while preparing to install the SQL intercept for the DB2 subsystem db2ssid. System Action: User Response: STR3045I Processing continues, but SQL for db2ssid will not be intercepted. Contact Compuware Customer Support.

Global Branch-Entry Services(GBES) reloaded A common storage routine (ECSA) was found to be down level and was Strobe SQL Agent (SSA) reloads routine STRBGBES.

Explanation: reloaded. System Action:

User Response: This is an expected message if you previously started a lower version of Strobe and are now starting a higher level. This message should only occur once per uplevel version change. If the message persists, contact Compuware Customer Support. STR3050E smid RECOVERY ENTERED FOR ABEND=Sxxx Uyyyy REASON=rrrrrrrr. An ABEND was detected by the named Strobe SQL Agent.

Explanation:

xxx = The system ABEND code, if the ABEND was a system ABEND. yyyy = The user ABEND code, if the ABEND was not a system ABEND. rrrrrrrr = A reason code which gives additional information about the cause of the ABEND. If ABEND=S0000 U0300 and REASON=00040004, DB2 is not present on the MVS image but SSA=YES was specified in the Strobe parameter dataset. If no DB2 exists on this system, the parameter dataset should specify SSA=NO.
System Action: Recovery processing is performed and termination of the named SSA begins.

User Response: For system ABENDS, contact Compuware Customer Support. For user ABENDS, see Chapter 4, Abend Codes Returned by Strobe for further information about diagnosing the failure condition.

Messages Produced by Strobe

3-67

STR3051E

smid RECOVERY ENTERED FOR ABEND=Sxxx Uyyyy REASON CODE NOT AVAILABLE. An ABEND was detected by the named Strobe SQL Agent.

Explanation:

xxx = The system ABEND code, if the ABEND was a system ABEND. yyyy = The user ABEND code, if the ABEND was not a system ABEND.
System Action: Recovery processing is performed and termination of the named SSA begins.

User Response: For system ABENDS, contact Compuware Customer Support. For user ABENDS, in the Messages guide, see Chapter 4, Abend Codes Returned by Strobe for further information about diagnosing the failure condition. STR3052E smid PSW AT TIME OF ERROR ******** ********. This message follows STR3050E or STR3051E and provides the error PSW. Recovery processing continues. None required.

Explanation: System Action: User Response: STR3060E

smid INVALID COMMAND IGNORED. An operator MODIFY specified an invalid command. The operation is not performed; processing continues. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR3061W

UNSUPPORTED COMMAND. An operator MODIFY specified an invalid command. The operation is not performed; processing continues. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR3062I

smid DB2 SSID=db2ssid, STATUS= {ACTIVE | INACTIVE}.

Explanation: An operator MODIFY specified the LIST command. The Strobe SQL Agent issues this message in response to the command. db2ssid is the subsystem ID of the DB2 subsystem for which the status is being displayed. System Action: User Response: STR3069I Processing continues. None required.

smid COMMAND COMPLETE.

Explanation: Processing of the operator MODIFY command has completed for the named Strobe SQL Agent. System Action: User Response: STR3100E Processing continues. None required.

smid RECOVERY ENTERED FOR ABEND=Sxxx Uyyyy REASON=rrrrrrrr. An ABEND was detected by the SQL intercept for the named Strobe SQL Agent.

Explanation:

xxx = The system ABEND code, if the ABEND was a system ABEND. yyyy = The user ABEND code, if the ABEND was not a system ABEND. rrrrrrrr = A reason code which gives additional information about the cause of the ABEND.
System Action: Recovery processing is performed and processing continues.

User Response: For system ABENDS, contact Compuware Customer Support. For user ABENDS, in the Messages guide, see Chapter 4, Abend Codes Returned by Strobe for further information about diagnosing the failure condition. STR3101E smid RECOVERY ENTERED FOR ABEND=Sxxx Uyyyy REASON CODE NOT AVAILABLE. An ABEND was detected by the SQL intercept for the named Strobe SQL Agent.

Explanation:

xxx = The system ABEND code, if the ABEND was a system ABEND. yyyy = The user ABEND code, if the ABEND was not a system ABEND.

3-68

Strobe Messages Guide

System Action:

Recovery processing is performed and processing continues.

User Response: For system ABENDS, contact Compuware Customer Support. For user ABENDS, in the Messages guide, see Chapter 4, Abend Codes Returned by Strobe for further information about diagnosing the failure condition. STR3102E smid PSW AT TIME OF ERROR ******** ********. This message follows STR3100E or STR3101E and provides the error PSW. Recovery processing continues. None required.

Explanation: System Action: User Response: STR3103S

smid DB2 EXIT PROCESSING HAS BEEN TERMINATED.

Explanation: The error count for the designated subscriber (measurement) has been exceeded. Exits will not be driven for this measurement. System Action: User Response: STR3104E Processing continues but SQL reporting will be degraded. Contact Compuware Customer Support.

smid ******** ******** ******** ********. This message follows STR3102E and provides register content. Recovery processing continues.

Explanation: System Action:

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR3111E smid.routine text

Explanation: An internal processing error has occurred in source module routine smid.routine and is described in text: PrIf2000 Fif* Attach failed MainLoop Previous XmPost failed MainCkAct bad IftTyp PrIi $TRC Init failed PrIi FIFM Init failed PrIfIn Fif* Duplicate subtask PrIf2000 Fif* Attach macro failed' PrIf2000 Fif* Attach failed' System Action: User Response: STR3120I The measurement task terminates. Contact Compuware Customer Support.

smid.routine text

Explanation: This is an informational message, described in text, that Compuware Customer Support can use to determine the status of a measurement in the event of a problem:
STR3120I STR3120I STR3120I STR3120I STR3120I STR3120I STR3120I STR3120I STR3120I STR3120I STRBFIFM: STRBFIFM: STRBFIFM: STRBFIFM: STRBFIFM: STRBFIFM: STRBFIFM: STRBFIFM: STRBFIFM: STRBFIFM: Command STAM received , PTF XXXXXX Command STAM completed Command FLSH received Command FLSH completed Command FLSHE received Command FLSHE completed Command MAKZ received Command MAKZ completed SQL Activity Acknowledged Buffer Re-positioned

System Action: User Response: STR3121E

None. None.

smid.routine text

Explanation: An internal processing error has occurred in source module routine smid.routine and is described in text: xxxxxxxx Storage Obtain Failed

Messages Produced by Strobe

3-69

Invalid Return - LOCATE_QIT Invalid Return - LOCATE_QIT_ENTRY Invalid Return - PUT_STS_TEXT Entry Not Found on Stack System Action: User Response: STR3122W smid.text The named Strobe SQL Agent issues user abend U500 and terminates. Contact Compuware Customer Support.

Explanation: The Strobe Agent has encountered an unexpected situation in source module smid. It issues a warning message and attempts to continue. One of the following messages appears in text: Unable to Access SMO for Zxx Record Unable to Write Zxx Record to SDS Trigger Begin Missed Stored Procedure Begin Missed No Beginning Statement Found for End routine SQL Text Truncated to Max Allowed Load of DSNRLI Failed Load of DSNHLI2 Failed RRSAF IDENTIFY Failed RSAF SIGNON Failed CREATE THREAD Failed RRSAF Terminate Failed routine Select Failed, SQLCODE: XXX routine Open Failed, SQLCODE: XXX routine Fetch Failed, SQLCODE: XXX routine Close Failed, SQLCODE: XXX routine Repeat SMO Extension Request System Action: User Response: STR3150E Processing continues, but generic text may be substituted for actual SQL. Contact Compuware Customer Support.

STRBGBES Stimerm Set failed

Explanation: An internal timer to protect against excessive elapsed time for Strobe SQL Agent (SSA) requests has failed. System Action: User Response: STR3151E Processing continues without time-out protection. If the message persists, contact Compuware Customer Support.

STRBGBES Stimerm Cancel failed

Explanation: The cancellation of an internal timer to protect against excessive elapsed time for Strobe SQL Agent (SSA) requests has failed. System Action: User Response: STR3152E Processing continues. If the message persists, contact Compuware Customer Support.

STRBGBES Stimerm exit SSA request timeout, abending request

Explanation: A request for Strobe SQL Agent (SSA) services has taken more than 5 minutes to complete. System Action: The measurement task stops sampling and terminates with a user ABEND code of 522. The Measurement Session Data report will be incomplete. User Response: STR3200E Contact Compuware Customer Support.

STRBFIFR: Unable to obtain buffer for IFI commands

Explanation: Strobe DB2 IFCID Trace Collector was unable to obtain storage for the IFI command buffer. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'04'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer.

3-70

Strobe Messages Guide

STR3201I

STRBFIFR: Unable to start internal trace. Strobe DB2 IFCID Trace Collector was unable to start the internal trace. The Strobe DB2 IFCID Trace Collector internal trace will be inactive. No action is required. This is an informational message.

Explanation: System Action: User Response: STR3202E

STRBFIFR: Running from a non-APF library.

Explanation: Strobe DB2 IFCID Trace Collector has been attached from a non-APF authorized library. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'10'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3203E STRBFIFR: Invalid SQL agent environment detected

Explanation: Strobe DB2 IFCID Trace Collector was unable to find one or more runtime Strobe internal Control Blocks. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'08'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3204E STRBFIFR: Unable to load IFI parameters module.

Explanation: Strobe DB2 IFCID Trace Collector was unable to load the IFI parameters module STRBFIFP. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'0C'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3205E STRBFIFR: Unable to obtain storage for IFI buffer prefixes.

Explanation: Strobe DB2 IFCID Trace Collector was unable to obtain storage for the IFI buffer prefixes. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'14'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3206E STRBFIFR: Unable to obtain storage for IFI buffers. Strobe DB2 IFCID Trace Collector was unable to obtain storage for the IFI

Explanation: buffers.

System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'18'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3207E STRBFIFR: Unable to initialize IFI environment.

Explanation: Strobe DB2 IFCID Trace Collector was unable to connect to the DB2 subsystem where the measured application is running. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'1C'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation.

Messages Produced by Strobe

3-71

User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3208E STRBFIFR: Unsupported DB2 version.

Explanation: Strobe DB2 IFCID Trace Collector detected an invalid DB2 Version on the DB2 Trace Anchor Block. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'20'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3209E STRBFIFR: Unable to format start trace command

Explanation: Strobe DB2 IFCID Trace Collector was unable to format the DB2 start performance trace command. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'24'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3210E STRBFIFR: Unable to start performance trace. Strobe DB2 IFCID Trace Collector was unable to start the DB2 performance

Explanation: trace.

System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'28'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3211I STRBFIFR: Initialization complete - Id=9999

Explanation: Strobe DB2 IFCID Trace Collector has established the DB2 IFI collection environment successfully. Id=9999 uniquely identifies the IFI Collector. System Action: User Response: STR3212E None. No action is required. This is an informational message.

STRBFIFR: Unable to start internal timer. Strobe DB2 IFCID Trace Collector was unable to start its internal timer.

Explanation:

System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'30'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3213I STRBFIFR: Maximum idle time reached, subtask shutting down. Strobe DB2 IFCID Trace Collector idle time reached the maximum idle time

Explanation: allowed.

System Action: The Strobe DB2 IFCID Trace Collector subtask is terminated if the maximum idle time is reached and no measurement collection request is in progress. User Response: STR3214I No action is required. This is an informational message.

STRBFIFR: Shutdown in progress, DB2 terminated.

Explanation: Strobe DB2 IFCID Trace Collector has been posted by DB2 subsystem indicating that DB2 is terminating. System Action: The Strobe DB2 IFCID Trace Collector subtask is terminated, and any IFI collection in progress is aborted.

3-72

Strobe Messages Guide

User Response: STR3215E

No action is required. This is an informational message.

STRBFIFR: IFI Collector Id=9999 ran out of buffers(1111/2222/3333)

Explanation: Strobe DB2 IFCID Trace Collector, identified by Id=9999, has run out of buffers to collect the IFCIDS generated by DB2, where:

1111 = Number of buffers ready to reuse 2222 = Number of buffers busy with one reader 3333 = Number of buffers with more than one reader.
System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'44'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3216I STRBFIFR: IFI EXRACO Enqueued buffer (NNNN) to inprocess Q

Explanation: Strobe DB2 IFCID Trace Collector internal routine EXRACO has enqueued buffer NNNN to the in-process buffer queue. System Action: User Response: STR3217E The Strobe DB2 IFCID Trace Collector subtask continues processing. No action is required, this is an informational message.

STRBFIFR: IFI GTBUIP Unable to obtain inprocess queue lock

Explanation: Strobe DB2 IFCID Trace Collector internal routine GTBUIP was unable to obtain a lock on the in-process buffer queue in order to return processed buffers to available buffer queue. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'58'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3218E STRBFIFR: IFI PTBUIP Unable to obtain inprocess queue lock

Explanation: Strobe DB2 IFCID Trace Collector internal routine PTBUIP unable to obtain a lock on the in-process buffer queue in order to add a buffer to the queue. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'54'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3219E STRBFIFR: IFI Collector experiencing shortage of trace buffers

Explanation: Strobe DB2 IFCID Trace Collector has been unable to return buffers from the in-process buffer queue to the available queue, and the available buffer queue is empty. System Action: Strobe DB2 IFCID Trace Collector will enter a wait for the number of times specified in BUFFER_SHORTAGE_LOOP. If the wait time specified expires, the Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'44'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3220I STRBFIFR: IFI Collector pausing IFCID collection - Id=9999

Explanation: Strobe DB2 IFCID Trace Collector, identified by Id=9999, has entered in a WAIT loop attempting to recover from a shortage of buffers. System Action: User Response: The Strobe DB2 IFCID Trace Collector subtask continues processing. No action is required. This is an informational message.

Messages Produced by Strobe

3-73

STR3221I

STRBFIFR: IFI CKIPQU Enqueued buffer (NNNN) to available Q

Explanation: Strobe DB2 IFCID Trace Collector internal routine CKIPQU has enqueued buffer NNNN to the available buffer queue. System Action: User Response: STR3222E The Strobe DB2 IFCID Trace Collector subtask continues processing. No action is required. This is an informational message.

STRBFIFR: *** Error, load of DSNRLI/DSNALI failed ***

Explanation: Strobe DB2 IFCID Trace Collector invoked an MVS service to load the DB2 Attach stub, but the load request failed. System Action: Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, return code=x'1C'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3223E STRBFIFR: *** Error, load of DSNWLIR/DSNWLI2 failed ***

Explanation: Strobe DB2 IFCID Trace Collector invoked an MVS service to load the DB2 IFI Interface stub, but the load request failed. System Action: Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, return code=x'1C'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard and notify the Strobe system programmer. STR3224E STRBFIFR: <DBM1><PLANNAME> not using IFI interface

Explanation: The authorization ID associated with this connection is not authorized to use the specified plan name or the specified plan name does not exist. Another possible cause is that the allocation of the plan to the connection failed. Either a resource is unavailable or the requested resource (plan) is not known DB2. System Action: Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, return code=x'1C'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3225E STRBFIFR: PlanName=PPPPPPPP, DB2Id=DDDD

Explanation: The release of the DB2 Attachment Stub and the DB2 subsystem do not match, but are compatible to make the connection. System Action: Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, return code=x'1C'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3226I STRBFIFR: DDDD IFI <XXXXX> connection established

Explanation: Strobe DB2 IFCID Trace Collector has established an IFI connection to DB2 DDDD using an XXXXX attachment. System Action: User Response: STR3227I The Strobe DB2 IFCID Trace Collector subtask continues processing. No action is required. This is an informational message.

STRBFIFR: DDDD IFI <XXXXX> connection terminated

Explanation: Strobe DB2 IFCID Trace Collector has terminated an IFI connection to DB2 DDDD using an XXXXX attachment. System Action: User Response: The Strobe DB2 IFCID Trace Collector subtask continues processing. No action is required, this is an informational message.

3-74

Strobe Messages Guide

STR3228E

STRBFIFR: Unable to locate XXXX Strobe control block

Explanation: Strobe DB2 IFCID Trace Collector internal routine GTSTCB was unable to locate the XXXX Strobe Control Block. System Action: Strobe DB2 IFCID Trace Collector will issue the message STR3203, and the Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'08'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3229I STRBFIFR: Buffer too small to hold READS data(00E60815)

Explanation: Buffer provided by the Strobe DB2 IFCID Trace Collector to DB2 was not large enough to accommodate all the IFCIDS returned by DB2 for READS command. System Action: User Response: STR3230I The Strobe DB2 IFCID Trace Collector subtask continues processing. Allocate more storage for the return area, if possible.

STRBFIFR: No data was returned for requested command(00E60804) No data was returned from the READS or READA request. The Strobe DB2 IFCID Trace Collector subtask continues processing. No action is required. This is an informational message.

Explanation: System Action: User Response: STR3231I

STRBFIFR: MONITOR1 auth required, no data can be collected

Explanation: An authorization failure occurred. On a READA request, the ownership token specified did not match the owner of an active trace, or on either a READA or READS request, the user did not have the correct monitor authority. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'50'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3232I STRBFIFR: Multiple attempts of READS failed, READS abandoned

Explanation: Strobe DB2 IFCID Trace Collector reached the maximum limit of retries for a READS command. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'60'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3233I STRBFIFR: IFI monitor trace is no longer active

Explanation: Strobe DB2 IFCID Trace Collector is no longer connected to this instance of the DB2 subsystem. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'44'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3234I EXIFRA READA failed: RC=00000008,RSN=xxxxxxxx

Explanation: Internal IFI READA DB2 command, issued by the Strobe DB2 IFCID Trace Collector, failed with the return code (RC) and reason code (RSN) shown in the message. System Action: The Strobe DB2 IFCID Trace Collector subtask continues processing.

User Response: Check DB2 message DSN1720I READA ERROR, REASON=xxxxxxxx for a complete explanation of possible values for the reason code.

Messages Produced by Strobe

3-75

STR3235I

STRBFIFR: Buffer too small to hold READA data(00E60815)

Explanation: Buffer provided by the Strobe DB2 IFCID Trace Collector to DB2 was not large enough to accommodate all the IFCIDs returned by DB2 for a READA command. System Action: User Response: STR3236I The Strobe DB2 IFCID Trace Collector subtask continues processing. Allocate more storage for the return area, if desired.

STRBFIFR: Multiple attempts of READA failed, READA abandoned

Explanation: Strobe DB2 IFCID Trace Collector reached the maximum limit of retries for a READA command. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'44'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer. STR3237I STRBFIFR: Unable to obtain buffer for IFICID 106 Strobe DB2 IFCID Trace Collector was unable to obtain storage for the IFICID The Strobe DB2 IFCID Trace Collector subtask continues processing. Allocate more storage for the return area, if possible.

Explanation: 105 buffer. System Action: User Response: STR3238I

STRBFIFR: ******* trace already active for DB2 ####

Explanation: Strobe DB2 IFCID Trace Collector has been requested to initiate a new Local/DDF collector for DB2 ####, but a Local/DDF collection is already active. System Action: User Response: STR3239I The Strobe DB2 IFCID Trace Collector subtask continues processing. No action is required. This is an informational message.

STRBFIFR: IFI collector dispatching priority lower than DB2; data might be lost

Explanation: Strobe DB2 IFCID Trace Collector has detected that its dispatching priority is lower than the DB2 dispatching priority, which might lead the collector to miss data. System Action: The Strobe DB2 IFCID Trace Collector subtask continues processing.

User Response: Assign the Strobe DB2 IFCID Trace Collector the same or higher priority than the DB2 MSTR Address Space. STR3240I STRBFIFR: IFI EXRACO Detected no reader for buffer(NNN)

Explanation: Strobe DB2 IFCID Trace Collector internal routine EXRACO has been posted by DB2 with a complete buffer, but there is no measurement active to be posted. Buffer is ignored. System Action: User Response: STR3241I The Strobe DB2 IFCID Trace Collector subtask continues processing. No action is required. This is an informational message.

STRBFIFR: Buffer too small to hold READA data(00E60815-RC=4)

Explanation: Buffer provided by the Strobe DB2 IFCID Trace Collector to DB2 was not large enough to accommodate all the IFCIDS returned by DB2 for a READA command. System Action: User Response: STR3242E The Strobe DB2 IFCID Trace Collector subtask continues processing. Allocate more storage for the return area, if desired.

STRBFIFR: RRS not active, SQL capture is terminated.

Explanation: Strobe DB2 IFCID Trace Collector has detected that the RRS ATTACH is not active on this z/OS image. System Action: The Strobe DB2 IFCID Trace Collector is terminated with ABEND U400, reason code=x'1C'. See ABEND Codes Returned by the Strobe SQL Agent on page 4-6 for reason code explanation. User Response: Process the dump according to your installations standard, and notify the Strobe system programmer.

3-76

Strobe Messages Guide

STR3243I

STRBFIFR: Starting as a fffffffff Collector for DB2 ####

Explanation: Strobe SQL Agent is starting a SQL capture on DB2 SSID ####. The type of trace ffffffff is either Filtering or non-Filtering. System Action: The Strobe measurement continues.

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR3244I STRBFIFR: Collecting IFCIDS for Request: ####, Jobname: jjjjjjjj Strobe SQL Agent is starting a filtered SQL capture, request ####, on Jobname The Strobe measurement continues.

Explanation: jjjjjjjj. System Action:

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR3245I STRBFIFR: ******************

Explanation: Strobe SQL Agent has received a DB2 command failure. The applicable Strobe Error Message will follow one or more of these STR3245I messages. The DB2 messages with the reason for the failure will be shown in these STR3245I messages. System Action: attribution. User Response: STR3246I The Strobe measurement may terminate or continue without SQL Contact Compuware Customer Support.

STRBFIFR: text

Explanation: This is a generalized message used by the Strobe IFI Collector module to display environmental information. The main audience of this message is Compuware Customer Support, and the purpose is to provide information for problem resolution. The following environmental information is displayed in the text area:

Strobe module STRBFIFR V-S9 R-040200 ddmmmyy PTF nnnnnn hh.mm DB2 OPx Buffer size in effect: nnMBytes Staging IFI buffers on memory object Using % free storage for IFI buffers DB2 Performance trace started Max# of DB2 Traces Active for SSID=tttt Highest memobj address used...nnnn # of memobj blocks reused...nnnn # of memobj blocks enqueued...nnnn # of memobj blocks processed...nnnn Free storage above the line...nnnn Total storage for IFI buffers...nnnn CKBUMO nnnnnnnn memobj buffers returned Total HV Common Storage allocated...nnnn Total HV Common Storage available...nnnn IFI Collector entering special read mode IFI Collector exiting special read mode(failure/success).

System Action: IFI Collections Processing continues. The only exception is for the text Max# of DB2 Traces Active for SSID= tttt, which indicates that IFI collection is no longer possible because the maximum number of traces allowed by DB2 has been reached. In that case, the IFI Collector is terminated. User Response: None required. In the case of text Max# of DB2 Traces Active for SSID= tttt, resubmit the measurement later. STR3247E STRBFIFR: -STA TRA (PERF) command failed (timeout), shutdown in progress

Explanation: A DB2 -START TRACE (PERFORMANCE) request issued by the Strobe IFI Collector (STRBFIFR) has taken more than 1 minute to complete. System Action: The Strobe SQL Attributor (STRBDSNA) issues message STR8710E, and the measurement task stops sampling and terminates immediately. The Measurement Session Data report will be incomplete.

Messages Produced by Strobe

3-77

User Response: Check the DB2 MSTR and IRLM Address Space logs for messages related to locks/timeouts associated with the DB2 TRACE component. STR3248I STRBFIFR: IFI Collector resuming IFCID collection - Id=9999

Explanation: Strobe DB2 IFCID Trace Collector, identified by Id=9999, is resuming the IFCID Collection after the WAIT loop attempting to recover from a shortage of buffers. System Action: User Response: STR3249I The Strobe DB2 IFCID Trace Collector subtask continues processing. No action is required. This is an informational message.

STRBFIFC: DB2 Accounting rollup: ACCUMACC=##,ACCUMUID=##

Explanation: This is an informational message issued by the Strobe IFI Accounting Collector module to display the current values of DB2 parameters ACCUMAC and ACCUMUID. These parameters are used by DB2 to control the DB2 Accounting data generation for DDF/RRSAF. This message is intended to provide information for problem resolution by Compuware Customer Support. For an explanation of the possible values for ACCUMAC and ACCUMUID, see IBMs DB2 for z/OS Installation and Migration Guide (GC19-2974-03). System Action: User Response: IFI Collections Processing continues. None required.

Messages Returned by Data Collectors


Data collector programs return the following messages.
STR4010I STR5 STROBE SQL AGENT TERMINATION - 2RM0 LEFT The Strobe SQL agent issued this message at the final stage of termination. Normal termination continues. No action is required. This is an informational message.

Explanation: System Action: User Response: STR4010I

STR5 STROBE SQL AGENT TERMINATION - 2RMD LEFT The Strobe SQL agent issued this message at the final stage of termination. Normal termination continues. No action is required. This is an informational message.

Explanation: System Action: User Response: STR4030I

STR5 STROBE SQL AGENT TERMINATION - SRM0 LEFT The Strobe SQL agent issued this message at the final stage of termination. Normal termination continues. No action is required. This is an informational message.

Explanation: System Action: User Response: STR4040I

STR5 STROBE SQL AGENT TERMINATION - SRMD LEFT The Strobe SQL agent issued this message at the final stage of termination. Normal termination continues. No action is required. This is an informational message.

Explanation: System Action: User Response: STR4110E

GETMAIN FAILURE - CICS DATA COLLECTOR DISABLED

Explanation: A GETMAIN failure occurred when the CICS data collector was trying to obtain virtual storage for its work area. You can produce a Performance Profile without the CICS Performance Supplement. System Action: User Response: Strobe continues sampling without the CICS data collector. Notify the Strobe system programmer.

STR4411E smid CAPTURE NOT ACTIVATED. COUNTS OR TIMES WILL NOT BE AVAILABLE. RC=xx REASON=yy. Explanation: Strobe was unable to establish an intercept for this measurement.

3-78

Strobe Messages Guide

System Action: User Response: STR4114E

Processing continues. SQL reporting will not contain counts or times. Contact Compuware Customer Support.

subsys RELEASE NOT SUPPORTED Strobe does not support the version of the measured subsystem subsys.

Explanation:

System Action: Strobe continues sampling without the data collector for that subsystem. Attribution reports for the named subsystem will be incomplete. User Response: STR4116E Notify the Strobe system programmer.

CICS MODULE IDENTIFICATION SERVICE NOT INITIALIZED Strobe was unable to initialize the CICS data collector. Strobe continues sampling without the CICS data collector. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR4118E

LOAD OF modname FAILED - CICS DATA COLLECTOR DISABLED Strobe could not invoke Strobe for CICS because it could not find the module Strobe continues sampling without the CICS data collector. Notify the Strobe system programmer.

Explanation: modname. System Action: User Response: STR4120E

GETMAIN FAILURE - modname DISABLED

Explanation: A GETMAIN failure occurred when the modname tried to obtain virtual storage for its work area. System Action: Strobe continues sampling, but the reports in the CICS Performance Supplement might be incomplete. User Response: STR4122E Notify the Strobe system programmer.

ABEND THRESHOLD EXCEEDED - modname DISABLED The CICS data collector encountered a severe error in modname.

Explanation:

System Action: Strobe continues sampling, but the reports in the CICS Performance Supplement may be incomplete. User Response: STR4124E DISABLED Notify the Strobe system programmer.

modname DETECTED CORRUPTION OF STROBE FOR CICS CONTROL BLOCK - MODULE

Explanation: Control section modname detected a storage corruption problem within Strobemanaged storage. System Action: User Response: STR4125E Strobe continues sampling without the CICS data collector. Notify the Strobe system programmer.

modname DISABLED - INITIALIZATION INCOMPLETE

Explanation: Strobe module modname failed to properly initialize itself at the start of a Strobe measurement session. System Action: The services provided by modname will not be available during the measurement session. Strobe for CICS will continue collecting data, but the data will be incomplete. User Response: STR4126E Notify the Strobe system programmer.

DBCTL DATA COLLECTION DISABLED A severe error occurred in the CICS DBCTL data collector. Strobe continues sampling without the CICS DBCTL data collector.

Explanation: System Action:

User Response: Examine the log for previously issued messages to determine why the CICS DBCTL data collector failed.

Messages Produced by Strobe

3-79

STR4128I

DBCTL CONNECTION NOT ACTIVE; DBCTL DATA COLLECTOR QUIESCED

Explanation: An active CICS/DBCTL connection was not present when the Strobe measurement session began. System Action: Strobe continues sampling without the CICS DBCTL data collector. The Performance Profile will not contain any DBCTL-specific information. User Response: Ensure that the CICS/DBCTL connection is active before you begin a measurement request. If not, use the CICS transaction CDBC to activate it. Once the connection is active, resubmit the measurement request. STR4130E INVALID INPUT - modname

Explanation: A Strobe driver invoked the Strobe module modname with an invalid parameter. System Action: User Response: STR4131I Strobe continues sampling; Strobe for CICS is not disabled. Notify the Strobe system programmer.

modname - PLACED OUT OF SERVICE Strobe for CICS disabled Strobe module modname.

Explanation:

System Action: Strobe continues sampling, however Strobe for CICS attribution and module identification functions are disabled. User Response: Notify the Strobe system programmer.

STR4210W SAMPLING TERMINATED BEFORE LIMIT REACHED - CICS SUPPLEMENT WILL BE INCOMPLETE Explanation: The measurement session terminated before reaching the target sample size because the user directed it to do so. System Action: Strobe produces the Performance Profile, but the CICS Performance Supplement is incomplete. User Response: Resubmit the measurement request, specifying LIMIT=QUIT. Strobe terminates the request when it reaches the target number of samples. STR4211E GETMAIN FAILURE IN csectname - CICS STATISTICS NOT PRODUCED

Explanation: A GETMAIN failure occurred when the CICS data collector in the control section csectname was trying to obtain virtual storage for a work area. System Action: Strobe continues sampling but the CICS Performance Supplement reports are missing from the Performance Profile. User Response: STR4212E Notify the Strobe system programmer.

STROBE STARTED DURING CICS INITIALIZATION - CICS STATISTICS NOT PRODUCED Strobe started sampling while CICS was being initialized.

Explanation:

System Action: Strobe continues sampling, but the CICS Performance Supplement reports are missing from the Performance Profile. User Response: STR4213E Resubmit the job after CICS is initialized.

CICS TERMINATING WHILE SAMPLING - STATISTICS NOT PRODUCED CICS terminated while Strobe was sampling.

Explanation:

System Action: Strobe continues sampling, but the reports in the CICS Performance Supplement could be incomplete. User Response: None required.

STR4214E ABEND IN CPS DATA COLLECTOR - CICS PERFORMANCE SUPPLEMENT WILL BE INCOMPLETE Explanation: Strobe encountered an ABEND while gathering statistics for the CICS Performance Supplement. System Action: Strobe continues sampling, but the reports in the CICS Performance Supplement will be incomplete.

3-80

Strobe Messages Guide

User Response: STR4215W

Notify the Strobe system programmer.

TRANSACTION PROFILING NOT SUPPORTED FOR RELEASE x.x

Explanation: Strobe for CICS detected an unsupported release of CICS, xx. Strobe cannot collect the performance information for the Transaction Profile. System Action: Strobe continues processing, but does not collect performance information for the CICS Transaction Profile. User Response: Verify that the environment is CICS Transaction Server Version 1.3 or greater. STR4216W PROFILED TRANSACTION tran MAY BE A SYSTEM TRANSACTION, WHICH MAY NOT BE

Explanation: You requested detailed performance information for the transaction tran and used a wildcard (*). However, the name of the transaction you specified could conflict with the names of existing CICS system transactions. System Action: Strobe continues processing. If the transaction is a CICS transaction, Strobe will not supply detailed performance information for the transaction. User Response: IBM transactions begin with the letter C. To reduce potential conflicts with system transactions, user transactions starting with C should be fully qualified. Do not use a wildcard (*). STR4217E LOAD OF modname FAILED - TRANSACTION PROFILING DISABLED

Explanation: Strobe for CICS could not provide detailed performance information for transactions because it could not locate the module modname. System Action: Strobe continues sampling, but does not gather detailed performance information for CICS transactions. User Response: Notify the Strobe programmer.

STR4218E CICS TRANSACTION PROFILING DATASPACE dataspace-id FULL CONDITION AT SAMPLE sample Explanation: Dataspace dataspace-id, used to collect detailed performance information, failed because it encountered a full condition at sample. The dataspace identification numbers relate to these dataspaces:

Dataspace ID 01 02 03 04

Dataspace Service Time Dataspace Transaction Profile Dataspace Non-transaction Profile Dataspace Region Level Dataspace

System Action: Strobe continues processing, but cannot collect performance information for the CICS Transaction Profile. User Response: Increase the size of the dataspace with the CICS=DSSIZE parameter. See the Strobe for CICS manual for more information. STR4219E TRANSACTION PROFILING GETMAIN BUFFER FAILURE -- reason

Explanation: Strobe was unable to obtain the required buffer area to gather detailed performance information for CICS transactions. There is not enough available virtual storage to satisfy requirements for the Transaction Queue Scan Buffer or the Bridge Transaction Buffer because of reason. System Action: Strobe continues processing, but is unable to collect performance information for the CICS Transaction Profile. User Response: Specify a larger region size.

Messages Produced by Strobe

3-81

STR4220W

TRANSACTION tran IS A SYSTEM TRANSACTION AND CANNOT BE PROFILED

Explanation: The CICS transaction tran you specified when you submitted the measurement request is a CICS system transaction. System Action: Strobe continues processing, but does not gather detailed performance information for the transaction tran. User Response: Enter only user transactions, not CICS system transactions, into the transaction detail list. STR4221E CICS TRANSACTION PROFILING DISABLED

Explanation: Strobe cannot collect performance information for the Transaction Profile because it encountered a severe error. System Action: Strobe continues processing without collecting detailed performance information for the transaction. User Response: response. Review the error messages in the Strobe log and follow the recommended

STR4224E UNABLE TO PLACE CICS SERVICE TIME CAPTURE, RETURN CODE FROM STRBGMIM = rc Explanation: Strobe for CICS received a non-zero return code rc from STRBGMIM, indicating an error condition. System Action: Strobe continues processing, but cannot collect performance information for the CICS Transaction Profile. User Response: STR4225E Contact Compuware Customer Support.

CICS SERVICE TIME CAPTURE DISABLED The CICS service time capture experienced a severe error.

Explanation:

System Action: Strobe continues processing but cannot collect performance information for the Transaction Profile. The transactions counts and service times in the CICS Transaction Profile Report are inaccurate. User Response: STR4227E Notify the Strobe programmer.

modname INTERNAL ERROR-reason-code A Strobe for CICS module, modname, experienced a severe internal error.

Explanation:

System Action: Strobe continues processing, but cannot collect performance information for the Transaction Profile. Strobe produces CICS Transaction Profiling Reports, but the counts and service times are inaccurate. User Response: STR4228E Notify the Strobe system programmer.

CICS SERVICE TIME EXIT MODULE NOT FOUND

Explanation: Strobe for CICS was unable to locate the CICS service time exit module at the initiation of the Measurement Session. System Action: Strobe continues processing, but cannot collect performance information for the CICS Transaction Profile. User Response: STR4229E Contact Compuware Customer Support.

UNEXPECTED MODULE HEADER LENGTH ENCOUNTERED

Explanation: Strobe for CICS encountered an unexpected length in the module header for the CICS service time exit module. System Action: Strobe continues processing, but does not collect performance information for the Transaction Profile. User Response: Contact Compuware Customer Support.

3-82

Strobe Messages Guide

STR4230E

ERROR IN DATASPACE API FUNCTION function DATASPACE dataspace-id RC return code

Explanation: Strobe for CICS encountered an error when issuing a call for function function dataspace dataspace-id to the Strobe dataspace API. The dataspace-ids are:

Dataspace ID 01 02 03 04

Dataspace Service Time Dataspace Transaction Profile Dataspace Non-transaction Profile Dataspace Region Level Dataspace

System Action: Strobe continues processing, but cannot collect performance information for the CICS Transaction Profile. Strobe produces the CICS Transaction Profile reports, but the counts and service times are inaccurate. User Response: Notify the Strobe system programmer.

STR4231E CICS SERVICE TIME CAPTURE LOST DATA FOR nn.nn SECONDS. TRANSACTIONS NOT RECORDED = tran Explanation: Strobe did not record tran CICS transactions because the buffer size was not large enough. Strobe for CICS could not collect data for nn.nn seconds. System Action: Strobe continues processing, but the reported transaction counts and service times could be inaccurate. User Response: Specify a larger buffer with the CICS=CAPTBUFF parameter on the OTHERS panel, or increase the sampling rate to allow Strobe to empty the buffer more frequently. STR4232E ABEND THRESHOLD EXCEEDED - modname DISABLED Strobe for CICS encountered a severe error in module modname. Strobe continues sampling, but CICS-specific reports could be incomplete. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR4233E

CICS SERVICE TIME CAPTURE DISABLED DUE TO LOST DATA The Service Time buffer exceeded the limit of buffer full conditions.

Explanation:

System Action: Strobe continues sampling, but cannot collect performance information for the CICS Transaction Profile. The CICS Transaction Profiling reports could be incomplete. User Response: Specify a larger buffer through the CICS=CAPTBUFF parameter or increase the sampling rate to allow Strobe to empty the buffer more frequently. STR4234E number CICS TRANSACTION PROFILING DISABLED DURING MEASUREMENT AT SAMPLE Strobe for CICS was disabled during the measurement of sample number.

Explanation:

System Action: Strobe continues processing without collecting performance information for the CICS Transaction Profile. Other Strobe reports are complete. User Response: View the Strobe log error messages and follow the recommended response.

STR4235W TRANSACTION PROFILE NOT AVAILABLE-DEFAULT TO CICS PERFORMANCE SUPPLEMENT Explanation: Strobe for CICS could not locate module STRBTXP and, therefore, could not complete the Transaction Profile request. System Action: statistics. User Response: Support. Strobe continues sampling, but only collects CICS Performance Supplement Verify the installation of Strobe for CICS and contact Compuware Customer

Messages Produced by Strobe

3-83

STR4310E

GETMAIN FAILURE - IMS DATA COLLECTOR DISABLED

Explanation: A GETMAIN failure occurred when the IMS data collector was trying to obtain virtual storage for its work area. System Action: User Response: STR4320E Strobe continues sampling without the IMS data collector. Notify the Strobe system programmer.

IMS RELEASE OR REGION TYPE NOT SUPPORTED - DATA COLLECTOR DISABLED

Explanation: Strobe does not support the type of IMS region in which the target job is running. Strobe supports Message Processing Regions (MPRs), IMS Fast Path regions (IFPs), Batch Message Processing regions (BMPs), Data Language/One batch applications (DL/I), control regions (CTL), and DL/I Separate Address Spaces (DLISAS). System Action: User Response: STR4410E Strobe continues sampling without the IMS data collector. Notify the Strobe system programmer.

GETMAIN FAILURE - DB2 DATA COLLECTOR DISABLED

Explanation: A GETMAIN failure occurred when the DB2 data collector was trying to obtain virtual storage for its work area. System Action: User Response: STR4220W Strobe continues sampling without the DB2 data collector. Notify the Strobe system programmer.

TRANSACTION tran IS A SYSTEM TRANSACTION AND CANNOT BE PROFILED

Explanation: The CICS transactions tran you specified to collect detailed performance information for is a CICS system transaction. System Action: Strobe continues processing, but does not gather detailed performance information for the transaction tran. User Response: Enter only user transactions, not CICS system transactions, into the transaction detail list. STR4501E GETMAIN FAILURE IDMS DATA COLLECTOR program name DISABLED The Strobe CA-IDMS data collector was unable to obtain virtual storage for its Strobe continues sampling without the CA-IDMS data collector. Increase the region size and resubmit the request. Notify the Strobe system

Explanation: work area. System Action: User Response: programmer. STR4502E

IDMS CV NUCLEUS REFRESHED - DATA COLLECTION DISABLED

Explanation: The CA-IDMS nucleus was refreshed while the measurement task was sampling. System Action: Strobe continues sampling without the CA-IDMS data collector. The CAIDMS and ADS/O Attribution reports in the Performance Profile will be incomplete. User Response: completed. STR4503E Rerun the measurement session after the CA-IDMS nucleus refresh is

IDMS DATA COLLECTION MODULE - STRBmodname - NOT IN STROBE LIBRARY

Explanation: The CA-IDMS data collector or DML batch attributor attempted to load the release-specific data collection module STRBmodname, but did not find the module. System Action: Strobe continues sampling without CA-IDMS data collection or DML batch attribution data. User Response: STR4601E Notify the Strobe system programmer.

GETMAIN FAILURE - CICS/DBCTL SUPPLEMENT DISABLED

Explanation: A GETMAIN failure occurred when the CICS/DBCTL data collector attempted to obtain virtual storage for a work area. System Action: Strobe continues sampling without CICS/DBCTL attribution data.

3-84

Strobe Messages Guide

User Response: programmer. STR4602E

Increase the region size and resubmit the request. Notify the Strobe system

CICS/DBCTL RELEASE NOT SUPPORTED

Explanation: Strobe attempted to measure a CICS/DBCTL region running an unsupported release of either IMS or CICS. System Action: User Response: STR4701E Strobe continues sampling without CICS/DBCTL attribution data. Notify the Strobe system programmer.

ADABAS RELEASE NOT SUPPORTED

Explanation: Strobe attempted to measure an Adabas region that was running a release of Adabas that Strobe does not support. System Action: User Response: STR4800E Strobe continues sampling but does not collect Adabas data. Notify the Strobe system programmer.

MQSERIES DATA COLLECTION DISABLED - reason

Explanation: Strobe disabled Strobe for WebSphere MQ processing because of reason. The following are possible causes:

Invalid input to routine STRBDCSQ Invalid input to subroutine subroutine Abend threshold exceeded Unable to access the required MVS data Invalid input to STRBCSQC Invalid input to STRBCSQT Abend threshold exceeded STRBSCQC Abend threshold exceeded STRBCSQT Invalid ALET returned by #PC service Internal diagnostic data for reason is given in code.
Strobe continues sampling without collecting MQSeries data. Contact Compuware Customer Support.

System Action: User Response: STR4801I

MQSeries data collection disabled: reason

Explanation: The Measurement Facility disabled Strobe for WebSphere MQ processing because of reason. The possible reasons are:

threshold for undefinable queue managers exceeded release xyz of MQSeries is not supported <QM=qqqq> measurement is of a queue manager address space could not obtain working storage no queue managers defined to MVS task in sample is not connected to a queue manager program check in intercept module abend detected in intercept module.
Strobe continues sampling without collecting more MQSeries data.

System Action:

User Response: Notify the Strobe system programmer. If the task was not connected to a queue manager, initiate a connection to the appropriate queue manager <qqqq> for the task. STR4802E MQSERIES ATTRIBUTION DISABLED-reason

Explanation: Strobe disabled Strobe for WebSphere MQ processing because of reason. The following are possible causes:

Invalid input to routine STRBACSQ or The abend threshold was exceeded


System Action: modules. User Response: Strobe continues sampling, but does not attribute some activity in MQSeries Notify the Strobe system programmer.

Messages Produced by Strobe

3-85

STR4803I

MQSERIES ATTRIBUTION DISABLED -- COULD NOT OBTAIN WORKING STORAGE

Explanation: The Measurement Facility disabled the MQSeries attributor because Strobe for WebSphere MQ could not obtain storage for an internal work area. System Action: User Response: STR4804I None. Notify the Strobe system programmer.

ATTRIBUTION OF USERS COMMON MQSERIES USER MODULE IS DISABLED-reason

Explanation: Strobe for WebSphere MQ does not identify the caller of the users common MQSeries user module because of reason. The following are possible causes:

The common user module is the module being measured The threshold for the number of failed attempts to identify the invoker has been reached
System Action: Strobe continues processing. Strobe for WebSphere MQ collects other data, but does not identify the invokers of the MQSeries common user module. User Response: Notify the Strobe system programmer. To identify the invoker of the common user module issuing the MQSeries APIs, separate the common user module from the one being measured. If the number of failed identifications of the common user module exceeds the threshold during the measurement, ensure that you are using the standard MVS linkage conventions for the common user module and the module that invoked it. If you are measuring a CICS region, ensure that you are using CICS calling conventions. STR4805I MQSERIES MQI COUNTS DISABLED [text]

Explanation: MQICAPTURE has been disabled because of an error in processing explained in text:

Intercept module not linked Intercept module invalid CICS environment not active CICS stub not found Implant failure Storage obtain failure
Further capture is terminated but existing data will be reported. Notify the Strobe system programmer.

System Action: User Response: STR4805I

MQSERIES TRANSACTION PROFILING DATA SPACE FULL AT SAMPLE NUMBER-number

Explanation: The Strobe MQSeries Transaction Profiling Dataspace encountered a full condition for the sample number number. System Action: Strobe continues processing, but does not create queue tokens to be used by the CICS Transaction Profile Function. User Response: STR4806I Increase the data space size by increasing the CICS=DISSIZE parameter.

MQSERIES FOR TRANSACTION PROFILING DISABLED BY strbcsqt The MQSeries component, strbcsqt, encountered a severe error.

Explanation:

System Action: Strobe continues processing, however, the MQSeries data will not appear in CICS Transaction Profile reports. User Response: STR4807E Notify the Strobe system programmer.

LOAD OF CICS TASK TABLE modname FAILED - CICS DATA COLLECTOR DISABLED

Explanation: Strobe for CICS was unable to load the table of CICS system transactions. The CICS data collector is disabled. System Action: User Response: library. Strobe continues processing, but does not collect CICS data. Verify that the CICS System Task Table STRBTSK is in the appropriate load

3-86

Strobe Messages Guide

STR4808I

MQ implant successful at sample #nnnnnnnn

Explanation: Strobe detected MQ activity at sample #nnnnnnnn and successfully implanted its MQ intercept.

The sample # at which the MQ implant was made is typically low for online systems such as CICS or IMS because MQ will already be active in these regions. The implant sample # for batch MQ is typically higher depending on the amount of work performed by your batch procedure before MQ activity is initiated and MQ modules are loaded into virtual storage. Strobe wont implant its intercept until MQ activity is detected.
System Action: Strobe continues processing and MQ data collection is initiated. User Response: The MQ API calls are typically very fast, so it is possible for an MQ call to be initiated and completed between Strobe samples. If that is the case, Strobe will not see this activity and you will not see this message. Try increasing your sampling rate so that Strobe has a chance to sample the MQ activity.

If your reports appear to be missing a significant amount of MQ data and the sample # at which data collection started was high, this may be an indication of something wrong in your environment. Check your Strobe report for other performance related issues. Otherwise, no response is required.
STR4901E JVM DATA COLL STRBJDC1 DISABLED BECAUSE [text]

Explanation: The data collector STRBJDC1 encountered a situation preventing it from continuing to process samples. It disables itself, and measurement continues without further JVM measurement. One of the following messages appears in text:

MODULE COULD NOT OBTAIN WORKING STORAGE - STRBJDC1 attempted to obtain working storage for itself or for the JVM Global Workarea, but the Storage Obtain function failed. TOO MANY TOKEN COMPRESSION ERRORS - STRBJDC1 encountered an excessive number of errors when tokenizing Java names.
System Action: STRBJDC1 stops processing the sample and disables itself. Measurement may continue, but no further JVM sample processing takes place. User Response: For a message concerning storage, contact your Strobe system programmer. For a message concerning the JVM release, ensure that the version of JVM you are trying to measure is supported by the version of Strobe in use. For a message concerning token compression errors, contact Compuware Customer Support. STR4902W SAMPLE IGNORED BY STRBJDC1 BECAUSE [text]

Explanation: The data collector STRBJDC1 cannot successfully process the current sample. It issues a warning message and exits. One of the following messages appears in text:

DCICALL2 WAS OUTSIDE RANGE - STRBJDC1 was called with an argument value outside the permissible range of values. The JVM processing portion ends for that sample, but measurement continues. DCICALL2 WAS ZERO - STRBJDC1 was called with an argument value of zero. The JVM processing portion of that sample by STRBJDC1 ends, but measurement continues. LONGNAME TOKEN COMPRESSION ERROR - The longname token subroutine called by STRBJDC1 exited with a return code greater than 4. STRBJDC1 stops processing that particular sample, but measurement continues. LONGNAME EXCEEDED BUFFER SIZE - The longname handled by STRBJDC1 exceeded the permissible length. STRBJDC1 stops processing the sample, but measurement continues.
System Action: STRBJDC1 ceases processing the current sample, but sample processing continues. STRBJDC1 continues processing with the next sample.

Messages Produced by Strobe

3-87

User Response: For a message concerning buffer size, ensure that the names which are in use are within the length of name supported by the version of Strobe in use. For all other messages, contact Compuware Customer Support. STR4911E JVM DATA COLL STRBJDC2 DISABLED BECAUSE [text]

Explanation: The data collector STRBJDC2 encountered a situation preventing it from continuing. It disables itself and measurement continues without further JVM measurement. One of the following messages appears in text:

LOCAL WORKAREA MISSING AFTER INIT - STRBJDC2 found that its workarea was no longer available. LOCAL WORKAREA FAILED EYECATCHER - STRBJDC2 found that the working storage eyecatcher was no longer present. GLOBAL COMM AREA MISSING AFTER INIT - STRBJDC2 found that the GLOBAL COMM AREA was no longer available. GLOBAL COMM AREA FAILED EYECATCHER - STRBJDC2 found that the GLOBAL COMM AREA eyecatcher was no longer present. SAMPLE ROUTINE FOUND BAD WORKAREA - STRBJDC2 found that a workarea eyecatcher was no longer present. IDENTIFY ROUTINE FOUND BAD WORKAREA - STRBJDC2 found that a workarea eyecatcher was no longer present. MODULE DID NOT OBTAIN WORKING STORAGE - STRBJDC2 attempted to obtain working storage for itself, but the Storage Obtain function returned an error code. MODULE COULD NOT OBTAIN GLOBAL STORAGE - STRBJDC2 attempted to obtain working storage for the JVM Global Workarea, but the Storage Obtain function returned an error code.
System Action: STRBJDC2 stops processing the sample and disables itself. Measurement may continue, but no further JVM sample processing takes place. User Response: STR4912W Contact Compuware Customer Support.

SAMPLE IGNORED BY STRBJDC2 BECAUSE [text]

Explanation: The data collector STRBJDC2 cannot successfully process the current sample. It issues a warning message and exits. One of the following messages appears in text:

DCICALL2 WAS OUTSIDE RANGE - STRBJDC2 was called with an argument value outside the permissible range of values. The JVM processing portion ends for that sample, but measurement continues. DCICALL2 WAS ZERO - STRBJDC2 was called with an argument value of zero. The JVM processing portion of that sample by STRBJDC2 ends, but measurement continues. SAMPLE CALL NOT A DIRECTED CALL - STRBJDC2 was called during sample time, but the call was not a directed call. STRBJDC2 stops processing that particular sample, but measurement continues. CALLER NOT IN CALLER TABLE - STRBJDC2 was not activated by a legal caller. STRBJDC2 stops processing the sample, but measurement continues.
System Action: STRBJDC2 ceases processing the current sample, but sample processing continues. STRBJDC2 continues processing with the next sample. User Response: STR4921E Contact Compuware Customer Support.

JVM ATTRIBUTOR STRBJVMA DISABLED BECAUSE [text]

Explanation: A failure occurred in the Strobe for Java Attributor. The explanation appears in text:

AN ABEND HAS OCCURRED - The Strobe for Java Attributor is disabled because an ABEND occurred.

3-88

Strobe Messages Guide

JVM RELEASE NOT SUPPORTED - The release level of the Java Virtual Machine is not supported by Strobe . MODULE COULD NOT OBTAIN WORKING STORAGE - The Strobe for Java Attributor was unable to obtain storage for its work area. MODULE COULD NOT OBTAIN GLOBAL WORK AREA - The Strobe for Java Attributor was unable to obtain storage for use by the modules that comprise Strobe for Java.
System Action: incomplete. User Response: Strobe continues sampling, but the Strobe Performance Profile will be Notify the Strobe system programmer.

STR4922W JVM ATTRIBUTOR STRBJVMA ERROR PROCESSING TARGET DATA. ATTRIBUTION CONTINUES, BUT WILL LOCATE THE MAIN METHOD. Explanation: A failure occurred in the Strobe for Java Attributor when processing Java targeting information. System Action: Strobe continues sampling, but the JAVA CPU USAGE BY CALLED METHOD and JAVA WAIT TIME BY CALLED METHOD reports in the Strobe Performance Profile will not reflect the requested targets. User Response: Notify the Strobe system programmer.

STR4923W JAVA METHOD IGNORED BY JVM ATTRIBUTOR STRBJVMA BECAUSE LONGNAME EXCEEDED BUFFER SIZE. Explanation: Strobe for Java detected one or more qualified method names (package plus signature) that exceeded the internal buffer size of 1024 bytes reserved for such names. System Action: Strobe stops processing the sample in which it detected the longname.

User Response: Reduce the size of qualified method names to less than 1024 bytes and resubmit the request. STR4924E JMETHODID DATASPACE ALLOCATION FAILED - RC xxxxxxxx

Explanation: Strobe for Java attempted to allocate its dataspace and was unable to do so. xxxxxxxx represents an eight byte decimal return code from the Strobe Dataspace Management routine. System Action: The Strobe for Java routine disables itself from further processing. Measurement session continues. User Response: Strobe log. STR4925W Contact Compuware Customer Support and provide sample dataset and

JV5D JMETHODID xxxxxxxxxxxxxxxx NOT FOUND AT SAMPLE # yyyyyyyy

Explanation: Strobe for Java could not find the sixteen byte method ID passed by the Strobe Java Agent in its dataspace. yyyyyyyy represents an eight byte decimal sample number in which this event occurred. System Action: User Response: Strobe log. STR4926I Measurement session continues. Contact Compuware Customer Support and provide sample dataset and

JV5D RECEIVED JMETHODID xxxxxxxxxxxxxxxx AT SAMPLE # yyyyyyyy

Explanation: xxxxxxxxxxxxxxxx represents a sixteen byte method ID received from the Strobe Java Agent. yyyyyyyy represents an eight byte decimal sample number in which this event occurred. System Action: User Response: STR4927I Measurement session continues. None.

JV5D ZERO METHODS RETURNED AT SAMPLE # xxxxxxxx

Explanation: xxxxxxxx represents an eight byte decimal sample number in which the zero method event occurred.

Messages Produced by Strobe

3-89

System Action: User Response: STR4928W zzzzzzzz

Measurement session continues. None.

JV5D JMETHODID xxxxxxxxxxxxxxxx DSPACE PUT ERROR - RC yyyyyyyy, SAMPLE #

Explanation: Strobe for Java was unable to write a sixteen byte method ID to its dataspace. yyyyyyy represents an eight byte decimal return code from the Strobe Dataspace Management routine. zzzzzzzz represents an eight byte sample number in which this event occurred. System Action: User Response: Strobe log. STR4929E Measurement session continues. Contact Compuware Customer Support and provide sample dataset and

JV5D POSTED BY TIMER EXIT AT SAMPLE # xxxxxxxx

Explanation: Strobe for Java was awakened by its timer exit routine, which indicates a possible problem with the Strobe Java Agent. xxxxxxxx represents an eight byte decimal sample number in which this event occurred. System Action: The Strobe for Java routine disables itself from further processing. Measurement session continues. User Response: Strobe log. Contact Compuware Customer Support and provide sample dataset and

STR4930W STROBE FOR JAVA ENCOUNTERED JAVA METHOD NAMES GREATER THAN 1024 BYTES nnnnnn TIMES DURING SAMPLING Explanation: nnnnnn is the number of times that Strobe for Java encountered a method name greater than 1k during sampling. System Action: User Response: STR4931E Strobe for Java will not include those samples in any of its reports. None required.

JV5D ENCOUNTERED THE FOLLOWING ERROR: xxxxxxxxxxxxxxxxxxxx

Explanation: Strobe for Java encountered one of the following three possible situations during its IDENTIFY phase:

1 - No CAA address - Strobe was unable to obtain the address of the Language Environment CAA. 2 - Bad LE control blk - Strobe was unable to validate key Language Environment control blocks. 3 - Bad env variable - An error occurred while processing environment variables.
System Action: Strobe for Java was unable to construct necessary records for Java Environment Report. Measurement session continues. User Response: Contact Compuware Customer Support and provide sample dataset and Strobe log dataset. STR5001W WAS OPTION LICENSED BUT WAS=N0 SPECIFIED IN PARMLIB - WAS DATA COLLECTION DISABLED Explanation: You are measuring a WebSphere region, and your site is licensed for Strobe for WebSphere Application Server, but WebSphere data collection was not activated for your measurement request. System Action: Strobe for WebSphere Application Server data will not be present in your Performance Profile reports. User Response: None required. If you want to see WebSphere activity, either contact your Strobe system programmer to set the global option on, or specify WAS=Y on the Strobe data collectors panel. STR5002E EXCEEDED WEBSPHERE DATA COLLECTOR DISABLED - MAX CONCURRENT WAS MEASUREMENTS

Explanation: The limit for concurrent executions of Strobe for WebSphere Application Server measurements has already been met. (The limit is set in the WASCNTS parameter).

3-90

Strobe Messages Guide

System Action: Measurement continues, but Strobe for WebSphere Application Serve reporting will not be present in your measurement reports. User Response: Submit your measurement later, or contact the Strobe system programmer to increase the value in the WASCNTS parameter. STR5003E nnnnnn DATASPACE ERROR - xxxxx COMMAND - RETURN CODE rc This error reflects one of the following situations:

Explanation:

nnnnnn is the dataspace name, which can be WAS LOCAL or WAS SCOPE=ALL. xxxxx can be GET, CREATE, or DELETE. rc is a 2-digit error code.
System Action: If the command was DELETE, your reports will not be affected, but you should report the error message to your system programmer. If the command was CREATE, your Performance Profile will not include any Strobe for WebSphere Application Server reports. If the command was GET, your Strobe for WebSphere Application Server reports will be incomplete. Explanation: STR5004E Contact the Strobe system programmer.

WAS DATA COLLECTOR INTERNAL ERROR xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation: This is an internal error. One of several possible self-explanatory and detailed error statements will appear in the message. System Action: Strobe for WebSphere Application Server is not able to continue for this measurement. The Strobe for WebSphere Application Server reports will be incomplete, but the measurement will continue for other components in the measured address space. User Response: Notify Strobe support.

STR5006E WAS DATA COLLECTOR DISABLED BECAUSE DATASPACE PC ROUTINE IS UNAVAILABLE Explanation: Internal error.

System Action: Strobe for WebSphere Application Server is unable to execute in this measurement, but the measurement will continue for other components. User Response: STR5008E Notify Compuware Customer Support.

WAS DATA COLLECTION DISABLED -- STRBBB0S UNABLE TO OBTAIN WORKAREA

Explanation: The Strobe for WebSphere Application Server data collector was unable to obtain memory in the measured address space. System Action: Strobe for WebSphere Application Server is not able to execute in this measurement, but measurement will continue for other components. User Response: Increase the region size for the measured address space and re-run.

STR5009E WAS DATA COLLECTION DISABLED -- ABEND IN LOGIC THAT INITS SCOPE=ALL DATASPACE Explanation: Internal error.

System Action: Strobe for WebSphere Application Server is unable to execute in this measurement, but measurement will continue for other components. User Response: Notify Compuware Customer Support.

STR5010E WAS DATA COLLECTION DISABLED -- UNABLE TO ENQUEUE ON QNAME qname RNAME rname Explanation: The Strobe for WebSphere Application Server data collector is unable to get control of the enqueued-upon resource where:

qname - the characters STRB followed by the Strobe release number rname - the Strobe version character followed by the characters WASDS1
System Action: Strobe for WebSphere Application Server will not include those samples in any of its reports. User Response: Try again later.

Messages Produced by Strobe

3-91

STR5011E

WAS DATA COLLECTION DISABLED -- ENQ ON qname XXXX rname XXXX FAILED RC XX

Explanation: The Strobe for WebSphere Application Server data collector is unable to get control of the enqueued-upon resource where:

qname - the characters STRB followed by the Strobe release number rname - the Strobe version character followed by the characters WASDS1
System Action: Strobe for WebSphere Application Server is not able to execute in this measurement, but the measurement will continue for other components. User Response: STR5012E Try again later.

WAS DATA COLLECTION DISABLED -- DEQ ON qname XXXX rname XXXX FAILED RC XX

Explanation: The Strobe for WebSphere Application Server data collector is not able to get control of the enqueued-upon resource where:

qname - the characters STRB followed by the Strobe release number rname - the Strobe version character followed by the characters WASDS1
System Action: Strobe for WebSphere Application Server is not able to execute in this measurement, but measurement will continue for other components. User Response: STR5013E None required.

WAS DATA COLLECTION DISABLED -- STRBWENV UNABLE TO OBTAIN WORKAREA The data collector was not able to obtain memory in the measured address

Explanation: space.

System Action: Strobe for WebSphere Application Server is not able to execute in this measurement, but the measurement will continue for other components. User Response: STR5014E Increase the region size for the measured address space and re-run.

WAS DATA COLLECTION DISABLED -- STRBWDRN UNABLE TO OBTAIN WORKAREA The data collector was not able to obtain memory in the measured address

Explanation: space.

System Action: Strobe for WebSphere Application Server is not able to execute in this measurement, but the measurement will continue for other components. User Response: STR5015E Increase the region size for the measured address space and re-run.

WAS DATA COLLECTION DISABLED -- STRBWWRT UNABLE TO OBTAIN WORKAREA The data collector was not able to obtain memory in the measured address

Explanation: space.

System Action: Strobe for WebSphere Application Server is not able to execute in this measurement, but the measurement will continue for other components. User Response: STR5016E Increase the region size for the measured address space and re-run.

WAS DATA COLLECTION DISABLED -- THE WAS OPTION IN MSAS IS NOT ACTIVE

Explanation: During initialization for this measurement, it was determined that the WAS option in the MSAS was not currently operational. This could be caused as the result of a prior abend in the Strobe for WebSphere Application Server SMF exit or as the result of a MODIFY command to STOPWAS. System Action: Strobe for WebSphere Application Server is not able to execute in this measurement, but the measurement will continue for other components. User Response: programmer. STR5050E Try again later. If the problem persists, notify your sites Strobe system

WEBSPHERE APPLICATION SERVER RELEASE { XXXX | UNSUPPORTED | UNKNOWN } The WebSphere release is not supported or cannot be determined:

Explanation:

nnnn UNSUPPORTED -- Strobe does not support version nnnn of WebSphere 0000 UNKNOWN -- Strobe could not determine the version of WebSphere.

3-92

Strobe Messages Guide

System Action: Strobe for WebSphere Application Serve is unable to execute in this measurement, but measurement will continue for other components. Note that if your LPAR is running very slowly, it can take longer for the release to be formatted within a WebSphere server address space than it can take for the data collector to be active and querying for the release information. User Response: If the release is unsupported, notify your Strobe system programmer. If the release is unknown, try your measurement again later. STR5051W WEBSPHERE APPLICATION SERVER RELEASE nnnnnnnnnnn IS UNSUPPORTED. PROCESSING WILL CONTINUE. Explanation: System Action: data. The WebSphere release is not supported. Strobe for WebSphere Application Server continues to collect measurement

User Response: Contact your Strobe system programmer to determine which versions of WebSphere Strobe supports.

Messages Returned in Response to Sampling Control Commands


The Strobe measurement task returns the following messages in response to sampling control commands sent to the Strobe measurement task via the Strobe SEND operation.
STR5300I STROBE SESSION ENDED AT time ON date FOR JOB jobname, REQUEST nnnn

Explanation: A Strobe measurement session ended at time time on date date, jobname jobname, and request number nnnn. Strobe issues this message when the NOTIFY parameter was specified on the ADD operation. System Action: User Response: STR5301I Strobe has completed sampling. None required.

STROBE RUNNING [- SsssDddd HAS ttttt/eeeee SAMPLES]

Explanation: Strobe received a START or STATUS command. The sample dataset whose loworder name syllable is SsssDddd contains ttttt total samples and eeeee execution samples. If the sample count message does not appear, Strobe opened a new sample dataset but did not collected any samples. System Action: dataset. User Response: STR5302I Strobe starts or continues sampling, placing the samples into the sample None required.

STROBE RUNNING AND SWITCHED - SsssDddd HAS ttttt/eeeee SAMPLES

Explanation: Strobe received a SWITCH command. The sample dataset whose low-order name syllable is SsssDddd contains ttttt total samples and eeeee execution samples and is closed and ready for reporting. System Action: Strobe continues sampling, now using a sample dataset whose low-order syllable is SsssDddd+1. User Response: STR5303I OPEN} None required.

STROBE SUSPENDED {- SsssDddd HAS ttttt/eeeee SAMPLES|- NO SAMPLE DATA SET

Explanation: Strobe received a STATUS command. If a sample dataset is open, its low-order syllable name is SsssDddd, it contains ttttt total samples and eeeee execution samples. It is not available for reporting. Otherwise, no sample dataset is open. System Action: User Response: Strobe is not sampling. None required.

Messages Produced by Strobe

3-93

STR5304I

STROBE SUSPENDED - NO SAMPLE DATA SET OPEN

Explanation: Strobe received a STOP command while in the suspended state with an open sample dataset. The sample dataset is closed and is available for reporting. System Action: Strobe takes no action and sampling remains suspended. No sample dataset is open. User Response: STR5305I None required.

STROBE TERMINATING

Explanation: Strobe received a QUIT command. If Strobe is sampling, the current sample dataset is closed and is available for reporting. System Action: Strobe stops sampling and cannot be restarted with a SEND operation.

User Response: To initiate further sampling, submit a new Strobe request statement, using the ADD operation. STR5310I STROBE MEASUREMENT SESSION SUSPENDING Strobe received a SUSPEND or STOP command. Strobe stops sampling. None required.

Explanation: System Action: User Response: STR5315W

STROBE NOT SAMPLING - REQUEST IGNORED

Explanation: Strobe received a SWITCH, STOP, or SUSPEND command. Strobe is not sampling and has no open dataset. System Action: User Response: STR5318W Strobe does not process the command. To resume sampling, enter a START command.

STROBE SAMPLING - REQUEST IGNORED Strobe received a START command, but sampling is already in process. Strobe does not process the command. None required.

Explanation: System Action: User Response: STR5320I

STROBE MEASUREMENT SESSION RESUMED Strobe received and processed a START command. Strobe begins sampling. None required.

Explanation: System Action: User Response:

Messages Returned by the Session Management Facility


The session management facility returns the following messages in response to Strobe commands, writing them to the SYSPRINT dataset and to an operators terminal when the request originated there. Strobe/ISPF users receive messages at the terminal and can also access them from the log dataset where the session management facility records them. Messages other than those produced in response to status commands are also written to the Strobe log.
STR6001I STROBE SESSION MANAGER release CALLED FROM {job | started_task} jobname AT time, SYSTEM=sysname Explanation: You initiated execution of the session manager for Strobe release release, from either a batch job or a started task, under a job named jobname, at time time. The MVS system name of the host is sysname. System Action: User Response: Strobe continues processing. None required.

3-94

Strobe Messages Guide

STR6005I STROBE SESSION MANAGER release COMPLETED FOR {job|started task} jobname RC=rc SYSTEM=sysname Explanation: You initiated execution of the session manager for Strobe release release, on system sysname from a batch job or a started task under a job named jobname.

A zero return code (RC=00) indicates that all operations requested were processed successfully. A nonzero return code indicates that Strobe detected an error when processing at least one operation. The error was reported in an earlier message. Refer to Return Codes and Severity Codes on page 1-2 for an explanation of the return codes and their associated severity codes. The MVS system name of the host computer is sysname.
System Action: Strobe completed execution for the job.

User Response: If the return code is not zero, locate the message reporting the error, and follow the recommended action in the message description. STR6006E commandname OPERATION FOR REQUEST nnnn ENDED WITH ERROR

Explanation: The processing of command commandname for request number nnnn ended with an error condition. System Action: Strobe may not have processed the command, as indicated by the error messages that preceded this message. User Response: programmer. STR6007I Check the log for additional messages and notify the Strobe system

DESIGNATED INTERNAL STRUCTURE structname INVALID

Explanation: Strobe attempted to free an unallocated or a negative amount of storage in structure structname. System Action: User Response: Strobe does not attempt to free the storage. None required.

STR6101I STROBE release CALLED FROM {batch job | TSO session | started_task} jobname AT time date SYSTEM=sysname Explanation: Execution of Strobe at version release was initiated from either a batch job, a TSO session, or a started task, under a job named jobname, at time time, on date date. The MVS system name of the host is sysname. System Action: User Response: STR6102S Strobe is ready to process Strobe control statements. None required.

INVALID OPERATING SYSTEM OR OPERATING SYSTEM LEVEL

Explanation: Strobe does not support the operating system or operating system release level. System Action: Strobe terminates.

User Response: Ensure that the specific Strobe option supports your operating system configuration. Notify the Strobe system programmer. STR6103S INSTALLATION ERROR - STROBE NOT MARKED REENTRANT

Explanation: Either the load module for the session manager, STRBCSM, is not marked as reentrant, or the load module for the session requester, STRBCSR, is not marked as reentrant. System Action: Strobe terminates.

User Response: Notify the Strobe system programmer. There has probably been an installation error. The Strobe system programmer should check the linkage editor output listing from the Strobe installation job to verify that the load module has been marked as reentrant. If not, reinstall the Strobe modules with link edit options RENT, REUS, and REFR. STR6104E REQUEST REJECTED - SESSION MANAGER IS NOT ACTIVE ON SYSTEM sysname

Explanation: This message is issued in response to a Strobe request issued on system sysname. A component of Strobe, the session manager, is either not active or has failed on system sysname. To use Strobe, the session manager must be active.

Messages Produced by Strobe

3-95

System Action: User Response: programmer.

Strobe does not process the request. To use Strobe, you must start the session manager. Notify the Strobe system

STR6105I STROBE release COMPLETED FOR {JOB|TSO USER|STRT TSK} jobname RC=rc SYSTEM=sysname Explanation: Execution of Strobe release release was initiated from a batch job, a TSO session, or a started task under a job named jobname. A zero return code (RC=00) indicates that all operations requested have been processed successfully. A nonzero return code indicates that Strobe detected an error when processing at least one operation. The error was reported in an earlier message. Refer to Return Codes and Severity Codes on page 1-2 for an explanation of the return code and the associated severity code. The MVS system name of the host computer is sysname. System Action: Strobe completed processing the job.

User Response: If the return code is not zero, locate the message reporting the error, and follow the action recommended in the message description. STR6106E MAXIMUM NUMBER OF REQUESTS EXCEEDED - REQUEST IGNORED

Explanation: The number of requests submitted to Strobe exceeds the number specified by your Strobe system programmer during the installation of the Strobe system. System Action: Strobe accepts no further requests.

User Response: Notify the Strobe system programmer who can delete the completed requests with a DELETE or CLEAN command. STR6107W NUMBER OF REQUESTS IS APPROACHING LIMIT - DELETE COMPLETED REQUESTS

Explanation: The number of requests accepted by Strobe exceeds 75% of the number specified by your Strobe system programmer during the installation of the Strobe system. System Action: Strobe accepts and processes the current request.

User Response: Notify the Strobe system programmer who can delete the completed requests or outdated AutoStrobe requests with a DELETE or CLEAN command. STR6108I PARMS=xxxxxxxx

Explanation: This message xxxxxxxx echoes the PARMS field received in a START command or EXEC statement used to invoke Strobe. System Action: User Response: STR6109S Strobe continues processing. None required.

STROBE NOT CALLED FROM AUTHORIZED LIBRARY The module STRBCSM was called from an unauthorized library. This can be

Explanation: caused by:

An unauthorized library in the STEPLIB concatenation Executing Strobe in an unauthorized dataset


System Action: The session manager cannot create the Strobe environment.

User Response: If Strobe is accessed via STEPLIB, either remove any unauthorized partitioned datasets from the STEPLIB concatenation or move the Strobe library to an authorized library or link list dataset. Contact the Strobe system programmer to determine if Strobe is in a link list. STR6110S STROBE NOT CALLED AS AUTHORIZED PROGRAM The module STRBCSM was not invoked as an authorized program. This can be

Explanation: caused by:

An unauthorized library in the STEPLIB concatenation Installing Strobe as an unauthorized program


System Action: The session manager cannot create the Strobe environment.

User Response: If Strobe is accessed via STEPLIB, either remove any unauthorized partitioned datasets from the STEPLIB concatenation or move the Strobe library to an authorized library or

3-96

Strobe Messages Guide

link list dataset. Contact the Strobe system programmer to determine if Strobe is in the link list and was installed properly. STR6111S STROBE SESSION MANAGER ALREADY ACTIVE The session manager is already active.

Explanation:

System Action: The duplicate version of Strobe will terminate and processing of the original version will continue unaffected. User Response: STR6112E None required.

CANNOT PERFORM ENVIRONMENT CHANGE - STROBE IN USE BY OTHER JOBS

Explanation: You cannot change the Strobe environment until other active executions of Strobe have terminated. System Action: Strobe continues processing.

User Response: To determine who are the active Strobe users, invoke the STATUS command. Wait until all other executions of Strobe terminate and resubmit the environment request. STR6113E REQUEST REJECTED [ON SYSTEM sysname -] INSUFFICIENT ACCESS AUTHORITY

Explanation: You submitted a request to either measure a job or to access an existing request. If identified, the system is sysname.

The Strobe security interface (access filter) determined that you do not have access to the job specified in the request.
System Action: The request is rejected and processing continues.

User Response: To enable you to measure this job, the Strobe system programmer or security administrator must grant you access to the job. STR6114I ACCESS FILTER DISABLED ON SYSTEM sysname BY INSTALLATION REQUEST

Explanation: During startup of the session manager on system sysname, Strobe determined that the access filter is disabled. The Strobe parameter disabled the access filter. System Action: User Response: STR6115I Strobe continues processing but the security interface is disabled. None required.

NO SECURITY SYSTEM FOUND ON SYSTEM sysname - ACCESS FILTER DISABLED

Explanation: During startup of the session manager on system sysname, Strobe was unable to locate one of the following security packages: RACF, CA-Top Secret, or CA-ACF2. System Action: Strobe continues processing with the security interface disabled. Strobe will function without security protection. User Response: To obtain access to the security system at your installation, review your installation security procedures with the Strobe system programmer. STR6116I ACCESS FILTER WILL BE ENABLED FOR security ON SYSTEM sysname

Explanation: During startup of the session manager on system sysname, Strobe determined that security package security is present. security can be RACF, TSS (CA-Top Secret), or ACF2 (CAACF2). System Action: User Response: STR6117I Strobe enabled the security interface for that security package. None required.

NO REQUESTS FOUND

Explanation: You submitted a LIST or CLEAN request, but no measurement requests meet the specified selection criteria. System Action: User Response: request. Strobe does not process the LIST or CLEAN request. If you specified an incorrect request identification, correct and resubmit the

Messages Produced by Strobe

3-97

STR6118I

nnnn {JOBS|PROCESSES} FOUND TO SATISFY REQUEST ON SYSTEM sysname

Explanation: Strobe found nnnn jobs on system sysname to satisfy a request to display active jobs. Strobe found nnnn processes on system sysname to satisfy a request to display active processes. System Action: User Response: STR6119I Strobe continues processing. None required.

STOP COMMAND RECEIVED FROM CONSOLE consoleid The session manager received a STOP command from operator console The session manager terminates, removing the environment and ending all None required.

Explanation: consoleid. System Action: processing. User Response: STR6120I

REQUEST MODIFIED BY INSTALLATION EXIT Strobe determined that installation exit STRBCXAC modified a user request. Strobe continues to process the request.

Explanation: System Action:

User Response: List the request to determine what options have changed. If the new options create problems, notify the Strobe system programmer. STR6121I REQUEST {nnnn|jobname} NOT FOUND

Explanation: Strobe cannot find any request that matches the request number nnnn or jobname jobname given in the LIST operation. Either you specified the wrong request number or jobname, or Strobe deleted the request. System Action: User Response: request. STR6122W Strobe does not process the LIST request. If you specified an incorrect request identification, correct and resubmit the

REQUEST {nnnn|jobname} NOT FOUND ON SYSTEM sysname

Explanation: Strobe was unable to find on system sysname a request matching the request number nnnn or jobname jobname given in the ADD, CHANGE, DELETE, or SEND operation. Either you specified the wrong request number or jobname, or Strobe deleted the request. System Action: User Response: request. STR6123W Strobe does not process the request. If you specified an incorrect request identification, correct and resubmit the

REQUEST ACTIVE - SOME OPERANDS INVALID

Explanation: For an active request, you specified a CHANGE operation with an operand other than GOMIN, LIMIT, SAMPLES, OPTIONS, or RETAIN. You cannot change any other keyword operands after the measurement session becomes active. System Action: User Response: STR6124E Strobe processes the request, excluding the unacceptable parameters. List the request to determine what options have changed.

REQUEST COMPLETE - CHANGE NOT VALID

Explanation: You submitted a CHANGE operation for a measurement request that has already terminated. For a completed request, only a CHANGE operation with RETAIN=COMPLETE=nnn is valid, where nnn is the number of days the request is to be retained. System Action: User Response: Strobe does not process the request. None required.

STR6125I STROBE MEASUREMENT SESSION {INITIALIZING|PROCESSING SEND OPERATION| NOT RESPONDING - USE LIST OPERATION LATER|TERMINATING} Explanation: Strobe is processing a request and the Strobe measurement session did not respond to the command.

3-98

Strobe Messages Guide

One or more of the following messages can appear in a busy system if the operating system did not give the measurement task enough time to process the request: INITIALIZING PROCESSING SEND OPERATION NOT RESPONDING (message STR6125W) USE LIST OPERATION LATER TERMINATING

System Action: If you issued an ADD operation, Strobe displays the STROBE MEASUREMENT SESSION INITIALIZING message as many as four times. On the fifth iteration, Strobe displays the STROBE MEASUREMENT SESSION NOT RESPONDING message, and Strobe terminates. Strobe displays the same series of messages for the SEND operation, except that the messages read STROBE MEASUREMENT SESSION PROCESSING SEND OPERATION.

The measurement session continues unless the program being measured terminates, at which point Strobe terminates the measurement task.
User Response: STR6126I DENIED Notify the Strobe system programmer if the problem persists.

{jobname|username} DID NOT HAVE AN ACEE - ACCESS TO RESOURCES WILL BE

Explanation: The Strobe sign-on procedure determined that the job jobname or user username does not have an accessor environment element (ACEE). System Action: If a security system is installed, Strobe will deny the user or job access to all resources or jobs. User Response: Notify the Strobe system programmer. The system programmer may need to disable the access filter. STR6127E DELETE REJECTED - JOB ACTIVE ON SYSTEM sysname

Explanation: You specified a DELETE operation for an active measurement session that is running on system sysname. DELETE can be specified only for queued, deferred, or completed requests. System Action: Strobe does not process the request.

User Response: Wait until the job completes or use the SEND operation with the QUIT operand to terminate an active measurement session. Then reissue the DELETE operation. STR6128E OPTIONS=NOQUIT NOT POSSIBLE

Explanation: You issued an ADD operation specifying OPTIONS=NOQUIT but, during installation, the Strobe system programmer specified JSTCB=NEVER in the Strobe parameter file. System Action: User Response: STR6129E Strobe does not process the request. Notify the Strobe system programmer.

OPTIONS=NOQUIT IN EFFECT, QUIT INVALID

Explanation: You issued a SEND operation with the QUIT option to a request that is running with the NOQUIT option, or you attempted to stop Strobe while a measurement session was active with NOQUIT specified. System Action: Strobe ignores the SEND operation and continues processing. You will not be able to deactivate the Strobe environment unless the Strobe system programmer issues the TERMINATE command. User Response: If the message resulted from a SEND operation, resubmit it, and specify the STOP operand. If you want to stop Strobe, issue the TERMINATE command. STR6130I oper OPERATION COMPLETED Strobe successfully performed the indicated operation oper. Strobe continues processing. None required.

Explanation: System Action: User Response:

Messages Produced by Strobe

3-99

STR6131E

JOB NOT ACTIVE ON SYSTEM sysname

Explanation: You submitted a request for an active job and that job is not executing on system sysname. System Action: Strobe does not process the request.

User Response: Wait until the target jobstep is executing before submitting a request on the Strobe - Add Active Request panel or use the STEP=* command syntax. If you would like to measure a job step that is executing later, submit a request on the Strobe - Add Queued Request panel. STR6132E DUPLICATE JOBS FOUND ON SYSTEM sysname

Explanation: Strobe discovered more than one job on system sysname with a jobname that matches the one specified on an ADD ACTIVE request. System Action: Strobe does not process the request.

User Response: Determine the ASID number of the target job, and resubmit the request specifying the ASID parameter. STR6133E ADDRESS SPACE FAILED

Explanation: Strobe determined that an address space associated with a measurement request no longer exists. System Action: User Response: STR6134W Strobe marks the measurement request completed. Notify the Strobe system programmer.

STROBE MEASUREMENT SESSION NOT ACTIVE

Explanation: You specified a SEND operation for a job step for which no measurement session is active. System Action: Strobe does not process the request.

User Response: Wait until the measurement session becomes active before submitting any SEND requests to it. STR6135W ATTACH FILTER DISABLED - REQUEST CANNOT BE SERVICED You issued a request to measure a future job step, but the attach filter is

Explanation: disabled.

System Action: Strobe adds the request to the request queue but cannot service the request unless the attach filter is enabled with an ENV operation. User Response: Either enable the attach filter or wait until the job step begins execution and submit another request. STR6136W JOB IS CURRENTLY ACTIVE ON SYSTEM sysname - STEP MAY HAVE BEEN EXECUTED

Explanation: Strobe accepted a request to measure a job step. Because the job is already active on system sysname, however, the step may already have executed. System Action: the current job. If the step executed, or is currently executing, Strobe does not measure it in

User Response: Notify the Strobe system programmer. The system programmer can use STEP=* to specify that the current job step should be measured. STR6137E STROBE ACTIVE FOR JOB jobname ON SYSTEM sysname - REQUEST REJECTED

Explanation: Strobe received an ADD request to measure the current step of an active job jobname for which a measurement session is already active on system sysname. System Action: Strobe assigns a request number to the duplicate ADD request and marks this request as completed. User Response: Use the SEND operation to obtain the current status of the measurement session and to send sampling control commands to Strobe.

3-100

Strobe Messages Guide

STR6138W

REQUEST nnnn IS A DUPLICATE OF rrrr - REQUEST nnnn IS STILL QUEUED

Explanation: An ADD request with the request number nnnn duplicates an existing add request, request number rrrr. System Action: When the target job becomes active, Strobe initiates a measurement session for request rrrr, while request nnnn remains queued. Strobe will initiate a measurement session for request nnnn the next time the target job becomes active. User Response: If you want Strobe to measure the target job only once, delete request nnnn. Otherwise, none is required. STR6139W ATTACH FILTER WAS DISABLED AT TIME- time Strobe determined that the attach filter was disabled at time time.

Explanation:

System Action: Strobe accepts both active and queued requests, but measures active requests only. User Response: Notify the Strobe system programmer who can enable the attach filter so that you can measure queued requests STR6140I rrrr jobname status [rrrr jobname status]

Explanation: Strobe returns this message in response to a Format 3 LIST command. Strobe lists all outstanding requests rrrr, each with an associated jobname jobname and a status code status. These codes are as follows: (Q) if the request is queued, (A) if the request is active, (C) if the requested measurement session is completed, (D) if the request is deferred, and (S) if the request is suspended or stopped. System Action: User Response: STR6141I Strobe continues processing. None required.

nnnn jobname [status sysname] [request-operands]

Explanation: Strobe returns this message in response to an ADD, CHANGE, DELETE, LISTGRP command, or a Format 1, 2, or 3 LIST command. Strobe shows request number nnnn, job name jobname, and if present request status status, the system name, sysname and current request parameters [request-operands]. System Action: User Response: STR6142I Strobe continues processing. None required.

dsname volume ttttt/eeeee [OPEN]

Explanation: This message sometimes follows message STR6141I. Strobe provides the name of the current sample dataset dsname, its volume serial number volume, and the current sample counts (ttttt total samples and eeeee execution samples). OPEN appears at the end of this message if the sample dataset is still open. System Action: User Response: STR6143I Strobe continues processing. None required.

MESSAGES FOR REQUEST nnnn FOLLOW

Explanation: Strobe produces this message in response to a Format 1, 2, or 3 LIST command. After this message, Strobe shows only those messages not previously listed for request number nnnn. System Action: User Response: STR6144I Strobe displays messages. Read and respond to the messages.

END OF MESSAGES FOR REQUEST nnnn

Explanation: Strobe produces this message after all messages have been listed in response to a Format 1 LIST command. It indicates the end of messages for request number nnnn. System Action: User Response: Strobe continues processing. None required.

Messages Produced by Strobe

3-101

STR6145I

STROBE USERS - active jobs

Explanation: This message lists in active jobs the TSO user IDs and batch jobs that are currently using Strobe. System Action: User Response: STR6147I Strobe continues processing. None required.

IPL QUEUE INITIALIZATION COMPLETE - NEXT REQUEST IS nnnn

Explanation: Strobe established the environment from the Strobe IPL queue dataset. Strobe recovered requests from the queue dataset. The next request number is nnnn. System Action: User Response: STR6149S Strobe continues processing. None required.

SVC nnn IN USE - TYPE t [string]

Explanation: At initialization, Strobe determined that the SVC number nnn, type t, assigned in the Strobe parameter dataset appears to be in use. If the address in the SVC table points to a module with an alphanumeric string, the message provides the alphanumeric field as well. System Action: Strobe cannot establish its environment.

User Response: Notify the Strobe system programmer. The Strobe system programmer must reinstall the Strobe system with an available SVC of the appropriate type, or override the SVC system-check with SVCOVR=YES parameter in the PARMLIB dataset. STR6150I STROBE ENVIRONMENT DOES NOT EXIST

Explanation: The session manager responded to an environment status command or reported during session manager initialization that the Strobe environment does not exist. System Action: The Strobe environment is not created. During normal processing, Strobe will create the environment. User Response: STR6151I None required.

SVC nnn UNUSED - TYPE t [string]

Explanation: SVC number nnn, type t, appears to be unused. Strobe received an ENV CHECK, a SHOW, or an SVC command. The SVC number nnn, type t, assigned in the Strobe parameter dataset appears to be not used. If the address in the SVC table points to a module with an alphanumeric string, the message provides the alphanumeric field as well. System Action: User Response: STR6152E Strobe initializes using the SVC specified in the Strobe parameter file. None required.

COMMAND NOT VALID -STROBE ENVIRONMENT DOES NOT EXIST

Explanation: The Strobe environment was not established and a user privileged to establish it submitted a request that is not an ENV CREATE command. System Action: User Response: operation. STR6153S Strobe rejects the request. Notify the Strobe system programmer who can submit an ENV CREATE

STROBE ENVIRONMENT INCOMPATIBLE - MUST BE REPLACED [ON SYSTEM sysname]

Explanation: There are two copies of Strobe operating with the same fourth character in their load module names, or with the same SVC. If given, sysname identifies the system on which Strobe is running. System Action: The Strobe environment cannot be initialized.

User Response: Notify the Strobe system programmer. There has probably been an installation error.

3-102

Strobe Messages Guide

STR6154I STROBE - ENVIRONMENT STATUS - CREATED AT time DATE date REQUESTS rrrr/mmmm ACTIVE aaaa/bbbb QUEUED qqqq COMPLETED cccc DEFERRED dddd AUTOMONITORED eeee BPXBATCH ffff AUTOTRAN gggg AUTOCC hhhh Explanation: Strobe issues this message in response to a STATUS command. The time of the creation of the Strobe environment is time, the date of creation, date. Strobe is maintaining rrrr requests in all (with a maximum of mmmm requests):

aaaa requests are active (with a maximum of bbbb requests) qqqq are queued cccc are completed if present, dddd are deferred if present, eeee is the number of batch requests monitored by AutoStrobe if present, ffff is the number of BPXBATCH requests if present, gggg is the number of transaction requests monitored by AutoStrobe if present, hhhh is the number of transaction candidate requests monitored by AutoStrobe
Strobe continues processing. None required.

System Action: User Response: STR6155I

ATTACH FILTER {ENABLED|DISABLED} SYSTEM= sysname The Strobe attach filter on operating system sysname has a status of enabled or

Explanation: disabled.

System Action: If the status is enabled, Strobe can measure all requests. If not, Strobe accepts all requests but measures active requests only. User Response: STR6156W None required.

ATTACH FILTER STATUS INCONSISTENT WITH DEFAULT

Explanation: The current attach filter status differs from that assigned by the Strobe parameter dataset. System Action: Strobe continues processing with the attach filter in the current status.

User Response: Contact the Strobe system programmer to determine if the attach filter needs to be enabled. STR6157S STROBE ATTACH FILTER FAILED PROCESSING JOB jobname AT time date

Explanation: The attach filter routine terminated abnormally while servicing the job jobname, at time time, on date date. A Strobe recovery procedure disabled the attach filter. System Action: performed. User Response: STR6158W Strobe processes the job normally, but measurement requests may not be Notify the Strobe system programmer.

ENVIRONMENT REQUEST RESULTS IN NO CHANGES

Explanation: Strobe already performed the requested action. The ENV operation has no effect on the current environment. System Action: User Response: System Action: STR6159E Strobe continues processing but does not process this request. None required. Notify the Strobe system programmer.

STROBE AUTHORIZED COMMAND

Explanation: You submitted an ENV, TEST, CLEAN, or SHOW command for which you are not authorized. System Action: User Response: STR6160I Strobe continues processing but does not process this request. Notify the Strobe system programmer who has access to these commands.

ATTACH FILTER IS NOW DISABLED Strobe successfully processed an ENV operation that disabled the attach filter.

Explanation:

Messages Produced by Strobe

3-103

System Action: Strobe accepts both active and queued requests, but measures active requests only. User Response: None required.

STR6161I CSA=aaK/bbbbK/.c% ecsa=ddK/eeeeK/.f% LPA=ggggg LPB=hhh TRC=jjjj SAST=mmmmm JLST=nnnnn USSPST=ooooo DFT=ppppp ABTAB=qqqq MSGS=rrrr/sssss svc=ttt Explanation: Strobe occupies aaK of the bbbbK of storage in the CSA, a percentage of c. In the extended CSA (ECSA), Strobe occupies ddK of eeeeK storage, a percentage of f. The size of the Strobe SVC in ECSA is ggggg. The size of the Strobe SVC in CSA is hhh. The size of the SVC trace table is jjjj. The size of the Address Space table is mmmmm. The size of the Job List is nnnnn. The size of the USS Process list is ooooo. The size of the Defaults table is ppppp. The size of the Abend table is qqqq. The number and size of Message Queue is rrrr/sssss. The Strobe SVC number is ttt. System Action: User Response: STR6162W Strobe continues processing. None required.

SVC nnn IN USE - TYPE t [string]

Explanation: Strobe received either an ENV CHECK or SHOW SVC command. The SVC number nnn, type t, assigned to the Strobe parameter file appears to be in use. If the address in the SVC table points to a module with an alphanumeric string, the message provides the alphanumeric field as well. System Action: User Response: STR6163I Strobe displays the SVC entry. Notify the Strobe system programmer.

{CLEAN | PURGE} COMPLETE Strobe issues this message on completion of the CLEAN operation. Strobe continues processing. None required.

Explanation: System Action: User Response: STR6164W

Delete for request nnnn refused - measurement termination in progress

Explanation: The request to delete a Strobe measurement has been refused because the termination of the measurement is still in progress. Deleting the request could cause the termination to abend. System Action: Strobe continues processing.

User Response: Wait until the measurement termination has completed before attempting to delete the request. STR6165E RECOVER NOT POSSIBLE - REQUESTS ACTIVE

Explanation: Strobe cannot perform an ENV RECOVER command because measurement requests are active. System Action: User Response: command. STR6166I Strobe continues processing the active requests. Wait for all measurement requests to be completed and resubmit the

FOLLOWING REQUESTS DELETED Strobe processed a CLEAN operation and deleted the listed requests. Strobe continues processing. None required.

Explanation: System Action: User Response:

3-104

Strobe Messages Guide

STR6168I time_date

STROBE release { PARTIAL | COMPLETE } ENVIRONMENT DELETED. CREATED AT

Explanation: The Strobe release environment was either partially or completely removed. The environment was created at time_date. System Action: User Response: The Strobe environment is no longer active. None required.

STR6169I STROBE ENVIRONMENT IS NOW CREATED ON SYSTEM sysname [AS MEMBER OF XCF GROUP xcfgroup] Explanation: Strobe successfully created the environment on system sysname and can process all operations. If this version of Strobe is a member of a Strobe-XCF group, it can process operations initiated on another member and initiate operations for execution on other members. If present, the XCF group is named in xcfgroup. System Action: User Response: STR6170I Strobe continues processing. None required.

ATTACH FILTER IS NOW ENABLED Strobe successfully processed an ENV operation that enabled the attach filter. Strobe can measure both queued and active requests. None required.

Explanation: System Action: User Response: STR6171E

ENVIRONMENT RECOVER REQUIRED

Explanation: Strobe cannot perform an ENV CREATE command because it detected an active environment from a previous release. System Action: Strobe cannot create the new environment until the old one is deactivated.

User Response: To deactivate the old environment and create the new one, issue an ENV RECOVER command. To do this, see the Strobe Installation and Customization Guide. STR6172E ENVIRONMENT RECOVER INVALID

Explanation: Strobe cannot perform an ENV RECOVER command because no previous release of Strobe exists. System Action: Strobe does not change the environment.

User Response: The Strobe system programmer uses the ENV RECOVER command only when replacing an old Strobe release. STR6173I OPERATING SYSTEM LEVEL IS syslvl

Explanation: The operating system level is syslvl. Strobe issues this message in response to a STATUS command. System Action: User Response: Strobe continues processing. None required.

STR6174S STROBE {SESSION MANAGER | SESSION REQUESTER | MEASUREMENT INITIALIZATION|MEASUREMENT SESSION| INTERFACE|SVC} ABENDED {S|U} abendcode - rsncode AT{psw addr|modname} [{modname offset|csect offset}] [SDWA NOT AVAILABLE] [{RECURSION | PERCOLATION}] Explanation: An ABEND occurred during Strobe processing. The message shows the system or user ABEND abendcode, reason code rsncode, at PSW address pswaddr, or module name modname and if available module name offset modname offset, or control section name and offset csect offset. If appropriate, SDWA (system diagnostic work area) NOT AVAILABLE displays. If present, the ABEND type is given as RECURSION or PERCOLATION. System Action: The Strobe measurement task or Strobe program terminates but user tasks are unaffected. User Response: Notify the Strobe system programmer. If Strobe issued ABEND code U00000000, increase the region size of the job you are measuring and resubmit the request.

Messages Produced by Strobe

3-105

STR6175S R0-R7= addr0 addr1 addr2...addr7 R8-RF= addr8 addr9 addrA...addrF addr [key data] addr [key data]... Explanation: An ABEND occurred in the Strobe system. The contents of registers 0 through 15 appear in fields addr0 through addrF. Subsequent lines addr key data display the contents of storage pointed to by the PSW (program status word) for a length of X50, followed by the contents of the storage pointed to by the registers. If accessible, the key field shows the protection key, and the data field dumps X 10 (32 bytes) of the area addressed by the registers. Strobe lists these lines in the Strobe log only. System Action: Strobe continues processing.

User Response: Contact Compuware Customer Support. This information is provided for diagnostic purposes. STR6176S SDWAFLAGS flags translation

Explanation: An ABEND occurred in the Strobe system. The values of the ABEND flags from the system diagnostic work area (SDWA), flags, appear with the translation of those flags, translation. This message appears in the Strobe log only. System Action: Strobe continues processing.

User Response: Contact Compuware Customer Support. This information is provided for diagnostic purposes. STR6177S SA - {FWD | BKWD} data

Explanation: An ABEND occurred in the Strobe system. The data will be split across several lines and will consist of: RT3 reserved ptr-pre ptr-next R14 R15 R0 entryname R1 R2.... R12, where R0.... R15are register contents. reserved is an IBM field. ptr-prev is a pointer to the previous save area. ptr-next is a pointer to the next save area. This message appears in the Strobe log only. System Action: User Response: Strobe continues processing. Contact Compuware Customer Support.

STR6178S PSW [FROM {SDWA | PRB | IRB | SVRB}] [AT ERROR] [sdwapsw|prbpsw| irbpsw|svrbpsw] Explanation: An ABEND occurred in the Strobe system. The PSW (program status word) at the time of the error appears in one of the following: sdwapsw, the SDWA (system diagnostic work area), or prbpsw, the PRB (program request block), or irbpsw, the IRB (interruption request block), or svrbpsw, the SVRB (supervisor request block). Message STR6182S displays the module, control section, or entry at the time of the error. System Action: User Response: STR6179S Strobe continues processing. Contact Compuware Customer Support.

TYPE tttt CP cc

PSW psw

R15 r15

R00 r0 TIME time

R01 RE r1 rr

ASID TCB aaaa tcb

Explanation: An ABEND occurred in the Strobe system. Strobe displays the trace table, listing the type of entry (tttt), the PSW (program status word), psw, the contents of registers 15, 0, and 1 (r15, r0, r1), RE a reserved field (rr), the CP id (cc), the ASID, (aaaa), the TCB (task control block address), tcb, and the time (time). This message appears in the Strobe log only. System Action: User Response: Strobe continues processing. Contact Compuware Customer Support.

3-106

Strobe Messages Guide

STR6180I AT offset]

MODULE modname AT modaddr(modlen) FROM source [ABENDS = num LAST IS abendcode

Explanation: ABENDs occurred in the Strobe system. The load module named modname at the address modaddr with length modlen was loaded from the load library with the dataset name or data definition name and concatenation number identified in source. If present, the number of ABENDs is num, the ABEND code of the last ABEND is abendcode, and its offset is offset. System Action: User Response: Strobe continues processing. None required.

STR6181I {MODULE | CSECT} csectname AT csaddr(cslen) > R=release <assembly date> PTF=FS000000 Explanation: An ABEND occurred in the Strobe system. The control section named csectname at the address csaddr with length cslen has a release number release. The last assembly date was assembly date and the PTF level was FS######. System Action: User Response: STR6182S Strobe continues processing. None required.

{MODULE|CSECT|ENTRY} name AT addr OFFSET offset - string

Explanation: An ABEND occurred in the module, control section, or entry name, located at addr. The site of the ABEND was at offset offset. The module, control section, or entry contains the phrase string. System Action: User Response: STR6183S Strobe continues processing. None required.

SVCDUMP - RC=rc - REQUEST nnnn

Explanation: Request nnnn specified that Strobe perform an SVCDUMP. The return code from the SVCDUMP request is rc. Depending upon the return code, the dump may reside in the system dump dataset. System Action: Strobe requests an SVC for the measured address space.

User Response: To process the dump according to your installations standards, contact the Strobe system programmer. STR6185I MODULE TRACKING TABLES FOR REQUEST NOT AVAILABLE

Explanation: Strobe deleted the module tracking tables for the specified request from storage. They are no longer available for display. System Action: User Response: STR6186S Strobe continues processing. None required.

SESSION MANAGER MUST BE ACTIVE BEFORE USING STROBE The Strobe address space was not started.

Explanation:

System Action: The Strobe address space was not available when this message was issued. Strobe services are not available unless the Strobe address space is started. User Response: STR6187E Notify the Strobe system programmer to start the Strobe address space.

commandname COMMAND REJECTED BY ACCESS CONTROL EXIT A Strobe user exit rejected the command commandname. Strobe rejects the requested command. See the system programmer responsible for the Strobe user-exit facility.

Explanation: System Action: User Response: STR6188E

MEASUREMENT SESSION INITIALIZATION REJECTED BY ACCESS CONTROL EXIT A Strobe user exit rejected the measurement session initialization request. Strobe cannot accept the measurement request. See the system programmer responsible for the Strobe user-exit facility.

Explanation: System Action: User Response:

Messages Produced by Strobe

3-107

STR6189I

{STR6189I|STR6189W| STR6189E| STR6189S} user exit message text

Explanation: A Strobe user exit rejected an operation or a measurement session initialization request. user exit message text gives the message returned by the user exit facility; the error severity indicator (I, W, E or S) depends on the returned message. System Action: User Response: STR6190W Strobe does not process the request because the user exit rejected it. Correct and resubmit the request.

STROBE LOG DATA SET IS nnn% FULL The Strobe log filled nnn% of its allocated space. Strobe continues processing. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR6191E

STROBE LOG DATA SET IS FULL All of the allocated extensions on the Strobe log are used. Strobe terminates processing.

Explanation: System Action:

User Response: Notify the system programmer. To continue processing, the system programmer must either clear the log with the LOG CLEAR command or backup and clear the log with Strobe Log (STRBCLOG) Utility. STR6192E INTERNAL ERROR - ddname NOT OPEN Strobe expects the ddname ddname to be open, but it is not.

Explanation:

System Action: Strobe may not process the current command or request, or all processing may terminate depending upon the severity of the error. User Response: STR6193I Notify the Strobe system programmer.

ddname DATA SET - dsname IS percent % FULL

Explanation: The name of the dataset referred to by ddname is dsname, and it is percent percent full. System Action: command. User Response: STR6194I Strobe issues this message in response to a STATUS or SHOW QUEUE None required.

LOG DATA SET - dsname IS percent % FULL [WITH nn EXTENTS]

Explanation: The name of the current Strobe log is dsname. It is percent percent full, and, if this value is provided, it has nn extents. System Action: User Response: STR6195S Strobe continues processing. None required.

RECENTLY REFERENCED SRE FOLLOWS

Explanation: Strobe terminated abnormally and displays the last active Strobe request element (SRE). System Action: Strobe continues processing.

User Response: Review the ABEND message and resubmit the request. If the problem occurs again, notify the Strobe system programmer. STR6196S STROBE ABEND RECOVERY COMPLETE - {TERMINATING|CONTINUING} Strobe experienced an ABEND. Strobe continues or terminates as stated in the message. Contact the Strobe system programmer to correct the problem and restart

Explanation: System Action: User Response: Strobe.

3-108

Strobe Messages Guide

STR6197E

Strobe of Changeman address space is not supported

Explanation: Strobe encountered a request to measure an address space that is running the Changeman Audit program. Strobe cannot measure such an address space because of a conflict with the tasking structure. System Action: Strobe rejects the measurement request. This message follows STR6203E, which gives the jobname and session initialization time. User Response: STR6198I None required.

SRC= src TMI= tmi OPC= opc SMI= smi This message is generated by internal tracing that Compuware has initiated.

Explanation:

src is the number of session requester calls the session manager has received. tmi is the number of timer interrupts that the session manager has received. opc is the number of operator commands that the session manager has received. smi is the number of SMI interrupts in the session manager.
Strobe continues processing. Your Compuware systems engineer will determine any further action.

System Action: User Response: STR6199E

STROBE HAS EXPIRED REQUEST DENIED The session manager determined that the current version of the Strobe system

Explanation: expired.

System Action: Strobe will allow you to list or delete requests, but it will not allow you to add requests. Strobe will not process any requests that are queued. User Response: STR6200I Notify the Strobe system programmer.

STROBE MEASUREMENT SESSION INITIALIZED FOR JOB jobname AT time date

Explanation: Strobe started a measurement session for job jobname at time time and date date. System Action: User Response: STR6201I Strobe continues processing. None required.

STROBE MEASUREMENT SESSION COMPLETED FOR JOB jobname AT time date Strobe completed a measurement session for job jobname at time time and date Strobe continues processing. None required.

Explanation: date. System Action: User Response:

STR6202I STROBE ATTACH FILTER PROCESSING FOR REQUEST nnnn STOPPED ON SYSTEM sysname - REQUEST ALREADY ACTIVE ON SYSTEM sysname Explanation: The attach filter for system sysname determined there is a measurement request (request nnnn) associated with a job step that is about to start, and attempted to initiate the measurement. However, another member of the Strobe-XCF group is already measuring the request. This message appears in the Strobe log only. System Action: User Response: STR6203E date Strobe terminates processing for request rrrr on system sysname. None required.

STROBE MEASUREMENT SESSION INITIALIZATION FAILED FOR JOB jobname AT time

Explanation: Strobe failed to initialize a measurement session for job jobname at time time and date date. Accompanying messages, including STR6197E, STR6206E, STR6210E, STR6215E, STR6216E, and STR6221E, provide additional information. System Action: Strobe stops processing the request.

User Response: If the request was for an unsupported address space there is no response required; otherwise resubmit the measurement request. If the problem persists, notify the Strobe system programmer.

Messages Produced by Strobe

3-109

STR6204E

STEP IS IN ALLOCATION You submitted a request for a job step that is still controlled by the MVS Strobe cannot measure the job step. Resubmit the request after the job step completes allocation.

Explanation: initiator. System Action: User Response: STR6205E

LIMITED FUNCTION ADDRESS SPACE

Explanation: The target program is running in a limited function address space. The operating system does not provide the functions that Strobe requires for its operation. System Action: User Response: Strobe cannot measure limited function address spaces. None required.

STR6206E STROBE INITIALIZATION SRB DID NOT COMPLETE - STEP=stepname PGM=pgmname REASON=reason TCBFLAGS=tcbflags Explanation: The Strobe initialization service request block (SRB) for step stepname, program pgmname did not complete. The reason is given in reason. The TCB flag values given in tcbflags are defined in the IBM z/OS MVS Data Areas Manual. System Action: Strobe does not process the request.

User Response: Resubmit the measurement request. If the problem persists, notify the Strobe system programmer. STR6207E IRB WAS NOT DISPATCHED

Explanation: Strobe attempted to implant itself into a user address space to start a measurement, but the IRB (Interrupt Request Block) scheduled by the Strobe SRB did not complete. System Action: Strobe canceled the IRB, so the measurement request did not start.

User Response: Determine why the IRB could not be dispatched or could not complete in the target address space and correct, if possible. It is also possible that the situation was a temporary one, and a repeat ADD command might implant Strobe successfully. STR6209I COBOL II DETECTED Strobe detected that the COBOL II environment is active. Strobe continues processing. None required.

Explanation: System Action: User Response: STR6210E

Strobe of HSC address space is not supported

Explanation: Strobe encountered a request to measure an address space that is running Storage Techs HSC system. Strobe cannot measure such an address space because of a conflict with the tasking structure. System Action: Strobe rejects the measurement request. This message follows STR6203E, which gives the jobname and session initialization time. User Response: STR6211E None required.

INSUFFICIENT AVAILABLE MEMORY

Explanation: The Strobe measurement session cannot be initialized because of insufficient virtual storage. The Strobe measurement task requires 300K of storage in the extended private address space. Each of the Strobe options has additional storage requirements. See the Strobe Installation and Customization Guide for the virtual storage requirements of Strobe and Strobe options. System Action: terminates. User Response: The Strobe environment is still available, but the measurement request Notify the Strobe system programmer.

3-110

Strobe Messages Guide

STR6212E

TOO MANY ACTIVE REQUESTS

Explanation: The number of active measurement requests on the Strobe system exceeded the maximum set at system installation. System Action: User Response: STR6213I Strobe cannot process additional requests. Notify the Strobe system programmer.

PROGRAM progname DETECTED - alias USED

Explanation: Strobe detected a program whose name on the EXEC PGM= statement (progname) begins with a recognized alias for CICS, IMS, or CA-IDMS. System Action: Strobe invokes module STRBCRB using the alias alias: DFHBCRB for CICS programs, DFSBCRB for IMS programs, and IDMBCRB for CA-IDMS programs. User Response: STR6214E None required.

STROBE INITIALIZATION IRB DID NOT COMPLETE - REASON=text

Explanation: The Strobe initialization processing under an IRB (Interruption Request Block) did not complete. The system-supplied reason is in text. System Action: User Response: STR6215E Strobe does not process the request. Notify the Strobe system programmer.

Strobe of MIM address space is not supported

Explanation: Strobe encountered a request to measure an address space that is running the MIM program. Strobe cannot measure such an address space because of an enqueue-handling conflict with MIM. System Action: Strobe rejects the measurement request. This message follows STR6203E, which gives the jobname and session initialization time. User Response: STR6216E None required.

Strobe of HSM address space is not supported

Explanation: Strobe encountered a request to measure an address space that is running IBMs DFHSM program. Strobe cannot measure such an address space because of conflicts with CA Technologies TMS program. System Action: Strobe rejects the measurement request. This message follows STR6203E, which gives the jobname and session initialization time. User Response: STR6217E None required.

SESSION MANAGER NOT ACTIVE The session manager is not active. Strobe does not measure the current job.

Explanation: System Action:

User Response: Notify the Strobe system programmer to restart the session manager and resubmit the request. STR6218E OPTIONS=NOQUIT REQUIRED

Explanation: Strobe detected a situation in which the Strobe measurement task must be attached as a job step task because the measured program already has job step tasks. The ADD operation did not specify the OPTIONS=NOQUIT operand, and the JSTCB parameter defined at Strobe installation either requires the OPTIONS=NOQUIT operand or disallows measurement of such jobs. System Action: Strobe rejects the measurement request.

User Response: If the Strobe system programmer specified JSTCB=ALLOW in the Strobe parameter file, resubmit the request, and specify OPTIONS=NOQUIT. STR6219W NOQUIT OPTION IN EFFECT

Explanation: Strobe added a measurement request for a job. The Strobe measurement task is attached as a job step task because the measured job attached its tasks as job step tasks. You

Messages Produced by Strobe

3-111

cannot issue a QUIT command to this request, and the Strobe environment cannot be deactivated until the measurement task terminates. System Action: Strobe continues processing. The measurement task remains in the target address space and does not terminate until the address space terminates. User Response: To stop sampling, issue a STOP command. Strobe will close the sample dataset and enter the wait state. The measurement task will terminate when the job step terminates. STR6220W OPTIONS=NOJSTCB USED - {TSO|VIO STEPLIB|VIO|TCAM}- ENCOUNTERED

Explanation: Strobe cannot attach the user program as a job step task because of compatibility problems with TSO, VIO STEPLIB, VIO, or TCAM. System Action: User Response: STR6221E Strobe attaches the user program as a step task. None required.

Strobe of MSAS address space is not supported

Explanation: Strobe encountered a request to measure the Strobe MSAS address space. Strobe cannot measure this address space because of a conflict with space switching PC routines used by Strobe. System Action: Strobe rejects the measurement request. This message follows STR6203E, which gives the jobname and session initialization time. User Response: STR6222S None required.

SESSION MANAGER IS STILL INITIALIZING The Strobe address space has not yet completed initialization. The Strobe address space is not yet available.

Explanation: System Action:

User Response: The time required for Strobe initialization depends upon a number of factors including the number of requests that exist at initialization and system performance. Strobe will be available once initialization completes. If this message persists, notify the Strobe system programmer. STR6223E DATA SET NAME PREFIX IS LARGER THAN 26 CHARACTERS The dataset name prefix entered in the Strobe parameter file is larger than 26

Explanation: characters.

System Action: The session manager startup terminates with an error after processing the Strobe parameter file. User Response: Contact the Strobe system programmer to correct the error and restart the session manager. STR6224E INVALID EXPIRATION DATE SPECIFIED The expiration date specified in the Strobe parameter dataset is invalid.

Explanation:

System Action: The session manager startup terminates with an error after processing the Strobe parameter file. User Response: Notify the Strobe system programmer to correct the error and restart the session manager. STR6225I DCB=(RECFM=VB, LRECL=137, BLKSIZE=blksize)

Explanation: Strobe displays the data control block (DCB) characteristics of the Strobe log. The record format (RECFM) is VB (variable block), the record length (LRECL) is 137, and the block size BLKSIZE) is blksize. System Action: User Response: STR6226I Strobe continues processing. None required.

SPACE= (alloc units, (xxxx,yyyy))

Explanation: Strobe displays the current space allocation of the Strobe log. alloc units can be block size (BLK), track (TRK), or cylinders (CYL). Primary allocation is xxxx, and secondary allocation is yyyy. This message is followed by STR6229I.

3-112

Strobe Messages Guide

System Action: User Response: STR6227I

Strobe continues processing. None required.

NUMBER OF EXTENTS USED nn

Explanation: Strobe displays the current number of allocation extents, nn, used by the Strobe log. System Action: User Response: STR6228I Strobe continues processing. None required.

LOG HISTORY

Explanation: If the log dataset is a generation data group, Strobe will display a history of the last ten Strobe logs used. This message is followed by STR6229I. System Action: User Response: STR6229I Strobe continues processing. None required.

dsname START TIME=(time date)

Explanation: Strobe displays the Strobe log name dsname followed by the start time time and start date date. System Action: User Response: STR6230S Strobe continues processing. None required.

STROBE SESSION REQUESTER ALREADY ACTIVE For the current job or user, the session requester is already active.

Explanation:

The session requester determined that there is another copy of the session requester active in the current address space.
System Action: The second copy of the session requester terminates with a return code of 12. User Response: STR6231I You are already in an active TSO session. Continue using the active session.

NUMBER OF {CA|CI} SPLITS nnn Strobe displays the number nnn of CA or CI splits in the queue dataset. Strobe continues processing.

Explanation: System Action:

User Response: Use these VSAM statistics to guide you in optimizing the efficiency of the VSAM environment. STR6232I NUMBER OF RECORDS IN QUEUE nnn Strobe displays the number, nnn, of records in the queue dataset. Strobe continues processing.

Explanation: System Action:

User Response: Use these VSAM statistics to guide you in optimizing the efficiency of the VSAM environment. STR6233I LAST USED RBA rba1 HIGH ALLOC RBA rba2

Explanation: Strobe displays the last used relative block address (RBA), rba1, and the high allocated RBA, rba2, in the VSAM queue dataset. System Action: Strobe continues processing.

User Response: Use these VSAM statistics to guide you in optimizing the efficiency of the VSAM environment. STR6234I NUMBER OF xxxxxxxx yyyyyyyy

Explanation: Strobe displays the number (yyyyyyyy) of inserts, updates, or deletes (xxxxxxxx) to the queue dataset. System Action: Strobe continues processing.

User Response: Use these VSAM statistics to guide you in optimizing the efficiency of the VSAM environment.

Messages Produced by Strobe

3-113

STR6235I

FREE SPACE (BYTES) xxx

Explanation: The amount of FREE SPACE in bytes available in the current queue allocation is xxx. System Action: User Response: STR6239I Strobe continues processing. None required.

PROCESSING FOR ENV commandname {INITIATED | COMPLETED} The processing for command commandname has initiated, or it has completed. None. None required.

Explanation: System Action: User Response:

STR6240I ABEND abendtype abendcode - rsncode AT {modname |pswaddr} - [modoffset - csectname csectoffset] jobname (asid) time date {UDUMP | ABEND| MDUMP| SDUMP} {PERC|RECUR} Explanation: This message lists the history of ABENDS from which Strobe recovered since the last time the session manager was started. The type of ABEND abendtype, the system or user ABEND code abendcode, and reason code rsncode are followed by the name of the module modname or the address of the program status word pswaddr. If available, the offset of the module modoffset, the name of the control section csectname and the offset of the control section csectoffset appear. Strobe then records the job name jobname (asid) at time time on date date.

Strobe action is one of the following: UDUMP, ABEND, MDUMP, or SDUMP. Then either PERC or RECUR appear.
System Action: The Strobe measurement task or Strobe program terminates but user tasks are unaffected. User Response: Notify the Strobe system programmer to contact Compuware Customer Support. Have the Strobe log available when calling in the trouble report. STR6241I NO ABENDS DETECTED

Explanation: Strobe detected no ABENDs in the system since the last time the session manager was started. System Action: User Response: STR6242E Strobe continues processing. None required.

QUEUE PROCESSING ERROR - MAX REQUESTS nnn QUEUED REQUESTS READ mmm

Explanation: During session manager startup, Strobe encountered more requests on the queue dataset mmm than the number defined by the MAX REQUESTS parameter nnn in the Strobe defaults. System Action: Strobe terminates.

User Response: Notify the Strobe system programmer. The Strobe system programmer must increase the Strobe defaults to allow for the number of requests to be read from the queue. STR6243S STROBE INITIALIZATION TERMINATED - ENVIRONMENT DOES NOT SUPPORT USE OF XCF GROUPS Explanation: You specified the XCFGROUP= parameter in the Strobe parameter dataset so that you can join the Strobe-XCF group. Your version of the MVS operating system, however, does not support use of Strobe-XCF groups. To use Strobe-XCF groups, the system must be at MVS/ESA V4R1 or higher. System Action: User Response: STR6244S Strobe terminates initialization. Notify the Strobe system programmer.

STROBE INITIALIZATION TERMINATED - UNABLE TO JOIN STROBE-XCF GROUP text

Explanation: Strobe could not join the Strobe-XCF group. One of the following statements appears in text:

INVALID GROUP NAME IN INSTALLATION PARAMETERS DUPLICATE STROBE-XCF MEMBER NAME

3-114

Strobe Messages Guide

SYSPLEX HAS MAXIMUM NUMBER OF XCF GROUPS STROBE ERROR DURING function PROCESSING XCF ERROR DURING JOIN PROCESSING RETURN CODE rc REASON CODE rsnc
System Action: Strobe terminates initialization.

User Response: In the first case, examine and change the specification for the XCFGROUP parameter. In the last four cases, notify the Strobe system programmer. STR6245S STROBE INITIALIZATION TERMINATED - UNABLE TO COMMUNICATE WITH STROBEXCF GROUP Explanation: Strobe could not communicate with the other Strobe-XCF group members once it had joined the Strobe-XCF group. System Action: User Response: Strobe terminates initialization. Notify the Strobe system programmer.

STR6246S STROBE INITIALIZATION TERMINATED - {QUEUE DATA SET NAME|MESSAGE DATA SET NAME| RELEASE LEVEL| VERSION CHARACTER} DOES NOT MATCH STROBE-XCF GROUP Explanation: One or more of the following values does not match the corresponding value for the Strobe-XCF group:

Dataset name for queue Dataset name for message Release level Version character
Strobe terminates initialization. Notify the Strobe system programmer.

System Action: User Response:

STR6247I PARAMETER(S) parameter1, parameter2, parameter3, CHANGED TO value1, value2, value3, TO MATCH STROBE-XCF GROUP VALUES Explanation: Strobe changed the values that you specified for the named parameter(s) parameter1, parameter2, parameter3, to the values specified in value1, value2, value3. The values were changed to conform to the values that the Strobe-XCF group uses. In a multisystem environment, these values must be the same among all members of the group. System Action: User Response: Strobe continues initialization. None required.

STR6248E commandname COMMAND PROCESSING TERMINATED - ERROR DURING fnctname PROCESSING Explanation: Strobe terminated processing for command commandname because it experienced an error while processing the internal function, subroutine, or value indicated in fnctname. System Action: User Response: Strobe does not process the command. Notify the Strobe system programmer.

STR6249W REQUEST FOR JOB jobname MAY NOT BE QUEUED TO SYSTEM sysname INSUFFICIENT ACCESS AUTHORITY Explanation: Your job jobname may not be queued on system sysname (one of the systems to which you targeted the request) because the security data base of the system on which you entered the request indicates that you are not authorized to measure the job on the system. System Action: request. Strobe still routes this request to all systems to which you targeted the

The security data bases of those systems will check your authorization. If Strobe finds one or more systems on which you are authorized to measure job jobname, Strobe will queue the request on those systems.
User Response: To measure a job on any specific system, the Strobe system programmer or security administrator must grant you access to the system in its security data base. The Strobe system programmer may want to change the systems on which you are authorized to submit measurement requests.

Messages Produced by Strobe

3-115

STR6250I

[text,] [rel,] [lvl,] [volser]

Explanation: This message lists information in response to a SHOW DEFAULTS command. In text it provides default values supplied through the parameter file and currently in storage. In addition it can display: the current release of Strobe (rel), the Strobe PTF level (lvl), and the Strobe tape volume serial number (volser). System Action: User Response: None. None required.

STR6251W REQUEST DELETED BEFORE AUTOMATIC PERFORMANCE PROFILE SUBMISSION ROUTINE CALLED Explanation: The completed request that stipulated automatic creation of a Performance Profile has been deleted. System Action: User Response: the request. STR6252E Strobe does not process the request. To obtain an automatically created Performance Profile, you must resubmit

AUTOMATIC PERFORMANCE PROFILE COULD NOT BE CREATED error reason

Explanation: The Performance Profile could not be automatically created. error reason is one of the following:

The internal variable SESSID is invalid. The internal variable SAMPDSN is invalid. The sample dataset name sdsname is invalid. ACEEUSRI is invalid.
Strobe does not process the request.

System Action:

User Response: Notify the Strobe system programmer. If you require further assistance, contact Compuware Customer Support. STR6253W PERFORMANCE PROFILE JCL CONTAINED UNRECOGNIZED TOKEN token Strobe was unable to recognize and could not substitute a value for the token

Explanation: token.

System Action: Depending upon the nature of the error, Strobe may or may not produce a Performance Profile. User Response: Verify the JCL used and resubmit the request.

STR6254E AUTOMATIC PROFILE CREATION COULD NOT BE COMPLETED. {TOKEN <SAMDSN> NOT FOUND} {TOKEN <PRINTDSN>NOT FOUND} Explanation: The Performance Profile could not be automatically created because either SAMDSN or PRINTDSN could not be found. System Action: User Response: STR6255E Strobe does not process the request. Verify the JCL used and resubmit the request.

INTRDR DYNAMIC ALLOCATION FAILED RC= rc ERC/IRC= erc/irc

Explanation: Strobe could not allocate the internal reader dataset. The return code is rc, the error reason code is erc, and the information reason code is irc. System Action: The requested Strobe command fails. Depending upon the nature of the error, Strobe may or may not continue processing. User Response: STR6256E Notify the Strobe system programmer.

INTRDR OPEN FAILED. RC = rc Strobe could not open the internal reader. The return code is rc. Strobe does not process the request. Save the contents of the Strobe log and contact Compuware Customer

Explanation: System Action: User Response: Support.

3-116

Strobe Messages Guide

STR6257I

JCL SUBMITTED FOR AUTOMATIC PROFILE CREATION The JCL for creating a Performance Profile automatically has been successfully Strobe processes the request. None required.

Explanation: submitted.

System Action: User Response: STR6258S yyyy/zzzz

SESSION REQUESTER ABEND RECOVERY COMPLETE - {TERMINATING | CONTINUING}

Explanation: Strobe experienced an ABEND. yyyy is the amount of stack space used. zzzz is the amount of stack space allocated. System Action: User Response: STR6259S yyyy/zzzz Strobe continues or terminates, as stated in the message. Contact the Strobe system programmer to correct the problem.

SESSION MANAGER ABEND RECOVERY COMPLETE - {TERMINATING | CONTINUING}

Explanation: Strobe experienced an ABEND. yyyy is the amount of stack space used. zzzz is the amount of stack space allocated. System Action: User Response: STR6260E Strobe continues or terminates, as stated in the message. Contact the Strobe system programmer to correct the problem.

REQUEST nnnn COMPLETE - CHANGE NOT VALID

Explanation: You submitted a CHANGE operation for measurement request nnnn, but that request has already terminated. For a completed request, only a CHANGE operation with RETAIN=COMPLETE=rrr is valid, where rrr is the number of days the request is to be retained. System Action: User Response: Strobe does not process the request. None required.

STR6261I {request|element} nnnn jobname STEP=stepname CREATED=date time [expiration] [groupname] parameters Explanation: Strobe displays request information:

In response to a LIST, ADD, CHANGE, SEND or DELETE command, Strobe displays details of the request. In response to a LISTGRP command submitted with a AutoStrobe request group name parameter, Strobe displays details of the elements in that request group. System Action: User Response: STR6262I None. None required.

{qname rname}| {GQSCAN-INCOMPLETE}| {GQSCAN-RC=rc}

Explanation: For qname rname, Strobe listed a resources major name qname and minor name rname in response to a SHOW ENQUEUES command. For GQSCAN-INCOMPLETE, the IBM MVS service GQSCAN issued an incomplete list of resource major names qnames and minor names rnames in response to a SHOW ENQUEUES command. For GQSCAN-RC=rc, the IBM MVS service GQSCAN issued a return code of rc in response to a failed SHOW ENQUEUES command. System Action: None.

User Response: For qname rname, the command executed successfully and no response is required. For GQSCAN-INCOMPLETE, the command executed unsuccessfully. Resubmit the SHOW ENQUEUES command to view the entire list of resource major names qnames and minor names rnames. For GQ-SCAN- RC=rc, refer to the IBM z/OS MVS Programming Authorized Assembler Services Reference volumes for an explanation of the return codes meanings. STR6263I asid jobname stepname stepname progname - ATTACH FILTER INFO

Explanation: This message is issued when a program for which there is an Add Queued request executes. The job to be measured with Strobe is identified by its address space identifier asid, job name, jobname, and step names, stepname. The name of the program that requests Strobe measurement is given in progname.

Messages Produced by Strobe

3-117

System Action: User Response: STR6264E

None. None required.

SEND COMMAND FAILED - PREVIOUS SEND IN PROGRESS FOR REQUEST nnnn

Explanation: The SEND command that you issued failed because a SEND command has already been issued for request nnnn. System Action: Strobe does not process the request.

User Response: Wait until the previous SEND command has completed. Check the Strobe log for additional messages. STR6265E REQUIRED POSITIONAL PARAMETER MISSING A positional parameter that is required for the command is missing. Strobe does not process the request.

Explanation: System Action:

User Response: Reissue the command using the correct required positional parameter. For the correct syntax for the command, refer to Measuring with Strobe Command Language in the Strobe User Guide. STR6266I GROUP groupname, GRPOWNER=grpowner

Explanation: This message is issued in response to a LISTGRP command that specifies the group name. It identifies the name of the group and will always be followed by STR6261I. System Action: User Response: STR6267E None. None required.

THE KEYWORD USER IS REQUIRED ON THE JOB STATEMENT The keyword USER and the associated value is missing from the job statement Strobe will not process the request. Notify your Strobe system programmer.

Explanation: JCL. System Action: User Response: STR6268E

THE KEYWORD USER VALUE DOES NOT MATCH THE ACTUAL USER

Explanation: The value for the keyword USER on the job statement is not valid because it does not match the users user ID. System Action: User Response: STR6269E Strobe does not process the request. Specify the users user ID and resubmit the job statement.

THE JOB STATEMENT SPECIFIED CONTAINED A PASSWORD KEYWORD

Explanation: The job statement contained a PASSWORD keyword. For security reasons, this parameter is not allowed on the job statement. System Action: User Response: STR6270E Strobe does not process the request. Resubmit the job statement and do not use the PASSWORD keyword.

routine - QUEUE DELETE FAILED. RC rc RSNC rsnc

Explanation: An error occurred while routine routine was attempting to delete a record from the queue dataset. The VSAM return code is rc, and the VSAM reason code is rsnc. System Action: User Response: STR6271E Strobe continues processing. Notify the Strobe system programmer.

routine - QUEUE READ FAILED - RC rc RSNC rsnc

Explanation: An error occurred while routine routine was attempting to read a record on the queue dataset. The VSAM return code is rc, and the VSAM reason code is rsnc. System Action: User Response: The session manager terminates. Notify the Strobe system programmer.

3-118

Strobe Messages Guide

STR6272E

routine - QUEUE UPDATE FAILED: RC rc RSNC rsnc

Explanation: An error occurred while routine was attempting to update a record on the queue dataset. The VSAM return code is rc, and the VSAM reason code is rsnc. System Action: User Response: STR6273I The session manager terminates. Notify the Strobe system programmer.

jobname (jobidentifier) SUBMITTED FOR AUTOMATIC PROFILE CREATION

Explanation: The JCL with jobname for creating a Performance Profile automatically has been successfully submitted and assigned the job identifier jobidentifier. System Action: User Response: STR6274E Strobe processes the request. None required.

routine - QUEUE OPEN FAILED - RC rc RSNC rsnc

Explanation: An error occurred while routine was attempting to open a record on the queue dataset. The VSAM return code is rc, and the VSAM reason code is rsnc. System Action: User Response: STR6275E The session manager terminates. Notify the Strobe system programmer.

LOG HISTORY PROCESSING FAILED - RC rc RSNC rsnc

Explanation: An error occurred while Strobe attempted to read or write to the Strobe log measurement session history record on the queue dataset. The return code is rc, and the reason code is rsnc. System Action: User Response: Strobe continues processing. Notify the Strobe system programmer.

STR6276E SESSION MANAGER FUNCTION ERROR - ROUTINE routinename FUNCTION fnctcode SMRC smrc FRC fntrc Explanation: An error occurred in the session manager while processing a request. The routine that detected the error is given in routinename. The function code for the request that was being processed when the error occurred is given in fnctcode. The return code from the session manager is smrc, and function return code is fntrc. System Action: Depending on the severity and nature of the error, Strobe will continue processing the request or terminate the request. User Response: Note the error messages that Strobe returns to your terminal and check the Strobe log for additional messages associated with the request number. Take action based on this information. For more information on the cause of the error, determine the definition of the function code, given in fnctcode, by referencing it in the section entitled Function Codes Returned by Strobe Session Manager in Chapter 4, Abend Codes Returned by Strobe. STR6277E LOG DATA SET IS NOT IN A GENERATION DATA GROUP. PLEASE USE COMMAND LOGCLEAR TO CLEAR LOG DATA SET Explanation: You entered a LOGSWITCH command for a nongeneration data group (nonGDG) log dataset. System Action: Strobe does not process the request. The LOGSWITCH command is invalid for a non-GDG log dataset. User Response: Use the LOGCLEAR command or the Strobe log utility STRBCLOG to clear the current Strobe log. STR6278E LOG DATA SET IS IN THE GENERATION DATA GROUP. PLEASE USE COMMAND LOGSWITCH TO SWITCH LOG DATA SET Explanation: You entered the LOGCLEAR command for a generation data group (GDG) log dataset. The LOGCLEAR command is invalid for a GDG log dataset. System Action: User Response: Strobe continues processing. Use the LOG SWITCH command rather than the LOGCLEAR command.

Messages Produced by Strobe

3-119

STR6279I

LOGCLEAR COMPLETE - SYSLOG DATA SET HAS BEEN CLEARED The LOGCLEAR command executed. The Strobe log is cleared and ready to be Strobe continues processing. None required.

Explanation: used. System Action: User Response: STR6280E

ISPF REENTRY WITHOUT INIT CALL Strobe encountered an internal error while processing an ISPF request. Strobe terminates processing the request.

Explanation: System Action:

User Response: Exit from Strobe to ISPF, and then reinvoke Strobe from the ISPF PRIMARY OPTIONS panel. If the problem persists, notify the Strobe system programmer. STR6282E BLDL FAILED FOR MODULE modname Strobe detected an internal error while trying to locate the module modname. Strobe terminates abnormally, with ABEND code 620-4.

Explanation: System Action:

User Response: Examine the ABEND output accompanying this message for more information. Notify the Strobe system programmer. STR6283E INTERNAL ERROR modname NOT FOUND Strobe detected an internal error while trying to locate the module modname. Strobe terminates abnormally, with user ABEND code 610-5.

Explanation: System Action:

User Response: Examine the ABEND output accompanying this message for more information. Notify the Strobe system programmer. STR6284E INTERNAL ERROR INVALID PARAMETER LIST PASSED TO LOGSUB RTN Strobe detected an internal error while processing a parameter list. Strobe terminates abnormally, with user ABEND code 610-6.

Explanation: System Action:

User Response: Examine the ABEND output accompanying this message for more information. Notify the Strobe system programmer. STR6285E INTERNAL ERROR INVALID RETURN FROM QREC RTN Strobe detected an internal error while processing a request.

Explanation:

System Action: If this error occurs during Strobe initialization, the request is deleted and initialization continues. In other cases, Strobe terminates abnormally, with user ABEND code 610-7. User Response: Examine the ABEND output accompanying this message for more information. Notify the Strobe system programmer. STR6286E ATTACH FILTER ENABLED DURING REMOVE ENV PROCESSING Strobe detected an internal error while processing an ENV REMOVE request. Strobe terminates abnormally, with user ABEND code 610-8.

Explanation: System Action:

User Response: Examine the ABEND output accompanying this message for more information. Notify the Strobe system programmer. STR6289E INTERNAL LOGIC ERROR SEARCHING SVC TABLE Strobe detected an internal error while searching the SVC table. Strobe terminates abnormally, with user ABEND code 610-10.

Explanation: System Action:

User Response: Examine the ABEND output accompanying this message for more information. Notify the Strobe system programmer. STR6290E SYSTEM SERVICE FAILED (sysserve) ddname - RC=rc [erc]

Explanation: The system service sysserve for ddname ddname failed. The return code is rc, and the reason code, if given, is erc.

3-120

Strobe Messages Guide

System Action: If OPEN fails for the SYSQUEUE dataset, Strobe terminates abnormally with user ABEND code 610-9. User Response: STR6291E Notify the Strobe system programmer.

DATA SET NOT ALLOCATED - ddname The dataset with data definition name ddname is not allocated. Strobe cannot find the dataset and does not process the request.

Explanation: System Action:

User Response: If the message shows STRMTLIB as the unallocated ddname, then your installation may be set up to run Strobe out of an APF-authorized load library, but the target jobstep (or user ID) did not correctly allocate that load library. Verify that the target jobstep correctly allocates the APF-authorized load library and retry the job. If the error persists, notify the Strobe system programmer. STR6292E OPEN FOR ddname1(ddname2) FAILED

Explanation: The data definition name for the dataset with logical name ddname1 and true ddname ddname2 cannot be opened. System Action: Strobe may terminate.

User Response: Check the data definition statements to ensure that Strobe is trying to open the correct dataset. If the statements are correct, notify the Strobe system programmer. STR6293E nnn MESSAGES LOST [FOR JOB jobname|FOR REQUEST rrrr]

Explanation: Excessive messages accumulated for either jobname or the request rrrr. Strobe is unable to write the messages to the Strobe log. System Action: User Response: STR6294E Strobe discards nnn messages and continues processing. Notify the Strobe system programmer.

INVALID SYSLOG SPECIFICATION Strobe detected an invalid Strobe log. Possible causes include assignments to:

Explanation:

DD Dummy A SYSOUT class A non-DASD device


System Action: Strobe terminates.

User Response: Notify the Strobe system programmer. There has probably been an installation error. STR6295E DYNAMIC ALLOCATION FAILED - RC=rc; ERC/IRC=erc/irc; dsname

Explanation: Strobe cannot allocate the dataset dsname. The return code is rc, the error reason code is erc, and the information reason code is irc. System Action: processing. User Response: STR6296I The requested Strobe command fails. Strobe may or may not continue Notify the Strobe system programmer.

NEW SYSLOG DATA SET IDENTIFIED: SWITCHING TO dsname

Explanation: Strobe determined that a new GDG log dataset dsname was cataloged and is automatically switching to the new dataset. System Action: Log processing continues using the new dataset. Strobe records all further messages in the new dataset. User Response: STR6297S None required.

MODULE modname NOT FOUND IN {linklist|steplib} Strobe cannot find the module modname in either linklist or steplib. Strobe does not process the request.

Explanation: System Action:

Messages Produced by Strobe

3-121

User Response: Notify the Strobe system programmer. There has probably been an error installing Strobe or defining Strobe to execute from an APF-authorized library. This procedure is explained in the Strobe Installation and Customization Guide. STR6298S INCOMPATIBLE MODULE- modname - release

Explanation: The module modname is invalid. release is the release of the module, and it is incompatible with the release of Strobe. System Action: Strobe does not process the request.

User Response: Notify the Strobe system programmer. There has probably been an installation error. STR6299I LOGSWITCH COMPLETE - NEW LOG DATA SET IS syslog name

Explanation: The LOGSWITCH command completed. Strobe allocated the new GDG log dataset syslog name. System Action: Log processing continues using the new dataset. Strobe records all further messages in the new dataset. User Response: STR6300I None required.

INPUT = operand

Explanation: Strobe received a request for an operation and displays the operation and its operands in operand. System Action: User Response: STR6301E Strobe continues processing. None required.

SYNTAX ERROR DETECTED PROCESSING - data

Explanation: Strobe detected a syntax error while interpreting a request. The error was within the data shown in data. System Action: User Response: STR6302E Strobe does not process the request. Correct the error and resubmit the request.

EXPECTED CONTINUATION NOT RECEIVED You submitted an incomplete operation. Strobe does not process the request.

Explanation: System Action:

User Response: Complete and resubmit the request. See the Strobe User Guide for a description of Strobe operations. STR6303E EXTRANEOUS OPERANDS - characters

Explanation: Strobe detected non-blank characters between the operand and comment fields of a request. The character string is characters. System Action: User Response: STR6304E Strobe does not process the request. Eliminate the extraneous characters and resubmit the request.

REQUIRED OPERAND MISSING [- operand] A required operand is missing. If given, the missing operand is operand. Strobe does not process the request. Specify the missing operand and resubmit the request.

Explanation: System Action: User Response: STR6305E

EXCESSIVE OPERAND LENGTH - operand

Explanation: Strobe detected an operand (operand) whose keyword length exceeds the maximum number of characters. System Action: User Response: Strobe does not process the request. Correct the error and resubmit the request.

3-122

Strobe Messages Guide

STR6306E

AUTOMATIC PROFILE CREATION SUBMISSION FAILED

Explanation: The IBM MVS internal reader rejected the JCL that you submitted for automatic Profile creation. System Action: Because the internal reader rejected the JCL, a Profile could not be automatically created. User Response: You cannot create a Performance Profile automatically. You can, however, create a Performance Profile using the sample dataset, which is valid. STR6307I STROBE ADDRESS SPACE IS {SWAPPABLE | NON-SWAPPABLE}

Explanation: The Strobe address space is running in either a swappable or non-swappable mode. You can set the mode using the SWAP = parameter. Setting the mode to SWAP = NO will improve the performance of the Strobe address space. System Action: User Response: STR6308W None. None required.

TRANSWAP FAILED IN rc

Explanation: Strobe issues this message when a customers request for the Strobe address space to run in SWAP = NO mode fails. The return code, rc, indicates the reason code for the failure. System Action: User Response: STR6309I The Strobe address space continues to run in a swappable mode. Contact Compuware Customer Support.

DISPOSITION=KEEP IS INVALID WITH SMS PARAMETERS OVERRIDDEN TO CATLG

Explanation: Strobe determined that an SMS parameter was coded on a measurement request with a dataset disposition of KEEP. System Action: Because the disposition of KEEP is invalid for an SMS dataset, Strobe uses a disposition of CATLG instead. User Response: STR6310E None required.

UNIDENTIFIED OPERAND - operand Strobe encountered an unidentified operand keyword operand while processing Strobe does not process the request. Correct the error and resubmit the request.

Explanation: a request.

System Action: User Response: STR6311E

AMBIGUOUS OPERAND - operand

Explanation: Strobe encountered an ambiguous operand keyword operand while processing a request. System Action: User Response: STR6312E Strobe does not process the request. Supply a unique abbreviation for the operand and resubmit the request.

DUPLICATE OPERAND - operand Strobe encountered a duplicate operand keyword operand while processing a Strobe does not process the request. Remove one of the operands and resubmit the request.

Explanation: request. System Action: User Response: STR6313E

MUTUALLY EXCLUSIVE OPERANDS - operand1 operand2 A request specifies keyword operands that are mutually exclusive. Strobe does not process the request. Eliminate all but one of the conflicting operands and resubmit the request.

Explanation: System Action: User Response:

Messages Produced by Strobe

3-123

STR6314E

INVALID OR MUTUALLY EXCLUSIVE OPERANDS ON ENVIRONMENT COMMAND An ENV command specifies keyword operands that are invalid or mutually Strobe does not process the request.

Explanation: exclusive. System Action:

User Response: Eliminate the invalid operands, or all but one of the conflicting operands, and resubmit the request. STR6315E INVALID OPERATION - operation Strobe encountered an invalid operation keyword operation while processing a Strobe does not process the request. Correct the error and resubmit the request.

Explanation: request. System Action: User Response: STR6316E

AMBIGUOUS OPERATION - operation

Explanation: Strobe encountered an ambiguous operation keyword operation while processing a request. System Action: User Response: STR6317E Strobe does not process the request. Supply a unique abbreviation for the operation, and resubmit the request.

MAXIMUM OF number LIST ENTRIES ALLOWED FOR LIST CONTAINING VALUE: value

Explanation: An ADD or CHANGE request contained a list of entries that is too large. The list of entries contains the value, and is limited to number of entries. System Action: User Response: request again. STR6318W Strobe does not process the request. Specify a list of values with fewer entries and submit the ADD or CHANGE

STORAGE OBTAIN FOR EPVT FAILED

Explanation: An attempt to measure an OS/390 UNIX System Services fork job was made. Strobe was unable to reserve the first several pages of EPVT, which results in an abend further into the measurement process. System Action: User Response: STR6319E Strobe continues processing the request. None required.

INVALID USE OF WILDCARD

Explanation: An ADD or CHANGE request is invalid because it had a wildcard (*) in the first character of a jobname parameter.A wildcard character is only valid as the last character in a jobname or as the only character. System Action: Strobe does not process the request.

User Response: Reenter the request using a valid character for the first character of the jobname parameter. STR6320E ddname FILE REQUIRES VSAM SHAREOPTIONS(4,3) The VSAM file ddname is not defined with SHAREOPTIONS(4,3), which Strobe Strobe fails to initialize.

Explanation: requires. System Action:

User Response: Use the IDCAMS option ALTER to change the VSAM file to SHAREOPTION(4,3), or delete and redefine the VSAM file with SHAREOPTIONS(4,3). STR6330E INVALID DECIMAL NUMBER - number

Explanation: While processing a request, Strobe found nonnumeric characters, number, in a field that only accepts numeric numbers, or Strobe found a numeric value greater than 2,147,483,647. System Action: User Response: Strobe does not process the request. Correct the number and resubmit the request.

3-124

Strobe Messages Guide

STR6332W

nnn IS TOO SMALL - min U Strobe found a number nnn to be beneath the range of acceptable values.

Explanation:

System Action: Strobe replaces the number with min, the smallest allowable value for that range, and continues processing. User Response: If you want to increase the value from min, use the CHANGE command to modify the request. STR6333W nnn IS TOO LARGE - max USED Strobe encountered a number (nnn) to be above the range of acceptable values.

Explanation:

System Action: Strobe replaces the number with max, the largest acceptable value for that range, and continues processing. User Response: If you want to decrease the value from max, use the CHANGE command to modify the request. STR6334E INVALID HEX STRING hexstring

Explanation: Strobe detected an invalid operand representing a hexadecimal character string hexstring. System Action: User Response: STR6335E Strobe does not process the request. Correct the value and resubmit the request.

INVALID operand SPECIFICATION

Explanation: The value specified for the operand operand on the ADD, CHANGE, LIST, or SEND operation is invalid. For example, specifying EXCLUDE=*ALL will elicit this message. This message will also be issued when DISP specifies SYSTEM=*ALL. System Action: User Response: STR6336W Strobe does not perform the operation. Correct the operand and resubmit the request.

STRBCXAC (parm) nnn IS TOO LARGE - max USED

Explanation: Strobe user exit STRBCXAC modified a parameter, parm, and the new value, nnn, is too large. System Action: User Response: STR6337W The exit interface will supply max, the largest value allowed. Notify the Strobe system programmer that the exit STRBCXAC has an error.

STRBCXAC (parm) nnn IS TOO SMALL - min USED

Explanation: Strobe user exit STRBCXAC modified a parameter, parm, and the new value, nnn, is too small. System Action: User Response: STR6338E The exit interface will supply min, the smallest value allowed. Notify the Strobe system programmer that the exit STRBCXAC has an error.

INVALID SYSTEM NAME sysname - NOT A STROBE-XCF GROUP MEMBER The system sysname is not a system in the Strobe-XCF group. Strobe does not process the request.

Explanation: System Action:

User Response: Resubmit the request with a valid system name. To see a list of members in the Strobe-XCF group, enter the SHOW MEMBERS command. STR6350I nnn RECORDS COPIED FROM ACTIVE LOG

Explanation: Strobe utility STRBCLOG copied nnn records from the active Strobe log to the backup dataset. System Action: processing. User Response: Strobe copied and cleared the active log. The session manager can resume None required.

Messages Produced by Strobe

3-125

STR6351E

DDNAME - SYSUT1 - NOT FOUND Strobe utility STRBCLOG could not find ddname SYSUT1. Strobe terminates.

Explanation: System Action:

User Response: Review the documentation and JCL to ensure that you adhere to the proper procedures for running Strobe. STR6360E QCREATE INTERNAL ERROR - QGWA ALREADY EXISTS A duplicate call was made to build a queue global work area (QGWA). The session manager terminates. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR6361E

fnctname INTERNAL ERROR - QGWA DOES NOT EXIST

Explanation: A function fnctname failed because Strobe could not find a queue global work area (QGWA) control block. System Action: User Response: STR6362I The session manager terminates. Contact Compuware Customer Support.

QUEUE DATASET ENVIRONMENT REMOVED Strobe disabled the queue dataset processing. Strobe continues processing. None required.

Explanation: System Action: User Response: STR6363E

fnctname - ddname DATASET NOT OPERATIONAL

Explanation: While executing function fnctname, Strobe found that the dataset that ddname ddname refers to is not operational. System Action: User Response: STR6364E The session manager terminates. Contact Compuware Customer Support.

fnctname - ddname ENVIRONMENT NOT ESTABLISHED

Explanation: Strobe attempted to use the dataset referred to by ddname ddname without first building the necessary control blocks. The function name that detected the error is fnctname. System Action: User Response: STR6365E The session manager terminates. Contact Compuware Customer Support.

QOPEN - ddname DATASET ALREADY OPEN

Explanation: Strobe attempted to open the dataset that ddname ddname refers to and found that it was already opened. System Action: User Response: STR6366E The session manager terminates. Contact Compuware Customer Support.

fnctname - ddname - QGWA CORRUPTION DETECTED

Explanation: While processing a call for function fnctname and ddname ddname, Strobe detected queue global work area (QGWA) corruption. System Action: User Response: STR6367E The session manager terminates. Contact Compuware Customer Support.

fnctname - ddname DATASET NOT OPEN

Explanation: Strobe function fnctname found that the dataset that ddname ddname refers to was already closed. System Action: User Response: The session manager terminates. Contact Compuware Customer Support.

3-126

Strobe Messages Guide

STR6368E

fnctname - ddname PLIST MISSING OR INVALID

Explanation: While processing a call for function fnctname and ddname ddname, Strobe found that the parameter list was missing or invalid. System Action: User Response: STR6369E The session manager terminates. Contact Compuware Customer Support.

fnctname ddname - QPL POINTER INVALID AT addr

Explanation: While processing function fnctname for ddname ddname, Strobe found that the queue parameter list pointer at address addr was invalid. System Action: User Response: STR6370S The session manager terminates. Contact Compuware Customer Support.

ddname DATASET NOT ALLOCATED

Explanation: During startup, Strobe determined that the dataset that ddname ddname refers to was missing. Strobe requires that this dataset be allocated. System Action: The session manager terminates.

User Response: Ask the Strobe system programmer to correct the session manager JCL and restart the session manager. STR6371S QSER - ddname RESERVE ALREADY OUTSTANDING

Explanation: Strobe attempted to issue two reserves for the same queue dataset that ddname ddname refers to. System Action: User Response: STR6372S The session manager terminates. Contact Compuware Customer Support.

fnctname - ddname RESERVE NOT ISSUED

Explanation: In the function fnctname, Strobe attempted to open the dataset that ddname ddname refers to without first reserving it. System Action: User Response: STR6373W The session manager terminates. Contact Compuware Customer Support.

QOPEN - ddname VSAM OPEN STATUS RC=rc RSN=rsn

Explanation: Strobe determined that the dataset that ddname ddname refers to was not properly closed and that VSAM has performed an implicit VERIFY. The VSAM return code is rc, and the VSAM reason code is rsn. System Action: User Response: STR6374E Strobe continues processing normally. Notify the Strobe system programmer.

QOPEN - ddname UNABLE TO INITIALIZE DATASET RC=rc

Explanation: Strobe was unable to complete the initialization of the dataset that ddname ddname refers to. The VSAM return code is rc. System Action: User Response: STR6375E The session manager terminates. Contact Compuware Customer Support.

fnctname - failingfnct ddname STATUS RC=rc RSN=rsn

Explanation: A function, failingfnct, failed for the dataset that ddname ddname refers to. The return code of the failed function is rc, and the reason code of the failed function is rsn. fnctname is the function currently executing. System Action: User Response: The session manager terminates. Contact Compuware Customer Support.

Messages Produced by Strobe

3-127

STR6376E

QDDFIND - ddname DDNAME INVALID

Explanation: The ddname referred to by ddname that was passed to the Strobe QDDFIND function is invalid. System Action: User Response: STR6377E The session manager terminates. Contact Compuware Customer Support.

QDDFIND - ddname DSNAME TABLE POINTER INVALID at addr

Explanation: Strobe function QDDFIND found that the dataset table pointer in the ddname table referred to by ddname is invalid at address addr. System Action: User Response: STR6378I The session manager terminates. Contact Compuware Customer Support.

call=routine LEN=length KEY=key DATE=date TIME=time

Explanation: Strobe issues this message in response to a SHOW SMTRACE command or during ABEND processing. It introduces trace table record information. The type of call is call and its values may be CVENTER, CVEXIT, or ENTRY. The name of the routine is routine. The length of the data is length, and the storage key of the data is key. The date and time that Strobe wrote the trace record is date and time. STR6379I follows this message. System Action: User Response: STR6379I Strobe continues processing. None required.

DATA= aaaaaaaa bbbbbbbb cccccccc dddddddd eeeeeeee ffffffff gggggggg hhhhhhhh Following DATA=, Strobe prints the trace table record information. Strobe continues processing. None required.

Explanation: System Action: User Response: STR6380E

PARAMETER parm INVALID WHEN STROBE IS STROBE NOT IN MULTISYSTEM MODE

Explanation: The command contains a parameter parm that is invalid when Strobe is not in multisystem mode. Examples of these parameters include SYSTEM= and EXCLUDE=. System Action: Strobe does not process the command.

User Response: Contact the Strobe system programmer if you would like to operate in multisystem mode. Otherwise, resubmit the command without the invalid parameter. STR6381I DATE FORMAT IS date TIME FORMAT IS time

Explanation: The date format you chose is date and the time format you chose is time. If you did not change the date and time format, Strobe uses the defaults: MM/DD/YYYY (month/day/year) for the date and HH:MM:SS (hours:minutes:seconds) for the time. System Action: User Response: STR6382W Strobe continues processing. None required.

INVALID TRACE TABLE. CANNOT PRINT

Explanation: During ABEND recovery processing or in response to a SHOW SMTRACE command, Strobe determined that it cannot print the trace table information. System Action: Strobe continues processing.

User Response: None required. To obtain trace information, ensure that the parameter TEST SMTRACE=ON is set. STR6383E CONSISTENCY ERROR PROCESSING STRBANCE PARAMETERS

Explanation: During processing of the Strobe for Natural STRBANCE parameters in the Strobe PARMLIB, an error was encountered. System Action: Strobe stops processing the Strobe PARMLIB and terminates startup.

User Response: Review the STRBANCE entries in the Strobe PARMLIB for errors. Required keywords are determined by ENVIRON value specified. See the Strobe Installation and Customization Guide for the STRBANCE definition.

3-128

Strobe Messages Guide

STR6390E

routine INTERNAL ERROR - block INVALID AT ADDRESS addr

Explanation: While performing Strobe routine routine in a multisystem environment, Strobe detected an error in the Strobe control block referenced by block. Strobe writes this message to the Strobe log. System Action: Strobe is not able to process the request. This message is followed by message STR6812I, which provides additional diagnostic information. User Response: Contact Compuware Customer Support.

STR6391I {SESSION REQUESTER | SESSION MANAGER} REGION SIZE {ABOVE | BELOW} 16MB IS nnnn BYTES (nnnnKB) Explanation: The region size of a component of Strobe, the session requester or session manager, above or below 16MB is nnnn bytes (hexadecimal), nnnnKB (decimal). Strobe issues this message in response to a STATUS command. System Action: User Response: STR6400W None. None required.

XCFGROUP PARAMETER IGNORED - SYSTEM sysname IS IN XCF-LOCAL MODE

Explanation: Strobe does not process the XCFGROUP parameter because the system sysname is in XCF-LOCAL mode. The system sysname is not configured to run in a sysplex environment. System Action: Strobe continues processing.

User Response: None required. To prevent Strobe from issuing this message, remove the XCFGROUP parameter from the PARMLIB dataset. STR6401I STROBE-XCF GROUP NAME IS: xcfgroup The name of the Strobe-XCF group is xcfgroup. None. None required.

Explanation: System Action: User Response: STR6402I

STROBE-XCF GROUP MEMBERS ARE: localsysname sysname1 sysname2...sysnamenn

Explanation: This message lists the names of the active systems in the Strobe-XCF group beginning with local system localsysname and continuing to the last system sysnamenn. System Action: User Response: STR6403I None. None required.

SYSTEM sysname IS NOT A MEMBER OF A STROBE-XCF GROUP The system named sysname is not defined as a member of any Strobe-XCF None. None required.

Explanation: group. System Action: User Response: STR6404I

SYSTEM sysname DOES NOT SUPPORT THE USE OF XCF GROUPS

Explanation: The system sysname does not support the use of XCF Groups. To use XCF Groups, the system must be at MVS/ESA V4R1 or higher. System Action: User Response: STR6405E Strobe does not process the request. None required.

routine XCF MEMBER xcfname NOT FOUND IN MEMBER LIST

Explanation: While performing Strobe routine routine in a multisystem environment, Strobe uses IBMs cross-system coupling services to communicate with other Strobe systems in the sysplex. Strobe issues this message when a member of the Strobe-XCF group attempted to communicate with another member of the group, named xcfname. At this time, xcfname is not an active member of the Strobe-XCF group, so it is not able to receive or send messages. System Action: Strobe does not process the request.

Messages Produced by Strobe

3-129

User Response: None required. If the request fails and the problem persists, contact the Strobe system programmer who can verify that system xcfname is active. If this system is active, the system programmer may want to stop and restart the version of Strobe on system xcfname. STR6406W XCF FUNCTION IXCfnctname FAILED, RC=rc, RSN=rsncode

Explanation: One of the services provided by the cross-system coupling facility (XCF) failed. The service name is identified as IXCfnctname. Possible service names, and their associated function, are as follows:

IXCJOIN - join an XCF group IXCLEAVE - leave an XCF group IXCMSGI - receive a message from another member of the XCF group IXCMSGO - send a message to another member of the XCF group IXCQUERY - determine status and active members of the XCF group

The return codes and reason codes issued from the failing XCF service are identified by rc and rsncode. For the explanations of these return and reason codes, see the IBM z/OS MVS Programming Authorized Assembler Services Reference volumes.
System Action: Strobe may not be able to join or leave the Strobe-XCF group, or to communicate with other members of the Strobe-XCF group. User Response: STR6407E Notify the Strobe system programmer.

routine XCF MEMBER xcfname NOT FOUND IN MEMBER LIST FOR REQUEST nnnn

Explanation: While performing Strobe routine routine in a multisystem environment, Strobe uses IBMs cross-system coupling services to communicate with other Strobe systems in the sysplex. Strobe issues this message when a member of the Strobe-XCF group attempted to communicate with another member of the group, named xcfname. At this time, xcfname is not an active member of the Strobe-XCF group, so it is not able to receive or send messages. The failed communication attempt occurred while processing request number nnnn. System Action: Strobe does not process the request.

User Response: None required. If the request fails and the problem persists, contact the Strobe system programmer who can verify that system xcfname is active. If this system is active, the system programmer may want to stop and restart the version of Strobe on system xcfname. STR6408S CONTINUE STROBE VERSION release ENVIRONMENT EXISTS. STROBE INITIALIZATION CANNOT

Explanation: Strobe found an existing older Strobe environment, release, but the Strobe system programmer did not specify REMV_OLD=YES in the parameter dataset. System Action: Strobe initialization terminates.

User Response: Bring up a Strobe Version release environment and issue the SEND, QUIT command against all active requests. If Strobe release is not available, stop the jobs that are being measured. When there are no more active requests, the system programmer must specify REMV_OLD=YES in the parameter dataset member ALLOCATE and begin initializing Strobe. STR6409I BEGINNING OF MESSAGES FROM PREVIOUS STROBE ENVIRONMENT

Explanation: Upon initializing, Strobe found a pre-existing Strobe environment and is reporting the messages for that environment. The Strobe messages follow. System Action: User Response: STR6410I Strobe continues processing. None required.

END OF MESSAGES FROM PREVIOUS STROBE ENVIRONMENT

Explanation: Upon initializing, Strobe found a pre-existing Strobe environment and is reporting the messages for that environment. This is the end of the Strobe messages. System Action: User Response: Strobe continues processing. None required

3-130

Strobe Messages Guide

STR6411W {CANNOT STOP | TERMINATING} STROBE. THE FOLLOWING REQUESTS {ARE | WILL REMAIN} ACTIVE sre nnn [, sre nnn, sre nnn.] Explanation: You issued a STOP or TERMINATE command, but one or more Strobe requests are still active. Strobe reports active request(s) in Strobe request element sre nnn, and if present, Strobe reports additional requests in sre nnn. System Action: In response to a STOP command, Strobe continues processing. In response to a TERMINATE command, Strobe stops processing and the requests remain active. User Response: If you issued a STOP command, wait for the measurement requests to be completed or, if necessary, stop the active measurements and reissue the STOP command. If you cannot stop the active measurements, issue the TERMINATE command.

If you issued the TERMINATE command, no response is required.


STR6412I STROBE FOUND A PREVIOUSLY EXISTING STROBE ENVIRONMENT Upon initialization, Strobe identified a pre-existing Strobe environment. Strobe continues processing. None required.

Explanation: System Action: User Response: STR6414I

ISSUING {SUSPEND | RESTART} FOR REQUEST # nnnn Upon initialization, Strobe found request nnnn to still be active.

Explanation:

System Action: Strobe continues initializing. The active request nnnn is suspended during Strobe initialization and is restarted once Strobe initialization is complete. User Response: STR6415W None required.

SERIALIZATION UNAVAILABLE FOR {SRE | CVU | SMI | SMT | SMW | SMW2} CHAIN

Explanation: While attempting to verify its control block chains during recovery processing, Strobe was unable to acquire serialization for one of the following chains: SRE (Strobe request element), CVU (session manager user element), SMI (session manager internal element), SMT (session manager timer queue), SMW (session manager work element), SMW2 (session manager work element for a specific user). System Action: User Response: STR6416W Strobe continues processing. None required.

INVALID CHAINING IDENTIFIED IN {SRE | CVU | SMI | SMT | SMW | SMW2} CHAIN

Explanation: While attempting to verify its control block chains during recovery processing, Strobe found one of the following chains to be invalid: SRE (Strobe request element), CVU (session manager user element), SMI (session manager internal element), SMT (session manager timer queue), SMW (session manager work element), SMW2 (session manager work element for a specific user). System Action: User Response: STR6417W Strobe processing continues. None required.

INVALID DATA FOUND IN {SRE | CVU | SMI | SMT | SMW | SMW2} ELEMENT

Explanation: While attempting to verify its control block chains during recovery processing, Strobe found that an item in one of the following chains was not an element: SRE (Strobe request element), CVU (session manager user element), SMI (session manager internal element), SMT (session manager timer queue), SMW (session manager work element), SMW2 (session manager work element for a specific user). System Action: User Response: STR6418I Strobe continues processing. None required.

ELEMENT PRIOR TO ERROR IS AS FOLLOWS {SRE | CVU | SMI | SMT | SMW | SMW2}

Explanation: While attempting to verify its control block chains during recovery processing, Strobe detected a problem in one of its chains. Strobe displays the chain element prior to the problem element. The element could be: SRE (Strobe request element), CVU (session manager user element), SMI (session manager internal element), SMT (session manager timer queue),

Messages Produced by Strobe

3-131

SMW (session manager work element), or SMW2 (session manager work element for a specific user). System Action: User Response: STR6419I Strobe continues processing. None required.

ELEMENT CONTAINING ERROR IS AS FOLLOWS {SRE | CVU | SMI | SMT | SMW | SMW2}

Explanation: While attempting to verify its control block chains during recovery processing, Strobe detected a problem in one of its chains. Strobe displays the problem element. The element could be: SRE (Strobe request element), CVU (session manager user element), SMI (session manager internal element), SMT (session manager timer queue), SMW (session manager work element), or SMW2 (session manager work element for a specific user). System Action: User Response: STR6420W Strobe continues processing. None required.

STORAGE AVAILABLE BUT NOT ALLOCATED BY APPLICATION

Explanation: While attempting to verify its control block chains during recovery processing, Strobe found storage on a chain that is not allocated to this version of Strobe. This message is always preceded by STR6416W, which identifies the chain in which the problem occurred. System Action: User Response: Strobe continues processing. None required.

STR6421W INVALID POINTER FOUND IN FOLLOWING STRUCTURE. NEXT ELEMENT POINTED TO IN CHAIN DOES NOT EXIST {SRE | CVU | SMI | SMT | SMW | SMW2} Explanation: While attempting to verify its control block chains during recovery processing, Strobe found a control block on one of the following chains that contained an invalid forward pointer: SRE (Strobe Request Element), CVU (session manager user element), SMI (session manager internal element), SMT (session manager timer queue), SMW (session manager work element), or SMW2 (session manager work element for a specific user). System Action: User Response: STR6423W Strobe continues processing. None required.

CANNOT SUSPEND REQUEST # nnnn, STROBE INITIALIZATION CONTINUING

Explanation: Either Strobe experienced an ABEND or you ended the Strobe session with a TERMINATE command. Upon initialization, Strobe found request nnnn to be active and Strobe was unable to suspend it. System Action: Strobe continues initialization and moves the active request to the version of Strobe that is initializing. User Response: STR6424W None required. The active measurement request may ABEND.

LICENSE VERIFICATION WARNING, RETURN CODE rc REASON CODE erc

Explanation: The Strobe base license is invalid for the reason specified by return code rc and error reason code erc. Strobe writes the explanation of the warning to the Strobe Log. If License Management message suppression and distribution is active, this message will not appear. However, the warning details are routed according to your LMSINIT SYSIN parameters.

Note: You may have entered the warning period for your current license. Ignore this message if you have already requested a new license.
System Action: User Response: assistance. Strobe continues processing. Contact Compuware License Management System Customer Support for

STR6425S STROBE VERSION release ENVIRONMENT HAS ACTIVE MEASUREMENTS AND CANNOT BE DELETED Explanation: Strobe found that an existing Strobe environment, Version release, has active requests and REMV_OLD=YES is specified. A new version of Strobe cannot be installed with the same version letter as an older version that has active measurements.

3-132

Strobe Messages Guide

System Action:

Strobe initialization terminates.

User Response: Bring up a Strobe Version release environment and issue the SEND,QUIT command against all active requests. If Strobe Version release is not available, stop the active measurement requests. If you cannot stop these measurement requests, initialize the new version of Strobe with a different version letter and a different SVC. STR6426E SIGN FOR THE TERMDATE PARAMETER IS INCORRECT

Explanation: The sign for the TERMDATE parameter is either incorrect or omitted. The TERMDATE parameter sign must be an F. System Action: Strobe session manager does not initialize.

User Response: Ensure that the TERMDATE parameter sign is an F. If the problem persists, contact Compuware Customer Support. STR6427W BLKSIZE WAS NOT SPECIFIED IN THE STROBE PARAMETER DATASET A value for BLKSIZE was not entered in the Strobe parameter dataset. Session Manager sets the BLKSIZE parameter to 8192 and continues

Explanation: System Action: initialization.

User Response: Update the Strobe parameter dataset to specify a value for BLKSIZE between 8192 and 32760. STR6428E STROBE FOR UNIX SYSTEM SERVICES IS NOT SUPPORTED ON SYSTEM sysname

Explanation: Strobe cannot process a request to display OS/390 UNIX System Services processes because Strobe for UNIX System Services is not installed on system sysname. System Action: User Response: programmer. STR6429W Strobe does not complete your request. To install Strobe for UNIX System Services, notify the Strobe system

UNIX SYSTEM SERVICE uss_routine RETURNED RC=rc RSNC=rsnc

Explanation: The OS/390 UNIX System Services routine uss_routine returned an error while processing a request. The UNIX System Services return code is rc; the UNIX System Service reason code is rsnc. System Action: Strobe terminates the request.

User Response: Refer to the IBM OS/390 UNIX System Services Messages and Codes manual to interpret the return codes rc and reason codes rsnc. STR6430W OPERATING SYSTEM LEVEL ON SYSTEM IS level NEEDS MINIMUM V02R06M00

Explanation: The display process function requires functionality level introduced in OS/390 Version 2 Release 6. System Action: Strobe terminates the request.

User Response: To upgrade your operating system to OS/390 Version 2 Release 6, notify your Strobe system programmer. STR6431W THE SESSION MANAGER USER ID IS NOT DEFINED TO THE SECURITY PRODUCT

Explanation: The Strobe session manager user identification does not have access to the systems security product. System Action: functions. User Response: STR6432W Strobe terminates the request to access OS/390 UNIX System Services Notify the Strobe system programmer.

SESSION MANAGER DOES NOT HAVE ACCESS TO SUPERUSER AUTHORITY The Strobe session manager user identification does not have SUPERUSER

Explanation: authority.

System Action: Strobe terminates the request to access OS/390 UNIX System Services process data. User Response: Notify the Strobe system programmer.

Messages Produced by Strobe

3-133

STR6433E

MEASUREMENT OF BPXBATCH RESTRICTED. CONTACT COMPUWARE

Explanation: Strobe cannot measure the BPXBATCH utility because you did not apply a program temporary fix (PTF) for IBM APAR OW38618 to your operating system. System Action: Strobe does not complete your measurement request. Your request remains in active initializing status. User Response: Delete your measurement request. Contact IBM or Compuware Customer Support to obtain the PTF for IBM APAR OW38618 that is compatible with your operating system. STR6434E QUEUED MEASUREMENT OF SPAWNED OR FORKED ADDRESS SPACE HAS FAILED

Explanation: Strobe implant processing failed because of the problem with the environment. System Action: The job continues to run. The request is marked complete, but measurement has failed. User Response: STR6435I Resubmit the measurement request.

USING LOCAL SYSTEM LICENSE DATA

Explanation: Strobe license management data is refreshed with the local system license data. System Action: User Response: STR6436E Strobe continues processing. None required.

LICENSE VERIFICATION FAILED RETURN CODE rc REASON CODE erc

Explanation: The Strobe base license is invalid for the reason specified by return code rc and error reason code erc. Strobe writes the explanation of the failure to the Strobe Log. System Action: All options are marked unlicensed and Strobe does not initiate new measurements. At initialization, Strobe stops processing. User Response: assistance. STR6436W Contact Compuware License Management System Customer Support for

LICENSE VERIFICATION FAILED RETURN CODE rc REASON CODE erc

Explanation: The Strobe base license is invalid for the reason specified by return code rc and error reason code erc.

Note: You may have entered the warning period for your current license. Ignore this message if you have already requested a new license.
System Action: All options are marked unlicensed and Strobe does not initiate new measurements. At initialization, Strobe stops processing. User Response: Contact the License Management System customer support group if the rc and erc are one of the following:

If rc = 4 and erc = 566, 571, 577, 582, 590, 591, 592, or 593 If rc =8 and erc = 562, 563, 564, 567, 568, 569, 573, 574, 575, or 578 Otherwise, contact Compuware Customer Support for an explanation of the return codes and error reason codes.
STR6437I LMRREFRESH {COMPLETED | IN PROGRESS | FAILED} ON SYSTEM sysname

Explanation: This message appears in response to a LMREFRESH command you issued or an internal LMREFRESH. The message indicates one of the following statuses:

COMPLETED the refresh completed successfully on the system sysname. IN PROGRESS at present a refresh is already being driven on system sysname. FAILED an invalid Strobe license was found on system sysname or, in a sysplex, Strobe was unable to send a license data request to system sysname.
System Action: In a sysplex, Strobe will use the license data from all systems that responded. User Response: If the Strobe base license is invalid, contact Compuware Customer Support. In a sysplex, this message may indicate sysplex or storage availability problems.

3-134

Strobe Messages Guide

STR6438I

LICENSE DATA UNAVAILABLE FROM SYSTEM sysname

Explanation: Strobe is unable to obtain license data from system sysname in a sysplex environment. System Action: Strobe continues processing license data for those systems from which it can obtain it. User Response: None required. This message, however, may indicate problems with the sysplex environment that warrant further investigation. STR6439I GLOBAL LICENSE DATA {REFRESHED | NOT REFRESHED} ON SYSTEM sysname Strobe either has or has not obtained license data from system sysname. Strobe processes license data for those systems from which it is available. None required.

Explanation: System Action: User Response: STR6440E

UNABLE TO OBTAIN STORAGE FOR purpose Strobe is unable to obtain storage for the purpose identified in purpose. Strobe terminates if the purpose is LICENSE MANAGEMENT CALL.

Explanation: System Action:

User Response: Configure your Strobe environment so that Strobe can obtain 6144 bytes of subpool 1 storage. STR6441E INVALID LICENSE CONFIGURATION: text

Explanation: Strobe license management has detected the invalid license combination described in text. System Action: All options are marked unlicensed and Strobe cannot initiate new measurements. At initialization, Strobe stops processing. User Response: STR6442E Contact Compuware Customer Support.

ALLOCATION FOR LICENSE MANAGEMENT SUBSYSTEM ddname FAILED The dynamic allocation of ddname provided in the parameter library LMSS Strobe will continue processing using the default license subsystem. Correct the dynamic allocation failure and restart Strobe.

Explanation: failed. System Action: User Response: STR6443E

INVALID LMSS VALUE SPECIFIED

Explanation: The value specified in the Strobe parameter library member for the LMSS parameter is invalid. The value can be either blank or specified as follows: CWSB in the first four characters and the name of the license management subsystem in the second four characters. When the value is blank, Strobe uses the primary default license management subsystem. System Action: User Response: member. STR6444W OPTION Strobe initialization fails. Correct the value specified for LMSS in your Strobe parameter library

CICS OPTION {CAPTBUFF| DSSIZE} IGNORED; INVALID WITHOUT RLI AND/OR TRAN

Explanation: If you specify a CICS option of either CAPTBUFF or DSSIZE, you must also specify RLI, TRAN, or both RLI and TRAN. System Action: User Response: Strobe continues processing without the option CAPTBUFF or DSSIZE. None required.

STR6445I ISSUE AN MVS CANCEL COMMAND TO STOP STROBE AND END ACTIVE REQUESTS AND USERS Explanation: Strobe cannot execute the STOP command that you issued because users or requests are active on the system. System Action: Strobe continues to process, and does not execute the STOP command.

Messages Produced by Strobe

3-135

User Response: To use the STOP command, you must first end active measurements and users. If you need to stop Strobe immediately or cannot end active measurements, you may issue the MVS CANCEL command. STR6447E MEASUREMENT SERVICES WAS NOT STOPPED BY AN OPERATOR AND CANNOT BE STARTED BY AN OPERATOR Explanation: An operator START command was issued for STRBMSAS, but the Measurement Services Address Space (MSAS) was not stopped via an operator STOP command. Measurement Services has failed or been stopped internally. System Action: User Response: Strobe continues processing. Measurement Services are not restarted. None

STR6448E {MEASUREMENT SERVICES INITIALIZATION FAILED| MEASUREMENT SERVICES RESTARTS REPEATEDLY FAILING} RETURN CODE=<return code> REASON CODE=<reason code> -orExplanation: If the message reads Measurement Services initialization failed, Strobe is unable to start Measurement Services during Strobe initialization. The reason and return code come from the ASCRE macro. If the messages Measurement Services Restarts Repeatedly failing, Strobe has attempted to restart the Measurement Services Address Space (MSAS) 3 times in the last 15 minutes. System Action: Strobe initialization failed. Once Strobe is initialized, Strobe does not attempt to restart Measurement Services User Response: During Strobe initialization, fix the problem and restart Strobe. After Strobe is initialized, no response is required. To restart Measurement Services in this situation, stop and restart Strobe. STR6449E NAME/TOKEN {CREATE|DELETE} FOR SESSION MANAGER PAIR FAILED, RETURN CODE=<return code> Explanation: failed. System Action: User Response: The NAME/TOKEN CREATE or DELETE for the Strobe NAME/TOKEN pair Processing continues. None required.

STR6452W {AUTOCANDIDATE | FAULT MANAGER | AUTOMEASURE} IS INVALID WITHOUT {AUTOMONITOR | AUTOSTROBE}. {SETTING FAULT_MANAGER=NO|SETTING AUTOMEASURE=NO}

This message appears in the following forms: AUTOCANDIDATE IS INVALID WITHOUT AUTOMONITOR. SETTING AUTOCANDIDATE=NO
Explanation: Strobe installation parameters specified that AutoStrobe should not be active (AUTOSTROBE=NO). AutoStrobe monitoring must be active on the system, where this instance of Strobe is being initialized. System Action: Strobe continues to initialize, but there will be no AutoStrobe monitoring.

FAULT MANAGER IS INVALID WITHOUT AUTOSTROBE. SETTING FAULT_MANAGER=NO


Explanation: Strobe was installed with FAULT_MANAGER=YES in the Strobe parameter dataset, requesting that Abend-AID Fault Manager be notified, but AutoStrobe is not licensed. System Action: Strobe continues to initialize, but will not send notification to the AbendAID Fault Manager.

AUTOMEASURE IS INVALID WITHOUT AUTOSTROBE - SETTING AUTOMEASURE=NO


Explanation: AUTOMEASURE=YES is specified in the installation parameter dataset, but AutoStrobe is not licensed. System Action: initialize. User Response: The AUTOMEASURE parameter is set to NO, and Strobe continues to Notify the Strobe system programmer.

3-136

Strobe Messages Guide

STR6453E

AUTOMONITOR IS INVALID WITHOUT AUTOSTROBE. SETTING AUTOMONITOR=NO

Explanation: AUTOSTROBE=YES was specified in the ALLOCATE member, but Strobe is not licensed for AutoStrobe. System Action: User Response: STR6454E AutoStrobe is disabled. To use AutoStrobe, contact Compuware to obtain a license for it.

AUTOMONITOR IS INVALID WITHOUT STRAUTO

Explanation: AUTOSTROBE=YES was specified in the ALLOCATE member, but the STRAUTO parameter for the AutoStrobe dataset name is not specified. System Action: User Response: STR6455E nnnn Session Manager initialization fails. Specify a value for STRAUTO in the ALLOCATE member.

NEW AUTOMONITOR REQUEST NOT ADDED, {REDUNDANT|DUPLICATE} OF REQUEST

Explanation: An ADD request was issued for an AutoStrobe monitor request. A match is found if both requests are AutoStrobe monitor requests with the same job name, program name step and proc names, and system. If the message reads REDUNDANT, SYSTEM=*ALL was specified on either the existing request and the ADD. If the message reads DUPLICATE, the same system was specified for the SYSTEM parameter on both the existing request and the ADD. System Action: The ADD request is ignored.

User Response: If the existing AutoStrobe monitoring request is adequate, none required. If not, delete the existing request and then ADD the new request. STR6456E AUTOMONITOR IS NOT ACTIVE

Explanation: An AutoStrobe function ADD, DELETE, CHANGE or copy of an AutoStrobe request was issued, but AutoStrobe is not active. System Action: Strobe attempts to process the request, updates it and saves the information to update AutoStrobe when it reactivates. User Response: None required, although you can check why AutoStrobe is inactive.

STR6457W AUTOMONITOR PARAMETERS REQUIRE AUTOSTROBE - IGNORING AUTOMONITOR PARAMETERS Explanation: A Strobe user issued an ADD request that contains AutoStrobe parameters, but AutoStrobe is either not authorized or was not specified on the request System Action: AutoStrobe parameters on the request are ignored.

User Response: If you want to make the ADD request an AutoStrobe monitored request, delete the original request and re-issue the ADD request with the correct AutoStrobe requirements. STR6458E FAILURE TRIGGERING MEASUREMENT FOR AUTOMEASURE | AUTOMONITOR TEMPLATE nnnn - TEMPLATE NOT FOUND

This message appears in the following forms: FAILURE TRIGGERING MEASUREMENT FROM AUTOMEASURE TEMPLATE <nnnn > - TEMPLATE NOT FOUND
Explanation: An AutoMeasure measurement was requested, but Strobe could not find the AutoMeasure template to clone the request. System Action: The AutoMeasure measurement request is not added; however, Strobe processing continues. User Response: Contact Compuware Customer Support.

FAILURE TRIGGERING MEASUREMENT FROM AUTOMONITOR TEMPLATE <nnnn > - TEMPLATE NOT FOUND
Explanation: AutoStrobe requested that a measurement be initiated for AutoStrobe monitored request nnnn, but the monitored request no longer exists.

Messages Produced by Strobe

3-137

System Action: User Response:

The AutoStrobe monitored request is not added. None required.

STR6460E COMMAND REJECTED - STROBE INTERFACE REQUIRED FOR AUTOMONITOR {ADD|CHANGE|DELETE} Explanation: An ADD, CHANGE or DELETE command was issued for an AutoStrobe request from other than the Strobe/ISPF interface. System Action: User Response: The command is ignored. Use the Strobe/ISPF interface to issue AutoStrobe commands.

STR6462E STROBE SQL AGENT WAS NOT STOPPED BY AN OPERATOR AND CANNOT BE STARTED BY AN OPERATOR Explanation: The operator has issued a START command for the Strobe SQL Agent. However, the Strobe SQL Agent was not stopped by an operator, and therefore an operator START command is not permitted. System Action: Strobe does not process the request.

User Response: None required. Under this circumstance, to restart the Strobe SQL Agent, you must stop and restart the Strobe session manager. STR6463I STROBE SQL AGENT text

The Strobe SQL agent could not be initialized because of text: INITIALIZATION FAILED RETURN CODE=xx, REASON CODE=yy
Explanation: The Strobe SQL Agent failed to initialize. The return code xx and reason code yy are those from the MVS ASCRE macro. System Action: Strobe initialization continues without the Strobe SQL Agent.

User Response: Contact Customer Support to determine why the Strobe SQL Agent initialization is failing.

STARTUP PROCEDURE FAILURE


Explanation: System Action: The Strobe SQL Agent startup procedure is failing. Strobe initialization continues initialization without the Strobe SQL Agent.

User Response: Determine why the Strobe SQL Agent startup procedure is failing. Under this circumstance, to restart the Strobe SQL Agent, you must stop and restart the Strobe session manager.

RESTARTS REPEATEDLY FAILING


Explanation: System Action: The Strobe SQL Agent has failed three times within a 15-minute period. Strobe stops trying to restart the Strobe SQL Agent.

User Response: Determine why the Strobe SQL Agent startup procedure is failing. The only way to restart the Strobe SQL Agent in this situation is to stop and restart the Strobe Session Manager. STR6464I EXISTING STROBE SQL AGENT BEING USED Strobe initialization found an existing Strobe SQL Agent. Strobe uses the exiting Strobe SQL Agent and does not start another. None required.

Explanation: System Action: User Response: STR6465I

STROBE SQL AGENT INITIALIZATION COMPLETE The Strobe SQL Agent initialized successfully. Strobe SQL Agent processing begins. None required.

Explanation: System Action: User Response:

3-138

Strobe Messages Guide

STR6466I

STROBE SQL AGENT IS INVALID WITHOUT DB2

Explanation: The Strobe parameter library specifies SSA=YES. However, this system does not have a valid Strobe for DB2 license. System Action: Strobe SQL Agent is set to NO.

User Response: None required. To use the Strobe SQL Agent, Strobe for DB2 must be licensed and installed. STR6471E REQUEST <request number> IS NOT THE AUTOMEASURE TEMPLATE. INVALID DELETE COMMAND Explanation: A DELETE command with TYPE=AUTOMEAS|AUTOMEASURE was issued for a request that is not the AutoMeasure template. System Action: User Response: STR6472I The AutoMeasure template is not deleted. Enter the request number for the AutoMeasure template.

AUTOMEASURE TEMPLATE CREATED - REQUEST <request #>

Explanation: Upon initialization, Strobe checks if the AutoMeasure template exists. If one does not exist, Strobe creates the AutoMeasure template. Strobe will do so only if AutoStrobe is licensed and the AUTOMONITOR and AUTOMEASURE installation parameters are set to YES in the parameter dataset. System Action: User Response: STR6479W Strobe creates an AutoMeasure template. None required.

CVU IS NOT A SESSION REQUESTER CVU

Explanation: During shutdown, Strobe found a CVU pointing to an address space that was no longer a Session Requester address space. System Action: User Response: Strobe deletes the CVU. None required.

STR6480I ATTACH FILTER IDENTIFIED PROGRAM xxxxxxxx BEING ATTACHED; xxxxxxxx IS ON THE EXCLUDEAQ LIST Explanation: Strobe detected program xxxxxxxx beginning to execute. This program is on the list specified to the EXCLUDEAQ installation parameter in the parameter dataset. EXCLUDEAQ specifies programs for which an Add Queued measurement request will not be permitted. System Action: If there is an Add Queued request for this program, Strobe will not initiate a measurement for it. User Response: To measure the program, do one of the following:

Issue an Add Active request for the program while it is executing. Remove the program from the list specified to the EXCLUDEAQ parameter.
STR6482 ADD QUEUED UNABLE TO OBTAIN ASID ENQUEUE FOR ASID=xxxx

Explanation: During initialization of an Add Queued request, Strobe could not obtain the enqueue on the ASID. System Action: The measurement request fails.

User Response: Delete any active AutoStrobe requests for the specified job/stepname and resubmit the measurement request. STR6483E @@PCMSAS CALL RECEIVED RC xxxx A call to the @@PCMSAS service failed for the reason specified in the return The @@PCMSAS function is not executed and AutoStrobe does not process Contact Compuware Customer Support.

Explanation: code. System Action: the request. User Response:

Messages Produced by Strobe

3-139

STR6484W {AUTOTRAN|CANDIDATE CREATE} MONITORING REQUEST nnnn BEING SUSPENDED TO ALLOW ADD ACTIVE MEASUREMENT Explanation: A measurement is starting in an address space in which there is an active AutoStrobe transaction monitoring or an AutoStrobe create candidates request. System Action: proceed. User Response: Strobe stops the active AutoStrobe request and allows the measurement to None required.

Additional Strobe Messages


STR6800I DSN=dataset name Explanation: This message identifies the dataset related to the preceding message. If it is a sample dataset, dataset name is in the format prefix.jobname.ssssdddd [.suffix]. System Action: User Response: STR6801I See the preceding message. See the preceding message.

STROBE SAMPLE DATA SET ALLOCATED VOLSER=volser [EXISTING DATA SET USED]

Explanation: Strobe allocated a sample dataset on the volume identified by volser. EXISTING DATA SET USED appears in this message if an existing dataset is reused. The fully qualified name of the dataset is given in message STR6800I. System Action: User Response: STR6802I Strobe continues processing. None required.

STROBE SAMPLE DATA SET DEALLOCATED

Explanation: Strobe allocated and cataloged a sample dataset. It can be used to produce a Strobe Performance Profile. The fully qualified name of the dataset is given in message STR6800I. System Action: User Response: STR6803S Strobe completes measurement of the sample dataset. None required.

STROBE SAMPLE DATA SET ALLOCATION FAILED - RC=rc; ERC/IRC/RSN=erc/irc/rsn

Explanation: Strobe was unable to allocate a sample dataset. The fully qualified name of the sample dataset is given in message STR6800I. The error reason code is erc, the information reason code is irc, and the SMS reason code is rsn. For an explanation of the codes, see the IBM z/OS MVS Programming Authorized Assembler Services Guide for interpreting DYNALLOC return codes. Note that rsn is applicable only when erc=97xx and otherwise will display as 00000000. System Action: Strobe terminates sampling.

User Response: Submit a new request to initialize a new measurement session. Ensure that the sample dataset name meets all access facility requirements and that a dataset of the chosen name can be written in the address space of the target program. STR6804E STROBE SAMPLE DATA SET DEALLOCATION FAILED - RC=rc; ERC/IRC=erc/irc

Explanation: Strobe was unable to deallocate a sample dataset. The fully qualified name of the dataset is given in message STR6800I.

The error reason code is erc and the information reason code is irc. The sample dataset may not be available for producing a Strobe Performance Profile until the target program has completed execution.
System Action: The Strobe measurement session continues.

User Response: Wait for the target program to complete execution. If you cannot produce a Performance Profile, contact your Strobe system programmer. STR6805E STROBE SAMPLE DATA SET ALLOCATION FAILED - HSM NOT ACTIVE RC=100 Strobe could not allocate a dataset because DFHSM was not active.

Explanation:

3-140

Strobe Messages Guide

System Action: User Response:

Strobe terminates sampling. Resubmit the measurement request after DFHSM becomes active.

STR6806E AN ERROR OCCURRED RETURNING ACTIVE MEASUREMENT SESSION DATA REQUESTED FROM SYSTEM sysname Explanation: Strobe encountered an error while attempting to return the data you requested from the system sysname. System Action: User Response: programmer. Strobe is unable to return the data that you requested. Resubmit the request. If the problem continues, notify the Strobe system

STR6807E AN ERROR OCCURRED FORMATTING ACTIVE MEASUREMENT SESSION DATA RETURNED FROM THE SYSTEM sysname Explanation: Strobe encountered an error while attempting to format the data that you requested from system sysname. System Action: User Response: programmer. Strobe is unable to present the data that you requested. Resubmit the request. If the problem continues, notify the Strobe system

STR6808E TIME OUT CONDITION OCCURRED WHILE PERFORMING requesttype OPERATION FOR REQUEST nnnn Explanation: Because of processing delays related to the target system, the sysplex, or the session manager, request nnnn may not have completed within the required time interval. The type of request (for example Add Active, Add Queued, Status) is indicated by the variable requesttype. If the request type does not operate on a specific request number, then N/A (not applicable) will appear instead of a number. System Action: processing. Strobe is unable to determine the state of request nnnn but continues

User Response: For more information regarding this request, refer to the Strobe log and search on the request number nnnn. If the time out condition is related to processing delays, Strobe follows this message with messages STR6811I and STR6812I. Otherwise, examine the log for additional messages that indicate the state of the session manager. STR6809S STROBE SYSQUEUE DATA SET IS FULL: NEW REQUESTS NOT ALLOWED - THE CONTINUED OPERATION OF STROBE WILL BE SEVERELY IMPAIRED Explanation: All of the allocated extensions for the queue dataset are used. You cannot make any new measurement requests; the overall operation of Strobe is severely limited. You may, however, display and delete requests. System Action: Strobe does not process any new measurement requests.

User Response: Notify the Strobe system programmer. As a possible temporary solution, the system programmer can display and then delete any unwanted requests from the dataset. In some cases, deleting unwanted requests will rectify the situation. To continue processing new requests, contact the Strobe system programmer.

The system programmer needs to clean up and reorganize the file. If a Strobe-XCF group exists, the system programmer must shut down all members of the Strobe-XCF group before attempting to clean up and reorganize the file. For specific instructions, see the Strobe Installation and Customization Guide.
STR6810W ddname DATA SET IS FULL

Explanation: All of the allocated extensions for the Strobe dataset, file ddname, are used. The value for ddname can be SYSMSG or SYSGROUP. File SYSMSG is the Strobe message dataset, which contains messages issued by Strobe and module tracking information. File SYSGROUP is the Strobe request group dataset, which is present when AutoStrobe is installed to contain request groups and their associated request group elements. System Action: Strobe functions requiring SYSMSG or SYSGROUP are unavailable until the space limitation is relieved.

Messages Produced by Strobe

3-141

User Response: Notify the Strobe system programmer to clean up and reorganize the file. If a Strobe-XCF group exists, the system programmer must shut down all members of the StrobeXCF group before attempting to clean up and reorganize the file. For specific instructions, see the Strobe Installation and Customization Guide. STR6811I UNEXPECTED RESPONSE FROM SYSTEM sysname

Explanation: Strobe received a response message that it cannot process from the system sysname. In some cases, the response message is associated with a measurement request from a system that has since timed out and, in that case, is preceded by STR6808E. System Action: Strobe discards the response from system sysname, and follows this message with STR6812I, which contains the discarded message. User Response: Retry the function. The unexpected response may have indicated a time out due to poor performance. But, if the problem persists, notify the Strobe system programmer. STR6812I string address offset data Strobe writes this message to the Strobe log in certain diagnostic situations. Strobe continues processing. None required.

Explanation: System Action: User Response: STR6813W

QRE DATA AND SRE DATA ARE INCONSISTENT FOR REQUEST rrrr

Explanation: The request element for request rrrr is not active. The Strobe request element (SRE), however, identified this request as active. This message appears in the Strobe log only. System Action: Strobe is unable to process the updates to the request because the measurement session for that request has already begun. User Response: None required.

STR6814E COMMUNICATION FAILURE, MESSAGE BROADCAST IS INCOMPLETE - OUT-OF-SYNC CONDITION MAY EXIST Explanation: Strobe sent a message to other members of a Strobe-XCF group. At least one of the members, however, did not receive the message. In some cases, this message indicates that the requests are out of synchronization with other members of a Strobe-XCF group. System Action: At this time, Strobe is not able to determine if the system is still active.

User Response: Notify the Strobe system programmer. The system programmer can determine whether the system is still active by checking the Strobe log, or by issuing the SHOW MEMBERS command. If the system has terminated, no response is necessary. If the system is still active, however, the requests on that system are potentially out of synchronization. In this case, the system programmer must either issue the RESYNC command or stop and restart Strobe. For more information, see the Strobe Installation and Customization Guide. STR6815E END REQUEST TO SYSTEM sysname FAILED

Explanation: Strobe attempted to send a message to another member of the Strobe-XCF group, but was not able to deliver the message to the group member (system sysname). System Action: Strobe is not able to send the message to system sysname. This message is preceded by message STR6806E, which contains the return and reason codes for the crosssystem coupling facility (XCF) that failed (IXCMSGO). Strobe also provides additional diagnostic information for this situation by writing message STR6812I to the Strobe log. User Response: Notify the Strobe system programmer. The system programmer can determine the cause of the failure by referencing the return and reason codes contained in STR6806E, and by viewing the STR6812I message associated with this request in the Strobe log. STR6816W STROBE UNABLE TO PROCESS REQUEST rrrr, DUE TO error

Explanation: Strobe is unable to continue processing request rrrr because it encountered the error identified in error. error can be:

QUEUE READ ERROR. Strobe encountered an error attempting to read the Strobe queue dataset. OPEN ERROR. Strobe encountered an error attempting to open the Strobe queue dataset.

3-142

Strobe Messages Guide

INVALID SRESTAT. Strobe identified an error in the status of a measurement request. BLDACEE ERROR. Strobe encountered an error attempting to build an Accessor Environment Element (ACEE) control block.
System Action: User Response: STR6817W Strobe does not process the measurement request. Notify the Strobe system programmer.

STROBE ENCOUNTERED A DUMMY QRE FOR REQUEST nnnn

Explanation: The new request, request number nnnn, which was added from one of the systems in the Strobe-XCF group, does not contain any measurement request information. It is a dummy request that Strobe uses as a place holder. System Action: User Response: Strobe reads the request but does not update its local work area. Contact Compuware Customer Support.

STR6818W REQUEST nnnn NOT QUEUED ON SYSTEM sysname - INSUFFICIENT ACCESS AUTHORITY Explanation: Request nnnn is not queued on system sysname because you are not authorized to measure the job on the system. System Action: If the job specified in request nnnn executes on system sysname, it will not be measured. User Response: To run a Strobe measurement request on system sysname, the Strobe system programmer or security administrator must grant you access to the system in the security data base for that system. STR6819W STROBE IS NOT LICENSED ON THIS PROCESSOR TYPE - CONTACT COMPUWARE CORPORATION FOR LICENSING INFORMATION Explanation: Strobe is not licensed for the type of processor on which you attempted to run Strobe. System Action: Strobe does not operate in this environment.

User Response: For more information about running Strobe on this type of processor, contact Compuware Corporation. STR6820W SR/SM TIMER SET FAILED. STIMERM RC = rc

Explanation: Strobe was unable to set the session requester/session manager timer. IBMs STIMERM service issues a return code of rc. System Action: Strobe will continue processing but because the SR/SM Timer is not set, in the event of a failure, Strobe will not follow normal recovery procedures. User Response: Refer to the documentation for IBMs STIMERM macro to determine the meaning of the return code. Check the Strobe log for messages and, if necessary, notify the Strobe system programmer. STR6821E CVU NOT FOUND FOR <jobname> IN <SMCA|SMCL>

Explanation: A call was made to the Strobe SVC by a component that has not logged in to Session Manager. System Action: User Response: STR6822E The call was aborted. Strobe processing continues. Contact Compuware Customer Support.

routine text An internal processing error has occurred in routine routine and is described in Strobe does not process the request.

Explanation: text. System Action:

User Response: This message contains important diagnostic information. Contact Compuware Customer Support.

Messages Produced by Strobe

3-143

STR6823I TOO MANY {JOBS|PROCESSES} TO DISPLAY - FIRST number {JOBS|PROCESSES} DISPLAYED Explanation: You requested to view all active jobs or processes on a specific system. However, the number of active jobs or processes on the system exceeds the maximum number that the cross-system coupling facility (XCF) can pass to Strobe from the specified system. System Action: Strobe displays the maximum number of active jobs or processes that XCF sends from the requested system, identified as number. User Response: STR6824I None required.

SEND OPERATION FAILED; REASON: text The SEND operation failed and the possible reasons are given in text. text can

Explanation: be:

REQUEST NOT FOUND UNKNOWN SEND REQUEST TYPE DELETE INPUT INVALID ACCESS DENIED ACEE BUILD FAILED SEND TIME-OUT.
Strobe does not process the request. Notify the Strobe system programmer.

System Action: User Response:

STR6825W STROBE INITIALIZATION TIMEOUT ON SYSTEM sysname1 WAITING FOR RESPONSE FROM SYSTEM sysname2 Explanation: Strobe initialization processing on system sysname1 sent an XCF signal to Strobe on system sysname2 and did not receive a response within the interval that Strobe allows. System Action: Strobe attempts to send the signal to another member of the Strobe-XCF group. If there are no more members to signal or if the members signaled do not respond, then Strobe will not be initialized on system sysname1 and will issue message STR6245S - STROBE

INITIALIZATION TERMINATED - UNABLE TO COMMUNICATE WITH STROBE-XCF GROUP.


User Response: Notify the Strobe system programmer.

STR6826W FOR STROBE INITIALIZATION ON SYSTEM sysname1, ERROR IN GRPPARMS PROCESSING ON SYSTEM sysname2 RC=rc Explanation: Strobe initialization processing on system sysname1 sent an XCF signal to system sysname2 requesting information, but the routine GRPPARMS issued a return code rc, indicating that it was unable to provide the data. System Action: Strobe attempts on system sysname1 to send the signal to another member of the Strobe-XCF group. If there are no more members to signal or if the members signaled do not respond, then Strobe will not be initialized on system sysname1 and will issue message STR6245S. User Response: Notify the Strobe system programmer.

STR6827W FOR STROBE INITIALIZATION ON SYSTEM sysname1, UNABLE TO PROCESS GRPPARMS DATA FROM SYSTEM sysname2 Explanation: Data that routine GRPPARMS passed from system sysname2 could not be accessed by Strobe on system sysname1. System Action: Strobe attempts to send the signal to another member of the Strobe-XCF group. If there are no more members to signal or if the members signaled do not respond, then Strobe will not be initialized on system sysname1 and will issue message STR6245S. User Response: STR6828E Notify the Strobe system programmer.

routine - ddname operation FAILED: RC vsamrc RSNC vsamrsnc

Explanation: Strobe routine routine attempted to perform an operation operation on ddname ddname. The operation failed with the VSAM return code vsamrc and the VSAM reason code vsamrsnc.

3-144

Strobe Messages Guide

System Action:

Strobe continues processing.

User Response: Notify the Strobe system programmer. The system programmer can investigate the problem and clean up and reorganize files if necessary. STR6829I TRIGGER REQUEST nnnn AND ANY RELATED REQUESTS WILL BE DELETED

Explanation: As requested, Strobe will delete the trigger request, identified by nnnn, for a concurrent set. Because you are deleting the trigger request, any related requests in the concurrent set will also be deleted. STR6141I will confirm the deletions. System Action: User Response: STR6830I Strobe processes the request. None required.

RELATED REQUEST nnnn WILL BE DELETED

Explanation: Because you deleted the trigger request for a concurrent set, all of the related requests will be deleted. This message will occur for each related request, listing each related request individually and identifying the request by its request number nnnn. STR6141I will confirm the deletions. System Action: User Response: Strobe processes the request. None required.

Messages Returned by the Migration Utility


STR6831S NEITHER SYSQUEUE NOR SYSGROUP ALLOCATED, MIGRATION TERMINATED Neither of the required input datasets is allocated. The migration utility terminates. Explanation: System Action:

User Response: Verify that the JCL is correct and that it points to the correct input dataset names. If you need assistance, contact Compuware Customer Support. STR6832S ddname NOT ALLOCATED, MIGRATION TERMINATED

Explanation: Because the dataset referred to by ddname ddname is not allocated, the migration was terminated. System Action: User Response: STR6833S The Strobe migration utility terminates. Verify that the output datasets are allocated and that the JCL is correct.

ddname DATA SET NOT EMPTY, MIGRATION TERMINATED

Explanation: Because the dataset referred to by ddname ddname is not empty, it will not be used in the migration. The migration is terminated. System Action: User Response: STR6834S The migration utility terminates. Allocate a new dataset to be used in the migration.

ddname fnct ERROR, RC=rc RSNC=rsnc

Explanation: VSAM returned an error while processing a request for the dataset referred to by ddname ddname while performing function fnct. The VSAM return code is rc; the VSAM reason code is rsnc. System Action: The migration utility terminates.

User Response: Look up the return codes and reason codes in the DFSMS/MVS Macro Instructions for Data Sets manual. If you need assistance, contact Compuware Customer Support. For diagnostic purposes, save the snap dump. STR6835E ddname error reason - SYSTEM = system SRE = sre nnn

Explanation: The dataset referred to by ddname ddname encountered the error described in error reason. The system is system and the Strobe request element number is sre nnn. System Action: Strobe does not process the record in error but continues processing other records in the dataset.

Messages Produced by Strobe

3-145

User Response: If you need assistance, contact Compuware Customer Support. For diagnostic purposes, save the snap dump. STR6836I ddname DATA SET SUCCESSFULLY MIGRATED FROM RELEASE vrn1 TO RELEASE vrn2

Explanation: Strobe successfully migrated the dataset referred to by ddname ddname from version release number vrn1 to version release number vrn2. System Action: User Response: STR6837W The migration utility completes successfully. None required.

ddname DATA SET MIGRATED FROM RELEASE vrn1 TO REPLACE vrn2 RC = rc

Explanation: Strobe migrated the dataset referred to by ddname ddname from version release number vrn1 to version release number vrn2 with a return code of rc. System Action: The migration utility completes with errors, which are documented in additional messages. User Response: STR6838W If you need assistance, contact Compuware Customer Support.

ddname DATA SET EMPTY The migration utility found an input dataset to be empty. The migration utility continues processing other datasets.

Explanation: System Action:

User Response: Verify that the JCL is pointing to the correct input datasets and rerun the migration utility. STR6839S ddname MIGRATION FROM RELEASE rel NOT SUPPORTED BY UTILITY VERSION vrn

Explanation: The dataset referred to by ddname ddname is at a release level rel that is not supported by the current level of the migration utility, vrn. System Action: The migration utility terminates.

User Response: Verify the JCL, and check that you are executing the latest version of the migration utility. STR6840S INTERNAL PROCESSING ERROR - error reason The migration utility encountered the internal processing error described in The utility terminates. Contact Compuware Customer Support. For diagnostic purposes, save the

Explanation: error reason. System Action: User Response: snap dump.

STR6841E ddname GROUP PROCESSING ERROR: nnn ELEMENT RECORDS EXIST, xxx EXPECTED GRPOWNER = grpowner GROUP = groupname Explanation: The migration utility detected an error processing the dataset referred to by ddname ddname. Strobe expected xxx element records in group groupname. However, nnn element records actually exist. The group owner is given in grpowner. System Action: The utility does not migrate any of the records in the group that experienced the error but continues processing the next group of records. User Response: If you cannot determine the cause of this problem, contact Compuware Customer Support. For diagnostic purposes, save the snap dump. STR6842E ddname error reason - GRPOWNER = grpowner GROUP = groupname ELEMENT = element

Explanation: The migration utility encountered an error while processing element element in group groupname for grpowner grpowner. The dataset is referred to by ddname ddname, and the error is described in error reason. System Action: The utility does not migrate any of the records in the group that experienced the error but continues processing the next group of records. User Response: If you cannot determine the cause of this problem, contact Compuware Customer Support. For diagnostic purposes, save the snap dump.

3-146

Strobe Messages Guide

STR6843S

error text Because of the reason displayed in error text, the migration will be terminated. The migration utility terminates.

Explanation: System Action:

User Response: Verify that the parameter specified is correct and rerun the migration utility. If you require assistance, contact Compuware Customer Support. STR6844I PARM = parmname1 [parmname2, parmname3...]

Explanation: The name of the input parameters is parmname1. Additional input parameters, if present, are given in parmname2, parmname3... System Action: User Response: STR6845I None. None required.

ddname type RECORDS WRITTEN: nnnn

Explanation: The migration utility has successfully written nnnn records of dataset name ddname and type type. System Action: User Response: STR6846I None. None required.

ddname DATA SET SUCCESSFULLY COPIED The migration utility successfully copied dataset ddname. None. None required.

Explanation: System Action: User Response: STR6847S

ddname NO RECORDS FOUND error reason

Explanation: The migration utility found no records for dataset name ddname because of the error described in error reason. System Action: Strobe does not process the request.

User Response: Verify that you entered the correct combination of parameters. You can use the LIST parameter to list the contents of the QUEUE and Group datasets. STR6848S MIGRATION FOR RELEASE rel NOT SUPPORTED BY UTILITY VERSION vrn

Explanation: The current version of the Strobe migration utility, vrn, does not support migration from or to release rel. System Action: The migration utility does not process the request.

User Response: You either used an out-of-date version of the migration utility or specified an incorrect release number. Correct the error and resubmit the request. STR6849I DATA SET ONLY COMPLETED REQUESTS WILL BE MIGRATED WHEN CREATING A TEST QUEUE

Explanation: The Strobe migration utility will migrate only completed requests when migrating to a test queue dataset. System Action: User Response: None. None required.

STR6850S STROBE MIGRATION TERMINATED, TARGET RELEASE xxxx IS OLDER THAN THE SOURCE RELEASE yyyy Explanation: The Strobe release xxxx designated as the target of a migration (OUTREL) was more recent than release yyyy, which was designated as the source of the migration (INREL). This message is preceded by STR6844I, which specifies the pertinent parameters. System Action: The STRBCMIG program terminated without attempting the migration.

User Response: Correct the input parameters in the JCL used to initiate the migration utility.

Messages Produced by Strobe

3-147

STR6851E MIGRATION FUNCTION TO SAME RELEASE LEVEL NOT SUPPORTED. USE COPY FUNCTION OF STRBCMIG. Explanation: The Strobe release designated as the target of a migration (OUTREL) was the same as the release designated as the source of the migration (INREL). The migration function applies only to generating queue and group datasets for releases that are newer than the release of the source datasets. System Action: The STRBCMIG program terminated without attempting the migration.

User Response: Change the primary input parameter (the PARM=function) to COPY, make sure that you specify the other parameters required with COPY, and resubmit the migration utility program. STR6853I IRB TIMER NOT SET

Explanation: The Strobe IRB (Interruption Request Block) initial implant process attempted to set a timer which failed to set. System Action: MVS has encountered an internal problem with Strobes timer request. Strobe processing continues anyway. User Response: Notify the Strobe system programmer. If the problem persists, contact Compuware Customer Support. STR6854I IRB TIMER EXPIRED

Explanation: Strobe could not implant into the address space within a fixed time interval (5 second default) because MVS marked the job as non-dispatchable. Strobe failed to implant in the target address space. System Action: Strobe aborts the implant process. The system or job may be too busy to allow Strobe into the address space. However, sometimes this will be resolved by retrying the job. User Response: If retrying does not resolve the issue, notify the Strobe system programmer. The default interval is a 5 second wait period before the IRB timer expires. If this is insufficient, the MAINTP1 parameter may be set to provide a longer wait time interval. MAINTP1 may be changed from zeros (the default) to 00000400 which sets the wait time to 30 seconds, or to 00000200 which sets the wait time to 60 seconds. You will need to recycle Strobe in order to re-read the parameter. STR6855I IRB HAS STARTED BUT NOT COMPLETED

Explanation: The Strobe initial implant processing under an IRB (Interruption Request Block) did not complete. System Action: Strobe most likely will abort the implant process. The system or job may be too busy to allow Strobe into the address space. However, sometimes this will be resolved by retrying the job. User Response: If retrying does not resolve the issue, notify the Strobe system programmer. The default interval is a 5 second wait period before the IRB timer expires. If this is insufficient, the MAINTP1 parameter may be set to provide a longer wait time interval. MAINTP1 may be changed from zeros (the default) to 00000400 which sets the wait time to 30 seconds, or to 00000200 which sets the wait time to 60 seconds. You will need to recycle Strobe in order to re-read the parameter. STR6861I AUTOCICSMAX CANNOT BE GREATER THAN AUTOMAX. SETTING AUTOCICSMAX TO XX Explanation: The AUTOCICSMAX parameter value is greater than the value of the AUTOMAX parameter. User Response: Strobe sets the value of the AUTOCICSMAX parameter to the value of the AUTOMAX parameter. User Response: STR6863W None.

STROBE FOR UNIX SYSTEM SERVICES IS NOT LICENSED

Explanation: Each time Strobe initializes, you will receive this message, if BPXBATCH=YES (default value) in the Strobe parameter dataset, and Strobe for Unix System Services is not licensed. System Action: Strobe sets BPXBATCH=NO and continues to initialize.

3-148

Strobe Messages Guide

User Response: If you do not want to see this message, set BPXBATCH=NO in the parameter dataset. If you want to license Strobe for Unix System Services, contact your Compuware sales representative. STR6867I ORIGINAL BATCH REQUEST nnnn MARKED COMPLETE FOR TARGET JOB jobname

Explanation: For the target job jobname Strobe has marked the original request, request number nnnn, complete because all designated steps were measured or the job has ended. The original request is a template request from which Strobe creates requests for each of the executing steps in this batch measurement. The original request itself is not associated with a measurement session. System Action: User Response: STR6870W None. None required.

BPXBATCH CLONE LIST FOR REQUEST nnnn IS FULL

Explanation: Strobe was measuring a USS application that involved over 20 internal processes. nnnn is the Strobe request number. System Action: Strobe continues to measure all processes that are still active.

User Response: If BPXBATCH is being used to run a script that is process-intensive (i.e., generates more that 20 processes), thenif possiblesplit the script into smaller steps and remeasure using multiple BPXBATCH steps. STR6873E {STEP1 | MULTIPLE STEPS} NOT SUPPORTED FOR USS BPXBATCH Explanation: You submitted an Add Queued request for BPXBATCH or AOPBATCH and specified one of the following for STEP:

STEP1. This value is not permitted. STEP1 is used by IBM as an internal stepname for UNIX System Services. Multiple steps or *ALL. You must specify a single stepname.
System Action: User Response: Strobe does not process the request. Specify a permitted value for STEP and resubmit the request.

STR6875E STROBE USS BPXBATCH EXITS NOT DISABLED BY STROBE; CANNOT BE RE-ENABLED BY STROBE Explanation: The ENABLEUSSX command was issued, but Strobe for Unix System Services has not been disabled. System Action: User Response: None. None required.

STR6875E STROBE USS BPXBATCH EXITS NOT DISABLED BY STROBE; CANNOT BE RE-ENABLED BY STROBE Explanation: The ENABLEUSSX command was issued, but Strobe for Unix System Services has not been disabled. System Action: User Response: None. None required.

STR6876I STROBE USS BPXBATCH EXITS SUCCESSFULLY <DISABLED | RE-ENABLED> Explanation: An operator ENABLEUSSX or DISABLEUSSX command was issued.

System Action: Strobe for Unix System Services successfully enabled or disabled service exits. User Response: None required.

STR6877E INVALID WRITE_SMF120_X PARM; SET PARM WAS=NO TO DISABLE OR SEE STROBE INSTALL GUIDE FOR CRITICAL WRITE_SMF120_X FACTS Explanation: Your site is licensed for Strobe for WebSphere Application Server, and your Strobe parmlib keyword WAS is set to Yes. However, a valid value for the WRITE_SMF120-x parameter as specified in the message text has not been specified. System Action: Strobe will not initialize.

Messages Produced by Strobe

3-149

User Response: If your site does not need to produce Strobe for WebSphere Application Server reports, change the parmlib keyword WAS to NO. If your site does need Strobe for WebSphere Application Server reports, set WRITE_SMF120_x to a valid value and restart Strobe. For information on customizing Strobe for WebSphere Application Server, see the Strobe Installation and Customization Guide. STR6863W STROBE FOR UNIX SYSTEM SERVICES IS NOT LICENSED

Explanation: Each time Strobe initializes, you will receive this message, if BPXBATCH=YES (default value) in the Strobe parameter dataset, and Strobe for Unix System Services is not licensed. System Action: Strobe sets BPXBATCH=NO and continues to initialize.

User Response: If you do not want to see this message, set BPXBATCH=NO in the parameter dataset. If you want to license Strobe for Unix System Services, contact your Compuware sales representative. STR6878W STROBE USS BPXBATCH IS NOT ACTIVE. CANNOT <DISABLE | RE-ENABLE> STROBE USS EXITS. Explanation: An operator ENABLEUSSX or DISABLEUSSX command was issued for Strobe for Unix System Services, but Strobe for Unix System Services exits are not active. System Action: collected. User Response: Strobe continues processing, but no Unix measurement data will be None required.

STR6879W MISMATCH BETWEEN REQUEST NUMBER <request number> AND SMW REQID <swm request ID>, SWM FUNCTION CODE IS <function code>. Explanation: System Action: User Response: STR6880W An error has occurred in internal Strobe processing. The function being processed will be terminated. Contact Compuware Customer Support.

Parameter <parameter name> missing, <action taken>

Explanation: A parameter in the Strobe parmlib was not supplied. Strobe displays the action taken:

"No defaults supplied" "Global Monitor set to NO" "GM_iStrobe set to NO" "GM_Vantage set to NO"
Strobe continues to initialize with degraded function.

System Action:

User Response: Consult the Strobe Installation and Customization Guide for details on setting parameters. Supply the missing parameters.

Messages Returned by the Session Management Facility for AutoStrobe


The session management facility returns the following messages in response to Strobe commands, writing them to the SYSPRINT dataset and to an operators terminal when the request originated there.
STR6900E ENTRIES STARTTIME AND STARTDATE PARAMETERS DO NOT CONTAIN THE SAME NUMBER OF

Explanation: You specified the STARTTIME and STARTDATE parameters on the ADD or SUBMIT operation, but did not specify a matching number of entries for each parameter. You must specify one STARTTIME parameter for each STARTDATE parameter. System Action: Strobe does not process the ADD or SUBMIT request.

User Response: Ensure that you have an equal number of entries for the STARTTIME and STARTDATE parameters and then resubmit the ADD or SUBMIT operation.

3-150

Strobe Messages Guide

STR6901I

ELEMENT jobname ADDED FOR GROUP groupname

Explanation: A new request group element, specified by jobname, has been added to the request group groupname. System Action: User Response: STR6902E Strobe adds the new request group element to the request group. None required.

ADDGRP ERROR - ELEMENT jobname GROUP groupname

Explanation: Strobe may have been unable to save the request (identified by jobname) as a request group element in the request group groupname. System Action: information. User Response: programmer. STR6903I Strobe may not have processed the request. The log contains additional Check the Strobe log for additional messages and notify the Strobe system

ELEMENT jobname CHANGED FOR GROUP groupname

Explanation: You changed one of the request group elements (identified by jobname) in the request group groupname. System Action: User Response: STR6904E Strobe modifies the request group element. None required.

CHANGE ERROR ELEMENT jobname GROUP groupname

Explanation: Strobe may have been unable to modify the request group element (identified by jobname) in the request group groupname. System Action: information. User Response: programmer. STR6905I Strobe may not have processed the request. The log contains additional Check the Strobe log for additional messages and notify the Strobe system

GROUP groupname DELETED

Explanation: Strobe processed a DELGRP operation, which specified that the request group groupname be deleted. System Action: User Response: STR6906E Strobe deletes the request group from the request group dataset. None required.

GROUP groupname NOT FOUND

Explanation: Strobe cannot find any request group that matches the name specified in groupname. Either you specified the wrong request group name, or the request group does not exist. System Action: User Response: request. STR6907E Strobe does not process the request. If you specified the incorrect request group name, correct and resubmit the

DELETE ERROR FOR GROUP groupname [ELEMENT jobname]

Explanation: Strobe may have been unable to process a Delete operation. The request group specified is groupname. If the delete specified elements in a request group, those elements are identified by jobname. System Action: Strobe may not have deleted the request group element. The log contains additional information. User Response: programmer. STR6908I Check the Strobe log for additional messages and notify the Strobe system

ELEMENTnnn DELETED IN GROUP groupname

Explanation: Strobe processed a DELGRP operation and deleted the request group element(s) that were specified by sequence number nnn from the request group specified in groupname.

Messages Produced by Strobe

3-151

System Action: User Response: STR6909E

Strobe deletes the request group element. None required.

ELEMENT jobname IN GROUP groupname NOT FOUND

Explanation: Strobe cannot find any request group element that matches the name specified in job jobname and group groupname. Either you specified the wrong request group element name, or the request group element does not exist. System Action: Strobe does not process the request.

User Response: If you specified an incorrect request group element name, correct and resubmit the request. STR6910I {STR6910I|STR6910W | STR6910E| STR6910S} GROUP groupname SUBMITTED, RC=rc

Explanation: The request group specified by groupname has been submitted for processing. The return code is rc. The error severity indicator (I, W, E, or S) depends on the return code. System Action: Strobe processes the submit request.

User Response: None required. If the return code is not zero, check the Strobe log for additional messages. STR6911E GROUP SUBMISSION ERROR FOR GROUP groupname

Explanation: Strobe may have been unable to process a SUBMIT operation for the request group groupname. System Action: Strobe may not process the request. The log contains additional information. User Response: Check the Strobe log for messages and resubmit the request. If the problem persists, notify the Strobe system programmer. STR6913I GROUP groupname COPIED TO newgroup

Explanation: You copied the request group groupname, and all of its associated request group elements, to the new request group specified in newgroup. System Action: Strobe creates the new request group and populates it with copies of the request group elements from request group groupname. User Response: STR6914E None required.

GROUP groupname COPY ERROR Strobe may not have been able to copy the request group groupname.

Explanation:

System Action: Strobe may not have processed the request. The Strobe log contains additional information. User Response: programmer. STR6915I Check the log for additional messages and notify the Strobe system

groupname, num of elements, num of subs, credate, last mod date, last sub, grpowner

Explanation: Strobe returns this message in response to a LISTGRP operation. Strobe lists the name of the request group (groupname), the number of request group elements in the request group (num of elements), the number of times the request group has been submitted (num of subs), the date the request group was created (credate), the date that the request group was last modified (last mod date), the last time the request group was submitted (last sub), and the group owner (grpowner) of the person who created the request group. System Action: User Response: Strobe continues processing. None required.

STR6916I REQUEST nnnn CLONED FROM xxxx ORIGINAL REQUEST yyyy {AUTOMEASURE|AUTOMONITOR|BPXBATCH} Explanation: Strobe has created a measurement request based on one of the following:

An ADD request that specified a list of job steps to be measured using the PROGRAM, STEP, NUMBER parameters

3-152

Strobe Messages Guide

An ADD request that specified that all steps of the job be measured using the *ALL parameter An ADD request that contained a schedule An ADD request that specified AutoMonitor and the criteria for AutoMonitor have been met A new or changed load module on the AutoMeasure list has been executed When you submit a single measurement request to measure multiple steps of a job, Strobe initiates a measurement session for each job step you specified. When the first measurement session is initiated, Strobe creates subsequent measurement sessions by copying or cloning the previous measurement request. This message displays the number of the new request (nnnn) as well as the numbers of the original measurement request (yyyy) and the previous request from which the measurement parameters were cloned (xxxx). This message appears for both the original request and the cloned request.
System Action: Strobe uses the parameters specified in the ORIGINAL REQUEST (yyyy) to create the subsequent or cloned request (nnnn). User Response: STR6917I None required.

CLONING OF REQUEST jobname nnnn TERMINATED

Explanation: Strobe issues this message when it has encountered an error in cloning target job jobname for Strobe request number nnnn. This message accompanies STR6106E. System Action: requests. User Response: STR6918I Strobe processes the current request but does not process subsequent None required.

MEASURING USS COMMAND: <command name>

Explanation: A measurement request has been cloned to measure the specified command command name. The command name will be up to 128 bytes long. System Action: User Response: STR6919I Measurement continues. None required.

SSI FUNCTION function {ENABLED | DISABLED}

Explanation: The Strobe subsystem function function is either enabled or disabled. Strobe uses subsystem function function to perform end-of-task processing or delete processing for multistep requests. System Action: User Response: STR6921I None. None required.

NNNN ENTRIES REMOVED FROM SCHEDULE - DATE AND TIME LESS THAN CURRENT

Explanation: You submitted a measurement request or a request group with one or more invalid entries for the STARTDATE and the STARTTIME parameters. Strobe removes these entries from the schedule. The values for these parameters must be a future date and time. The number of invalid entries is identified by nnnn. System Action: User Response: STR6922E Strobe removes the invalid entries and processes the request. None required.

NO TRIGGER FOUND FOR CONCURRENT SET concurrentname GROUP groupname

Explanation: You designated one or more request group elements in a request group as related requests in a concurrent set, but have not yet specified a trigger request. The concurrent set name is concurrentname and the request group name is groupname. System Action: User Response: Strobe does not create the concurrent set association between the requests. Specify a request group element as the trigger request for the concurrent set.

Messages Produced by Strobe

3-153

STR6923I HALTED

TRIGGER JOB jobname CONCURRENT SET concurrentname NOT ACTIVE, PROCESSING

Explanation: You submitted a request group for processing containing concurrent set concurrentname. The trigger request jobname for the concurrent set is specified as an Add Active request group element. The target job for the trigger request is not currently active. System Action: Strobe does not process the SUBMIT request and deletes the requests.

User Response: Either resubmit the request group when the target job for trigger request jobname is active, or change the trigger request to an Add Queued request group element. STR6924I ORIGINAL MULTISTEP REQUEST nnnn MARKED COMPLETE FOR TARGET JOB jobname

Explanation: For the target job jobname Strobe has marked the original request, request number nnnn, complete because all designated steps were measured or the job has ended. The original request is a template request from which Strobe creates requests for each of the executing steps in this multistep measurement. The original request itself is not associated with a measurement session. System Action: User Response: STR6926I None. None required.

ONLY TWO ENTRIES REMAIN IN SCHEDULE REQUEST nnnn ORIGINAL REQUEST xxxx

Explanation: Only two entries remain for the scheduled measurement request or the scheduled request group. The remaining (deferred) requests are contained in xxxx and are from the original request nnnn. This message alerts you that entries in your scheduled request are about to run out. System Action: Strobe continues processing.

User Response: None required. If you want to continue to measure automatically with Strobe on a schedule, you need to set up another scheduled measurement request. STR6927W INVALID DATE/TIME ENTRIES FOUND IN SCHEDULE. xxxx ENTRIES REMOVED FROM REQUEST [nnnn] Explanation: You submitted a measurement request or a request group for a request with one or more invalid entries for the STARTDATE and the STARTTIME parameters. Strobe removes xxxx entries from the schedule. The values for these parameters must be a future date and time or the current date with a future time. The future time must be at least three minutes in the future from when the system receives the request. If present, the request number is nnnn. System Action: User Response: Strobe removes the invalid entries and continues processing. None required.

STR6928E NO VALID DATE/TIME ENTRIES FOUND IN SCHEDULE REQUEST [nnnn] MARKED COMPLETED Explanation: No valid entries for the STARTDATE and the STARTTIME parameters remain in the scheduled request. The values for these parameters must be a future date and time (or the current date with a future time). The future time must be at least two minutes in the future from when the system receives the request. The request is marked completed. If present, the request number is nnnn. System Action: User Response: STR6929I Strobe marks the scheduled request as completed and continues processing. None required.

UNUSED REQUEST nnnn WILL BE DELETED

Explanation: In a multistep measurement request, the step for request nnnn never ran, so the measurement for request nnnn never initiated. This request will be deleted. System Action: User Response: STR6930E Strobe deletes the request. None required.

GROUPNAME PARAMETER MUST BE SPECIFIED FOR THIS REQUEST

Explanation: You specified a SUBMIT operation to submit a request group for processing but did not specify the group name using the GROUPNAME parameter.

3-154

Strobe Messages Guide

System Action: User Response: STR6931I IGNORED

Strobe does not process the request. Resubmit the request using the GROUPNAME parameter.

SCHEDULE PARAMETERS NOT SUPPORTED ON GROUP REQUESTS - PARAMETERS

Explanation: You specified an ADDGRP operation to save a request as a request group element in a request group. However, you have also specified some of the scheduling parameters, such as STARTDATE and STARTTIME. These parameters are not allowed on the ADDGRP operation, because the request is being saved in the group, not submitted for processing. System Action: parameters. Strobe saves the request in the request group, but ignores the scheduling

User Response: None required. If you want to submit the request group with a schedule, use the SUBMIT operation, as described in the Strobe User Guide. STR6932I REQUEST xxxx BEING TERMINATED BY TRIGGER REQUEST nnnn

Explanation: The primary (trigger) request of the concurrent set (nnnn) terminated the related request (xxxx) in a concurrent set. In concurrent set processing, the primary, or trigger, request controls the initiation and termination of all the related requests in the concurrent set. System Action: User Response: STR6933I Strobe marks the requests as completed and continues processing. None required.

ADDGRP FAILED - REQUEST MUST BE AN ADD ACTIVE

Explanation: The Add Group request was unsuccessful. You attempted to specify an Add Queued request group element as a related request in a concurrent set incorrectly. You attempted to enter this request as an Add Queued, but it must be an Add Active. System Action: User Response: group element. Strobe does not process the request. Resubmit the request, ensuring that the request is an Add Active request

STR6934W SUBMIT FAILED FOR RELATED CONCURRENT SET concurrentname GROUP groupname, REQUESTS NOT SUBMITTED Explanation: The SUBMIT operation for concurrent set concurrentname failed. This concurrent set is a member of group groupname. System Action: Strobe terminates all of the related requests in the concurrent set.

User Response: Examine the Strobe log to determine the cause of the failure, correct the problem, and resubmit the request group. STR6935E LIST FAILED FOR GROUP groupname STORAGE UNAVAILABLE RC=rc

Explanation: You attempted to list the elements in the request group identified by groupname. However, Strobe cannot complete the request because of insufficient storage. The return code, rc, holds the contents of register 15 from IBMs GETMAIN macro. System Action: User Response: programmer. STR6936E Strobe does not display the contents of the request group. Check the Strobe log for additional messages and notify the Strobe system

SUBMIT FOR GROUP groupname FAILED MAX REQUESTS WOULD BE EXCEEDED

Explanation: You have attempted to submit the request group, identified by groupname, for processing. However, Strobe could not process the request group because the total number of requests on the Strobe system would exceed the maximum amount specified by the Strobe system programmer at installation time. System Action: User Response: Strobe does not submit the request group. Notify the Strobe system programmer.

Messages Produced by Strobe

3-155

STR6937E NUMBER OF GROUP ELEMENTS NOW EXCEEDS MAX REQUESTS. GROUP groupname CANNOT BE SUBMITTED Explanation: The total number of request group elements in the request group groupname exceeds the maximum number of allowable request group elements. This number is defined as the maximum number of requests allowed on the system. System Action: User Response: Strobe cannot submit the request group for processing. Delete some of the request group elements in request group groupname.

STR6938W SEQUENCE NUMBER EXCEEDS 999 FOR GROUP groupname - GROUP MUST BE RESEQUENCED Explanation: You attempted to add request elements to group groupname. However, the sequence numbers for the request group have already reached 999. As you add elements to a group, Strobe assigns a unique sequence number to each request element. The maximum sequence number that Strobe will assign is 999. You cannot add to the group once Strobe has assigned this number. The sequence numbers associated with each request element within a group do not change even if you delete request elements from the group. For Strobe to supply new sequence numbers, you must first delete some request elements and then copy the group to a new group name. Strobe will then assign new sequence numbers to the request elements. This message is followed by STR6939W. System Action: Strobe will not process the request.

User Response: Delete the unwanted request elements from group groupname and follow the instructions in STR6939W. STR6939W COPY GROUP groupname TO A NEW GROUP

Explanation: To resequence the numbers assigned to request elements in the group, copy the group to a new name. This message is preceded by STR6938W. System Action: User Response: STR6940W Strobe processes the request. Copy groupname to a new group name.

IMPLANT FOR SCHEDULED REQUEST FAILED - REQUEST MARKED COMPLETE

Explanation: Strobe attempted to run a scheduled Add Active measurement request at the dates, times, number of retry intervals, and number of retry attempts that you specified, but Strobe could not find the specified job. Although the term implant refers to the Strobe measurement request in the Strobe address space, this message could be generated by any of the following reasons:

The job that Strobe was to measure never became active. Strobe was not running in the address space. The implant for the measurement was never established.
System Action: Strobe changes the status of the current element from deferred to completed. Strobe was unable to measure this element in the group, however, it will attempt to measure other elements in the group according to the submissions and retry intervals that you specified. User Response: None required. You cannot produce a Performance Profile from the request (even though it is identified as completed) because there is no measurement data. STR6941S STROBE SSI FUNCTION function FAILED PROCESSING JOB jobname AT time date Strobe function function failed while processing job jobname at time time and The subsystem interface becomes disabled. Notify the Strobe system programmer.

Explanation: date date. System Action: User Response: STR6942S

MULTISTEP NOT ALLOWED - AUTOSTROBE NOT INSTALLED ON SYSTEM sysname

Explanation: Strobe cannot process a request to measure multiple steps of a job because the AutoStrobe is not installed on system sysname. System Action: User Response: Strobe will process the first specified job step in the measurement request. None required. To install AutoStrobe, notify the Strobe system programmer.

3-156

Strobe Messages Guide

STR6943S

CONCURRENT NOT ALLOWED - AUTOSTROBE NOT INSTALLED ON SYSTEM sysname

Explanation: Strobe cannot process all measurement requests of a concurrent set because AutoStrobe is not installed on system sysname. System Action: Strobe processes the trigger request of the concurrent set but will not process any related requests. User Response: To install AutoStrobe, contact Compuware Customer Support.

STR6944E NOT AUTHORIZED TO ISSUE commandname COMMAND FOR {OWNER= | NEWOWNER=} username Explanation: You tried to issue an AutoStrobe group processing command commandname for the owner or new owner identified in username. The Strobe security interface determined that you do not have authority to issue this command for groups created by this owner or new owner. System Action: Strobe will not process the request.

User Response: Do not issue this command for username. The Strobe administrator can issue this command for this user. STR6945E SYSGROUP DATASET ERROR, RTN: routine, RC= vsamrc RSNCD=vsamrsnc

Explanation: The session manager encountered an error executing routine routine while accessing the SYSGROUP dataset. The VSAM return code is vsamrc, and the VSAM reason code is vsamrsnc. System Action: User Response: STR6946E groupname Strobe does not process the request. Notify the Strobe system programmer.

MULTIPLE TRIGGERS FOUND FOR CONCURRENT SET concurrentname GROUP

Explanation: You designated more than one trigger request for related requests in a concurrent set. The concurrent set name is identified by concurrentname and the request group name is identified by groupname. System Action: User Response: concurrent set. STR6947E Strobe does not create the concurrent set association among the requests. Specify only one request group element as the trigger request for the

TIMEOUT FOR COMMAND commandname, PROCESSING HALTED RC=rc Command commandname has timed out with return code rc. Strobe may not have processed the command. The log contains additional

Explanation: System Action: information.

User Response: Check the Strobe log for additional information and notify the Strobe system programmer. STR6948W ROUTINE routinename SENSED SESSION MANAGER TIMEOUT ROUTINE COMPLETED SUCCESSFULLY Explanation: This message accompanies STR6947E. Although you received a timed out message for the command, the routine routinename has completed successfully. System Action: User Response: STR6949I Strobe successfully processed the request. Notify the Strobe system programmer.

STROBE ACTIVE FOR <number> ASIDS FOR JOB <jobname> ON SYSTEM <system>.

Explanation: The maximum number of active measurements for jobname on system have been initiated. System Action: Subsequent measurement requests for this jobname will not be initiated until one of the active measurements stops. User Response: None required.

Messages Produced by Strobe

3-157

STR6950W

AUTOMEASURE IS INVALID WITHOUT AUTOMONITOR. SETTING AUTOMEASURE=NO

Explanation: The AUTOMEASURE installation parameter is set to YES, but the AUTOMONITOR installation parameter is set to NO. AutoMeasure requires that the AUTOMONITOR installation parameter be set to YES in the parameter dataset. System Action: The AUTOMEASURE installation parameter is set to NO and Strobe continues to initialize. User Response: YES. STR6951E To activate AutoMeasure, set the AUTOMONITOR installation parameter to

DELETE REJECTED - REQUEST IS AUTOMEASURE TEMPLATE REQUEST

Explanation: A DELETE command has been issued to delete the AutoMeasure template, but TYPE=AUTOMEASURE|AUTOMEAS was not specified in the command. System Action: The DELETE command fails.

User Response: To delete the AutoMeasure template, specify TYPE=AUTOMEASURE|AUTOMEAS in the command. STR6952E CANNOT ADD BLANK TARGET

Explanation: An attempt was made to specify a JAVA targeting request for which the JAVA target type was valid but the actual target name was missing. For example, JAVA=(JAVATGT=('P')) . System Action: The measurement request is failed.

User Response: To specify JAVA targeting, the operand of the JAVATGT= keyword must be of the form JAVATGT=('Xtarget.name') where X is the JAVA target type (see message STR6916E on page 3-151), and target.name is the JAVA entity that corresponds to the specified target type. Examples:
JAVA=(JAVATGT=('Pcom.userwritten.package')) JAVA=(JAVATGT=('CUserWrittenJavaClass')) JAVA=(JAVATGT=('MexecUserSQLQueryMethod'))

STR6953E

Target type must be P,C or M

Explanation: An attempt was made to specify a JAVA targeting request for which the JAVA target type was invalid. For example, JAVA=(JAVATGT=('Ocom.userwritten.package')) . System Action: The measurement request is failed.

User Response: To specify JAVA targeting, the operand of the JAVTGT= keyword must be of the form JAVATGT=('Xtarget.name'). X is the JAVA target type, which must be P, C, or M (that is, Package, Class, or Method). This value must be in uppercase. target.name is the JAVA entity that corresponds to the specified target type. Examples:
JAVA=(JAVATGT=('Pcom.userwritten.package')) JAVA=(JAVATGT=('CUserWrittenJavaClass')) JAVA=(JAVATGT=('MexecUserSQLQueryMethod'))

Messages Returned by Strobe/ISPF


Strobe/ISPF produces the following messages. The short version of each message appears in the ISPF message line at the top right corner of a panel. The long version of the message, shown below the short version, appears when you press the Help function key.
STR7010E INVALID DISPOSITION. THE VALID SAMPLE DATA SET DISPOSITIONS ARE CATLG AND KEEP Explanation: System Action: You selected an invalid dataset disposition. Strobe/ISPF does not process the measurement request.

3-158

Strobe Messages Guide

User Response: Specify either CATLG or KEEP in the DISP field on the Strobe - Add Active Request, Strobe - Add Queued Request, or Strobe - Change Queued Request panel, or on the corresponding Strobe - Batch-Submission panel. STR7013E INVALID JOBNAME. ENTER UP TO 8 ALPHANUMERIC CHARACTERS - THE 1ST MUST NOT BE NUMERIC Explanation: System Action: You specified the JOBNAME field incorrectly. Strobe/ISPF does not process the measurement request.

User Response: Specify a jobname from 1 to 8 alphanumeric or national characters. The first character must be alphabetic or national. STR7014E INVALID SESS. DURATION. SESSION DURATION MUST BE A NUMBER FROM 1 to 1440

Explanation: You specified the SESSION DURATION field incorrectly. This field is used to estimate in minutes the duration of the measurement session. System Action: Strobe/ISPF does not process the measurement request.

User Response: Specify a number from 1 to 1440. If you leave the field blank, Strobe uses the default of 1 minute. STR7015E NUM SAMPLES OUT OF RANGE. NUMBER OF SAMPLES REQUESTED SHOULD BE BETWEEN 1,000 AND 150,000 Explanation: System Action: You specified the NUMBER OF SAMPLES field incorrectly. Strobe/ISPF does not process the measurement request.

User Response: Specify a value between 1,000 and 150,000 or clear the field to accept the Strobe/ISPF default value of 10,000 samples. STR7016E FINAL SESS. ACT. INVALID. FINAL SESSION ACTION MUST BE Q, S, OR C (IF NO CICS DATA COLLECTOR) Explanation: You specified the FINAL SESSION ACTION field incorrectly. This field indicates the action to be taken when the target sample size is reached in the last measurement session.

You cannot specify a final session action of C if the CICS data collector is invoked.
System Action: Strobe/ISPF does not process the measurement request.

User Response: Specify Q to Quit sampling and terminate the request, S to Stop sampling but leave the measurement session active, or C to take no action and continue sampling. If you leave the field blank, Strobe uses the default value of Q for an Add Active request or C for an Add Queued request. STR7018E MSG DS ALLOC FAILURE. RC= rc; ERC/IRC= erc/irc; TEMP DATA SET WITH SSMF MSGS

Explanation: The operating system returned a nonzero return code rc while attempting to allocate a temporary dataset to display the Strobe messages. The error reason code is erc, and the information reason code is irc. System Action: The Strobe log will not display with the Strobe/ISPF Browse Log function or the .CVM command. User Response: Notify the Strobe system programmer.

STR7019E INVALID OPTION/COMMAND. CHECK THE SPECIFICATION IN THE OPTION OR COMMAND FIELD Explanation: You selected an option that the panel does not support or entered a command that is invalid. System Action: User Response: Strobe/ISPF does not process the option or command. Select one of the options listed on the panel or enter a valid command.

STR7020I REQ nnnn {ACTIVE|SUSPENDED|QUEUED|TERMINATED|SCHEDULED} [RC=rc] {A STROBE REQUEST HAS BEEN ADDED FOR jobname|THE STROBE REQUEST WAS TERMINATED FOR jobname} Explanation: You submitted a measurement request. Strobe/ISPF reports the request number (nnnn) and status in the short message field. If the request was submitted successfully, the

Messages Produced by Strobe

3-159

jobname appears in the long message field. Otherwise, the return code appears in the short message field and the appropriate error message appears in the long message field. System Action: User Response: Strobe successfully processed the request and is waiting for the next request. None required.

STR7021E SELECT AN OPTION. OPTION FIELD IS BLANK - SELECT AN OPTION FROM THE OPTIONS ON PANEL Explanation: System Action: User Response: STR7022E You did not specify a processing option for the request. None. Enter the option code in the OPTION field and resubmit the request.

WORK DS ALLOC FAILURE. RC=rc; ERC/IRC=erc/irc; ddname

Explanation: Strobe/ISPF encountered a nonzero return code, rc, while attempting to allocate a work dataset, ddname, for foreground processing. The error reason code is erc and the information reason code is irc. System Action: User Response: Strobe/ISPF cannot allocate the work dataset. Notify the Strobe system programmer.

STR7023E REQUIRED FIELD. PROGRAM NAME OR STEPNAME/STEPNUMBER OR PROCSTEP.STEPNAME REQUIRED Explanation: You identified the target job incorrectly in the PROGRAM or STEP field of the Strobe - Add Queued Request panel. System Action: Strobe/ISPF does not process the measurement request.

User Response: You must specify one or more of the job identification operands: program name, stepname, stepnumber, and procstepname.stepname. Resubmit the request, and specify the job step or program you want to measure.

If SCHEDULE REQUEST is an option on the Strobe - Add Queued panel, AutoStrobe is installed and you can measure multiple steps of a job. To do this, clear the PROGRAM and STEP fields and press Enter. The Strobe - Add Queued Request - Multiple Steps panel will appear. On this panel, you can fill in the program names, step names, or step numbers that you would like to measure. To measure all the steps of a job, specify *ALL in the STEP field or select Option 4 on the Strobe - Add Queued Request - Multiple Steps panel.
STR7024E INVALID PROGRAM NAME. ENTER UP TO 8 ALPHANUMERIC CHARACTERS - THE 1ST MUST NOT BE NUMERIC; LAST CHARACTER MAY BE AN ASTERISK Explanation: System Action: You have entered an invalid program name in the PROGRAM field. Strobe/ISPF does not process the measurement request.

User Response: Specify a program name of 1 to 8 alphanumeric or national characters in the PROGRAM field. The first character must be alphabetic or national. The last character may be an asterisk, which acts as a wildcard. A single asterisk is not valid. STR7025E INVALID STEPNAME. SPECIFY EITHER THE RELATIVE STEP NUM (1-255) OR A VALID STEPNAME Explanation: You entered an invalid step in the STEP field of the Strobe - Add Queued Request panel or you have chosen Option 2 on the Strobe - Add Queued Request - Multiple Steps panel and specified the name of one or more steps or step.procsteps incorrectly. System Action: Strobe/ISPF does not process the measurement request.

User Response: Supply a relative step number between 1 and 255, or a stepname, or a procstepname and stepname. The stepname or procstepname must contain from 1 to 8 alphanumeric characters. The first character must be alphabetic or national. The three national characters are @, #, and $.

If you want to measure multiple steps of a job, clear the PROGRAM and STEP fields and press Enter. This will bring you to the Strobe - Add Queued Request - Multiple Steps panel on which you can fill in the program names, step names, or step numbers that you would like to measure. To measure all the steps of a job, specify *ALL in the

3-160

Strobe Messages Guide

STEP field or select Option 4 on the Strobe - Add Queued Request - Multiple Steps panel.
STR7026E LINES/PAGE OUT OF RANGE. LINES PER PAGE SHOULD BE FROM 45 TO 80

Explanation: You specified an invalid number of lines per page in the LINES/PAGE field. This field controls the number of lines printed on each page of the Performance Profile. System Action: Strobe/ISPF does not process the Performance Profile request.

User Response: Enter a value between 45 and 80 or clear the field to accept the Strobe default of 60. STR7027I JOBNAME MAX NUM OF JOBS SELECTED. TO ADD MORE JOBS REPEAT REQUEST WITH BLANK You chose more than 32 Active jobs from the Active Job Selection List. Strobe/ISPF will process the first 32 jobs selected.

Explanation: System Action:

User Response: To process additional jobs, add the first 32 Add Active requests, clear the JOBNAME field on the last Strobe - Add Active Request panel, and select up to 32 more jobs to process from the Strobe - Active Job Selection List panel. Repeat this process until you have selected all desired jobs. STR7028E STROBE ERROR. STROBE message

Explanation: Strobe detected an error while processing a measurement request. The long message field provides the Strobe message. System Action: Strobe does not process the measurement request.

User Response: To view all the session management facility messages, enter .CVM in the option field or command line, and then notify the Strobe system programmer. STR7029E PROFILE ALLOC ERROR. RC= rc; ERC/IRC= erc/irc; dsname

Explanation: The operating system returned a nonzero return code rc while Strobe/ISPF attempted to allocate a dataset, dsname, for foreground processing of the Strobe Performance Profile. The error reason code is erc and the information reason code is irc. Strobe normally stores a version of the Performance Profile with an 80-character format in this dataset. System Action: request. User Response: STR7030W Strobe does not allocate the dataset or process the Performance Profile Notify the Strobe system programmer.

STROBE WARNING. STROBE message

Explanation: Strobe detected an error and issued this warning message while processing a measurement request. The long message field gives the entire message. System Action: options. User Response: line. STR7031E Strobe processes the measurement request but may not apply all specified To view all the Strobe messages, enter .CVM in the option field or command

INTERNAL ERROR modname info - NOTIFY STROBE SYSTEM PROGRAMMER

Explanation: A Strobe/ISPF module modname encountered an internal error. Information about the error appears in info. This summary includes the return code, if applicable. System Action: User Response: Strobe/ISPF does not perform the requested action. Notify the Strobe system programmer.

STR7032E USE S AS A SELECT CODE. USE S TO THE LEFT OF THE ENTRY TO INCLUDE IT IN YOUR SELECTION LIST Explanation: System Action: User Response: You specified the selection code incorrectly. Strobe/ISPF does not process the request. Use S to select an entry in the list.

Messages Produced by Strobe

3-161

STR7033I

STROBE ENV NOT ACTIVE. STROBE message

Explanation: Strobe is not active. If Strobe issued only one message, it is displayed in the long message field. Otherwise, all messages are displayed in the Strobe log. System Action: Strobe/ISPF cannot process the option. You cannot select Add Active and Add Queued requests, request groups (applicable only if you have AutoStrobe), status, or the log utility function. You can select other Strobe/ISPF options that do not require the Strobe session management facility. These options include: setting user defaults, creating a Performance Profile, using the Indexer, and viewing messages and changes. User Response: STR7034S Ask the Strobe system programmer to activate the Strobe environment.

SSMF ERRORCHECK THE LOG FOR ADDITIONAL INFORMATION

Explanation: You selected an option that requires a component of Strobe, the Strobe session management facility, but this facility issued a return code of 20 (severe error) on a previous call. System Action: Strobe/ISPF cannot process the option. You cannot select Add Active and Add Queued requests, request groups (applicable only if you have AutoStrobe), status, or the log utility function. You can select other Strobe/ISPF options that do not require the Strobe session management facility. These options include: setting user defaults, creating a Performance Profile, using the Indexer, and viewing messages and changes. User Response: Use the ISPF Browse function (not Strobe/ISPF) to examine the Strobe log for additional information. If you cannot browse the Strobe log, notify the Strobe system programmer. STR7035E RESOLUTION OUT OF RANGE. RESOLUTION SHOULD BE BETWEEN 1 AND 9999

Explanation: You specified an invalid value in the RESOLUTION field. The value in this field determines the size of the codeblocks into which Strobe will subdivide long procedures for detailed reporting. System Action: Strobe/ISPF does not process the Performance Profile request.

User Response: Enter a value between 1 and 9999 or clear the field to accept the Strobe default of 64 bytes. STR7036S SSMF ERROR. AN UNRECOVERABLE FAILURE HAS OCCURRED

Explanation: Strobe/ISPF encountered a return code of 20 (severe error) while trying to call the Strobe session management facility. The Strobe session management facility cannot recover from this failure. System Action: All Strobe session management facility processing stops.

User Response: To view all the Strobe messages, enter .CVM in the option field or command line. Notify the Strobe system programmer. STR7037E ENTER 'B' OR 'F'. YOU MUST SPECIFY (B)ACKGROUND OR (F)OREGROUND You did not specify a processing option in the option field. Strobe/ISPF does not process the request.

Explanation: System Action:

User Response: To generate a batch job, specify B for background processing. Multiple requests for Performance Profiles or map datasets are generated as steps in the same job.

To view the Performance Profile or create the map dataset online, specify F for foreground processing.
STR7038E DYNAMIC ALLOCATION ERROR. RC= rc; ERC/IRC= erc/irc; {dsname [member]|ddname}

Explanation: The operating system returned a nonzero return code rc while attempting to allocate the dataset specified by the dataset name dsname or the data definition name ddname. If the dataset is a partitioned dataset, the member name is member. The error reason code is erc and the information reason code is irc. System Action: User Response: Strobe/ISPF does not allocate the dataset. Notify the Strobe system programmer.

3-162

Strobe Messages Guide

STR7039E

SYSIN DATA SET NOT FOUND. SYSIN DATA SET dsname NOT FOUND A SYSIN dataset, dsname, is specified, but the SYSIN dataset is not cataloged.

Explanation:

System Action: Strobe/ISPF cannot produce a Performance Profile until either a cataloged dataset is specified or the SYSIN field is cleared to indicate that a SYSIN dataset is not needed. User Response: STR7040E AND 9999 Specify a valid SYSIN dataset name in the SYSIN field or clear the field.

INVALID REQ NUMBER. REQUEST NUMBER MUST BE A NUMBER BETWEEN 1 You specified an invalid request number. Strobe/ISPF does not process the request. Enter a numeric value from 1 to 9999.

Explanation: System Action: User Response: STR7041E

BASELINE OUT OF RANGE. DETAIL BASELINE MUST BE A VALUE FROM 0 TO 99 You specified an invalid percentage in the DETAIL BASELINE field. Strobe/ISPF does not process the Performance Profile request. Specify a value between 0 and 99.

Explanation: System Action: User Response: STR7042E

DEFAULT PROFILE ERROR. RC = rc; ERC/IRC = erc/irc; BLANK OR CHOOSE ANOTHER

Explanation: You chose Option G from the STATUS panel, but Strobe/ISPF has encountered a nonzero return code, rc, while attempting to allocate the sample dataset. The error reason code is erc and the information reason code is irc. System Action: Strobe cannot create a Performance Profile from the dataset.

User Response: Clear the SAMPLE DATA SET NAME field and press Enter to bypass the failing dataset or enter another sample dataset name in this field. Notify the Strobe system programmer. STR7043E UNABLE TO LOCATE SSR. progname WAS NOT FOUND IN A LINKLIST

Explanation: Strobe/ISPF is unable to load the session requester because it did not find the program progname. System Action: Strobe/ISPF cannot process any option that requires the session requester.

User Response: Notify the Strobe system programmer. There has probably been an installation error. STR7044E WRONG SSR VERSION. SSR RELEASE NUM IS ccc; STROBE/ISPF RELEASE NUM IS sss

Explanation: The release number (NUM), ccc, of a component of Strobe, the Strobe session requester (SSR), does not match the release number of Strobe/ISPF, sss. System Action: Strobe/ISPF cannot process any option requiring SSR.

User Response: Notify the Strobe system programmer. There has probably been an installation error. STR7045E UNIT & VOLUME REQUIRED. THE UNIT AND VOLUME ARE REQUIRED FOR AN UNCATALOGED DATA SET Explanation: You specified an uncataloged dataset but have not provided a unit name, volume serial number, or both. System Action: Strobe/ISPF cannot allocate the dataset.

User Response: Specify the unit name and volume serial number of the device on which the dataset is located. STR7046E VOLUME IS INVALID. VALID VOLUME IS 1 TO 6 ALPHANUMERIC, SPECIAL OR NATIONAL CHARACTERS Explanation: System Action: You specified an invalid volume serial number in the VOLUME field. Strobe/ISPF does not process the request.

Messages Produced by Strobe

3-163

User Response: Specify a valid volume serial number. It must be 1 to 6 alphanumeric, special, or national characters. The three national characters are @ # $. The eleven special characters are the blank character,. / ) ( * & = +. STR7047E UNABLE TO FIND progname. progname NOT FOUND IN LINKLIST

Explanation: Strobe/ISPF cannot find the program progname in the link list dataset, and your Strobe system programmer did not specify a Strobe load library on the UI_STRBLOAD parameter in the Strobe parmlib member. System Action: Strobe/ISPF does not process the request.

User Response: Ask the Strobe system programmer to specify the Strobe load library containing this program on the UI_STRBLOAD parameter in the Strobe parmlib member or to copy the load module into a link list dataset. STR7048E UNABLE TO FIND progname. progname NOT IN loadlib OR LINKLIST

Explanation: Strobe/ISPF cannot find the program progname in a link list dataset or in the dataset loadlib specified on the UI_STRBLOAD parameter in the Strobe parmlib member. System Action: User Response: Strobe/ISPF does not process the request. Notify the Strobe system programmer.

STR7049I SPECIFY JCL DISPOSITION. JCL FOR JOB STEPS CREATED - SELECT OPTION TO PROCESS OR 'END' Explanation: You pressed End at the Strobe - Produce A Performance Profile panel or from the Strobe - Index To Create a Map Dataset panel after submitting requests for background processing. System Action: Strobe /ISPF places the job control statements for the requests in a temporary dataset and displays the Strobe - Select Option For Job Stream panel. User Response: Select the desired option from this panel or press End to cancel the background requests. STR7050E NO SELECTIONS MADE. NO DATA SETS WERE SELECTED FROM DATA SET LIST JUST PRESENTED Explanation: You did not select a dataset to process after you requested a list of datasets available for Performance Profile processing. System Action: Strobe /ISPF does not process the request.

User Response: Request the dataset list again and select the datasets to process by placing an S to the left of the dataset names, and press Enter, or press End to cancel the request. STR7051I NO REQUESTS FOUND. NO MEASUREMENT REQUESTS EXIST [FOR OWNERID ownerid]

Explanation: No current measurement requests meet the selection criteria you specified. If you specified an owner ID on the STATUS panel, it is displayed in the variable ownerid.

This message is issued when you perform any of the following operations under the conditions specified: Select Option 3 (STATUS) on the Strobe Options menu, and no requests were found that match the owner ID in the OWNERID MASK field. Refresh the STATUS panel, and the measurement requests previously displayed no longer exist. Attempt to refresh a sample dataset list created through the STATUS panel, and the request numbers you selected no longer exist. Attempt to display or refresh the sample dataset list from the Strobe - Produce a Performance Profile panel, but Strobe found no measurement requests that match the owner ID on the STATUS panel.
System Action: Strobe/ISPF does not display the request or sample dataset list.

User Response: If you want to display requests, change the owner ID mask in the OWNERID MASK field of the STATUS panel to match the owner ID of the requests. If the request that you want to display is deleted, search the Strobe log for messages about the request and a record of the sample datasets created for the request.

3-164

Strobe Messages Guide

STR7052E

INVALID PERCENTAGE VALUE. PERCENTAGE MUST BE BETWEEN 00.0 AND 99.9 You specified an invalid percentage. Strobe/ISPF does not process the Performance Profile request. Specify a value between 00.0 and 99.9.

Explanation: System Action: User Response:

STR7053E COMPRESS ID INVALID. PREFIX MAY BE UP TO 8 CHARS - THE FIRST CHARACTER CANNOT BE NUMERIC Explanation: You specified an incorrect prefix under the COMPRESS option on the Strobe Detail For a Performance Profile panel. System Action: Strobe/ISPF does not process the Performance Profile request.

User Response: Specify a valid prefix and resubmit the request. Valid prefixes contain three alphanumeric characters, beginning with an alphabetic or national character. Following the prefix, the other seven characters may be alphabetic, numeric, national, or the global search character asterisk (*). The global search character specifies a shortened prefix field for grouping and should be used in the second or third position, not the first. STR7054E MISSING MEMBER NAME. A PARTITIONED DATA SET IS SPECIFIED BUT NO MEMBER NAME IS SUPPLIED Explanation: NAME field. System Action: You specified a partitioned dataset without a member name in the DATA SET Strobe/ISPF does not process the Performance Profile request.

User Response: Enter a valid partitioned dataset with a member name or enter a valid sequential dataset without a member name. STR7055E ERROR AUTHORIZATION ERROR. DELETE OF dsname REC'D PROBABLE AUTHORIZATION

Explanation: You tried to delete a request and its associated sample datasets using Option X from the STATUS panel, but you are not authorized to delete the sample dataset, dsname. System Action: User Response: Strobe does not delete the request or any of the associated sample datasets. Verify that you have the authority to delete the sample datasets.

STR7056E WORKPRI VAR NOT SPEC'D. PRIMARY SPACE ALLOCATION IS NOT SPECIFIED FOR ISPF VAR WORKPRI Explanation: The Strobe system programmer did not specify a value for the parameter UI_WORKPRI (primary space allocation) in the Strobe parmlib member. System Action: Strobe dynamic allocation will fail unless your installation has established default space allocation parameters. User Response: Ask the Strobe system programmer to specify the parameter UI_WORKPRI.

STR7057I SAMPLE DSN(S) NOT DLET. SAMPLE DSN NOT FOUND/NOT DELETED FOR REQ nnnn; REQ NUMBER DELETED Explanation: You tried to delete a request, nnnn, and its associated sample datasets using Option X from the STATUS panel, but Strobe/ISPF has found no sample datasets associated with this request. System Action: User Response: Strobe deletes only the request number nnnn. None required.

STR7058E USE 'Y' TO SELECT LANG. TO SELECT A LANGUAGE, ENTER 'Y' NEXT TO THE PROGRAM LANGUAGE NAME Explanation: System Action: User Response: You entered an invalid selection code next to a program language name. Strobe/ISPF does not process the Indexer request. Select a language by entering a Y to the right of the program language name.

Messages Produced by Strobe

3-165

STR7059E

LIST DATA SET REQ'D. SPECIFY A LIST DATA SET NAME IN THE FIRST FIELD

Explanation: You did not specify a dataset name in the first INPUT: Compiler SYSPRINT Datasets field on the Strobe - Index To Create a Map Dataset panel. This field must name a dataset containing the SYSPRINT listing produced by a compiler or an assembler. System Action: User Response: STR7060E DATA SET Strobe/ISPF does not process the Indexer request. Specify a dataset name in the first INPUT: Compiler SYSPRINT Datasets field.

MEMBER NAME NOT VALID. A MEMBER NAME IS NOT ALLOWED ON A SEQUENTIAL

Explanation: You specified a sequential dataset with a member name in parentheses. A member name cannot be specified for this dataset. System Action: Strobe/ISPF does not process the Indexer request.

User Response: Remove the member name from the sequential dataset or specify a partitioned dataset. STR7061E INVALID SPECIFICATION. CICS DC MUST BE SPECIFIED AS Y FOR THE CICS OPTIONS TO BE USED Explanation: You requested a CICS processing option without selecting the CICS data collector on the Strobe - Data Collectors panel. System Action: invoked. User Response: panel. STR7062I Strobe cannot process any CICS options until the CICS data collector is Specify Y next to the CICS data collector on the Strobe - Data Collectors

MAP DATA SET CREATED. THE STROBE MAP DATA SET HAS BEEN CREATED IN dsname

Explanation: You specified foreground indexing of a SYSPRINT dataset for a map dataset. The name of the dataset is dsname. System Action: Strobe successfully completed and created a map dataset in the foreground.

User Response: If you requested the creation of a map dataset through the Profile option, you can press Enter to supply the map dataset to the Reporter. Otherwise, you can supply the map dataset later when you produce a Performance Profile. STR7063E INDEXER CMPLTD RC=rc. indexer message

Explanation: You selected foreground processing from the Strobe - Index To Create a Map Dataset panel. System Action: Strobe Indexer returned a nonzero return code, rc.

User Response: Press Help key to view the corresponding Indexer error message in the long message field. Find the message in Strobe Messages Guide (this manual) and read the indicated response. STR7064E TEMP SYSIN DS ALLOC ERR. RC= rc; ERC/IRC= erc/irc; dsname

Explanation: The operating system returned a non-zero return code, rc, while attempting to allocate a temporary dataset for the Reporter operands specified on the Strobe - Produce a Performance Profile panel. The error reason code is erc and the information reason code is irc. System Action: Strobe does not allocate the dataset named dsname. Strobe cannot complete the request to create a Performance Profile. User Response: Notify the Strobe system programmer.

STR7065E PROGRAM LANGUAGE REQ'D. ENTER 'Y' NEXT TO THE PROGRAM LANGUAGE OF THE SYSPRINT DATA SETS Explanation: System Action: User Response: You did not specify a program language. Strobe/ISPF does not process the Indexer request. Enter a Y next to the language of the programs you want to index.

3-166

Strobe Messages Guide

STR7066E

SELECT ONLY 1 LANGUAGE. SELECT ONLY ONE LANGUAGE PER MAP DATA SET

Explanation: You selected more than one program language name on the Strobe - Index To Create a Map Dataset panel. System Action: Strobe/ISPF does not process the Indexer request.

User Response: Enter a Y next to the language of the programs you want to index. You can specify only one language for each map dataset.

To index programs with different source languages, create multiple map datasets.
STR7067E ENTER REQ NUM OR JOBNAME. SPECIFY EITHER REQUEST NUMBER OR JOBNAME FOR THE CHANGE REQUEST Explanation: You either specified both a jobname and a request number or neither the jobname nor the request number. System Action: Strobe does not process the change for your request.

User Response: Specify either the jobname or the request number (but not both) to identify the request you wish to change. STR7068E SYSPRINT ALLOC ERROR. RC=rc; ERC/IRC= erc/irc; dsname

Explanation: Strobe encountered an error when it attempted to dynamically allocate dataset dsname with the user input on the Strobe - Produce a Performance Profile panel or the Strobe Index To Create a Map Dataset panel. The operating system returned a non-zero return code, rc, an error reason code, erc, and an information reason code, irc. System Action: Strobe/ISPF does not allocate the dataset.

User Response: Check for errors in the unit or volume specification. If necessary, consult IBMs Authorized Assembler Programming Guide manual, which documents dynamic allocation services return codes and reason codes. If this information does not help you to resolve the problem, notify the Strobe system programmer. If you are using Storage Management Subsystem (SMS), be sure that the unit and volume specifications comply with SMS rules. STR7069E ENTERED OPTION/PARM CONFLICT. OPTION 2 REQUIRED FOR PARAMETER CHANGE(S)

Explanation: You specified values in the SESSION DURATION, TARGET SAMPLE SIZE, or FINAL SESSION ACTION fields on the Strobe - Change Request panel, but selected an option other than 2 in the OPTION field. You can specify these values only when selecting Option 2. System Action: Strobe/ISPF does not process the change for your request.

User Response: Select Option 2 or clear the SESSION DURATION, TARGET SAMPLE SIZE, and FINAL SESSION ACTION fields before selecting a different option. STR7070I PROFILE GENERATED. THE STROBE PROFILE [dsname] IS CREATED

Explanation: Strobe successfully created a Performance Profile through foreground processing. Strobe encountered no warnings or errors. The name of the dataset that contains the Profile is dsname. (If a dataset has not been specified in the DATA SET NAME field on the Strobe - Produce a Performance Profile panel, then dsname does not appear.) System Action: User Response: STR7071I Strobe produces a Performance Profile. None required.

PROFILE CMPLTED RC= rc . A RETURN CODE OF rc WAS RECEIVED FROM progname The program progname sent a nonzero return code, rc, to Strobe/ISPF.

Explanation:

System Action: Strobe/ISPF displays the messages returned by the Reporter. If the return code is less than the severe error value of 12, Strobe also produces a Performance Profile. User Response: If the return code (rc) is less than 12, view the Performance Profile. Otherwise, view the messages and take the corrective action indicated. STR7072E COMPRESS FIELD ERROR. A COMPRESS PREFIX AND GROUP NAME MUST BE SPECIFIED TOGETHER Explanation: You did not specify both a prefix and a group name under the COMPRESS option on the Strobe - Detail For a Performance Profile panel.

Messages Produced by Strobe

3-167

System Action:

Strobe/ISPF does not process the Performance Profile request.

User Response: Specify both a prefix (of up to eight characters) and a group name (of up to seven characters). STR7073I JCL GENERATED. nnn SSMF CONTROL STATEMENTS GENERATED FOR BATCHSUBMISSION Explanation: You specified at least one batch-submission action.

System Action: Strobe/ISPF wrote nnn job control statements to the SYSIN dataset to execute Strobe on another system. User Response: Select Option 7 to submit the control statements, or press F3 to discard them. STR7074E INVALID REQ NUM/JOBNAME. FIELD DOES NOT CONTAIN A VALID REQUEST NUMBER OR A VALID JOBNAME Explanation: You specified an invalid jobname or request number on the Strobe - BatchSubmission List/Delete Request panel. System Action: Strobe/ISPF does not produce commands for the list or delete operations.

User Response: Specify a number between 1 and 999, or specify a 1- to 8-character jobname consisting of alphanumeric or national characters; the first character cannot be numeric. STR7075E INVALID SPECIFICATION. VALID OPTIONS ARE 'Y' OR 'N' You specified a value other than Y or N in the field shown by the cursor. Strobe/ISPF does not process the request. Specify Y in the field to select the desired option.

Explanation: System Action: User Response: STR7076E

JOBNAME REQUIRED. A JOBNAME MUST BE SPECIFIED FOR THE SELECTED OPTION Strobe/ISPF requires a jobname to process the request. Strobe/ISPF does not process the request. Enter a valid jobname.

Explanation: System Action: User Response:

STR7077I JOBNAME NOT FOUND. THE SPECIFIED JOBNAME COULD NOT BE FOUND IN THE ACTIVE JOB LIST Explanation: longer active. System Action: User Response: selection. STR7078E The job you selected from the Strobe - Active Job Selection List panel is no Strobe/ISPF does not process the request. To update the ACTIVE JOB SELECTION LIST, press Enter without making a

UNABLE TO LOCATE DSN. LOCATE RC=4 FOR dsname

Explanation: The operating system returned a return code of 4 (warning) while attempting to retrieve information from a catalog for dataset dsname. System Action: User Response: error. Strobe/ISPF cannot allocate the dataset. Notify the Strobe system programmer. There has probably been a cataloging

STR7079E UNABLE TO OPEN LIBRARY. THE OPEN FOR THE STROBE LOAD LIBRARY WAS UNSUCCESSFUL Explanation: Strobe/ISPF cannot open the Strobe unauthorized load library. The dataset name of the unauthorized Strobe library that contains the Strobe Reporter and Indexer programs is specified on the parameter UI_STRBLOAD in the Strobe parmlib member. System Action: User Response: Strobe/ISPF does not process the request. Notify the Strobe system programmer.

3-168

Strobe Messages Guide

STR7080E

INVALID STATUS TYPE. ENTER 'Q', 'A', 'C', [D] OR BLANK

Explanation: You have entered an invalid type in the STATUS TYPE field on the Strobe Batch-Submission List/Delete Request panel. Valid types are:

Q A C D Blank

to list queued requests to list active requests to list completed requests to list deferred requests to list all requests
Strobe/ISPF does not produce control statements for the LIST operation. Specify a valid type.

System Action: User Response: STR7081E

STROBE/ISPF ABEND. STROBE message text An ABEND occurred during Strobe/ISPF execution.

Explanation:

Information about the ABEND appears in the long message text. You may review additional information by browsing the Strobe log or entering the .CVM command in the OPTION field.
System Action: Strobe/ISPF attempts to restart processing at the Strobe Options menu. If Strobe/ISPF cannot recover, then Strobe/ISPF processing terminates. User Response: STR7082E Notify the Strobe system programmer.

UNABLE TO OPEN SYSIN. UNABLE TO OPEN SYSIN DCB

Explanation: Strobe cannot open the SYSIN dataset used to pass report operands to the Reporter in the foreground Strobe - Produce a Performance Profile panel. You specified this data on the Strobe - Detail For a Performance Profile panel or with the &STRSYSIN variable on the Strobe - Default Options panel. System Action: Strobe/ISPF does not process the Performance Profile request.

User Response: Ensure that the dataset name on the panel is valid. If it is, or if you have not specified a dataset name, notify the Strobe system programmer. STR7083E progname ABEND Sxxx. progname ABENDED WITH AN xxxx

Explanation: A Strobe program, progname, terminated abnormally with a system code of xxxx. The program is the STROBEDT, the report reformatter STROBEDS, or an Indexer. System Action: User Response: Strobe/ISPF does not process the request. If the Reporter has terminated abnormally, verify the sample dataset name.

If an Indexer has terminated abnormally, verify the compiler SYSPRINT dataset name and the programming language specified on the Strobe - Index To Create a Map Dataset panel. If the region size is 4096KB or less, increasing the region size may correct the problem. Notify the Strobe system programmer.
STR7084E UNIT NAME REQUIRED. A UNIT NAME IS REQUIRED TO ALLOCATE THE DATA SET You did not specify a unit name. Strobe cannot allocate the dataset. Enter a unit name in the UNIT field.

Explanation: System Action: User Response: STR7085I

JCL GENERATED. ppp PROFILE STEP(S) AND iii INDEXER STEP(S) GENERATED

Explanation: Strobe generated ppp job steps to create Strobe Performance Profiles and iii job steps to create map datasets.

Messages Produced by Strobe

3-169

System Action: Strobe/ISPF stores the job control statements in a temporary dataset until you save, submit, or cancel them. User Response: Select Option 1 to submit the job, or select Option 2 or 3 to save the job control statements in a permanent dataset. To edit the job stream, select Option 2. STR7086E NO SAMPLE DATA SETS. NO SAMPLE DATA SETS EXIST [FOR OWNERID ownerid]

Explanation: You requested the Sample Data Set list by clearing the SAMPLE DATA SET NAME field, but no sample datasets are available. If an owner ID has been specified on the STATUS panel in the OWNERID MASK field, it is ownerid. System Action: Strobe/ISPF does not process the Performance Profile request.

User Response: Select a completed request that has associated sample datasets, or change the owner ID to display additional requests. STR7087I ENTERED NO CHANGES MADE. A CHANGE REQUEST WAS SELECTED BUT NO CHANGES WERE You submitted a change request but have not changed the original parameters. Strobe/ISPF does not generate a CHANGE control statement.

Explanation: System Action:

User Response: Specify the new parameters on the change request panel and press Enter, or press End to cancel. STR7088E OPTION 7 NO COMMANDS TO PROCESS. CHOOSE ANOTHER OPTION BEFORE SELECTING

Explanation: You selected the JOB STREAM MENU, Option 7, however, no Strobe control statements were generated. System Action: Strobe/ISPF does not generate a job step until you request Strobe control statements from other options on the Strobe - Batch-Submission Options menu. User Response: menu. STR7089E Select one of these options or press End to return to the Strobe Options

DELETE GROUP FAILED. THE GROUP WAS NOT DELETED DUE TO ERRORS

Explanation: A component of Strobe, the Strobe session management facility, detected errors in the processing of the DELETE GROUP command. System Action: User Response: STR7090E Strobe does not process the command. Correct the errors displayed on the browse screen and reissue the command.

FIELD MUST BE NUMERIC. THIS FIELD REQUIRES A NUMERIC SPECIFICATION You entered a nonnumeric value in a field that requires a numeric Strobe/ISPF does not process your selection. Enter a numeric value.

Explanation: specification. System Action: User Response:

STR7091E SORTSIZE OUT OF RANGE. THE SORT CORE SIZE VALID VALUES ARE ZERO OR FROM 12000 TO 999999 Explanation: System Action: You specified an invalid value in the SORT SIZE field. Strobe/ISPF does not process the request.

User Response: Specify a number between 12000 and 999999, or select zero to accept the system default. If you clear the field, Strobe/ISPF uses the Strobe default of 999999. STR7092E INVALID OWNERID. ENTER VALID JOBNAME, OWNERID, PATTERN, OR BLANKS You specified an invalid owner ID in the OWNERID field. Strobe/ISPF does not process your selection.

Explanation: System Action:

User Response: To view requests submitted under one jobname or TSO owner ID, enter the jobname or owner ID consisting of alphanumeric characters. The first character must not be numeric.

3-170

Strobe Messages Guide

To view requests submitted under all jobnames or TSO owner IDs that begin with a common prefix, enter the prefix followed by the global search character asterisk (*). To view all requests, clear the field or enter only the global search character asterisk (*).
STR7093E INVALID DATA SET NAME. YOUR DSNAME SPECIFICATION IS SYNTACTICALLY INCORRECT Explanation: System Action: User Response: You specified an invalid dataset name. Strobe/ISPF does not process your selection. Enter a valid dataset name.

STR7094E INVALID LIST. AN SVC LIST MUST CONTAIN TWO OR MORE SVC ENTRIES SEPARATED BY COMMAS Explanation: System Action: User Response: You specified a list of SVC numbers incorrectly. Strobe/ISPF does not process the request. Separate the entries in the list of SVC numbers and ranges with commas.

STR7095E CANNOT ALLOCATE PDS. THE PARTITIONED DATA SET SPECIFIED MUST BE CATALOGED Explanation: System Action: User Response: You specified an uncataloged partitioned dataset in the DATA SET NAME field. Strobe/ISPF cannot allocate a new partitioned dataset. Specify either a sequential dataset or a cataloged partitioned dataset.

STR7096E SPECIFY MESSAGE NUMBER. SPECIFY THE FOUR-DIGIT NUMERIC PORTION OF THE MESSAGE IDENTIFIER Explanation: System Action: User Response: STR7097E You did not specify a message number in the MESSAGE NUMBER field. Strobe/ISPF does not display the message text. Enter the four-digit numeric portion of the message key.

MSG LIBRARY NOT FOUND. UNABLE TO LOCATE dsname

Explanation: The library dsname, which contains the Strobe message text, is not cataloged. The Strobe error message text library must be specified on the parameter UI_STRBETXT in the Strobe parmlib member. System Action: User Response: STR7098E Strobe/ISPF does not display the message text. Notify the Strobe system programmer.

LIB ALLOCATION ERROR. RC=rc; ERC/IRC=erc/irc; dsname

Explanation: Strobe/ISPF attempted to allocate the Strobe error message text library dsname, and the operating system returned a nonzero return code, rc. The error reason code is erc and the information reason code is irc. The Strobe error message text library is specified on the parameter, UI_STRBETXT in the Strobe parmlib member. System Action: message. User Response: STR7099I Strobe/ISPF cannot allocate the dataset or display the explanation of a Notify the Strobe system programmer.

MESSAGE NOT FOUND. NO MESSAGES WERE FOUND WITH THE MESSAGE KEY nnnn

Explanation: You specified a message key for which there is no associated message text in the Strobe message library. System Action: User Response: STR7100E Strobe/ISPF does not display the message text. Correctly specify the four-digit numeric portion of the message key.

PERMANENT I/O ERROR. PERM I/O ERROR OR INSUFF STORAGE - dsname

Explanation: Strobe/ISPF encountered an error while reading the dataset dsname. The error indicates insufficient storage or a permanent I/O error.

Messages Produced by Strobe

3-171

System Action: User Response: STR7101E

Strobe/ISPF stops processing. Notify the Strobe system programmer.

UNABLE TO OPEN MSG LIB. UNABLE TO OPEN THE ERROR MSG LIB - dsname

Explanation: Strobe/ISPF was unable to open the Strobe message library dsname while processing a request from the Strobe - Display Message Text panel or the .M command. The Strobe error message text library is specified on the parameter, UI_STRBETXT in the Strobe parmlib member. System Action: User Response: STR7102E 255 Strobe/ISPF does not display the message text. Notify the Strobe system programmer.

NUMBER OF COPIES INVALID. COPIES MUST BE A NUMERIC VALUE BETWEEN 1 AND You specified an invalid number of copies in the NUMBER OF COPIES field. Strobe/ISPF does not process the Performance Profile request. Specify a number of copies that is between 1 and 255.

Explanation: System Action: User Response: STR7103E

INVALID MESSAGE NUMBER. THE ERROR MESSAGE KEY MUST BE NUMERIC You specified an invalid message key in the MESSAGE NUMBER field. Strobe/ISPF does not display the message text. Enter the four-digit numeric portion of the message key.

Explanation: System Action: User Response: STR7104E PANEL

NO MAP GENERATED. MAXIMUM NUMBER OF MAP DATA SETS SPECIFIED ON THE

Explanation: You specified Y in the NEW MAPS field, but all the MAP DATA SET NAMES fields are filled. System Action: Strobe/ISPF does not process the Indexer request.

User Response: Delete one of the seven MAP DATA SET NAMES fields so that Strobe/ISPF can enter the new map dataset name. STR7105E MESSAGE LIB NOT SPEC'D. STROBE MESSAGE LIB DSN IS NOT SPEC'D FOR THE PARAMETER UI_STRBETXT Explanation: A dataset name for the library containing the Strobe error message texts is not specified on the parameter UI_STRBETXT in the Strobe parmlib member. System Action: User Response: Strobe/ISPF does not display the message text. Notify the Strobe system programmer.

STR7106E DATA SET NAME REQUIRED. A DATA SET NAME MUST BE SPECIFIED WHEN OPTION 2 OR 3 IS SELECTED Explanation: You selected Option 2 or 3 to write the job stream to a dataset, but you did not specify a dataset name. System Action: Strobe/ISPF does not write the job stream to a dataset.

User Response: Specify a sequential dataset or a member of an existing partitioned dataset. If the sequential dataset does not already exist, Strobe/ISPF creates and catalogs it. STR7107E OUTPUT SPECIFY MAP DSNAME. A MAP DATA SET NAME IS REQUIRED FOR THE INDEXER

Explanation: You left the MAP DATA SET field blank. This field specifies a name for the map dataset produced by a Strobe Indexer. System Action: Strobe/ISPF does not process the Indexer request.

User Response: Specify a fully qualified dataset name within single quotation marks. If you specify a dataset name without single quotation marks, Strobe/ISPF appends your TSO prefix or owner ID or the system-default high-level qualifier to the dataset name.

3-172

Strobe Messages Guide

STR7108E

ISPF SERVICE FAILED. SERVICE servicename RC = rc IN modname

Explanation: Strobe called the dialog service servicename from module modname, but the service routine failed with a return code of rc. System Action: User Response: STR7110E NAME Strobe/ISPF does not process your selection. Notify the Strobe system programmer.

MEMBER NAME NOT ALLOWED. MEMBER NAME IS NOT ALLOWED IN THE DATA SET

Explanation: You cannot specify a partitioned dataset for a sample dataset or a Performance Profile dataset. System Action: User Response: STR7111E Strobe/ISPF does not process your request. Specify the name of a sequential dataset.

VOLUME NOT MOUNTED. dsname IS NOT AVAILABLE, MOUNT VOLUME volume

Explanation: Strobe/ISPF attempted to retrieve a dataset, dsname, from the specified volume volume and the operating system returned a return code of 4 (warning). System Action: User Response: STR7112E The volume is not mounted. Request that the device be mounted or specify a dataset on another volume.

DATA SET NOT ON VOLUME. dsname NOT ON volume

Explanation: Strobe/ISPF attempted to retrieve the dataset dsname from the specified volume volume on a direct-access storage device, and the operating system returned a return code of 8. The dataset is not cataloged on that volume. System Action: User Response: STR7113E Strobe/ISPF does not process the request. Specify an existing dataset name.

VALIDATION ERROR. RC=rc ON VOLUME volume FOR dsname

Explanation: Strobe/ISPF attempted to retrieve dataset dsname from volume volume on a direct-access storage device, and the operating system has returned a return code, rc, of 12 or 16 (severe errors). System Action: User Response: programmer. Strobe/ISPF does not process the request. Refer to the relevant IBM publication and notify the Strobe system

STR7114W TIME OUT OCCURRED. REQ NUM NOT AVAILABLE - CHECK STATUS PANEL OR LOG FOR VERIFICATION Explanation: Strobe may have been unable to add the request.

System Action: Strobe may not have processed the request. The log and STATUS panel contain additional information. User Response: Check the Strobe log for additional messages and the STATUS panel for additional information. If the request succeeded, it will appear on the STATUS panel. STR7115E CATALOG DATA SET NOT CATALOGED. dsname COULD NOT BE LOCATED IN THE SYSTEM

Explanation: Strobe/ISPF attempted to retrieve dataset information from a catalog, and the operating system returned a nonzero return code. Strobe/ISPF cannot locate the dataset named dsname in the system catalog. System Action: User Response: STR7116E Strobe/ISPF does not process the request. Specify an existing cataloged dataset name.

INVALID DATA SET NAME. A SYNTAX ERROR EXISTS IN THE DSNAME dsname

Explanation: The operating system returned a return code of 20 (severe error) while attempting to retrieve information from a catalog by dsname. You specified an invalid dataset name.

Messages Produced by Strobe

3-173

System Action: User Response:

Strobe/ISPF does not allocate the dataset. Specify a fully qualified dataset name.

STR7117E I/O ERROR ON CATALOG. AN I/O ERROR WAS ENCOUNTERED ATTEMPTING TO LOCATE dsname Explanation: The operating system returned a return code of 24 while attempting to locate dataset dsname. This is a permanent I/O error. System Action: User Response: STR7120E Strobe/ISPF does not process the request. Notify the Strobe system programmer.

CICS/IMS NOT ALLOWED. CICS AND IMS CANNOT BE SELECTED TOGETHER

Explanation: You cannot select both the CICS and the IMS subsystems. Overriding the CPS or Terminal Activity Report causes CICS to be invoked; leave these fields blank if you select IMS.

Strobe will automatically collect DBCTL activity in a CICS address space if both Strobe for CICS and Strobe for IMS are present. Do not specify Y in the IMS field.
System Action: User Response: STR7121E TOGETHER Strobe/ISPF does not process the request. Specify either CICS or IMS or use the system defaults.

NOT ALLOWED WITH NATURAL. ADABAS AND NATURAL CANNOT BE SELECTED You cannot select both the ADABAS and NATURAL data collectors together. Strobe/ISPF does not process the request. Specify either ADABAS or NATURAL, or use the system defaults.

Explanation: System Action: User Response: STR7122E TOGETHER

ADABAS/ADA3GL CONFLICT. ADABAS AND ADA3GL CANNOT BE SELECTED You cannot select both the ADABAS and the ADA3GL data collectors together. Strobe/ISPF does not process the request. Specify either ADABAS or ADA3GL, or use the system defaults.

Explanation: System Action: User Response: STR7123E

SEL LIST NOT AVAILABLE. NO ACTIVE JOBS FOUND FOR THE SELECTED LIST TYPE

Explanation: On the Strobe - Limit Active Job Lists panel you selected a TYPE for which Strobe/ISPF could find no active jobs. System Action: Strobe/ISPF does not display the active job list.

User Response: Select another list type by entering Y to select the desired type on the Strobe - Limit Active Job Lists panel. To view all active jobs, clear the JOBNAME field and press Enter. STR7124E ENTER REQ NUM/JOBNAME. A REQUEST NUMBER OR A JOBNAME IS REQUIRED TO PROCESS THE REQUEST Explanation: You selected an option on the Strobe - Batch-Submission List/Delete Request panel that requires either a request number or jobname, but neither has been specified. System Action: operations. Strobe/ISPF does not produce control statements for the LIST or DELETE

User Response: Specify at least one request number or jobname in the REQUEST NUMBER or JOBNAME fields on this panel. STR7128E INVALID DATE. DATE IS EITHER IN INVALID FORMAT, OR IT IS A FUTURE DATE

Explanation: You specified an invalid date in the STARTING DATE field. You cannot specify a future date, and you must specify the date in the correct format. System Action: Strobe/ISPF does not process the request.

User Response: You cannot specify a future date. Enter the date in the format that the Strobe system programmer specified in the PARMLIB library when installing Strobe. If the Strobe system programmer did not change the specified date format, the default value is

3-174

Strobe Messages Guide

dd/mm/yyyy. The value for the day must be from 1 to 31, and the value for the month must be from 1 to 12. STR7129E INVALID USERID. ENTER ALPHANUMERIC CHARACTERS, FIRST CHARACTER MUST NOT BE NUMERIC Explanation: System Action: You specified an invalid user ID in the USERID field. Strobe/ISPF does not allocate the dataset.

User Response: Specify a valid user ID consisting of alphanumeric characters or the global search character asterisk (*). The first character must not be numeric. STR7130E UNABLE TO LOCATE LOG. dsname IS PROBABLY DELETED OR UNCATALOGED

Explanation: Strobe/ISPF cannot locate the dataset for the Strobe log. The Strobe log is either deleted or uncataloged. System Action: Strobe/ISPF does not allocate the dataset.

User Response: Notify the Strobe system programmer. There has probably been an installation error. STR7131E INVALID SUPPRESS OPTION. SUPPRESS CANNOT BE COMBINED WITH OTHER ATTRIBUTION OPTIONS Explanation: You specified Y in both the SUPPRESS field and in one or more of the SUPPRESS REPORTS fields.

The SUPPRESS option suppresses all attribution reports, and it cannot be combined with any other attribution options.
System Action: Strobe/ISPF does not process the Performance Profile request.

User Response: Select only the SUPPRESS option to suppress all attribution reports, or you can choose to suppress selected attribution reports. STR7133I NO LOG MESSAGES SELECTED. NO LOG MESSAGES WERE FOUND WHICH MET THE SELECTION CRITERIA Explanation: Strobe/ISPF did not find any messages meeting the selection criteria you specified. You may have specified conflicting or overly restrictive criteria. System Action: Strobe/ISPF does not display messages from the Strobe log.

User Response: Adjust the selection criteria or clear all criteria fields to view the entire Strobe log. STR7134E SUPPRESS OR CONDENSE. A CONDENSE PERCENTAGE CANNOT BE SPECIFIED WITH THE SUPPRESS OPTION Explanation: You specified Y in the SUPPRESS field and entered a baseline percentage in the BELOW% field. System Action: User Response: STR7135E Strobe/ISPF does not process the Performance Profile request. Enter a baseline percentage or select the SUPPRESS option for these reports.

UNABLE TO OPEN DATA SET. UNABLE TO OPEN dsname You specified a function that requires an open dataset. Strobe/ISPF cannot open the dataset dsname. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR7136E

UNABLE TO OPEN DATA SET. UNABLE TO OPEN LOG DATA SET

Explanation: You attempted to view messages with the .CVM command, with Option L from the Strobe Options menu, or when Strobe returns multiple messages. System Action: messages. User Response: Strobe/ISPF cannot open a temporary dataset in which to display the Strobe Notify the Strobe system programmer.

Messages Produced by Strobe

3-175

STR7137I

NO SSMF MESSAGES. THERE ARE NO SSMF MESSAGES TO DISPLAY

Explanation: There are no messages from a component of Strobe, the Strobe session management facility. System Action: User Response: STR7139E 255 Strobe/ISPF does not display SSMF messages. None required.

INVALID SVC NUMBER. SVC NUMBER SHOULD BE NUMERIC AND BETWEEN 0 AND You specified an invalid SVC number. Strobe/ISPF does not process the request. Enter a value between 0 and 255.

Explanation: System Action: User Response:

STR7140E SESSION NUM OUT OF RANGE. NUMBER OF SESSIONS MUST BE A NUMERIC VALUE FROM 1 TO 99 Explanation: You specified an invalid session number in the NUMBER OF SESSIONS field. This number determines how many separate sample datasets Strobe creates during the measurement request. System Action: User Response: STR7141E Strobe/ISPF does not process the request. Specify a value from 1 to 99.

INVALID RANGE. SVC RANGE MUST BE ASCENDING You entered a range of SVC numbers that is not in ascending order. Strobe/ISPF does not process the request. Enter the range in ascending order, separating the numbers with a hyphen.

Explanation: System Action: User Response: STR7142E ERRORS

REQUEST NOT ADDED. ADD REQUEST WAS NOT PROCESSED BY SSMF BECAUSE OF

Explanation: A component of Strobe, the Strobe session management facility, detected errors in the Add Active or Add Queued request. System Action: Strobe does not process the request.

User Response: Enter the .CVM command to display the error messages for the request. Correct the errors and resubmit the request. STR7143E OPTION CODE NOT VALID. VALID CODES ARE 'V', 'C', 'P', 'G', 'Q', 'X', and 'B'

Explanation: You entered an invalid option code. The valid options are: V (view), C (change), P (Profile), G (default Profile), Q (Quit), D (delete request), X (delete request and associated datasets), and B (browse auto Profile). System Action: User Response: STR7144E Strobe/ISPF does not process the option. Specify a valid option to the left of the appropriate request.

OPTION NOT ALLOWED. THIS OPTION IS NOT ALLOWED FOR status REQUESTS You selected an option that is invalid for a request with the status status. Strobe/ISPF does not process the option. Specify a valid option to the left of the appropriate request.

Explanation: System Action: User Response: STR7145E

GRP SUBMIT UNSUCCESSFUL. SUBMIT FAILED FOR ONE OR MORE GROUP ELEMENTS

Explanation: One of the request groups that you selected on the Strobe - Request Group Processing panel was not successfully submitted for processing. The line option for this request is highlighted. System Action: User Response: Strobe does not add the elements of the group in which it detected errors. Correct the error(s) and resubmit the group.

3-176

Strobe Messages Guide

STR7146E NO SAMPLE DATA SET. MEASUREMENT TASK ERRORS - MESSAGES ARE IN THE STROBE LOG Explanation: You selected a request with no associated sample datasets for Profile (P) or default Profile (G) processing. A sample dataset is necessary to create a Performance Profile. System Action: Strobe/ISPF does not process the Performance Profile request.

User Response: To determine why the sample dataset was not allocated, view the measurement task messages for this request in the Strobe log. STR7147E SAMPLE DATA SET IS OPEN. AN OPEN SAMPLE DATA SET CANNOT BE USED TO PRODUCE A PROFILE Explanation: You submitted a request to produce a Strobe Performance Profile from an open sample dataset. The sample dataset must be closed before Strobe can produce a Performance Profile. System Action: Strobe/ISPF does not process the Performance Profile request.

User Response: If the request is ACTIVE or SUSPENDED and the sample dataset is open, select Option 3 (STATUS) to send a CHANGE command to close the sample dataset. STR7148I VERIFY CANCEL REQUEST. VERIFY THE CANCEL REQUEST - END TO EXIT, ENTER TO CONTINUE Explanation: You issued an END command. Strobe/ISPF requires verification before it deletes the generated job stream. System Action: Strobe/ISPF does not delete the job stream.

User Response: Press End to complete termination. Strobe/ISPF deletes all the generated job control statements.

Press Enter to continue with background processing.


STR7149E INVALID COMMAND. THE ABOVE IS AN INVALID SCROLLING COMMAND

Explanation: You entered an invalid scrolling command. Valid scrolling commands are a direction (up or down) and an amount (page, half, max, csr, data, or an integer between 0 and 9999) in the SCROLL or OPTION or COMMAND field. System Action: User Response: field. Strobe/ISPF does not scroll for the selected value. Enter a valid command on the OPTION/COMMAND line or in the SCROLL

STR7150E INVALID NUM OF SESSIONS. WHEN FINAL SESSION ACTION IS 'C', NUMBER OF SESSIONS MUST BE ONE Explanation: If the final session action is C (continue), you must specify 1 in the NUMBER OF SESSIONS field. System Action: Strobe/ISPF does not process the request.

User Response: Specify 1 in the NUMBER OF SESSIONS field or specify Q (quit) or S (stop) as the final session action. STR7151E SELECT 'S' OR 'Q'. FINAL SESSION ACTION OF 'C' CANNOT BE SELECTED WITH CICS

Explanation: You specified a final session action of C (Continue) for a measurement session with CICS as a data collector.

You cannot specify a final session action of C if the CICS Performance Supplement is to be generated.
System Action: Strobe/ISPF does not process the request.

User Response: Specify Q (quit) or S (stop) in the FINAL SESSION ACTION field or use the Strobe - Data Collectors panel to suppress CICS. STR7152W NO OPTION INSTALLED. UNABLE TO BUILD OR PROCESS THE INSTALLED OPTIONS TABLE: table Explanation: Strobe/ISPF cannot locate any licensed entries in the options table listed. table identifies the options table being processed:

Messages Produced by Strobe

3-177

DCC/ATTR - Data Collectors/Attributors INDEXER - Source mapping language Indexers STRITDAX - Internal options table.
System Action: Strobe/ISPF attempts to continue processing, but may be severely impacted in what can be processed.

No DCC/ATTR entries means that Strobe processes the measurement request, but will gather no subsystem-specific data. No INDEXER entries means that this installation does not use any of the languages supported by the INDEXER and that Strobe will not be able to process Source Language Mapping via the INDEXER. No STRITDAX entries means that Strobe processes the measurement request, but will gather no subsystem-specific data.
User Response: Notify the Strobe system programmer and ensure the following:

The load module STRBSLMX is available. The Options are licensed. The STRITDAX CSECT is included in the STRBISPF LMOD.
STR7154I REQUEST GENERATED. SELECT ANOTHER OPTION OR 7 TO PROCESS THE REQUEST You generated a Batch-Submission Add, Change, or List/Delete request.

Explanation:

System Action: Strobe/ISPF saves the control statement generated by the request in a dataset until you submit the job. To submit the job use Option 7 on the Strobe - Batch-Submission Options panel. User Response: Generate more requests and submit the stored control statements using Option 7 or cancel the batch-submission request by pressing End. STR7156I USER DEFAULTS SAVED. USER SPECIFIED OPTIONS HAVE BEEN SAVED You changed your user defaults. Strobe will use the new user default values for subsequent actions. None required.

Explanation: System Action: User Response: STR7157E

INVALID SPECIFICATION. VALID OPTIONS ARE 'YES' OR 'NO' You entered an invalid response. Strobe/ISPF does not process the request. Enter YES or NO.

Explanation: System Action: User Response: STR7158E

INVALID SPECIFICATION. VALID SPECIFICATIONS ARE 'T' OR 'I' OR BLANK You entered an invalid response. Strobe/ISPF does not process the Performance Profile request. Enter T for a Profile report, I for an iStrobe file, or blank for your terminals

Explanation: System Action: User Response: default format. STR7159E

LOG ALLOCATION ERROR. FREE FAILED FOR LOG DSN = dsname The Strobe log deallocation failed. The temporary dataset remains allocated.

Explanation:

System Action: Strobe keeps the dataset allocated, which may cause problems with further allocation requests. User Response: STR7160E FAILED If problems occur, notify the Strobe system programmer.

DYNAMIC ALLOCATION ERROR. RC=rc; ERC/IRC=erc/irc; INPUT LOG DEALLOCATION

Explanation: The operating system returned a nonzero return code while attempting to deallocate the input browse log dataset. The return code is rc, the error reason code is erc, and the information reason code is irc. System Action: Strobe keeps the dataset allocated, which may cause problems with further allocation requests.

3-178

Strobe Messages Guide

User Response: STR7161E

Notify the Strobe system programmer.

INVALID DATA SET. DATA SET ORGANIZATION MUST BE PHYSICAL SEQUENTIAL

Explanation: The organization of the dataset is incorrect for this function. Strobe will not process a dataset with a dataset organization other than physical sequential. System Action: User Response: STR7162E Strobe does not process the dataset. Specify a dataset with a dataset organization of physical sequential.

INVALID LOG DATA SET. DATA SET RECORD FORMAT MUST BE VBA

Explanation: The record format of the dataset is incorrect for this function. Strobe will not process a dataset with a record format other than VBA. System Action: User Response: STR7163E Strobe does not process the dataset. Specify a dataset with a record format of VBA.

INVALID LOG DATA SET. DATA SET RECORD LENGTH MUST BE 137

Explanation: The dataset record length is incorrect. Strobe will not process a dataset with a record length other than 137. System Action: User Response: STR7164E Strobe does not process the dataset. Specify a dataset with a record length of 137.

COMMAND NOT VALID. option NOT VALID ON CONFIRM PURGE OF DATA SET PANEL

Explanation: You attempted to execute a Strobe command on the Strobe - Confirm Purge of Data Set panel. You cannot issue Strobe commands from this panel. System Action: User Response: Strobe/ISPF does not process the command. Proceed to the next panel to issue a Strobe command.

STR7165E INVALID DATA SET. DATA SET ORGANIZATION MUST BE PHYSICAL SEQUENTIAL OR PARTITIONED Explanation: The organization of the dataset is incorrect for this function. Strobe will not process a dataset with a dataset organization other than physical sequential or partitioned. System Action: User Response: partitioned. STR7166E Strobe does not process the dataset. Specify a dataset with a dataset organization of physical sequential or

BROWSE DATA SET ERROR. BROWSE DATA SET DEALLOCATION FAILED

Explanation: You were browsing a dataset allocated dynamically by Strobe/ISPF. The deallocation of the dataset failed. System Action: User Response: STR7167E Strobe/ISPF may not be able to allocate another dataset of the same type. If problems occur, notify the Strobe system programmer.

BROWSE DATA SET ERROR. BROWSE DATA SET ALLOCATION FAILED You attempted to browse a dataset but the dataset allocation failed.

Explanation:

System Action: Strobe could not allocate the browse output dataset and could not complete the browse function. User Response: STR7168E Notify the Strobe system programmer.

START/END DATE ERROR. START DATE CANNOT BE GREATER THAN END DATE You specified a starting date that is later than the ending date. Strobe/ISPF does not process the request. Enter dates with a valid range.

Explanation: System Action: User Response: STR7169E

UNABLE TO OPEN DATA SET. UNABLE TO OPEN OUTPUT DATA SET You specified a function that requires an open dataset.

Explanation:

Messages Produced by Strobe

3-179

System Action: User Response: STR7170E SELECTED

Strobe is unable to open the output dataset. Notify the Strobe system programmer.

INVALID COMBINATION. DATA SET NAMES CANNOT BE BOTH SPECIFIED AND

Explanation: You entered a name of a dataset for the Strobe log and also selected a name of a dataset from the list of names. System Action: Strobe/ISPF does not display messages from the Strobe log.

User Response: If you select from the list, clear the dataset name field. If you enter the name of a dataset, do not select a name from the list. STR7171E INDICATE LOG DATA SETS. INDICATE LOG DATA SETS OR END TO EXIT

Explanation: You pressed Enter without first selecting or entering the name of a dataset for the Strobe log. System Action: Strobe/ISPF does not display messages from the Strobe log.

User Response: To specify a log dataset, either enter the log dataset name or select the name from the list of names and then press Enter. If you do not wish to specify a log dataset, enter END to cancel. STR7173E FUNCTION MEMORY SHORTAGE. STROBE/ISPF COULD NOT GET MEMORY NEEDED FOR You specified a function that requires an internal table.

Explanation:

System Action: Strobe/ISPF could not build an internal table because sufficient virtual storage was not available. User Response: STR7175E FAILED Allocate more storage or notify the Strobe system programmer.

DYNAMIC ALLOCATION ERROR. RC=rc; ERC/IRC=erc/irc; OUTPUT LOG DEALLOCATION

Explanation: The operating system returned a non-zero return code while attempting to deallocate the output log dataset. The return code is rc, the error reason code is erc, and the information reason code is irc. System Action: Strobe keeps the dataset allocated, which may cause problems with further allocation requests. User Response: Notify the Strobe system programmer.

STR7176E DATA SET NAME REQUIRED. A DATA SET NAME MUST BE SPECIFIED WHEN OPTION 'C' IS SELECTED Explanation: You selected C, the copy option, from the Strobe - Log Utilities panel, but you did not specify a destination dataset name. System Action: User Response: STR7177E Strobe/ISPF does not process the request. Specify the dataset name to which you will copy.

INVALID FUNCTION. THE VALID FUNCTIONS ARE 'B', 'P', OR 'C' The function you specified is invalid. Strobe/ISPF does not process the option. Specify either B (browse), P (print), or C (copy).

Explanation: System Action: User Response: STR7178E 'KEEP'

INVALID DISPOSITION. THE VALID COPY DATA SET DISPOSITIONS ARE 'CATLG' AND

Explanation: The disposition that you entered in the DISP field is invalid. The valid dispositions are CATLG or KEEP. System Action: User Response: Strobe/ISPF does not allocate the dataset. Enter either CATLG or KEEP.

3-180

Strobe Messages Guide

STR7179E

VOLUME NOT SUPPLIED. VOLUME MUST BE SUPPLIED WITH DISPOSITION OF 'KEEP' You entered a disposition of KEEP in the DISP field without specifying a Strobe/ISPF does not allocate the dataset. Specify a volume or change the disposition to CATLG.

Explanation: volume. System Action: User Response: STR7180E

INVALID SPECIFICATION. VALID OPTIONS ARE 'Y', 'N', OR BLANK The selection you entered is invalid. Strobe/ISPF does not process the option. Enter either Y or N, or clear the field.

Explanation: System Action: User Response: STR7181E

INVALID NAME. ENTER VALID JOBNAME, USERID, STARTED TASK, OR BLANKS You specified the JOBNAME field incorrectly. Strobe/ISPF does not process the request.

Explanation: System Action:

User Response: Specify a job name with from one to eight alphanumeric or national characters. The first character must be alphabetic or national. The three national characters are @ # $. STR7182I COPY LOG COMPLETED. LOG EXTRACTS COPIED INTO DATA SET dsname Strobe successfully copied the specified portions of the Strobe log to dataset Strobe continues processing. None required.

Explanation: dsname. System Action: User Response: STR7183E

PRINT ALLOCATION FAILED. DYNAMIC ALLOCATION ERROR; RC=rc ERC/IRC=erc/irc

Explanation: The operating system returned a nonzero return code while attempting to allocate the print file. The return code is rc, the error reason code is erc, and the information reason code is irc. System Action: User Response: STR7184E Strobe/ISPF does not allocate the dataset. Notify the Strobe system programmer.

INVALID PRINT CLASS. PRINT CLASS prntclass INVALID; MUST BE ALPHANUMERIC The print class you coded is not alphabetic (A through Z) or numeric (0 Strobe/ISPF does not print messages from the Strobe log. Enter a valid print class.

Explanation: through 9). System Action: User Response: STR7185I

NO JOBS WITH LIST LIMITS. NO ACTIVE JOBS MATCH LIST LIMITS You specified list limits for the active job list. No active jobs match the active job listing criteria that you specified. If the jobs you want to measure are excluded, specify broader limits for the

Explanation: System Action: User Response: job list. STR7186I

PRINT LOG COMPLETED. LOG EXTRACT PRINTED TO OUTPUT CLASS outputclass You requested Strobe/ISPF to print messages from the Strobe log.

Explanation:

System Action: Strobe successfully printed the specified portions of the Strobe log to output class outputclass. User Response: STR7187E You can review the messages in the output class you specified.

NO TYPES SELECTED. AT LEAST ONE ACTIVE TYPE MUST BE SELECTED You did not specify a type of address space for the active job list. Strobe/ISPF does not display the active job list.

Explanation: System Action:

Messages Produced by Strobe

3-181

User Response: To select types of address spaces, enter Y next to one or more of the selection types. STR7188E INVALID CHARACTER FOUND. 'A' OR 'D' EXPECTED You entered an invalid character for a sort sequence. Strobe/ISPF does not process the request. Enter either A for ascending or D for descending.

Explanation: System Action: User Response: STR7190E AND 999

INVALID RETENTION PERIOD. RETENTION PERIOD MUST BE A NUMBER BETWEEN 0 You entered an invalid retention period. Strobe/ISPF does not process the request. Enter a value between 0 and 999.

Explanation: System Action: User Response:

STR7191E INVALID SMS CLASS. YOUR SMS CLASS SPECIFICATION IS SYNTACTICALLY INCORRECT Explanation: System Action: You entered invalid characters in one of the SMS CLASS fields. Strobe/ISPF does not process the request.

User Response: Specify a valid Storage Management Subsystem (SMS) class, and resubmit the request. STR7192E INVALID NUMBER. NUMBER SHOULD BE IN THE RANGE 1 - 12 You entered an invalid number for display order or sort column. Strobe/ISPF does not display the active job list. Enter a number in the range of 1 to 12.

Explanation: System Action: User Response: STR7193E

ALREADY SPECIFIED. THIS VALUE HAS ALREADY BEEN SPECIFIED IN THIS COLUMN

Explanation: The value you entered for display order or sort column is a duplicate of a value already entered. System Action: User Response: Strobe/ISPF does not display the active job list. Enter a unique number in the range of 1 to 12.

STR7194E INVALID CHARACTERISTICS. MAP DATA SET RECORD LENGTH MUST BE 36, FORMAT MUST BE FB Explanation: You specified a partitioned dataset with incorrect map dataset record length or record format. System Action: Strobe/ISPF does not process the Indexer request.

User Response: Specify a partitioned dataset with a record length of 36 and a record format of FB or choose a sequential dataset. STR7195E UNIT IS INVALID. VALID UNIT IS 1 TO 8 ALPHANUMERIC, SPECIAL OR NATIONAL CHARACTERS Explanation: System Action: You specified an invalid unit parameter in the UNIT field. Strobe/ISPF does not process the request.

User Response: Specify a valid unit parameter. It must be from 1 to 8 alphanumeric, special, or national characters. The three national characters are @ # $. The eleven special characters are blank,. / ) ( * & = +. STR7196E LOG RECORD IS TOO LONG. LENGTH OF LOG RECORD EXCEEDS THE CAPACITY OF THE RESERVED BUFFER Explanation: System Action: User Response: The message in the Strobe log exceeds the maximum limit of 255 characters. Strobe/ISPF does not display the message in the Strobe log. Notify the Strobe system programmer.

3-182

Strobe Messages Guide

STR7197E

INVALID SORT COLUMN. SORT COLUMN MUST BE IN THE RANGE 1 - 4

Explanation: At the Strobe - Request Group Sort panel, you specified an invalid value in one of the SORT COLUMN fields. Values must be in the range 1 - 4 for general users. System Action: User Response: Strobe does not process the request. Enter only valid values (1 - 4) in the SORT COLUMN fields.

STR7198E INVALID DATE SPECIFIED. THE DATE MUST BE GREATER THAN OR EQUAL TO THE CURRENT DATE Explanation: You entered an invalid date in the schedule for a measurement request or a request group. When you create a schedule, the start date and the end date of the schedule must be either the current date or a future date. System Action: Strobe/ISPF does not process the request.

User Response: Specify a valid date in the STARTING DATE or the ENDING DATE field on the Strobe - Request Scheduler panel. STR7199E INVALID OPTION. EXPECTED 'A' OR 'E'

Explanation: You specified an invalid option while customizing a measurement request or a request group schedule. System Action: Strobe/ISPF does not process the request.

User Response: In the OPT field on the Strobe - Request Scheduler panel, specify either A to add a specific date to the schedule, or E to exclude a specific date. STR7200E INVALID SCHEDULE. A REQ OR REQ GROUP CANNOT BE SCHEDULED BEYOND A YEAR FROM TODAY Explanation: You attempted to schedule a measurement request element or a request group for more than one year in the future from todays date. System Action: Strobe/ISPF does not process the request.

User Response: On the Strobe - Request Scheduler panel, ensure that the values in the STARTING DATE and ENDING DATE fields represent a time period of one year or less from todays date, or specify a value in the NUMBER OF WEEKS field that is one year or less from todays date. STR7201E NO DAY OF WEEK SELECTED. AT LEAST ONE DAY OF THE WEEK MUST BE SELECTED

Explanation: You attempted to schedule a measurement request or a request group but did not specify the days of the week on which you want the measurement session initiated. System Action: Strobe/ISPF does not process the request.

User Response: Enter a Y in the field under one or more of the days shown near the top of the Strobe - Request Scheduler panel, or create a customized list by completing the bottom portion of the panel. STR7203E DUPLICATE DATE SPECIFIED. THIS DATE AND TIME HAS ALREADY BEEN GENERATED IN THE WEEKLY LIST Explanation: You attempted to add an individual date to the weekly schedule for a measurement request or a request group. The date you specified, however, is already included in the weekly schedule. System Action: Strobe/ISPF does not process the request.

User Response: Ensure that the individual date is not included in the weekly schedule designated in the top section of the Strobe - Request Scheduler panel. STR7204E DATE/TIME DOES NOT EXIST. THIS DATE AND TIME DOES NOT EXIST IN THE GENERATED WEEKLY LIST Explanation: You attempted to exclude an individual date from the weekly schedule for a measurement request or a request group. The date and time you specified, however, does not exist in the weekly schedule. System Action: Strobe/ISPF does not process the request.

Messages Produced by Strobe

3-183

User Response: Ensure that the individual date is included in the weekly schedule designated in the top section of the Strobe - Request Scheduler panel. STR7205E CANNOT BUILD ADD COMMAND. NEED TO INCREASE REGION MEMORY SIZE ALLOCATED FOR THE PROGRAM Explanation: The ADD command that you are trying to create is too large for the region size that is set. System Action: User Response: Strobe/ISPF does not process the request. Logoff, increase your TSO region size and resubmit the request.

STR7206E DUPLICATE START TIME. THIS TIME HAS ALREADY BEEN SPECIFIED. DUPLICATES ARE NOT PERMITTED Explanation: You specified a duplicate starting time for a scheduled measurement request or a request group. System Action: Strobe/ISPF does not process the request.

User Response: Ensure that the times you have specified in the STARTING TIME(s) field of the Strobe - Request Scheduler panel are unique. STR7207E DUPLICATE ENTRY. THIS ENTRY HAS ALREADY BEEN SPECIFIED. DUPLICATES ARE NOT PERMITTED Explanation: You specified an individual date for a measurement request or a request group that is already included in the list of scheduled dates. System Action: Strobe/ISPF does not add the duplicate entry.

User Response: Ensure that the dates and times you specified in the list of individual dates at the bottom of the Strobe - Request Scheduler panel are unique. STR7208S TOO MANY ENTRIES. NUMBER OF UNIQUE DATES > STROBE/ISPF LIMIT (12). OPTION UNAVAILABLE Explanation: You are attempting to change the schedule for a request that has more than 12 dates on the bottom of the Strobe - Request Scheduler panel. This will result in a loss of data. System Action: panel. User Response: STR7209E Strobe/ISPF does not allow you to access the Strobe - Request Scheduler To change the schedule, use the Strobe Command interface.

INVALID OPTION. VALID ENTRIES ARE 'A' OR BLANK

Explanation: You excluded an individual date from the weekly schedule for a measurement request or a request group. However, no weekly schedule is specified. System Action: Strobe/ISPF does not process the request.

User Response: Enter an A in the OPT field at the bottom of the Strobe - Request Scheduler panel to add an individual schedule date, or create a weekly schedule. STR7210E INVALID RETRY INTERVAL. RETRY INTERVAL MUST BE IN THE RANGE OF 0 - 60

Explanation: You specified a retry interval for an Add Active measurement request or a request group. However, the value you specified in the RETRY INTERVAL field is invalid. This field represents the time interval, in minutes, that Strobe waits to resubmit the request. System Action: Strobe/ISPF does not process the request.

User Response: Enter a value in the range of 0 - 60 in the RETRY INTERVAL field of the Strobe - Request Scheduler panel. STR7211E INVALID TIME SPECIFIED. HOUR RANGE MUST BE 0 - 23 / MINUTE RANGE MUST BE 0 - 59 Explanation: While creating the schedule for a measurement request or a request group, you specified an invalid time either in the weekly schedule or the list of individual dates and times. System Action: Strobe/ISPF does not process the request.

User Response: Ensure that the hour and minute values that you entered on the Strobe Request Scheduler panel are valid.

3-184

Strobe Messages Guide

STR7212E NUM WEEKS/END DATE ERROR. SPECIFY EITHER THE NUMBER OF WEEKS OR THE END DATE; NOT BOTH Explanation: While creating the schedule for a measurement request or a request group, you specified both the end date and the number of weeks. System Action: User Response: STR7213E Strobe/ISPF does not process the request. Specify either an ending date or the number of weeks but not both.

INVALID ENTRY. THIS FIELD MUST BE BLANK IF NO WEEKDAY IS SELECTED

Explanation: You specified a value in one of the scheduling fields on the Strobe - Request Scheduler panel, but did not specify a day of the week on which the schedule will run. System Action: Strobe/ISPF does not process the request.

User Response: Enter a Y in one or more of the weekday fields shown near the top of the Strobe - Request Scheduler panel. STR7214E START TIME NOT SPECIFIED. AT LEAST ONE START TIME MUST BE SPECIFIED

Explanation: You attempted to schedule a measurement request or a request group but did not specify the time at which you want the measurement session initiated. System Action: Strobe/ISPF does not process the request.

User Response: Enter at least one time in the STARTING TIME(s) field shown near the top of the Strobe - Request Scheduler panel. STR7215E START DATE NOT SPECIFIED. START DATE MUST BE SPECIFIED

Explanation: You specified a day or days of the week on which to schedule a measurement request or a request group but did not specify the date on which you want the schedule to begin. System Action: Strobe/ISPF does not process the request.

User Response: Enter a date in the STARTING DATE field shown near the top of the Strobe Request Scheduler panel. STR7216E INVALID DATE FORMAT. MONTH: 1-12 / DAY: DEPENDS ON MONTH / YEAR: UP TO 1 YEAR FROM TODAY Explanation: While creating a schedule for a measurement request or a request group, you specified an unacceptable value in a date field. System Action: Strobe/ISPF does not process the request.

User Response: Ensure that the month, day, and year values that you entered are valid. The date must be in the format that the Strobe system programmer specified in the PARMLIB library when installing Strobe. If the Strobe system programmer did not change the specified date format, the default value is dd/mm/yyyy. STR7217E NUM OF WEEKS NOT ENTERED. EITHER THE NUMBER OF WEEKS OR AN END DATE MUST BE SPECIFIED Explanation: You attempted to schedule a measurement request or a request group but did not specify either the number of weeks or the ending date. System Action: Strobe/ISPF does not process the request.

User Response: Enter a date in the ENDING DATE field or enter a value in the NUMBER OF WEEKS field that is one year or less from todays date. STR7218E INVALID NUMBER OF WEEKS. NUMBER OF WEEKS MUST BE IN THE RANGE 1 - 52

Explanation: While creating the schedule for a measurement request or a request group, you specified an invalid number in the NUMBER OF WEEKS fields of the Strobe - Request Scheduler panel. System Action: User Response: todays date. Strobe/ISPF does not process the request. Enter a value in the NUMBER OF WEEKS field that is one year or less from

Messages Produced by Strobe

3-185

STR7219E

INVALID RETRY ATTEMPTS. RETRY ATTEMPTS MUST BE IN THE RANGE OF 0 - 24

Explanation: You specified an invalid entry in the RETRY ATTEMPTS field. This field represents the number of attempts that Strobe will make to resubmit the request. System Action: Strobe/ISPF does not process the request.

User Response: Enter a value in the range of 0 - 24 in the RETRY ATTEMPTS field of the Strobe - Request Scheduler panel. STR7220E INPUT REQUIRED. ENTER DATA ON THE PANEL OR PRESS END TO CANCEL You did not specify required data on the panel. Strobe/ISPF does not process the request. Enter data or press End to exit the panel.

Explanation: System Action: User Response: STR7221I

NO SYSTEMS AVAILABLE. NO SYSTEMS CAN BE FOUND IN THE SYSPLEX

Explanation: On the Strobe - Add Active or Strobe - Add Queued panel, you attempted to list all the systems in the sysplex by leaving the SYSTEM field blank. Strobe, however, found no systems in the sysplex. System Action: Strobe/ISPF does not process the request.

User Response: Notify the Strobe system programmer. The system programmer can check the Strobe-XCF group to ensure that it is set up correctly. STR7222E SCHEDULE NO SCHEDULE GENERATED. THERE ARE NO DATE AND TIME ENTRIES IN THE You excluded all dates from the weekly schedule. Strobe/ISPF does not process the request.

Explanation: System Action:

User Response: If you wish to create a schedule for the measurement request or the request group, complete the Strobe - Request Scheduler panel according to the instructions in the Strobe User Guide. STR7223E INVALID SYSTEM NAME. ENTER UP TO 8 ALPHANUMERIC CHARACTERS You have entered an invalid system name in the SYSTEM field. Strobe does not process the request. Enter up to 8 alphanumeric characters in the SYSTEM field.

Explanation: System Action: User Response:

STR7224E INVALID DAY(S) AND DATES. THE SELECTED DAYS OF THE WEEK ARE NOT IN THE SPECIFIED DATE RANGE Explanation: While creating the schedule for a measurement request or a request group, you selected a weekday that is not within the range specified by the STARTING DATE and ENDING DATE fields on the Strobe - Request Scheduler panel. System Action: Strobe/ISPF does not process the request.

User Response: Review your selections and adjust either your weekday selection or the date range specified by the STARTING DATE and ENDING DATE fields. STR7225I GROUP SUBMIT SUCCESSFUL. GROUP SUBMIT(S) SUCCESSFUL

Explanation: All the request groups that you selected on the Strobe - Request Group Processing panel have been submitted for processing. System Action: Strobe continues processing.

User Response: None required, though to verify that all the request groups were processed, refer to the Strobe log. If the request group was submitted with a schedule, check the Strobe log dataset after the scheduled date and time. STR7226E INVALID STEP NAME. ENTER A VALID STEP OR STEP.PROCSTEP NAME

Explanation: You entered an invalid step name in the STEP field on the Strobe - Add Queued Request panel or on the Strobe - Add Queued Request - Multiple Steps panel. System Action: Strobe/ISPF does not accept the value that you entered in this field.

3-186

Strobe Messages Guide

User Response:

Enter a valid name.

STR7227E INVALID STEP NUMBER. ENTER VALID STEP NUMBER (1-255) OR RANGE (XXX-YYY) WHERE YYY > XXX Explanation: You entered an invalid step number on the Strobe - Add Queued Request Multiple Steps panel. System Action: User Response: Strobe/ISPF does not process the request. Enter a valid number or range of numbers.

STR7228E INVALID START TIME. START TIME MUST BE AT LEAST 3 MINUTES LATER THAN THE CURRENT TIME Explanation: The start time that you entered is not at least 3 minutes later than the current time. When you are creating a schedule for a measurement request or a request group, the start time of the schedule must be at least 3 minutes later than the current time. System Action: Strobe/ISPF does not process the request.

User Response: Specify a valid time in the STARTING TIME field on the Strobe - Request Scheduler panel. STR7229W CON SET ERROR - ENTER HELP. CONCURRENT SET ERROR - NEW OWNER MUST EDIT GROUP groupname Explanation: There is an error in the concurrent set in group groupname, and the owner specified by the groups owner must edit the group to correct the error. The error can be: there is no trigger request, there is more than one trigger request, or there are no related requests. System Action: User Response: error. Strobe continues processing. The owner specified by the groups owner must edit the group to correct the

STR7230W GROUP WILL BE DELETED. ENTER TO DELETE ALL ELEMENTS AND THE GROUP OR END TO CANCEL Explanation: On the Strobe - Request Group Elements panel, you specified that one or more request group elements be deleted. Because you are deleting all the elements in the request group, the request group itself will also be deleted. System Action: group. Strobe/ISPF will delete both the request group elements and the request

User Response: To delete both the request group elements and the request group, press Enter. Otherwise, press End to exit the panel without making any changes. STR7231I NO GROUPS FOUND. NO GROUPS HAVE BEEN CREATED

Explanation: Strobe/ISPF displays this message when you select Option G (REQUEST GROUPS) from the Strobe Options menu or select SAVE REQUEST IN A GROUP from the Strobe - Add Queued Request panel or the Strobe - Add Active Request panel, but you have not yet created any groups. System Action: Strobe continues processing.

User Response: Enter the name of a new group to create a group or press End to return to the previous panel. STR7232E INVALID GROUP NAME. CHECK THE SPECIFICATION IN THE GROUP NAME FIELD

Explanation: The value that you specified in the GROUP NAME field on the Strobe - Request Group Processing panel or the Strobe - Save Request In Group panel is invalid. System Action: Strobe does not create the request group.

User Response: Enter an acceptable value in the GROUP NAME field. Valid entries cannot exceed 18 characters in length and can not include embedded blanks. STR7233E INVALID LINE OPTION. VALID OPTIONS ARE 'C', 'D', 'E', 'L', 'U', AND 'T'

Explanation: You specified an invalid line option in the OPTION column of the Strobe Request Group Processing panel. Valid options are C (copy), D (delete), E (edit), L (list), U (submit), and T (submit with schedule).

Messages Produced by Strobe

3-187

System Action: User Response: STR7234E

Strobe/ISPF does not process the request. Specify one of the valid options in the OPTION column.

DUPLICATE GROUP NAME. THE SPECIFIED GROUP NAME ALREADY EXISTS

Explanation: You attempted to create a new request group or save a request in a new group. However, a request group already exists with the name you specified. System Action: User Response: Strobe/ISPF does not process the request. Choose a unique name for the request group.

STR7235E PROCESSING CONFLICT. YOU CANNOT ENTER A NEW GROUP AND USE LINE OPTIONS AT THE SAME TIME Explanation: You attempted to create a new request group or save a request in a new group. However, you also entered one or more of the line options in the OPTION column on the panel. System Action: Strobe/ISPF does not create the request group.

User Response: Either enter a group name or enter a line option in the OPTION column, but do not enter both. STR7236E GROUP NOT CREATED. THE SPECIFIED GROUP HAS NOT BEEN CREATED - NO ELEMENTS WERE ADDED Explanation: You attempted to create a new request group on the Strobe - Request Group Processing panel, but you did not create any request group elements for the group. System Action: Strobe/ISPF does not create the request group. Request groups must have at least one request group element to be saved. User Response: Attempt to create the request group again, ensuring that you have created at least one request group element for the group by entering A or Q on the option line of the Strobe - Request Group Elements panel and completing the subsequent panel. If you specify A, the subsequent panel is the Strobe - Create an 'Add Active' Element panel. If you specify Q, the subsequent panel is the Strobe - Create an 'Add Queued' Element panel. STR7237E concurrent CONCURRENT SET ERROR. EXACTLY ONE TRIGGER MUST BE SPECIFIED FOR SET

Explanation: You have more than one trigger request in a concurrent set. The concurrent set name is identified by concurrent. System Action: Strobe/ISPF does not allow you to exit the Strobe - Request Group Elements panel without correcting the problem. User Response: concurrent set. STR7238E concurrent Specify only one request group element as the trigger request for the

CONCURRENT SET ERROR. AT LEAST ONE NON-TRIGGER MUST BE SPECIFIED FOR SET

Explanation: You do not have a non-trigger (related) request in the concurrent set. The concurrent set name is identified by concurrent. System Action: Strobe/ISPF does not allow you to exit the Strobe - Request Group Elements panel without correcting the problem. User Response: concurrent set. Specify at least one request group element as a related request for the

STR7239I GROUP [MERGED |DELETED|COPIED|EDITED|CREATED] GROUP(S) [MERGED INTO EXISTING GROUP: groupname| DELETED|COPIED INTO NEW GROUP: groupname|EDITED| CREATED: groupname] Explanation: The group was either merged or copied into groupname, was edited or deleted entirely, or was created with the name groupname, dependent upon your request. System Action: User Response: Strobe/ISPF successfully processed the request. None required.

3-188

Strobe Messages Guide

STR7241I

ELEMENT ADDED. AN ELEMENT HAS BEEN ADDED TO GROUP: groupname You added a request group element to request group groupname from:

Explanation:

the Strobe - Create an 'Add Active' Element panel or the Strobe - Create an 'Add Queued' Element panel
System Action: Strobe/ISPF adds the request group element to the request group and continues processing. User Response: STR7242I None required.

ELEMENT EDITED. AN ELEMENT HAS BEEN MODIFIED IN GROUP: groupname

Explanation: You edited a request group element in request group groupname from either the Strobe - Edit an 'Add Active' Element panel or the Strobe - Edit an 'Add Queued' Element panel. System Action: User Response: STR7243E Strobe/ISPF modifies the request group element. None required.

INVALID LINE OPTION. VALID OPTIONS ARE 'C', 'D', 'E', AND 'V'

Explanation: You specified an invalid line option in the OPT column of the Strobe - Request Group Elements panel. Valid options are C (copy), D (delete), E (edit), and V (view). System Action: User Response: STR7244E Strobe/ISPF does not process the selection. Specify one of the valid line options in the OPT column.

INVALID LINE OPTION. VALID OPTIONS ARE 'S' AND 'L'

Explanation: You specified an invalid line option in the OPTION column of the Strobe - Save Request In a Group panel. Valid options are S (save) and L (list). System Action: User Response: Strobe/ISPF does not process the request. Specify one of the valid line options in the OPTION column.

STR7246W SCHEDULE WILL BE REMOVED. THE SCHEDULE WILL BE REMOVED FROM REQUEST BEING SAVED INTO A GROUP Explanation: You specified a Y in the SAVE REQUEST IN GROUP field of the Strobe - Add Active Request or the Strobe - Add Queued Request panel. However, you also specified that this request be submitted with a schedule. System Action: Strobe/ISPF submits the request with the schedule, but removes the schedule from the request before saving it into the request group. The request being saved into the request group will not retain the schedule. User Response: STR7247E SET NAME None required.

INVALID CONCURRENT NAME. 'SCHEDULE' CAN NOT BE USED AS THE CONCURRENT

Explanation: SCHEDULE, the value that you specified in the CONCURRENT SET NAME field of the Strobe - Concurrent Request panel, is invalid. System Action: Strobe does not create the concurrent set.

User Response: Enter an acceptable value in the CONCURRENT SET NAME field. Valid entries cannot exceed 8 characters in length. Note that the word SCHEDULE is not a valid name for a concurrent set. STR7248E INVALID CONCURRENT NAME. CHECK THE SPECIFICATION IN THE CONCURRENT SET NAME FIELD Explanation: The value that you specified in the CONCURRENT SET NAME field of the Strobe - Concurrent Request panel is invalid. System Action: Strobe does not create the concurrent set.

User Response: Enter an acceptable value in the CONCURRENT SET NAME field. Valid entries cannot exceed 8 characters in length.

Messages Produced by Strobe

3-189

STR7249E

INVALID LINE OPTION. 'V' IS THE ONLY VALID LINE OPTION

Explanation: You specified an invalid line option in the OPT column of the Strobe - List Group Elements panel. The only valid line option on this panel is V (view). System Action: User Response: Strobe/ISPF does not process the request. Specify V in the OPT column.

STR7250E GROUP INVALID - ENTER HELP. CONCURRENT SET ERROR. EDIT GROUP groupname OWNER ownerid Explanation: There is an error in a concurrent set within group groupname with owner ownerid. Either there is more than one trigger, there is no trigger, or there are no related (nontrigger) requests. System Action: Strobe/ISPF does not allow you to exit the Strobe - Request Group Processing panel without correcting the problem. User Response: Edit the group identified by groupname and owner ownerid. Specify only one request group element as the trigger request for the concurrent set and specify at least one request group element as a related (non-trigger) request for the concurrent set. STR7251E SYSTEM NAME NOT FOUND. SYSTEM IS NOT A GROUP MEMBER

Explanation: The value that you specified on the SYSTEM field is not the name of an existing member of the Strobe-XCF group. Either the system is not included in the installations sysplex definition, or the system is defined to the sysplex, but the correct version of Strobe was not started on the system. System Action: Strobe does not process the request.

User Response: Enter a valid system name. To find the system names in the sysplex, leave the SYSTEM field blank and press Enter. STR7252E MORE THAN ONE SELECTED. SELECT ONLY ONE SYSTEM

Explanation: You selected more than one system on the Strobe - System Selection List panel for an Add Active request. System Action: User Response: STR7253E PANEL Strobe does not process the request. Resubmit the request and specify only one system.

S AND E CONFLICT. 'S' AND 'E' ARE MUTUALLY EXCLUSIVE: REMOVE ONE FROM THE You cannot choose S (select) and E (exclude) at the same time. Strobe does not process the request. Choose either S or E (but not both), or press End to exit the panel.

Explanation: System Action: User Response: STR7254E

NO SELECTION MADE. MAKE A SELECTION OR PRESS END TO EXIT You did not select an option from the Strobe - System Selection List panel. Strobe does not process the request. Choose an option or press End to exit the panel.

Explanation: System Action: User Response:

STR7255W ONLY 1ST 40 WILL BE KEPT. MORE THAN 40 ENTRIES SELECTED, ONLY FIRST 40 KEPT AS DEFAULT VALUES Explanation: You selected S or excluded E more than 40 entries on the Strobe - System Selection List panel. System Action: User Response: Although Strobe displays more than 40 systems, it will save only 40 values. None required.

STR7256E INVALID SYSTEM NAME. ENTER UP TO 8 ALPHANUMERIC CHARACTERS, THE 1ST CANNOT BE NUMERIC Explanation: System Action: The system name that you specified is invalid. Strobe does not process the request.

3-190

Strobe Messages Guide

User Response: Enter a valid system name. The system name can be up to 8 alphanumeric or national characters, and the first character cannot be numeric. STR7257E *LIST NOT ACCEPTED. CLEAR THE FIELD & PRESS ENTER TO SELECT A LIST FROM THE NEXT SCREEN Explanation: System Action: Strobe was not able to find the list that the *LIST value represented. Strobe does not process the request.

User Response: Clear the SYSTEM field on the Strobe - Add Queued Request panel and press Enter to access the Strobe - System Selection List panel. Indicate the systems on which you want to run the measurement, either by entering S (select), or from which you want to exclude measurement, by entering E (exclude). STR7258E *LIST NOT ACCEPTED. CLEAR PGM & STEP FIELDS, PRESS ENTER TO INPUT A LIST ON NEXT SCREEN Explanation: You specified the value *LIST in the PROGRAM or STEP field of the Strobe Add Queued Request panel. System Action: Strobe/ISPF does not accept the value you entered in this field.

User Response: To access the Strobe - Add Queued Request - Multiple Steps panel and specify a list of program names, step names, step numbers, or all steps, clear the PROGRAM and STEP fields and press Enter. STR7259E INVALID SPACE UNIT. DEFAULT WORKSPAC PARAMETER IS INVALID, 'TRACK' SUBSTITUTED Explanation: System Action: You entered an invalid value for the UI_WORKSPAC parameter. Strobe will use the default value of TRACK and process the request.

User Response: Contact your Strobe system programmer to enter a valid value for the UI_WORKSPAC parameter in the Strobe parmlib member. STR7260I ELEMENT [COPIED|EDITED]. THE ELEMENT HAS BEEN [COPIED|EDITED] The element was successfully copied or edited. Strobe successfully processed the request. None required.

Explanation: System Action: User Response: STR7261I

ELEMENT CREATED. A NEW ELEMENT HAS BEEN ADDED TO GROUP groupname Strobe successfully created an element and added it to the group groupname. Strobe successfully processed the request. None required.

Explanation: System Action: User Response:

STR7262W SYSTEM PARAMETER. SYSTEM PARAMETER SPECIFIED IN REQUEST(S) MAY NOT BE SUPPORTED Explanation: For a batch-submission request, you have supplied a SYSTEM parameter. If the system you are sending the request to is not a member of a Strobe sysplex, the system will not recognize the system parameter. System Action: If the system to which you are sending the request does not support multisystem, Strobe will fail with a syntax error. User Response: If the system to which you are sending the request does not support multisystem, go to the JOB STREAM option on the Strobe Options panel, select Option 2 and remove the system parameter from the generated job control statements. STR7263E AUTHORIZATION FAILURE. NOT AUTHORIZED TO EDIT, SUBMIT, OR SAVE A REQUEST IN THIS GROUP Explanation: Users with administrator privileges receive this message when they attempt to edit, submit, or save a request into a group that they did not create. For groups that they did not create, administrators can only copy, list, or delete. System Action: Strobe does not process the request.

Messages Produced by Strobe

3-191

User Response: You cannot submit, edit, or save requests in a group that you did not create. If you want to submit, edit, or save these requests, you must first copy the group to your user ID. STR7264E INVALID COMBINATION. WHEN *LIST IS USED IN PROGRAM OR STEP FIELD THE OTHER MUST BE BLANK Explanation: The combination of entries on this panel is invalid. Either you entered *LIST in one field and data in the other field, or the system returned *LIST in one field and you entered data in the other field. System Action: User Response: STR7265E NAME Strobe/ISPF does not process the request. Clear one of the fields.

INVALID COMBINATION. A STEP NUMBER CANNOT BE SPECIFIED WITH A PROGRAM

Explanation: The combination of entries on this panel is invalid. The PROGRAM field contains a program name and the STEP field contains a step number. System Action: Strobe/ISPF does not process the request.

User Response: Clear either the PROGRAM field or the STEP field. You cannot specify both a program name and a step number. STR7266E INVALID COMBINATION. WHEN *ALL IS USED IN THE STEP FIELD THE PROGRAM FIELD MUST BE BLANK Explanation: The combination of entries on this panel is invalid. The PROGRAM field contains a program name and the STEP field contains *ALL. System Action: User Response: Strobe/ISPF does not process the measurement request. Clear the PROGRAM field and enter *ALL in the STEP field.

STR7267E INVALID COMBINATION. JOBS CANNOT BE SELECTED IF 'Y' IS ENTERED IN CHANGE LIST OR DISPLAY Explanation: You entered an invalid combination. You cannot enter a Y in either the CHANGE LIST LIMITS field or the CHANGE DISPLAY FORMAT field and also enter an S in the SEL column to select a job name to measure. System Action: Strobe/ISPF does not process the request.

User Response: To select one or more job names to measure, clear both the CHANGE LIST LIMITS field and the CHANGE DISPLAY FORMAT field and enter one or more Ss in the SEL column. To limit the active jobs displayed, enter a Y in the CHANGE LIST LIMITS field. To change the information displayed, enter a Y in the CHANGE JOB DISPLAY FORMAT field. You may enter a Y in both the CHANGE LIST LIMITS field and the CHANGE JOB DISPLAY field at the same time, but cannot combine these with one or more Ss in the SEL column. STR7268E INVALID START DATE. THE SCHEDULE START DATE CANNOT BE LATER THAN ONE YEAR FROM TODAY Explanation: You attempted to schedule a measurement request or a request group with a start date that is more than one year from todays date. System Action: Strobe/ISPF does not process the request.

User Response: On the Strobe - Request Scheduler panel, ensure that the STARTING DATE field is one year or less from todays date. STR7269I X. ELEMENTS DELETED. ELEMENT(S) HAVE BEEN DELETED Strobe has deleted one or more elements. x represents the number of elements Strobe successfully processed the request. None required.

Explanation: deleted. System Action: User Response: STR7270E

AUTO PROFILE NOT SELD. AUTO PROFILE WAS NOT PART OF THIS REQUEST

Explanation: You selected B for Browse Auto Profile from the Strobe - Status panel, but you did not specify AUTO PROFILE CREATION for this measurement request.

3-192

Strobe Messages Guide

System Action: User Response: STR7271E

Strobe/ISPF does not process the request. To create a Performance Profile, type P to the left of your request.

SAMPLE FILE NOT CLOSED. AUTO PROFILE REQUIRES CLOSED SAMPLE FILE

Explanation: You selected B for Browse Auto Profile from the Strobe - Status panel, but the measurement session has not yet produced a closed sample file from which to automatically create a Performance Profile. System Action: User Response: STR7272E Strobe/ISPF does not process the request. Select the option later, once Strobe has produced a closed sample file.

INVALID SAMPLE FILE. SAMPLE FILE HAS INVALID FORMAT The sample file name does not have the required Strobe format. Strobe/ISPF does not process the request.

Explanation: System Action:

User Response: Notify the Strobe system programmer. If necessary, contact Compuware Customer Support. STR7273E DATA SET NOT AVAILABLE. AUTO PROFILE DATA SET NOT FOUND. VERIFY THE SUBMITTED JOB Explanation: System Action: Strobe/ISPF is unable to locate the Performance Profile dataset. Strobe/ISPF does not process the request.

User Response: Verify that the JCL is correct and that the job has run. Retry Option B Browse Auto Profile. If the problem persists, contact the Strobe system programmer. STR7274E INVALID SORT COLUMN. SORT COLUMN MUST BE IN THE RANGE 1 - 5

Explanation: At the Strobe - Request Group Sort panel, you specified an invalid value in the SORT COLUMN field. Values must be in the range of 1 - 5 for users with administrative authority. System Action: User Response: Strobe does not process the request. Enter only valid values (1 - 5) in the SORT COLUMN fields.

STR7275E INVALID SORT SEQUENCE. SORT SEQUENCE MUST BE BLANK IF SORT COLUMN IS NOT SPECIFIED Explanation: At the Strobe - Request Group Sort panel, you specified a value in the SORT SEQUENCE column but did not specify a value in the SORT COLUMN. System Action: Strobe does not process the request.

User Response: To specify a value of A (ascending) or D (descending) in the SORT SEQUENCE column, you must specify a value in the corresponding SORT COLUMN field. STR7278E INVALID OWNERID. ENTER VALID OWNERID, PATTERN, OR BLANKS You specified an invalid owner ID in the OWNERID field. Strobe/ISPF does not process the request.

Explanation: System Action:

User Response: Enter a valid owner ID in the OWNERID field. To view multiple owner IDs, enter a pattern or blanks. STR7280E INVALID SYSTEM NAME. *ALL OR *LIST IS INVALID FOR ACTIVE REQUESTS/ACTIVE GROUP ELEMENTS Explanation: You specified *ALL or *LIST in the SYSTEM field for an ADD ACTIVE request or an ACTIVE GROUP ELEMENT. For an ADD ACTIVE request or an ACTIVE GROUP ELEMENT you must specify a system name in the SYSTEM field or leave the field blank. System Action: Strobe does not process the request.

User Response: Specify the name of a system or leave the field blank and press Enter. If you leave the field blank, select only one of the systems from the list that appears on the subsequent Strobe - System Selection List panel.

Messages Produced by Strobe

3-193

STR7281E CANNOT SCHEDULE. CANNOT SCHEDULE FROM 23:57 TO 23:59 WITH START DATE = CURRENT DATE Explanation: For internal processing, Strobe requires a three-minute margin between the time you submit a measurement request and the time at which the measurement request is scheduled to execute. Because of this constraint, Strobe cannot process a request submitted during the last three minutes of the day (from 23:57 to 23:59) that is scheduled to execute before the end of the same day (either on or before 23:59). System Action: Strobe does not process the request.

User Response: To schedule a request to execute during the last three minutes of the day (from 23:57 to 23:59) submit the request earlier than three minutes before the end of the day (earlier than 23:57). This only applies to requests that are scheduled to execute on the same day that they are submitted. STR7282E INVALID SPECIFICATION. ENTER 'A' FOR AM OR 'P' FOR PM

Explanation: A and P are the only characters that are valid for this field, and you entered a character that is not an A or a P. System Action: User Response: Strobe does not process the request. Enter A for A.M. or P for P.M.

STR7283E INVALID TIME SPECIFIED. HOUR MUST BE 1 - 12 | MINUTE MUST BE 0 - 59| AM/PM MUST BE A OR P Explanation: The time that you specified is invalid. In the hour field you must enter a number from 1 to 12. In the minute field you must enter a number from 0 to 59. In the AM/PM field you must enter either A (for A.M.) or P (for P.M.). System Action: Strobe does not process the request.

User Response: Because you have chosen the AM/PM format, you must enter a number from 1 to 12 in the hour field. Enter a number from 0 to 59 in the minute field. Enter A (for A.M.) or P (for P.M.) in the AM/PM field. STR7284E INVALID SPECIFICATION. IMS DC MUST BE SET TO 'Y' FOR THE IMS CAPTURE OPTION TO BE USED Explanation: You requested an IMS processing option without selecting the IMS data collector on the Strobe - Data Collectors panel. System Action: invoked. Strobe cannot process any IMS options until the IMS data collector is

User Response: Specify Y next to the IMS data collector on the Strobe - Data Collectors panel. STR7285E INVALID SPECIFICATION. DB2 DC MUST BE SET TO 'Y' FOR THE DB2 CAPTURE OPTION TO BE USED Explanation: You requested a DB2 processing option without selecting the DB2 data collector on the Strobe - Data Collectors panel. System Action: invoked. User Response: panel. Strobe cannot process any DB2 options until the DB2 data collector is Specify Y next to the DB2 data collector on the Strobe - Data Collectors

STR7286E PROCESSING CONFLICT. YOU CANNOT CHANGE THE OWNER MASK AND USE LINE OPTIONS AT THE SAME TIME Explanation: You attempted to change the owner mask, and you entered one or more of the line options in the OPTION column on the panel. System Action: Strobe does not process the request.

User Response: Either change the owner mask or enter a line option in the OPTION column, but do not attempt to do both.

3-194

Strobe Messages Guide

STR7287E PROCESSING CONFLICT. YOU CANNOT CHANGE SORT CRITERIA AND USE LINE OPTIONS AT THE SAME TIME Explanation: You attempted to change the criteria used for sorting, and you entered one or more of the line options in the OPTION column on the panel. System Action: Strobe does not process the request.

User Response: Either change the sort criteria or enter a line option in the OPTION column, but do not attempt to do both. STR7288E INVALID TRANSACTION. ENTER A VALID TRANSACTION. A WILDCARD IS PERMITTED

Explanation: You entered a transaction that is syntactically incorrect. The transaction name must consist of from 18 of the following alphanumeric or national characters: AZ, #, $, @, 0 9. The first character may not be numeric, but it may be a period. The last character may be an asterisk (*), which acts as a wildcard. System Action: User Response: paragraph. STR7289E Strobe will not process the request. Enter a transaction name that follows the rules given in the Explanation

INVALID DBRM. ENTER A VALID DBRM. A WILDCARD IS PERMITTED

Explanation: You entered a DBRM name that is syntactically incorrect. The DBRM name must consist of from 18 of the following alphanumeric or national characters: AZ, #, $, @, 0 9. The first character may not be numeric. The last character may be an asterisk (*), which acts as a wildcard. System Action: User Response: paragraph. Strobe will not process the request. Enter a DBRM name that follows the rules given in the Explanation

STR7290E INVALID STEP NAME. ENTER VALID STEP OR STEP.PROCSTEP. A WILDCARD IS PERMITTED Explanation: You entered a step or step.procstep name that is syntactically incorrect. The step name must consist of from 18 of the following alphanumeric or national characters: AZ, #, $, @, 09. The first character may not be numeric. The last character may be an asterisk, which acts as a wildcard. A single asterisk in the field is valid and it also acts as a wildcard. System Action: Strobe will not process the request.

User Response: Enter a step or step.procstep name that follows the rules given in the Explanation paragraph. STR7291E INVALID HISTORIAN. ENTER A VALID HISTORIAN. A WILDCARD IS PERMITTED

Explanation: You entered a historian name that is syntactically incorrect. The historian name must consist of from 18 of the following alphanumeric or national characters: AZ, #, $, @, 09. The first character may not be numeric. The last character may be an asterisk, which acts as a wildcard. System Action: User Response: STR7292E Strobe will not process the request. Enter a historian name that follows the rules given in Explanation.

REQUIRED FIELD. SORT ORDER AND SEQUENCE FIELDS MUST BE ENTERED IN PAIRS

Explanation: You did not enter a sort order or sort sequence in pairs. When you specify a sort order for one of the display titles, you must also specify a sequence for the sorteither A (ascending) or D (descending). Also, if you specify a sequence for a display title, you must indicate the order in which to sort it. System Action: Strobe does not process the request.

User Response: For each value that you select in the DISPLAY TITLE column, you must enter both a sort order and a sort sequence. STR7293E RANGE INVALID SORT ORDER. SORT ORDER FIELD IS EITHER NOT NUMERIC OR OUT OF

Explanation: One or more of the values that you specified for sort order is invalid. The sort order must be a numeric value in the range specified on the panel.

Messages Produced by Strobe

3-195

System Action: User Response: STR7294E

Strobe does not process the request. Enter a valid sort order.

INVALID FUNCTION. VALID OPTIONS ARE 'P' AND 'E'

Explanation: The only valid options are P to print the history data or E to export the history data. System Action: User Response: STR7296E Strobe does not process the request. Enter either P to print or E to export the history data.

INVALID PRINT CLASS. THE PRINT CLASS MUST BE ALPHANUMERIC You entered a print class that is not alphanumeric (AZ or 09). Strobe does not process the request. Enter a print class that adheres to the rules defined in the Explanation.

Explanation: System Action: User Response:

STR7297E ONE PRINT VALUE REQUIRED. ENTER EITHER A PRINT DATA SET NAME OR A SYSOUT CLASS, NOT BOTH Explanation: You entered both a dataset name and a sysout class on the PRINT OPTIONS section of the Strobe - History - Print/Export panel. You cannot choose both. System Action: Strobe does not process the request.

User Response: To print to a dataset, enter only a dataset name. To print to a sysout class, enter only a sysout class. STR7298E INVALID FREQUENCY. THE ANNUAL FREQUENCY VALUE MUST BE IN THE RANGE OF (0 - 9999), (0 - 99999999) Explanation: You entered an annual frequency value that is not in the range of (09999) for step views or (099999999) for DBRM or transaction views. System Action: User Response: STR7299E Strobe does not process the request. Enter a numeric value for annual frequency within the required range.

HISTORY DISABLED. THE STROBE HISTORY FUNCTION IS DISABLED The Strobe history manager is not functioning. Strobe will not display history Strobe continues processing but does not process history related requests.

Explanation: data. System Action:

User Response: An ABEND or an error has occurred either during Strobe installation or while accessing history data. Contact the Strobe system programmer to ensure that the correct parameters were specified during Strobe installation. If the problem persists, contact Compuware Customer Support. STR7300E NO RECORDS FOUND. NO HISTORY RECORDS WERE FOUND FOR THE SPECIFIED FILTER CRITERIA Explanation: There are no measurement session history records that match the filter criteria that you specified. System Action: User Response: STR7301E BOTH Strobe does not process the request. Enter different filter criteria.

COMMAND CONFLICT. ENTER EITHER A PANEL COMMAND OR LINE OPTIONS, NOT

Explanation: You entered both a panel command and one or more line options. You cannot enter both panel commands and line options at the same time. System Action: User Response: STR7302E Strobe does not process the requests. Enter either a panel command or one or more line options.

INVALID LINE OPTION. VALID LINE OPTIONS ARE 'S' AND 'D'

Explanation: You entered a line option other than S or D. On this panel, the only valid line options are S to select a record or D to delete a record.

3-196

Strobe Messages Guide

System Action:

Strobe does not process the request.

User Response: Enter either S or D as line options, or any of the available panel commands, which are defined on the panel. STR7303E INVALID LINE OPTION. THE ONLY VALID LINE OPTION IS 'S'

Explanation: You entered a line option other than S. On this panel, the only valid line option is S to select a record. System Action: User Response: the panel. STR7304E FOUND Strobe does not process the request. Enter an S line option or any of the panel commands, which are defined on

INVALID COMMAND. PRINT/EXPORT IS DISABLED WHEN NO HISTORY DATA IS

Explanation: You entered the PE panel command to print or export measurement session history records, but no measurement session history records are present. System Action: Strobe does not process the request.

User Response: Because Strobe found no measurement session history records for the filter criteria that you specified, no measurement session history records were available to print or export. The Print/Export command is not valid when no measurement session history records are present. STR7305E INVALID LINE OPTION. VALID LINE OPTIONS ARE 'D', 'P', 'U', 'V', 'B', AND 'O'

Explanation: You entered an invalid line option. The only valid line options are: D (delete), P (profile), U (update measurement session history record), V (view more details), B (baseline), and O (compare to baseline). System Action: Strobe does not process the request.

User Response: Enter a valid line option or any of the available panel commands, which are defined on the panel. STR7306E HISTORY ERROR errortext The history manager has encountered an error. The error is described in Strobe does not process the request. Notify the Strobe system programmer.

Explanation: errortext. System Action: User Response: STR7307E

ONE RECORD AS BASELINE. ONLY ONE RECORD MAY BE SELECTED AS THE BASELINE

Explanation: You entered a B line option, indicating select as a baseline, for more than one measurement session history record. Only one measurement session history record may be designated as the baseline against which other measurement session history records will be compared. System Action: User Response: STR7308E Strobe does not process the request. Designate only one measurement session history record as a baseline.

BASELINE REQUIRED. A BASELINE IS REQUIRED IF COMPARE RECORDS ARE SELECTED

Explanation: For one or more measurement session history records, you entered an O line option, indicating that the measurement session history record is to be compared to the baseline measurement session history record, but you did not select a baseline measurement session history record. If you select one or more comparison measurement session history records, you must select a baseline measurement session history record. System Action: User Response: option B. Strobe does not process the request. Select a baseline measurement session history record by entering line

Messages Produced by Strobe

3-197

STR7309E COMPARE RECORD REQUIRED. 1 OR MORE COMPARE RECORDS REQUIRED IF A BASELINE IS SELECTED Explanation: You entered a B line option, indicating that the measurement session history record is a baseline measurement session history record, but you did not select measurement session history records to be compared to the baseline. System Action: User Response: Strobe does not process the request. Select one or more comparison records by entering an O line option.

STR7310E INVALID EXCP COUNT. EXCP COUNT THRESHOLD MUST BE A NUMBER FROM 0 TO 2147483647 Explanation: The value you entered for the EXCP count threshold is not valid. Valid values are within the range of 0 to 2147483647. System Action: User Response: STR7311E Strobe does not process the request. Enter a valid value.

INVALID VALUE. CPU TIME HAS A MAXIMUM OF 1440 MINUTES

Explanation: The value you entered as the CPU time minutes threshold is not valid. Valid values are within the range of 0 to 1440. System Action: User Response: STR7312E Strobe does not process the request. Enter a valid value.

INVALID VALUE. THRESHOLD SECONDS MUST BE A NUMBER FROM 0 TO 59.00

Explanation: The value you entered as the seconds threshold is not valid. Valid values are within the range of 0 to 59.00. System Action: User Response: STR7313E 99.99 Strobe does not process the request. Enter a valid value.

INVALID PERCENTAGE. THRESHOLD PERCENTAGE MUST BE A NUMBER FROM 0 TO

Explanation: The value you entered as the percentage threshold is not valid. Valid values are percentages within the range of 0 to 99.99. System Action: User Response: STR7314E Strobe does not process the request. Enter a valid value.

VALID LINE OPTION IS 'U'. THE ONLY VALID LINE OPTION IS 'U' FOR UPDATE

Explanation: The only valid line option is U, which enables you to update the measurement session history record. System Action: Strobe will not process the request.

User Response: Enter U to update the measurement session history record, or enter any of the available panel commands, which are defined on the panel. STR7315E COMMAND FAILED. THE COMMAND REQUESTED DID NOT COMPLETE SUCCESSFULLY Explanation: System Action: User Response: STR7316E The command you issued failed. Strobe does not process the request. Notify the Strobe system programmer.

NO COST RECORD FOUND. DEFAULT COST RECORD HAS NOT BEEN DEFINED A default cost record was not defined at installation. Strobe will not process cost data. Notify the Strobe system programmer.

Explanation: System Action: User Response:

3-198

Strobe Messages Guide

STR7317E INVALID COMMENT. UNDERSCORE OR DOUBLE QUOTES ARE INVALID IN COMMENT TEXT Explanation: You entered an underscore (_) or double quotes (") in the comment field. Underscores or double quotes are not allowed in this field. System Action: User Response: quotes ("). STR7318E Strobe will not update the record. Enter text in the comment field without using an underscore (_) or double

INVALID COST RECORD DATA. COST CATEGORY MUST BE 0, 1, OR 2 The history dataset has become corrupted. Strobe does not process the request. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR7319I

commandname SUCCESSFUL. commandname COMPLETED SUCCESSFULLY The command you issued, commandname, completed successfully. None. None required.

Explanation: System Action: User Response: STR7320E

INTERNAL ERROR. INVALID RECORD TYPE PASSED TO modname An invalid record type was passed to module modname. Strobe does not process the request. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR7321E

INVALID COST CATEGORY. COST CATEGORY MUST BE 'PR', 'NP', OR BLANK

Explanation: You entered a cost category other than PR for prime cost, NP for non-prime cost, or blank. System Action: Strobe does not process the request.

User Response: Enter a cost category of PR for prime, NP for non-prime, or blank. If you leave the field blank, the system will determine the cost based on the time of measurement and the cost record associated with the system on the measurement session history record. STR7322E COMMAND NOT ALLOWED. THE HISTORY CANNOT BE CHANGED WITHOUT A DEFAULT COST RECORD Explanation: A default cost record was not defined at installation. You cannot update the measurement session history record without first defining a default cost record. System Action: User Response: STR7323E Strobe does not process the request. Notify the Strobe system programmer to define a default cost record.

COMPARE FAILED. errortext The comparison routine failed. errortext describes the error. Strobe does not display the history comparison information. Notify the Strobe system programmer.

Explanation: System Action: User Response:

STR7324E NO COST DATA. COST DATA IS NOT AVAILABLE. THE COST COMPARISON COMMAND IS REJECTED Explanation: The cost comparison function cannot complete because cost information is not available on your system. System Action: User Response: Strobe does not process the request. Notify the Strobe system programmer.

STR7325E RECORD NOT FOUND. THE HISTORY RECORD NEEDED FOR THE FUNCTION REQUESTED WAS NOT FOUND Explanation: The history dataset has become corrupted.

Messages Produced by Strobe

3-199

System Action: User Response:

Strobe does not process the request. Notify the Strobe system programmer.

STR7326E COMMAND CONFLICT. CANNOT ADD A COST RECORD AND USE LINE OPTIONS AT THE SAME TIME Explanation: You entered Y in the Add Cost Record field and also entered one or more line options for the cost records. You cannot add a cost record and use line options at the same time. System Action: Strobe does not process the request.

User Response: To add a cost record, enter Y in the Add Cost Record field. Do not use line options at the same time as adding a cost record. STR7327E COST RECORD DELETED. COST RECORD SUCCESSFULLY DELETED The deletion of a cost record from the history database was successful. None. None required.

Explanation: System Action: User Response: STR7328E

INVALID LINE OPTION. VALID LINE OPTIONS ARE 'U' AND 'D'

Explanation: You entered a line option other than U to update a record or D to delete a record. The only valid line options are U or D. System Action: User Response: Strobe does not process the request. Enter either U to update a record or D to delete a record.

STR7329E CANNOT DELETE DEFAULT. THE DEFAULT PRIME AND NON-PRIME COST RECORDS CANNOT BE DELETED Explanation: System Action: User Response: STR7330E You cannot delete the default prime and non-prime cost records. Strobe does not process the request. None required.

NO CHANGES MADE. UPDATE WAS SELECTED BUT NO CHANGES WERE MADE

Explanation: You entered the U line option to update a cost record, but entered no changes on the Strobe - History - Machine Cost Edit panel. System Action: Strobe does not process the request.

User Response: To update a record, enter your changes on this panel and press Enter, or press End to cancel. STR7331E INVALID CPU MODEL. INVALID CPU MODEL - NO EMBEDDED BLANKS AND CANNOT BE A SINGLE '*' Explanation: System Action: The CPU model that you specified is not syntactically correct. Strobe does not process the request.

User Response: Enter a CPU model that is syntactically correct. It cannot have embedded blanks and it cannot be a single asterisk (*). If you use an asterisk, however, it will not act as a wildcard. STR7332E INVALID RECORD TYPE. ENTER 'S' FOR A SYSTEM RECORD OR 'U' FOR A USER RECORD

Explanation: You either left the RECORD TYPE field blank or entered a record type other than S for SYSTEM or U for USER. A system record is used globally by all users while a user record is used only by the record creator. System Action: User Response: STR7333E Strobe does not process the request. Enter either S to indicate a SYSTEM record or U to indicate a USER record.

RECORD ALREADY EXISTS. THIS COST RECORD ALREADY EXISTS This cost record already exists. Strobe does not process the request.

Explanation: System Action:

3-200

Strobe Messages Guide

User Response: To add a new cost record from this panel, change the system definition information and press Enter. To update the cost record from this panel, press PF3 to exit the panel and then enter the U line option. STR7334I RECORD ADDED. THE COST RECORD WAS SUCCESSFULLY ADDED The addition of the cost record to the history database was successful. None. None required.

Explanation: System Action: User Response: STR7336E

RECORD UPDATED. THE COST RECORD WAS SUCCESSFULLY UPDATED The cost record you selected has been updated. None. None required.

Explanation: System Action: User Response: STR7337E

INVALID COST INPUT. ENTER CPU AND I/O COST -OR- SERVICE UNIT COST

Explanation: You must specify the same category of cost for both prime and non-prime rates. For example, if you specify CPU hour and I/O costs for Prime cost then you must specify CPU hour and I/O costs for non-prime cost. Similarly, if you specify service units for Prime cost, you must also specify service units for non-prime costs. System Action: User Response: STR7338E Strobe does not process the request. Specify the same category of cost for both prime cost and non-prime cost.

INVALID COST INPUT. ENTER CPU AND I/O COST -NOT- SERVICE UNIT COST

Explanation: Because you specified CPU and I/O cost for prime cost, you must also specify CPU and I/O cost for non-prime cost. System Action: Strobe does not process the request.

User Response: Enter the same category of costs for both prime and non-prime costs: either CPU and I/O cost or service units cost. STR7339E INVALID COST INPUT. ENTER SERVICE UNIT COST -NOT- CPU AND I/O COST

Explanation: Because you specified service units for prime cost, you must also specify service units for non-prime cost. System Action: Strobe does not process the request.

User Response: Enter the same category of costs for both prime and non-prime costs: either CPU and I/O cost or service units cost. STR7340E INVALID CPU HOUR COST. MUST BE A NUMERIC VALUE FROM 0 TO 99999.99

Explanation: You entered an invalid value for the CPU hour cost. The greatest value you can enter is 99999.99 specified in that format. The maximum number of digits to the left of the decimal point is five and the maximum number of digits to the right of the decimal point is two. System Action: User Response: STR7341E Strobe does not process the request. Enter a value that adheres to the rules in the Explanation.

INVALID I/O COST. MUST BE A NUMERIC VALUE FROM 0 TO 999999.999

Explanation: You entered an invalid value for the I/O cost. The greatest value you can enter is 999999.999 specified in that format. The maximum number of digits to the left of the decimal point is six and the maximum number of digits to the right of the decimal point is three. System Action: User Response: STR7342E Strobe does not process the request. Enter a value that adheres to the rules in the Explanation.

INVALID SERVICE UNIT CST. MUST BE A NUMERIC VALUE FROM 0 TO 99999.999

Explanation: You entered an invalid value for the service unit cost. The greatest value you can enter is 99999.999 specified in that format. The maximum number of digits to the left of

Messages Produced by Strobe

3-201

the decimal point is five and the maximum number of digits to the right of the decimal point is three. System Action: User Response: STR7343E Strobe does not process the request. Enter a value that adheres to the rules in the Explanation.

INVALID COST RECORD DATA. COST CATEGORY INDICATOR MUST BE 'D', 'S', OR 'U' The history dataset has become corrupted. Strobe does not process the request. Notify the Strobe system programmer.

Explanation: System Action: User Response: STR7344E

INVALID COST RECORD DATA. COST CATEGORY MUST BE 'NP', OR 'PR' You entered a cost category other than PR for prime cost or NP for non-prime Strobe does not process the request. Enter either PR for prime cost or NP for non-prime cost.

Explanation: cost. System Action: User Response: STR7345E

COST TABLE FULL. THERE ARE MORE THAN 100 SYSTEM/CPU PAIRS DEFINED

Explanation: You attempted to add a cost record, however, the maximum number of system/CPU pairs, which is 100, has already been defined. System Action: User Response: Strobe does not process the request. Notify the Strobe system programmer.

STR7346E LINE COMMAND NOT ALLOWED. LINE COMMANDS ARE NOT ALLOWED WHEN THE FREQUENCY IS CHANGED Explanation: You entered a line command while you were changing the annual frequency on one of the Measurement Session History panels of AutoStrobe. System Action: Strobe/ISPF does not process the request.

User Response: Change the annual frequency and press Enter. After the panel is refreshed, enter a line command to view the history details. The selections cannot be combined. STR7347I FREQUENCY UPDATED. THE FREQUENCY HAS BEEN CHANGED TO frequency The annual frequency is now frequency. None. None required.

Explanation: System Action: User Response: STR7348E

INVALID RANGE. TOP N WAIT USERS FIELD HAS LIMIT OF 20 You entered a value for the top number of wait users that exceeds the limit of Strobe does not process the request. Enter a value of 20 or less for the top wait users.

Explanation: 20. System Action: User Response:

STR7349 INVALID COMBINATION. CANNOT ENTER BOTH TOTAL WAIT PERCENT AND TOP N WAIT USERS Explanation: You entered values for total wait time percent and the top number of wait users. You cannot choose values for both. System Action: Strobe does not process the request.

User Response: Enter a value that defines the percent of total wait time or the top number of wait time users, not both. STR7350E INVALID COMBINATION. CANNOT ENTER BOTH TOTAL CPU PERCENT AND TOP N CPU USERS Explanation: You entered values for total CPU consumption percent and the top number of CPU users. You cannot choose values for both.

3-202

Strobe Messages Guide

System Action:

Strobe does not process the request.

User Response: Enter a value that defines the percent of total CPU or the top number of wait time users, not both. STR7351E INVALID ENTRY. ENTER ALPHANUMERIC OR NATIONAL CHARACTERS - 1ST MUST NOT BE NUMERIC Explanation: You entered a value that is syntactically incorrect. Enter a value that consists of the following alphanumeric or national characters: AZ, #, $, @, 09. The first character may not be numeric, but it may be a period. System Action: User Response: STR7352E Strobe does not process the request. Enter a value that adheres to the rules in the Explanation.

SELECT A REPORT TYPE. AT LEAST ONE REPORT TYPE MUST BE SELECTED

Explanation: You indicated that you wanted to see SQL analysis reports, but you failed to select one or more of the available options for the type of report. System Action: Strobe does not process the request.

User Response: Enter one or more of the following options for the types of SQL analysis reports you want to see: EXPLAIN, TRANSLATION, OPPORTUNITIES, and STATISTICS. STR7354I RECORD NOT UPDATED. THE UPDATE WAS NOT CONFIRMED SO THE COST RECORD WAS NOT UPDATED Explanation: request. System Action: Strobe did not update the cost record because you did not confirm the update Strobe does not update the cost record.

User Response: None required. To update the cost record, reenter the update request and press Enter to confirm the update. STR7355E BASELINE OUT OF RANGE. DBRM AND TRAN BASELINES MUST BE A VALUE BETWEEN 0.0 AND 99.999 Explanation: The value that you entered in the DBRM baseline or TRAN (transaction) baseline field is invalid. Valid values are between 0.0 and 99.999. System Action: Strobe does not process the request.

User Response: Enter a valid value or leave blank to accept the default baseline. See the Strobe User Guide for default values. STR7356E INVALID VALUE. TOTAL SAMPLES PROCESSED HAS A MAXIMUM OF 150000

Explanation: The value that you entered as the total samples processed threshold is not valid. Valid values are within the range of 0 to 150000. System Action: User Response: STR7357E Strobe does not process the request. Enter a valid value.

INVALID VALUE. SESSION TIME HAS A MAXIMUM OF 1440 MINUTES

Explanation: The value that you entered as the session time minutes threshold is not valid. Valid values are within the range of 0 to 1440 minutes. System Action: User Response: STR7358E Strobe does not process the request. Enter a valid value.

INVALID VALUE. WAIT TIME HAS A MAXIMUM OF 1440 MINUTES

Explanation: The value that you entered as the wait time minutes threshold is not valid. Valid values are within the range of 0 to 1440. System Action: User Response: Strobe does not process the request. Enter a valid value.

Messages Produced by Strobe

3-203

STR7359E

INVALID VALUE. STRETCH TIME HAS A MAXIMUM OF 1440 MINUTES

Explanation: The value that you entered as the stretch time minutes threshold is not valid. Valid values are within the range of 0 to 1440. System Action: User Response: Strobe does not process the request. Enter a valid value.

STR7360E NOT AUTHD TO DELETE SDS. YOU ARE NOT AUTHORIZED TO DELETE A SAMPLE DATASET. USE D INSTEAD Explanation: this request. System Action: You do not have the authority to delete the sample datasets associated with Strobe/ISPF does not process the request.

User Response: Select D to delete request without deleting datasets, or notify the Strobe system programmer. STR7361E INVALID NUMBER. NUMBER SHOULD BE IN THE RANGE OF 1-13 You entered an invalid number for the display order. Strobe/ISPF does not display the active process list. Enter a number in the range of 1 to 13.

Explanation: System Action: User Response: STR7362E

INVALID SPECFICATION. VALID OPTIONS ARE J OR P

Explanation: You entered an invalid value in the JOBNAME field on the Strobe - Add Active Request panel. System Action: User Response: Strobe/ISPF does not process request. Enter J to display active jobs or P to display active processes.

STR7363E INVALID SPECIFICATION. MQSERIES DC MUST BE SPECIFIED AS Y FOR MQSERIES OPTIONS TO BE USED Explanation: You requested a Strobe for WebSphere MQ processing option without specifying Y in the MQSeries data collector field on the Strobe - Data Collectors panel. System Action: Strobe/ISPF cannot process MQSeries options unless you specify Y in the MQSeries data collector field. User Response: panel. Specify Y next to the MQSeries data collector on the Strobe - Data Collectors

STR7364E CICS OPTIONS ERROR. PERFORMANCE SUPPLEMENT & REGION DATA/TRANS CANNOT BOTH BE SELECTED Explanation: You entered a Y in both the Produce Performance Supplement/Collect Terminal Activity fields and in the Collect Region Data/Detail Transactions fields on the Strobe - CICS Data Collector Options panel. System Action: Strobe/ISPF does not process the request.

User Response: You cannot enter Y for both options. Select either the option for Produce Performance Supplement/Collect Terminal Activity or the option for Collect Region Data/Detail Transactions on the Strobe - CICS Data Collector Options panel. STR7365E INVALID COMBINATION. ENTER 1 OR MORE TRANSACTIONS OR SPECIFY WHICH REPORT TO PROCESS Explanation: You entered an N in either the Collect Region Data field or the Produce Performance Supplement field on the Strobe - CICS Data Collector Options panel, but left the other fields blank. System Action: User Response: them. Strobe/ISPF does not process the request. Enter transactions or enter Y to produce these reports. Enter N to suppress

3-204

Strobe Messages Guide

STR7366E INVALID TRANSACTION NAME. ENTER UP TO 4 ALPHANUMERIC/NATIONAL/ SPECIAL CHAR--WILDCARD PERMITTED Explanation: System Action: User Response: characters: You entered an incorrect character in the transaction field. Strobe/ISPF does not process the request Enter up to four of any of the following alphanumeric, national, or special

AZ az 09 $ @ # . / % & ? ! : ^ < >


STR7367E PARAMETER OUT OF RANGE. VALUE MUST BE BETWEEN 0.000 AND 99.999 SECONDS

Explanation: You entered an invalid value for either the CICS Transaction Profile compress below % field or for the CICS Region Level compress below % field. System Action: User Response: Strobe/ISPF does not process the request. Enter a value between 0.000 and 99.999.

STR7368E INVALID COMBINATION. CANNOT SUPPRESS ALL REPTS OR SPECIFY CICS TRANS & SPECIFY FILTERS Explanation: You cannot suppress both the CICS Transaction Profile reports and the nonCICS Transaction Profile reports. You also cannot specify CICS transactions and suppress CICS Transaction Profile reports. System Action: Strobe/ISPF does not process the request.

User Response: Either suppress the CICS Transaction Profile reports or suppress the non-CICS Transaction Profile reports. STR7369E DISPLAY INVALID COMBINATION. JOBS CANNOT BE SELECTED IF Y IS ENTERED IN CHANGE

Explanation: You entered an invalid combination. You cannot enter a Y in the CHANGE DISPLAY FORMAT field and an S in the SEL column on the Strobe - Active Process Selection List panel to select a process to measure. System Action: Strobe/ISPF does not process the request.

User Response: To select one or more processes to measure, clear the CHANGE DISPLAY FORMAT field and enter one or more Ss in the SEL column. To change the displayed information, enter a Y in the CHANGE DISPLAY FORMAT field and clear all Ss in the SEL column. STR7370W LIMITED STROBE NOT ACTIVE. STROBE PACKAGING UTILITY FUNCTIONALITY WILL BE The Strobe session manager address space is not active.

Explanation:

System Action: Strobe continues processing, but the Strobe Packaging Utility panels do not include the sample and log file dataset names. User Response: STR7371W Notify the Strobe system programmer.

NO SAMPLE DATA SETS. NO CATALOGED DATA SETS WERE FOUND The Strobe Packaging Utility did not find as cataloged the sample datasets you Strobe continues processing without displaying sample datasets.

Explanation: specified.

System Action:

User Response: Enter the names of four cataloged datasets in the SPECIFY INPUT DATA SET NAMES TO INCLUDE field. STR7372E DATA SET PREFIX REQUIRED. AN OUTPUT DATA SET PREFIX MUST BE SPECIFIED

Explanation: You did not specify an output dataset prefix during your Strobe Packaging Utility dataset transfer request. System Action: The Strobe Packaging Utility does not process the request.

User Response: Specify an output dataset for the prefix and resubmit the Strobe Packaging Utility dataset transfer request.

Messages Produced by Strobe

3-205

STR7373I VERIFY CANCEL REQUEST. END TO EXIT STROBE PACKAGING UTILITY, ENTER TO CONTINUE Explanation: This message enables you to verify your request to cancel the Strobe Packaging Utility. System Action: The Strobe Packaging Utility stops processing your request.

User Response: Press End to cancel the Strobe Packaging Utility, or press Enter to continue Utility processing. STR7374E INTERNAL ERROR. STRBPKG RC= rc FROM servicename

Explanation: The Strobe Packaging Utility called the dialog service servicename, but the service routine failed with a return code of rc. System Action: User Response: STR7375E The Strobe Packaging Utility does not process your selection. Notify the Strobe system programmer.

OSTARXMT ERROR. text

The specified message text is output from the OSTARXMT REXX exec. The following are possible texts: Workfile STSUT2 allocation failure
Explanation: System Action: The procedure was unable to allocate a temporary work file. Processing terminates.

User Response: See other TSO messages and modify the allocation for SYSUT2 in OSTARXMT to conform to local standards.

Invalid control file DSN Try OSTARXMT with no parms


Explanation: System Action: User Response: The control file STRBPKG is passing to OSTARXMT is invalid. Processing terminates. Contact Compuware Customer Support.

Unable to allocate file. ODSN with DISP=NEW


Explanation: System Action: The output file cannot be allocated. Perhaps the dataset already exists. Processing terminates.

User Response: Delete the existing dataset of the same name. Otherwise, see other TSO messages and modify the dataset name to conform to local standards.

DSN not found. Rejected


Explanation: System Action: OSTARXMT could not find the dataset. Processing terminates.

User Response: Check that the name was entered correctly using normal TSO naming standards. If the name is not in single quotes it will be prefixed with your userid. If the name is correct, the dataset is not migrated. If you had a typing error then correct it and retry.

Error writing to ODSN


Explanation: Either the output dataset filled up, the volume is full, or you do not have write access to the dataset. System Action: Processing terminates.

User Response: If the output dataset has gone to 16 extents then increase the size on the allocate for SYSUT1 in OSTARXMT.

All datasets were not processed, but ODSN is valid


Explanation: file. System Action: User Response: This is a warning. The datasets that were specified correctly are in the output None. None required.

3-206

Strobe Messages Guide

Unable to copy IDSN to workfile


Explanation: System Action: The TSO TRANSMIT command failed to write the input file to the work file. Processing terminates.

User Response: If this is a large file, try increasing the size of the work file allocated via SYSUT2 in OSTARXMT. Otherwise, check preceding TSO errors.

Read error on temp file


Explanation: System Action: User Response: This should not occur. Processing terminates. Record the preceding TSO error messages.

Error writing to output file


Explanation: System Action: Either the output file is full or you do not have write access to it. Processing terminates.

User Response: If it is full, increase the size of the dataset allocated as SYSUT1 in OSTARXMT. STR7376E OSTARREC ERROR. text

Explanation: The specified message text is output from the OSTARREC REXX exec. The following are possible texts:

Error allocating work file


Explanation: System Action: User Response: standards. The procedure was unable to allocate a temporary work file. Processing terminates. Modify the allocation for SYSUT2 in OSTARREC to conform to local

Unable to allocate file ISDN


Explanation: System Action: Allocation of input file failed. Processing terminates.

User Response: Check other error messages. Possible errors are security violations or exclusive shares.

Invalid input DSN ISDN. Invalid header


Explanation: The input file does not start with the expected header information. Possible causes are transmission error or wrong input dataset used. System Action: User Response: Processing terminates. Correct input dataset name, if incorrect, otherwise, retransmit.

Input file is VERSION. You need a new version of OSTARREC


Explanation: System Action: User Response: The file you have uploaded requires a newer version of OSTARREC. Processing terminates. Contact Compuware Customer Support.

Read error on input file


Explanation: System Action: User Response: Unable to read the input file. Processing continues. See other TSO messages for details.

File level error checking failed


Explanation: not 88. System Action: User Response: File validation failed. Possible reasons include transmission error and LRECL Processing terminates. Correct error and retry.

Messages Produced by Strobe

3-207

Record level error checking failed


Explanation: System Action: User Response: File validation failed. Transmission error. Processing terminates. Correct error and retry.

Write error to temp file


Explanation: System Action: User Response: The temporary work file allocated via SYSUT2 is not big enough. Processing terminates. Find the allocate statement for SYSUT2 in OSTARREC and increase the size.

INMR152I RECEIVE failed. Senders node ID is not recognized


Explanation: This message is produced by the TSO RECEIVE command which is used, under covers, by OSTARREC. It is produced when the TSO TRANSMIT/RECEIVE customization has not been performed at the site when TSO/E was installed. System Action: User Response: STR7378E Processing terminates. Contact your system programmer.

STRBPKG MUST BE INVOKED VIA 'P' FROM THE STROBE OPTIONS MENU

Explanation: You attempted to access the Strobe packaging utility using a command. You must access this utility by selecting P from the Strobe Options menu in Strobe/ISPF. System Action: User Response: menu. Strobe does not invoke the packaging utility. To invoke the packaging utility, select option P from the Strobe Options

STR7379W AUTOSTROBE DISABLED AUTOSTROBE ALLOCATION ERROR CAUSED AUTOSTROBE TO BE DISABLED Explanation: A problem occurred during the allocation of a file required by AutoStrobe.

System Action: The AutoStrobe option does not appear on the primary Strobe Options menu. User Response: STR7380I jobname Notify the Strobe system programmer.

AUTOSTROBE REQUEST ADDED. AN AUTOSTROBE REQUEST HAS BEEN ADDED FOR

Explanation: You submitted a measurement request. Strobe/ISPF reports the request number (nnnn) and status in the short message field. If the request was submitted successfully, the jobname appears in the long message field. Otherwise, the return code appears in the short message field and the appropriate error message appears in the long message field. System Action: User Response: Strobe successfully processed the request and is waiting for the next request. None required.

STR7381W NO BASIS DATA RECORDS. THE AUTOSTROBE REQUEST HAS NO BASIS DATA RECORDS TO DISPLAY Explanation: Strobe issued this warning in a response to a request to display basis data records associated with an AutoStrobe request which has no such records. System Action: User Response: STR7382E None. Remove the invalid request.

ARCHIVE ERROR. error text The history manager has encountered an error. The error is described in Strobe does not process the request. Notify the Strobe system programmer.

Explanation: errortext. System Action: User Response:

3-208

Strobe Messages Guide

STR7383E

INVALID STEPNAME. SPECIFY A VALID STEPNAME OR STEP.PROCESTEP NAME

Explanation: You entered an invalid step in the STEP field of the Strobe - Add Queued Request panel, or you have chosen Option 2 on the Strobe - Add Queued Request - Multiple Steps panel and specified the name of one or more steps or step.procsteps incorrectly. System Action: Strobe does not process the measurement request.

User Response: Supply a relative step number between 1 and 255, or a stepname, or a procstepname and stepname. The stepname or procstepname must contain from 1 to 8 alphanumeric characters. The first characters must be alphabetic or national. The three national characters are @, #, and $. STR7384E NO RECORDS FOUND. NO AUTOSTROBE RECORDS WERE FOUND FOR THE SPECIFIED FILTER CRITERIA Explanation: Strobe issued this message in a response to a request to display AutoStrobe requests based on filter values for the fields: Jobname, Program Stepname, OwnerId, System. No AutoStrobe requests matched the filter. System Action: User Response: STR7385E Strobe does not display any data. Make the filters less restrictive, using an asterisk (*) as a wildcard character.

INVALID SESSION/TCP TIME. MUST BE A NUMERIC VALUE FROM 0 TO 9999

Explanation: The value you entered as the SESSION/TCB time minutes threshold is not valid. Valid values are within the range of 0 to 9999. System Action: User Response: STR7386E Strobe does not process the request. Enter a valid value.

INVALID SPECIFICATION. VALID OPTIONS ARE "A" OR "Q" OR "B" OR "W" The value you entered as the request type are not valid. Valid values are A, Q, Strobe does not process the request. Enter a valid value.

Explanation: B, or W. System Action: User Response:

STR7387E UNABLE TO FIND CWPIDRVB CWPIDRVB NOT IN UI_CSSLIB OR LINKLIST Explanation: Strobe/ISPF cannot find CWPIDRVB in a link list dataset or in the dataset specified on the UI_CSSLIB parameter in the Strobe parmlib member. System Action: User Response: STR7388E Strobe/ISPF does not process the request. Notify the Strobe system programmer.

INVALID SPECIFICATION. SELECT A VALID OPTION AS LISTED ON THE PANEL You specified an invalid on the panel. Strobe/ISPF does not process the request. Specify a valid option.

Explanation: System Action: User Response:

STR7389I NO BASIS DATA FOUND. NO BASIS DATA WERE FOUND TO THE SPECIFIED AUTOSTROBE REQUEST Explanation: There are no measurement session basis data records that match the filter criteria that you specified. System Action: User Response: Strobe does not process the request. Enter different filter criteria.

STR7390I NO REQUESTS FOUND. NO ARCHIVED REQUESTS WERE FOUND FOR THE SPECIFIED FILTER CRITERIA Explanation: There are no measurement session basis data records that match the filter criteria that you specified. System Action: Strobe does not process the request.

Messages Produced by Strobe

3-209

User Response:

Enter different filter criteria.

STR7391I INVALID SCHEDULE. AN AUTOSTROBE REQUEST CANNOT BE SCHEDULED BEYOND A YEAR FROM TODAY Explanation: You attempted to schedule a measurement request element or a request group for more than one year in the future from todays date. System Action: Strobe/ISPF does not process the request.

User Response: On the Strobe - Request Scheduler panel, ensure that the values in the STARTING DATE and ENDING DATE fields represent a time period of one year or less from todays date, or specify a value in the NUMBER OF WEEKS field that is one year or less from todays date. STR7392E NO SCHEDULE GENERATED. THERE ARE NO DATE ENTRIES IN THE SCHEDULE

Explanation: You attempted to schedule a measurement request or a request group but did not specify the days of the week on which you want the measurement session initiated. System Action: Strobe/ISPF does not process the request.

User Response: Enter a Y in the field under one or more of the days shown near the top of the Strobe - Request Scheduler panel, or create a customized list by completing the bottom portion of the panel. STR7393E DUPLICATE ADD CONFLICT. THIS DATE HAS ALREADY BEEN GENERATED IN THE WEEKLY LIST Explanation: You attempted to add an individual date to the weekly schedule for a measurement request or a request group. The date you specified, however, is already included in the weekly schedule. System Action: Strobe does not process the request.

User Response: Ensure that the individual date is not included in the weekly schedule designated in the top section of the Strobe - Request Scheduler panel. STR7394E DATE DOES NOT EXIST. THIS DATE DOES NOT EXIST IN THE GENERATED WEEKLY LIST

Explanation: You attempted to exclude an individual date from the weekly schedule for a measurement request or a request group. The date and time you specified, however, does not exist in the weekly schedule. System Action: Strobe does not process the request.

User Response: Ensure that the individual date is included in the weekly schedule designated in the top section of the Strobe - Request Scheduler panel. STR7396E INVALID SPECIFICATION A THRESHOLD MINIMUM CANNOT BE SPECIFIED WITH THE SUPPRESS OPTION Explanation: You specified a Y in the SUPPRESS field and entered a threshold minimum in the OVERRIDE THESHOLD field. System Action: User Response: Strobe does not process the AutoStrobe request. Enter a threshold minimum or select the SUPRESS option or do neither.

STR7397E CANNOT SUPPRESS ALL THRESHOLDS CANNOT ALL BE SUPPRESSED Explanation: You specified Y in the SUPPRESS fields. There must at least one threshold used by AutoStrobe. System Action: User Response: Strobe does not process the AutoStrobe request. Change at least one SUPPRESS field to N.

STR7398E CHANGE INVALID ON WARN CANNOT CHANGE MEASUREMENT PARAMETERS IF ACTION IS WARN Explanation: You specified Y in the Change Measurement Parameters field and specified an action of Warn. Measurement parameters do not apply when an action of warn is specified. System Action: Strobe does not process the AutoStrobe request.

3-210

Strobe Messages Guide

User Response: Change the action from Warn to a measurement type, (Q, A, or B) or change the Y to N in the Change Measurement Parameters field. STR7402E INVALID FILE FILE IS NOT DDIO OR MAP Explanation: file. System Action: User Response: You specified a file to use for indexing at was neither a DDIO file nor a map Strobe does not process the your request. Enter the correct file name.

STR7403E DDIO FILE CODE = xxxx DDIO DATASET VERIFY RETURNED AN INVALID STATE Explanation: System Action: User Response: The Compuware CSS routine returned a bad return code xxxx to Strobe. Strobe does not process the your request. Look up the meaning of the return code in the CSS manual.

STR7404E INVALID EXCPS MUST BE A NUMERIC VALUE FROM 20000 TO 2147483647 Explanation: System Action: User Response: You entered a value that is out of range. Strobe/ISPF does not process the request. Enter a value within the minimum or clear the field.

STR7405E EXCLUSION ADDED CANDIDATE WAS ADDED TO THE EXCLUSION LIST Explanation: System Action: User Response: STR7406E The exclusion record you selected has been updated. None. None required.

INTERNAL ERROR STRBJTG RC = <rc> FROM <message text>

Explanation: An internal error occurred in Java target processing. message text specifies the error location. System Action: User Response: STR7407I Strobe does not process the request. Notify the Strobe system programmer.

SELECT A TARGET OR PRESS END TO EXIT On a targeting panel, you pressed Enter without specifying at least one Java Strobe does not process the request. Enter or select a target, or press End to exit without adding a target.

Explanation: target. Explanation: Explanation: STR7408E

ERROR IN JAVA SELECTOR PROCESSING: <message text>

Explanation: A serious error occurred in the Strobe Java Selector processing. See the message text for details about the error that occurred. message text can be:

MVSOUT ALLOCATION RETURN CODE = rc SELECTOR CANNOT BE USED - FILE CANNOT BE ALLOCATED TARGET NOT FOUND. REENTER TARGET OR PRESS END TO EXIT JAVA CLASS SELECTOR RETURN CODE = rc JAVA SELECTOR FILE COPY RETURN CODE = rc TARGETING DATA ERROR: rc (Various other SELECTOR errors)
System Action: Strobe does not process the request.

Messages Produced by Strobe

3-211

User Response: programmer. STR7409E TARGETS.

Correct the error described in the message text or notify the Strobe system

NUMBER OF TARGETS CANNOT EXCEED <nnn>. YOU HAVE SELECTED <mmm>

Explanation: On a Strobe Java targeting panel, you selected mmm targets, which is more than the maximum of nnn that can be processed. System Action: User Response: Strobe does not process the request. Delete one or more targets until fewer than nnn targets are selected.

STR7410E - STRBJTG MUST BE INVOKED FROM THE STROBE DATA COLLECTORS PANEL Explanation: You attempted to access the Java targeting function (STRBJTG) outside of Strobe/ISPF. You must access this function only from the Strobe - JAVA Data Collector Options panel in Strobe/ISPF. System Action: Strobe does not invoke the Java targeting function.

User Response: To run the Java targeting function, invoke Strobe/ISPF and select JAVA Targeting Data from the Strobe - JAVA Data Collector Options panel. STR7411E DUPLICATE RECORD THIS RECORD ALREADY EXISTS ON THE FILE Explanation: System Action: User Response: The exclusion record you entered already exists on the file. Strobe/ISPF does not process the request. Ensure that the exclusion record that you add does not already exist.

STR7413E INDICATE M-MAP OR D-DDIO ENTER AN M FOR A MAP FILE OR A D FOR A DDIO DATASET Explanation: You listed a file to be used for indexing, but did not indicate whether it is a map file or DDIO file. System Action: User Response: Strobe does not process your request. Specify M for a map file or D for a DDIO dataset.

STR7419E DATE-LOADLIB-OPTION REQ. START DATE, UPDATE OPTION AND AT LEAST ONE LOADLIB ARE REQUIRED Explanation: You requested to build an AutoMeasure load module list, but did not specify a value for the start date, the update option, or a name of a load library to be searched. System Action: User Response: Strobe does not process the request. Enter the missing values in the appropriate fields.

STR7420I NO RECORDS FOUND. NO AUTOMEASURE RECORDS WERE FOUND FOR THE SPECIFIED FILTER Explanation: Strobe could not find any AutoMeasure records for the values specified on the Strobe - AutoStrobe Automeasure Utility panel or the AutoMeasure utility has not been run. System Action: User Response: No records are displayed.

If the AutoMeasure utility has not been run, go to Option 5 on the Strobe AutoStrobe Options panel, and run the utility. If it has been run, change the values

specified on the Strobe - AutoStrobe Automeasure Utility panel to include more records. STR7421E INVALID DATE. DATE IS IN INVALID FORMAT You used an invalid format for the date. Strobe does not process the request.

Explanation: System Action:

User Response: Enter the date using the format that was specified in the parameter dataset when Strobe was installed. The default format is DD/MM/YY. The value for the day must be from 1 to 31, and the value for the month must be from 1 to 12.

3-212

Strobe Messages Guide

STR7422E

INVALID SPECIFICATION. VALID OPTIONS ARE "R" OR "U"

Explanation: You entered an invalid list option on the Strobe - AutoStrobe Automeasure Utility panel. Valid values are R for Replace or U for Update. System Action: User Response: STR7424E Strobe does not process the request. Enter a valid value.

PERIOD INCOMPLETE. PERIOD STARTING AND ENDING TIMES ARE REQUIRED

Explanation: The collection period on the AutoStrobe Create Transaction Candidates request is incomplete. Each collection period must have a starting and ending time. System Action: User Response: Strobe does not process the request. Supply the missing information.

STR7425E PERIOD INVALID. CANDIDATE COLLECTION ENDING TIME MUST BE GREATER THAN STARTING TIME Explanation: The AutoStrobe Create Transaction Candidates request has an invalid collection period. System Action: User Response: starting time. STR7426E OVERLAP Strobe does not process the request. Change the ending time of the collection period so that it occurs after the

PERIODS OVERLAP. TRANSACTION CANDIDATE COLLECTION PERIODS MAY NOT

Explanation: The AutoStrobe Create Transaction Candidates request has an invalid collection period. Collection periods cannot overlap. System Action: User Response: Strobe does not process the request. Change the time ranges of the collection periods so they do not overlap.

STR7427E DAYS OUT OF RANGE. TRANSACTION CANDIDATE COLLECTION NUMBER OF DAYS MUST BE BETWEEN 1 AND 31 Explanation: The AutoStrobe Create Transaction Candidates request has an invalid number of collection days. The number must be from 131 days. System Action: User Response: Strobe does not process the request. Type a number from 131 in the Days to Collect field.

STR7428E MIN TRAN COUNT INVALID. TRANSACTION CANDIDATE COLLECTION MINIMUM TRAN COUNT MUST BE BETWEEN 1 AND 9999 Explanation: The AutoStrobe Create Transaction Candidates request has an invalid minimum transaction count. The minimum qualifying transaction count must be from 1 9999 transactions. System Action: User Response: Strobe does not process the request. Type a number from 19999 in the Qualifying Minimum Tran Count field.

STR7429E MIN RESP TIME INVALID. TRANSACTION CANDIDATE COLLECTION MINIMUM RESPONSE TIME MUST BE BETWEEN .1 AND 999.9 seconds Explanation: The AutoStrobe Create Transaction Candidates request has an invalid minimum response time. The minimum qualifying response time must be from .1999.9 seconds. System Action: User Response: field. Strobe does not process the request. Type a number from .1999.9 in the Qualifying Minimum Response Time

Messages Produced by Strobe

3-213

STR7430E MIN CPU TIME INVALID. TRANSACTION CANDIDATE COLLECTION MINIMUM CPU TIME MUST BE BETWEEN .00001 AND 9.99999 seconds Explanation: The AutoStrobe Create Transaction Candidates request has an invalid minimum CPU time. The minimum qualifying CPU time must be from .000019.99999 seconds. System Action: User Response: field. Strobe does not process the request. Type a number from .000019.99999 in the Qualifying Minimum CPU Time

STR7431E INSUFFICIENT DATA. THE TRANSACTION CANDIDATE DATA COLLECTED IS NOT SUFFICIENT TO CALCULATE THRESHOLDS Explanation: Sufficient data for a transaction candidate detail is available when:

The candidacy period is completed (Days to Collect) AutoStrobe has collected data for at least three days System Action: Strobe does not process the request.

User Response: Determine when AutoStrobe has collected data for at least three days or when the candidacy period is completed, and view the transaction candidate detail after that time. STR7432E SELECT ONLY 5 TRAN ID'S. THE MAXIMUM NUMBER OF TRANSACTIONS THAT CAN BE SPECIFIED IS 5. PLEASE SELECT NO MORE THAN 5 TRANSACTION ID'S Explanation: The Add AutoStrobe Transaction request or an Add Active request is invalid, because you selected more than five transactions from the Strobe - AutoStrobe Candidate Transaction Detail panel. System Action: User Response: Strobe does not process the request. Select no more than five transactions.

STR7433E SPECIFICATION INCOMPLETE. JOBNAME, PROGRAM AND AT LEAST ONE TRANSACTION NAME REQUIRED Explanation: The Add AutoStrobe Transaction request is incomplete. The monitoring request must have at a minimum: a job name, program name, and at least one transaction. System Action: User Response: STR7434E MINUTES Strobe does not process the request. Supply the missing information.

ANALYSIS INTVL INVALID. ANALYSIS INTERVAL MUST BE A VALUE BETWEEN 5 AND 60

Explanation: The Add AutoStrobe Transaction request has an invalid analysis interval. The analysis interval must be from 560 minutes. System Action: User Response: Strobe does not process the request. Type a number from 560 in the Analysis Interval field.

STR7435E SPECIFY TRANSACTION. A TRANSACTION MONITOR PERIOD, RESPONSE TIME OR CPU TIME THRESHOLD WAS SPECIFIED WITHOUT TRANSACTION NAME Explanation: The Add AutoStrobe Transaction request is incomplete. A transaction threshold was specified on the monitoring request without a transaction name. System Action: User Response: Strobe does not process the request. Type a transaction name in the Tran Id field.

STR7436E PERIOD INCOMPLETE. TRANSACTION MONITOR PERIOD STARTING AND ENDING TIMES ARE REQUIRED Explanation: The Add AutoStrobe Transaction request is incomplete. A monitoring period is missing a starting or ending time. System Action: User Response: Strobe does not process the request. Supply the missing information.

3-214

Strobe Messages Guide

STR7437E PERIOD INVALID. TRANSACTION MONITOR ENDING TIME MUST BE AT LEAST 5 MINUTES GREATER THAN STARTING TIME Explanation: The Add AutoStrobe Transaction request has an invalid monitoring period. The ending time of the monitoring period must be greater than the starting time by at least five minutes. System Action: Strobe does not process the request.

User Response: Change the ending time of the monitoring period so that it is at least five minutes greater than the starting time. STR7438E PERIODS OVERLAP. TRANSACTION MONITOR PERIODS MAY NOT OVERLAP

Explanation: The Add AutoStrobe Transaction request has an invalid monitoring period. The monitoring periods overlap. System Action: User Response: Strobe does not process the request. Change the time ranges of the monitoring periods so they do not overlap.

STR7439 THRESHOLD INVALID. A TRANSACTION CPU OR RESPONSE TIME THRESHOLD IS INVALID OR OUT OF RANGE Explanation: A transaction threshold is invalid on the Add AutoStrobe Transaction request. The range of valid values for the CPU threshold are .000019.99999 seconds. The range of valid values for the response time threshold is 0.1999.9 seconds. System Action: Strobe does not process the request.

User Response: Type a number from .000019.99999 in the CPU threshold field; or type a number from 0.1999.9 in the Response threshold field. STR74451E INVALID SPECIFICATION. VALID SELECTION FOR DDF REQUESTER IS 'P' FOR PRIMARY OR 'S' FOR SECONDARY Explanation: System Action: User Response: You typed a value other than P, S, or blank in one of the DDF requester fields. Strobe does not process the request. Correct the invalid field.

STR7446E 1 P REQUIRED, S OPTIONAL. ENTER ONE 'P' FOR PRIMARY AND OPTIONALLY ONE 'S' FOR SECONDARY Explanation: System Action: You typed more than one P or S, or you typed an S without a P. Strobe does not process the request.

User Response: Select the Primary DDF Requester using a P and, optionally, one Secondary DDF Requester using an S. STR7447E FILTERS MAX OF 2 FILTERS ALLOWED. USE ONLY FIELDS USED AT MEASUREMENT FOR

Explanation: You entered filters for more than two DDF requesters. Only two DDF requesters are permitted; therefore, only two DDF filters are allowed. System Action: User Response: measurement. STR7448E Strobe does not process the request. Only specify filters in the fields corresponding to the DDF requesters used at

INVALID THRESHOLD VALUE. MUST BE A NUMERIC VALUE FROM 0 TO 99.99999

Explanation: You typed an invalid value for the threshold. Valid values are 099.99999 seconds. Specify the value in nn.nnnnn format. System Action: User Response: STR7450I Strobe does not process the request. Type a valid value for the threshold.

NO RECORDS WERE FOUND FOR THE SPECIFIED CRITERIA No event records match the ownerid that you specified. Strobe does not process the request.

Explanation: System Action:

Messages Produced by Strobe

3-215

User Response:

Enter a different ownerid.

STR7451E DUPLICATE EVENT NAME THE SPECIFIED EVENT ALREADY EXISTS Explanation: exists. System Action: User Response: You attempted to create a new event, but an event with this name already Strobe does not process the request. Choose a unique name for the event.

STR7452E ALL FIELDS REQUIRED ENTER A VALUE IN ALL 5 FIELDS Explanation: You attempted to create or update an event, but required information is missing. Enter a value, or clear the field to use the default. If there is no default, you must enter a value. System Action: User Response: Strobe does not process the request. Supply the required information.

STR7453E EVENT NAME NOT FOUND NAME IS NOT AN EXISTING EVENT Explanation: System Action: User Response: You specified an event name, but AutoStrobe cannot locate that event. Strobe does not process the request. Supply an existing event or add and specify a new one.

STR7454E MORE THAN ONE SELECTED SELECT ONLY ONE EVENT Explanation: System Action: User Response: You selected more than one event for a request. Strobe does not process the request. Resubmit the request and specify no more than one event.

STR7455E STEP INVALID ON IMMED RQ A MONITOR IMMEDIATE OR CANDIDATE IMMEDIATE REQUEST MAY NOT INCLUDE A STEP NAME Explanation: The AutoStrobe transaction monitoring or create transaction candidates request is invalid, because you specified Monitor Immediate or Immediate Eligibility and also specified a step name. System Action: User Response: STR7456E Strobe does not process the request. Resubmit the request and specify either Monitor Immediate or a step name.

This field should be left blank when the output format is an iStrobe file.

Explanation: When the OUTPUT FORMAT is I for iStrobe, the fields NUMBER OF COPIES FOR BACKGROUND REPORTS and DATASET NAME for a saved copy of the Strobe Profile have no meaning and should be left blank. System Action: User Response: dialog. STR7457E Strobe/ISPF dialog waits for correct entry. Blank out the specified input fields and continue with the Profile creation

Please enter the name of a supported code page. The translation code page specified is not supported. Strobe/ISPF dialog waits for correct entry. Enter one of the following supported code pages:

Explanation: System Action: User Response:

IBM-STD : Latin 1/Open Systems (default) IBM-037 : USA/Canada IBM-273 : German IBM-277 : Danish IBM-278 : Swedish

3-216

Strobe Messages Guide

IBM-280 IBM-284 IBM-285 IBM-297 IBM-423 IBM-424 IBM-500 IBM-870 IBM-875

: : : : : : : : :

Italy Spanish United Kingdom French Greek Israel Switzerland Polish Greek

STR7468E Invalid High Level Qualifier For Temporary Datasets. The entered temporary dataset high level qualifier is invalid. Explanation: name. System Action: You specified an unacceptable high-level qualifier for your temporary dataset Strobe/ISPF dialog waits for correct entry.

User Response: Enter a valid high-level qualifier for your temporary dataset name. Blank out the field and press Enter to restore the default value. STR7501E ERROR OCCURRED DURING UNMARSHALLING OF THE REQUEST MSG Strobe transfer client encountered an error while reading. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7504E

ERROR OCCURRED WHILE EXECUTING THE SAVE REQUEST Strobe transfer client encountered an error during the SAVE process. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7507E

REQUESTED FILE OR DIRECTORY COULD NOT BE FOUND AS SPECIFIED Strobe transfer client could not find the directory as specified. Strobe terminates the download. Correct the directory and resubmit.

Explanation: System Action: User Response: STR7508E

WRITE ACCESS FAILED FOR FILE OR DIRECTORY Strobe transfer client encountered a directory with Write access denied. Strobe terminates the download. Correct access to the directory or chose another directory.

Explanation: System Action: User Response: STR7511E

NEW DIRECTORY REQUEST FAILED: DIRECTORY ALREADY EXISTS Strobe transfer client encountered a directory error. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7512E

SAVE OF PROFILE FAILED WITH VERIFY ERROR Strobe transfer client encountered a directory error during SAVE processing. Strobe terminates the download.

Explanation: System Action:

User Response: Check the iStrobe Manager log for details, and correct the directory error. If the problem persists, contact Compuware Customer Support. STR7513E WRITE ERROR OCCURRED DURING DOWNLOAD OF PROFILE Strobe transfer client encountered an error during SAVE processing. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response:

Messages Produced by Strobe

3-217

STR7514E

SAVE FAILED ON PROFILE DATA TRANSMIT ERROR Strobe transfer client encountered an error during transmit processing. Strobe terminates the download. Rerun the job or contact Compuware Customer Support.

Explanation: System Action: User Response: STR7515E

DESTINATION FOR PROFILE IS NOT A VALID PATH FOR THIS SERVER

Explanation: Strobe transfer client could not find the directory in the directory list. Valid directories can be found in the transfer client message following this message. System Action: User Response: STR7516E Strobe terminates the download. Correct the directory and resubmit.

PROFILE LOCATIONS ARE NOT DEFINED. CONTACT YOUR ISTROBE ADMINISTRATOR The iStrobe manager configuration does not define the Profile Locations. Strobe terminates the download. Contact your iStrobe administrator.

Explanation: System Action: User Response: STR7520E

EMAIL NOTIFICATION WAS REQUESTED BUT FAILED The iStrobe manager configuration does not have the mail server installed. Strobe terminates the download. Contact your iStrobe administrator.

Explanation: System Action: User Response: STR7521E

RESPONSE RETURN CODE OR MESSAGE NUMBER IS INVALID, RESPONSE FOLLOWS Strobe transfer client encountered an error. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7522E

EMAIL NOTIFICAION WAS IGNORED, CONFIGURATION HAS NOT BEEN PERFORMED

Explanation: The iStrobe manager e-mail configuration has not been performed. The mail server smtpservr is configured to send from sender istrobe@compuware.com. The Profile has been processed and can be viewed in iStrobe via the open profiles dialog. System Action: User Response: STR7530E None. Contact your iStrobe administrator.

LMS CHECKOUT FAILURE Strobe transfer client encountered an error during LMS processing. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7531E

THE RESPONSE MESSAGE DID NOT CONTAIN THE EYECATCHER Strobe transfer client encountered an error with the transmitted data. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7532E

PROPERTIES MODULE WAS NOT LOADED Strobe transfer client encountered an error processing the HOST data. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7533E RETURN

CALL TO GETRETURNEDMESSAGE WAS MADE AND THERE WAS NO MESSAGE TO Strobe transfer client encountered an error processing the RETURNMESSAGE.

Explanation:

3-218

Strobe Messages Guide

System Action: User Response: STR7534E

Strobe terminates the download. Contact Compuware Customer Support.

UNICODE CONVERSION ERROR ON REQUEST MESSAGE Strobe transfer client encountered an error processing the Unicode conversion. Strobe terminates the download. Contact Compuware Customer Support.

Explanation:

System Action: User Response: STR7535E

UNICODE CONVERSION ERROR ON RESPONSE MESSAGE Strobe transfer client encountered an error processing the Unicode conversion. Strobe terminates the download. Contact Compuware Customer Support.

Explanation:

System Action: User Response: STR7536E

SENDING DATA ON A SOCKET FAILED Strobe transfer client encountered an error during SEND processing. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7537E

CONNECTION HAS BEEN LOST Strobe transfer client encountered a Lost Connection. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7538E

UNABLE TO LOCATE THE SERVER ADDRESS Strobe transfer client could not connect to the server address/IP address Strobe terminates the download. Correct the server address/IP address and resubmit the job.

Explanation: supplied. System Action: User Response: STR7539E

SOCKET CREATION FAILED

Explanation: Strobe transfer client could not connect to the server address/IP address and/or PORT supplied. System Action: Strobe terminates the download.

User Response: Correct the server address/IP address and resubmit the job. If the job continues to fail, contact Compuware Customer Support. STR7540E SERVER ADDRESS IS NOT AVAILABLE

Explanation: Strobe transfer client could not connect to the server address/IP address and/or PORT supplied from the system. System Action: Strobe terminates the download.

User Response: Correct the server address/IP address and resubmit the job, and/or check with your network administrator for connection verification. If the job continues to fail, contact Compuware Customer Support. STR7541E SERVER REFUSED THE CONNECTION Strobe transfer client encountered a connection refused. Strobe terminates the download.

Explanation: System Action:

User Response: Correct the server address/IP address and resubmit the job, and/or check with your network administrator for connection verification. If the job continues to fail, contact Compuware Customer Support. STR7542E THE CONNECTION FAILED Strobe transfer client could not establish a connection with the network.

Explanation:

Messages Produced by Strobe

3-219

System Action:

Strobe terminates the download.

User Response: Check with your network administrator for connection verification. If the job continues to fail, contact Compuware Customer Support. STR7543E DISCONNECT MESSAGE WAS RECEIVED Strobe transfer client connection was terminated. Strobe terminates the download. Resubmit the job. If the job continues to fail, contact Compuware Customer

Explanation: System Action: User Response: Support. STR7544E

TCP/IP ERROR OCCURED RECEIVING THE DATA Strobe transfer client received an error during RECEIVE processing. Strobe terminates the download. Resubmit the job. If the job continues to fail, contact Compuware Customer

Explanation: System Action: User Response: Support. STR7545E

SESSION HANDSHAKE ERROR Strobe transfer client encountered a handshake error. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7546E

ERROR OCCURRED DURING THE SESSION HANDSHAKE Strobe transfer client encountered a session handshake error. Strobe terminates the download. Contact Compuware Customer Support

Explanation: System Action: User Response: STR7547E

UCS ERROR OCCURRED WITH DATA SENT Strobe transfer client encountered a UCS error sending data to the iStrobe Strobe terminates the download. Contact Compuware Customer Support

Explanation: manager. System Action: User Response: STR7548E

UCS ERROR OCCURRED WITH THE DATA RECEIVED Strobe transfer client encountered a UCS error receiving data from the iStrobe Strobe terminates the download. Contact Compuware Customer Support

Explanation: manager. System Action: User Response: STR7550E

UNKNOWN ERROR RETURNED, RC=xxxxxxxx Strobe transfer client encountered an unknown error. Strobe terminates the download. Contact Compuware Customer Support

Explanation: System Action: User Response: STR7560E

FAILED TO OPEN SYSPRINT. CHECK THAT IT IS ALLOCATED. SYSPRINT allocation failed. Strobe terminates the download. Check for SYSPRINT DD card or Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7561E

FAILED TO OPEN ISTRIN. CHECK THAT IT IS ALLOCATED. ISTRIN allocation failed. Strobe terminates the download. Check for ISTRIN DD card or Contact Compuware Customer Support.

Explanation: System Action: User Response:

3-220

Strobe Messages Guide

STR7562E

FAILURE LOADING MODULE Internal LOAD failure for the module specified. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7563I Explanation: System Action: User Response: STR7564E

Informational message used to display the transfer parameters. None. None required.

PARM ERROR FOR Specified parameter is invalid. Strobe terminates the download. Correct the parameter on the Strobe - Produce a Performance Profile panel.

Explanation: System Action: User Response: STR7570E

DYNAMIC ALLOCATION RC=XXXX ERROR=XXXX INFO=XXXX The PROFILE specified cannot be allocated. Strobe terminates the download.

Explanation: System Action:

User Response: Verify and correct the Sample Dataset Name parameter on the Strobe Produce a Performance Profile panel. STR7571E INPUT PROFILE DATASET FAILED TO OPEN The PROFILE specified cannot be OPENed. Strobe terminates the download.

Explanation: System Action:

User Response: Verify and correct the Sample Dataset Name parameter on the Strobe Produce a Performance Profile panel. STR7572E PROFILE DATASET PROCESSING FAILED Error reading the PROFILE dataset. Strobe terminates the download.

Explanation: System Action:

User Response: Verify the PROFILE contains data and resubmit. If the job continues to fail, contact Compuware Customer Support. STR7573E TRANSFER RESPONSE IS NULLS The response from the iStrobe server is null. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7574E

TRANSFER RESPONSE IS NOT NULL TERMINATED The response from the iStrobe server is not null terminated. Strobe terminates the download. Contact Compuware Customer Support.

Explanation: System Action: User Response: STR7575I

TRANSFER COMPLETE, TERMINATING The transfer has completed, and termination is being performed. None. None Required.

Explanation: System Action: User Response: STR7576I

COS TRANSFER, transfer status Information returned from the COS Alert processor. None.

Explanation: System Action:

Messages Produced by Strobe

3-221

User Response:

None.

Messages Returned by Attribution Data Collectors


Data collectors for attribution routines return the following messages.
STR8110E GETMAIN FAILURE IN program name - UNABLE TO COLLECT ATTRIBUTION DATA The named Strobe program was unable to obtain virtual storage for its work Strobe continues sampling without collecting attribution data. Increase the region size and resubmit the request. Notify the Strobe system

Explanation: area. System Action: User Response: programmer. STR8120E

INVALID INPUT TO modname - ATTRIBUTION WILL BE INCOMPLETE Strobe called the attributor module modname incorrectly.

Explanation:

System Action: Strobe continues sampling without the attribution data and places a dump of the request block in the sample dataset. User Response: STR8130E Notify the Strobe system programmer.

STROBE DOES NOT SUPPORT MEASUREMENT OF lang UNDER subsys

Explanation: You requested attribution data for the language lang, but Strobe does not support programs in the language under the subsystem named in subsys. System Action: User Response: STR8140E Strobe continues sampling without attribution data. Notify the Strobe system programmer.

NOSYNCH IN EFFECT - subsys ATTRIBUTOR DISABLED The measurement session is running with NOSYNCH.

Explanation:

System Action: Strobe continues sampling without collecting attribution data for the subsystem subsys. User Response: STR8205E Notify the Strobe system programmer.

ABEND LIMIT EXCEEDED - CICS ATTRIBUTOR DISABLED

Explanation: Strobe for CICS cannot collect attribution data because it encountered a severe error. System Action: User Response: STR8206E Strobe continues sampling without CICS attribution data. Notify the Strobe system programmer.

MAX NUMBER JVM PROFILES PROCESSED - STRBDKXX DISABLED

Explanation: Strobe will collect Java environment data for up to 50 JVM Profiles seen active in the measured CICS address space. System Action: If more than 50 JVM Profiles were seen active during measurement, only data for the first 50 will be reported. User Response: STR8207W None required.

FAILURE ATTEMPTING TO PROCESS JVM PROFILE INFORMATION

Explanation: Strobe will collect Java environment data for up to 50 JVM Profiles seen active in the measured CICS address space. System Action: If more than 50 JVM Profiles were seen active in the same sample, Strobe will collect data for only the first 50. On later samples, Strobe will collect environment data for JVM Profile it had not yet processed. User Response: None required.

3-222

Strobe Messages Guide

STR8300E

UNACCEPTABLE PARAMETERS PASSED; STRBASSA DISABLING Strobe called the IMS attributor module STRBASSA with an invalid parameter Strobe continues sampling without IMS DL/I attribution data. Notify the Strobe System programmer.

Explanation: list. System Action: User Response:

STR8301W UNABLE TO RECORD DL/I INFORMATION; ATTRIBUTION REPORTS WILL BE INCOMPLETE Explanation: The IMS attributor cannot collect DL/I attribution data because it encountered a severe error. System Action: Strobe continues sampling, but IMS DL/I attribution data will be incomplete. User Response: Notify the Strobe system programmer.

STR8302E ABEND TOLERANCE EXCEEDED FOR STRBASSA - MODULE DISABLED. TRACE VECTOR = text Explanation: The IMS attributor cannot collect DL/I attribution data because it encountered a severe error. The message text text is critical in analyzing this problem. System Action: User Response: STR8304I Strobe continues sampling without IMS DL/I attribution data. Save the message text and notify the Strobe system programmer.

DL/I CAPTURE ACTIVE, TCB=addr Strobe activated DL/I capture at task control block address addr. None. None required.

Explanation: System Action: User Response: STR8306E

STRBDFSB: DL/I CAPTURE DISABLING The DL/I capture experienced severe errors.

Explanation:

System Action: Strobe continues sampling but no longer captures DL/I calls. Strobe will produce a Performance Profile, but the transaction counts and service time data on the Transaction Summary report will be inaccurate. User Response: programmer. STR8307W Check the log for additional error messages and notify the Strobe system

THE DL/I CAPTURE LOST DATA - TRANSACTION COUNTS MAY BE INACCURATE

Explanation: The DL/I capture routine could not collect data on all IMS transaction counts during measurement. Additional DL/I capture routine messages appear in the Strobe log. System Action: Strobe produces the Performance Profile, but IMS transaction counts and service times could be inaccurate. User Response: Check for application abends in the Message Processing Region or other DL/I capture messages in the Strobe MPR log. Notify the Strobe system programmer. STR8308E DL/I CAPTURE INTERNAL ERROR nn

Explanation: A failure occurred in DL/I capture processing. This message may be accompanied by other DL/I capture messages in the Strobe log. System Action: inaccurate. User Response: STR8430E Strobe continues processing; transaction counts and service times could be Notify the Strobe system programmer.

GETMAIN FAILURE IN STRBDSNA FOR block - DBRM ATTRIBUTION DISABLED

Explanation: Strobe cannot obtain enough storage for block, where block may be the DCI WORKAREA or STAGING AREA. System Action: Strobe continues sampling without DBRM attribution data. Strobe will not identify the DBRMs and SQL statements responsible for DB2 CPU activity in the Strobe Performance Profile.

Messages Produced by Strobe

3-223

User Response: programmer. STR8431E

Increase the region size and resubmit the request. Notify the Strobe system

UNABLE TO LOCATE SYSTEM TABLE - DBRM ATTRIBUTION DISABLED Strobe cannot locate an internal table.

Explanation:

System Action: Strobe continues sampling without DBRM attribution data. Strobe will not identify the DBRMs and SQL statements responsible for DB2 CPU activity in the Strobe Performance Profile. User Response: STR8432W Notify the Strobe system programmer.

GETMAIN FAILURE IN STRBDSNA FOR block - SOME DBRMS MAY NOT BE MAPPED Strobe cannot obtain enough storage to map the DBRMs. block may be:

Explanation:

R24 WORKAREA SQL BUFFER DBRM TABLE READ ROUTINE BLDL LIST DCB

System Action: Strobe continues sampling, but some of the DBRMs reported in the Performance Profile may not be indexed. User Response: programmer. STR8436E Increase the region size and resubmit the request. Notify the Strobe system

I/O ERROR, SYNAD EXIT ENTERED dsname, synadaf message

Explanation: Strobe encountered an I/O error using dataset dsname, probably because of a hardware problem. Strobe displays the message from the MVS I/O error handler. System Action: Strobe continues sampling, but it may not index some of the DBRMs reported in the Performance Profile. User Response: STR8437E Notify the Strobe system programmer.

I/O ERROR, DCB ABEND EXIT ENTERED

Explanation: Strobe encountered an I/O error processing the DBRM dataset and has invoked its DCB exit routine. System Action: Strobe continues sampling, but it may not index some of the DBRMs reported in the Performance Profile. User Response: Notify the Strobe system programmer of the problem.

STR8439W UNABLE TO OBTAIN ADB/CPDATA - SOME DBRM ATTRIBUTION INFORMATION MAY BE MISSING Explanation: Strobe encountered an error while obtaining an internal work area.

System Action: Strobe continues sampling without DBRM attribution data. Strobe will not identify the DBRMs and SQL statements responsible for DB2 CPU activity in the Strobe Performance Profile. User Response: STR8440I Notify the Strobe system programmer.

STRBDSNA: Sampling is active - SMO = ******************* A Strobe for DB2 initialization informational message. Processing continues.

Explanation: System Action:

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR8441E UNABLE TO LOCATE SYSTEM TABLE - SQL ATTRIBUTION DISABLED Strobe cannot locate an internal table.

Explanation:

System Action: Strobe continues sampling without attribution data. Strobe does not identify the DBRMs and SQL statements responsible for DB2 CPU activity in the Performance Profile.

3-224

Strobe Messages Guide

User Response:

Notify the Strobe system programmer.

STR8442W GETMAIN FAILURE IN STRBDSNA FOR block, SOME SQL ATTRIBUTION INFORMATION MAY BE MISSING Explanation: Strobe cannot obtain enough storage for attribution processing. block may be:

SPI WORKAREA STS QIT QTK

System Action: Strobe continues sampling, but some attribution information may be missing from the Performance Profile. User Response: programmer. STR8443W MISSING Increase the region size and resubmit the request. Notify the Strobe system

UNABLE TO OBTAIN block - SOME SQL ATTRIBUTION INFORMATION MAY BE Strobe cannot obtain attribution information from the area named in block.

Explanation: block may be:

ADBLOCK SQL STMT SQL BUFFER CMD BUFFER

System Action: Strobe continues sampling, but some attribution information may be missing from the Performance Profile. User Response: If block is SQL STMT, resubmit the request. Otherwise, increase the region size and then resubmit the request. Notify the Strobe system programmer. STR8444W ABEND OCCURRED IN STROBE EXIT, SOME SQL ATTRIBUTION INFORMATION MAY BE MISSING Explanation: severe error. System Action: User Response: STR8447W TCB = addr Strobe for DB2 cannot collect attribution data because it has encountered a Strobe continues sampling without DB2 attribution data. Notify the Strobe system programmer.

DB2 CAPTURE LOST DATA. BEGIN = time1 END = time2 TOTAL RECORDS LOST= nnnn,

Explanation: The Strobe for DB2 buffer became full at time time1. Strobe emptied the buffer at time time2. Records lost, nnnn, reflects the count of the number of times an SQL call was made to DB2 and the data was not captured. The task control block (TCB) address addr is the task with the DB2 connection. System Action: Strobe continues processing; however, the counts and elapsed times reported for some SQL calls may be inaccurate. User Response: Specify a larger buffer for the capture function or increase the sampling rate to allow Strobe to empty the buffer more frequently. STR8449I ACQUIRED DATA SPACE FOR DB2 CAPTURE FUNCTION Strobe for DB2 created a data space to support the DB2 capture function. Strobe continues processing. None required.

Explanation: System Action: User Response:

STR8450I MAXIMUM SQL BUFFER STORAGE REACHED, SPECIFIED = nnn KB, USED = nnn KB, NEEDED = nnnnn BYTES Explanation: Strobe attempted to save a copy of an SQL statement, however it was unable to do so because that would cause the value specified by the MAXMEM parameter to be exceeded. The specified, used, and needed storage values are given. Strobe discards the SQL statement.

Messages Produced by Strobe

3-225

System Action: missing. User Response:

Strobe continues processing but SQL information may be inaccurate or Specify a larger value for the MAXMEM parameter.

STR8451I THE DB2 CAPTURE FUNCTION HAS TERMINATED. REFER TO THE LOG DATA SET FOR INFORMATION Explanation: terminated. System Action: disabled. This message alerts you that the Strobe for DB2 SQL capture function has Strobe continues processing but the Strobe for DB2 capture function is

User Response: View the log error messages describing the problem and follow the recommended response. STR8452E STRBDSNA unable to establish IFI environment While initializing, Strobe was unable to establish a DB2 IFI Trace connection. Strobe continues processing, but the Strobe for DB2 SQL capture function is See message STR8712E for more information.

Explanation: System Action: disabled. User Response: STR8453E

UNABLE TO OBTAIN BUFFER CONTROL AREA

Explanation: Strobe for DB2s attempt to acquire a work area during initialization of the capture facility failed. System Action: disabled. User Response: STR8454E Strobe continues processing but the Strobe for DB2 SQL capture function is Specify a larger region size for the job.

UNABLE TO DETERMINE DB2 ATTACH FACILITY TYPE. DIAGCNAM = values

Explanation: Although Strobe for DB2 recognized that a task control block was connected to DB2, the values values contained in the DB2 allied agent do not match a known type. System Action: disabled. User Response: STR8455E Strobe continues processing but the Strobe for DB2 SQL capture function is Contact Compuware Customer Support.

UNABLE TO PLACE CAPTURE RETURN CODE FROM SSA-AGNT = rc

Explanation: Strobe for DB2 received a non-zero return code, rc, from the Strobe SQL Agent, indicating an error condition. System Action: disabled. User Response: STR8456E Strobe continues processing but the Strobe for DB2 SQL capture function is Contact Compuware Customer Support.

UNABLE TO OBTAIN SHADOW BUFFER. RETURN CODE FROM GETMAIN = rc

Explanation: There is not enough available virtual storage to satisfy a request for a buffer equal in size to CAPTBUFF. The return code is rc. System Action: disabled. User Response: STR8457E Strobe continues processing but the Strobe for DB2 SQL capture function is Either specify a larger region size or reduce the value for CAPTBUFF.

ERROR ON {GETMAIN | FREEMAIN} OF BUFFER CONTROL AREA. ERROR CODE = rc

Explanation: The buffer control area has experienced either a GETMAIN or a FREEMAIN failure. The error code is rc. System Action: For a GETMAIN failure, Strobe capture processing terminates. For a FREEMAIN failure, Strobe continues processing with the original buffer control still allocated. User Response: If the failure is a GETMAIN failure, specify a larger region size. If the failure is a FREEMAIN failure, contact Compuware Customer Support.

3-226

Strobe Messages Guide

STR8458E RECORD CHAIN IN CAPTURE IS BROKEN. ATTEMPTING TO FIND NEXT DATA RECORD BY SCAN OF BUFFER. Explanation: An error occurred in the chaining of address and offset pointers to records being added to the buffer. The pointer to the next record from the last record added does not point to a valid record. Strobe attempts to locate the next sequential record in the buffer by scanning the entire buffer. System Action: If this happens more than five times during a measurement session, Strobe terminates capture processing. User Response: STR8459E RECORD. Contact Compuware Customer Support.

RECORD CHAIN IN CAPTURE IS BROKEN. SETTING LAST REMOVED TO CURRENT

Explanation: An error occurred in the chaining of address and offset pointers to records being added to the buffer. The pointer to the next record from the last record added does not point to a valid record. The Strobe attempt to locate the next sequential record in the buffer by scanning the entire buffer failed. System Action: Strobe continues processing but capture data may be lost, and counts and elapsed time may be inaccurate. User Response: Contact Compuware Customer Support.

STR8460E DB2 CAPTURE ERROR HAS OCCURRED. COUNTS AND TIMES ARE PROBABLY INACCURATE. REFER TO THE LOG Explanation: occurred. System Action: inaccurate. An error condition that is not serious enough to stop capture processing Strobe continues processing, but counts and times reported are probably

User Response: Look in the Strobe log for error messages that describe the problem and follow the recommended action. STR8461I CAPTURE ERROR. CAPTURE POINT = OLD = old NEW = new SAMPLE = sample

Explanation: The address in the DB2 attachment facility that Strobe needed for the Strobe for DB2 capture code to function is overlaid.

old is the address at which the Strobe for DB2 capture facility started new is the address at which it now exists The sample number when Strobe detected this condition is given in sample.
System Action: User Response: STR8462E The Strobe for DB2 capture facility terminates. Contact Compuware Customer Support.

CAPTURE ERROR. CAPTURE FACILITY ERROR FLAG = {SUSPEND | ABENDED} The Strobe for DB2 capture facility encountered either a logical error or an

Explanation: ABEND.

FLAG = SUSPEND indicates a logical error. FLAG = ABENDED indicates that an ABEND occurred in the DB2 capture facility code
System Action: User Response: The Strobe for DB2 capture facility terminates. Contact Compuware Customer Support.

STR8463E CAPTURE FACILITY ERROR ON STORAGE OBTAIN REG 15 = r15, DYNAMIC SQL CANNOT BE PROCESSED Explanation: A storage OBTAIN failed. A buffer area that the DB2 capture facility requires to process dynamic SQL was not available. The value in register 15 upon return of the storage OBTAIN function is given in r15. System Action: SQL. The Strobe for DB2 capture facility continues to function, but only for static

Messages Produced by Strobe

3-227

User Response: Increase the size of the extended private area available to the address space that Strobe is measuring. STR8464I CAPTURE ERROR. TRACE FUNCTION STORAGE OBTAIN FAILED. RETURN CODE = rc

Explanation: Although you submitted the measurement with the DB2 flag setting specified as DEBUG, the storage required for the trace table was not available. The reason for the error is indicated by the return code rc. System Action: data. Strobe continues measuring, but the sample dataset will contain no trace

User Response: Increase the size of the extended private area available to the address space that Strobe is measuring. STR8465I CAPTURE ERROR. TRACE FUNCTION TRACE TABLE CAPACITY EXCEEDED. TRACE INOPERATIVE Explanation: The volume of SQL activity in the address space that Strobe is measuring exceeds the capacity of the default trace table. System Action: Strobe continues measuring, but the trace function terminates.

User Response: Contact Compuware Customer Support to obtain a program temporary fix (PTF) that will enlarge the trace table. STR8467I CAPTURE ERROR. CAPTURE FACILITY ERROR REASON = erc, SAMPLE = sample

Explanation: The Strobe for DB2 capture facility was not able to recognize the control block structure in place in the DB2 attachment facility to locate the SQL. The error reason code, erc, indicates the location in the logic where the control block structure becomes unrecognizable. The sample number when Strobe detected the error is given in sample. System Action: User Response: STR8468E Strobe issues this message. None required. This information appears for diagnostic purposes only.

CAPTURE ERROR. CAPTURE BUFFER TCB WORK AREA OUT OF ROOM

Explanation: The Strobe for DB2 capture buffer TCB area is not large enough to hold all of the DB2 activity present in the address space. System Action: User Response: STR8469E The Strobe for DB2 capture facility terminates. Contact Compuware Customer Support.

CAPTURE TERMINATING - INCOMPATIBLE WITH DSNTRACE ACTIVE

Explanation: The DB2 trace facility DSNTRACE is active in the targeted address space. Strobe cannot measure accurately when DSNTRACE is active. System Action: The Strobe for DB2 capture facility terminates.

User Response: Remove the DSNTRACE DD card from the targeted address space and rerun the Strobe measurement. STR8470I CAPTURE ENDS - MAXIMUM NUMBER OF TCBs ALLOWED TO BE MEASURED HAS BEEN EXCEEDED Explanation: Strobes limit of 400 Task Control Blocks (TCBs) for a DB2 measurement has been exceeded. Strobe for DB2 measurement ends. System Action: User Response: STR8471I Strobe continues processing, without DB2 measurement. None required.

STRBDSNA text

Explanation: A Strobe for DB2 initialization failed to communicate with the SQL agent capture process. The text may be any of the following: SQL Agent (STRBSSA) rejected SSAREQ xxxxxx request SSAREQ Service Request xxxxxx ABENDed SSAREQ Service Request ABENDed with xxxxx DDF DETECTION FAILURE - NO DAB DDF DETECTION FAILURE - NO SYSTABLE

3-228

Strobe Messages Guide

DDF DETECTION FAILURE - NO STRBDSNS DDF DETECTION FAILURE - NO DB2 SUBSYS System Action: User Response: STR8472E SQL capture processing does not occur. Contact Compuware Customer Support.

SQL CAPTURE IS TERMINATED FOR THIS MEASUREMENT - REASON = xx

Explanation: When attempting to initialize SQL capture, flush an SQL statement from the capture data space, or terminate SQL capture, Strobe for DB2 capture processing encountered an error that caused capture processing to be terminated for the measurement. System Action: When attempting to initialize SQL capture, flush an SQL statement from the capture data space, or terminate SQL capture, Strobe for DB2 capture processing encountered an error that caused capture processing to be terminated for the measurement. Values for the reason code xx are as follows: 01 02 03 04 11 12 13 14 15 16 17 32 33 UNABLE TO CREATE THE CAPTURE DATA SPACE UNABLE TO OBTAIN STORAGE FOR THE SHADOW BUFFER UNABLE TO OBTAIN STORAGE FOR THE HOLDING BUFFER REQUEST TO SUBSCRIBE THE MEASUREMENT TO THE SSA FAILED NO ALET DESIGNATED FOR THE CAPTURE DATA SPACE NO START-ADDRESS DESIGNATED FOR THE CAPTURE DATA SPACE NO ADDRESS DESIGNATED FOR THE SHADOW BUFFER INVALID EYECATCHER IN THE INTDATA STATEMENT-HEADER INTDATA HEADER INDICATES THAT STATEMENT IS ALREADY FLUSHED INTDATA HEADER INDICATES ZERO DATA LENGTH INTDATA HEADER INDICATES EXCESSIVE DATA LENGTH UNABLE TO RELEASE SHADOW-BUFFER STORAGE UNABLE TO RELEASE HOLDING-BUFFER STORAGE

System Action: Strobe for DB2 capture processing terminates for this measurement. Measurement processing continues. User Response: STR8473E Contact Compuware Customer Support.

ERRONEOUS STATEMENT COUNT IN CAPTURE DATA SPACE HEADER

Explanation: When Strobe for DB2 invoked the flush routine to flush the SQL data from the capture data space, the count of the number of SQL statements in the data space was zero. System Action: Strobe for DB2 flush processing indicates that the data space has been flushed, thereby making it available to receive SQL statements that may be captured subsequently. User Response: Contact Compuware Customer Support.

STR8475E CONVERSION OF SQL TEXT TO EBCDIC FAILED - RC (xxxxxxxx | yyyyyyyy) VER=n, TNQ=nn, SRC=nnnn, TRG=nnnnn, DDA=nnnnnnn, TBF=nnnnnnn, WBF=nnnnnnn Explanation: Unicode code conversion service failed with xxxxxxxx return and yyyyyyyy reason codes. Therefore, Strobe was unable to convert the text of this SQL statement to EBCDIC. Strobe supplied Unicode code conversion services with the following information: VER: Version number of the Unicode conversion services used TNQ: Technical-search order for the source and target CCSIDs SRC: CCSID of the SQL text in the input buffer TRG: CCSID of the SQL text in the output buffer DDA: Decimal size in bytes of the dynamic data area. This is the working storage area used by Unicode conversion services. TBF: Decimal size in bytes of the target buffer. Unicode conversion services uses this buffer to store the converted results. WBF: Decimal size in bytes of the work buffer. Unicode conversion services uses this buffer to store intermediate results. System Action: Strobe failed to convert this particular SQL statement, but will attempt to convert the text of subsequent SQL statements to EBCDIC. User Response: Determine the reason for the failure by finding the return and reason codes in the IBM Support for Unicode manual. If you do not understand the reason code associated with the return code, contact Compuware Customer Support with the information that Strobe supplied to Unicode conversion services for this SQL statement.

Messages Produced by Strobe

3-229

STR8476W LOAD MODULE xxxxxxxx NOT AVAILABLE - RC=yyyyyyyy, RSN=zzzzzzzz TARGET CCSID 37 USED AS DEFAULT. Explanation: Load module xxxxxxxx (usually DSNHDECP) was not loaded. This module was not found in an APF-authorized concatenation or in the linklist concatenation. System Action: Latin-1, USA). Incoming SQL text from the application is converted to CCSID 37 (EBCDIC

User Response: If code page 37 is not acceptable for your site, update the DSNHDECP load module. Consult the IBM DB2 installation manual on updating DSNHDECP. See the IBM MVS System Codes manual for an explanation of the yyyyyyyy return and zzzzzzzz reason codes returned by the LOAD macro. STR8477W APPLICATION REQUESTING DATA FROM A REMOTE LOCATION location, SQL ATTRIBUTION INFORMATION MAY BE MISSING. Explanation: Strobe for DB2 cannot collect SQL attribution data because it has encountered an application requesting data from the remote location location. System Action: User Response: Strobe continues sampling without DB2 attribution data. Notify the Strobe system programmer.

STR8478W APPLICATION SENDING DATA TO A REMOTE LOCATION, SQL ATTRIBUTION INFORMATION MAY BE MISSING. Explanation: Strobe for DB2 cannot collect SQL attribution data because it has encountered an application requesting data from a remote location. System Action: User Response: STR8505E Strobe continues sampling without DB2 attribution data. Notify the Strobe system programmer.

DML-SEQUENCE NUMBER NOT AVAILABLE - DML ATTRIBUTION INCOMPLETE

Explanation: Strobe could not locate the DML-sequence number in the user program. The user program was not compiled with the CA-IDMS debug protocol. System Action: Strobe continues sampling, but attribution data will be incomplete.

User Response: Recompile the program using the CA-IDMS debug protocol option and resubmit the request. STR8506E GETMAIN FAILURE - ADS/O ATTRIBUTION MODULE STRBADXX DISABLED

Explanation: The ADS/O attribution module STRBADXX cannot obtain sufficient storage for its work area. System Action: User Response: STR8507E Strobe disables ADS/O attribution. Increase the region size and resubmit the request.

ADS/O ATTRIBUTION DISABLED The ADS/O attribution module failed during initialization. Strobe continues sampling but will not attribute any ADS/O dialog activity.

Explanation: System Action:

User Response: Refer to the preceding error message in the Strobe log for the specific reason for the ADS/O attributor module failure. STR8508E GETMAIN FAILURE - SQL ATTRIBUTION MODULE program name DISABLED

Explanation: Strobe was unable to obtain virtual storage to locate and load the CA-IDMS release-specific SQL data collection module. System Action: User Response: STR8509E Strobe disables CA-IDMS attribution. Increase the region size and resubmit the request.

SQL ATTRIBUTION MODULE program name NOT FOUND

Explanation: Strobe was unable to locate and load the CA-IDMS release-specific SQL data collection module. System Action: Strobe continues sampling, but will not attribute any CA-IDMS SQL activity.

3-230

Strobe Messages Guide

User Response: failure. STR8510C REPORTED

Examine the preceding error message in the Strobe log for the cause of this

CA-IDMS IS NOT ACTIVE. TRANSACTION COUNTS AND SERVICE TIMES ARE NOT

Explanation: CA-IDMS has either experienced an ABEND or was terminated before the Strobe measurement session completed. System Action: Strobe will produce a Performance Profile but will not report CA-IDMS transaction counts and service times. User Response: Resubmit the Strobe measurement request and then restart CA-IDMS. To end the Strobe measurement session, issue a SEND,QUIT command before terminating CA-IDMS. STR8600E PARMLIB STROBE NATURAL CONFIGURATION PARAMETERS NOT SUPPLIED IN STROBE

Explanation: Strobe could not invoke Strobe for Natural because it could not find the Natural configuration parameters in the PARMLIB. System Action: User Response: STR8700E Strobe continues sampling without Natural attribution data. Notify the Strobe system programmer.

TCMNAME PARM VALUE parm IS NOT A VALID THREAD CONTROL BLOCK

Explanation: In the Strobe for Adabas/Natural configurations module, STRBANCM, the TCMNAME = parameter value parm for the Natural/CICS region being measured is not the name of a valid Natural Thread control block. System Action: Strobe continues sampling without Natural attribution data.

User Response: Specify the valid Thread control block module name of the Natural/CICS region being measured in the Strobe for Adabas/Natural configurations module, STRBANCM. Reinstall the configurations module as described in the Strobe Installation and Customization Guide. STR8701C ATTRIBUTION SUPPRESSED FOR NATURAL PROGRAM progname - COMPILED date time RECOMPILED compdate comptime Explanation: Strobe has suppressed attribution for Natural program progname because this program was recompiled during the Strobe measurement session. The message gives the date and time the program was originally compiled (date and time) and the date and time the program was recompiled (compdate and comptime). System Action: Strobe stops collecting attribution data for the program that was recompiled.

User Response: Rerun the measurement session. Do not recompile the target Natural program during a Strobe measurement session. STR8702E STROBE DOES NOT SUPPORT MEASUREMENT OF NATURAL UNDER ADABAS

Explanation: You specified NATURAL=Y on the Strobe - Data Collectors panel when measuring an Adabas region. Strobe does not support attribution of Natural triggers and stored procedures running in an Adabas region. System Action: Strobe continues processing but does not collect Natural or Adabas attribution data. User Response: Do not specify NATURAL=Y on the Strobe - Data Collectors panel when measuring an Adabas region. STR8710E STRBDSNA: DDF INITR command failed,RC=XX,RS=XXX

Explanation: The DB2 Attributor SSAREQ0 request to initialize the SQL capture subtask for a DDF Address Space failed with the return code and reason code shown in the message. See Strobe Programmed Terminations on page 4-1 for RC and RS codes. System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer.

Messages Produced by Strobe

3-231

STR8711E

STRBDSNA: INITM command failed,RC=XX,RS=XXX

Explanation: The DB2 Attributor SSAREQ0 request to initialize the SQL capture subtask for a non-DDF Address Space failed with the return code and reason code shown in the message. See Strobe Programmed Terminations on page 4-1 for RC and RS codes. System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer. STR8712E STRBDSNA: STAM command failed,RC=XX,RS=XXX

Explanation: The DB2 Attributor SSAREQ0 request to the SQL capture subtask to start the IFICID collection failed with the return code and reason code shown in the message. See Strobe Programmed Terminations on page 4-1 for RC and RS codes. System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: Collect the meaning/action for the return code and reason code combination from Table 4-1 on page 4-3 and notify the Strobe system programmer. STR8713E STRBDSNA: IFI Environment invalid at close SDS The DB2 Attributor found an invalid or not present IFI environment at Close The DB2 Attributor terminates the Close SDS processing. Notify the Strobe system programmer.

Explanation: SDS time. System Action: User Response: STR8714I

STRBDSNA: IFI Flushing at Close SDS started.

Explanation: The DB2 Attributor has started the final flushing process of the SQL attribution samples, associated to the closing of the Strobe SDS dataset. System Action: User Response: STR8715I None. No action is required. This is an informational message.

STRBDSNA: IFI Command FLSH being issued.

Explanation: The DB2 Attributor has issued an SSAREQ FLSH command as part of the flushing process of the SQL attribution samples, associated to the closing of the Strobe SDS dataset. System Action: User Response: STR8716E None. No action is required. This is an informational message.

STRBDSNA: IFI Flushing at close SDS failed,RC=XX,RS=XXX

Explanation: The SSAREQ FLSH command, issued by the DB2 Attributor as part of the flushing process of the SQL attribution samples at CLOSE SDS time, failed with the return code and reason code shown in the message. See Strobe Programmed Terminations on page 4-1 for RC and RS codes. System Action: The DB2 Attributor terminates the Close SDS processing.

User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer. STR8717E STRBDSNA: IFI Flushing Z6T14 write failed,RC=XX,RS=XXXX

Explanation: The $DSN1 FSHT14 command, issued by the DB2 Attributor as part of the flushing process of the SQL attribution samples at CLOSE SDS time, failed with the return code and reason code shown in the message. See Strobe Programmed Terminations on page 4-1 for RC and RS codes. System Action: The DB2 Attributor terminates the Close SDS processing.

3-232

Strobe Messages Guide

User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer. STR8718E STRBDSNA: IFI Flushing SMO cleanup failed,RC=XX,RS=XXXX

Explanation: The $DSN1 QDEL command, issued by the DB2 Attributor as part of the flushing process of the SQL attribution samples at CLOSE SDS time, failed with the return code and reason code shown in the message. See Strobe Programmed Terminations on page 4-1 for RC and RS codes. System Action: The DB2 Attributor terminates the Close SDS processing.

User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer. STR8719I STRBDSNA: IFI Command FLSH completed.

Explanation: The SSAREQ FLSH command, issued by the DB2 Attibutor as part of the flushing process of the SQL attribution samples at CLOSE SDS time, has been completed successfully. System Action: User Response: STR8720I None. No action is required. This is an informational message.

STRBDSNA: IFI Command MAKZ being issued.

Explanation: The DB2 Attributor has issued an SSAREQ MAKZ command as part of the flushing process of the SQL attribution samples, associated to the closing of the Strobe SDS dataset. System Action: User Response: STR8721E None. No action is required. This is an informational message.

STRBDSNA: IFI Command MAKZ failed,RC=XX,RS=XXX.

Explanation: The SSAREQ MAKZ command, issued by the DB2 Attributor as part of the flushing process of the SQL attribution samples, failed with the return code and reason code shown in the message. See Strobe Programmed Terminations on page 4-1 for RC and RS codes. System Action: The DB2 Attributor terminates the Close SDS processing.

User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer. STR8722I STRBDSNA: IFI Command MAKZ completed.

Explanation: The SSAREQ MAKZ command issued by the DB2 Attibutor as part of the flushing process of the SQL attribution samples has completed successfully. System Action: User Response: STR8723E None. No action is required. This is an informational message.

STRBDSNA: IFI Write ZTYPE records failed,RC=XX,RS=XXX

Explanation: The $DSN1 ZWRIT command, issued by the DB2 Attributor as part of the flushing process of the SQL attribution samples, failed with the return code and reason code shown in the message. System Action: The DB2 Attributor terminates the Close SDS processing.

User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer. STR8724I STRBDSNA: IFI Environment terminating.

Explanation: The DB2 Attributor has issued an SSAREQ TERM command as part of the flushing process of the SQL attribution samples, associated to the closing of the Strobe SDS dataset.

Messages Produced by Strobe

3-233

System Action: User Response: STR8725I

None. No action is required. This is an informational message.

STRBDSNA: IFI Flushing at CLOSE SDS complete

Explanation: The SSAREQ TERM command issued by the DB2 Attibutor as part of the flushing process of the SQL attribution samples has completed successfully. System Action: User Response: STR8726I None. No action is required. This is an informational message.

STRBDSNA: IFI Flushing at CPU IDENT time enabled

Explanation: The DB2 Attributor issues this message upon receiving the first CPU Identify Call from the Strobe driver to indicate that flushing processing at CPU Identify time has been activated. System Action: User Response: STR8727I None. No action is required. This is an informational message.

STRBDSNA: IFI Flushing at CPU IDENT suspended.

Explanation: The DB2 Attributor issues this message upon receiving a signal from the SQL Agent the first IFCID for the measured address space has been captured. This message indicates that flushing processing at CPU Identify time has been suspended. System Action: User Response: STR8728E None. No action is required. This is an informational message.

STRBDSNA: IFI Flushing at CPU IDENT failed,RC=XX,RS=XXX

Explanation: The SSAREQ FLSH command, issued by the DB2 Attributor as part of the flushing process of the SQL attribution samples at CPU IDENT time, failed with the return code and reason code shown in the message. See Strobe Programmed Terminations on page 4-1 for RC and RS codes. System Action: The DB2 Attributor terminates the CPU IDENT processing.

User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer. STR8729E STRBDSNA: IFI Flushing Z6T14 write failed,RC=XX,RS=XXXX

Explanation: The $DSN1 FSHT14 command, issued by the DB2 Attributor as part of the flushing process of the SQL attribution samples at CPU IDENT time, failed with the return code and reason code shown in the message. System Action: The DB2 Attributor terminates the CPU IDENT processing.

User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer. STR8730E STRBDSNA: IFI Flushing SMO cleanup failed,RC=XX,RS=XXXX

Explanation: The $DSN1 QDEL command, issued by the DB2 Attributor as part of the flushing process of the SQL attribution samples at CPU IDENT time, failed with the return code and reason code shown in the message. System Action: The DB2 Attributor terminates the CPU IDENT processing.

User Response: Collect the meaning/action for the return code and reason code combination from Strobe Programmed Terminations on page 4-1 and notify the Strobe system programmer. STR8731E STRBDSNA: Check Strobe environment failure - no MSCB The DB2 Attributor was unable to find internal Strobe MSCB Control Block.

Explanation:

System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution.

3-234

Strobe Messages Guide

User Response: STR8732E

Notify the Strobe system programmer.

STRBDSNA: Check Strobe environment failure - no CPWRTBL The DB2 Attributor was unable to find internal Strobe CPWRTBL Control

Explanation: Block.

System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: STR8733E Notify the Strobe system programmer.

STRBDSNA: Check Strobe environment failure - no SAG. The DB2 Attributor was unable to find internal Strobe SAG Control Block.

Explanation:

System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: STR8734E Notify the Strobe system programmer.

STRBDSNA: Check Strobe environment failure - invalid SAG The DB2 Attributor has detected an invalid internal Strobe SAG Control Block.

Explanation:

System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: STR8735E Notify the Strobe system programmer.

STRBDSNA: Check Strobe environment failure - no SAL. The DB2 Attributor was unable to find internal Strobe SAL Control Block.

Explanation:

System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: STR8736E Notify the Strobe system programmer.

STRBDSNA: DDF detection failure - no DAB.

Explanation: The DB2 Attributor was unable to find internal Strobe DAB Control Block for a DB2 DDF Strobe measurement. System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: STR8737I Notify the Strobe system programmer.

STRBDSNA: DDF measurement detected. The DB2 Attributor has detected a DB2 DDF measurement. None. No action is required. This is an informational message.

Explanation: System Action: User Response: STR8738E

STRBDSNA: Check Strobe environment failure - no #IFT. The DB2 Attributor was unable to find internal Strobe #IFT Control Block.

Explanation:

System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: STR8739E Notify the Strobe system programmer.

STRBDSNA: Check Strobe environment failure - no DFT. The DB2 Attributor was unable to find internal Strobe DFT Control Block.

Explanation:

System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: STR8740E Notify the Strobe system programmer.

STRBDSNA: Invalid Strobe environment detected.

Explanation: The DB2 Attributor was unable to find a required internal Strobe Control Block.

Messages Produced by Strobe

3-235

System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: STR8741E Notify the Strobe system programmer.

STRBDSNA: Check Strobe environment failure - no #SSB. The DB2 Attributor was unable to find internal Strobe SSB Control Block.

Explanation:

System Action: The DB2 Attributor is disabled. Strobe continues sampling without collecting attribution. User Response: STR8742I Notify the Strobe system programmer.

STRBDSNA: SQL activity has been detected.

Explanation: The DB2 Attributor has detected SQL activity generated by the User Application being measured. System Action: User Response: STR8743I Strobe continues sampling without collecting attribution. No action is required.This is an informational message.

STRBDSNA: Unable to get DB2 Release info - xxxxxxxxxxxxxxxxxx

Explanation: The DB2 Attributor was unable to determine the DB2 Version and Release information for a DDF measurement. System Action: User Response: STR8744I Strobe measurement is terminated. No action is required. This is an informational message.

STRBDSNA: DB2 V### not supported. No SQL Attribution done for DB2: ####

Explanation: The DB2 Attributor has detected SQL activity generated for a DB2 subsystem Version 7 or lower. System Action: Local: Strobe continues sampling without SQL attribution. DDF: Strobe continues without sampling and without SQL attribution. User Response: STR8745I No action is required. This is an informational message.

STRBDSNA: Parameter SSA=No is in effect. SQL Attribution not possible.

Explanation: The Strobe Parameter member contains SSA=NO. This causes no Strobe SQL Agent to be active, so SQL cannot be detected for attribution. System Action: Measurement continues without SQL attribution.

User Response: None required. This is an informational message for the use of Compuware Customer Support only. STR8746I STRBDSNA: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx(NNNNN)

Explanation: Strobe DB2 SQL Attributor issues this message to display the reason for the IFI Trace activation or inactivation, where: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx shows the reason of the activation/inactivation. Valid values are:

Active per User Request Disable per User Request Disable per Invalid Capture Options. NNNNN shows the combination of internal flags that lead to the IFI trace activation or inactivation. This message is issued to assist Compuware Customer Support in problem determination.
System Action: The Strobe DB2 SQL Attributor continues processing.

User Response: No action is required. This is an informational message for the use of Compuware Customer Support only. STR8747I STRBDSNA: TERM call received from Attribution driver. Strobe for DB2 termination message. Termination continues.

Explanation: System Action:

3-236

Strobe Messages Guide

User Response: None required. This is an informational message for the use of Compuware Customer Support only.

Messages Returned by Strobe SQL Analysis


Strobe SQL analysis returns the following messages.
STR9501I PLAN_TABLE CREATED FOR AUTHORIZATION ID authID

Explanation: Strobe SQL analysis created an instance of PLAN_TABLE for authorization ID authID during Profile creation. System Action: User Response: STR9502E Processing continues. None required.

GENERATION OF QUERY NUMBER FAILED, SEE PRECEDING MESSAGE(S)

Explanation: Strobe SQL analysis cannot generate a unique query number for an SQL statement it processed. System Action: User Response: STR9503E Strobe SQL analysis attempts to process that statement again. Refer to preceding messages for additional information.

NO UNIQUE QUERY NUMBERS ARE AVAILABLE

Explanation: Strobe SQL analysis cannot generate a unique query number for SQL statements it processes because all possible unique query numbers in PLAN_TABLE are used. System Action: User Response: STR9504E Processing for the current Profile stops. Delete rows from PLAN_TABLE and resubmit the Profile creation request.

MEMORY ALLOCATION FAILED Strobe SQL analysis cannot allocate sufficient virtual storage. Processing for the current Profile/statement stops.

Explanation: System Action:

User Response: If you were creating a Performance Profile including SQL Analysis information when you received this message, try reducing the number of SQL statements that are processed and then recreate the Profile.

Several parameters can reduce the number of SQL statements processed: TOTAL CPU PERCENT or TOP N USERS TOTAL WAIT TIME or TOP N WAIT DBRM NAME For information on how to specify these parameters, see the Strobe User Guide. In addition, if you are using SQL Analysis with DDF reports, you can limit the number of SQL statements processed by SQL Analysis by using DDF thresholds and filters. For more information, see the Strobe for DB2 option manual. If you were not creating a Performance Profile including SQL Analysis information, increase your region size.
STR9505E SQL STATEMENT PARSE NOT COMPLETED, SEE PRECEDING MESSAGE(S)

Explanation: Strobe SQL analysis has encountered an error while processing a SQL statement. Either Strobe SQL analysis encountered an internal error or the SQL verb is not processed by Strobe SQL analysis. System Action: User Response: STR9506I Processing for the current SQL statement stops. Refer to preceding messages for additional information.

THE FOLLOWING STATEMENT IS NOT DML sqlstemtext The SQL statement text is not a valid DML statement.

Explanation:

Messages Produced by Strobe

3-237

System Action: Processing for the current SQL statement stops. Processing continues with the next statement. User Response: None required. Only DML SQL statements (that manipulate data such as SELECT, INSERT, UPDATE and DELETE) are processed by Strobe SQL analysis. STR9507E ERROR OCCURRED DURING ACCESS OF PLAN_TABLE, SEE PRECEDING MESSAGE(S)

Explanation: An attempt by Strobe SQL analysis during Profile creation either to create an instance of PLAN_TABLE for the resolved authorization ID or to locate an instance of PLAN_TABLE when using existing PLAN_TABLE rows failed. System Action: Processing for the current Profile stops.

User Response: If the Profile request specified use of existing PLAN_TABLE rows, ensure that an instance of PLAN_TABLE exists for the specified authorization ID. Otherwise, refer to preceding messages for additional information. STR9508E RETRIEVAL OF TABLE TYPE FOR tablename FAILED An attempt to retrieve the table type for table tablename failed. Processing for the current SQL statement stops.

Explanation: System Action:

User Response: Ensure tablename identifies an existing table in the catalog of the DB2 subsystem against which Strobe SQL analysis connected. STR9509E RETRIEVAL OF TEXT FOR ALIAS aliasname FAILED, SEE PRECEDING MESSAGE(S) An attempt to retrieve the text for alias aliasname failed. Processing for the current SQL statement stops. Refer to preceding messages for additional information.

Explanation: System Action: User Response: STR9510E

RETRIEVAL OF TEXT FOR VIEW viewname FAILED, SEE PRECEDING MESSAGE(S) An attempt to retrieve the SQL statement text for view viewname failed. Processing for the current SQL statement stops. Refer to preceding messages for additional information.

Explanation: System Action: User Response: STR9511E

PROCESSING OF CAF SERVICE service FAILED: RC = rc RE = X're'

Explanation: A DB2 Call Attach Facility error occurred processing service request service with return code rc and reason code re.

Refer to accompanying message STR9512I, STR9513I, or STR9514I for additional information.


System Action: User Response: STR9512I Processing for the current file stops. Notify the Strobe system programmer of the problem.

CAF CONNECT PARAMETERS: SSID: (subsystemID)

Explanation: subsystemID identifies the DB2 subsystem to which Strobe SQL analysis attempted to connect through the DB2 Call Attach Facility. If subsystemID is blank, the sample dataset was probably created with a version of Strobe prior to Version 1 Release 9.2. System Action: Processing for the current file stops

User Response: Specify the ID of the subsystem in the DB2 SUBSYSTEM field of the Strobe SQL Analysis Feature Report Settings panel. If subsystemID is not blank, ensure the subsystem is available, then resubmit the Profile creation request.

Refer to accompanying message STR9511E for additional information. Notify the Strobe system programmer of the problem.
STR9513I CAF OPEN PARAMETERS: SSID: (subsystemID) PLAN: (planname)

Explanation: subsystemID identifies the DB2 subsystem with which Strobe SQL analysis attempted to open plan planname through the DB2 Call Attach Facility.

planname should be STRANANA, the application plan created during installation of Strobe SQL analysis.

3-238

Strobe Messages Guide

System Action:

Processing for the current profile stops.

User Response: If subsystemID is available, ensure that planname exists and that the resolved authorization ID has EXECUTE privilege for planname. Then resubmit the Profile creation request.

Refer to accompanying message STR9511E for additional information. Notify the Strobe system programmer of the problem.
STR9514I CAF CLOSE PARAMETERS: TERM: (termoption)

Explanation: termoption identifies the option used to terminate the thread created previously with the open service request through the DB2 Call Attach Facility. System Action: User Response: Processing for the current profile stops. Refer to accompanying message STR9511E for additional information.

Notify the Strobe system programmer of the problem.


STR9515E LOAD OF MODULE modname FAILED

Explanation: An attempt to load module modname from either a link list dataset or the library specified by STEPLIB failed. System Action: User Response: STR9516E Processing for the current profile stops. Notify the Strobe system programmer of the problem.

CREATION OF TEMPORARY FILE FAILED Strobe SQL analysis cannot allocate a temporary file. Processing for the current Profile stops. Notify the Strobe system programmer of the problem.

Explanation: System Action: User Response: STR9517E

ALLOCATION OF TABLE INDEX FAILED Strobe SQL analysis cannot allocate an internal table. Processing for the current Profile stops. Notify the Strobe system programmer of the problem.

Explanation: System Action: User Response: STR9518E

ALLOCATION OF PLAN BUFFER FAILED Strobe SQL analysis cannot allocate an internal table. Processing for the current Profile stops. Notify the Strobe system programmer of the problem.

Explanation: System Action: User Response: STR9519E

DEFINITION FOR PLAN planname NOT FOUND Strobe SQL analysis cannot retrieve the application qualifier for plan planname.

Explanation:

The sample dataset for which a Profile request was submitted contains the qualifier.
System Action: User Response: STR9521E Processing for all SQL statements associated with planname stops. Ensure that planname identifies a valid plan in the DB2 catalog.

EXPLAIN FAILED, SEE PRECEDING MESSAGE(S) An attempt to issue an SQL EXPLAIN failed. Processing for the current SQL statement stops.

Explanation: System Action:

User Response: If you receive the DB2 error message SQL=-104, a possible cause may be that Strobe SQL analysis is attempting to process truncated static SQL statements. Your application may contain statements greater than 4,096 bytes in length, but a DB2 limitation prevents Strobe from reporting on statements of that length. Refer to messages following STR9531I for additional information.

Messages Produced by Strobe

3-239

STR9522E

DELETE FAILED, SEE PRECEDING MESSAGE(S)

Explanation: An attempt to issue an SQL DELETE failed. This occurs at the end of processing for a DB2 subsystem only. System Action: User Response: STR9523E Processing for the current SQL statement stops. Refer to messages following STR9531I for additional information.

ATTEMPT TO GET OR SET AUTHORIZATION ID FAILED, SEE PRECEDING MESSAGE(S)

Explanation: An attempt to either retrieve the primary authorization ID or set a secondary authorization ID failed. System Action: User Response: STR9524E Processing for the current Profile stops. Refer to preceding messages for additional information.

SET FAILED An attempt to issue an SQL SET failed. Processing for the current Profile stops. Refer to messages following STR9531I for additional information.

Explanation: System Action: User Response: STR9525E

PREPARE FAILED sqlstmttext...

Explanation: An attempt to issue an SQL PREPARE for the SQL statement identified by sqlstmttext failed. System Action: User Response: STR9526E Processing for the current SQL statement stops. Refer to messages following STR9531I for additional information.

OPEN CURSOR FAILED An attempt to issue an SQL OPEN CURSOR failed. Processing for the current SQL statement stops. Refer to messages following STR9531I for additional information.

Explanation: System Action: User Response: STR9527E

FETCH FAILED An attempt to issue an SQL FETCH failed. Processing for the current SQL statement stops. Refer to messages following STR9531I for additional information.

Explanation: System Action: User Response: STR9528E

CLOSE CURSOR FAILED An attempt to issue an SQL CLOSE CURSOR failed. Processing continues. Refer to messages following STR9531I for additional information.

Explanation: System Action: User Response: STR9529E

CREATE TABLE FAILED An attempt to issue an SQL CREATE TABLE failed. Processing for the current Profile stops. Refer to messages following STR9531I for additional information.

Explanation: System Action: User Response: STR9530E

EXEC IMMEDIATE FAILED sqlstmttext...

Explanation: An attempt to issue an SQL EXEC IMMEDIATE for the SQL statement identified by sqlstmttext failed. System Action: User Response: STR9531I Processing for the current SQL statement stops. Refer to messages following STR9531I for additional information.

DB2 MESSAGES BEGIN: The SQL Communication Area (SQLCA) and message text produced for a DB2

Explanation: error begins.

3-240

Strobe Messages Guide

If you receive the DB2 error message SQL=-104, a possible cause may be that Strobe SQL analysis is attempting to process truncated static SQL statements. Your application may contain statements greater than 4,096 bytes in length, but a DB2 limitation prevents Strobe from reporting on statements of that length.
System Action: User Response: apparent. STR9532I Processing continues reporting the DB2 error. Notify Compuware Customer Support if the cause of the problem is not

DB2 MESSAGES END The SQL Communication Area (SQLCA) and message text produced for a DB2 Processing of the DB2 request terminates. None required.

Explanation: error end. System Action: User Response:

STR9533E GENERATION OF STATISTICS FOR CURRENT SUBSYSTEM FAILED, SEE PRECEDING MESSAGE(S) Explanation: System Action: continues. User Response: STR9534E An error occurred while generating the Catalog Statistics report. Strobe SQL Analysis processing terminates. Performance Profile creation Refer to preceding messages for additional information.

INVALID SQL STATEMENT sqlstmttext An error was found in the text of SQL statement sqlstmttext. Processing for the current SQL statement stops. Notify Compuware Customer Support of the problem.

Explanation: System Action: User Response: STR9535E

GENERATION OF stattype STATISTICS FAILED, SEE PRECEDING MESSAGE(S)

Explanation: An error occurred during generation of the stattype statistics, where stattype is one of the following:

Table Column Index Index partition Non-uniform column Tablespace Tablespace partition
Processing for the current profile stops. Refer to preceding messages for additional information.

System Action: User Response: STR9536E

DATABASE RESOURCE UNAVAILABLE, SEE FOLLOWING MESSAGE(S)

Explanation: A DB2 Call Attach Facility error occurred processing an open service request because a required resource is not available. System Action: Processing for the current profile stops.

User Response: Ensure that the Strobe SQL analysis plan STRANANA exists in the DB2 subsystem identified in message STR9513I.

Refer to the message block beginning with STR9531I that follows STR9536E to identify the unavailable resource.
STR9537E TABLE DEFINITION FOR tablename NOT FOUND

Explanation: Strobe SQL analysis encountered an internal error attempting to retrieve a control block for table tablename. System Action: User Response: Processing for the current SQL statement stops. Notify Compuware Customer Support of the problem.

Messages Produced by Strobe

3-241

STR9538E

INVALID EXECUTION TYPE: exectype The statement execution type exectype passed to Strobe SQL analysis is invalid. Processing for the current SQL statement stops. Notify Compuware Customer Support of the problem.

Explanation: System Action: User Response: STR9540E

REPORT reportnumber NOT FOUND

Explanation: An attempt by Strobe SQL analysis to locate report reportnumber in the sample file when using existing PLAN_TABLE rows failed.

Either no DB2 SQL activity was recorded during measurement or an error occurred during measurement, so the DB2 information required to complete the Profile request is incomplete.
System Action: User Response: apparent. STR9542E Processing for the Profile stops. Notify Compuware Customer Support of the problem if the cause is not

ALLOCATION OF CURSOR INDEX FAILED Strobe SQL analysis cannot allocate sufficient virtual storage for an internal Processing for the current Profile stops. Notify the Strobe system programmer of the problem.

Explanation: table. System Action: User Response: STR9543E

CURSOR INDEX BUILD FAILED Strobe SQL analysis cannot build an internal table. Processing for the current Profile stops.

Explanation: System Action:

User Response: Refer to accompanying message STR9504E or messages following STR9531I for additional information. STR9544E NO PLAN_TABLE ROWS FOR STATEMENT mfstmtnumber (srcstmtnumber) IN objecttype objectname OF PLAN planname Explanation: An attempt by Strobe SQL analysis to locate existing PLAN_TABLE rows for statement mfstmtnumber (srcstmtnumber) in objecttype objectname of plan planname failed.

objecttype identifies objectname as either a package or a DBRM. mfstmtnumber is the SQL statement number assigned by Strobe. srcstmtnumber is the SQL statement number assigned by the DB2 precompiler that EXPLAIN inserts into the QUERYNO column of table PLAN_TABLE. One of the following has occurred: EXPLAIN(YES) was not specified when objectname was bound into plan planname. The resolved authorization ID does not qualify the correct instance of PLAN_TABLE.
System Action: Processing for the current SQL statement stops.

User Response: Check the AUTHID and USEPTRWS options. Notify Compuware Customer Support of the problem if it cannot be resolved by changing options. STR9545E NO EXISTING PLAN_TABLE FOUND FOR AUTHORIZATION ID authID

Explanation: An attempt by Strobe SQL analysis to locate an instance of PLAN_TABLE for authorization ID authID when using existing PLAN_TABLE rows failed. System Action: Processing of SQL statements for the current collection or DBRM stops.

User Response: See the following message, STR9562E, to identify the collection/DBRM name. Check the AUTHID and USEPTRWS options. Notify Compuware Customer Support of the problem if the problem cannot be resolved by changing options.

3-242

Strobe Messages Guide

STR9546E

NO INDEX SLOTS AVAILABLE, CURRENT NUMBER OF SLOTS IS slotcount Strobe SQL analysis encountered an overflow in an internal table of size Processing for the current SQL statement stops. Notify Compuware Customer Support of the problem.

Explanation: slotcount. System Action: User Response: STR9547W

CURRENT OF CURSOR NOT PROCESSED: sqlstmttext

Explanation: Strobe SQL analysis does not process SQL statements containing a WHERE CURRENT OF clause.

Refer the declaration of the cursor in sqlstmttext for access path information.
System Action: User Response: STR9550E Processing for the current SQL statement stops. None required.

CURSOR INDEX ENTRY entry NOT FOUND

Explanation: An attempt by Strobe SQL analysis to locate internal index entry entry when using existing PLAN_TABLE rows failed. System Action: Processing for the current SQL statement stops.

User Response: If you have the required DB2 privileges, resubmit the Profile creation request without specifying Y in the USE EXISTING PLAN-TABLE ROWS field on the Strobe - SQL Analysis Feature Report Settings panel.

Notify Compuware Customer Support of the problem.


STR9551E LOAD OF RULE THRESHOLD SET ruleset FAILED An attempt by Strobe SQL analysis to load rule threshold set ruleset failed. Processing for the current Profile stops.

Explanation: System Action:

User Response: Ensure that the value of ruleset specified in the RULE THRESHOLD SET field of the Strobe - SQL Analysis Feature Report Settings panel identifies a valid, loadable PDS member, and that the member is in a library that is available to SQL Analysis during Profile creation. STR9552E UNDEFINED TOKEN TEXT: tokenid (firsttoken)

Explanation: An attempt by Strobe SQL analysis to locate an entry for token tokenid in an internal table failed. System Action: Processing for the current SQL statement continues, but the text (undefined) will appear in the Translation report. User Response: STR9553E Notify Compuware Customer Support of the problem.

I/O ERROR ON FILE ID fileid: text

Explanation: Strobe SQL analysis encountered an I/O error while processing the file identified by fileid. text describes the reason for the error.

Note:

A fileid of //tmp:## is the equivalent of DDNAME SYSTMP##.


Processing for the current Profile stops. Notify Compuware Customer Support if the cause of the problem is not

System Action: User Response: apparent. STR9554E

INVALID EXECUTION TYPE FOR EXISTING PLAN_TABLE ROWS: exectype

Explanation: The statement execution type exectype passed to Strobe SQL analysis is not a valid type when using existing PLAN_TABLE rows; existing PLAN_TABLE rows can be used for embedded, static SQL statements associated with DBRMs for which Strobe recorded measurement activity. System Action: Processing for the current SQL statement stops.

Messages Produced by Strobe

3-243

User Response: Enter N in the USE EXISTING PLAN-TABLE ROWS field in the Strobe - SQL Analysis Feature Report Settings panel and recreate the Profile. STR9555E EXPECTED TOKEN NOT FOUND IN STATEMENT: mfstmtnumbertext:sqlstmttext

Explanation: An internal error occurred in Strobe SQL analysis while parsing SQL statement sqlstmttext, where mfstmtnumber is the SQL statement number assigned by Strobe. System Action: User Response: STR9556E Processing for the current SQL statement stops. Notify Compuware Customer Support of the problem.

ALLOCATION OF DATABASE OBJECT BUFFER FAILED Strobe SQL analysis cannot allocate an internal table. Processing for the current SQL statement stops. Notify the Strobe system programmer of the problem.

Explanation: System Action: User Response: STR9557E

RETRIEVAL OF DATABASE OBJECT object FAILED Strobe SQL analysis cannot resolve the definition for database object object. Processing for the current SQL statement stops.

Explanation: System Action:

User Response: Ensure that object identifies an existing database object in the catalog of the DB2 subsystem against which Strobe SQL analysis connected.

To determine to which subsystem Strobe SQL analysis connected, first review the PF Parameters line in the Report Parameters section of the Measurement Session Data report. If you requested that Strobe SQL analysis connect to a specific DB2 subsystem, the report displays that subsystem ID following PF parameter SSID. Otherwise, Strobe SQL analysis connected to the subsystem identified in the Subsystems line of the Measurement Parameters section in the Measurement Session Data report. If object does identify a valid object in the DB2 subsystem, refer to the messages that precede STR9557E for additional information.
STR9558E DEFINITION FOR objecttype objectname NOT FOUND

Explanation: Strobe SQL analysis cannot retrieve objectname that exists in the sample dataset for which a Profile request was submitted. objecttype identifies a package or DBRM. System Action: Processing for all SQL statements associated with objectname stops.

User Response: Ensure that objectname identifies a valid object of type objecttype in the DB2 catalog of the DB2 subsystem to which Strobe SQL analysis connected. STR9559W OPEN FOR TRACE OUTPUT FILE FAILED, TRACE OPTION DISABLED Strobe SQL analysis cannot open the file into which it writes trace output. Strobe SQL analysis disables generation of trace output for the Profile.

Explanation: System Action:

For batch jobs, Strobe SQL analysis writes trace output to the file defined for ddname SYSTERM.
User Response: the job. Insert a data definition statement for SYSTERM into your JCL and resubmit

STR9560E INCOMPLETE PLAN_TABLE DEFINED FOR AUTHORIZATION ID authID OR SQL STATEMENT CONTAINS CORRELATED REFERENCE THAT IS NOT DEFINED IN THE SQL STATEMENT BEING EXPLAINED Explanation: The instance of PLAN_TABLE defined for authorization ID authID does not contain all the columns required by Strobe SQL analysis. System Action: User Response: Processing for the current Profile stops. See the Response for each Scenario below.

Scenario 1: User has selected USE SELECTED PLAN_TABLE ROWS =Y and CREATOR ID=XXX where XXX is the prefix of the existing plan table. For example, if

3-244

Strobe Messages Guide

DB2P.PLAN_TABLE is what the customer uses, they should specify DB2P as the CREATOR ID. Problem: If the STR9560E error occurs, this indicates the customer is using a PLAN_TABLE that is back-leveled in DB2 support. For example, the Strobe measurement could have been for DB2 Version 7.1. so SQLAF expects a 7.1-formatted PLAN_TABLE. However, the existing PLAN_TABLE does not have the additional columns that have added for DB2 V7.1 Instead, the PLAN_TABLE may still be in DB2 V6.1 or V5.1 format. SQLAF will fail when it does the SELECT for that statement because the columns may be missing from that PLAN_TABLE. Response: Either DROP the instance of PLAN_TABLE defined for authID and let Strobe SQL analysis create a new instance during a subsequent Profile request, or ALTER the PLAN_TABLE so that it includes the complete set of columns that you can define for PLAN_TABLE. Scenario 2: User has selected DYNAMIC EXPLAIN WHERE USE EXISTING PLAN_TABLE ROWS=N, CREATOR ID should be blank and AUTH ID may be specified but isnt required. Problem: If the STR9560E error occurs, this indicates the customer is using a PLAN_TABLE that is back-leveled in DB2 support. Even for DYNAMIC EXPLAIN, If a user is dynamically generating EXPLAIN for a SQL statement into a PLAN_TABLE that already exists, SQLAF will process cleanly on the EXPLAIN, but will fail when it attempts to select that row, just as in Scenario 1. Refer to the IBM manuals IBM DATABASE 2 SQL Reference and IBM DATABASE 2 Administration Guide, Volume III for additional information regarding the definition of PLAN_TABLE. Response: Either DROP the instance of PLAN_TABLE defined for authID and let Strobe SQL analysis create a new instance during a subsequent Profile request, or ALTER the PLAN_TABLE so that it includes the complete set of columns that you can define for PLAN_TABLE. Scenario 3: The STR9560E message is preceded by an STR9531I DB2 MESSAGES BEGIN: SQLCODE= -206 correlation-name.column IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE, OR IS NOT THE COLUMN OF THE TRIGGERING TABLE OF A TRIGGER and STR9530E EXEC IMMEDIATE FAILED error message for an EXPLAIN SQL statement. The SQL statement being explained by SQLAF was captured from a Trigger that was executed during a Strobe DB2 measurement session. The correlation-name can be either a DB2 correlated reference or table identifier found in a REFERENCING clause for a CREATE TRIGGER. Refer to the DB2 SQL Reference manual for the complete CREATE TRIGGER syntax. Problem: The SQL in the EXPLAIN statement contains a reference to a column name using a correlation name or table identifier that is defined in the REFERENCING clause of a CREATE TRIGGER. Because the reference is defined outside the actual SQL statement being explained, DB2 is not able to determine what object the correlation name or table identifier refers to. Response: There is no workaround that allows the EXPLAIN statement to be successfully processed. The SQLAF processing will continue, but no information (EXPLAIN information, Statistics, Observations, etc.) will be generated for this SQL statement.
STR9561E STR9561E DB2 VERSION version NOT SUPPORTED

Explanation: The version of Strobe SQL analysis that you invoked while creating a Profile does not support the version of DB2 identified in version. System Action: User Response: Processing for the current Profile stops. Notify the Strobe system programmer.

Messages Produced by Strobe

3-245

STR9562E

ATTEMPT TO SET COLLECTION ID collid FAILED, SEE PRECEDING MESSAGE(S)

Explanation: An attempt by Strobe SQL analysis to use the package set identified by collection collid failed. System Action: Processing for the current Profile stops.

User Response: To determine for which collection ID, Strobe SQL analysis generated this message, refer to the value following CATCRID in the PF Parameters line of the Report Parameters section in the Measurement Session Data report.

Also, refer to the messages that precede STR9562E for additional information.
STR9563E ALLOCATION OF TOKEN STACK FAILED Strobe SQL analysis cannot build an internal table. Processing for the current SQL statement stops. Refer to accompanying message STR9504E for additional information.

Explanation: System Action: User Response: STR9564E

UNDEFINED TOKEN FOUND: tokentext

Explanation: Strobe SQL analysis encountered an undefined token tokentext while parsing the current SQL statement. System Action: Processing for the current SQL statement stops.

User Response: Refer to accompanying message STR9555E for additional information. Notify Compuware Customer Support of the problem. STR9565W PROCESSING FOR STATEMENT mfstmtnumber IN objecttype objectname OF PLAN planname WAS UNSUCCESSFUL Explanation: Strobe SQL analysis did not successfully process SQL statement mfstmtnumber in DBRM objectname bound to plan planname:

mfstmtnumber is the SQL statement number assigned by Strobe for DB2. objecttype identifies objectname as either a package or a DBRM. planname identifies the plan into which the user bound objectname.
System Action: User Response: STR9566I Processing for the current SQL statement stops. Refer to the messages that precede STR9565W for additional information.

FUNCTION_TABLE CREATED FOR AUTHORIZATION ID authID

User Response: Strobe SQL analysis created an instance of FUNCTION_TABLE for authorization ID authID during Profile creation. System Action: User Response: STR9567W MESSAGES Strobe continues processing. None required.

ERROR OCCURRED DURING ACCESS OF FUNCTION_TABLE, SEE PRECEDING

Explanation: An attempt by Strobe SQL analysis during Profile creation either to create an instance of FUNCTION_TABLE for the resolved authorization ID or to locate an instance of FUNCTION_TABLE when using existing PLAN_TABLE rows failed. System Action: The user-defined function section of the Translation report will not appear.

User Response: If the Profile request specified use of existing PLAN_TABLE rows, ensure that an instance of FUNCTION_TABLE exists for the specified authorization ID. Otherwise, refer to preceding messages for additional information. STR9568W ALLOCATION OF FUNCTION TABLE BUFFER FAILED Strobe SQL analysis cannot allocate an internal table. Processing continues. Notify the Strobe system programmer of the problem.

Explanation: System Action: User Response:

3-246

Strobe Messages Guide

STR9569W

INCOMPLETE FUNCTION_TABLE DEFINED FOR AUTHORIZATION ID authID

Explanation: The instance of FUNCTION_TABLE defined for authorization ID authID does not contain all the columns required by Strobe SQL analysis. System Action: The user-defined function section of the Translation report will not appear.

User Response: Either DROP the instance of FUNCTION_TABLE defined for authID and let Strobe SQL analysis create a new instance during a subsequent Profile request, or ALTER the FUNCTION_TABLE so that it includes the complete set of columns that you can define for FUNCTION_TABLE.

Refer to the IBM manuals IBM DATABASE 2 SQL Reference and IBM DATABASE 2 Administration Guide, Volume III for additional information regarding the definition of FUNCTION_TABLE.
STR9570W NO FUNCTION_TABLE ROWS FOR STATEMENT mfstmtnumber (srcstmtnumber) IN objecttype objectname OF PLAN planname Explanation: An attempt by Strobe SQL analysis to locate existing FUNCTION_TABLE rows for statement mfstmtnumber (srcstmtnumber) in objecttype objectname of plan planname failed.

objecttype identifies objectname as either a package or a DBRM. mfstmtnumber is the SQL statement number assigned by Strobe. srcstmtnumber is the SQL statement number assigned by the DB2 precompiler that EXPLAIN inserts into the QUERYNO column of table PLAN_TABLE. EXPLAIN(YES) was not specified when objectname was bound into plan planname. The resolved authorization ID does not qualify the correct instance of FUNCTION_TABLE.
System Action: The user-defined function section of the Translation report will not appear.

User Response: Rebind the plan with the correct authorization ID and EXPLAIN(YES) if the user_defined function section of the Translation report is desired. STR9571I NO EXISTING FUNCTION_TABLE FOUND FOR AUTHORIZATION ID authID

Explanation: An attempt by Strobe SQL Analysis to locate an instance of FUNCTION_TABLE for authorization ID authID when using existing PLAN_TABLE rows failed. System Action: The user-defined function section of the Translation report will not appear.

User Response: Verify the value of the AUTHORIZATION ID on the Strobe - SQL Analysis Feature Report Settings panel. Notify Compuware Customer Support if you are unable to resolve the problem. STR9580E BUFFER OVERFLOW OCCURRED WHILE FORMATTING SQL STATEMENT

Explanation: Strobe SQL analysis encountered an internal error when attempting to prepare an SQL statement for processing. System Action: User Response: STR9599I Processing for the current profile/statement stops. Notify Compuware Customer Support of the problem

release_number Strobe SQL analysis version release_number has been validated by Strobe. Processing continues. None required.

Explanation: System Action: User Response:

4-1

Chapter 4. Abend Codes Returned by Strobe

Chap 4

Measuring with Strobe does not affect the execution of the target program. Strobe causes a measured step to terminate abnormally only when the user program itself has terminated abnormally. When a measurement task module abnormally terminates, Strobe writes abnormal termination information to the sample data set. The session management facility writes abnormal termination data to the Strobe log and to its SYSPRINT data set.

Strobe Programmed Terminations


Under certain circumstances, the measurement task can terminate with a programmed abnormal termination. User programs are not affected. When you receive any of the abnormal termination (ABEND) codes listed below, note the ABEND code number and inform the Strobe system programmer of the problem. ABEND Code 0000 0001 0002-4 0002-8 0002-12 0002-16 0003 0100 0101 0103 0322 0522 Reason for the measurement task ABEND Strobe issued an ABEND during measurement initialization Strobe issued an ABEND request to the measurement task The measurement task detected an internal error in the ADB chain. The reason code identifies the specific location. The measurement task detected an internal error in the ADB chain. The reason code identifies the specific location. The measurement task detected an internal error in the ADB chain. The reason code identifies the specific location. The measurement task detected an internal error in the ADB chain. The reason code identifies the specific location. The measurement task detected an internal error in the ADB chain. The release level of the session management facility is earlier than the release level of the measurement task The release level of the measurement task and the release level of the session management facility are incompatible The user attempted to invoke the measurement facility through STRBVPH1 The measurement task used an excessive amount of time there may be a loop in the program The measurement task used an excessive amount of elapsed time there may be a hang in the program

The session management facility also issues ABEND codes. Conditions that can cause these abnormal terminations include: A program that was not part of the Strobe system attempted to use the session management facility.

4-2

Strobe Messages Guide

The program being measured damages the measurement task or its working storage (both located in the target programs address space). The operating system malfunctions. The session management facility uses ABEND codes for all programmed ABENDs and shows the ABEND code with the termination message. These codes take the form 6xx. The reason code is represented as the hexadecimal equivalent of the value. ABEND and Reason Code 610-0 610-1 610-2 610-4 610-5 610-6 610-7 610-8 610-9 610-F 610-10 610-11 610-12 610-14 610-18 611-0 611-1 620-1 620-2 620-3 620-4 620-5 620-6 630-0 650-0 650-1 650-2 Reason for the Session Management Facility ABEND An ENV test command was issued ISPF and session requester releases are incompatible Call to session requester is invalid BLDL failed for the module Strobe could not locate the module Strobe detected an internal error while processing a parameter list Strobe detected an internal error while processing a request Strobe detected an internal error while processing an ENV REMOVE request Open failed for the SYSQUEUE data set Strobe experienced a failure issuing the SVCUPDTE service or ENQ service Strobe detected an internal error while searching an SVC table Strobe detected an internal error in parser; the reason code identifies the specific location of the error Strobe detected an internal error in parser; the reason code identifies the specific location of the error Strobe detected an internal error in parser; the reason code identifies the specific location of the error System service QEDIT failed during started task initialization Session requester terminated because the operator pressed the ATTN key Session requester terminated as part of session manager ABEND processing Versions of STRBCPH0 and STRBCLPA are incompatible Attach of users program failed System service BLDL failed Strobe detected an internal error; the reason code gives the specific location of the error Strobe detected a serialization error during measurement task initialization Strobe attempted to attach the session requester as a subtask and this attach failed Versions of STRBCLPA and STRBCRB are incompatible An invalid entry code passed to the Strobe SVC, or the Strobe SVC was called by an unauthorized user Invalid SRE address passed to the Strobe SVC Invalid parameter passed to the Strobe SVC message function

Abend Codes Returned by Strobe

4-3

ABEND and Reason Code 650-3 650-4 650-5

Reason for the Session Management Facility ABEND Cross-memory post failed during a SEND command while the session manager was trying to post the measurement task Cross-memory post failed during POST processing while trying to post the session manager or the session requester Cross-memory post failed during end-of-task exit processing while the session manager or the session requester was trying to post STRBCSM or STRBCSR SVC ABEND; Strobe detected an internal error in DELETE function SVC ABEND; Strobe detected an internal error in SEND function SVC ABEND; Strobe detected an internal error in SEND function SVC ABEND; Strobe detected an internal error in SEND function SVC ABEND; Strobe detected an internal error in SEND function STRBCXAC error calling exit Internal error building MSCB Strobe detected an invalid OUCB Invalid parameter passed to Strobe SVC sign-on function Invalid parameter passed to Strobe SVC sign-on function Strobe detected an internal error in SWAREQ processing SRB ABEND; cross-memory post failed IRB ABEND; cross-memory post failed Sysevent transwrap failed Cross-memory post of session manager failed Attach of AutoStrobe subtask failed Timer failure AutoStrobe work area unavailable Cross-memory post of Measurement Services Address Space (MSAS) failed

650-6 650-7 650-8 650-9 650-A 650-B 650-C 650-D 650-E 650-F 650-10 660-0 670-0 700-8 700-12 700-22 701-1 701-3 777-2

Table 4-1 lists Strobe SSAREQ return codes, reason codes, and meaning/action for each.
Table 4-1. SSAREQ Return Codes and Reason Codes Reason Codes X'00' X'04' X'ff' X'08' X'04' 04 X'08' 08 X'0C' 12 X'10' 16 X'14' 20 X'18' 24 X'0C' Meaning/Action Rc00 Normal Rc04 Warning wRsn model Rc08 Error eRsn Function code invalid/unsupp. eRsn No Ift slots avail. eRsn No match on IftAs eRsn Subtask Attach failed eRsn #IfiCCmd invalid eRsn SALSAWT invalid Rc12 Logic error

Return Codes IfiRcOk EQU IfiRcWrn EQU IfiRwxxx EQU IfiRcErr EQU IfiReFnc EQU IfiReIns EQU IfiReInf EQU IfiReInA EQU IfiReCmd EQU IfiReSal EQU IfiRcLog EQU

4-4

Strobe Messages Guide

Table 4-1.

SSAREQ Return Codes and Reason Codes Reason Codes X'04' 04 X'08' 08 X'ff' X'10' X'04' 04 X'08' 08 X'0C' 12 X'10' 16 X'14' 20 X'18' 24 X'1C' 28 X'20' 32 X'24' 36 X'28' 40 X'2C' 44 X'30' 48 X'34' 52 X'38' 56 X'40' 64 X'44' 68 X'48' 72 X'4C' 76 X'50' 80 X'54' 84 X'58' 88 X'5C' 92 X'60' 96 X'64' 100 X'68' 104 X'F00' Meaning/Action nRsn FIFA/M Internal ShowNotOccur nRsn FIFA 1st call must be #IfiCtIi lRsn model Rc16 Environment nRsn INPUT PARM AREA NOT ACCESABLE nRsn STORAGE OBTAIN FAILED TOKEN AREA nRsn STORAGE OBTAIN FAILED LCL BFR nRsn SSA NO DB2 Act (SALSIB=0) nRsn SSA NO DB2 Act (SIBDACC=0) nRsn LOAD fail DB2 RRSAF/CAF Intf nRsn LOAD fail DB2 WLIR/WLI2 Intf nRsn DB2 CAF CONNECT FAILURE nRsn DB2 CAF OPEN FAILURE nRsn UNABLE TO UPDATE SSA SIB nRsn INTERNAL IFI BUFFER NOT PRESENT nRsn INVALID DAB CONTROL BLOCK nRsn IFI READS FAILURE nRsn IftU zero nRsn RRSAF Identify err nRsn RRSAF Signon Err nRsn WLI Dis Trace err nRsn WLI Sta Trace err nRsn FIF* SubT unexpected term nRsn FIF0 Enq failed nRsn FIF0 Deq failed nRsn FIF0 Stor Obt DsEndDs failed nRsn FIF0 Stor Rel DsEndDs failed nRsn FIF0 Stor Rel #IFI failed nRsn FIFA SAW failed validity ck nRsn HotReason-testing e.g. dcb open

Return Codes IfiRlSno EQU IfiRlRat EQU IfiRlxxx EQU IfiRcEnv EQU IfiRnIpr EQU IfiRnStg EQU IfiRn0C EQU IfiRn10 EQU IfiRn14 EQU IfiRnDWL EQU IfiRnDW2 EQU IfiRn20 EQU IfiRn24 EQU IfiRn28 EQU IfiRn2C EQU IfiRn30 EQU IfiRnIrf EQU IfiRnNiu EQU IfiRnRid EQU IfiRnRsn EQU IfiRnWdt EQU IfiRnWst EQU IfiRnAbn EQU IfiRnEnq EQU IfiRnDeq EQU IfiRnSoq EQU IfiRnSrq EQU IfiRnSri EQU IfiRnSaw EQU IfiRnHot EQU

Function Codes Returned by Strobe Session Manager


When function codes appear in error messages, they provide additional information about the state of Strobe Session Manager when the error occurred. This diagnostic information can be helpful in troubleshooting errors that Strobe may encounter. Function Code returned by Strobe Session Manager 10 Definition of the Function Code

Terminates a request

Abend Codes Returned by Strobe

4-5

Function Code returned by Strobe Session Manager 12 14 15 16 17 18 20 21 22 23 32 33 34 35 36 37 38 39 48 49 50 51 52 53 54 55 64 65 66 67 68 69 70 72 73 80 81 82 83 84

Definition of the Function Code

Checks Queue space Obtains a request number Shows XCF Group members Calls task mode receiver Collects XCF Group parameters Strobe Request Element update facility Deletes dummy Queue record Calls the Group Configuration Manager Activates the Attach Filter Request RESYNC Command ADD QUEUED (phase 1) ADD QUEUED (phase 2) CHANGE QUEUED (phase 3) CHANGE QUEUED (phase 2) DISPLAY (phase 1) DISPLAY (phase 2) ADD QUEUED (phase 3) Reads module tracking record (MTTR) ADD ACTIVE (phase 1) ADD ACTIVE (phase 2) ADD ACTIVE (phase 3) SEND (phase 1) SEND (phase 2) SEND (phase 3) CHANGE ACTIVE (phase 1) Initiates Queued Request Element Build/Write/Broadcast Error in processing message from member Message in response to internal Strobe command Error processing internal Strobe command Internal Delete (phase 1) Internal Delete (phase 2) Strobe Request Element Update Facility (phase 1) Strobe Request Element Update Facility (phase 2) CHANGE ACTIVE (phase 2) CHANGE ACTIVE (phase 3) DELETE (phase 2) DELETE (phase 3) DELETE (phase 4) Initializes Timer Queue Strobe Expiration Check

4-6

Strobe Messages Guide

Function Code returned by Strobe Session Manager 86 87 88 89 96 97 98 99 100 113 114 115 116 117 118 119 120 121 128 129 130 131 132 144 145

Definition of the Function Code

Reads Messages Service Task-Mode Receiver (phase 2) Synchronous return to Session Requester (ADD QUEUED) Synchronous return to Session Requester (CHANGE QUEUED) ADD GROUP CHANGE GROUP LIST GROUP DELETE GROUP SUBMIT GROUP AutoStrobe Scheduling Internal ADD ACTIVE (phase 1) Internal ADD ACTIVE (phase 2) Internal ADD ACTIVE (phase 3) Internal SEND (phase 1) Internal SEND (phase 2) Internal SEND (phase 3) AutoStrobe Concurrent ADD (phase 1) AutoStrobe Concurrent ADD (phase 2) Session Manager internal NOP function AutoStrobe Scheduling Marks Strobe Request Element complete (phase 1) Marks Strobe Request Element complete (phase 2) AutoStrobe Concurrent ADD (phase 3) Creates Auto Profile (phase 1) Creates Auto Profile (phase 2)

ABEND Codes Returned by the Strobe SQL Agent


This section describes ABEND codes returned by the Strobe SQL agent when it encounters an unrecoverable error. The system ABENDs the Strobe SQL Agent. Reason codes for all errors are saved in register 15. For all errors, respond to any messages issued to the console or the job log and for any accompanying system ABENDs. See the descriptions of the Strobe SQL Agent ABEND codes for suggestions. If the problem persists, contact Compuware Customer Support and provide the following documentation: All printed output and output data sets related to the problem The JCL for the job. The Logrec data set error record

Abend Codes Returned by Strobe

4-7

A copy of the system dump data set if available. ABEND Code U0300 Issuing module STRBAGNT (the Strobe SQL Agent) Reason Code and Explanation 00080004 Job step was not APF-authorized. 00080008 An internal error was detected. 0008000C Possible attempt to start Strobe SQL Agent from the system console. 00080010 Unable to load STRBSFR0. 00080014 Unable to load STRB2RMI. 00080018 Unable to load STRBGBES. 0008001C Unable to load STRB2RM0. 00080020 Unable to load STRBFTBL. 00080024 Unable to load STRBFxxx. 00080028 Unable to load STRBSRMD. 0008002C An internal error was detected. 00080030 An internal error was detected. 00080038 Unable to load STRBSRM0. 0008003C Unable to load STRB2RMD. 00080040 Unable to load STRBARM0. 000Cxxxx An internal error was detected. System Action Programmer response Ensure that the Strobe SQL Agent is running from an APF-authorized load library. Contact Compuware Customer Support. Do not attempt to start the Strobe SQL Agent from the system console; it may only be started by STOBE session manager. Ensure that all necessary Strobe modules are present in the load library. Ensure that all necessary Strobe modules are present in the load library. Ensure that all necessary Strobe modules are present in the load library. Ensure that all necessary Strobe modules are present in the load library. Ensure that all necessary Strobe modules are present in the load library. Ensure that all necessary Strobe modules are present in the load library. Ensure that all necessary Strobe modules are present in the load library. Contact Compuware Customer Support. Contact Compuware Customer Support. Ensure that all necessary Strobe modules are present in the load library. Ensure that all necessary Strobe modules are present in the load library. Ensure that all necessary Strobe modules are present in the load library. Contact Compuware Customer Support.

4-8

Strobe Messages Guide

ABEND Code

Issuing module

Reason Code and Explanation 00100004 Unable to allocate work area. 0010004C Strobe SQL Agent unable to communicate with Strobe Session Manager. 00100008 00100078 An internal error was detected.

System Action

Programmer response Retry the request.

Recycle Strobe to ensure the Strobe Session Manager initialization has already occurred when the Strobe SQL Agent is starting. Contact Compuware Customer Support.

U0301

STRBSFR0

000C0004 Unsupported function code. 000C0004 An internal error was detected. 00100004 An internal error was detected. 000C0004 An internal error was detected. 000C0004 An internal error was detected. 000C0004 Storage obtain for working storage failed.

The system Ensure that all Strobe ABENDs the caller. modules have been installed at the same maintenance level. Operation continues. Contact Compuware Customer Support.

U0302

STRBARM0

U0303

SSASQLI0

The system Contact Compuware ABENDs the caller. Customer Support. The system Contact Compuware ABENDs the caller. Customer Support. The system Contact Compuware ABENDs the caller. Customer Support. The SQL Collector subtask is terminated. Check to see if the SQL Agent Procedure has REGION=0M. If not, change it, restart Strobe, and try again. If it does, contact Compuware Customer Support. Contact Compuware Customer Support.

U0304

STRB2RMI

U0305

STRBSRM0

U0400

STRBFIFR

000C0008 Unable to get Strobe control blocks. 000C000C Load of IFI parms module STRBFIFP failed.

The SQL Collector subtask is terminated. The SQL Collector subtask is terminated.

Contact Compuware Customer Support.

Abend Codes Returned by Strobe

4-9

ABEND Code

Issuing module

Reason Code and Explanation 000C0010 Insufficient DB2 Authorization.

System Action The SQL Collector subtask is terminated.

Programmer response Check to see if the authorizations grants in STRBSAMP member STRBGRNT were given to the SQL Agent. If not, grant them, restart Strobe, and try again. If they have been granted, contact Compuware Customer Support. Check to see if the SQL Agent Procedure has REGION=0M. If not, change it, restart Strobe, and try again. If it does, contact Compuware Customer Support.

000C0014 The SQL Collector Getmain for buffer subtask is prefixes storage terminated. failed.

000C0018 Strobe DB2 SQL IFI Check to see if the SQL Getmain for buffer trace collection is Agent Procedure has storage failed. terminated. REGION=0M. If not, change it, restart Strobe, and try again. If it does, contact Compuware Customer Support. 000C001C IFI initialization failed. Strobe DB2 SQL IFI Check the SQL Agent trace collection is Procedure log for any DB2 terminated. messages. If no DB2 messages are present, contact Compuware Customer Support. Strobe DB2 SQL IFI Check the SQL Agent trace collection is Procedure log for any DB2 terminated. messages. If no DB2 messages are present, contact Compuware Customer Support. Strobe DB2 SQL IFI Contact Compuware trace collection is Customer Support. terminated. Strobe DB2 SQL IFI Check the SQL Agent trace collection is Procedure log for any DB2 terminated. messages. If no DB2 messages are present, contact Compuware Customer Support. Strobe DB2 SQL IFI Contact Compuware trace collection is Customer Support. terminated. Strobe DB2 SQL IFI Contact Compuware trace collection is Customer Support. terminated.

000C0020 Unable to obtain trace user class.

000C0024 Unable to format DB2 Start Trace command. 000C0028 DB2 Async IFI command failed.

000C0030 Internal SETTMR routine failed. 000C0034 Internal STIMERM cancel failed.

4-10

Strobe Messages Guide

ABEND Code

Issuing module

Reason Code and Explanation 000C0038 Internal timer pop service routine failed. 000C003C Internal DB2 TERM service routine failed. 000C0040 Internal Control events service routine failed. 000C0044 IFI buffers exhausted. 000C0048 Internal SETTMR service routine failed.

System Action

Programmer response

Strobe DB2 SQL IFI Contact Compuware trace collection is Customer Support. terminated. Strobe DB2 SQL IFI Contact Compuware trace collection is Customer Support. terminated. Strobe DB2 SQL IFI Contact Compuware trace collection is Customer Support. terminated. Strobe DB2 SQL IFI Contact Compuware trace collection is Customer Support. terminated. Strobe DB2 SQL IFI Contact Compuware trace collection is Customer Support. terminated.

000C0054 Strobe DB2 SQL IFI Contact Compuware trace collection is Customer Support. Internal PTBUIP terminated. routine unable to obtain buffer lock. 000C0058 Strobe DB2 SQL IFI Contact Compuware Internal GTBUIP trace collection is Customer Support. routine unable to terminated. obtain buffer lock. U0400 STRBFSS0 00100004 Unable to allocate work area. 00100008 An internal error was detected. 0010000C An internal error was detected. U0401 STRBFUS0 000C0004 An internal error was detected. 00100004 Unable to allocate work area. U0500 STRBFIFM Any RC The system Retry the request. ABENDs the caller. An internal error was detected. An internal error was detected. Retry the request.

Contact Compuware Customer Support.

The system Contact Compuware ABENDs the caller. Customer Support. The system Retry the request. ABENDs the caller. DB2 trace terminates Contact Compuware Customer Support.