I would add to the wrapper to SAVE all the UniData Internal Variables then call your subroutine, and then RESTORE all the Variables.
Example: U.ID = @ID U.DICT = @DICT U.RECORD = @RECORD READLIST U.SEL THEN SEL.FLAG = @TRUE (Any other COMMON variables that might be modified) ... DO YOUR CALL ... IF SEL.FLAG THEN FORMLIST U.SEL @RECORD = U.RECORD @DICT = U.DICT @ID = U.ID Thanks, David A. Green www.dagconsulting.com (480) 813-1725 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jon Wells Sent: Friday, April 24, 2009 6:04 AM To: [email protected] Subject: [U2] I-descriptor subroutine / SELECT question Hi all, I was asked to create an I-descriptor friendly wrapper subroutine for a subroutine that has one input argument and 10 outputs. Turns out this subroutine calls another subroutine that executes a select (against a different file). Active select -> LIST FILE-1 I-DESC -> I-DESC calls wrapper -> wrapper calls subroutine -> called subroutine tries to execute select against FILE-2. Is there any way to get around the active select so the query against FILE-2 works correctly? BTW - We're running Unidata 7.1 Thanks, *-----------------------------------------------------------* Jon Wells Database Administrator Beloit College Information Services & Resources Beloit, Wisconsin 608-363-2290 [email protected] 608-363-2100 (fax) *-----------------------------------------------------------* ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
