Dynare v4.2.0 keeps complains warning when run mod file

Anybody can help to shut off the noisy warning. The warning keeps showing up whenever I run mod files.

Warning: The RandStream.setDefaultStream static method will be removed in a future release. Use
RandStream.setGlobalStream instead.

In RandStream.RandStream>RandStream.setDefaultStream at 456
In set_dynare_seed at 35
In global_initialization at 319
In welfare_loss at 14
In dynare at 132

Please update Dynare. If you need 4.2, you need to identify the warning identifier and shut it off. If this was the last warning, you can use

and then

[quote=“jpfeifer”]Please update Dynare. If you need 4.2, you need to identify the warning identifier and shut it off. If this was the last warning, you can use

[msgstr, msgid] = lastwarn

and then

warning('off',msgid)

It does not work. Here is the info.

[msgstr, msgid] = lastwarn
msgstr =
The RandStream.setDefaultStream static method will be removed in a future release. Use RandStream.setGlobalStream instead.
msgid =
MATLAB:RandStream:SetDefaultStream
warning(‘off’,msgid)
dynare welfare_loss

Configuring Dynare …
[mex] Generalized QZ.
[mex] Sylvester equation solution.
[mex] Kronecker products.
[mex] Sparse kronecker products.
[mex] Bytecode evaluation.
[mex] k-order perturbation solver.
[mex] k-order solution simulation.

Starting Dynare (version 4.2.0).
Starting preprocessing of the model file …
Found 22 equation(s).
Evaluating expressions…done
Computing static model derivatives:

  • order 1
    Computing dynamic model derivatives:
  • order 1
  • order 2
    Processing outputs …done
    Preprocessing completed.
    Starting MATLAB/Octave computing.

Warning: The RandStream.setDefaultStream static method will be removed in a future release. Use
RandStream.setGlobalStream instead.

In RandStream.RandStream>RandStream.setDefaultStream at 456
In set_dynare_seed at 35
In global_initialization at 319
In welfare_loss at 15
In dynare at 132
Total computing time : 0h00m01s

Sorry, but I don’t have a setup where I can test this. You should probably just ignore the warning or update your system.