On a D3 7.4 on Windows system there has been a recent spate of
 ‘illegal or missing modifier used in defining the file area(s)’
errors at regular login, the consequence being that pib# are being allocated in a higher range than typical which is causing screen format issues in Telnet/CUI applications for the users.
N.B. Telnet ports are not nailed in the PIB Configuration and there is nothing in the application which restricts terminal number ranges used, so higher pib# shouldn’t be an issue
Any guidance on the underlying cause of  and how to rectify?
Is there a way to reset next available pib# back to 1 without a VME stop & start?