Dumping XCA-attached CCL NCPs

Because CCL NCPs attached directly to VTAM® through an XCA major node follow the remote NCP model and use native NCP token-ring (NTRI) support, only those functions supported by remote token-ring attached NCPs are supported for CCL NCPs.

To summarize:

XCA-attached CCL NCPs support dynamic dumps sent directly to the host.
XCA-attached CCL NCPs support static dumps to disk, and the subsequent transfer of these static dumps to the host. (In the CCL environment, dumping a CCL NCP to disk means writing the NCP dump to a file in the Linux file system.)
XCA-attached CCL NCPs do not support static dumps sent directly to the host. This is true for both active and inactive (abended) NCPs.

To capture a static dump of an active XCA-attached CCL NCP, use the MODIFY DUMP command with ACTION=STORE. To capture a static dump of an inactive (abended) XCA-attached CCL NCP, you must preconfigure the CCL NCP to automatically dump to disk when it abends by ensuring that the Auto Dump/Load switch is set. You can then use the MODIFY DUMP command with ACTION=TRANSFER to transfer a static dump to the host for problem diagnosis.

Restriction: You cannot use the VTAM VARY ACT command with LOADFROM=HOST or LOADFROM=EXTERNAL to set the Auto Dump/Load switch for a CCL NCP that is directly attached to VTAM through an XCA major node. However, if you use the MODIFY LOAD command to set a Timed IPL request for a CCL NCP, CCL always ensures that the Auto Dump/Load switch is set immediately before executing the Timed IPL request. The only other way to set or reset the Auto Dump/Load switch for a XCA-attached CCL NCP is to use the CCL MOSS console.