Explanation
VTAM® issues
this message when the contents of the communication controller have
been scheduled to be dumped to a disk, or have successfully or unsuccessfully
been dumped to a data set.
resourcename is
one of the following:
dumptype can be one of the following:
- STATIC
- NCP processing stops. The contents of the communication controller
are dumped by microcode services, and VTAM deactivates
the major node associated with resourcename.
- DYNAMIC
- NCP processing continues while the NCP contents are dumped. VTAM does not deactivate the NCP.
- MOSS
- VTAM transfers a maintenance
operator subsystem dump contained on the MOSS disk in the IBM® 3720, 3725, or 3745 Communication
Controller to a host data set.
- CSP
- VTAM transfers a communication
scanner processor dump contained on the MOSS disk to a host data set.
- TRANSFER
- VTAM transfers an NCP dump
contained in the IBM 3720, 3725,
or 3745 Communication Controller to a host data set.
status can be one of the following:
- CANCELLED — PATH BLOCKED
- VTAM attempted the dump
but was unable to access the controller because it was being dumped
or loaded by another host.
- CANCELLED — PATH NOT OPERATIONAL
- VTAM attempted the dump
but was unable to access the controller because the channel path was
not operational. This is probably because the controller is in the
process of being dumped or loaded by another host. However, this
can also indicate a hardware or software problem.
- COMPLETE
- The dump is complete.
- PARTIALLY COMPLETE
- During dump processing, a permanent I/O error occurred on the
communication controller, the dump data set, or the SDLC link. A
portion of the dump is not usable. The dump data set might be too
small to contain the entire dump.
Note: If ACTION=TRANSFER and either
TYPE=CSP or TYPE=MOSS were specified on the MODIFY DUMP command, the
BER log, CDF, TIC dump, and CA dump are transferred from the hard
disk even when the CSP or MOSS dump is not present on the disk. This
message indicates that data has been transferred to the dump data
set even though the specified dump was not present.
- SCHEDULED TO DISK
- The dump to disk request has been forwarded to the NCP resourcename.
- STARTED
- The dump has begun.
- FAILED — PERMANENT I/O ERROR
- During dump processing, an unrecoverable I/O error occurred on
the communication controller or the dump data set. The dump is unusable.
- FAILED — ddname CANNOT BE OPENED
- VTAM attempted the dump,
but could not open the dump data set defined by ddname.
Dump processing terminated.
- FAILED — UNSUPPORTED DEVICE TYPE
- VTAM attempted the dump,
but could not open the dump data set because it was located on an
unsupported device. Dump processing terminated.
System action
If
status is:
- CANCELLED — PATH BLOCKED
- The dump terminates, and VTAM waits
for contact with NCP resourcename to be re-established.
- CANCELLED — PATH NOT OPERATIONAL
- The dump terminates, and VTAM waits
for contact with NCP resourcename to be re-established.
- COMPLETE
- Processing continues.
- PARTIALLY COMPLETE
- The dump terminates.
- SCHEDULED TO DISK
- Processing continues.
- STARTED
- The dump has begun.
- FAILED — PERMANENT I/O ERROR
- The dump terminates.
- FAILED — ddname CANNOT BE OPENED
- The dump terminates.
- FAILED — UNSUPPORTED DEVICE TYPE
- The dump terminates.
Operator response
If
status is:
- CANCELLED — PATH BLOCKED
- None.
- CANCELLED — PATH NOT OPERATIONAL
- If contact with NCP resourcename is not re-established
in a few minutes, save the system log for problem determination.
- COMPLETE
- You can format the entire dump using the NCP dump utility program.
- PARTIALLY COMPLETE
- If the dump is valid and enough data was saved, you can format
and print the portion of the dump that was taken using the NCP dump
utility program. Dump utility messages will provide information about
the validity of the dump and data saved.
Attempt to dump the
NCP using the NCP dump utilities. See the NCP, SSP, and EP Diagnosis
Guide for information on using the NCP dump utilities.
Save
the system log for problem determination, and run your operating system
service aid program. See the EREP User's Guide and Reference for
more information on using EREP.
- SCHEDULED TO DISK
- Re-establish communication with the NCP resourcename and
query the MOSS disk for the dump status. If the dump is present, you
can use the MODIFY DUMP command to transfer the dump to a host data
set. The dump can be formatted and printed using the utility program.
- STARTED
- None.
- FAILED — PERMANENT I/O ERROR
- This is probably a hardware error.
- Make sure the communication controller is powered on.
- Check the HARD STOP and PROGRAM STOP indicators on the communication
controller operator panel. If either indicator is on, press the LOAD
switch.
- If the communication controller is switchable between processors,
make sure the communication controller is switched to the VTAM host processor.
- Attempt to dump the NCP using the NCP dump utilities. See the NCP,
SSP, and EP Diagnosis Guide for information on using the NCP
dump utilities.
- Save the system log for problem determination, and run your operating
system service aid program. See the EREP User's Guide and Reference for
more information on using EREP.
- FAILED — ddname CANNOT BE OPENED
- If you specified the dump data set name correctly, save the system
log for problem determination.
- FAILED — UNSUPPORTED DEVICE TYPE
- Ensure that the dump data set resides on a supported access device.
If the problem persists, save the system log for problem determination.
System programmer response
If
status is:
- CANCELLED — PATH BLOCKED
- None.
- CANCELLED — PATH NOT OPERATIONAL
- Take the following actions:
- Check the channel definition in the NCP definition library to
ensure that the channel adapter that failed is defined to NCP resourcename.
- If the channel adapter is correctly defined to NCP resourcename,
this is probably a hardware error. Ensure that the channel adapter
is online from MOSS.
- If the channel adapter is online, and you continue to have problems,
contact the IBM hardware support
center.
- COMPLETE
- None.
- PARTIALLY COMPLETE
- You might need to increase the size of the dump data set. If you
cannot determine the cause of the problem from the output provided
or need additional assistance, contact the IBM hardware support center.
- SCHEDULED TO DISK
- None.
- STARTED
- None.
- FAILED — PERMANENT I/O ERROR
- If you cannot determine the cause of the problem from the output
provided or need additional assistance, contact the IBM hardware support center.
- FAILED — ddname CANNOT BE OPENED
- Ensure that
- The dump data set name is spelled correctly on either the DUMPDS
operand of the MODIFY DUMP command or the DUMPDS, CDUMPDS, or MDUMPDS
operands of the PCCU definition statement.
- The appropriate JCL statements are included with the VTAM start options.
Check the output provided by the operator to ensure that
all requirements for VTAM are
correct for your system. When you have corrected the error condition,
ask the operator to reenter the command.
- FAILED — UNSUPPORTED DEVICE TYPE
- Check the output provided by the operator to ensure that all requirements
for VTAM are correct for your
system. When you have corrected the error condition, ask the operator
to reenter the command.
Routing code
Descriptor code