I have recently encountered a very strange UniObjects bug. I have an application that includes a file containing unnamed commons. The application calls a subroutine that also includes that same unnamed common. I also have a command that includes the unnamed comman and calls the same subroutine that includes the unnamed common. When I run the command and subroutine sequentially in a loop via UniObjects, the UniSession dies. If I only run the subroutine or the command in a loop, it works like a champ. Adding more unnamed commons to the include file only causes the problem to happen less often.
Please look at my sample application to see if you have any insight into why this fails consistently. Attached are the sample applications. Thanks, Sean Ferguson [demime 1.01d removed an attachment of type application/octet-stream which had a name of asjava.jar] [demime 1.01d removed an attachment of type application/octet-stream which had a name of asjava_p.jar] COMMON POS INCLUDE RMS.BP INPUT.COMMON.POS CALL TEST.SHARED.SUB SUBROUTINE TEST.COMMON.SUB INCLUDE RMS.BP INPUT.COMMON.POS CALL TEST.SHARED.SUB RETURN SUBROUTINE TEST.SHARED.SUB INCLUDE RMS.BP INPUT.COMMON.POS POS = "1" RETURN [demime 1.01d removed an attachment of type application/octet-stream which had a name of TestCommons.jar] ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
