Avoid writing over unarchived JT files after message EQQN180W is issued by controller

In the subject PMR 65928,L6Q,000 (the files for which are available under internal PMR 53795,999,000 ) the JTARC filled up (B37) after which all the JT files were used but could NOT be copied to the JTARC file. This resulted in EQQZ045E for normal mode manager task (NMM). However instead of immediately correcting the problem by making the JTARC file LARGER (so that the JTxx files could be archived) a restart of the controller was performed. Message EQQN180W was correctly issued since the current JT file and the last archived JT file were the same. However-- the next action was to switch to the next JT file and begin writing to it-- but this JT file had never been archived either (in fact, at this point NONE of the JT01-JT05 files had been archived). It seems a check is missing in the JT RECOVERY. A JT file which has not been archived should NEVER be overwritten as this causes loss of tracking records. In fact in the subject PMR, two JT files were overwritten (causing the loss of 100,000 tracking records as each JT file held 50,000 records) before the problem was realized and the JTARC file increased in size. This caused a very difficult manually recovery as thousands of jobs were in the wrong state (example- IWSz showed the job in started status but it had already been completed).