When attempting to setup MTCA with the ESM microservice using ACF2 the ESM microservice service indicates a successful validation:
ACF01137 uuuuuuu LAST SYSTEM ACCESS 06.56-02/11/20 FROM STCINRDR
However, the browser flashes for a brief moment with the MTCA home screen and the following messages appear in the MTCA TOMCAT server log:
12:43:37.548 .https-jsse-nio-8443-exec-11. DEBUG c.c.m.c.OpsAuthenticationProvider - authenticate: ESM server info (example.com, 7100, TLS-ESM)
12:43:38.191 .https-jsse-nio-8443-exec-11. DEBUG c.c.m.c.OpsAuthenticationProvider - authenticate: Login response = {"api
Message":{"metadata":{"messageVersion":"1","messageTime":"2020-02-11T12:43:38.138Z","resourceTypes":."login".},"data":{"login":.{"to
ken":"5BFv9-w","domain":"*","
userId":"uuuuuuu","applicationResourceClass":"IBMFAC","applicationResourceName":"OP$MVS.OPSAOF","applicationResourceAccess":"READ","
creation":1581425018169,"expiration":1581430018169}.},"messages":..}}
2:43:38.420 .https-jsse-nio-8443-exec-11. DEBUG c.c.m.c.PlatformController - GET /api/user
12:43:42.215 .https-jsse-nio-8443-exec-20. DEBUG c.c.m.c.RulesController - rulesList: GET /api/rules/list
12:43:42.215 .https-jsse-nio-8443-exec-20. DEBUG c.c.m.c.RulesController - rulesList: parameters = , , , , , ,
12:43:42.215 .https-jsse-nio-8443-exec-20. INFO c.c.m.c.RulesController - rulesList: Access rejected, initialization not
complete (uuuuuuu)
The log messages would indicate lack of access to this resource, but according to following rules the userid has the required permissions:
RESOURCE RULE OP$MVS STORED BY uuuuuuu ON mm/dd/yy
$KEY(OP$MVS) TYPE(FAC) ROLESET
OPSAOF USER(uuuuuuu) SERVICE(READ) ALLOW
OPSAOF USER(uuuuuuu) SERVICE(READ,UPDATE) ALLOW
OPSPARM USER(uuuuuuu) SERVICE(READ,UPDATE) ALLOW
OPSPARM USER(uuuuuuu) SERVICE(READ,UPDATE) ALLOW
TOTAL RECORD LENGTH= 339 BYTES, 1 PERCENT UTILIZED
In MTCA log, there is message:
ERROR c.c.m.c.DiscoveryController - DiscoveryControllerWorker.run: A fatal error occurred during database initalization. java.lang.Exception: org.h2.jdbc.J dbcSQLException: File corrupted while reading record: null. Possible solution: use the recovery tool
OPS/MVS
Component : MAINFRAME TEAM CENTER AUTOMATION
The MTC-A database became corrupted.
Deleting the database and then restarting MTCA, which recreates the database maybe a workaround.
It's recommended to open a case with the OPS/MVS support team.