If a command is used in one context, it might produce one response, but in another context might produce a completely different format.
iTest response mapping automatically finds the appropriate response map based on applicability data. When more than one applicable map is found, then iTest will sort these based on applicable priority (a property of the response map) and try the highest priority first. But if the first one doesn't map correctly (i.e., produces response map errors), then it will move on and try the next one. If that one maps without errors, then it is used. If not, it will try the next, and so on.
Therefore, you can create multiple response maps for the same command, and set up the applicability data and priority appropriately. When you do this, you may want to name tokens and queries consistently among these different maps -- so that the same queries in the test case will work regardless of which of the maps ends up being used.
Attached zip file contains a test case, response maps and a session profile that demonstrates this. The test case uses CMD to perform two different ping commands that produce different formatted output.