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
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
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 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.
I assume you mean 9.2.5?
I have tested with 9.2.5 on RHEL 8 and it works correctly for me. Can you upload a sample program that reproduces the issue so I can try with that?
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
I use C$LOCKPID on Linux Red Hat 8.5 with ACU 10.4.1 and it works correctly. I handled the PROCESS-ID variable in the declarative section of the file after opening it in I-O mode and reading it.
example:
PROCEDURE DIVISION.
*----------------------*
DECLARATIVES.
ERRORE-ANCLFO SECTION.
USE AFTER ERROR PROCEDURE ON ANCLFO.
GESTIONE-ERRORE-ANCLFO.
IF FILE-STATUS = "99"
CALL "C$LOCKPID" GIVING PROCESS-ID
END-IF
END DECLARATIVES.
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 Mathew,
You might actually be using software originally developed by myself :)
I have relied on C$LOCKPID for many years. I have actually built it into the FG4 constructor - along with many other constructor enhancements - as an automatic feature.
Feel free to contact me if you have not come right (cobsolv@global.co.za)
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
