CurtisZ

About Me

I'm a Special Projects programmer for Dexter + Chaney. I write customized interfaces and reports for the construction accounting package that the company develops and markets. I also have experience in Crystal Reports, Visual Basic.NET, AS/400 (iSeries; System i; what-have you) systems administration and programming - CL and RPG/400.

In my spare time I work with my wife to raise three wonderful daughters. I attempt the house repairs, and I'm getting fairly proficient with auto repairs. I also play offensive line for a local semi-pro football (American) team.

Topics I've Started

We have been having an issue of late in our programming environment, but I am not sure if it is an issue with our environment or if this could be a PROIV bug.

Firstly, our environment. We use VMWare View Client to access Windows XP images to access our environments to program in. PROIV and MS SQL 2k8 is hosted on the same Windows 2k3 server.

Secondly, our issue. We have noticed that when we are working in logic, and we accidently press F3 then F4 in a rapid succession, this causes the session to hang. At this point we are unable to kill the session through any of the PROIV tools, and it will not time out. We cannot do anything with the code, because it is considered locked by the rogue session, so we have to restart the PROIV services.

Lastly, I am wondering if anyone else has experienced this, or could duplicate it for me as this would help me determine where our issue may lie. This does not happen often, but it is a royal PITA to have to get all the developers and testers off the server for us to restart services.

A couple of the programmers here have been wanting to create accounts to participate, but they are telling me the forum is not allowing new users. When they have tried e-mailing about the issue, they have not had any response.

We are migrating our code from 5.5 to 6.1. All of our code is in VIP 5.5927. The PROIV release notes for 6.1.57.0 state the following:

'PROIV Version 6 is

not genfile compatible with PROIV Version 5; the only upgrade path is to export your source code from Version 5 and import into Version 6 and then build your functions. To do this we recommend that you are on the latest maintenance release of PROIV Version 5.5. Please refer to the PROIV website for the latest release on your platform. You must have a minimum of 5.5r517or 5.5r518 and the minimum version of VIP 5.5932.

In addition to providing an export format suitable for import into PROIV Version 6, the 5.5.932 release of VIP also allows for export of other non function source (for example security settings) – this is referred to as Non-Source Export. An enhanced version of Non-Source Export, supporting more object types, was introduced in VIP 5.5949, and the matching import functionality was introduced in PROIV Developer 6.1.10.0. Non-Source Export is explained in detail below. Attempting to import a VPX generated by a VIP version earlier to 5.5932 may corrupt the Version 6 installation.'

So, we have been installing our code on an intermediate client that has VIP version 5.594, then we export it out of that client into our V6.1 client. However, we have been thinking about attempting to install some of our smaller projects straight from our VIP 5.5932 into 6.1 to reduce some overhead (do not ask me why we do not just upgrade our VIP environment to 5.5932 or higher, I would, but I don't make that call).

Is anyone currently upgrading their code to 6.1 that is using a VIP version earlier than 5.5932? I have currently upgraded a couple projects straight from 5.5927 with no issues, but I do not want to 'press my luck' if anyone else is currently doing this and having issues.