Building on Win2K8 R2 with VisualAge PL/1

[Chris Westcott]

I know this kind of question comes up from time to time and I’ve been reading through those posts and think that my question is slightly different to those.

I had read in “VisualAge PL1 for Windows on Server 2008” that 2.R1.14 is able to compile 64-bit exe's. I've tried to set this up as follows:

* Install VisualAge PL/1 2.R1.08
* Upgrade via repair option to 2.R1.10
* Upgrade via repair option to 2.R1.14

What I’m trying to do is get this set up to not only target up to Windows 2008 R2 (64-bit) but also compile on this set up.

I’ve tried these steps as Administrator and with limited success. Running in Windows 2000 compatibility mode means I can run the compiler successfully, creating object files however ilink.exe fails (crashes on run). Again I’ve checked compatibility mode options and they all fail.

A few more questions:
* Is RDz the only option for compiling on this configuration?
* Haa anyone had success with this configuration?
* If I can build DLL’s using VisualAge PL/I 2.R1.14 on another machine, are they compatible for use with PL/1 applications compiled with RDz on Windows 2008 R2?

Many thanks in advance for your time.

Chris

[Chris Westcott]

I made a mistake in my original post. The version I installed from CD before patching up was IBM VisualAge PL/1 2.R1.07 from CD.

[Mike Zimnov]

Same versions and installation order on W8x64 (WXP SP2 compatibility). Compiler and linker work, but
1. Compiler has very strange behavior (do not compile old and succesfully compiled on earlier versions Windows sources
2. Linker works, but executable doesn't work in W8x64 (checked for couple simple examples)

For Rdz. I have v7, but it doesn't install on w7 (some java problems). Newest calls PL/I as deffered...

[John Wood]

In article <477e6458-0bb1-4447...@googlegroups.com>,
Chris Westcott <ch...@westcottwideweb.com> writes

>I had read in “VisualAge PL1 for Windows on Server 2008” that 2.R1.14 is able to
>compile 64-bit exe's. I've tried to set this up as follows:
>
>* Install VisualAge PL/1 2.R1.08
>* Upgrade via repair option to 2.R1.10
>* Upgrade via repair option to 2.R1.14
>

On my normal Win32 WinXP machine
I have had lots of trouble with 2.1.14 with backend compiler failures
so I dont use that version any more

I have recently installed vaPLI 2.1.12 on a new i7 quadcore machine
Win7 Ultimate 64 bit
The vaPLI installations always fail first time, and the OS asks if you
would like it installed with the 'correct options'
Not quite sure what that means, but YES gives a clean install
I installed 2.1.03 07 10 12
Simple programs will compile and link fine, exe runs OK
EXE is not marked as "XP compatible"
How do I determine if my executable is 32 or 64 bit? and
how did you ask for a 64 bit executable ?

--
John Wood Birmingham UK

[Mike Zimnov]

John,

Thanks, I repeat your steps on Win8 64 with no success... Will try on Win7, but I don't think that there is big difference. Strange.

[Daiyu Hurst]

On Thursday, March 7, 2013 12:28:27 AM UTC-5, Mike Zimnov wrote:
> Same versions and installation order on W8x64 (WXP SP2 compatibility). Compiler and linker work, but
>
> 1. Compiler has very strange behavior (do not compile old and succesfully compiled on earlier versions Windows sources
>
> 2. Linker works, but executable doesn't work in W8x64 (checked for couple simple examples)

Compiler and linker work for me fine on Win7-64, executables run ok too (they are 32-bit but still run).

[RickNH]

Just curious ... does your idebug.exe work OK on W2008 64?