Messages Returned by the Measurement Task
The measurement task returns the following messages.
STR0106I DIE MODULE xxxxxxxx LOADED AT yyyyyyyy
Explanation: Strobe has successfully loaded the named Disabled Interrupt Exit module at the address shown, in page fixed common storage. This module is required to perform measurement requests.
System Action: Subsequent measurement requests will be initiated.
User Response: None required. This message is informational only.
STR0107I DIE MODULE xxxxxxxx NOT FOUND, WAS NOT DELETED
Explanation: An attempt was made to delete the named Strobe Disabled Interrupt Exit module either by Measurement Services Address Space termination or by the REMVVDIE or REPLVDIE MODIFY command entered from the System console, but the named module was not found to be loaded.
System Action: Processing continues.
User Response: Check the Strobe log for an STR0106I message with a matching module name as shown here and if found, attempt to locate the module at the address listed in STR0106I and then contact Compuware Customer Solutions for assistance. Otherwise, the DIE module was never successfully loaded; thus no DELETE is required.
STR0110E DIE MODULE xxxxxxxx NOT FOUND - REQUIRED FOR MEASUREMENTS
Explanation: An attempt to load the named Strobe Disabled Interrupt Exit module failed, either at Measurement Services initialization or from an executed LOADVDIE or REPLVDIE MODIFY command. Ensure that the named DIE module is available in the STEPLIB of the Measurement Services Address Space or in the LNKLST concatenation.
System Action: Until the named Strobe DIE module is made available and LOADVDIE MODIFY command is executed or the MSAS restarted, measurement requests will be accepted but stay in a SUSPENDED state.
User Response: Notify the Strobe system programmer. There has probably been an installation error. Locate the missing DIE module and add it to a LNKLST dataset, and then execute an LLA REFRESH followed by the LOADVDIE MODIFY command. Any SUSPENDED measurement requests resulting from the missing DIE module need to be terminated and resubmitted.
STR0113E ERROR DELETING DIE MODULE xxxxxxxx, MODULE REMAINS in ECSA at yyyyyyyy
Explanation: Explanation: An attempt was made to delete the named Strobe Disabled Interrupt Exit module by the REMVVDIE or REPLVDIE MODIFY command entered from the System console, but the DELETE of the named module failed.
System Action: Processing continues with the named DIE module Remaining in page fixed common storage, until the MSAS is terminated.
User Response: Check the Strobe log for an STR0106I message with a matching module name as shown here. If found, attempt to locate the module at the address listed in STR0106I and contact Compuware Customer Solutions for assistance.
STR0115E SAMPLING MODULE modname NOT FOUND - MEASUREMENT SESSION TERMINATED.
Explanation: Strobe did not find the sampling routine named modname.
System Action: The measurement task terminates.
User Response: Notify the Strobe system programmer. There has probably been an installation error.
STR0117E I/O ERROR LOCATING SAMPLING ROUTINES - MEASUREMENT SESSION TERMINATED
Explanation: Strobe encountered an I/O error while issuing a BLDL for the sampling routines.
System Action: The measurement task terminates.
User Response: Notify the Strobe system programmer.
STR0118W I/O ERROR SEARCHING DCC LIBRARY - DCCLIB OPERAND IGNORED
Explanation: Strobe encountered an I/O error while issuing a BLDL for a data collector.
System Action: Strobe attempts to load the data collectors from either a linklist dataset or the library specified by STRMTLIB.
User Response: Save the JES log of the measured job and notify the Strobe system programmer.
STR0119W 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 linklist 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/ISPF add active or 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
Explanation: An internal error has occurred.
System Action: Strobe continues measuring, but measurement data may be invalid or incomplete.
User Response: Contact Compuware Customer Support.
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/ISPF data collectors panel.
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/ISPF add active request or 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
Explanation: Virtual storage is not available for the critical control block block.
System Action: The measurement task terminates.
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
Explanation: Strobe detected an invalid header in PCMG module modname.
System Action: The measurement task terminates.
User Response: Contact Compuware Customer Support.
STR0126E PCMG csectname CSECT NOT FOUND
Explanation: Strobe did not find CSECT csectname.
System Action: Strobe continues sampling but may issue additional error messages.
User Response: Contact Compuware Customer Support.
STR0127E PCMG cdename CDE NOT FOUND
Explanation: Strobe did not find CDE cdename.
System Action: Strobe continues sampling but may issue additional error messages.
User Response: Contact Compuware Customer Support.
STR0128E PCMG entryname ENTRY NOT FOUND
Explanation: Strobe did not find the entry point entryname.
System Action: Strobe continues sampling but may issue additional error messages.
User Response: Contact Compuware Customer Support.
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: Strobe does not accept the measurement request.
User Response: 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.
STR0136I Strobe RESMGRs set for ASID=xxxx JOBNAME=aaaaaaaa STEP=bbbbbbbbcccccccc
Explanation: During measurement initialization there are two RESMGR routines set to release resources, at the TASK level and at the ADDRSPC level. This message indicates that both were successfully set for the ASID, JOBNAME, and STEP name(s) shown.
System Action: Processing continues.
User Response: Informational message, no action required.
STR0137I Strobe task RESMGR entered for ASID=xxxx JOBNAME=aaaaaaaa STEP=bbbbbbbbcccccccc
Explanation: During measurement termination the RESMGR routine set to release resources has gained control from RTM. A key function is to DELETE the RESMGR routine at the ADDRSPC level. This message shows the ASID, JOBNAME, and STEP name(s) for which it was entered.
System Action: Processing continues.
User Response: Informational message, look for a subsequent STR0146I message showing the return code from the DELETE. Refer to message STR0146 for the appropriate Response.
STR0138I Strobe RESMGR entered ASID=xxxx JOBNAME=aaaaaaaa ASCBINTS=yyyyyyyyyyyyyyyy
Explanation: The measurement resource manager was entered at MEMTERM to release global resources at address space termination. The values presented here are from the ASCB address passed by the system to the Strobe ADDRSPC resource manager.
System Action: Processing continues.
User Response: Informational message, unless an abend follows then contact Compuware Customer Support and provide the sample dataset, Strobe log, the daily SYSLOG for the relevant SYSID, and any associated dump.
STR0139I Strobe RESMGR MSCB request=#### JOBNAME=aaaaaaaa MSCBINTS=yyyyyyyyyyyyyyyy
Explanation: The measurement resource manager was entered at MEMTERM to release global resources at address space termination. The values presented here are from the MSCB passed at measurement initialization to the Strobe ADDRSPC resource manager.
System Action: Processing continues.
User Response: Informational message, unless an abend follows then contact Compuware Customer Support and provide the sample dataset, Strobe log, the daily SYSLOG for the relevant SYSID, and any associated dump.
STR0140I MQSERIES COUNTS DISABLED FOR MEASUREMENT
Explanation: Strobe support for MQSeries Counts is not enabled.
System Action: Strobe continues sampling but will not collect MQSeries counts.
User Response: For information about enabling Strobe support for MQSeries counts, contact Compuware Customer Support.
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: None.
User Response: Contact Compuware Customer Support and provide the sample dataset and Strobe log.
STR0146I STR0146E RESMGR ADDRSPC DELETE rc ##
Explanation: The measurement resource manager was entered to free up measurement resources at task termination. The attempt to delete the ADDRSPC resource manager did not complete with a zero return code, rather that shown in the message.
System Action: Processing continues.
User Response: This message should be an error only if the return code is greater than 8, then contact Compuware CustomerSupport and provide the sample dataset, Strobe log, and daily SYSLOG for the relevant SYSID.
STR0188W 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 Strobe 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: Notify the Strobe or Abend-AID system programmer.
STR0189I 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: AutoStrobe monitoring or Strobe measurement-termination processing continues.
User Response: 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: Notify the Strobe system programmer.
STR0191I csectname CRITERIA MATCHED
Explanation: Informational message identifying a Strobe csectname that has reached a specific service criteria.
System Action: Measurement session continues.
User Response: 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.
User Response: Notify the Strobe system programmer. An installation error may have occurred.
STR0200I Strobe MEASUREMENT ENDED
Explanation: The measurement session terminated normally. The sample dataset is ready for reporting.
System Action: Strobe completes processing.
User Response: None required.
STR0207E GETMAIN FAILURE - MEASUREMENT SESSION TERMINATED
Explanation: A measurement task module cannot obtain sufficient storage for its work area.
System Action: The measurement task terminates.
User Response: Increase the region size and resubmit the request.
STR0208E MEASUREMENT TASK UNABLE TO ISSUE ESTAE - MEASUREMENT SESSION TERMINATED
Explanation: The measurement task is unable to establish its ABEND protection.
System Action: The measurement task terminates.
User Response: 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 LinkList Set. The SETPROG LNKLST,UPDATE,JOB=jobname command was issued.
System Action: Strobe continues processing but the module mapping or attribution may be inaccurate.
User Response: Resubmit the measurement request. Ensure that the SETPROG LNKLST,UPDATE,JOB=jobname command is not issued while the measurement is active.
STR0210W Strobe MEASUREMENT LOOP TIMER HAS BEEN RESET - CPU
TIME FOR MEASUREMENT IS INVALID
Explanation: While measuring, Strobe detected that its main task timer had been canceled. The task timer was reset by something other than Strobe sampling control logic.
System Action: Strobe sets its timer to a known state and continues processing. However, the CPU time used by Strobe is no longer accurate. This inaccuracy will be reflected in the CPU times for the user tasks being measured as well as CPU time used by the Strobe measurement task.
User Response: None required. Strobe handles the condition and continues with the measurement. However, for more accurate results, the measurement should be repeated.
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: None required.
STR0215W One or more RMODE64 programs found, attribution will be incomplete.
Explanation: The application contains one or more programs executing above the bar (RMODE64). Strobe does not support RMODE64 programs.
System Action: Strobe continues measuring, but attribution will be incomplete.
User Response: None required.
STR0222I Topaz Java Agent acknowledged - sample # xxxxxxxx
Explanation: Strobe found the Topaz Java agent while measuring the application at sample number xxxxxxxx.
System Action: Strobe continues measuring.
User Response: None required.
STR0223I Topaz Java Agent interface complete RC xxxxxxxx
Explanation: Strobe started communications with the Topaz for Java agent. RC xxxxxxxx represents the return code from initialization.
System Action: Strobe continues measuring.
User Response: None required.
STR0224I Topaz Java Agent interface stopped.
Explanation: Strobe issued a request to the Topaz for Java Agent to stop processing.
System Action: Strobe continues with measurement completion.
User Response: None required.
STR0225I Topaz Java Agent interface already stopped rc xxxxxxxx
Explanation: The Topaz Java Agent had already completed when Strobe was completing the measurement. This is an indication that the Java application terminated.
System Action: Strobe continues with measurement completion.
User Response: None required.
STR0226W Strobe encountered the following error: xxxxxxxxxxxxxxxxxxx
Explanation: An error occurred while trying to process LE options. xxxxxxxxxxxxxxxxxxxx displays specific information about what caused the error.
System Action: Strobe continues processing, but may be unable to provide LE options analysis.
User Response: Notify the Strobe system programmer.
STR0295E 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 DATASET 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: The measurement task completes processing.
User Response: None required.
STR0301E sdsname SAMPLE DATASET 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.
User Response: Modify the REGION parameter in the JCL, and resubmit the request.
STR0302E sdsname SAMPLE DATASET OPEN FAILED FOR UPDATE
Explanation: Strobe cannot open the sample dataset sdsname for update. sdsname is the low-order qualifier for the dataset name.
System Action: Strobe continues execution of the target program. The Measurement Session Data report will be incomplete.
User Response: Notify the Strobe system programmer.
STR0303W GETMAIN FAILURE FOR CSECT TABLE - SOME ATTRIBUTION INFORMATION MAY BE LOST
Explanation: A measurement task module cannot obtain additional storage.
System Action: Strobe continues sampling, but some control section mapping detail may be lost.
User Response: Increase the region size and resubmit the request.
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 linklist 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: None required.
STR0306W 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 MODULE modname MAPPED SIZE UNEQUAL TO IDENTIFIED SIZE, CSECT DATA DISCARDED
Explanation: The version of module modname referenced for mapping was different from the version executing in the job.
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
Explanation: You specified more than 16 load libraries on the STRBLIB operand.
System Action: Strobe uses only the first 16 load libraries specified.
User Response: None required.
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
Explanation: A load module has the scatter attribute.
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.
STR0311W 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: The measurement task completes processing, although some module data may be lost.
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.
System Action: Strobe continues sampling, but module mapping data may be missing for some modules.
User Response: Modify security subsystem rules to authorize read access to the library.
STR0314W DATASPACE ALLOCATION FAILURE-- LONGNAMES WILL NOT BE REPORTED
Explanation: An error occurred during the allocation of the long names dataspace.
System Action: Strobe continues measuring without measuring modules with names exceeding eight characters.
User Response: Notify the Strobe system programmer.
STR0316E CREATE failure for MAPS D-SPACE - measurement session terminated rc xx
Explanation: An error occurred during the allocation of the Maps dataspace. xx is the return code from dataspace create.
System Action: Strobe terminates without mapping.
User Response: Notify the Strobe system programmer.
STR0317E Mapping error - Func: xx RC: yy
Explanation: An error occurred in Mapping function xx with return code yy.
System Action: Strobe continues without mapping.
User Response: Notify the Strobe system programmer.
STR0318E PDSE mapping support disabled due to differences in REGION sizes: LDAELIM=x00000000 LDAEVVRG=x11111111
Explanation: In order to safely invoke IEWBIND to map a PDSE object, Strobe performs some checks on the Extended User Region limits to avoid S0F4 abends that can lead to S878 or S04D abends and a region crash.
System Action: Strobe continues sampling, but program object modules from a PDSE will not be mapped.
User Response: Notify the MVS system programmer. Refer to IBM's z/OS MVS Installation Exits manual for information on the IEFUSI exit.
STR0319E Check your IEFUSI exit to resolve differences in REGION limits; REGSIZA and REGLIMA
Explanation: In order to safely invoke IEWBIND to map a PDSE object, Strobe performs some checks on the Extended User Region limits to avoid S0F4 abends that can lead to S878 or S04D abends and a region crash.
System Action: Strobe continues sampling, but program object modules from a PDSE will not be mapped.
User Response: Notify the MVS system programmer. Refer to IBM's z/OS MVS Installation Exits manual for information on the IEFUSI exit.
STR0320E 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: Notify the Strobe system programmer.
STR0321W Longname dataspace flush failed - DASP(xx), RC(xx), RSN(xx)
Explanation: An error occurred during end-of-measurement processing of the long names dataspace.
System Action: Strobe continues end-of-measurement processing; however, names exceeding eight characters may not be reported correctly.
User Response: Notify the Strobe system programmer.
STR0322I Using member xxxxxxxx for IMS preload report
Explanation: Informational message identifying the PROCLIB member used in providing the IMS preload report.
System Action: Measurement session continues.
User Response: None required. This message is informational only.
STR0330E message
Explanation: The CA-Panexec interface had difficulty processing a Strobe request. The message displayed is returned by the CA-Panexec interface program.
System Action: Strobe continues sampling, but module mapping data may be missing for some modules.
User Response: Notify the Strobe system programmer.
STR0331I PID found nnnnnnnn sample xxxxxxxx
Explanation: Strobe identified that it is running in an OMVS address space and has collected the PID (Process ID) nnnnnnnn on sample number xxxxxxxx.
System Action: Strobe continues.
User Response: No response necessary. Message is for diagnostics only.
STR0332I dynaTrace agent found aaaaaaaaaaaaaaaaa
Explanation: Strobe identified that dynaTrace agent aaa...aaa is active in the address space.
System Action: Strobe continues by connecting to dynaTrace and starting a session.
User Response: No response necessary. Message is for diagnostics only.
STR0340W 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: Strobe continues sampling, but module mapping data may be missing for some modules.
User Response: Notify the Strobe system programmer.
STR0341W PANXACCS INTERFACE ERROR-- SAVE LOG AND SAMPLE FILE-- CONTACT CUSTOMER SUPPORT
Explanation: Strobe encountered an error in the Strobe CA-Panexec interface.
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
Explanation: Strobe displays text, the Binder API error message.
System Action: Strobe continues sampling, but module mapping may be incomplete.
User Response: Refer to IBM’s MVS System Messages manual for information on the message issued by the binder.
STR0343C FROM BINDER API: FUNCTION=fnct RC=rc RSN=rsnc lmod
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. the load module, lmod, is listed after the rsnc if available.
System Action: Strobe continues sampling, but module mapping may be incomplete.
User Response: Notify the Strobe system programmer. Refer to IBM’s DFSMS/MVS Program Management manual for the binder API return codes and reason codes.
For return code (C) reason code (1080002F), the acquisition of working storage was not successful. The request was rejected.
Increase your REGION size to REGION=0M for your job.
STR0344C ACTIVE DEVICE TABLE CORRUPTED
Explanation: Strobe detected an error in the Active Device Table.
System Action: Strobe will not report DASD model type, VTOC location, and cache status.
User Response: Save a copy of the sample dataset and the Strobe log, and then contact Compuware Customer Support.
STR0345W GETMAIN FAILED FOR THE CACHE I/O AREA - CACHE STATUS WILL NOT BE REPORTED
Explanation: Strobe cannot obtain enough virtual storage in ESQA (subpool 245).
System Action: Strobe continues sampling, but will not report cache status on the Data Set Characteristics Supplement.
User Response: Notify the Strobe system programmer.
STR0346W 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
Explanation: The FREEMAIN failed for a segment of the Active UCB table, beginning at address addr.
System Action: The measurement task terminates.
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: Strobe will not report DASD model type, VTOC location, or cache status for device nnnn.
User Response: Save a copy of the sample dataset and Strobe log. Notify the Strobe system programmer.
STR0349W 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
Explanation: A critical measurement task failed to obtain sufficient storage for its initialization.
System Action: The measurement task terminates.
User Response: Increase the region size and resubmit the request.
STR0351E RECURSIVE ENTRY TO STRVPH3 INIT
Explanation: A fatal control error occurred in a measurement task module.
System Action: The measurement task terminates.
User Response: Notify the Strobe system programmer.
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.
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: Strobe continues processing, but all thresholds are disabled.
User Response: Reduce sampling time and resubmit the request.
STR0358I MODULE CALLABLE SERVICE xxxxxxxx FAILED, RC=rc, RSNC=rsnc
Explanation: The UNIX System Services Callable Service xxxxxxxx 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 DataSet Characteristics and DataSet 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 HFS 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: HFS and z/FS I/O counts are not reported on the Data Set Characteristics report.
User Response: To report I/O counts for HFS or z/FS files, modify a user-exit module in the Strobe control dataset. See the Advanced-Configuration-Guide for an example of a user-exit module.
STR0360W STRBXDS2 CONTROL BLOCK xxx INVALID - NO MATCH ON EYECATCHER
Explanation: Validation of control block xxx failed.
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.
User Response: None required.
STR0401W GETMAIN FAILURE - I/O INFORMATION WILL NOT BE REPORTED
Explanation: A measurement task module cannot obtain sufficient storage for its work area.
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: Increase the region size and resubmit the request.
STR0402W GETMAIN FAILURE - SOME DATA SETS MAY NOT BE MAPPED
Explanation: Strobe cannot obtain enough virtual storage for an internal table.
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: Increase the region size and resubmit the request.
STR0403W GETMAIN FAILURE - DATA SET CHARACTERISTICS MAY BE MISSING
Explanation: Strobe cannot obtain enough virtual storage for an extension to its internal dataset table.
System Action: Strobe continues sampling but may not collect dataset characteristics for some datasets active during the measurement session.
User Response: Increase the region size and resubmit the request.
STR0404E STRBVIO FAILURE - DATASET CHARACTERISTICS MAY BE MISSING
Explanation: A measurement task module has encountered an unrecoverable error.
System Action: Strobe continues sampling but stops taking I/O samples.
User Response: Notify the Strobe system programmer.
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: The next time you submit this request, increase the region size.
STR0406W STRBLSRS DISABLED, EXCEEDED MAX GETMAINS
Explanation: An internal error occurred in the measurement task module STRBLSRS.
System Action: Strobe disabled STRBLSRS. Sampling continues, but Strobe will no longer collect LSR statistical information during this measurement session.
User Response: Notify the Strobe system programmer.
STR0407W 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: Notify the Strobe system programmer.
STR0408W GETMAIN FAILURE FOR THE ACTIVE DEVICE TABLE
Explanation: Strobe cannot obtain enough virtual storage for an internal table.
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.
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: Strobe continues processing, but there may be some loss of function.
User Response: Notify the Strobe system programmer.
STR0410E 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: Strobe continues processing, but there may be some loss of function.
User Response: Notify the Strobe system programmer.
STR0411W 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: Strobe continues processing, but there may be some loss of function.
User Response: Notify the Strobe system programmer.
STR0412E 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: Strobe continues processing, but there may be some loss of function.
User Response: Notify the Strobe system programmer.
STR0413W MODULE FUNCTION FAILED, RC=rc
Explanation: The specified function failed with the return code of rc.
System Action: Strobe continues processing.
User Response: Notify the Strobe system programmer.
STR0414W STORAGE OBTAIN FAILED FOR storarea
Explanation: A STORAGE OBTAIN for the area specified by storarea failed.
System Action: Strobe continues processing.
User Response: Notify the Strobe system programmer.
STR0415W BatchPipes query failed RC xxxx RSNC xxxxx
Explanation: Strobe unsuccessfully invoked an MVS function to query BatchPipes. RC xxxx is the return code and RSNC xxxx is the reason code returned from the query. Strobe does not support third-party implementations of BatchPipes.
System Action: Strobe continues processing, but BatchPipes statistics will not be provided.
User Response: Notify the Strobe system programmer if using IBM's BatchPipes.
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: Notify the Strobe system programmer. There has probably been a hardware error.
STR0502W 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.
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: Notify the Strobe system programmer. There has probably been a hardware error.
STR0503E OUT OF SPACE ON SAMPLE DATASET
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 User Guide for additional information.
STR0504E I/O ERROR WRITING TO SAMPLE DATASET
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: Strobe continues execution of the target program but collects no further samples.
User Response: Notify the Strobe system programmer. There has probably been a hardware error.
STR0505E ABEND WHILE PROCESSING SAMPLE DATASET - 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: Notify the Strobe system programmer.
STR0506E WRITE ATTEMPTED TO CLOSED SAMPLE FILE
Explanation: The measurement task attempted to write to a closed sample dataset.
System Action: The measurement task terminates.
User Response: Notify the Strobe system programmer.
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: The measurement task terminates.
User Response: Notify the Strobe system programmer.
STR0508W ABEND WHILE READING LOAD LIBRARY - COMPLETE CODE= abendcode, RETURN CODE=rc
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.
STR0509W DATASPACE API INITIALIZATION FAILED -- FUNCTION DISABLED, RC=rrr, ERC=erc
Explanation: An error occurred during the initialization of the Dataspace Manager API.
System Action: Strobe continues sampling without Dataspace Manager functions.
User Response: Notify the Strobe system programmer.
STR0510W DATASPACE API DEALLOCATION FAILURE; RC=rrr; ERC=erc
Explanation: An error occurred during the termination of the Dataspace Manager API.
System Action: Strobe continues terminating Dataspace Manager API.
User Response: Notify the Strobe system programmer.
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: The measurement task terminates.
User Response: The error may be temporary. Try resubmitting the request.
STR0540W 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: Notify the Strobe system programmer.
STR0550W 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
Explanation: A Strobe internal storage request for control block block failed.
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.
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: Strobe continues measuring but does not execute the requested function.
User Response: Contact Compuware Customer Support.
STR0553W STRBGMIM: CAPTURE PROCESSING FAILED DURING VECTOR SWAP
Explanation: A Strobe internal request to insert a capture routine failed.
System Action: Strobe continues measuring, but does not enable the capture routine.
User Response: Contact Compuware Customer Support.
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.
User Response: Contact Compuware Customer Support.
STR0555W STRBGMIM: CAPTURE PROCESSING FAILED. MULTIPLE CAPTURES FOR SAME ADDRESS
Explanation: Strobe made an internal request for a capture routine with a vector address that had previously been processed.
System Action: Strobe continues measuring but does not enable the capture routine.
User Response: Contact Compuware Customer Support.
STR0556W STRBGMIM: CAPTURE PROCESSING FAILED. CAPTURE FACILITY DISABLED
Explanation: A Strobe internal request for a capture routine failed because the facility was disabled.
System Action: Strobe continues measuring with the capture routine disabled.
User Response: None required.
STR0557I xxxxxxxx Capture active during removal hhhhhhhh
Explanation: Strobe found a capture entry to be active while attempting to remove it. xxxxxxxx indicates where the attempt to free .5k of storage at location hhhhhhhh was made. The entry will be freed when the measured task terminates.
System Action: Strobe continues processing.
User Response: None required.
STR0559I STRBGMIM: xxxxxxxxxx
Explanation: Strobe has stored diagnostic data in xxxxxxxxxx.
System Action: Strobe continues processing, but some measurement data may be missing.
User Response: Contact Compuware Customer Solutions.
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 User Guide.
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
Explanation: Strobe cannot find the data collector modname.
System Action: Strobe continues sampling without the data collector.
User Response: Place the data collector in a link list dataset 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: Strobe continues sampling without the data collector.
User Response: Notify the Strobe system programmer.
STR0604W 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: Strobe continues sampling without the data collector.
User Response: Notify the Strobe system programmer.
STR0605W GETMAIN FAILURE - SOME MODULES MAY NOT BE MAPPED
Explanation: Strobe cannot obtain sufficient storage for an extension to its internal module table.
System Action: Strobe continues sampling without mapping information for some modules.
User Response: Increase the region size and resubmit the request.
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: Strobe continues sampling without subsystem or attribution data.
User Response: Notify the Strobe system programmer.
STR0607W DATA COLLECTION INTERFACE CALLED WITH INVALID FUNCTION CODE (fctcode)
Explanation: The data collection interface was called with an invalid function code fctcode.
System Action: Strobe continues sampling without some subsystem or attribution data.
User Response: Examine all user-written data collectors, and then notify the Strobe system programmer.
STR0608W DATA COLLECTION INTERFACE CALLED WITH NO PARAMETER LIST
Explanation: The data collection interface was called with no parameter list pointer.
System Action: Strobe continues sampling without some subsystem or attribution data.
User Response: Notify the Strobe system programmer.
STR0609W DATA COLLECTION INTERFACE INVOKED BY UNKNOWN CALLER
Explanation: The data collection interface was called by a program not recognized by Strobe.
System Action: Strobe continues sampling without some subsystem or attribution data.
User Response: 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
Explanation: Virtual storage is not available for the VDCCWORK AREA.
System Action: Strobe continues sampling without any 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.
STR0613W DATA COLLECTOR datacollector IGNORED - Strobe INTERFACE NOT LICENSED
Explanation: You attempted to use the Strobe Interface, but your site has not licensed this option.
System Action: Strobe will not invoke the user-written data collector datacollector.
User Response: To obtain information about licensing the Strobe Interface, contact Compuware Customer Support.
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: The variable returned depends on the caller of the API.
User Response: Notify the Strobe system programmer.
STR0630E 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: Increase the region size and resubmit the request.
STR0631W BATCHPIPE WAIT DETECTED, FILE CANNOT BE IDENTIFIED
Explanation: Strobe identified BatchPipe wait but is unable to assign this wait to a specific 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 Advanced-Configuration-Guide. If you have performed the procedure and the problem persists, contact Compuware Customer Solutions.
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: Contact Compuware Customer Solutions.
STR0633W 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: Strobe does not identify the HFS or z/FS file. Strobe continues processing.
User Response: Contact Compuware Customer Solutions.
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: Strobe suspends the HFS or z/FS data collection interface.
User Response: Contact Compuware Customer Solutions.
STR0701W GETMAIN FAILURE IN STRBATTR - ATTRIBUTION DATA COLLECTION DISABLED
Explanation: Strobe cannot obtain virtual storage for a work area.
System Action: Strobe continues sampling without attribution data.
User Response: Increase the region size and resubmit the request. Notify the Strobe system programmer.
STR0702W ATTRIBUTOR modname NOT FOUND - UNABLE TO COLLECT REQUESTED ATTRIBUTION DATA
Explanation: Strobe cannot find the requested attributor modname.
System Action: Strobe continues sampling without some attribution data.
User Response: Notify the Strobe system programmer.
STR0703W 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: Strobe continues sampling without the attributor.
User Response: Notify the Strobe system programmer.
STR0704W ATTRIBUTOR modname ABENDED - ROUTINE DISABLED
Explanation: The attributor name modname terminated abnormally.
System Action: Strobe continues sampling without the attributor.
User Response: Notify the Strobe system programmer.
STR0705W ATTRIBUTION DRIVER STRBATTR ABENDED - ATTRIBUTION DISABLED
Explanation: The attribution driver terminated abnormally.
System Action: Strobe continues sampling without attribution data.
User Response: Notify the Strobe system programmer.
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 operator’s 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 operator’s 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.
System Action: The Measurement Services Address Space (MSAS), which includes AutoStrobe, was not initialized.
User Response: Report the problem to the Strobe system programmer.
STR0714E 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 manager’s 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 Strobe MEASUREMENT SERVICES release STOP COMMAND RECEIVED FROM CONSOLE console id
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 operator’s 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: Attribution for the current sample terminates. Measurement continues.
User Response: None required.