topic Re: LIB$WAIT & COBOL/VMS in Operating System - OpenVMS

LIB$WAIT & COBOL/VMS

Alex Bartonek — Fri, 21 Oct 2005 23:03:00 GMT

May or may not be the proper forum but its worth a shot..

Currently in my COBOL program I am using the lib$wait routine. Its being called in block of code that is being run via a perform loop.

For testing purposes I set the initial wait time to 10 seconds. The first time the perform loop runs through and hits the LIB$WAIT call it waits for 10 seconds. If there is no work to do it calls lib$wait but completely skips the 10 second count from then on as if it had met the 10 second wait criteria.

Here is my call:
CALL "LIB$WAIT" USING BY REFERENCE duration, libnowake, float-type

duration is set to 10
libnowake is set to 0 or 1, but I've also substituted 'OMITTED' in place of libnowake..none of these values fixed the problem.

Current versions of software pertinent to this problem:
OVMS = 7.3-2, roll-up patch 4
COBOL 2.8
RDB 7.1-411

I thank you'all in advance!

-Alex

Re: LIB$WAIT & COBOL/VMS

Hein van den Heuvel — Fri, 21 Oct 2005 23:52:13 GMT

Hmmm,

I would have suspected the Control flags arguments: "The flags argument is the address of a longword integer that contains the control flags. The following flag is defined: Bit 0, LIB$K_NOWAKE LIB$WAIT will not wake in the case of an interrupt.

This is an optional argument. If omitted, the default is 0, and LIB$WAIT
will wake in the case of an interrupt. "

As discussed in:
https://forums2.itrc.hp.com/service/forums/questionanswer.do?threadId=948325

But it sounds like you already tried passing the integer value 1 as argument there.

I would triple-check and print out all arguments to lib$wait just before it being called.

Hein.

Re: LIB$WAIT & COBOL/VMS

Garry Fruth — Sat, 22 Oct 2005 00:38:23 GMT

I'd add to Hein's suggestion, add the GIVING clause and see that the return status is normal (1).

Re: LIB$WAIT & COBOL/VMS

Ian Miller. — Sat, 22 Oct 2005 11:48:55 GMT

Re: LIB$WAIT & COBOL/VMS

Ian McKerracher_1 — Sat, 22 Oct 2005 14:24:59 GMT

Hello Alex,

It may be worth checking the variable which you use as the 'seconds' argument. LIB$WAIT requires a F-FLOATING value but your variable may not be declared as a COMP-1. If the variable is declared correctly is the compiler using an unexpected floating point type.

Regards,

Ian

Re: LIB$WAIT & COBOL/VMS

Arch_Muthiah — Sat, 22 Oct 2005 21:51:36 GMT

Alex,

could you please try this once...

01 duration comp-1.
....
move 10.0 to duration.
CALL "LIB$WAIT" using by reference duration.

-----------------------------
The other way....

and other doubt I have is when I read the VMS help about lib$wait, in which they mentioned about the thrid argument float type....

float-type
"This is an optional argument. If omitted, the default is F_floating. F_floating is
the "--required--" float-type when LIB$WAIT is called from a module written in a language that "--prototypes--" functions"

Looks like we should use this third argument (LIB$K_VAX_F -- Alpha, LIB$K_IEEE_S --- IA64).

So try float-type = LIB$K_VAX_F alternatively with LIB$K_NOWAKE and LIB$K_NOWAIT control flags. Just trial only...

If it doesn't work, could please past your PERFORM loop code?

Archunan

Re: LIB$WAIT & COBOL/VMS

Alex Bartonek — Sun, 23 Oct 2005 21:27:44 GMT

Ok.. the problem was in the declaration of the libnowait variable..

I was using comp-1, it should have been pic 9(5) comp value 1.

-Alex

Re: LIB$WAIT & COBOL/VMS

Alex Bartonek — Sun, 23 Oct 2005 21:28:19 GMT

solution was to declare the variable as:

pic 9(5) comp value 1.