Hi Adrian I've never seen this particular issue before. What release of UniVerse or UniData is this (likewise the clients too)? What OS/platform is your U2 installation on?
I would suggest some of the following to assist you in drill down the root cause: a) Execute a "DIVERT.OUT" or "COMO ON" (or call !COMO) to capture the host sessions standard output errors. Sometimes you can see the actual error in your output file (if there is any additional errors output) b) Check the VOC entries for the subroutines you're calling c) Call the subroutines as globally catalogued subroutines (CATALOG BP *MYSUB).. see if there is a difference Regards, David ************** 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 [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
