You can obtain both an SVC dump and a summary dump through the SDUMPX macro. You can obtain a stand-alone dump by asking the operator to request one for you.
When you use SDUMPX to request an SVC dump, you also get a summary dump by default. Summary dumps can contain up to 4 megabytes (4MB) of data, so the application might plan on receiving about 3.5MB of trace data. If your trace buffers are much larger than 3.5MB, consider suppressing the summary dump and externalizing the trace data through the SVC dump only.
See z/OS MVS Diagnosis: Tools and Service Aids for information about the stand-alone dump program (SADMP).
Many components can locate their CTRACE buffers in a dump without the USERDATA supplied by a CTRACE DEFINE operation. IBM® advises such components to supply a CTRACE parmlib statement during IPCS session initialization. This allows the CTRACE subcommand to associate the name of the component with the name of the format table supplied by the component. In turn, this permits the component CTRACE buffers to be located and processed regardless of whether a dump contains SDATA=(SQA) information, which is the traditional way that the CTRACE subcommand determines the name of the format table for a component.