When reviewing a VLSUTIL Library listing like this:
PROD.SYSTEMS.IDDAT LIBRARY LISTING 08/27/25 0923 PAGE 0001
NAME DESCRIPTION ADDED UPDATED RCDS BLKS
LSTMEM1LIST @ 04/27/25 04/27/25 2 2 (The @ is in cc 23)
LSTMEM2LIST @ 04/27/25 04/27/25 2 2
. . .
LIBRARY NAME LENGTH: 24
How do we determine the proper name of the VLS members to use in a LIST command. I tried this unsuccessfully:
LIST LSTMEM2LIST/4040404040404040404040/@/40/ -> MEMBER NOT FOUND - LSTMEM2LIST/4040404040404040404040/@/40/
Entering the COLS command to verify everything was no help:
---+----1----+----2----+-
LSTMEM1LIST @
LSTMEM2LIST @
Not reviewing the columns shown by the COLS command could cause your data to reflect starting in column 2 instead of column 1.
The Library listing shows the member name length (in this case, it is 24). Now, looking closely at the COLS ruler in the description will show that the ruler starts in column 2 instead of column 1. This would lead to using a bad definition. In this case, the correct name has 10 spaces before the @ and 2 spaces after it, not one as in the original problem display.
As an alternative to the Hex format used in the description, you can now enclose the name in quotes and this will more easily include the spaces. In this case, the LIST statement can be specified as either of these options:
HEX /
LIST LSTMEM2LIST/40404040404040404040/@/4040/
or
LIST 'LSTMEM2LIST @ '
As always, please contact Broadcom support for Datacom if you have further questions.