Hi all, just wondering if anyone has encountered this before?
I was running some tests and discovered that doing a "PORT.STATUS PID pid CALL.STACK" on a program that is waiting to open a named pipe with OSOPEN caused it to bomb out. I looked and it didn't have an ON ERROR statement, so I added it and checked again. Every time I made the PORT.STATUS call, it caused it to drop into the ON ERROR section. My guess would be to perform the check on the program; it has to interrupt it, hence causing it to bomb out of any blocking calls. Until now, I had assumed the PORT.STATUS command would not affect a program, but now it appears that it can, meaning it could potentially be dangerous to use in a production environment. Is this documented anywhere? Regards, Dan ########################################################################################### The information transmitted in this message and attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files with the permission of IMB. ########################################################################################### _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
