You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So something happened today that our team started have very slow response times when connecting, opening filters, getting library list ect. Liam suggested I revert to the pre-release of Code4i so I did. Still same slow response times. When I say slow response times I means minutes upwards to 5 mins or longer. The DB2 for i connection seems very fast and I can run SQL statements there fine.
Is there a server job running on the IBMi that might need to be restarted? I can run the same SQL Code4i is running in QSH and run it in ACS and it runs very quickly.
The text was updated successfully, but these errors were encountered:
@thomprl if you watch the log as you connect, is there anything that sticks out as taking a while? This is very user specific, so unless we add timestamps or something we won't know.
@worksofliam I'm beginning to think it's a server issue now. Or something going on with QSH. Other users are reporting similar problems and I think they are about to IPL the box. I'll keep you posted.
So something happened today that our team started have very slow response times when connecting, opening filters, getting library list ect. Liam suggested I revert to the pre-release of Code4i so I did. Still same slow response times. When I say slow response times I means minutes upwards to 5 mins or longer. The DB2 for i connection seems very fast and I can run SQL statements there fine.
Is there a server job running on the IBMi that might need to be restarted? I can run the same SQL Code4i is running in QSH and run it in ACS and it runs very quickly.
The text was updated successfully, but these errors were encountered: