Additional Strobe Messages
STR6800I DSN=prefix.jobname.ssssdddd (.suffix) (unit volser)
Explanation: This message fully identifies the sample dataset referred to in the preceding message. The sample dataset, which Strobe attempted to allocate or deallocate, is named prefix.jobname.ssssdddd. If present, the suffix is suffix, the unit is unit, and the volume serial number is volser.
System Action: See the preceding message.
User Response: See the preceding message.
STR6801I 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 iStrobe. The dataset is given in message STR6800I.
System Action: Strobe continues processing.
User Response: None required.
STR6802I 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: Strobe completes measurement of the sample dataset.
User Response: None required.
STR6803S 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
Explanation: Strobe could not allocate a dataset because DFHSM was not active.
System Action: Strobe terminates sampling.
User Response: 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: Strobe is unable to return the data that you requested.
User Response: Resubmit the request. If the problem continues, notify the Strobe system programmer.
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: Strobe is unable to present the data that you requested.
User Response: Resubmit the request. If the problem continues, notify the Strobe system programmer.
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: Strobe is unable to determine the state of request nnnn but continues processing.
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 DATASET 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 Advanced Configuration Guide.
STR6810W ddname DATASET 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.
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 Strobe-XCF group before attempting to clean up and reorganize the file. For specific instructions, see the Strobe Advanced Configuration 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
Explanation: Strobe writes this message to the Strobe log in certain diagnostic situations.
System Action: Strobe continues processing.
User Response: None required.
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 Advanced Configuration 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 cross-system 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.
•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: Strobe does not process the measurement request.
User Response: Notify the Strobe system programmer.
STR6817W 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: Strobe reads the request but does not update its local work area.
User Response: 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. IBM’s 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 IBM’s 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: The call was aborted. Strobe processing continues.
User Response: Contact Compuware Customer Support.
STR6822E routine text
Explanation: An internal processing error has occurred in routine routine and is described in text.
System Action: Strobe does not process the request.
User Response: This message contains important diagnostic information. Contact Compuware Customer Support.
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: None required.
STR6824I SEND OPERATION FAILED; REASON: text
Explanation: The SEND operation failed and the possible reasons are given in text. text can be:
•REQUEST NOT FOUND
•UNKNOWN SEND REQUEST TYPE
•DELETE INPUT INVALID
•ACCESS DENIED
•ACEE BUILD FAILED
•SEND TIME-OUT.
System Action: Strobe does not process the request.
User Response: Notify the Strobe system programmer.
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: Notify the Strobe system programmer.
STR6828E 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.
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: Strobe processes the request.
User Response: None required.
STR6830I 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: Strobe processes the request.
User Response: None required.