Dumping an NCP

You can request either a dynamic dump or a static (destructive) dump of an NCP.

Dynamic dump: When you request a dynamic dump (MODIFY DUMP OPTION=DYNA), NCP processing continues while the NCP contents are being dumped. A dynamic dump reflects the storage contents of the communication controller over a period of time.
Static dump: You request a static dump by entering the MODIFY DUMP command with OPTION=STATIC (the default value), or by replying "yes" when VTAM® offers to dump a failed NCP. When you request a static dump, NCP processing stops and the current storage contents of the NCP are dumped. This dump effectively destroys a running NCP. The NCP must be reactivated (and reloaded) before communication with that NCP can resume.

The method for obtaining a static dump of an NCP depends upon whether the NCP is active or inactive.

Active NCP: If the NCP is active, specify the name of the NCP to be dumped. Select the dump station and dump file to use as described under Selecting a dump station for a static dump of an NCP and Selecting a dump file for an NCP dump. As a result of the dump, the NCP is deactivated.
Inactive NCP: If the NCP is inactive, specify the name of an SDLC link station within an NCP adjacent to the communication controller containing the NCP to be dumped.

The link station specified on the command is the dump station. This link station can be either active or inactive, but the associated SDLC link must be active so that it can be used to carry the dump traffic. As a result of the dump, the link station is deactivated, if it is not already inactive. Because there is no dump file associated with a link station, specify the logical unit name (SYSxxx) on the DUMPDS operand on the MODIFY DUMP command.

Although this method can also dump an active link-attached NCP, it is primarily used for dumping an inactive link-attached NCP. If an active NCP is dumped by specifying ID=adjacent link station on the MODIFY DUMP command, the adjacent link station, not the NCP, is deactivated when the dump is completed. To deactivate the NCP, issue the VARY INACT command.

You can also obtain a static dump by using the NCP independent dump utility if the NCP is in a channel-attached communication controller. For more information about the NCP independent dump utility, see the NCP, SSP, and EP Diagnosis Guide.

When you request a static dump by specifying ACTION=STORE, OPTION=STATIC on the MODIFY DUMP command, the NCP terminates. The contents of the NCP are dumped to the controller hard disk only if the automatic dump/load was previously set (DUMPLOAD=YES,SAVEMODE=YES,LOADFROM=HOST or DUMPLOAD=YES,LOADFROM=EXT) and the dump slot on the MOSS controller hard disk is empty. The load module stored on the controller hard disk is reloaded, but you need to reactivate the NCP before you can resume communication with that NCP. To transfer an NCP dump stored on a controller hard disk to the host, use the ACTION=TRANSFER operand on the MODIFY DUMP command.

Use the DISPLAY NCPSTOR command to display the contents of the NCP external disk dump file. To print the contents of the NCP dump file, use the NCP independent dump utility described in the NCP, SSP, and EP Diagnosis Guide.

If an expiration date exists for the dump file and it has not yet been reached, do not respond to message IEC507D by entering REPLY xx,M. Enter REPLY xx,U to override the expiration date and allow write access to the file. Entering REPLY xx,M causes the dump to be abnormally terminated by the operating system.