|
We have the same problem with users creating runaway jobs by just clicking the 'x' in a Rumba session. We were looking at possibly the same thing. I wonder if you can do something with the QIBM_QTG_DEVTERM exit point? jk -----Original Message----- From: Jodi_Walker@ccmail.columbia.com [mailto:Jodi_Walker@ccmail.columbia.com] Sent: Wednesday, September 13, 2000 1:08 PM To: MIDRANGE-L@midrange.com Subject: Exit point the situation: we have a file that is created in QTEMP when a user logs in. the file is populated by different programs. within each of those programs, the contents of the QTEMP file are then processed either when the user presses enter or F3, depending on the application. after a record is processed, it is then deleted from the QTEMP file.(the process will be undergoing a major re-write, but that is a good year or so away) the problem: if the user's PC loses power, the user clicks on the X to close the emulator program or whatever, then the records in their QTEMP file do not get processed. this causes a major problems elsewhere. my proposed resolution: as the session is being disconnected from the 400, check the QTEMP file to see if there are any records in it, if so, then call the program to process those records and then allow the session to finish the disconnect process - or some variation thereof. maybe copy the file contents to a dataq, and process from there, whatever. my question: is there an exit point during session disconnect, whether that disconnect is started by the user using an end session command, an operator using an endjob command, or the system ending the session because it has been idle too long (in the case of a power loss to the PC or the user improperly closing their emulator), that i can use to run an exit program to accomplish my resolution? if so, what is the name? i've done some research but have come up empty handed so far. any suggestions on redbooks or manuals would also be appreciated as this will be my first attempt at using exit programs/points. thanks jw +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.