Yeah I have compiled all my subroutines after creating the Commons.

Like I said.. No issues when I make the calls using VB6 UniObjects.
But an issue when I use the UniObjects .NET

The error that is returned is 

[IBM U2][UODOTNET - UNICLIENT][ErrorCode=30105] Unable to load the subroutine 
on the server

SR.AHTEST.CALL1 only inserts AH.COMMON1

And

SR.AHTEST.CALL2 inserts AH.COMMON1 and AH.COMMON2


I assume it is an issue with the common block cause if I comment out $INSERT 
AH.COMMON2 in the SR.AHTEST.CALL2 subroutine I don't get any errors in 
UniObjects .NET.

Examples of this working in VB6 and throwing an exception in .NET can be 
downloaded from

http://www.mediafire.com/?sharekey=dfc3c5e4b0702c4d2fb2ca15d7ea42d9e04e75f6e8ebb871

The subroutines have been included as text files.




Adrian Halid
Senior Analyst/Programmer
 
IT Vision Australia Pty Ltd (ABN: 34 309 336 904)
PO Box 881, Canning Bridge WA 6153
Level 3, Kirin Centre, 15 Ogilvie Road, Applecross, WA, 6153
P:  (08) 9315 7000      F:  (08) 9315 7088
E:  [email protected]        W: http://www.itvision.com.au
    
___________________________________________________________  
                          
NOTICE : This e-mail and any attachments are intended for the addressee(s) only 
and may
contain confidential or privileged material. Any unauthorised review, use, 
alteration,
disclosure or distribution of this e-mail (including any attachments) by an 
unintended recipient
is prohibited. If you are not the intended recipient please contact the sender 
as soon as
possible by return e-mail and then delete both messages.
___________________________________________________________


-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of ozemail
Sent: Thursday, 8 October 2009 12:40 PM
To: 'U2 Users List'
Subject: Re: [U2] UniObject .NET Session and Common Block Bug

Hi Adrian

I don't have problem with named commons.  There is a problem if you update
the parameters in a named common and you do not compile all the subroutines
with the named common.  If you call a routine that has not been recompiled
you get a fatal, named common mismatch.  Is that a possible issue for you.
This is a general basic issue and is not an issue with .Net API.  

Regards

David Jordan

_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to