ARC0200I

Explanation
 DFSMShsm finished adding or removing a trap
for module modname when an error errcode occurred.
The rest of the message indicates what action DFSMShsm takes. This message
is in response to a user who entered the TRAP command. In certain
cases, this message is also issued the first time an error occurs
in DFSMShsm and
for which a TRAP command for the specific error condition was not
entered.
 errcode is one of the following: When the message is issued for the first time the error occurs,
an entry is made in the trap table. ARCERP manages the trap table
and also contains the action to take. For those entries added to the
trap table, errcode is the error code sent to ARCERP
by the module recognizing the error condition. The TRAP command overrides
the error procedures in ARCERP and causes the error processing to
take a different action when the error occurs.
If errcode is ANY, this message is issued in
response to the TRAP command where the ERRCODE parameter of the TRAP
command was either entered as 0 or omitted.
If errcode is SYSTEM ABEND CODE a system abnormal
end (abend) occurred in the module modname.
If errcode is a number from 400-499, a second
message appears with the same error condition, but with a different
module name. This error represents an error in a module path. Search
problem reporting databases for a fix for the problem. If no fix exists,
contact the IBM® Support Center.

 If the modname is ARCZWRIT and the errcode is
8, the message indicates a record with a duplicate key already existed
when DFSMShsm tried
to write the record. This condition is an error.
 More information
about modules and error codes can be found in z/OS DFSMShsm Diagnosis 
under "Diagnosing From Return Codes and Reason Codes" in the
table titled "Entries that Pass Error Codes to ARCERP".

System action
 If the message is the result of a TRAP command,
no action is taken by the system; however, an entry is placed in the
trap table that invokes the requested TRAP command action when the
specified error occurs.
 If the message is issued as a result
of an error, the following actions are taken depending on the action
indicated in the message:  LOG ALWAYS ADDED  A log entry of the error is written to the DFSMShsm log
and message ARC0900I is issued to the operator.

FATAL ONCE ADDED  The DFSMShsm task that had the error is abended
with a dump request.
 A log entry of the error is written to
the DFSMShsm log
and message ARC0900I is issued to the operator.
 DFSMShsm is
shut down immediately.

NODUMP ONCE ADDED | ABEND ONCE ADDED  The DFSMShsm task that had the error
is abended.
 A log entry of the error is written to the DFSMShsm log
and message ARC0900I is issued to the operator.

SNAP NEVER ADDED | ABEND NEVER ADDED  No action is taken, but
a table entry is created and the number of times this error occurred
is set to 1 in the entry.
 A log entry of the error is written
to the DFSMShsm log
and message ARC0900I is issued to the operator.

SNAP ALWAYS ADDED  A SNAP dump of the DFSMShsm address space is taken.
 A
log entry of the error is written to the DFSMShsm log and message ARC0900I
is issued to the operator.

SNAP ONCE ADDED  The DFSMShsm task that had the error is snapped
if this is the first occurrence of the condition. If this is not the
first occurrence of the condition, a table entry is created and the
number of times this error occurred is set to 1 in the entry.
 A
log entry of the error is written to the DFSMShsm log and message ARC0900I
is issued to the operator.

ABEND ALWAYS ADDED  The DFSMShsm task that had the error is abended.
 A
log entry of the error is written to the DFSMShsm log and message ARC0900I
is issued to the operator.

DEBUG ALWAYS ADDED  A log entry of the error is written to
the DFSMShsm log.

Programmer response
 If FATAL ONCE is added, restart DFSMShsm.
 If
you want DFSMShsm to
stop issuing this message, issue the TRAP command with the OFF parameter.

Source
 DFSMShsm