Hi

Are there any known issues with using C$LOCKPID on Red Hat. 

When doing CALL C$LOCKPID GIVING W-PID, if I step through the call in the debugger, it initially gets he the correct PID and then on exiting the READ, W-PID is immediately reset to 0. It is working fine on SUSE Linux, so just checking if its a known issue, or f there is a workaround. 

thank you

I am not aware of any issues with C$LOCKPID on RHEL. What version of the product and OS are you testing with? I can try to reproduce it here. Thank you

Hi Martin, thanks for replying.

I am testing on RHEL 8, with ACU 9.5

In the debugger if you execute the READ with a 'P' command you never see  W-PID getting set, it shows 0, and jumps to the next command, however if you execute the READ with 'S' it first shows the PID, then if you 'S' again (still on the READ command) , it zeros out then jumps  the next command.

You have to add W-PID as a monitored variable in the debugger with a break on change of value.

Hi

Are there any known issues with using C$LOCKPID on Red Hat. 

When doing CALL C$LOCKPID GIVING W-PID, if I step through the call in the debugger, it initially gets he the correct PID and then on exiting the READ, W-PID is immediately reset to 0. It is working fine on SUSE Linux, so just checking if its a known issue, or f there is a workaround. 

thank you

Hi

Are there any known issues with using C$LOCKPID on Red Hat. 

When doing CALL C$LOCKPID GIVING W-PID, if I step through the call in the debugger, it initially gets he the correct PID and then on exiting the READ, W-PID is immediately reset to 0. It is working fine on SUSE Linux, so just checking if its a known issue, or f there is a workaround. 

thank you