CMSHR.EXE and the Linker

[rodprince]

Now that the Pascal Compiler is available we are testing our system build procedures on x86. We use CMS for our source code libraries. Many of our utilities make use of the callable CMS interface. We have noticed that with x86 the sys$library:cmsshr.exe is not "automatically" included in an image link. We have had to modify our build procedures to include a linker opt file that specifies sys$library:cmsshr.exe/share so that they can resolve any CMS$ calls they may have. While its not an issue to modify the build procedures, I was wanting to point it out in case its not the expected behavior.

We currently use the following on our IA64 &Alpha systems

say = "write sys$output"
$!
$ say " Compiling Build..."
$ pascal build
$!
$ say " Compiling build cld..."
$ set command/object build_cld
$!
$ say " Linking build..."
$ link build,build_cld
$!

We have had to change the link command to be

$ link build,build_cld,build/opt

The build.opt file contains the following: sys$library:cmsshr/share

[imiller]

If CMS is installed then it should be in SYS$SHARE:IMAGELIB.OLB

$ pipe lib/list sys$share:imagelib.olb | sear sys$input: cms

should show
CMSSHR

and linker should therefore find it.

Added in 8 minutes 15 seconds:
I did a quick test

The following products have been installed:
VSI X86VMS CMS V4.8-9 Layered Product
VSI X86VMS DECSET V13.0-1 Platform (product suite)

%PCSI-I-IVPEXECUTE, executing test procedure for VSI X86VMS CMS V4.8-9 ...
%PCSI-I-IVPSUCCESS, test procedure completed successfully
$ pipe lib/list sys$share:imagelib.olb | sear sys$input: cms
%SEARCH-I-NOMATCHES, no strings matched

Added in 8 minutes 1 second:
$lib/insert sys$share:imagelib.olb sys$share:cmsshr.exe

should add it

[rodprince]

I do see the sys$share:cmsshr.exe file.

The lib/insert command you specified makes the linker all happy, and I don't have to modify any build procedures.

Thank You

Rod

[jreagan]

The DECset installation should have done that insert command for you. I'll pass this long to the right person.

[cct]

Slight thread drift, but will a future DECSet include LSE? Any rough timescale?

CHris

[arne_v]

Slight thread drift, but will a future DECSet include LSE? Any rough timescale?

https://vmssoftware.com/about/roadmap/ says H2 aka within next 4.5 month.

[cct]

Missed that - thanks Arne

Chris

[jreagan]

Huh? The current DECset kit doesn't include LSE? I'm running LSE on my x86 systems (and have for a while now). Maybe I have an internal kit that hasn't been published? I'll go ask.

[arne_v]

Huh? The current DECset kit doesn't include LSE?

That is the word.

And what the roadmap says.

And what https://vmssoftware.com/products/langua ... ve-editor/ says.

I'm running LSE on my x86 systems (and have for a while now). Maybe I have an internal kit that hasn't been published? I'll go ask.

I am sure you have access to a lot of things the rest of us don't have.

[jreagan]

Yes, I've confirmed that the current kit on the portal doesn't have LSE. I have an internal version. It works for me, but I did notice that in spite of asking for VMSLSE command syntax, it comes up in PORTABLE more. I had to add explicit commands to my LSE init file. The maintainer knows about that. I'll push on him as appropriate.