Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

File Functions

7 posts in Appeon (partner product) Last posting was on 2005-04-27 05:42:18.0Z
angelo.anolin@gmail.com Posted on 2005-04-20 07:32:04.0Z
Sender: 35a9.426601c7.1804289383@sybase.com
From: Angelo (angelo.anolin@gmail.com)
Newsgroups: sybase.public.appeon
Subject: File Functions
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4266056f.35ee.1681692777@sybase.com>
X-Original-NNTP-Posting-Host: 10.22.241.42
X-Original-Trace: 20 Apr 2005 00:31:59 -0800, 10.22.241.42
Lines: 22
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 20 Apr 2005 00:32:02 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 20 Apr 2005 00:32:04 -0700
X-Trace: forums-1-dub 1113982324 10.22.108.75 (20 Apr 2005 00:32:04 -0700)
X-Original-Trace: 20 Apr 2005 00:32:04 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:786
Article PK: 12685

In the Supported Features Guide of Appeon 2.8, it is stated
that Windows API Functions are unsupported. Now, I have
learned that in workarounds being posted in the Appeon
website, it is advised to replace file functions in
Powerbuilder with Windows API function calls to be declared
as Global External Functions. Further reading, I again
encountered in the Supported Features Guide that Global and
Local External Functions are unsupported in Appeon. The
workaround posted contradicts so much with the Supported
Features Guide. Nevertheless, I took the initiative to
check the method as proof of concept. I tried using the
Windows API Function call thru the kernel32.dll in a test PB
application. The function call went well. I analyzed the
test application using Appeon Developer and the analysis
provided no conflicts whatsoever so I decided to deploy the
test application. When i deployed the test application and
run the web app, the file functions i used returned errors.
Please advise.

Please note that subsequent file function errors were
encountered since the file functions are simulated to run
after each succesful function call.


Julie Jiang Posted on 2005-04-21 10:23:14.0Z
From: "Julie Jiang" <julie.jiang@appeon.net>
Newsgroups: sybase.public.appeon
References: <4266056f.35ee.1681692777@sybase.com>
Subject: Re: File Functions
Lines: 178
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01C5469E.C72BA2F0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Original-NNTP-Posting-Host: 210.21.221.178
Message-ID: <42677f0d$1@forums-2-dub>
X-Original-Trace: 21 Apr 2005 03:23:09 -0800, 210.21.221.178
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 21 Apr 2005 03:23:11 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 21 Apr 2005 03:23:14 -0700
X-Trace: forums-1-dub 1114078994 10.22.108.75 (21 Apr 2005 03:23:14 -0700)
X-Original-Trace: 21 Apr 2005 03:23:14 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:792
Article PK: 20895

Hi Angelo,
 
The Workarounds Guide reflects the product state more correctly, because the Workarounds Guide is a "live" document on the website that can be updated with the lasted testing findings.   Of course, Appeon is also trying the best on ensuring the correctness of Appeon Help, so we thank you very much for reporting the discrepancies! 
 
Regarding the test case, I think that you should be using the test case provided on the Workarounds site.  The test case can work well.  The reason for the failure should be, the dll file used by the application is not in "C:\WINNT\system32", resulting in the Web application cannot find the DLL file.  As stated in the Appeon Help, "When your application calls an external function, it must be able to find the DLL (Dynamic link library) or the shared library in which that function resides.  To ensure this, you must update the library path environment variable on the client machine to include the directory where that DLL or shared library is stored" 
 
Therefore, I suggest you copy the handfile.file to the "C:\WINNT\system32" folder at the client and try again. 
 
Regards,
Julie
 
 
"Angelo" <angelo.anolin@gmail.com> wrote in message news:4266056f.35ee.1681692777@sybase.com...
> In the Supported Features Guide of Appeon 2.8, it is stated
> that Windows API Functions are unsupported.  Now, I have
> learned that in workarounds being posted in the Appeon
> website, it is advised to replace file functions in
> Powerbuilder with Windows API function calls to be declared
> as Global External Functions.  Further reading, I again
> encountered in the Supported Features Guide that Global and
> Local External Functions are unsupported in Appeon.  The
> workaround posted contradicts so much with the Supported
> Features Guide.  Nevertheless, I took the initiative to
> check the method as proof of concept.  I tried using the
> Windows API Function call thru the kernel32.dll in a test PB
> application.  The function call went well.  I analyzed the
> test application using Appeon Developer and the analysis
> provided no conflicts whatsoever so I decided to deploy the
> test application.  When i deployed the test application and
> run the web app, the file functions i used returned errors.
> Please advise.
>
> Please note that subsequent file function errors were
> encountered since the file functions are simulated to run
> after each succesful function call.