Strobe Programmed Terminations
Under certain circumstances, the measurement task can terminate with a programmed abnormal termination. User programs are not affected.
When you receive any of the abnormal termination (ABEND) codes listed below, note the ABEND code number and inform the Strobe system programmer of the problem.
ABEND Code | Reason for the Measurement Task ABEND |
|---|---|
0000 | Strobe issued an ABEND during measurement initialization. |
0001 | Strobe issued an ABEND request to the measurement task. |
0002-4 | The measurement task detected an internal error in the ADB chain. The reason code identifies the specific location. |
0002-8 | The measurement task detected an internal error in the ADB chain. The reason code identifies the specific location. |
0002-12 | The measurement task detected an internal error in the ADB chain. The reason code identifies the specific location. |
0002-16 | The measurement task detected an internal error in the ADB chain. The reason code identifies the specific location. |
0003 | The measurement task detected an internal error in the ADB chain. |
0100 | The release level of the session management facility is earlier than the release level of the measurement task. |
0101 | The release level of the measurement task and the release level of the session management facility are incompatible. |
0103 | The user attempted to invoke the measurement facility through STRBVPH1. |
0322-10 | The measurement task used an excessive amount of time; there may be a loop in the program. The reason code indicates that the timeout occurred during measurement initialization and sample file open. |
0322-20 | The measurement task used an excessive amount of time; there may be a loop in the program. The reason code indicates that the timeout occurred during sampling. |
0322-30 | The measurement task used an excessive amount of time; there may be a loop in the program. The reason code indicates that the timeout occurred during measurement termination and sample file close. |
0522 | The measurement task used an excessive amount of elapsed time; there may be a hang in the program |
The session management facility also issues ABEND codes. Conditions that can cause these abnormal terminations include:
- A program that was not part of the Strobe system attempted to use the session management facility.
- The program being measured damages the measurement task or its working storage (both located in the target program’s address space).
- The operating system malfunctions.
The session management facility uses ABEND codes for all programmed ABENDs and shows the ABEND code with the termination message. These codes take the form 6xx. The reason code is represented as the hexadecimal equivalent of the value.
ABEND and Reason Code | Reason for the Session Management Facility ABEND |
|---|---|
610-0 | An ENV test command was issued. |
610-1 | ISPF and session requester releases are incompatible. |
610-2 | Call to session requester is invalid. |
610-4 | BLDL failed for the module. |
610-5 | Strobe could not locate the module. |
610-6 | Strobe detected an internal error while processing a parameter list. |
610-7 | Strobe detected an internal error while processing a request. |
610-8 | Strobe detected an internal error while processing an ENV REMOVE request. |
610-9 | Open failed for the SYSQUEUE dataset. |
610-F | Strobe experienced a failure issuing the SVCUPDTE service or ENQ service. |
610-10 | Strobe detected an internal error while searching an SVC table. |
610-11 | Strobe detected an internal error in parser; the reason code identifies the specific location of the error. |
610-12 | Strobe detected an internal error in parser; the reason code identifies the specific location of the error. |
610-14 | Strobe detected an internal error in parser; the reason code identifies the specific location of the error. |
610-18 | System service QEDIT failed during started task initialization. |
611-0 | Session requester terminated because the operator pressed the ATTN key. |
611-1 | Session requester terminated as part of session manager ABEND processing. |
620-1 | Versions of STRBCPH0 and STRBCLPA are incompatible. |
620-2 | Attach of user’s program failed. |
620-3 | System service BLDL failed. |
620-4 | Strobe detected an internal error; the reason code gives the specific location of the error |
620-5 | Strobe detected a serialization error during measurement task initialization. |
620-6 | Strobe attempted to attach the session requester as a subtask and this attach failed. |
630-0 | Versions of STRBCLPA and STRBCRB are incompatible. |
650-0 | An invalid entry code passed to the Strobe SVC, or the Strobe SVC was called by an unauthorized user. |
650-1 | Invalid SRE address passed to the Strobe SVC. |
650-2 | Invalid parameter passed to the Strobe SVC message function. |
650-3 | Cross-memory post failed during a SEND command while the session manager was trying to post the measurement task. |
650-4 | Cross-memory post failed during POST processing while trying to post the session manager or the session requester. |
650-5 | Cross-memory post failed during end-of-task exit processing while the session manager or the session requester was trying to post STRBCSM or STRBCSR. |
650-6 | SVC ABEND, Strobe detected an internal error in DELETE function. |
650-7 | SVC ABEND, Strobe detected an internal error in SEND function. |
650-8 | SVC ABEND, Strobe detected an internal error in SEND function. |
650-9 | SVC ABEND, Strobe detected an internal error in SEND function. |
650-A | SVC ABEND, Strobe detected an internal error in SEND function. |
650-B | STRBCXAC error calling exit |
650-C | Internal error building MSCB |
650-D | Strobe detected an invalid OUCB. |
650-E | Invalid parameter passed to Strobe SVC sign-on function. |
650-F | Invalid parameter passed to Strobe SVC sign-on function. |
650-10 | Strobe detected an internal error in SWAREQ processing. |
660-0 | SRB ABEND, cross-memory post failed. |
670-0 | IRB ABEND, cross-memory post failed. |
700-8 | Sysevent transwrap failed. |
700-12 | Cross-memory post of session manager failed |
700-22 | Attach of AutoStrobe subtask failed |
701-1 | Timer failure |
701-3 | AutoStrobe work area unavailable. |
777-2 | Cross-memory post of Measurement Services Address Space (MSAS) failed. |
778 | Diagnostic dump issued to obtain the current storage when Strobe has detected environmental issues concerning inter-address space communication with the MSAS address space. |
Table 1 lists Strobe SSAREQ return codes, reason codes, and meaning/action for each.
Table 1. SSAREQ Return Codes and Reason Codes
Return Codes | Reason Codes | Meaning/Action |
|---|---|---|
IfiRcOk EQU | X'00' | Rc00 Normal |
IfiRcWrn EQU | X'04' | Rc04 Warning |
IfiRwxxx EQU | X'ff' | wRsn model |
IfiRcErr EQU | X'08' | Rc08 Error |
IfiReFnc EQU | X'04' 04 | eRsn Function code invalid/unsupp. |
IfiReIns EQU | X'08' 08 | eRsn No Ift slots avail |
IfiReInf EQU | X'0C' 12 | eRsn No match on IftAs |
IfiReInA EQU | X'10' 16 | eRsn Subtask Attach failed |
IfiReCmd EQU | X'14' 20 | eRsn #IfiCCmd invalid |
IfiReSal EQU | X'18' 24 | eRsn SALSAWT invalid |
IfiRcLog EQU | X'0C' | Rc12 Logic error |
IfiRlSno EQU | X'04' 04 | nRsn FIFA/M Internal ShowNotOccur |
IfiRlRat EQU | X'08' 08 | nRsn FIFA 1st call must be #IfiCtIi |
IfiRlxxx EQU | X'ff' | lRsn model |
IfiRcEnv EQU | X'10' | Rc16 Environment |
IfiRnIpr EQU | X'04' 04 | nRsn INPUT PARM AREA NOT ACCESABLE |
IfiRnStg EQU | X'08' 08 | nRsn STORAGE OBTAIN FAILED TOKEN AREA |
IfiRn0C EQU | X'0C' 12 | nRsn STORAGE OBTAIN FAILED LCL BFR |
IfiRn10 EQU | X'10' 16 | nRsn SSA NO Db2 Act (SALSIB=0) |
IfiRn14 EQU | X'14' 20 | nRsn SSA NO Db2 Act (SIBDACC=0) |
IfiRnDWL EQU | X'18' 24 | nRsn LOAD fail Db2 RRSAF/CAF Intf |
IfiRnDW2 EQU | X'1C' 28 | nRsn LOAD fail Db2 WLIR/WLI2 Intf |
IfiRn20 EQU | X'20' 32 | nRsn Db2 CAF CONNECT FAILURE |
IfiRn24 EQU | X'24' 36 | nRsn Db2 CAF OPEN FAILURE |
IfiRn28 EQU | X'28' 40 | nRsn UNABLE TO UPDATE SSA SIB |
IfiRn2C EQU | X'2C' 44 | nRsn INTERNAL IFI BUFFER NOT PRESENT |
IfiRn30 EQU | X'30' 48 | nRsn INVALID DAB CONTROL BLOCK |
IfiRnIrf EQU | X'34' 52 | nRsn IFI READS FAILURE |
IfiRnNiu EQU | X'38' 56 | nRsn IftU zero |
IfiRnRid EQU | X'40' 64 | nRsn RRSAF Identify err |
IfiRnRsn EQU | X'44' 68 | nRsn RRSAF Signon Err |
IfiRnWdt EQU | X'48' 72 | nRsn WLI Dis Trace err |
IfiRnWst EQU | X'4C' 76 | nRsn WLI Sta Trace err |
IfiRnAbn EQU | X'50' 80 | nRsn FIF* SubT unexpected term |
IfiRnEnq EQU | X'54' 84 | nRsn FIF0 Enq failed |
IfiRnDeq EQU | X'58' 88 | nRsn FIF0 Deq failed |
IfiRnSoq EQU | X'5C' 92 | nRsn FIF0 Stor Obt DsEndDs failed |
IfiRnSrq EQU | X'60' 96 | nRsn FIF0 Stor Rel DsEndDs failed |
IfiRnSri EQU | X'64' 100 | nRsn FIF0 Stor Rel #IFI failed |
IfiRnSaw EQU | X'68' 104 | nRsn FIFA SAW failed validity ck |
IfiRnHot EQU | X'F00' | nRsn HotReason-testing e.g. dcb open |