Your comment: "I had only input, output copybooks, sample request and response pairs with me."
When you created your MQ R/R pairs, did you also include sidecar files? Your R/R pairs only contain the body of the request / response. The sidecar provides the ability to add the request / response JMS header information.
Refer here for some additional information:
Request/Response Pairs - DevTest Solutions - 10.1 - CA Technologies Documentation
In terms of the copybook mapping, you need to identify the request data content that will identify the copybook to DevTest. Perhaps, this data is a queue name or perhaps a value in the request has a specific piece of data that identifies a transaction name. Knowledge of the specific transactions is required to determine how the mapping will occur.
Consider everything that follows as a sample to give an idea.
Ensure the copybook_bundle.cbb file contains "startColumn":"6", "endColumn":"72" in its attributes. This tells the parser that the copybooks tagnames and picture clauses are standard Cobol layout.
Since you only have one request / response, use a simple mapping to identify the copybook. For example, indicate in the mapping.xml file that a value of SDMHEADR001 indicates to use the SDMKI214 copybook. In the long term, this will probably change, but to try to get a sample mapping working, create a copy of your mapping file that looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<payloads>
<payload name="TEST" type="request" matchType="all" key="COMPANY-NAME" value="SDMHEADR001" definesResponse="true">
<section name="requestBody">
<copybook key="CPY1" order="1" max="1">SDMKI214.txt</copybook>
</section>
</payload>
<payload name="TEST" type="response" matchType="payload" key="STATUS" value="SUCCESS">
<section name="responseBody">
<copybook key="CPY1" order="1" max="1">NHSAZB1C.txt</copybook>
</section>
</payload>
</payloads>
I did not see a cobol tagname in the response copybook, NHSAXB1C, that looks like it carries a value of "SUCCESS". I see a CSTPROFO-RSP-CD, but this field is only 3 characters long. Hopefully, your response contains the value "SUCCESS" in it somewhere; otherwise, the "value=" in the response-side mapping will need to contain some other value.
You may need to open a ticket with CA Support to get the entire flow to work.