Topology logon hangs with SIO increase and requires task restart of started task

Products

• Topology

Issue/Introduction

Mainframe Topology users experience a hang during the logon process, often accompanied by a significant increase in System Input/Output (SIO) activity for the Topology started task.

Users are able to reach the logon screen, but the session freezes or turns black after entering credentials. The Topology joblog contains the following error: 

####-##-## 11:20:54.880 Uhttps-jsse-nio-pppp-exec-41~ ERROR com.broadcom.restapi.sdk.repository.FolderSynchronization - Cannot lock folder tmp                                                                                                                   

Environment

• Mainframe Topology
• z/OS

Cause

The tmp directory in the USS deployment path (defined by the DEPLOY_PATH variable in the TPLSCONF member) contains a file used to store invalidated authentication tokens. If this file becomes locked or inaccessible to the User ID running the Topology API STC, the service cannot complete the authentication handshake.

Resolution

To resolve the hang, recreate the temporary directory:

1. Stop the Topology API started task (TPLSPROC).
2. Navigate to the DEPLOY_PATH specified in the TPLSCONF member via USS.
3. Delete the tmp directory and all its contents.
4. Verify that the User ID assigned to the started task has full read, write, and execute permissions for the deployment path.
5. Restart the Topology API started task.

The service recreates the tmp directory with the correct access privileges upon startup.