Client is getting "IKJ56231I DATA SET <name> NOT ALLOCATED, SYSTEM OR INSTALLATION ERROR+"
A new person is trying to use MAT. Here is what the MAT joblog shows:
TN0495I Profile: C91677A CA MAT ECSA packet initialized at 25AA1000
TN0101I Profile: C91677A now monitoring JOB: C91677A PGM: DFSRRC00
TN0102I Profile: C91677A USERID: C91677 Data set: TRT.C91677.C91677A.D2017019.T1053247
TN0104I Profile: C91677A Initial Observation rate: 0010, Observations: 006000, Elapsed: 00060
IKJ56231I DATA SET TRT.C91677.C91677A.D2017019.T1053247 NOT ALLOCATED, SYSTEM OR INSTALLATION ERROR+
IKJ56231I CATALOG I/O ERROR
TN0496I Profile: C91677A CA MAT IMS 13.1 packet initialized (JOB14166,01) at 7F63F9E0
TN0496I Profile: C91677A CA MAT DB2 A1 packet initialized (JOB14166) at 25D1E000 for IDB2
TN8090I Profile: C91677A Monitoring completed for JOB: C91677A
TN8091I Profile: C91677A Monitor counters: 000008/000012/000000/000000/000000
TN0106I Profile: C91677A Final Observation rate: 0010, Observations: 006000, Elapsed: 00060
TN0108I Profile: C91677A ECSA Used: 289352 (bytes); SRB CPU time: 00:00:00.008
I couldn't find any documentation where IKJ56231I had a secondary message of CATALOG I/O ERROR.
We use Top Secret for our security. Some time ago we had errors where TRT was removed from the ALL record and I thought that has been fixed. Even though there are no TSS messages during the time this happened we ran a TSS violations report and found:
01/19/17 10:53:24 MVS1 C91677 CAMAT 99F 01 TNMXWTR CREATE
01/19/17 10:53:24 MVS1 C91677 CAMAT 99F 02 TNMXWTR SCRATCH
both with violation code *08*-65 that means ...
65 = DATASET NOT ACCESSIBLE -
66 = ACCESS NOT GRANTED TO DATASET
We are guessing that maybe the user doesn't have the security to update the user catalog that the TRT alias is in. We are looking for confirmation.
The ALL record has the following permit:
XA DATASET = TRT.TEMP. OWNER(STANDT )
ACCESS = UPDATE,CREATE
This is the only TRT permit in the ALL record.
The failing user is getting a violation on dataset TRT.C91677.C91677A.xxx, which is not a match for TRT.TEMP. The new user does not have any matching permits (including masked permits) on his acid or any profiles attached, so the violation is valid. You need to find out why the new user is not using TRT.TEMP.xxx.