We're running Entrinsik's Informer against Unidata 8.2.1 on Redhat 7, and the logs show an error suggesting that we increase the VFIELDSIZE.
Their recommendation is to increase it - globally - to 10K, which I'm happy to do.
Is there a way to get it to take effect without having to restart Unidata?
Page 1 / 1
We're running Entrinsik's Informer against Unidata 8.2.1 on Redhat 7, and the logs show an error suggesting that we increase the VFIELDSIZE.
Their recommendation is to increase it - globally - to 10K, which I'm happy to do.
Is there a way to get it to take effect without having to restart Unidata?
Their recommendation is to increase it - globally - to 10K, which I'm happy to do.
Is there a way to get it to take effect without having to restart Unidata?
VFIELDSIZE is an environment variable so needs to be set before the udt or uniobjects process is spawned for it to work. You do not need to restart UniData you just need to make sure it's set before entering udt.
From the Bourne or Korn shell:
# VFIELDSIZE=10240 ; export VFIELDSIZE
# $UDTBIN/udt
The same principle applies for a UniObjects, UO.NET, ODBC, UOJ, ODBC and UniOLEDB connections for these you need to set the value before the unirpcd service is started.
# $UDTBIN/startunirpcd
Unirpcd is started
Note there is a stopunirpcd script that you use to stop the unirpcd without stopping UniData.
​​
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.