Mainframe Topology API Server did not come up full.
Article ID: 251047
Updated On:
Products
Issue/Introduction
One of the possible reasons why the Mainframe Topology API Server did not come up full could be the existence of a temporary file with the name LOCKED. After checking USS temporary dir user had a question regarding the file with the name LOCKED. The file was automatically created after a few executions of the Mainframe topology job - TPLSARUN. What is the purpose of that file?
Environment
Release : 14.0
Component : TOPOLOGY
Cause
Temporary file wasn't deleted.
Resolution
This file is part of ZOWE SDK. It's a synchronization file that manages access to the folder that is used for saving info about jwt logout tokens. After the information about the new token is saved it might disappear/be deleted. A possible reason why it is still present could be some threads that want to read that file to verify the jwt token are waiting when it will be freed. Suggestion will be to delete that file manually.
Feedback
