I believe there may be several issues.
1) A valid Cobol element name should not contain the "(" or ")" symbols, so the attached example removes those.
2) Most Cobol copybooks begin in column 7. The fist 5 characters are reserved for line numbers and column 6, when it contains an "*" is considered a comment line. So, I shifted your copybooks over.
3) Your input data is in UTF format format. Many times when dealing with mainframe data, you need to apply an IBM037 codepage conversion to take care of EBCDIC characters. Your example payloads are clear text so I did NOT apply a codepage conversion. Your live data may need this conversion so you will need to check on that with the Dev team.
Once I executed steps 1 & 2 above, I could get your copybook to parse into a bundle.
The next step is to identify what value constitutes the identification of a request and maps it to a given copybook and similarly a response mapping. For sake of example, I used the incoming request queue name located in the payload as the value that aligns requests & responses to the copybooks. This is likely incorrect, but it was the only thing I could figure out by looking at the sample payload.
I generated a simple copybook mapping. Then took your R/R pairs and ran them through a fictitious R/R pair from JMS recorder. The attached DT project file has a fake VSI that you can look at to see an example mapping of the request document and bundle. I forgot to include a Copybook DPH on the response side, so the response looks like a response payload without the Cobol copybook mapping applied. You can simply take the R/R pairs and apply this DPH to see how it looks in the response.
Hopefully, this will get you moving in the right direction.