Skip to main content

After performing an upgrade from UniVerse 12.1 to 12.2.1 - we receive the message "Your VOC is out of date. Update to current release (Y/N)?" on the initial LOGTO on each account.

Is there a way to just complete these VOC updates en-masse for all accounts? 

Your VOC is out of date. Update to current release (Y/N)?Y

Your VOC is configured for PICK compatibility

Updating your "VOC" file.  (Each "*" = 10 records)

***********************************************************

****

6 item(s) were removed from your VOC file and placed in

file "&TEMP&" to prevent them from being overwritten.

 

Updating your "D_VOC" file.  (Each "*" = 10 records)

*

11 item(s) were removed from your VOC file and placed in

file "DICT &TEMP&" to prevent them from being overwritten.

After performing an upgrade from UniVerse 12.1 to 12.2.1 - we receive the message "Your VOC is out of date. Update to current release (Y/N)?" on the initial LOGTO on each account.

Is there a way to just complete these VOC updates en-masse for all accounts? 

Your VOC is out of date. Update to current release (Y/N)?Y

Your VOC is configured for PICK compatibility

Updating your "VOC" file.  (Each "*" = 10 records)

***********************************************************

****

6 item(s) were removed from your VOC file and placed in

file "&TEMP&" to prevent them from being overwritten.

 

Updating your "D_VOC" file.  (Each "*" = 10 records)

*

11 item(s) were removed from your VOC file and placed in

file "DICT &TEMP&" to prevent them from being overwritten.

There is no mass account update command that I know of.  You can create a script on your o/s to cd to each account and perform a "uv ACCOUNT.UPDATE".  This will execute the ACCOUNT.UPDATE command without generating the account update query.  Another option would be to create a paragraph to walk to all the accounts and perform an ACCOUNT.UPDATE.  I have not worked with version 12 but versions 11 and under don't trigger an account update when you perform a LOGTO.  The update query only appears when you enter UniVerse from the o/s.

In either case you will need to take two things into consideration.  First is your LOGIN paragraph.  It will get invoked once you enter UniVerse.  You will need to bypass this for any solution you come up with.  The second item is the contents of the &TEMP& file.  Unless the VOC files are all identical across your accounts, you will want to make sure they are purged before you update the accounts.  Otherwise you will end up mixing the commands from the previous account upgrade.

After performing an upgrade from UniVerse 12.1 to 12.2.1 - we receive the message "Your VOC is out of date. Update to current release (Y/N)?" on the initial LOGTO on each account.

Is there a way to just complete these VOC updates en-masse for all accounts? 

Your VOC is out of date. Update to current release (Y/N)?Y

Your VOC is configured for PICK compatibility

Updating your "VOC" file.  (Each "*" = 10 records)

***********************************************************

****

6 item(s) were removed from your VOC file and placed in

file "&TEMP&" to prevent them from being overwritten.

 

Updating your "D_VOC" file.  (Each "*" = 10 records)

*

11 item(s) were removed from your VOC file and placed in

file "DICT &TEMP&" to prevent them from being overwritten.

Sorry!  Got the command muddled.  The correct command is UPDATE.ACCOUNT.

After performing an upgrade from UniVerse 12.1 to 12.2.1 - we receive the message "Your VOC is out of date. Update to current release (Y/N)?" on the initial LOGTO on each account.

Is there a way to just complete these VOC updates en-masse for all accounts? 

Your VOC is out of date. Update to current release (Y/N)?Y

Your VOC is configured for PICK compatibility

Updating your "VOC" file.  (Each "*" = 10 records)

***********************************************************

****

6 item(s) were removed from your VOC file and placed in

file "&TEMP&" to prevent them from being overwritten.

 

Updating your "D_VOC" file.  (Each "*" = 10 records)

*

11 item(s) were removed from your VOC file and placed in

file "DICT &TEMP&" to prevent them from being overwritten.

hi,

I'm used to update all accounts with external verbe 'updaccount' 

here is the linux script to search all directory with a VOC file then cd and updaccount 

export ICI=`pwd`
echo "updaccount from these level (1 level)"
echo -n "Ok ?[y/N]"
read rep
if [ "x$rep" != "xy" ] && [ "x$rep" != "xY" ];
  then
    echo user abort
    exit 1
fi 
echo "" > /tmp/account.updaccount.found.$$
ls | while read tt; do
  if [ -d $ICI/$tt ];
    then
      if [ -e $ICI/$tt/VOC ];
        then
          echo $ICI/$tt 
          echo $ICI/$tt >> /tmp/account.updaccount.found.$$
          cd $ICI/$tt
          updaccount
          cd $ICI
      fi
  fi
done
exit 0

and here a script on powershell.exe for windows plateform 

$basuvdb = ... 
Get-ChildItem -Path "$baseuvdb"-Directory | ForEach-Object { 
     set-location -Path "$($_.FullName)" 
     if (test-path -path "VOC" -pathtype Leaf) {
                 updaccount 
    }
}

Feel free to clear &TEMP& before updaccount ; to check what was replaced on you VOC.

I suggest to update your NEWACC and NEWACC,flavor with your custom verbs the you deploy the correct value.

I hope this help

manu

Terms & ConditionsAccessibility statement