Many sessions to a single application are hanging with PCINIT status.
When VTAM builds or receives the CINIT, VTAM then calls the applications logon exit. At this point, the session status is put into a state of PCINIT. The application needs to acknowledge to VTAM that the Logon exit was driven by issuing an OPNDST or CLSDST macro. Until the application acknowledges the logon exit being driven, the session will hang in the PCINIT state.
Diagnosing the problem
Display the LU with a D NET,ID=lu_name,E to display the session status.
Resolving the problem
The application needs to be investigated to see why it is not responding to the logon exit being driven by VTAM.