From Newsgroup: comp.os.vms

What does one link with to make a program using CMA_ functions
run?

Linking with sys$share:cma$open_rtl does not give any link
errors.

But it seems like whatever I call then I get:

%CMA-F-EXISTENCE, object referenced does not currently exist

So I guess I should be linking with something else. But what?

VMS 9.2-3 if it matters.

Arne


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.os.vms

On 12/1/25 9:22 PM, Arne Vajh|+j wrote:

What does one link with to make a program using CMA_ functions
run?

Linking with sys$share:cma$open_rtl does not give any link
errors.

But it seems like whatever I call then I get:

%CMA-F-EXISTENCE, object referenced does not currently exist

So I guess I should be linking with something else. But what?

VMS 9.2-3 if it matters.

Isn't there an image called CMA$TIS_SHR?
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.os.vms

On 12/1/2025 10:29 PM, Craig A. Berry wrote:

On 12/1/25 9:22 PM, Arne Vajh|+j wrote:

What does one link with to make a program using CMA_ functions
run?

Linking with sys$share:cma$open_rtl does not give any link
errors.

But it seems like whatever I call then I get:

%CMA-F-EXISTENCE, object referenced does not currently exist

So I guess I should be linking with something else. But what?

VMS 9.2-3 if it matters.

Isn't there an image called CMA$TIS_SHR?

Yes.

I tried adding that, adding PTHREAD$RTL in various combinations.

Same error.

I also tried on VMS Alpha - same problem. So it is not a x86-64
problem - I am doing something wrong.

Arne

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.os.vms

On 12/2/2025 9:50 AM, Arne Vajh|+j wrote:

On 12/1/2025 10:29 PM, Craig A. Berry wrote:

On 12/1/25 9:22 PM, Arne Vajh|+j wrote:

What does one link with to make a program using CMA_ functions
run?

Linking with sys$share:cma$open_rtl does not give any link
errors.

But it seems like whatever I call then I get:

%CMA-F-EXISTENCE, object referenced does not currently exist

So I guess I should be linking with something else. But what?

VMS 9.2-3 if it matters.

Isn't there an image called CMA$TIS_SHR?

Yes.

I tried adding that, adding PTHREAD$RTL in various combinations.

Same error.

I also tried on VMS Alpha - same problem. So it is not a x86-64
problem - I am doing something wrong.

Found it.

Second argument to pthread_create is a pthread_attr_t*.

NULL works fine.

Second argument to cma_thread_create is a cma_t_attr*.

NULL gives the error above.

A cma_t_attr memset to zero works.

Arne

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.os.vms

On 12/2/2025 11:18 AM, Arne Vajh|+j wrote:

Second argument to pthread_create is a pthread_attr_t*.

NULL works fine.

Second argument to cma_thread_create is a cma_t_attr*.

NULL gives the error above.

A cma_t_attr memset to zero works.

And now I found some documentation for cma_.

The right solution is apparently to call with
cma_c_null !

Arne

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.os.vms

On 12/4/2025 9:05 AM, Arne Vajh|+j wrote:

On 12/2/2025 11:18 AM, Arne Vajh|+j wrote:

Second argument to pthread_create is a pthread_attr_t*.

NULL works fine.

Second argument to cma_thread_create is a cma_t_attr*.

NULL gives the error above.

A cma_t_attr memset to zero works.

And now I found some documentation for cma_.

The right solution is apparently to call with
cma_c_null !

Arne

When all else fails, RTFM ..
--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.os.vms

On 12/9/2025 12:23 AM, Dave Froble wrote:

On 12/4/2025 9:05 AM, Arne Vajh|+j wrote:

On 12/2/2025 11:18 AM, Arne Vajh|+j wrote:

Second argument to pthread_create is a pthread_attr_t*.

NULL works fine.

Second argument to cma_thread_create is a cma_t_attr*.

NULL gives the error above.

A cma_t_attr memset to zero works.

And now I found some documentation for cma_.

The right solution is apparently to call with
cma_c_null !

When all else fails, RTFM ..

Or as they say "Amazing how a few hours of creative
experimentation can save several minutes of reading
the documentation".

In this case the first problem was to find the documentation
because this API seems to have been removed from documentation
30 years ago.

Arne


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.os.vms

In article <69382175$0$677$14726298@news.sunsite.dk>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:

On 12/9/2025 12:23 AM, Dave Froble wrote:

On 12/4/2025 9:05 AM, Arne Vajh|+j wrote:

On 12/2/2025 11:18 AM, Arne Vajh|+j wrote:

Second argument to pthread_create is a pthread_attr_t*.

NULL works fine.

Second argument to cma_thread_create is a cma_t_attr*.

NULL gives the error above.

A cma_t_attr memset to zero works.

And now I found some documentation for cma_.

The right solution is apparently to call with
cma_c_null !

When all else fails, RTFM ..

Or as they say "Amazing how a few hours of creative
experimentation can save several minutes of reading
the documentation".

In this case the first problem was to find the documentation
because this API seems to have been removed from documentation
30 years ago.

That should tell you something. :-)

- Dan C.

--- Synchronet 3.21a-Linux NewsLink 1.2