The OpenEdge Hive

I'm trying to fix an issue in Prolint, but this is a general ABL question. Here's the code:

   handlers = "":U.
   FILE-INFO:FILE-NAME = ProfileDirectory + "/handlers.d":U.
   IF FILE-INFO:FULL-PATHNAME <> ? THEN DO:
      INPUT FROM VALUE(file-info:FULL-PATHNAME).
      REPEAT:        
         IMPORT handler.                               
         /* if handler exists and supported in this Progress session, then add to list */
         IF CAN-FIND(tt_output WHERE tt_output.progname=handler) THEN 
            handlers = handlers + ",":U + handler.
      END.
  

We are (still) using AS400 dataserver version 8.0C60 to access DB2 database on AS400
iSeries (os version V5R3). We have to apply the AS400 patch every 6 months but other than
that everything is working fine (client is the Progress application release 9.1D09 (no appserver)
on IBM AIX 4.3.3.0).

Our company is looking into upgrading our AS400 iSeries system, including os upgrade to
V5R4M5 or 6.1.

What am I hearing from Progress support for now is that only OE ODBC Dataserver 10.1C
is supporting V5R4. But our 9.1D client can not 'talk' to OE 10.1C ODBC Dataserver, and we

Hello everybody,
I would like to know that:

Is there an implementation of "RESTful principle" (Representational state transfer) in OpenEdge?
The ideas behind REST were formalized in Chapter 5 of Roy Fielding’s 2000 PhD dissertation
http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm

hi have worked remotely before , have 8 -9 year experience in progress 4gl and openedge taking a break is there anyone out there who needs some skills , just bored have oe10 compiler on laptop , not particularly looking for necessarily paid work. wont be working till january so would like to keep my brain ticking over anyone got anything

jango

I am trying to call the progress UI(Built using AppBuilder) in C #; I would like to know if there is any way to do it? I am using progress 10.2 beta version.
Please help me!

When creating a new program, we need to ensure the SVN header was added before checking the code in. What rule could I look at or copy with slight modifications for this? I noticed a couple of different approaches and I want the one that' most efficient.

Basically, I'm thinking all I need to do is see if SVN is somewhere in a comment at the top of the program.

I'm trying out the ProParse/ProLint utilities and can't find a solution on how to deal with the following situation:
- use of Varusage to check on defined variables that are never used
- If there are variables that are only used in &if-blocks (and at the moment of the check this &if-statement gives a false result) I will get the message that this variable is defined but never used.
Now in this cases the next step I should do is to delete these unused variables but it is possible that the variable is used if the &if-statement give a positive result (so the variable has to be defined).

Hi,

I wonder if the .Net framework supported in the upcoming 10.2A already have classes defined to be just what we'd need for the OERA components (from the beta presentation site, .Net 3.0 and 3.5 seem to be supported)?
I know almost nothing about .Net, but there seems to be a large API with a well thought structure.

Since 10.2A will support ABL classes inheriting from .Net classes, we'll probably be able to override .Net component methods to use our own ABL implementation if needed, and in many cases, we'll probably don't even need to have an ABL implementation!

Has anyone written some sort of procedure editor customization for the character based version that would handle the same job has subclipse does for openedge architect ?

In other words, I am looking for an added menu item in the procedure editor that would pertain to most subversion tasks and activities (ie: Update, Commit, Synchronize, Diff, Merge etc.)

Thanks.

I am scheduled to do some Prolint consulting, starting mid-October. We will be setting up Prolint on a server, where it will monitor file changes and generate reports as a batch-style process.

My hope is that I'll be able to start them off right away using the new proparse.jar rather than the old proparse.dll. This means I'll have to move fast on a new version of Prolint.