Hello,
I'd like to specify that I'm not an administrator, so my knowledge is limited. We've created partitions on our Power 9 server. When we connect to our main partition, we never have any issues. However, when connecting to one of the new partitions, many of us have disconnects. It feels like it's related to inactivity. If we don't do anything for a while, we get disconnected.
After a few disconnects, the connection somehow is able to remain connected. However, it is extremely exhausting to have to reconnect so many times before it is able to do so. Some users suffer no disconnects at all, others suffer disconnects all the time. Once we are disconnected, no joblog or spool is conserved, meaning the job is no longer in the system and we can't see the joblog for clues.
We are all connected to the same network by ethernet cable.
Is there any way to see why our 5250 sessions are being disconnected? Is there any way to force the joblog to be created as a spool so the job remains in the system and so we can look at the joblog once the job disconnects for clues?
Thanks.
I'd like to specify that I'm not an administrator, so my knowledge is limited. We've created partitions on our Power 9 server. When we connect to our main partition, we never have any issues. However, when connecting to one of the new partitions, many of us have disconnects. It feels like it's related to inactivity. If we don't do anything for a while, we get disconnected.
After a few disconnects, the connection somehow is able to remain connected. However, it is extremely exhausting to have to reconnect so many times before it is able to do so. Some users suffer no disconnects at all, others suffer disconnects all the time. Once we are disconnected, no joblog or spool is conserved, meaning the job is no longer in the system and we can't see the joblog for clues.
We are all connected to the same network by ethernet cable.
Is there any way to see why our 5250 sessions are being disconnected? Is there any way to force the joblog to be created as a spool so the job remains in the system and so we can look at the joblog once the job disconnects for clues?
Thanks.
Comment