SAVEDLISTS Key Length

UniData 8.2.2

Hi All,

Does anyone know if Rocket have recently changed the key length for the SAVEDLISTS file? On older versions I had no issues saving keys like -

TRAWL*LAZ.PROGS*197609

I know about the potential 000-999 issue when the OS tags the chunk numbers onto the end of the key, but I could at least save the list. Now, the response I get from the system is - 

can not open file: 'SAVEDLISTSTRAWL*LAZ.PROGS*197609

I tried tagging some alphas onto the end of the key to get around the numeric chunking clash, but it didn't make any difference. If I hardcode the list key to 'BOB', it saves the list as BOB000 just fine.

I don't really want to reduce the length of the key because I want to keep it unique and also visibly descriptive. 

Thanks

Leon

@Leon Pearce

I don't know if your saw my last update, this is a windows restriction, windows does not allow '*' in a file name.
SAVEDLISTS is a directory and each 'list or record' in SAVEDLISTS would be a file.

Thanks,
Jonathan
​

UniData 8.2.2

Hi All,

Does anyone know if Rocket have recently changed the key length for the SAVEDLISTS file? On older versions I had no issues saving keys like -

TRAWL*LAZ.PROGS*197609

I know about the potential 000-999 issue when the OS tags the chunk numbers onto the end of the key, but I could at least save the list. Now, the response I get from the system is - 

can not open file: 'SAVEDLISTSTRAWL*LAZ.PROGS*197609

I tried tagging some alphas onto the end of the key to get around the numeric chunking clash, but it didn't make any difference. If I hardcode the list key to 'BOB', it saves the list as BOB000 just fine.

I don't really want to reduce the length of the key because I want to keep it unique and also visibly descriptive. 

Thanks

Leon

If this list is created on a *nix machine, the '*' is allowed in the file name. If you want to take it over to a Windows machine you can use a utility like WinSCP or convert the name yourself. If you convert it to a standard URL, it can exist on either box and not have an issue. To that end, using WinSCP or manually, any '*' character will be converted to '%2A' in the name and it can then be stored on the Windows box. 
There are other characters that should be considered, as well:
Original Character     URL conversion
' ' (space)                         %20
" (double quote)           %22
* (asterisk)                      %2A
/ (forward slash)          %2F
: (colon)                           %3A
<                                          %3C
>                                          %3E
?                                          %3F
(back slash)                %5C
| (pipe)                              %7C

While this specific issue relates to a list name, U2 allows some or all of these characters to be used in record ID's. Creating a function that allows conversion of a string to/from a URL format can be helpful in moving data from ​​U2 hashed files to Type 1 or Type 19 files. Simply convert the the ID to a URL, write it out or, if importing, convert the URL to a U2 friendly string before writing it to you hashed file.

So, a U2 ID "JOHN*Q*PUBLIC" would become "JOHN%2AQ%2APUBLIC" which is valid in either OS.