The input file used as the Index_Dump_File has a line which has the index type StgPool and contains a partSize that is not valid.
Here is the syntax of the line with index type StgPool:
[StgPool]: ID, Name, lastAlloc, blockSize, allocSize, partSize, volCount, isDefault, alertPct, allocatable, descriptionHere is an example of a line with index type StgPool:
[StgPool]::3,testpool0,0,4096,0,16777216,0,0,80,16552,pool0 descriptionNote that the mkpool parameter -partsize value must be either 16, 64, or 256 megabytes. The Index_Dump_file value of the field partSize is in bytes. To calculate the -partsize value, we normalize by 2^20 so we divide partSize in bytes by 1048567 and round down to an integer. In the above [StgPool] example the -partsize value is 16 because 'int ( 16777216 / 1048567 )' is equal to 16.
When the Index_Dump_file has the correct partSize values, then the resulting TankSysCLI.auto output file created by sys_metadata_dr.pl will have mkpool commands that have -partsize values of 16, 64, or 256. Here are some examples of valid mkpool commands:
mkpool -partsize 16 -thresh 80 testpool1 mkpool -partsize 64 -thresh 80 testpool2 mkpool -partsize 256 -thresh 80 testpool3Check the input file used for the Index_Dump_File and determine the StgPool line that is incorrect and has a partSize that is not valid. Under normal operation the partSize should always have a valid value.
Run the "sfscli startmetadatacheck" command to check for any metadata corruptions. Then consult with IBM Service on how to proceed.
Parent topic: System metadata messages