The input file used as the Index_Dump_File has a line which has the index type StgPool and contains an allocSize 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 are examples of lines with index type StgPool:
[StgPool]::8,testpool5,0,4096,1,16777216,0,0,80,13164,pool5 description [StgPool]::9,testpool6,0,4096,32,16777216,0,0,80,25965,pool6 descriptionThe Index_Dump_file value of the field allocSize is in 4K byte blocks. Note the values of allocSize in the example lines above are 1 and 32. Note that the mkpool parameter -allocsize value when used must be either 4 or 128 kilobytes. To calculate the -allocsize value we multiply allocSize by 4. In the above [StgPool] examples, the -allocsize values are 1*4=4 and 32*4=128.
The resulting TankSysCLI.auto output file created by sys_metadata_dr.pl should then have mkpool commands that have -allocsize values of 4 or 128 if the input file allocSize is nonzero (1 or 32).
Here are the coresponding examples of the valid mkpool commands:
mkpool -partsize 16 -allocsize 4 -thresh 80 testpool5 mkpool -partsize 16 -allocsize 128 -thresh 80 testpool6Check the input file used for the Index_Dump_File and determine which StgPool line that is incorrect and has a partSize that is not valid. Under normal operation, the allocSize 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