|
Patrick This seems to mirror the green screen behaviour that occurs when the users initial program does not have an explicit signoff command. This may have been done to allow users to call the initial program from a command line (developer convenience/lack of intelligent security) but in any case, the subsequent quick fix to add some security and remove user access to system menus (as pointed out elsewhere) is to alter the user profile to have *SIGNOFF as the initial menu value. This ensures that when the initial program has ended (i.e. application ends) the job is then forced to signoff. The fix is to either alter the current initial program to have an explicit SIGNOFF command, or (if your current program cannot be altered for some reason) create a brand new new initial program that calls the current program and then does a sign off when it completes. I think this should fix your problem. Regards Evan Harris >Hi, > >When we quit a WebFacing application, we get a 'signoff'-screen in our >web-browser as follows: > >==> >job xxxx/xxxx/xxx started on 22/01/002 at 09:08:58 in subsystem SBSNAME in >QGPL.Job entered system on 22/01/02 at 09: >Message Queue xxxx is allocated to another job. >Initial program ended and *SIGNOFF specified for initial menu. > >press enter to continue. > >==> >Also the activated VT-job stay's active. > >Wat I would like is to return to the page from which the application is >loaded and to end the active VT-job. > > >Patrick Goovaerts >IT/Clipper Support nv
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.