First time logging in using IBMUSER:
After logging in to TSO/ISPF, everything looks fine. There are about 59 datasets in volume SBSYS1. There are 10 datasets named USER.* in the SBSYS1 volume. These datasets are empty (i.e., no members in these PDS's), but accessible.
Then, we just logoff without performing any other action.
Logging in for the second time:
Then, if we try to login again, we are facing issues due to certain datasets being not accessible. Most of these datasets are starting with USER.* qualifier and ALL of them are in the SBSYS1 volume. These datasets are present in the logon PROC and since these are not available, the ISPPROF, ISPPLIB, SYSPROC, etc. DD allocations fail. After manually allocating these DD (by excluding the USER.* datasets from the concatenation), using alloc command from READY prompt, we are able to login to ISPF. But, we get further issues when creating and accessing datasets in SBSYS1 volume. For example, if we create a dataset named IBMUSER.CNTL in the SBSYS1 volume, then every time we try to access this dataset through option 3.4, we get some error messages in the log indicating that there is some problem in accessing the catalog:
IEC331I 028-002,IBMUSER ,ISPFPROC,IGG0CLEG
IEC332I GETO,GFL ,ICDV,ACD1
Also, datasets like USER.CLIST appear in 3.4 option (DSLIST), but if we try to edit them, we get the message "Data set not found". We can see only 41 datasets under SBSYS1 volume if we just enter the volume name in option 3.4. The USER.* datasets are not appearing. (it appears as if the catalog entry exists, but the VTOC entry is missing). There were 59 of them when we logged in for the first time.
Our understanding of root cause:
The VVDS or VTOC of the volume SBSYS1 gets corrupted once we logoff from IBMUSER TSO/ISPF session the first time. We have tried restoring the system volumes from the installation disks and re-start the z/OS system freshly. Every time, the SBSYS1 volume gets corrupted after the first logon/logoff of IBMUSER. Only thing that happens during the first logon of IBMUSER is the creation of ISPF profile dataset IBMUSER.ISPF.ISPPROF. This dataset gets automatically created in SBSYS1 volume. Somehow, this corrupts the VVDS/VTOC/Catalog entries related to other datasets in that volume. Please note: The master catalog resides on SBSYS1 volume, and the IBMUSER.* datasets get cataloged in the master catalog.
Snapshot of devmap defining the SBSYS1 volume:
name awsckd 0001
device 0a80 3390 3990 /home/z/SBRES1
device 0a81 3390 3990 /home/z/SBRES2
device 0a82 3390 3990 /home/z/SBSYS1
Output of ls -l command to see the properties of SBSYS1 file in Linux:
-rwxr-xr-x. 1 ibmsys1 ibmsys1 2846431232 Oct 17 15:15 /home/z/SBSYS1
Output of awsstat a82 command:
Config file: /home/ibmsys1/aprof11, IOCDS: None, 3270port: 3270
DvNbr S/Ch --Mgr--- Actv Busy
0A82 34 AWSCKD Yes Yes 7487 Cyl-676, Head-0 /home/z/SBSYS1
Can anyone suggest what could be causing the corruption of VTOC/VVDS/Catalog after the first dataset (IBMUSER.ISPF.ISPPROF) is cataloged and IBMUSER logs off? Any advice or suggestion will be of great help for us.