Feedback
Did this article resolve your question/issue?

   

Article

Error 5638 and 196 on IHttpRequest using Http Client

Information

 
TitleError 5638 and 196 on IHttpRequest using Http Client
URL Nameerror-5638-and-196-on-ihttprequest-using-http-client
Article Number000113948
EnvironmentProduct: OpenEdge
Version: 11.6.x, 11.7.x
OS: All supported platforms
Other:
Question/Problem Description
Trying to send a request from a Webspeed agent using Http Client fails to compile. Errors 5638 and 196 are reported when trying to compile an HTML file that includes Speedscript and using Http Client.
Same issue if another class is added to the speedscript code,  for example Progress.Json.ObjectModel.JsonObject.
 
Invalid datatype specified: IHttpRequest. Specify a datatype such as ‘character’ or the name of a class. (5638)
** ablProc.w Could not understand line (196)
The following sample code generates these errors:
 
Invalid datatype specified: <type>. Specify a datatype such as 'character' or the name of a class. (5638)
** <program> Could not understand line <number>. (196)
 
Steps to ReproduceTry to compile an HTML file that includes Http Client.

Add this lines in a new HTML file:

<SCRIPT LANGUAGE="SpeedScript">
/*------------------------------------------------------------------
File:
Description:
Created:
-------------------------------------------------------------------*/

USING OpenEdge.Net.HTTP.*.

DEFINE VARIABLE oReq AS IHttpRequest.
</SCRIPT>
Clarifying Information
Error MessageInvalid datatype specified: <type>. Specify a datatype such as 'character' or the name of a class. (5638)
** <program> Could not understand line <number>. (196)
Defect/Enhancement NumberDefect PSC00250002 / OE00227519
Cause
Recent OpenEdge releases have introduced new syntax to the language that must be located on the first line of the program.  This has never been true of ABL syntax until this point and the WebSpeed code that is used to generate the temp (compilable) programs from SpeedScript generates its own code at the top of these interim programs.

This causes errors to occur when compiling SpeedScript programs with syntax like the ROUTINE-LEVEL and USING statements, because these statements have to be located at the top of the programs and there is no venue to accomplish this using SpeedScript in WebSpeed Workshop.
 
Resolution
None at this time.
Workaround
Please follow the steps described in article 000036155 in the workaround section.
 
Notes
Progress Article(s):

000036155Cannot use top-only ABL statements in SpeedScript
Last Modified Date1/17/2019 8:16 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.