Chris Pepper

Something to play with...

ProIV Global Logic types can be A / N / W return a value using the RETURN() statement.
We have discovered that (up to and including ProIV 5.5 - our current version) there is no validation on the data type returned. If it is the "wrong" type then a a value is returned depending on the value stored in a ProIV internal temporary variable.

Example: Create a Global Logic type A and RETURN(-1) this returns a string of "00" when the Global logic is called in a Function.

You can also see this if you put in an EXIT or RETURN statement without a value - the value returned will be a value from previous temporary result.

I'm interested if this behaviour occurs in 6.x or 7.x or if any of the development environments trap it.

I had to laugh... I'm finally working on converting our development system from 3.0 to 5.5 and hit a problem with Tags.

Searching for help here I found an old topic I created that starts...
Posted 15 January 2003 - 06:40 AM

I've looked at the history on converting from 4.6 to 5.0. Has anyone any more comments?
I'm not interested in any GUI related changes as our ProIV is purely server side. I am interested in any bootstrap file changes as we store source in text files in a code management system and I need to load functions from this into a 5.0 environment. It won't be a one off as I'll need to support multiple versions for a while. Any comments on the 'Tags' would be helpful if they are related to non-gui code.

How optimistic was that!

Anyway I did get some clues to help from here. Just in case anyone else is upgrading from and end-of-life version to a slightly newer end-of-life version... I was getting a 729 - DUPLICATE FIELD TAG NAME error on genning. It appears the Import/Export is adding Tags to both the fields and LS - however @CFUN is not Tag aware so when I copied LS2 to LS3 on a Function it happily duplicated the name Cycle2 for both LS. It appears that Tags in Cycles aren't accessible in @MOD - at least if they are I can't find where! So just beware of that!
At least when I've finished getting our development environment up the real source code of our system won't be being loaded through Import/Export, it'll be loaded by my routines straight from the Source Code Control System.

Does anyone know of any improvements to the ALIAS command in versions 6, 7, 8?

Specifically, is it still restricted to 40 characters? Is the Upper case conversion problem fixed? (Unix/Linux related)

We may soon have a vacancy for a ProIV developer in Central London.
We are not a standard site, you'll only be working in ProIV with Updates and Reports. No screens, no ProIV GUI. All presentation level is in Microsoft GUI and Java.

Very good basic ProIV skills in a pre-6.0 standard ProIV development environment are the main requirement.

Any additional skills/experience in any of Oracle or DB2 databases, Java, VB, C or C++, Citrix, Perforce, VMs, Unix, Linux or VMS would be beneficial but by no means mandatory. Chances to expand your skills into these areas.

1) No agencies
2) No contractors
3) Applicants should be pre-qualified to work in the UK

We have a very low staff turnover, for very good reasons, so we don't often recruit.

Send me a message or email through the site if you have any questions, or might be interested. I'm not personally in charge of this, but will pass on possible candidates to those that are.

This error message is being issued under the following conditions:

A specific Function is being genned (under 4.6 / Oracle if relevant).
The gen continues for a long time, then the message above is given.

It appears that the gen is "successful" (i.e. the Gen records are created) but the Function does not execute properly.

I'm guessing that the message is a problem with the gen process, rather than a gen error in the Function. From the length of time, I would guess that the gen process is getting itself into a loop.
Any ideas or previous experience would be useful at this stage.

I'm going to request a support call, so will update if there is any official response.