topic Re: AESTing SCAN images on Itanium in Operating System - OpenVMS

AESTing SCAN images on Itanium

Malcolm Davies — Wed, 19 Jul 2006 05:24:04 GMT

Hi,

We are testing a new Itanium development box, and we have some tools that rely on Scan images when building Decforms (replacing token placeholder code with language specific variants).

We have AEST'd the SCN exe's on the Itanium system using AEST defaults, but are now getting errors - without associated SCN message libraries we are a bit stuck trying to figure this out and no longer have a Vax with Scan on to look for the message, any suggestions or advice would be welcome at this point (Does anyone have a Vax with Scan message libraries who could translate the error code below?).

Some details:
$ scan_form_input_file = "scr:PATCH_REQUEST_FORM.IFDL"
$ scan_form_tags_file = "obj:PATCH_REQUEST_FORM.tags"
$ scan_form_panels_file = "scr:PATCH_REQUEST_FORM.panels"
$ create_panels_file = "Y"
create_form_tags_file_scn.*
$ run/nodeb utl_rel:[exec]create_form_tags_file_scn
%SCN-F-NOMSG, Message number 0132809C
$get_out_err:

Thanks,
Malcolm

Re: AESTing SCAN images on Itanium

Volker Halle — Wed, 19 Jul 2006 05:42:11 GMT

Malcolm,

$ @<.tools>msgtxt 0132809C
fac_no: 132 severity: 4 (SEVERE)
Message found in SYS$COMMON:[SYSMSG]SCN$MSG.EXE;1
%SCN-F-FILPRVCLS, Close failed - file not open

Volker.

Re: AESTing SCAN images on Itanium

Robert Gezelter — Wed, 19 Jul 2006 05:44:45 GMT

Malcolm,

Licensing issues aside, if you need a VAX system to check things out on (and you have your old backup files), you can use SIMH or Charon-VAX.

SIMH is available at http://simh.trailing-edge.com
Charon-VAX is available at http://www.charon-vax.com

Both effectively provide the ability to run an emulation of VAX hardware on an Intel IA32 Windows system.

- Bob Gezelter, http://www.rlgsc.com

Re: AESTing SCAN images on Itanium

Volker Halle — Wed, 19 Jul 2006 05:50:01 GMT

Malcom,

there is a CHARON-VAX/Freeware for OpenVMS I64 download, which would enable you to emulate a VAX running on OpenVMS I64 (with 1 VUPS only, but it works). So if you still have the BACKUPs of your VAX system disk, this may also be way to go.

Volker.

Re: AESTing SCAN images on Itanium

Ian Miller. — Wed, 19 Jul 2006 06:22:13 GMT

Scan is available natively on OpenVMS Alpha

http://www.emulatorsinternational.com/en/vaxscan.htm

You could contact them to see if they have or plan to have it on OpenVMS I64

Re: AESTing SCAN images on Itanium

Martin Michalecz — Wed, 19 Jul 2006 07:28:26 GMT

Volker already answered using his tool.
I would like to add the manual version.

SGDEV6::MM:000000 >SET MESSAGE SYS$MESSAGE:SCN$MSG.EXE
(B) SGDEV6::MM:000000 >WRITE SYS$OUTPUT F$MESSAGE(%X0132809C)
%SCN-F-FILPRVCLS, Close failed - file not open

On our system (IA64, VMS 8.2-1) the SCN$MSG file is installed by default.

Martin

Re: AESTing SCAN images on Itanium

Hein van den Heuvel — Wed, 19 Jul 2006 07:31:20 GMT

Maybe it is time to replace your scan code.
It was a good idea at the time, but it's getting too tricky now.

The task you describe sounds like relatively suiteable for a perl script.
Its regular expressions make token recognition relatively easily and you'd be working with a language the many more people know and/or are willing to learn.

fwiw,
Hein.

Re: AESTing SCAN images on Itanium

Malcolm Davies — Wed, 19 Jul 2006 07:37:53 GMT

Thanks for the great responses. I have followed up a few of them. Firstly we have now defined the correct logical for SCN$MSG and so see the error message correctly.

Secondly, I contacted emulators international who said as only 2 people use the Alpha version, no way they would do IA64 unless we were willing to pay for it. Following this, the suggestion to rewrite in Perl sounds promising. We do have the original code, so this should be straight forward. Until then I will be checking the file open/close sections of the code to see if I can track down the error, maybe even creat debug version of image using AEST.

thanks,
Malcolm

Malcolm.

Re: AESTing SCAN images on Itanium

Malcolm Davies — Wed, 19 Jul 2006 09:28:19 GMT

Following advice from the forum, we tracked down an incorrect logical pointing to the sys$library:SCNRTL.EXE image, problem now resolved.