I've got an odd question for ya: are there problems associated with constantly connecting to/disconnecting from a session during the course of a day?
The situation: we are allowed only a single connection to a remote mainframe for each workstation; each user now has at least two programs that need to retrieve data from that session, and the user needs to be able to use it also.
I've just done a quick test to see whether the program could successfully connect/disconnect/re-connect the session, and it worked like a charm so what I'm considering now is having each program connect/retrieve/disconnect, connect/update/disconnect - leaving the session available for another program to connect.
Doing it this way, there's no likelihood of the two programs competing for a connection - but this is a cycle that'll happen hundreds of times per day, per user, and that's where my concern lies.
Has anybody tried this? Had success/failure with it?
The situation: we are allowed only a single connection to a remote mainframe for each workstation; each user now has at least two programs that need to retrieve data from that session, and the user needs to be able to use it also.
I've just done a quick test to see whether the program could successfully connect/disconnect/re-connect the session, and it worked like a charm so what I'm considering now is having each program connect/retrieve/disconnect, connect/update/disconnect - leaving the session available for another program to connect.
Doing it this way, there's no likelihood of the two programs competing for a connection - but this is a cycle that'll happen hundreds of times per day, per user, and that's where my concern lies.
Has anybody tried this? Had success/failure with it?