by steve-myers » Mon 30 Apr 2012, 14:12
Based on a couple of years of experience, it takes several hours for a "stuck" session to time out. The Mainframe FAQ has a topic that discusses how to (most of the time) cancel a stuck session. A second ID won't help you. If the process in Mainframe FAQ does not terminate your "stuck" session, you will probably need assistance from an administrator to "force" your session, though in recent months when this problem has been encountered other methods were required.
Right now (about 9:15 AM system time) it appears JES2 is having trouble and an administrator will have to get involved.