SYSVIEW for APM - STC SYSVAPPS produced unexpected JVM datasets during system problem
Article ID: 266014
Updated On:
Products
Issue/Introduction
This is related to SYSVIEW for APM.
Our Storage Management team just alerted me to a number of large, uncatalogued SYSVAPPS datasets that were created during serious auxiliary storage problems on that system. Not only are these not catalogued, but they are using the STC name (SYSVAPPS) as their high level qualifier. Since this is not defined as an alias, these datasets got cataloged in the master catalog.
Can you shed any light on these? Perhaps they were created directly by JVM and not by SYSVAPPS itself?
Enter "/" to select action Tracks %Used XT
--------------------------------------------------------------------
SYSVAPPS.JVM.SYSVAPPS.D230423.T040833.X001 47733 100 4
SYSVAPPS.JVM.SYSVAPPS.D230423.T040847.X001 47771 100 4
SYSVAPPS.JVM.SYSVAPPS.D230423.T041320.X001 47775 100 4
SYSVAPPS.JVM.SYSVAPPS.D230423.T045347.X001 41438 100 4
SYSVAPPS.JVM.SYSVAPPS.D230423.T050615.X001 41544 100 4
Since SYSVAPPS is not defined as a high level qualifier it won't let anyone open them.
Here are the DCB attributes of the datasets from ISPF 3.2:
Organization . . . : PS
Record format . . . : FBS
Record length . . . : 4160
Block size . . . . : 24960
1st extent tracks . : 12603
Secondary tracks . : 12603
Resolution
In the IBM JVM doc link below there is an option that can be used. Note that for system dumps, the SUBOPTION name will be DSN instead of FILE.
The place to specify -Xdump:system:dsn=MY.DUMP.DATASET for SYSVAPPS is in the sysvapps_runtime_dir/config/stdenv.cfg file. There is a section near the bottom where you can specify IJO options.
Add a new line: IJO="$IJO -Xdump:system:dsn=SYSU.SYSVAPPS.JVM.DUMP", so that it looks similar to the following:
#
IJO="-Xms16m -Xmx512m -Xquickstart "
IJO="$IJO -Xdump:system:dsn=SYSU.SYSVAPPS.JVM.DUMP"
#
The IBM documentation also points to some predefined tokens you can include in the data set name as well, similar to JCL symbols.
Feedback
