Allow ZCDNV to set a configurable number of NVPs that would be displayed on Dump messages sent to prime cras console

As we increase the use of Name-Value Pairs for saving information useful in Troubleshooting and for Realtime Runtime Metrics Collection (RTMC), the Name-Value Pair (NVP) area is becoming increasingly important to our application developers to rapidly troubleshoot test and production issues.  All our legacy Communications packages, newer Communications packages such as REST Services, and some TPF applications have been updated to store Input Message/Inbound Data payload, Communications path, Communcations application routing information, embedded Service for Structured Data, End to End tracking ID, REST Operation ID, User Identifier, User Role, User Location, and other useful information.   The NVP area now provides a consolidated view of what the message was, how the message came into the system, who drove the message into the system, and what it was trying to do which is extremely useful in troubleshooting producton issues. We'd like to see ZCDNV updated to be able to set a configurable number of NVPs to be displayed on the Dump messages sent to the prime cras console rather than the current limit of 3 NVPs. This is extremely useful especially since the majority of Dumps are NODUMP'd in our TPF systems so the data is not available to look at via the dump so the NVPs on the dump messsages allow for better pattern recognition to determine if the dumps are impacting only one or many Comms paths, Users, Locations, etc...when multiple dumps are issued.  Since each IBM zTPF customer has different uses for the NVPs and may not want additional prime cras console clutter, it would be better to have the number of NVPs configurable to the TPF shop rather than a fixed number of NVPs.