Been a few years since I've used Mitz, but I remember seeing this every time I would make an online edit. I think it is memory allocated for online edits. I seem to remember there was somewhere where you could increase this number from 500 to a higher value. I also remember that as I would make more and more edits, the available "steps" would decrease, and I think when they got to zero, it would just ask if I wanted to increase it and I would say yes and carry on.
So basically it was never a problem as far as I could remember and never stopped me from doing what I had to do. I'm sure someone here will chime in with a more in-depth answer.
I have never had it go to zero, I believe it puts NOP's in places to allow an on-line change so if there are too many NOP's or the code you are changing will shift the code by more than the number of steps set in the compiler it will become a problem, the way round it is to compile & download the complete code, this will reset it back to the default 500 steps.
Some things you cannot do on-line download for example if you modify a function block (only valid in FBD/LAD) or you have a jump to a subroutine & the code moves the pointer too far then again the only option is to compile & download in stop mode.
NOP means No-Operation
Basically a NULL command used as a placeholder for an empty rung, and what I call a FYI rung - N.O.'s and compares at the beginning just to show the status of the bit or word when monitoring online
Sometimes a small change like removing a contact in a rung the download (well compile & download will put in a NOP (no operation) rather than shift up the whole program for example if you have a program that is 2000 instructions long but you delete an instruction in a rung at about 600 then rather than reduce the whole program (shift up) from 600 to 2000 it will only shift up the one ladder then insert a NOP, so the program is still 2000 instructions long.