Messages Returned by Global Monitoring
STRGB0001I Strobe Monitoring for batch @@ task @@ initialization in progress
Severity: Informational
Explanation: The Strobe Monitoring task for batch jobs is initializing.
System Action: Processing continues.
User Response: None.
STRGB0002I Strobe Monitoring for batch @@ task @@ initialization complete
Severity: Informational
Explanation: The Strobe Monitoring task for batch jobs has completed initialization.
System Action: Processing continues.
User Response: None.
STRGB0003I Strobe Monitoring for batch @@ task @@ termination in progress
Severity: Informational
Explanation: The Strobe Monitoring task for batch jobs is terminating.
System Action: Processing continues.
User Response: None.
STRGB0004I Strobe Monitoring for batch termination complete return code @@
Severity: Informational
Explanation: The Strobe Monitoring task for batch jobs has terminated. The return code is shown in the message
System Action: Processing continues.
User Response: None.
STRGB0010W Strobe Monitoring for JOB @@ @@ STEP @@ PROCSTEP @@ failed to complete.
Severity: Warning
Explanation: Strobe Monitoring for batch attempted to process a monitored JOB STEP but the JOB appears to have ended without the Strobe Monitoring SMF exit at IEFACTRT seeing the JOB or STEP end.
System Action: The STEP that was being monitored will not be used in calculating CPU and elapsed time thresholds.
User Response: Be certain that the Strobe Monitor SMF exits at IEFACTRT remain active using the MNAS MODIFY SMFX_LIS command, and SMF 30 records for SYSJES2 are being captured in SMFPRMxx using the D SMF,O command. If the exits are still active and SMF 30 records are being captured, collect the SMF 30 records from the time the listed JOB started until the time it ended, and contact BMC Support.
STRGB0031S Unable to obtain storage for @@ data area. Return code=@@.
Severity: Severe
Explanation: The Strobe Monitoring for batch task attempted to obtain storage for a data area. The storage request failed. The name of the data area and the return code from the STORAGE OBTAIN macro instruction are shown in the message.
System Action: Processing continues.
User Response: Be certain that sufficient storage is available the MNAS.
STRGB0101I Posting subtask @@ task @@ to shut down
Severity: Informational
Explanation: The batch task has posted a subtask to shut down. The name of the subtask module is shown in the message.
System Action: Processing continues.
User Response: None.
STRGB0102I Waiting for subtask detach
Severity: Informational
Explanation: The batch task has posted subtasks to shut down and is waiting for them to terminate. This is a debugging message for BMC Support.
System Action: Processing continues.
User Response: None.
STRGB0103I Detaching subtask @@ task @@
Severity: Informational
Explanation: The batch task has posted a subtask to shut down. The subtask is now being detached. The name of the subtask module is shown in the message.
System Action: Processing continues.
User Response: None
STRGB0104I Waiting for subtask @@ to end
Severity: Informational
Explanation: The batch task has posted a subtask to shut down. The subtask is now being detached. The name of the subtask module is shown in the message.
System Action: Processing continues.
User Response: None
STRGB0900I @@ Processing work queue.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGB0901I @@ task @@ posted with @@ for JOB @@ STEP @@ PSTEP @@ JOBID @@
Severity: Informational
Explanation: The Global Monitor Batch component detected a threshold exception and submitted the specified request type for the listed JOB/STEP/PSTEP.
System Action: Processing continues.
User Response: If necessary verify a measurement is required for the listed JOB/STEP/PSTEP. If not then reevaluate the Global Monitor criteria definitions in the STRGMCRI data set.
STRGB0902W @@ no subtasks available for @@ of JOB @@ STEP @@ PSTEP @@
Severity: Informational
Explanation: The Global Monitor Batch component detected a threshold exception but failed to submit the specified request type for the listed JOB/STEP/PSTEP, because there were no subtasks available to carry out the request.
System Action: Processing continues.
User Response: If necessary verify a measurement is required for the listed JOB/STEP/PSTEP. If not then reevaluate the Global Monitor criteria definitions in the STRGMCRI data set.
STRGC0001S Unable to load module @@. CICS monitoring shutting down.
Severity: Severe
Explanation: The Strobe Monitoring task for CICS was unable to load a required module. The module name is shown in the message.
System Action: Strobe monitoring for CICS terminates.
User Response: Ensure the module named in the message is available to the Monitoring Address Space.
STRGC0101I Strobe Monitoring for CICS initialization in progress
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is initializing.
System Action: Processing continues.
User Response: None.
STRGC0102I Strobe Monitoring for CICS initialization complete
Severity: Informational
Explanation: The Strobe Monitoring task for CICS has completed initialization.
System Action: Processing continues.
User Response: None.
STRGC0103I Strobe Monitoring for CICS termination in progress
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is terminating.
System Action: Processing continues.
User Response: None.
STRGC0104I Strobe Monitoring for CICS termination complete return code @@
Severity: Informational
Explanation: The Strobe Monitoring task for CICS has terminated. The return code is shown in the message
System Action: Processing continues.
User Response: None.
STRGC0105I Request @@ @@ for JOB @@ JOBID @@ @@ @@ PSTEP @@ received.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS has been posted to process a request for the JOB, JOBID, and STEP or transaction shown.
System Action: Processing for the request begins.
User Response: None.
STRGC0106E Unable to @@ ALET for JOB @@, ALESERV return code @@
Severity: Error
Explanation: The Strobe Monitoring task for CICS was unable to add or delete an ALET used to access CICS storage. The ALESERV return code is shown.
System Action: Request processing terminates for ADD requests and continues for DELETE requests.
User Response: Repeat the attempt to monitor the CICS region shown in the message. If problem persists contact Compuware Technical Support.
STRGC0107I REGISTER in progress for JOB @@ JOBID @@ STEP @@ PSTEP @@.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is attempting to IDENTIFY the CICS release of the JOB, STEP, and PSTEP shown in the message.
System Action: Identification of CICS and its release begins.
User Response: None.
STRGC0108I JOB TERM in progress for JOB @@ JOBID @@.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is attempting to disconnect CICS JOB shown in the message from being monitored.
System Action: The JOB will no longer be known to the Strobe Monitoring task.
User Response: None.
STRGC0109I STEP TERM initiated for JOB @@ JOBID @@ STEP @@ PSTEP @@ FLAGS @@
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing STEP termination for the STEP and PSTEP in the JOB shown in the message.
System Action: The STEP will no longer be known to the Strobe Monitoring task.
User Response: None.
STRGC0110I @@ found zero (or matching) CICS JOB entries in the system.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing a CICS modify command and either found no JOB entries or none for a specific JOB.
System Action: Processing of the command terminates.
User Response: Use the CICSDISPLAY command to verify finding no CICS JOB entries or none that match the entered JOB name.
STRGC0111I Processing MODIFY command @@.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS has received a MODIFY command shown in the message.
System Action: Process the command.
User Response: None.
STRGC0112E Invalid MODIFY @@ received: @@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS has received an invalid MODIFY command or operand shown in the message.
System Action: Command processing terminates.
User Response: Review Strobe Global Monitoring MODIFY commands and correct.
STRGC0113E CICSSTART found GMMJ for JOB @@ JOBID @@ STEP @@ PSTEP @@ flag @@
Severity: Error
Explanation: The Strobe Monitoring task for CICS is processing a CICSSTART command and found an existing entry for the JOB, JOBID, STEP, PSTEP, and flags shown in the message.
System Action: Processing of the CICSSTART command terminates.
User Response: Review log messages to verify that issuing a CICSSTART command for the JOB is appropriate. Contact Compuware Technical Support if a CICSSTOP for the JOB completed successfully.
STRGC0114E CICSSTART could not locate necessary information for JOB @@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS is processing a CICSSTART command but could not find the necessary information from the ASCB for JOB @@.
System Action: Processing of the CICSSTART command terminates.
User Response: Ensure that the JOB is fully initialized before issuing a CICSSTART for the JOB.
STRGC0115I @@ found entry for JOB @@ JOBID @@ STEP @@ PSTEP @@.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing a CICSSTOP or CICSPURGE command and found an entry for the JOB, JOBID, STEP, and PSTEP shown the message.
System Action: Processing of the CICSSTOP or CICSPURGE command continues.
User Response: None.
STRGC0116E @@ could not find a tracking entry for JOB @@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS is processing a CICSDISABLE or CICSENABLE command and could not find an entry for the JOB shown the message.
System Action: Processing of the CICSDISABLE or CICSENABLE command terminates.
User Response: Check the logs for messages indicating the target JOB had been previously enabled or disabled.
STRGC0117E @@ could not find CICS information for JOB @@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS is processing a CICSDISABLE or CICSENABLE command and could not find associated CICS information for the JOB shown in the message.
System Action: Processing of the CICSDISABLE or CICSENABLE command terminates.
User Response: Check the logs for messages indicating the target JOB had been previously enabled or disabled.
STRGC0118E Identify request for JOB @@ JOB ID @@ reached maximum attempts.
Severity: Error
Explanation: The Strobe Monitoring task for CICS was attempting to identify the CICS release of the JOB shown but reached the maximum attempts.
System Action: Identify processing terminates.
User Response: Use the CICSSTOP and CICSSTART commands to re-initialize the identify and implant process, if the JOB is CICS.
STRGC0119W @@ JOB name operand @@ exceeds 8 characters.
Severity: Warning
Explanation: A CICSDISPLAY command was received with a JOB name operand that exceeded 8 characters.
System Action: JOB name operand is truncated to the first 8 characters which may result in incorrect results.
User Response: If necessary reenter the CICSDISPLAY command with the correct JOB name not to exceed 8 characters.
STRGC0120I @@ Last Request @@ Intercept Address @@ Work Area @@ Re @@ FG3 @@
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing a CICSDISPLAY command and found an entry for the JOB, JOBID, and STEP known to be a CICS JOB.
System Action: Processing of the CICSDISPLAY command continues.
User Response: None.
STRGC0121I @@ CICS Release @@ State @@ Intercept State @@ CBs found @@
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing a CICSDISPLAY command and found an entry for the JOB, JOBID, and STEP known to be a CICS JOB.
System Action: Processing of the CICSDISPLAY command continues.
User Response: None.
STRGC0122I @@ CICS Prolog @@ Entry @@ Intercept Prolog @@ Entry @@ State @@
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing a CICSDISPLAY command and found an entry for the JOB, JOBID, and STEP known to be a CICS JOB.
System Action: Processing of the CICSDISPLAY command continues.
User Response: None.
STRGC0123I @@ found @@ CICS JOB STEP entries in the system.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing a CICSDISPLAY command and found the displayed number of CICS JOB(s) in the system.
System Action: Processing of the CICSDISPLAY command terminates.
User Response: None.
STRGC0124E Cannot implant in JOB @@, it does not meet your monitor criteria.
Severity: Error
Explanation: The Strobe Monitoring task for CICS is processing a CICSSTART command and found the displayed JOB is either excluded or not included in your STRGMCRI data set.
System Action: Processing of the CICSSTART command terminates.
User Response: Review your INCLUDE and EXCLUDE criteria using the STRBGMCL utility.
STRGC0125I Querying criteria specifications for JOB @@ STEP @@ PSTEP @@.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is querying the criteria loaded from your STRGMCRI data set to determine if it should be monitored.
System Action: Processing depends upon the contents of your STRGMCRI, either the JOB will be monitored or not.
User Response: Review subsequent messages and your STRGMCRI contents using the STRBGMCL utility if monitoring is not as expected.
STRGC0126I ASVT scan complete, @@ total entries queried with @@ identified.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS scanned the ASVT looking for JOBs to be monitored based upon your criteria loaded from STRGMCRI. The number of JOBs queried and meeting your criteria are shown.
System Action: Processing depends upon the contents of your STRGMCRI, either the JOB(s) will be monitored or not.
User Response: Review subsequent messages and your STRGMCRI contents using the STRBGMCL utility if monitoring is not as expected.
STRGC0127E The @@ command requires @@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS was attempting to process the listed command but could not complete because of the stated error condition.
System Action: Processing terminates.
User Response: Review Global Monitor for CICS command documentation and attempt to repeat the command.
STRGC0200I CICS @@ received @@ processed @@ lost @@.
Severity: Informational
Explanation: The Global Monitor CICS task displayed the number of transaction buckets received, the number successfully buffered to the Global Monitor pump task, the number unable to be buffered, and the corresponding transactions received, buffered and lost for these buckets. If this message resulted from a CICSSTATS command, the data is displayed in hex and represents the totals as of the last day. If displayed automatically on the hourly interval, the data is displayed in decimal and represents totals for the current day.
System Action: Processing continues; this is informational and may be requested by Compuware Technical Support.
User Response: A high number of lost buckets/transactions may indicate a problem communicating to or availability of the SMF Manager in iStrobe. Check the status of the SMF Manager in the iStrobe Configuration. It could also represent a workload issue that requires adding more buffers. Run the Global Monitor PUMPSTATS command and contact Compuware Technical Support for assistance.
STRGC0201E Validity check occured on request @@ for JOB @@ JOBID @@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS was processing the request for the JOB shown in the message but an internal validity check failed.
System Action: Processing of the request terminates.
User Response: Contact Compuware Technical Support.
STRGC0202I @@ request @@ ended with RC=@@ Reas=@@.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS was processing a request which ended with a return code and reason code, all shown in the message.
System Action: Processing of the request completed.
User Response: None.
STRGC0203E @@ STORAGE OBTAIN request failed, RC=@@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS failed to obtain storage in CICS, STORAGE OBTAIN failed with the return code shown.
System Action: Processing of the request terminates.
User Response: Contact Compuware Technical Support.
STRGC0204E @@ Intercept remains from a previously failed DISCONNECT.
Severity: Error
Explanation: The Strobe Monitoring task for CICS was processing an implant request which found a copy of the intercept in the CICS address space.
System Action: Implant processing terminates.
User Response: Use the Modify CICSPURGE then CICSSTART commands to start monitoring the target CICS JOB.
STRGC0205I @@ Disabled intercept has been instructed to reconnect.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS was processing an implant request which found a copy of the intercept in the CICS address space.
System Action: Implant processing completes.
User Response: Ensure that monitoring resumes using the MODIFY CICSDISPLAY command for the target CICS JOB.
STRGC0206S @@ Implant processing failed on the swap.
Severity: Severe
Explanation: The Strobe Monitoring task for CICS was processing an implant request which failed to insert the intercept in the CICS MN domain.
System Action: Implant processing terminates.
User Response: Use the MODIFY CICSDISPLAY command for the target CICS JOB and contact Compuware Technical Support.
STRGC0207E @@ STORAGE RELEASE request failed, address=@@ RC=@@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS failed to release storage in CICS, STORAGE RELEASE failed with the return code shown.
System Action: Processing of the request terminates.
User Response: Contact Compuware Technical Support.
STRGC0208E @@ request Implant found @@ already implanted in CICS @@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS failed to implant the intercept because it found that another MNAS had implanted in this CICS.
System Action: Processing of the request terminates.
User Response: If desired remove the intercept from the MNAS shown in the message using the CICSSTOP or CICSPURGE command on the CICS JOB. If running multiple MNAS decide which one is to monitor this CICS JOB and update the criteria file.
STRGC0300I @@ JOB @@ JOBID @@ STEP @@ is CICS at release @@.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing an Identify request and found that the JOB is CICS at the release shown.
System Action: Identify processing is complete.
User Response: None.
STRGC0301I @@ JOB @@ JOBID @@ STEP @@ is CICS but not release @@.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing an Identify request and found that the JOB is CICS but not at the release shown.
System Action: Identify processing continues.
User Response: None.
STRGC0302I @@ JOB @@ JOBID @@ STEP @@ is CICS release @@ but PLTPI not done.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing an Identify request and found that the JOB is CICS at the release shown but is not fully initialized.
System Action: Identify processing continues.
User Response: None.
STRGC0303I @@ JOB @@ JOBID @@ STEP @@ could not find all CBs, found @@.
Severity: Informational
Explanation: The Strobe Monitoring task for CICS is processing an Identify request but could not find all of the necessary control blocks for identification. A hex representation of what was found is given.
System Action: Identify processing continues.
User Response: None.
STRGC0304E @@ JOB @@ JOBID @@ STEP @@ could not identify DFHMNXM.
Severity: Error
Explanation: The Strobe Monitoring task for CICS is processing an Identify request but could not identify the IBM DFHMNXM module in order to implant Global Monitoring.
System Action: Identify processing terminates.
User Response: Contact Compuware Technical Support.
STRGC0305E @@ JOB @@ JOBID @@ STEP @@ is CICS but unsupported release @@.
Severity: Error
Explanation: The Strobe Monitoring task for CICS is processing an Identify request and found that the JOB is CICS but is an unsupported (old) release.
System Action: Identify processing terminates.
User Response: Monitor supported releases of CICS.
STRGC0904I Error sending CICS transaction data to data pump r/c=@@ Reason co de=@@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGC0905I @@ @@ @@. CPU/Elapsed=@@ @@. Entry=@@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGC0906I Global Monitoring CICS scheduling SRB. Target job name @@ ASID @@ Function @@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGC0907I Global Monitoring CICS SRB schedule failed: @@ @@ @@ @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGC0908I Global Monitoring CICS SYSEVENT failed RC=@@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI0016E Unable to find module @@ r/c=@@ reason code=@@.
Severity: Error
Explanation: The Strobe Monitoring task for IMS attempted to find the module shown in the message. The return and reason code from the BLDL macro are also shown in the message.
System Action: The Strobe IMS task terminates.
User Response: Be sure the module shown in the message is in a load library available to the MNAS.
STRGI0101I Strobe Monitoring for IMS initialization in progress
Severity: Informational
Explanation: The Strobe Monitoring task for IMS is initializing.
System Action: Processing continues.
User Response: None.
STRGI0102I Strobe Monitoring for IMS initialization complete
Severity: Informational
Explanation: The Strobe Monitoring task for IMS has completed initialization.
System Action: Processing continues.
User Response: None.
STRGI0103I Strobe Monitoring for IMS termination in progress
Severity: Informational
Explanation: The Strobe Monitoring task for IMS is terminating.
System Action: Processing continues.
User Response: None.
STRGI0104I Strobe Monitoring for IMS termination complete return code @@
Severity: Informational
Explanation: The Strobe Monitoring task for IMS has terminated. The return code is shown in the message
System Action: Processing continues.
User Response: None.
STRGI0111I Processing MODIFY command @@.
Severity: Informational
Explanation: The Strobe Monitoring task for IMS has received a MODIFY command shown in the message.
System Action: Process the command.
User Response: None.
STRGI0112E Invalid MODIFY @@ received: @@.
Severity: Error
Explanation: The Strobe Monitoring task for IMS has received an invalid MODIFY command or operand shown in the message.
System Action: Command processing terminates.
User Response: Review Strobe Global Monitoring MODIFY commands and correct.
STRGI0113E Global Monitoring for IMS already active for region @@ job ID @@ ASID @@.
Severity: Error
Explanation: The Strobe Monitoring task for IMS is processing a IMSSTART command and determined that Global Monitoring for IMS is already active for the IMS region. The job name job ID, and address space ID (ASID) are shown in the message.
System Action: Processing of the IMSSTART command terminates for the named IMS region.
User Response: Review log messages to verify that issuing a IMSSTART command for the region is appropriate.
STRGI0114E IMSSTART could not locate necessary information for JOB @@.
Severity: Error
Explanation: The Strobe Monitoring task for IMS is processing a IMSSTART command but could not find the necessary information from the ASCB for JOB @@.
System Action: Processing of the IMSSTART command terminates.
User Response: Ensure that the JOB is fully initialized before issuing a IMSSTART for the JOB.
STRGI0119W @@ job name operand @@ exceeds 8 characters.
Severity: Warning
Explanation: A command was received with a JOB name operand that exceeded 8 characters.
System Action: JOB name operand is truncated to the first 8 characters which may result in incorrect results.
User Response: If necessary reenter the command with the correct JOB name not to exceed 8 characters.
STRGI0120I List of monitored IMS MPP regions follows:
Severity: Informational
Explanation: The IMSDISPLAY command was recieved and is being processed. A list of the currently monitored IMS MPP regions follows this message.
System Action: Processing continues
User Response: See message STRGI0121 for information about each MPP region actively being monitored.
STRGI0121I IMS MPP region job name: @@. ASID: @@. IMS ID: @@
Severity: Informational
Explanation: The IMSDISPLAY command was recieved and is being processed. This message displays information about a MPP region that is currently being monitored.
System Action: Processing continues
User Response: None.
STRGI0123I End of List. @@ IMS MPP region(s) currently monitored
Severity: Informational
Explanation: The IMSDISPLAY command was received and is being processed. This message concludes the list of currently monitored IMS MPP regions and shows the number of regions currently being monitored.
System Action: Processing continues
User Response: None.
STRGI0124E Cannot implant in JOB @@, it does not meet your monitor criteria.
Severity: Error
Explanation: The Strobe Monitoring task for IMS is processing a IMSSTART command and found the displayed JOB is either excluded or not included in your STRGMCRI data set.
System Action: Processing of the IMSSTART command terminates.
User Response: Review your INCLUDE and EXCLUDE criteria using the STRBGMCL utility.
STRGI0200I IMS @@ received @@ processed @@ lost @@.
Severity: Informational
Explanation: The Global Monitor IMS task displayed the number of transaction buckets received, the number successfully buffered to the Global Monitor pump task, the number unable to be buffered, and the corresponding transactions received, buffered, and lost for these buckets. If this message resulted from a IMSSTATS command, the data is displayed in hex and represents the totals as of the last day. If displayed automatically on the hourly interval, the data is displayed in decimal and represents totals for the current day.
System Action: Processing continues; this is informational and may be requested by Compuware Technical Support.
User Response: A high number of lost buckets/transactions may indicate a problem communicating to or availability of the SMF Manager in iStrobe. Check the status of the SMF Manager in the iStrobe Configuration. It could also represent a workload issue that requires adding more buffers. Run the Global Monitor PUMPSTATS command and contact Compuware Technical Support for assistance.
STRGI0900I @@ Processing work queue.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI0901I Calling STRBGIIM for @@. Job name: @@. IMS ID: @@. Function: @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI0902I Calling STRBGIIM for @@. Job name: @@. Function: @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI0903I Global Monitoring for IMS SRB module address: @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI0904I Error sending IMS transaction data to data pump r/c=@@ Reason cod e=@@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI0905I @@ @@ @@. CPU/Elapsed=@@ @@. Entry=@@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI0910I Error attempting to @@. IMS Job: Step:Pstep=@@:@@:@@. RC=@@. FLG2=@
Severity: Informational
Explanation: An attempt was made to implant or remove the Strobe Global Monitoring IMS intercept. The current attempt failed. The request type (Implant/Remove), the IMS job name, and the return code from the implant/remove module are shown in the message. The flag indicates what items were found when determining if the target JOB is a dependent IMS message processing region. The possible values are:
•X'80' - FOUND TARGET JOB IN VTD
•X'40' - ASXBITCB FOUND
•X'20' - DFSRRC00 FOUND
•X'10' - DEPENDENT RGN FOR TXNS
•X'08' - EXEC PGM= FOUND NOT RC00
•X'04' - PARM=() NOT FOUND
•X'02' - S0C4 ACCESSING TARGET REGN
•X'01' - DEPENDENT RGN NOT FOR TXNS
System Action: Processing continues.
User Response: If the problem occurred during implant, attempt to implant the intercept again using the IMSSTART command. If the problem occurred during remove, attempt to remove the intercept again using the IMSSTOP command. To determine if the implant was eventually successful use the IMSDISPLAY command, or set GM_DEBUG=YES and look for a corresponding STRGI1021I with the JOB name from this message.
STRGI1016E Unable to find module @@ r/c=@@ reason code=@@.
Severity: Error
Explanation: The Strobe Monitoring for IMS implant routine attempted to find the module shown in the message. The return and reason code from the BLDL macro are also shown in the message.
System Action: The Strobe IMS implant routine terminates.
User Response: Be sure the module shown in the message is in a load library available to the Strobe implant routine.
STRGI1020I @@ found IMS SVC @@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel. The program shown in the message found an IMS SVC. The address of the SVC routine is shown in the message.
System Action: Processing continues.
User Response: None.
STRGI1021I Target IMS region found: @@ @@ @@ @@ @@ @@.
Severity: Informational
Explanation: Based on Global Monitor criteria (target IMS MPR) and validation that the target is an IMS MPR, Global Monitor IMS will attempt an implant of the Global Monitor IMS intercept for this address space. Check subsequent messages or use the Global Monitor IMSDISPLAY command to check the results of that implant attempt.
System Action: Processing continues.
User Response: None.
STRGI1022I Global Monitoring IMS intercept stub address: @@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI1023I IMS Logical Logger (DFSFLLG0) found: @@ @@ @@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI1024I Global Monitoring IMS intercept address: @@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI1025I Global Monitoring IMS SRB module address: @@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI1026I Global Monitoring @@ SRB scheduled. Target job name @@. ASID @@. Function @@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI1027I Global Monitoring IMS SRB schedule failed: @@ @@ @@ @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI1028I Error removing Global Monitoring IMS intercept: @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI1309I Name/Token pair @@ not deleted. Name/Token Callable services r/c =@@.
Severity: Informational
Explanation: The Name/Token pair associated with Global Monitoring for IMS was not deleted. The name portion of the Name/Token pair, and the return code from IBM Name/Token Callable Services are shown in the message.
System Action: Processing continues.
User Response: None.
STRGI1322I Name/Token pair @@ not found. Name/Token Callable Services r/c @ @.
Severity: Informational
Explanation: The Name/Token pair associated with Global Monitoring for IMS was not found. This is a normal situation if the MNAS has not been active since the last IPL. The name portion of the Name/Token pair and the return code from IBM Name/Token Callable Services are shown in the message.
System Action: Processing continues.
User Response: If the return code is 4, none.
STRGI1328I Name/Token pair @@ deleted.
Severity: Informational
Explanation: The Name/Token pair associated with Global Monitoring for IMS was deleted. The name portion of the Name/Token pair is shown in the message.
System Action: Processing continues.
User Response: None.
STRGI1330I GIST address = @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI1420E Name/Token pair @@ not deleted. MNAS @@ is currently active.
Severity: Error
Explanation: The Name/Token pair associated with the Strobe Monitoring Address Space was not deleted. The MNAS associated with the Name/Token pair is currently active. The name portion of the Name/Token pair and the job name of the MNAS are shown in the message.
System Action: Processing continues.
User Response: Shut down the MNAS prior to running the Name/Token pair delete utility.
STRGI1422I Name/Token pair @@ not found. Name/Token Callable Services r/c @ @.
Severity: Informational
Explanation: The Name/Token pair associated with the Strobe Monitoring Address Space was not found. This is a normal situation if the MNAS has not been active since the last IPL. The name portion of the Name/Token pair and the return code from IBM Name/Token Callable Services are shown in the message.
System Action: Processing continues.
User Response: If the return code is 4, none.
STRGI1500I IMS SVC EPA: @@. SVC number: @@.
Severity: Informational
Explanation: This message displays the IMS SVC entry point address and the SVC number.
System Action: Processing continues.
User Response: None.
STRGI1501I Dependent region job name: @@. IMS ID: @@. IMS release: @@. Contr ol region: @@.
Severity: Informational
Explanation: This message displays the job name of an IMS dependent region and the IMS ID with which that region is associated. The IMS release and control region job name are also shown.
System Action: Processing continues.
User Response: None.
STRGI1907i Global Monitoring IMS SRB schedule failed: @@ @@ @@ @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGI1908i Global Monitoring IMS SYEVWENT failed RC= @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM0001I Strobe Monitoring Address Space initialization complete
Severity: Informational
Explanation: The Monitoring Address Space has successfully initialized.
System Action: Processing continues.
User Response: None.
STRGM0002I Setting address space non-swappable
Severity: Informational
Explanation: The MNAS is being set non-swappable.
System Action: None.
User Response: None.
STRGM0003I Strobe Monitoring Address Space termination complete
Severity: Informational
Explanation: The Monitoring Address Space has terminated.
System Action: Processing continues.
User Response: None.
STRGM0006E Unable to load Strobe License Management interface module @@.
Severity: Error
Explanation: Strobe Monitoring attempted to load the the Strobe License Management interface module. The name of the Strobe License Management interface module is shown in the message.
System Action: The Monitoring Address Space terminates.
User Response: Contact Compuware Technical Support.
STRGM0007E An iStrobe license is required for the @@ component of Strobe Monitoring.
Severity: Error
Explanation: The Strobe Monitoring component shown in the message requires an iStrobe license. The verification of licensing for iStrobe indicates that it is not licensed.
System Action: The component is not initialized.
User Response: To avoid these messages set the component shown in the message to NO in the Strobe parameter data set. To obtain a license for iStrobe contact your Compuware sales representative. STRGM0008E An AutoStrobe license is required for Strobe Monitoring.
Severity: Error
Explanation: Strobe Monitoring requires an AutoStrobe license. The verification of licensing for AutoStrobe indicates that it is not licensed.
System Action: The Monitoring Address Space terminates.
User Response: To obtain a license for AutoStrobe contact your Compuware sales representative.
STRGM0009E Strobe Monitoring license verification failed. R/C @@. Reason @@ .
Severity: Error
Explanation: The Monitoring Address Space has attempted verify that Strobe is licensed. That attempt has failed. The return code and reason code from License Management name are shown in the message.
System Action: The Monitoring Address Space terminates.
User Response: Contact Compuware Technical Support.
STRGM0010S Unable to open Strobe Monitoring Address Space log file
Severity: Severe
Explanation: The Monitoring Address Space has attempted to open the message log file. That attempt has failed.
System Action: The Monitoring Address Space terminates.
User Response: Correct the reason for the open failure and restart the Monitoring Address Space.
STRGM0011I Monitoring repository data set name @@
Severity: Informational
Explanation: This message displays the 44 character Monitoring data set name.
System Action: Monitoring initialization continues.
User Response: None.
STRGM0012E Error allocating Monitoring repository data set
Severity: Error
Explanation: The Monitoring task has attempted to dynamically allocate the repository data set. The attempt was not successful.
System Action: Monitoring terminates.
User Response: See the subsequent STR0013I message for details about this error.
STRGM0013E Dynalloc RC=@@. Error=@@. Reason Code=@@
Severity: Error
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: Monitoring processing terminates.
User Response: Using the return code, error code and reason code determine the cause of the dynamic allocation failure.
STRGM0014E Unable to load monitoring module @@
Severity: Error
Explanation: An attempt to load a Strobe monitoring module failed. The name of the module is shown in the message.
System Action: The Monitoring Address Space terminates.
User Response: Ensure that the module shown in the message is in a library available to the Monitoring Address Space.
STRGM0015E Unable to create Default Table (DFT). Return Code=@@
Severity: Error
Explanation: An attempt to build the Strobe default table has failed. The return code is shown in the message.
System Action: The Monitoring Address Space terminates.
User Response: Review the parameter member specified on the PARMLIB DD statement for syntax errors and correct.
STRGM0016E Unable to locate monitoring module @@. BLDL r/c=@@ reason code @ @.
Severity: Error
Explanation: An attempt to locate a Strobe monitoring module failed. The name of the module and the return and reason codes from the BLDL macro instruction are shown in the message.
System Action: The Monitoring Address Space terminates.
User Response: Ensure that the module shown in the message is in a library available to the Monitoring Address Space.
STRGM0017E Error allocating Monitoring criteria data set
Severity: Error
Explanation: The Monitoring task has attempted to dynamically allocate the criteria. The attempt was not successful.
System Action: Monitoring terminates.
User Response: See the subsequent STR0013I message for details about this error.
STRGM0018S Version mismatch between @@ at @@ and @@ at @@
Explanation: Strobe Monitoring successfully loaded the named modules but the versions did not match. The name of the loading module is first and the name of the module loaded not having the same version is listed second in the message.
System Action: The Monitoring Address Space terminates.
User Response: Check the dynamically allocated SYSOUT DD SYS00001 containing the list of Strobe Global Monitor modules for any other modules not at the same version, then verify the library from which they were loaded contains modules that are all at the same version.
STRGM0020I Strobe Monitoring file task initializing
Severity: Informational
Explanation: The Strobe Monitoring file task is initializing.
System Action: Processing continues.
User Response: None.
STRGM0021I Strobe Monitoring file task initialization complete
Severity: Informational
Explanation: The Strobe Monitoring file task has completed initialization.
System Action: Processing continues.
User Response: None.
STRGM0022I Strobe Monitoring file task terminating
Severity: Informational
Explanation: The Strobe Monitoring file task is terminating.
System Action: Processing continues.
User Response: None.
STRGM0024I Strobe Monitoring file task termination complete return code @@
Severity: Informational
Explanation: The Strobe Monitoring file task has terminated. The return code is shown in the message
System Action: Processing continues.
User Response: None.
STRGM0030E Attach for subtask @@ failed. Return code=@@
Severity: Error
Explanation: An attempt to attach a Strobe monitoring task has failed. The name of the program being attached and the return code from the ATTACH macro instruction are shown in the message.
System Action: Processing continues.
User Response: Using the return code shown in the message, determine the cause of the error.
STRGM0031I Subtask @@ has ended. Completion code @@
Severity: Informational
Explanation: A subtask has terminated. The name of the attached program and the completion code are shown in the message.
System Action: The subtask is reattached.
User Response: If the subtask has abended, save any SVC dumps and the log data set from the MNAS, and contact Compuware Technical Support.
STRGM0032I Subtask @@ is being reattached
Severity: Informational
Explanation: A subtask has terminated and is being reattached.
System Action: Processing continues.
User Response: None.
STRGM0033S Subtask @@ has failed and will not be reattached
Severity: Severe
Explanation: A subtask has terminated with a severe error and has indicated that it should not be reattached. The name of the attached program is shown in the message.
System Action: Processing continues.
User Response: Contact Compuware Technical support. The MNAS will have to be restarted in order for the subtask to be reinitialized.
STRGM0034S Subtask @@ has terminated @@ times and will not be reattached
Severity: Severe
Explanation: A subtask has terminated more frequently than allowed. The name of the attached program is shown in the message.
System Action: Processing continues.
User Response: Contact Compuware Technical support. The MNAS will have to be restarted in order for the subtask to be reinitialized.
STRGM0035E Request to restart @@ processing failed. Subtask entry not found
Severity: Error
Explanation: An operator command has been issued to restart a component service task. That request has failed due to an error in an internal control block. The name component is shown in the message.
System Action: Processing continues.
User Response: Contact Compuware Technical support. The MNAS will have to be restarted in order for the subtask to be reinitialized.
STRGM0036E Request to restart @@ processing failed. Subtask is active
Severity: Error
Explanation: An operator command has been issued to restart a component service task. That request has failed because the component task is still active.
System Action: Processing continues.
User Response: Ensure that the task has been terminated before attempting to restart it.
STRGM0037I Subtask @@ has terminated
Severity: Informational
Explanation: A subtask has terminated and has indicated that it may be reattached by the RESTART operator command. The name of the attached program is shown in the message.
System Action: Processing continues.
User Response: If desired, the task may be restarted using the RESTART operator command.
STRGM0038E Request to restart @@ processing failed. Subtask is not eligible for restart
Severity: Error
Explanation: An operator command has been issued to restart a component service task. That request has failed because the component task indicated that it cannot be restarted.
System Action: Processing continues.
User Response: Contact Compuware Technical Support.
STRGM0039E Invalid component name specified
Severity: Error
Explanation: An operator command has been issued to restart a component service task. That request has failed because the component name specified is invalid.
System Action: Processing continues.
User Response: Specify a valid component name. Valid component names are BATCH, CICS, and DATAPUMP.
STRGM0040E Required SMF record type @@ is not being collected
Severity: Error
Explanation: The SMF record type shown in the message is required. The SMFRTEST macro indicated that this record is not being collected.
System Action: Initialization of the MNAS terminates.
User Response: Ensure that the SMF record type shown in the message is being collected at the installation.
STRGM0041E Unable to find @@ SMF exit module @@
Severity: Error
Explanation: An SMF exit module was not found. The name of the SMF exit and the name of the module are shown in the message.
System Action: Initialization of the MNAS terminates.
User Response: Ensure that the module shown in the message is in a load library available to the MNAS.
STRGM0042E Unable to obtain storage for @@ SMF exit module @@. Return code= @@.
Severity: Error
Explanation: The Strobe Monitoring main task attempted to obtain CSA storage in which to load an SMF exit module. The name of the SMF exit, the name of the module and the return code from the STORAGE OBTAIN macro instruction are shown in the message.
System Action: Processing continues.
User Response: Be certain enough stroage is available in the CSA for Strobe Monitoring.
STRGM0043W Unable to @@ SMF exit. Exit=@@. Module=@@. Retc=@@ Reas=@@.
Severity: Warning
Explanation: The Strobe Monitoring main task attempted to define/add/delete an SMF exit. The attempt failed. The exit name, any module name, and the return and reason codes from the CSVDYNEX macro instruction are shown in the message.
System Action: Processing continues.
User Response: This may or may not be an error depending on the request, exit name and/or module name. Be certain any module name shown in the message is in an authorized library available to the MNAS or in a system library.
STRGM0044E Load for module @@ failed. System completion code=@@. Reason co de @@.
Severity: Error
Explanation: The Strobe Monitoring main task attempted to load a module and the load failed. The name of the module, the system completion code and the reason code are shown in the message.
System Action: Processing continues.
User Response: Be certain the Strobe authorized library is available to the MNAS, and that the module shown in the messagae is in the library.
STRGM0045I SMF exit @@ defined @@ has @@ routines, flags=@@.
Severity: Informational
Explanation: The Strobe Monitoring main task is listing all of the exits returned by CSVDYNEX TYPE=ANY.
System Action: Processing continues.
User Response: Informational only but may be requested by Compuware Technical Support for SMF exit issues.
STRGM0046I SMF exit @@ state @@ at @@ loadpt @@ length @@ flags=@@.
Severity: Informational
Explanation: The Strobe Monitoring main task is listing all of the exits returned by CSVDYNEX TYPE=ANY.
System Action: Processing continues.
User Response: Informational only but may be requested by Compuware Technical Support for SMF exit issues.
STRGM0047I SMF EXITS for @@ @@ @@ @@ explicitly defined in SMFPRMxx.
Severity: Informational
Explanation: The Strobe Monitoring main task is summarizing all of the exits returned by CSVDYNEX TYPE=ANY that are of interest to Global Monitoring. The type(s) shown in the message was defined in the SMFPRMxx member in SYS1.PARMLIB with an EXITS parameter.
System Action: Processing continues.
User Response: Informational only but may be requested by Compuware Technical Support for SMF exit issues.
STRGM0048I SMF EXITS at SYS = @@, STC = @@, JES2 = @@, JES3 = @@.
Severity: Informational
Explanation: The Strobe Monitoring main task is summarizing all of the exits returned by CSVDYNEX TYPE=ANY that are of interest to Global Monitoring. The bit values shown represent IEFUSI, IEFACTRT, IEFU83, and IEFU84 as found in SYS1.PARMLIB member SMFPRMxx on an EXITS parameter.
System Action: Processing continues.
User Response: Informational only but may be requested by Compuware Technical Support for SMF exit issues.
STRGM0049E *** Mismatch found for SMF EXITS specified at @@ and @@. ***
Severity: Error
Explanation: The Strobe Monitoring main task has determined that the list of exits on the named SMFPRMxx EXITS do not match. Global Monitor uses CSVDYNEX to ADD our SMF exit routines but SMFPRMxx EXITS parameters can prevent them from being called. This error appears when the number of required EXITS in the SUBSYS is less than the SYS EXITS. SUBSYS is given priority over SYS, which might lead to the exclusion of some necessary EXITS.
System Action: Processing continues.
User Response: Review the STRGM0045 and STRGM0046 messages in the STRDLOG for details, and review the IBM documentation for SMFPRMxx on how the SYS and SUBSYS(xxxx,EXITS(...)) function when SMF calls (or not) the dynamic exit routines.
STRGM0051W Mismatch found for SMF EXITS specified at @@ and @@.
Severity: Warning
Explanation: The StrobeMonitoring main task has determined that the list of exits on the named SMFPRMxx EXITS do not match. Global Monitor uses CSVDYNEX to ADD our SMF exit routines but SMFPRMxx EXITS parameters can prevent them from being called. This warning appears when the number of required EXITS in SYS is less than the SUBSYS EXITS.
System Action: Processing continues.
User Response: Review the STRGM0045 and STRGM0046 messages in the STRDLOG for details, and review the IBM documentation for SMFPRMxx on how the SYS and SUBSYS(xxxx,EXITS(...)) function when SMF calls (or not) the dynamic exit routines.
STRGM0052E Unable to obtain storage for Resource Manager module @@. Return code=@@.
Severity: Error
Explanation: The Strobe Monitoring main task attempted to obtain CSA storage in which to load a resource manager module. the name of the module and the return code from the STORAGE OBTAIN macro instruction are shown in the message.
System Action: MNAS initialization terminates.
User Response: Be certain enough strorage is available in the CSA for Strobe Monitoring.
STRGM0100I STOP command received. The MNAS is shutting down.
Severity: Informational
Explanation: The MVS STOP command was issued to the MNAS. The MNAS has begun the process of termination.
System Action: The MNAS begins shutdown.
User Response: None.
STRGM0101I Posting subtask @@ to shut down.
Severity: Informational
Explanation: The main task has posted a subtask to shut down. The name of the subtask module is shown in the message.
System Action: Processing continues.
User Response: None.
STRGM0102I Waiting for subtask detach.
Severity: Informational
Explanation: The main task has posted subtasks to shut down and is waiting for them to terminate. This is a debugging message for Compuware Technical Support personnel.
System Action: Processing continues.
User Response: None.
STRGM0103I Detaching subtask @@.
Severity: Informational
Explanation: The main task has posted a subtask to shut down. The subtask is now being detached. The name of the subtask module is shown in the message.
System Action: Processing continues.
User Response: None.
STRGM0110E Unsupported MVS console command entered. Supported commands are STOP and MODIFY.
Severity: Error
Explanation: An unsupported MVS console command was entered. The only MVS console commands supported by the MNAS are STOP and MODIFY.
System Action: Processing continues.
User Response: Enter a valid MVS command for the MNAS.
STRGM0111E Invalid MODIFY command @@ entered.
Severity: Error
Explanation: An invalid command was issued to the MNAS using the MVS MODIFY command. The invalid command entered is shown in the message.
System Action: Processing continues.
User Response: Enter a valid MNAS command.
STRGM0112I MODIFY command @@ received. Data=@@. Processing component code=@@ .
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM0113E Unable to obtain storage for the command data buffer. Return code =@@.
Severity: Error
Explanation: The Strobe Monitoring main task attempted to obtain storage for a command data buffer. The storage request failed. The return code from the STORAGE OBTAIN macro instruction is shown in the message.
System Action: Processing continues.
User Response: Be certain that sufficient storage is available the MNAS.
STRGM0114I Debugging messages have been enabled.
Severity: Informational
Explanation: The Strobe Monitoring debugging message have been enabled by the GM_DBUG YES command.
System Action: Processing continues.
User Response: None.
STRGM0115I Debugging messages have been disabled.
Severity: Informational
Explanation: The Strobe Monitoring debugging messages have been disabled by the GM_DBUG NO command.
System Action: Processing continues.
User Response: None.
STRGM0130I Strobe Monitoring utility task initializing
Severity: Informational
Explanation: The Strobe Monitoring utility task is initializing.
System Action: Processing continues.
User Response: None.
STRGM0131I Strobe Monitoring utility task initialization complete
Severity: Informational
Explanation: The Strobe Monitoring utility task has completed initialization.
System Action: Processing continues.
User Response: None.
STRGM0132I @@ Processing work queue.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM0137I Requestor's ASCB address @@ is invalid
Severity: Informational
Explanation: The requestor of services from the Strobe Monitoring utility task passed an ASCB address indicating that it is running in an address space other than the MNAS. The storage at that address was not an ASCB.
System Action: The request is not processed.
User Response: None.
STRGM0138I Strobe Monitoring for utility task termination in progress
Severity: Informational
Explanation: The Strobe Monitoring utility task is terminating.
System Action: Processing continues.
User Response: None.
STRGM0139I Strobe Monitoring utility task termination complete return code @ @
Severity: Informational
Explanation: The Strobe Monitoring utility task has terminated. The return code is shown in the message
System Action: Processing continues.
User Response: None.
STRGM0140I @@ Processing Global Monitoring REFRESH request.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM0141I @@ R/C from criteria builder=@@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM0500E Unable to obtain storage for 4 hour rolling average service. STO RAGE R/C=@@.
Severity: Error
Explanation: Strobe Global Monitoring attempted to obtain storage in order to acquire 4 hour rolling average usage information for the LPAR. The attempt to obtain storage failed with the return code shown in the message.
System Action: Processing continues. Further attempts to acquire the 4 hour rolling average will be disabled.
User Response: Increase the region size for the MNAS.
STRGM0510E Undefined return code from REQLPDAT service. R/C=@@.
Severity: Error
Explanation: Strobe Global Monitoring attempted to acquire 4 hour rolling average usage information for the LPAR. An undefined return code was received from the service. The return code is shown in the message.
System Action: Processing continues. Further attempts to acquire the 4 hour rolling average will be disabled.
User Response: Contact Compuware Technical Support.
STRGM0511I REQLPDAT service: data contained in defined capacity section is n ot valid.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues. Attempts to acquire the 4 hour rolling average will be continued at the next interval.
User Response: None.
STRGM0512I IXCQUERY service: This LPAR is in Monoplex mode.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues. Attempts to acquire the defined capacity section will be disabled.
User Response: None.
STRGM0520I Error sending average CPU service data to data pump R/C=@@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues. Further attempts to acquire the 4 hour rolling average will be disabled.
User Response: Contact Compuware Technical Support.
STRGM0521I Data sent to GM Data Pump: @@ @@ @@ @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM0522I Uncapped: @@. Capped: @@. Interval: @@. Current: @@. 4-Hour avg.: @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM1001I @@
Severity: Informational
Explanation: Informational Message.
System Action: None.
User Response: None.
STRGM1002W @@
Severity: Warning
Explanation: Warning Message.
System Action: None.
User Response: None.
STRGM1003E @@
Severity: Error
Explanation: Error Message.
System Action: None.
User Response: Review message(s) and perform corractive action.
STRGM1004E @@ @@
Severity: Error
Explanation: Error Message.
System Action: None.
User Response: Contact Compuware Technical Support.
STRGM1005W @@ @@
Severity: Warning
Explanation: Warning Message.
System Action: None.
User Response: Review parameter requirements.
STRGM1006E Parmlib processing failed RC @@ RSN @@
Severity: Error
Explanation: Fetch of parmlib parameters failed using the Common Parmlib service.
System Action: Processing terminates.
User Response: Review parameter requirements.
STRGM1007I @@ @@
Severity: Informational
Explanation: Displays Parmlib and Member name used at Address space initialization.
System Action: Processing continues.
User Response: None.
STRGM1309I Name/Token pair @@ not deleted. Name/Token Callable services r/c =@@. MNAS job name: @@.
Severity: Informational
Explanation: The Name/Token pair associated with the Strobe Monitoring Address Space was not deleted. The name portion of the Name/Token pair, the return code from IBM Name/Token Callable Services and the job name of the monitoring address space (MNAS) are shown in the message.
System Action: Processing continues.
User Response: None.
STRGM1320E Name/Token pair @@ not deleted. MNAS @@ is currently active.
Severity: Error
Explanation: The Name/Token pair associated with the Strobe Monitoring Address Space was not deleted. The MNAS associated with the Name/Token pair is currently active. The name portion of the Name/Token pair and the job name of the MNAS are shown in the message.
System Action: Processing continues.
User Response: Shut down the MNAS prior to running the Name/Token pair delete utility.
STRGM1322I Name/Token pair @@ not found. Name/Token Callable Services r/c @ @.
Severity: Informational
Explanation: The Name/Token pair associated with the Strobe Monitoring Address Space was not found. This is a normal situation if the MNAS has not been active since the last IPL. The name portion of the Name/Token pair and the return code from IBM Name/Token Callable Services are shown in the message.
System Action: Processing continues.
User Response: If the return code is 4, none.
STRGM1328I Name/Token pair @@ deleted. MNAS job name: @@.
Severity: Informational
Explanation: The Name/Token pair associated with the Strobe Monitoring Address Space was deleted. The name portion of the Name/Token pair and the job name of the Monitoring address space are shown in the message.
System Action: Processing continues.
User Response: None.
STRGM1960E Dynamic @@ error. Return Code @@ ERROR @@ INFO @@ @@
Severity: Error
Explanation: Dynamic Allocation encountered an error.
System Action: Processing terminates.
User Response: None.
STRGM1964I Criteria record count for system id @@=@@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM1965S Invalid Criteria data set for current release. KEYLEN=@@.
Severity: Severe
Explanation: An invalid criteria data set for the current release of Strobe Global Monitoring. The key length is shown in the message.
System Action: The MNAS terminates.
User Response: Run the migration utility to migrate the criteria data set from a previous release to the format required for the current release, and restart the MNAS.
STRGM1966I @@ @@ @@ @@ @@ @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM1967I @@ @@ @@ @@ @@ @@ @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM1968I @@ @@ @@
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM1969I @@ @@ @@ @@ @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGM1970E Error opening Criteria data set. VSAM r/c=@@. Error=@@. PGM=@@.
Severity: Error
Explanation: An error occurred opening the Strobe Monitoring criteria data set. The VSAM return code and error code are displayed in the message. The name of the program issuing the message is also shown in the message.
System Action: Processing terminates.
User Response: See the job log for the corresponding VSAM messages. If there are no messages, contact Compuware Technical Support.
STRGM1971E Error on Criteria File. VSAM req=@@, VSAM r/c=@@, Feedback=@@. PGM=@@.
Severity: Error
Explanation: An error occurred accessing a Strobe Monitoring criteria data set data record. The VSAM request, return code and feedback code are displayed in the message. The name of the program issuing the message is also shown in the message.
System Action: Processing continues.
User Response: Refer to subsequent message for the criteria record keys.
STRGM1972I Processing SYSIN input command: @@.
Severity: Informational
Explanation: The STRGMCRI utility is processing the SYSIN input shown.
System Action: Processing continues.
User Response: None.
STRGM1973E @@ for @@ request. PGM=@@.
Severity: Error
Explanation: A common VSAM error occurred accessing a Strobe Monitoring criteria data set data record. The VSAM error and criteria utility command are shown in the message. The entire input record is shown in the associated STRGM1972I message.
System Action: Processing continues.
User Response: Resolve the error accordingly.
STRGM1974E Error closing Global Monitoring VSAM dataset, r/c=@@
Severity: Error
Explanation: VSAM dataset was not closed properly.
System Action: Abend.
User Response: None.
STRGM1975E RACF Authorization checking failed. VSAM r/c=@@. Error=@@. PGM=@@.
Severity: Error
Explanation: RACF denied access to the Strobe Monitoring criteria data set. The VSAM return code and error code are displayed in the message. The name of the program issuing the message is also shown in the message.
System Action: Processing terminates.
User Response: See the job log for the corresponding VSAM messages. If there are no messages, contact Compuware Technical Support.
STRGM1976S Invalid Criteria data set for current release. KEYLEN=@@.
Severity: Severe
Explanation: An invalid criteria data set for the current release of Strobe Global Monitoring. The key length is shown in the message.
System Action: The criteria file is not updated.
User Response: Run the migration utility to migrate the criteria data set from a previous release to the format required for the current release.
STRGM1979I Criteria SYSIN data set processing complete, Includes=@@, Exclude s=@@, Programs=@@, Read=@@.
Severity: Informational
Explanation: All of the criteria input records have been processed. The number of valid includes, excludes, and records read are shown.
System Action: Processing terminates.
User Response: If the number of includes and excludes added together do not equal the number of records read, check the GMCRERRS output for invalid SYSIN cards.
STRGM1980E Error opening Repository data set. VSAM r/c=@@. Error=@@. PGM=@@.
Severity: Error
Explanation: An error occurred opening the Strobe Monitoring repository data set. The VSAM return code and error code are displayed in the message. The name of the program issuing the message is also shown in the message.
System Action: Processing continues.
User Response: See the job log from the MNAS for the corresponding VSAM messages. If there are no messages, contact Compuware Technical Support.
STRGM1981E Error writing Repository File data record. VSAM r/c=@@. Feedback= @@. PGM=@@.
Severity: Error
Explanation: An error occurred writing the Strobe Monitoring repository data set data record. The VSAM return code and feedback code are displayed in the message. The name of the program issuing the message is also shown in the message.
System Action: Processing continues.
User Response: See the job log from the MNAS for the corresponding VSAM messages. If there are no messages, contact Compuware Technical Support.
STRGM1982I Repository File Summary successful. DSN=@@.
Severity: Informational
Explanation: The repository file summery report was successfully produced. The name of the repository data set is shown in the message.
System Action: Processing continues.
User Response: None.
STRGM1984E Error encountered during keyword processing, KEYWORD=@@
Severity: Error
Explanation: An invalid criteria keyword was found.
System Action: Criteria processing stops.
User Response: Correct the invalid keyword.
STRGM1985E Error encountered during parameter processing, ERROR=@@
Severity: Error
Explanation: An invalid criteria parameter was found.
System Action: Current criteria skipped.
User Response: Correct the invalid parameter.
STRGM1986I Parameter ignored, PARM=@@
Severity: Informational
Explanation: A criteria parameter was specified but ignored.
System Action: Criteria parameter processing skipped.
User Response: None.
STRGM1990W Unable to add JOB @@ @@ @@ to the MDAT memory object.
Severity: Warning
Explanation: Strobe was attempting to add a tracking entry for the JOB and STEP or JOB and transaction shown.
System Action: Processing continues without tracking the JOB/STEP or JOB/transaction.
User Response: Increase the GM_MAXNUM parameter and restart the MNAS. Valid values are 1 to 999999.
STRGM1991E Error reading Repository File @@ Control record. VSAM r/c=@@. Feedback=@@. PGM=@@.
Severity: Error
Explanation: An error occurred reading the Strobe Monitoring repository data set control record. The Repository file number, and the VSAM return code and feedback code are displayed in the message. The name of the program issuing the message is also shown in the message.
System Action: Processing continues.
User Response: See the job log from the MNAS for the corresponding VSAM messages. If there are no messages, contact Compuware Technical Support.
STRGM1992E Error reading Repository File data record. VSAM r/c=@@. Feedback= @@. PGM=@@.
Severity: Error
Explanation: An error occurred reading the Strobe Monitoring repository data set record. The VSAM return code and feedback code are displayed in the message. The name of the program issuing the message is also shown in the message.
System Action: Processing continues.
User Response: See the job log from the MNAS for the corresponding VSAM messages. If there are no messages, contact Compuware Technical Support.
STRGM1993I MDAT successfully written to the repository data set.
Severity: Informational
Explanation: Strobe monitoring data was successfully written to the repository data set.
System Action: Processing continues.
User Response: None.
STRGM1994I Repository data set successfully switched to @@.
Severity: Informational
Explanation: Strobe monitoring data was successfully switched. The DD name of the new repository is shown in the message.
System Action: Processing continues.
User Response: None.
STRGM1995E Error writing Repository File @@ Control record. VSAM r/c=@@. Feedback=@@. PGM=@@.
Severity: Error
Explanation: An error occurred writing the Strobe Monitoring repository data set control record. The Repository file number, and the VSAM return code and feedback code are displayed in the message. The name of the program issuing the message is also shown in the message.
System Action: Processing continues.
User Response: See the job log from the MNAS for the corresponding VSAM messages. If there are no messages, contact Compuware Technical Support.
STRGM1996E Invalid Global Monitoring Repository data set name prefix specifi ed
Severity: Error
Explanation: The value specified in the GM_REPOSITORY_DSN Strobe parameter must be a valid data set name prefix.
System Action: Global Monitoring terminates.
User Response: Specify a valid data set name prefix on the GM_REPOSITORY_DSN Strobe parameter.
STRGM1997E Global Monitoring Repository data set name greater than 38 charac ters
Severity: Error
Explanation: The Global Monitoring repository data set name is too big.
System Action: Global Monitoring terminates.
User Response: Create a shorter GM_REPOSITORY_DSN parm.
STRGM1998E Global Monitoring Repository data set already in use
Severity: Error
Explanation: The Global Monitoring repository data set can be used by only one Strobe image running on an LPAR.
System Action: Global Monitoring terminates.
User Response: Create a separate repository data set for each Strobe running on an LPAR.
STRGM1999I Global Monitoring repository data set name @@
Severity: Informational
Explanation: This message displays the 44 character Global Monitoring data set name.
System Action: Global Monitoring initialization continues.
User Response: None.
STRGP0001I Strobe Monitoring communication task initialization in progress
Severity: Informational
Explanation: The Strobe Monitoring communication task is initializing.
System Action: Processing continues.
User Response: None.
STRGP0002I Strobe Monitoring communication task initialization complete
Severity: Informational
Explanation: The Strobe Monitoring communication task has completed initialization.
System Action: Processing continues.
User Response: None.
STRGP0003I Strobe Monitoring communication task termination in progress
Severity: Informational
Explanation: The Strobe Monitoring communication task is terminating.
System Action: Processing continues.
User Response: None.
STRGP0004I Strobe Monitoring communication task termination complete return code @@
Severity: Informational
Explanation: The Strobe Monitoring communication task has terminated. The return code is shown in the message
System Action: Processing continues.
User Response: None.
STRGP0005S Strobe Monitoring communication task not started for lack of server parameters
Severity: Severe
Explanation: The Strobe Monitoring communication task is not starting because GM_SMFHOST, GM_SMFIP, GM_TCPNAME, nor GM_SMFPORT were specified in the PARMLIB member used by the MNAS.
System Action: The Strobe Monitoring Communication task terminates.
User Response: None.
STRGP0030E Attach for subtask @@ failed. Return code=@@
Severity: Error
Explanation: An attempt to attach a Strobe monitoring task has failed. The name of the program being attached and the return code from the ATTACH macro instruction are shown in the message.
System Action: Processing continues.
User Response: Using the return code shown in the message, determine the cause of the error.
STRGP0031I Subtask @@ has ended. Completion code @@
Severity: Informational
Explanation: A subtask has terminated. The name of the attached program and the completion code are shown in the message.
System Action: The subtask is reattached.
User Response: If the subtask has abended, save any SVC dumps and the log data set from the MNAS, and contact Compuware Technical Support.
STRGP0032I Subtask @@ is being reattached
Severity: Informational
Explanation: A subtask has terminated and is being reattached.
System Action: Processing continues.
User Response: None.
STRGP0033S Subtask @@ has failed and will not be reattached
Severity: Severe
Explanation: A subtask has terminated with a severe error and has indicated that it should not be reattached. The name of the attached program is shown in the message.
System Action: Processing continues.
User Response: Contact Compuware Technical support. The MNAS will have to be restarted in order for the subtask to be reinitialized.
STRGP0034S Subtask @@ has terminated @@ times and will not be reattached
Severity: Severe
Explanation: A subtask has terminated more frequently than allowed. The name of the attached program is shown in the message.
System Action: Processing continues.
User Response: Contact Compuware Technical support. The MNAS will have to be restarted in order for the subtask to be reinitialized.
STRGP0035E Request to restart @@ processing failed. Subtask entry not found
Severity: Error
Explanation: An operator command has been issued to restart a component service task. That request has failed due to an error in an internal control block. The name component is shown in the message.
System Action: Processing continues.
User Response: Contact Compuware Technical support. The MNAS will have to be restarted in order for the subtask to be reinitialized.
STRGP0036E Request to restart @@ processing failed. Subtask is active
Severity: Error
Explanation: An operator command has been issued to restart a component service task. That request has failed because the component task is still active.
System Action: Processing continues.
User Response: Ensure that the task has been terminated before attempting to restart it.
STRGP0037I Subtask @@ has terminated
Severity: Informational
Explanation: A subtask has terminated and has indicated that it may be reattached by the RESTART operator command. The name of the attached program is shown in the message.
System Action: Processing continues.
User Response: If desired, the task may be restarted using the RESTART operator command.
STRGP0038E Request to restart @@ processing failed. Subtask is not eligible for restart
Severity: Error
Explanation: An operator command has been issued to restart a component service task. That request has failed because the component task indicated that it cannot be restarted.
System Action: Processing continues.
User Response: Contact Compuware Technical Support.
STRGP0050E Load for module @@ failed. System completion code=@@. Reason co de @@.
Severity: Error
Explanation: The Strobe Monitoring communication task attempted to load a module and the load failed. The name of the module, the system completion code and the reason code are shown in the message.
System Action: Processing continues.
User Response: Be certain the Strobe authorized library is available to the MNAS, and that the module shown in the messagae is in the library.
STRGP0051S Unable to obtain storage for @@ data area. Return code=@@.
Severity: Severe
Explanation: The Strobe Monitoring communication task attempted to obtain storage for a data area. The storage request failed. The name of the data area and the return code from the STORAGE OBTAIN macro instruction are shown in the message.
System Action: Processing continues.
User Response: Be certain that sufficient storage is available the MNAS.
STRGP0052S Unable to attach subtask @@. Return code=@@.
Severity: Severe
Explanation: The Strobe Monitoring communication task attempted to attach a service subtask. The attach request failed. The module name of the task being attached and the return code from the ATTACH macro instruction are shown in the message.
System Action: Processing continues.
User Response: Be certain the Strobe authorized library is available to the MNAS, and that the module shown in the messagae is in the library.
STRGP0100I @@ successful.
Severity: Informational
Explanation: The Strobe Monitoring communication task successfully performed the TCP/IP event.
System Action: Processing continues.
User Response: None.
STRGP0101W @@ unsuccessful RETCD=@@ ERRNO=@@
Severity: Warning
Explanation: The Strobe Monitoring communication task unsuccessfully performed the TCP/IP event. Return code and ERRNO are displayed.
System Action: Processing continues.
User Response: Resolve the event using Return code and ERRNO or contact Compuware Support.
STRGP0102I @@ @@ @@
Severity: Informational
Explanation: The Strobe Monitoring communication task informational message.
System Action: Processing continues.
User Response: None.
STRGP0111I Processing MODIFY command @@.
Severity: Informational
Explanation: The Strobe Monitoring data pump task has received a MODIFY command shown in the message.
System Action: Process the command.
User Response: None.
STRGP0112E Invalid MODIFY @@ received: @@.
Severity: Error
Explanation: The Strobe Monitoring data pump task has received an invalid MODIFY command or operand shown in the message.
System Action: Command processing terminates.
User Response: Review Strobe Global Monitoring MODIFY commands and correct.
STRGP0200I Data buffers of length @@ count @@ used @@ unavailable @@.
Severity: Informational
Explanation: The Global Monitoring data buffers of the size listed have been successfully used the number of times shown along with the number of times a buffer was unavailable. Unavailable data buffers indicates data intended for the iStrobe SMF Manager was lost. If this message resulted from a PUMPSTATS command the data is displayed in hex and represents the totals as of the last day. If displayed automatically on the hourly interval the data is displayed in decimal and represents totals for the current day.
System Action: Processing continues, this is informational and may be requested by Compuware Technical Support.
User Response: A high number of unavailable data buffers may indicate a problem communicating to or availability of the SMF Manager in iStrobe. Check the status of the SMF Manager in the iStrobe Configuration.
STRGP0201I TCP buffers to @@ length @@ count @@ used @@ unavailable @@ sent @@.
Severity: Informational
Explanation: The Global Monitoring TCP buffers for the destination shown have been successfully used the number of times shown, along with the number of times a buffer was unavailable, and the number sent. Unavailable data buffers indicates data intended for the destination was lost. If this message resulted from a PUMPSTATS command, the data is displayed in hex and represents the totals as of the last day. If displayed automatically on the hourly interval, the data is displayed in decimal and represents totals for the current day.
System Action: Processing continues; this is informational and may be requested by Compuware Technical Support.
User Response: A high number of unavailable TCP buffers may indicate a problem communicating to or availability of the SMF listener targeted. Check the status of the SMF listener for the destination shown.
STRGP0202I Type @@ SMF records - received @@ processed @@, lost @@.
Severity: Informational
Explanation: The Global Monitoring SMF capture received and processed the numbers of record types shown. Differences in the number received and processed indicate records of no interest were found or a failure to convert to UTF-8 occurred. If this message resulted from a PUMPSTATS command, the data is displayed in hex and represents the totals as of the last day. If displayed automatically on the hourly interval, the data is displayed in decimal and represents totals for the current day.
System Action: Processing continues; this is informational and may be requested by Compuware Technical Support.
User Response: A big difference between numbers received and sent may indicate a problem in the records or what Global Monitor is expecting. Contact Compuware Technical Support for assistance when large discrepancies occur.
STRGP0203I SMF records exceeding 32K and truncated - @@.
Severity: Informational
Explanation: The Global Monitoring SMF processing encountered SMF records that exceeded 32K and were truncated. If this message resulted from a PUMPSTATS command, the data is displayed in hex and represents the totals as of the last day. If displayed automatically on the hourly interval, the data is displayed in decimal and represents totals for the current day.
System Action: Processing continues; this is informational and may be requested by Compuware Technical Support.
User Response: None.
STRGP0800I @@ @@
Severity: Informational
Explanation: Informational message from Strobe SMF Data Processor.
System Action: Processing continues.
User Response: None.
STRGP0801S @@ @@
Severity: Severe
Explanation: Strobe SMF data processor encountered an error.
System Action: Processing terminates.
User Response: Review the message and correct the error. Restart the job. If the error cannot be identified, contact Compuware support.
STRGP0900I @@ Processing work queue.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGP0901I @@ Work Queue element address=@@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGP0902I @@ Processing send request. Desination=@@ @@ @@ @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGP0903I @@ Work queue element returned to queue.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGP0904I @@ Terminating subtask @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRGP0905I @@ Detaching subtask @@.
Severity: Informational
Explanation: This is a debugging message for Compuware support personnel.
System Action: Processing continues.
User Response: None.
STRJP0200I @@ @@ @@ @@ @@ @@ @@ @@
Severity: Informational
Explanation: A debugging message written by the JVMTI agent. Content will vary.
System Action: Processing continues.
User Response: None.
STRJP0300I Topaz Java Strobe interface initialization in progress on TCB @@
Severity: Informational
Explanation: The Topaz Java Strobe interface task is initializing.
System Action: Processing continues.
User Response: None.
STRJP0301I Topaz Java Strobe interface intialization complete on TCB @@
Severity: Informational
Explanation: The Topaz Java Strobe interface task has completed initialization.
System Action: Processing continues.
User Response: None.
STRJP0302I Topaz Java Strobe interface running in @@ @@ ASID @@
Severity: Informational
Explanation: The Topaz Java Strobe interface task has completed initialization and is running in the JOB/STC shown.
System Action: Processing continues.
User Response: None.
STRJP0303I Topaz Java Strobe interface termination in progress on TCB @@
Severity: Informational
Explanation: The Topaz Java Strobe interface task is terminating.
System Action: Processing continues.
User Response: None.
STRJP0304I Topaz Java Strobe interface found a name/token with storage at @@
Severity: Informational
Explanation: The Topaz Java Strobe interface task found an existing name/token pair and the associated JPAI at the address shown.
System Action: Processing continues.
User Response: None.
STRJP0305I Topaz Java Strobe interface created a name/token, JPAI at @@
Severity: Informational
Explanation: The Topaz Java Strobe interface task created a new name/token pair and the associated JPAI is at the address shown.
System Action: Processing continues.
User Response: None.
STRJP0306I Topaz Java Strobe interface returned from NTP delete, r/c=@@
Severity: Informational
Explanation: The Topaz Java Strobe interface task attempted to delete the name/token pair and the return code is shown.
System Action: Processing continues.
User Response: If the return code is not 0 contact Compuware Technical Support.
STRJP0310I Topaz Java Strobe interface releasing JPAI at @@
Severity: Informational
Explanation: The Topaz Java Strobe interface task is releasing the JPAI storage at the address shown.
System Action: Processing continues.
User Response: None.
STRJP0311I Topaz Java Strobe interface leaving JPAI at @@
Severity: Informational
Explanation: The Topaz Java Strobe interface task has been posted to terminate while a Strobe measurement was in progress, so JPAI is being left behind for Strobe to use. If the meaured address space is not terminating it will be retrieved for re-use upon the next agent initialization.
System Action: Processing continues.
User Response: None.
STRJP0320I Topaz Java on TCB @@ posted to @@ for Strobe request @@
Severity: Informational
Explanation: The Topaz Java Strobe task has been posted to process a request from Strobe, and the request number is shown.
System Action: Processing continues.
User Response: None.
STRJP0321I Topaz Java requested to sample @@ times over @@ minutes by Strobe request @@
Severity: Informational
Explanation: The Topaz Java Strobe task has been posted to process a sample from Strobe, and the request number, sample count, and sample time in minutes is shown.
System Action: Processing continues.
User Response: None.
STRJP0322I Topaz Java entering WAIT on TCB @@ last request @@
Severity: Informational
Explanation: The Topaz Java Strobe task is entering a WAIT with the task address and previous Strobe request shown.
System Action: Processing continues.
User Response: None.
STRJP0323I Topaz Java entering WAIT, last request @@ Strobe request @@ Agent r /c=@@
Severity: Informational
Explanation: The Topaz Java Strobe task is entering another WAIT, and the previous Strobe request and request number are shown along with the Agent return code for that request.
System Action: Processing continues.
User Response: None.
STRJP0330I Topaz Java Strobe interface on TCB @@ posted to terminate
Severity: Informational
Explanation: The Topaz Java Strobe task has been posted to terminate at JVM termination.
System Action: Processing continues.
User Response: None.
STRJP0800S Abend @@ occurred in module @@
Severity: Severe
Explanation: The named module experienced an abend during the processing listed. The abend code is also listed. This message is the first in a series of messages.
System Action: Processing terminates.
User Response: Review the JES message log for additional error messages that might have been issued. Refer to subsequent messages for additional information and contact Compuware Technical Support.
STRJP0801I PSW at entry to abend @@-@@ ILC @@ INTC @@
Severity: Informational
Explanation: This message lists the PSW at entry to the abend listed in the previous STRJP0800S message. This message is the second in a series of messages.
System Action: Processing terminates.
User Response: Review the JES message log for additional error messages that might have been issued. Refer to subsequent messages for additional information and contact Compuware Technical Support.
STRJP0802I GPR @@ @@ @@ @@ @@
Severity: Informational
Explanation: This message lists four of sixteen general purpose registers at the time of the abend, and repeats four times.
User Response: Review the JES message log for additional error messages that might have been issued. Refer to subsequent messages for additional information and contact Compuware Technical Support.
STRJP0803I GPR @@ @@ @@ @@ @@
Severity: Informational
Explanation: This message lists four of sixteen 64bit general purpose registers at the time of the abend, and repeats four times. It appears ONLY if the abending module was in AMODE64.
User Response: Review the JES message log for additional error messages that might have been issued. Refer to subsequent messages for additional information and contact Compuware Technical Support.