Skip to main content
Environ:  UV 11.2.5 on RHEL7

I noticed today that when I run 'LIST.READU'  if the locked item ID is longer than 63 characters I see the following
  1. The Item ID is truncated visually at the 63rd character
  2. The output does not stop at the end of the page

After capturing the output via wIntegrate I noticed that the 64th character is actually a control char (so far I have observed char(3), char(4) and char(14) as the truncating character).

I also tested using the unix command 'list_readu', as well as the 'LIST.READU INTERNAL' variation.
All produced the same result.

So is this normal behaviour for the command when dealing with longer Item ID's?
Is this as a result of the lock table truncating the ID, or is it just a reporting problem?
Is there any significance to the character value at the 64 position in the ItemID?
Environ:  UV 11.2.5 on RHEL7

I noticed today that when I run 'LIST.READU'  if the locked item ID is longer than 63 characters I see the following
  1. The Item ID is truncated visually at the 63rd character
  2. The output does not stop at the end of the page

After capturing the output via wIntegrate I noticed that the 64th character is actually a control char (so far I have observed char(3), char(4) and char(14) as the truncating character).

I also tested using the unix command 'list_readu', as well as the 'LIST.READU INTERNAL' variation.
All produced the same result.

So is this normal behaviour for the command when dealing with longer Item ID's?
Is this as a result of the lock table truncating the ID, or is it just a reporting problem?
Is there any significance to the character value at the 64 position in the ItemID?
Hi Gregor,
Internally the lock table holds a maximum of 64 characters for a record id.
As best as I can tell, the remainder of the key beyond character 63 is used to uniquely identify the record id and that is what is showing up in position 64.
So the output you are seeing with the LIST.READU command is expected.
Hopefully that answers your question. If not, please let me know.
Thank you.
Neil
Environ:  UV 11.2.5 on RHEL7

I noticed today that when I run 'LIST.READU'  if the locked item ID is longer than 63 characters I see the following
  1. The Item ID is truncated visually at the 63rd character
  2. The output does not stop at the end of the page

After capturing the output via wIntegrate I noticed that the 64th character is actually a control char (so far I have observed char(3), char(4) and char(14) as the truncating character).

I also tested using the unix command 'list_readu', as well as the 'LIST.READU INTERNAL' variation.
All produced the same result.

So is this normal behaviour for the command when dealing with longer Item ID's?
Is this as a result of the lock table truncating the ID, or is it just a reporting problem?
Is there any significance to the character value at the 64 position in the ItemID?
Thanks Neil.
That 64th character can play havoc with terminal emulators.
We have a tvi965 that reacts to having char(3) sent to it by responding with a terminal id. This is taken as user input and the user is suddenly looking at page 6 or 7 of the lock table not page 1!
I have had create a wrapper to truncate the ID at 63 characters and add "+" if there is a 64th to indicate the ID is longer than can be shown.
Terms & ConditionsAccessibility statement