We are having intermittent issues related to our OPS/MVS EPIs REXX EXECs.
Since Sunday morning it was noticed that sometimes, the EXECs are failing with the same TSO message:
INVALID USERID OR PASSWORD SPECIFIED.
The z/OS systems were these EXECs runs were upgraded to z/OS 2.4 version Sunday morning, just before this
issue started. We do suspect that this could be a timing issue during the EXEC execution time, but we would
like to trace back why this started to happen all of sudden so we can fix this situation.
The EXECs works most of the times.
Release : 13.0
Component : OPS/MVS
The error noted in the description is not an OPS/MVS generated error. Adding a second delay in the EPI REXX code resolved this issue for the customer.
Enable tracing by adding a TRACE I to the start of the REXX EXEC. If unable to determine the problem from the trace, send the OPSLOG surrounding the time of the REXX being executed to Broadcom Support to further evaluate. Copies of the REXX code having the issue should also be supplied.