JVM domain trace points
This table lists the JVM domain (SJ) trace points, including the trace ID, the module name, the trace level, the trace type, and the data returned by the trace point. Trace points for the JVM domain take the form "SJ xxxx".
Point ID | Module | Lvl | Type | Data |
---|---|---|---|---|
SJ 0101 | DFHSJDM | SJ 1 | Entry |
|
SJ 0102 | DFHSJDM | SJ 1 | Exit |
|
SJ 0103 | DFHSJDM | Exc | Recovery |
|
SJ 0104 | DFHSJDM | Exc | Invalid format |
|
SJ 0105 | DFHSJDM | Exc | Invalid function |
|
SJ 0106 | DFHSJDM | Exc | Release lock error |
|
SJ 0107 | DFHSJDM | Exc | No storage for sja |
|
SJ 0108 | DFHSJDM | Exc | No storage for stats |
|
SJ 010A | DFHSJDM | Exc | Inquire STGPROT failed |
|
SJ 010B | DFHSJDM | Exc | No storage for SJCB | No data |
SJ 010D | DFHSJDM | Exc | Create bundle directory failed |
|
SJ 0201 | DFHSJIN | SJ 1 | Entry |
|
SJ 0202 | DFHSJIN | SJ 1 | Exit |
|
SJ 0203 | DFHSJIN | Exc | Recovery |
|
SJ 0204 | DFHSJIN | Exc | Invalid format |
|
SJ 0205 | DFHSJIN | Exc | Invalid SJIN function |
|
SJ 0206 | DFHSJIN | Exc | Get lock error |
|
SJ 0207 | DFHSJIN | Exc | Release lock error |
|
SJ 0208 | DFHSJIN | Exc | Invalid DSAT function |
|
SJ 0209 | DFHSJIN | Exc | Internal error |
|
SJ 020E | DFHSJIN | SJ 2 | Running Java version |
|
SJ 030C | DFHSJIS | Exc | Delete all tcbs error |
|
SJ 030D | DFHSJIS | SJ 1 | Setting JVM trace option |
|
SJ 030E | DFHSJIS | SJ 1 | Retrieved JVM trace option |
|
SJ 0401 | DFHSJST | SJ 1 | Entry |
|
SJ 0402 | DFHSJST | SJ 1 | Exit |
|
SJ 0403 | DFHSJST | Exc | Recovery |
|
SJ 0404 | DFHSJST | Exc | Invalid format |
|
SJ 0405 | DFHSJST | Exc | Invalid function |
|
SJ 0406 | DFHSJST | Exc | Invalid parms |
|
SJ 0407 | DFHSJST | Exc | Get exc lock error |
|
SJ 0408 | DFHSJST | Exc | Release exc lock error |
|
SJ 0409 | DFHSJST | Exc | Get shr lock error |
|
SJ 0410 | DFHSJST | Exc | Release shr lock error |
|
SJ 0411 | DFHSJST | Exc | Recovery release lock error |
|
SJ 0412 | DFHSJST | Exc | Unknown KE error code |
|
SJ 0501 | DFHSJL | Exc | Attach failed |
|
SJ 0502 | DFHSJL | Exc | Listen failed |
|
SJ 0601 | DFHSJNT | SJ 1 | Entry |
|
SJ 0602 | DFHSJNT | SJ 1 | Exit |
|
SJ 0603 | DFHSJNT | Exc | Invalid format |
|
SJ 0604 | DFHSJNT | Exc | Invalid function |
|
SJ 0605 | DFHSJNT | Exc | Recovery |
|
SJ 0901 | DFHSJSM | SJ 1 | Entry |
|
SJ 0902 | DFHSJSM | SJ 1 | Exit |
|
SJ 0903 | DFHSJSM | Exc | Invalid format |
|
SJ 0904 | DFHSJSM | Exc | Invalid function |
|
SJ 0905 | DFHSJSM | Exc | Recovery |
|
SJ 0A01 | DFHSJDS | SJ 1 | Entry |
|
SJ 0A02 | DFHSJDS | SJ 1 | Exit |
|
SJ 0A03 | DFHSJDS | Exc | Recovery |
|
SJ 0A04 | DFHSJDS | Exc | Invalid format |
|
SJ 0A05 | DFHSJDS | Exc | Invalid function |
|
SJ 0A06 | DFHSJDS | Exc | Internal error |
|
SJ 0A07 | DFHSJDS | Exc | Exception data |
|
SJ 0B01 | DFHSJJS | SJ 1 | Entry |
|
SJ 0B02 | DFHSJJS | SJ 1 | Exit |
|
SJ 0B03 | DFHSJJS | Exc | Invalid format |
|
SJ 0B04 | DFHSJJS | Exc | Invalid function |
|
SJ 0B05 | DFHSJJS | Exc | Recovery entered |
|
SJ 0B07 | DFHSJJS | Exc | Internal error |
|
SJ 0B08 | DFHSJJS | SJ 2 | Language Environment runtime options |
|
SJ 0B09 | DFHSJJS | Exc | Getmain error |
|
SJ 0B0A | DFHSJJS | Exc | Attach error |
|
SJ 0B0B | DFHSJJS | Exc | URI error |
|
SJ 0B0C | DFHSJJS | Exc | URI map error |
|
SJ 0B0D | DFHSJJS | SJ 2 | Attach parameters |
|
SJ 0B0E | DFHSJJS | Exc | Attach disabled |
|
SJ 0B0F | DFHSJJS | Exc | Attach not found |
|
SJ 0B10 | DFHSJJS | SJ 2 | JVM server request |
|
SJ 0B11 | DFHSJJS | Exc | URIMAP disabled error |
|
SJ 0B12 | DFHSJJS | Exc | URIMAP scheme error |
|
SJ 0B13 | DFHSJJS | Exc | Inquire bundle failed |
|
SJ 0B14 | DFHSJJS | SJ 2 | TCB deleted from JVM server |
|
SJ 0B15 | DFHSJJS | Exc | URI map located is UNAVAILABLE |
|
SJ 0B17 | DFHSJJS | Exc | Profiledir too long |
|
SJ 0B22 | DFHSJJS | Exc | Statistics collection error |
|
SJ 0B28 | DFHSJJS | Exc | JVM server not found |
|
SJ 0C01 | DFHSJTH | SJ 1 | Entry |
|
SJ 0C02 | DFHSJTH | SJ 1 | Exit |
|
SJ 0C03 | DFHSJTH | Exc | Invalid format |
|
SJ 0C04 | DFHSJTH | Exc | Invalid function |
|
SJ 0C05 | DFHSJTH | Exc | Recovered entered |
|
SJ 0C06 | DFHSJTH | Exc | Failure |
|
SJ 0C07 | DFHSJTH | Exc | Unknown kernel error |
|
SJ 0C08 | DFHSJTH | Exc | Lock error |
|
SJ 0C09 | DFHSJTH | Exc | Unlock error |
|
SJ 0C0A | DFHSJTH | Exc | Return from JNI |
|
SJ 0C0B | DFHSJTH | Exc | Native entry |
|
SJ 0C0C | DFHSJTH | SJ 2 | Thread allocated to JVM server |
|
SJ 0C0D | DFHSJTH | SJ 2 | Wait for thread allocation |
|
SJ 0C0E | DFHSJTH | SJ 2 | Thread deallocated from JVM server |
|
SJ 0D01 | DFHSJSC | SJ 2 | Native entry |
|
SJ 0D02 | DFHSJSC | SJ 2 | Native exit |
|
SJ 0D03 | DFHSJSC | SJ 1 | Attach thread failed |
|
SJ 0D04 | DFHSJSC | SJ 1 | Class not found |
|
SJ 0D05 | DFHSJSC | SJ 1 | Method not found |
|
SJ 0D06 | DFHSJSC | SJ 1 | JVM threw exception |
|
SJ 0D07 | DFHSJSC | SJ 1 | Detach thread failed |
|
SJ 0D10 | DFHSJSC | SJ 2 | Entry |
|
SJ 0D11 | DFHSJSC | SJ 2 | Exit |
|
SJ 0D12 | DFHSJSC | SJ 2 | Event |
|
SJ 0D13 | DFHSJSC | SJ 2 | Event |
|
SJ 0D14 | DFHSJSC | SJ 2 | Event |
|
SJ 0D20 | DFHSJSC | Exc | JVM server not configured for Liberty profile |
|
SJ 0D21 | DFHSJSC | Exc | Unable to open file |
|
SJ 0D22 | DFHSJSC | Exc | File read failed |
|
SJ 0D23 | DFHSJSC | Exc | File installedApps.xml is corrupt |
|
SJ 0D24 | DFHSJSC | Exc | Unable to obtain file status |
|
SJ 0D25 | DFHSJSC | Exc | WAR bundle is already installed |
|
SJ 0D26 | DFHSJSC | Exc | Environment variable is not set |
|
SJ 0D27 | DFHSJSC | Exc | Java property is not set |
|
SJ 0D28 | DFHSJSC | Exc | File write failed |
|
SJ 0E01 | DFHSJRL | SJ 1 | Entry |
If function = CREATE
If function = INQUIRE_BY_NAME
|
SJ 0E02 | DFHSJRL | SJ 1 | Exit |
If function = CREATE
|
SJ 0E03 | DFHSJRL | Exc | Invalid format |
|
SJ 0E04 | DFHSJRL | Exc | Invalid function |
|
SJ 0E05 | DFHSJRL | Exc | Recovery |
|
SJ 0E07 | DFHSJRL | Exc | Unknown KE error code |
|
SJ 0E0A | DFHSJRL | Exc | Getmain for XML failed |
|
SJ 0E0B | DFHSJRL | Exc | Getmain for bundle part failed |
|
SJ 0E0C | DFHSJRL | Exc | UTF-8 to EBCDIC conversion failed |
|
SJ 0E0D | DFHSJRL | Exc | Bad XML data |
|
SJ 0E0E | DFHSJRL | Exc | Define OSGi program failed |
|
SJ 0E0F | DFHSJRL | Exc | Acquire OSGi program failed |
|
SJ 0E10 | DFHSJRL | Exc | Create channel failed |
|
SJ 0E11 | DFHSJRL | Exc | Bundle installation failed |
|
SJ 0E12 | DFHSJRL | Exc | Bundle failed to enable |
|
SJ 0E13 | DFHSJRL | Exc | Get versionRange container failed |
|
SJ 0E14 | DFHSJRL | Exc | Attempt to find highest semantic version of bundle failed |
|
SJ 0E15 | DFHSJRL | Exc | Phasein of new version of a bundle failed |
|
SJ 0E17 | DFHSJRL | Exc | JVMSERVER not enabled |
|
SJ 0E18 | DFHSJRL | Exc | Getmain of useful storage failed |
|
SJ 0E30 | DFHSJRL | SJ 2 | Parsed XML |
|
SJ 0E31 | DFHSJRL | SJ 1 | OSGi bundle information |
|
SJ 0E32 | DFHSJRL | SJ 1 | WAR bundle information |
|
SJ 0E33 | DFHSJRL | SJ 1 | EBA bundle information |
|
SJ 0E34 | DFHSJRL | SJ 1 | EAR bundle information |
|
SJ 0E35 | DFHSJRL | SJ1 | OSGi bundle information |
|
SJ 0E36 | DFHSJRL | SJ2 | Highest semantic version found |
|
SJ 0E41 | DFHSJRL | Exc | Duplicate OSGi bundle |
|
SJ 0E61 | DFHSJBD | SJ 1 | Entry |
|
SJ 0E62 | DFHSJBD | SJ 1 | Exit |
|
SJ 0E63 | DFHSJBD | Exc | Invalid format |
|
SJ 0E64 | DFHSJBD | Exc | Invalid function |
|
SJ 0E65 | DFHSJBD | Exc | Recovery |
|
SJ 0E66 | DFHSJBD | SJ2 | New SJBUN allocated |
|
SJ 0F01 | DFHSJXM | SJ1 | Entry |
|
SJ 0F02 | DFHSJXM | SJ1 | Exit |
|
SJ 0F03 | DFHSJXM | Exc | Recovery |
|
SJ 0F04 | DFHSJXM | Exc | Invalid format |
|
SJ 0F05 | DFHSJXM | Exc | Invalid function |
|
SJ 0F06 | DFHSJXM | Exc | Unexpected recovery bit |
|
SJ 4D00 | DFHAPJVMT | Exc | DFHAPJVMT plug-in failed |
|
SJ 4D01 1 | DFHAPJVMT | SJ 29–322 | JVM trace point3, 4 |
|
SJ 4D02 1 | DFHAPJVMT | SJ 29–322 | JVM trace point3, 4 |
|
Note:
- Every JVM trace entry that is produced by any JVM in the CICS® region generates an instance of either the SJ 4D01 or the SJ 4D02 CICS trace entry. SJ 4D02 is the trace point used for formatted JVM trace information. SJ 4D01 is used for any JVM trace points that cannot be formatted by CICS.
- The JVM trace point ID begins at offset 6 in the JVM trace point data.
The JVM trace point ID is in the format TPID_componentId.number, where componentId is the name of the JVM component that issued the trace point, and number is the unique identifying number within the component. This format is variable length.
- The items preceding the JVM trace point ID in the JVM trace point data are:
ThreadID
(<P
or*
>,<JNI ENV Pointer
>), where:P
indicates that the thread is prime (CICS TCB), and*
indicates that the thread is other (offset 4 in data)JNI ENV Pointer
is a unique address representing the thread (offset 0 - 3 in data).