I useful thing I have found for any connectivity made via U2 APIs (be it UOJ, UCI, etc) is to get your subroutine to establish a COMO/DIVERT.OUT to log errors that made not get logged anywhere but output to 'standard output'.
It's surprising the number of errors you get before your main UV programs get initiated.... Regards, David -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Hester Sent: Wednesday, 1 July 2009 7:11 AM To: U2 Users List Subject: Re: [U2] UV UOJ hung sessions Thanks for the replies. I don't have either of the suggested trace tools and the UV errlog has no useful info, but I was able to find another method. We call a subroutine at the beginning of all of our UV BASIC programs that records user and execution time. I was able to add code there that executes a dummy VOC entry (just a proc that does nothing) followed by the program name whenever @TTY = uvcs. Now PORT.STATUS displays the name of the last subroutine executed by the hung sessions. -John ************** IMPORTANT MESSAGE ***************************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ************************************************************** _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
