Hey all:
Windows Server 2016
Version 8.3.2, Build 2000
UDT Configuration: Server, 64-bit(x64)
The manual provides the following syntax for RESIZE:
RESIZE {DICT} filename modulo {DYNAMIC | STATIC} [BLOCK.SIZE n]
D_FUND_ADVICE.LIS recommends we resize DICT FUND.FILE from 7 to 13 and BLOCK SIZE from 1024 to 4096.
udtconfig shows SHM_LBA=4096.
Yet when I try to resize, this is the result:
RESIZE DICT FUND.FILE STATIC 13 BLOCK.SIZE 4096
-------------------------------^
syntax error
RESIZE DICT FUND.FILE STATIC 13 BLOCKSIZE 4096
-------------------------------^
syntax error
What am I missing?
------------------------------
Rich Lucibella
Director
Rocket Forum Shared Account
------------------------------
Hey all:
Windows Server 2016
Version 8.3.2, Build 2000
UDT Configuration: Server, 64-bit(x64)
The manual provides the following syntax for RESIZE:
RESIZE {DICT} filename modulo {DYNAMIC | STATIC} [BLOCK.SIZE n]
D_FUND_ADVICE.LIS recommends we resize DICT FUND.FILE from 7 to 13 and BLOCK SIZE from 1024 to 4096.
udtconfig shows SHM_LBA=4096.
Yet when I try to resize, this is the result:
RESIZE DICT FUND.FILE STATIC 13 BLOCK.SIZE 4096
-------------------------------^
syntax error
RESIZE DICT FUND.FILE STATIC 13 BLOCKSIZE 4096
-------------------------------^
syntax error
What am I missing?
------------------------------
Rich Lucibella
Director
Rocket Forum Shared Account
------------------------------
Rich,
The BLOCK.SIZE is as below - a multiplier, not a byte value :
The size, expressed as a multiplier, of each group in a hashed file.
If you specify a block size multiplier of 0, UniData creates 512-byte Groups. A block size multiplier of 1 represents 1024 bytes, 2 represents 2048 bytes, and so on. For 32-bit files, the maximum block size multiplier is 16.
If specifying a larger value 16 will be used. For 64-bit (new at UniData 8.1.0), the block size limit is '2 GB - 1' (2,147,483,647). If the block size multiplier is not a power of 2, it will be rounded down to the nearest power of 2. See the CREATE.FILE help for more details on 64-bit files.
Hoping this helps.
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
Rich,
The BLOCK.SIZE is as below - a multiplier, not a byte value :
The size, expressed as a multiplier, of each group in a hashed file.
If you specify a block size multiplier of 0, UniData creates 512-byte Groups. A block size multiplier of 1 represents 1024 bytes, 2 represents 2048 bytes, and so on. For 32-bit files, the maximum block size multiplier is 16.
If specifying a larger value 16 will be used. For 64-bit (new at UniData 8.1.0), the block size limit is '2 GB - 1' (2,147,483,647). If the block size multiplier is not a power of 2, it will be rounded down to the nearest power of 2. See the CREATE.FILE help for more details on 64-bit files.
Hoping this helps.
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
BwaHaHa... I knew I was missing something. Thanks so much!
------------------------------
Rich Lucibella
Director
Rocket Forum Shared Account
------------------------------
Rich,
The BLOCK.SIZE is as below - a multiplier, not a byte value :
The size, expressed as a multiplier, of each group in a hashed file.
If you specify a block size multiplier of 0, UniData creates 512-byte Groups. A block size multiplier of 1 represents 1024 bytes, 2 represents 2048 bytes, and so on. For 32-bit files, the maximum block size multiplier is 16.
If specifying a larger value 16 will be used. For 64-bit (new at UniData 8.1.0), the block size limit is '2 GB - 1' (2,147,483,647). If the block size multiplier is not a power of 2, it will be rounded down to the nearest power of 2. See the CREATE.FILE help for more details on 64-bit files.
Hoping this helps.
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
Well, that just opened a whole new can of worms:
1) If I understand you and read the manual correctly:
RESIZE DICT CAP.FILE 3 BLOCK.SIZE 4
should result in a BLOCK SIZE of 4096, no?
2) If I've created a file without specifying the bit, it's created at 32BIT....
Would
RESIZE [FILE NAME] [MODULO] DYNAMIC 64BIT
convert it to 64BIT Addressing?
Thanks again-
Rich
------------------------------
Rich Lucibella
Director
Rocket Forum Shared Account
------------------------------
Well, that just opened a whole new can of worms:
1) If I understand you and read the manual correctly:
RESIZE DICT CAP.FILE 3 BLOCK.SIZE 4
should result in a BLOCK SIZE of 4096, no?
2) If I've created a file without specifying the bit, it's created at 32BIT....
Would
RESIZE [FILE NAME] [MODULO] DYNAMIC 64BIT
convert it to 64BIT Addressing?
Thanks again-
Rich
------------------------------
Rich Lucibella
Director
Rocket Forum Shared Account
------------------------------
Richard,
That's what I would expect - I've also copied some notes below:
| 64BIT |
Sets the addressing type of the file to 64-bit mode. This option is new at UniData 8.1.0. |
| 32BIT |
Sets the addressing type of the file to 32-bit mode. This is the default addressing type. This option is new at UniData 8.1.0. |
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
Hey all:
Windows Server 2016
Version 8.3.2, Build 2000
UDT Configuration: Server, 64-bit(x64)
The manual provides the following syntax for RESIZE:
RESIZE {DICT} filename modulo {DYNAMIC | STATIC} [BLOCK.SIZE n]
D_FUND_ADVICE.LIS recommends we resize DICT FUND.FILE from 7 to 13 and BLOCK SIZE from 1024 to 4096.
udtconfig shows SHM_LBA=4096.
Yet when I try to resize, this is the result:
RESIZE DICT FUND.FILE STATIC 13 BLOCK.SIZE 4096
-------------------------------^
syntax error
RESIZE DICT FUND.FILE STATIC 13 BLOCKSIZE 4096
-------------------------------^
syntax error
What am I missing?
------------------------------
Rich Lucibella
Director
Rocket Forum Shared Account
------------------------------
Rich,
Along side the introduction of the 64BIT keyword for CREATE.FILE, there is a also a documented environment variable to switch the default file creation bit mode from 32BIT to 64BIT, should you wish to create all your files as 64BIT. In UniVerse this is controlled with a configurable in the uvconfig file, in UniData it is controlled via an environment variable.
For more details see the 'Environment Variables For UniData' in the 'Administrating UniData on Windows and Unix Platforms' and review the details for UD_CREATE_64BIT
Regards,
Jonathan
------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------
Rich,
Along side the introduction of the 64BIT keyword for CREATE.FILE, there is a also a documented environment variable to switch the default file creation bit mode from 32BIT to 64BIT, should you wish to create all your files as 64BIT. In UniVerse this is controlled with a configurable in the uvconfig file, in UniData it is controlled via an environment variable.
For more details see the 'Environment Variables For UniData' in the 'Administrating UniData on Windows and Unix Platforms' and review the details for UD_CREATE_64BIT
Regards,
Jonathan
------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------
Got it. Found it. Did it.
Thanks, Jonathan.
Rich
------------------------------
Rich Lucibella
Director
Rocket Forum Shared Account
------------------------------
Hey all:
Windows Server 2016
Version 8.3.2, Build 2000
UDT Configuration: Server, 64-bit(x64)
The manual provides the following syntax for RESIZE:
RESIZE {DICT} filename modulo {DYNAMIC | STATIC} [BLOCK.SIZE n]
D_FUND_ADVICE.LIS recommends we resize DICT FUND.FILE from 7 to 13 and BLOCK SIZE from 1024 to 4096.
udtconfig shows SHM_LBA=4096.
Yet when I try to resize, this is the result:
RESIZE DICT FUND.FILE STATIC 13 BLOCK.SIZE 4096
-------------------------------^
syntax error
RESIZE DICT FUND.FILE STATIC 13 BLOCKSIZE 4096
-------------------------------^
syntax error
What am I missing?
------------------------------
Rich Lucibella
Director
Rocket Forum Shared Account
------------------------------
There are in fact two environment variables you can use
DEFAULT_FILE_IS_64BIT When set to 1, all SQL table files, hashed files and non-hashed files get created as 64BIT (without the need for the 64BIT keyword)
and
UD_CREATE_64BIT When set to 1, all hashed files get created as 64BIT (without the need for the 64BIT keyword)
Although not mentioned currently in the help for CREATE.FILE these are documented in the Administration Guide. The command reference manual will be updated to reference these variables in a latter release.
------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------
There are in fact two environment variables you can use
DEFAULT_FILE_IS_64BIT When set to 1, all SQL table files, hashed files and non-hashed files get created as 64BIT (without the need for the 64BIT keyword)
and
UD_CREATE_64BIT When set to 1, all hashed files get created as 64BIT (without the need for the 64BIT keyword)
Although not mentioned currently in the help for CREATE.FILE these are documented in the Administration Guide. The command reference manual will be updated to reference these variables in a latter release.
------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------
Thanks again, Jonathan.
Rich
------------------------------
Rich Lucibella
Director
Rocket Forum Shared Account
------------------------------