-----------------------------------------------------------------------
  Update error procedures

  -----------------------------------------------------------------------

Toxicology Data Management System

  ----------------------------------- -----------------------------------
  **Document Number:**                LP-1009-2.0

  **Version:**                        2.0

  **Issued:**                         February 18, 2000

  **Reviewed & Approved by:**         Ginger Harrell, Program Director

  **Signature:**                      

  **Date:**                           

                                      
  ----------------------------------- -----------------------------------

Update Error Procedures

National Toxicology Program Support

Update Error Procedures

Prepared for: National Institute of Environmental Health Sciences

> Research Triangle Park, NC 27709

Contract no.: 273-95-I-0012

Prepared by: Technology Planning & Management Corporation

Imperial Center

Canterbury Hall, Suite 310

4815 Emperor Boulevard

Durham, NC 27703

[]{#__RefHeading___Toc475510482 .anchor}Revision Summary

  ------------ ------------ ------------ -------------------------------------
  **Date       **Document   **Revision   **Reason for Revision**
  Released**   Number**     Level**      

  2/2000       LP-1009      2.0          Update for new manual template, VAX
                                         to HAZEL references

  12/94        LP-1009      1.0          New
  ------------ ------------ ------------ -------------------------------------

Table of Contents

Revision Summary [ii](#__RefHeading___Toc475510482)

Chapter 1 [1](#__RefHeading___Toc475510483)

Introduction [1](#__RefHeading___Toc475510484)

Chapter 2 [2](#__RefHeading___Toc475510485)

Procedures [2](#__RefHeading___Toc475510486)

2.1 No EIS Data for PEIS Update [3](#no-eis-data-for-peis-update)

2.2 Change Trans, No Rec Found [4](#change-trans-no-rec-found)

2.3 DEL Trans, No REC Found [6](#del-trans-no-rec-found)

2.4 Add Trans, Rec Exists [8](#add-trans-rec-exists)

2.5 ADABAS [9](#adabas)

2.6 Duplicate Carcass ID [10](#duplicate-carcass-id)

2.7 Trans not ADD, Change, Delete [10](#trans-not-add-change-delete)

2.8 Neoplastic Flag Not Found [11](#neoplastic-flag-not-found)

2.8 Rec Exists or PE Group Full [11](#rec-exists-or-pe-group-full)

2.9 Not ADD and Record Not Found [11](#not-add-and-record-not-found)

2.10 Maintaining the Update Error Notebook
[12](#maintaining-the-update-error-notebook)

Appendix A [1](#__RefHeading___Toc475510498)A

Error Examples [1](#__RefHeading___Toc475510499)A

Update Error [1](#update-error)A

No EIS Data for PEIS Update Error
[1](#no-eis-data-for-peis-update-error)A

Change Trans, No Rec Found Error [1](#change-trans-no-rec-found-error)A

DEL Trans, No REC Found Error [2](#del-trans-no-rec-found-error)A

Add Trans, Rec Exists [2](#add-trans-rec-exists-1)A

ADABAS Error [2](#adabas-error)A

Duplicate Carcass ID Error [2](#duplicate-carcass-id-error)A

Trans Not ADD, Change, Delete Error
[2](#trans-not-add-change-delete-error)A

Neoplastic Flag Not Found Error [2](#neoplastic-flag-not-found-error)A

Rec Exists or PE Group Full Error
[3](#rec-exists-or-pe-group-full-error)A

Not ADD and Record Not Found [3](#not-add-and-record-not-found-1)A

[]{#__RefHeading___Toc475510484 .anchor}Introduction

This document defines the update errors that may occur during the
validate/update cycle, and it describes in detail the procedures that
the liaison must follow to correct the update errors.

The Validate/Update System consists of subsystems Validate and Update.
Validate parses incoming transaction files generated from the
*Laboratory Data Acquisition System* (LDAS), and the *Toxicology Data
Management System* (TDMS) *Error Correction System* (ECS).

Update verifies the existence of transaction records on the database
before the transactions are modified or deleted. Update also verifies
the nonexistence of a record before adding a record. If Update detects
an error, it generates an error report describing the error, and does
not post the record to the mainframe database. If Update detects no
errors, it posts the record to the mainframe database.

Each weekday, production control runs the update program that adds all
new data to the studies in progress. For every update, the TDMS system
automatically generates an *Update Error Report*. The *Update Error
Report* shows which segment failed Update and identifies the reason for
the failure. The *Update Error Report* contains the following
information:

-   Study number

-   Name of laboratory responsible for study

-   Type of transaction that did not update

-   System on which the transaction was created

-   Segment name

-   Segment ID

-   Date/time of the record to be modified, added, or deleted.

    []{#__RefHeading___Toc475510486 .anchor}Procedures

This chapter provides a list of update errors that may occur, a
description of the error, and the specific procedures to resolve the
error.

Update errors are displayed on the *TDMS Validate/Update Error Report*.
This report displays each record that could not be updated in the
database. Listed below are the type of errors that may occur. All of
these errors are described in this chapter:

-   No EIS Data for PEIS Update

-   Change Trans, No Rec Found

-   Delete Trans, No Rec Found

-   Add Trans, Rec Exists

-   Adabas Error

-   Duplicate Carcass ID

-   Trans Not Add, Change, Delete

-   Neoplastic Flag Not Found

-   Rec Exists or PE Group Full

-   Not Add & Record Not Found

An example of an *Update Error* is shown in Appendix A.

Below is an explanation of the fields in the update error:

STUDY Seven-digit number of the test

LAB The laboratory responsible for the test

ERROR Type of transaction and error occurred

M/E Source of the transactionM is Micro, E is ECS

SEGMENT NAME Type of record

CAGE Cage number of record

ANIMAL Animal identification number

CID Carcass identification

DATE Data date record originated

TIME Time record originated

# 2.1 No EIS Data for PEIS Update

The *No EIS Data for PEIS Update Error* occurs when pathology data is
collected for an animal with no animal removal segment on the HAZEL.
This problem is a priority and needs to be fixed immediately.

An example of the *No EIS Data for PEIS Update Error* is shown in
Appendix A.

NOTE

> The CID number is a 14-digit number. The number is comprised of a
> two-digit agency number, a seven-digit study number, and a five-digit
> animal number.

Follow these steps to resolve the problem:

1.  Analyze the error report, and determine the study and the animal
    affected.

2.  Locate the CID or animal number specified on the error report.

3.  Run the CID sort program to identify the cage number for the animal.

4.  Access the *TDMS Error Correction System* (ECS).

5.  Attempt to display the animal removal segment on Hazel. Verify that
    an animal removal segment does not exist for the CID or animal
    number identified in step 2.

6.  Run a Stattran report to be sure all In-Life transaction sets for
    the study have been transmitted. If there is a missing set, ask the
    Data Administrator to transmit the set. If the missing animal
    removal is in this transaction set, it will be added to the database
    during Update.

7.  If a missing transaction set is not the cause of the problem,
    contact the Data Administrator and make sure that the animal has
    been removed from the study. If the animal has not been removed,
    make sure the lab removes the animal and transmit the transaction
    set containing the animal removal.

8.  Once the animal removal segment is on the database, copy the
    transaction file that produced the update error from the Transaction
    Directory to the STARRECEIVEERROR Directory. Edit the file deleting
    all unneeded data, rename the file, and resubmit it.

    NOTE

    > The edited transaction file is renamed by retaining the original
    > file name but changing the set number. For example: original
    > filename: sre_aaa_bbbbb_bb_xxx.upl new filename:
    > sre_aaa_bbbbb_bb_yyy.upl where aaa = three-character lab code
    > bbbbb_bb = seven-digit experiment/test number xxx or yyy = set
    > number

    The transaction file is located in STARTRANSACTION if submitted in
    the current month.

```{=html}
<!-- -->
```
9.  After the resubmitted transaction file is processed and updated
    correctly, the liaison and the data administrator should run a
    PEISRPT14 for the specific cage to make sure the data is correct.

# 2.2 Change Trans, No Rec Found

The *Change Transaction, No Record Found Error* occurs when a change
transaction is performed on a segment that does not exist on the
database.

An example of the *Change Trans, No Rec Found Error* is shown in
Appendix A.

NOTE

> The probable cause of the error is either:

-   The data to be changed is in a transaction file that was submitted
    > after the change transaction

-   The data to be changed is in a transaction file that was not
    > processed successfully by RECEIVE.

Follow these steps to resolve the problem:

1.  On the Hazel mainframe, search for the original data by doing the
    following:

```{=html}
<!-- -->
```
a)  At the \$ prompt, type:

    Set default STARTRANSACTIONS (or STARTRXMMMYY)

b)  At the \$ prompt, type:

    Search SRE_lab_xxxxx_xx\_\*.upl

    where lab = three-character lab code

    xxxxx_xx = experiment/text number

c)  At the "\_String(s):" prompt, type the transaction layout for the
    original data. The string should be in quotes and begin with "A\|,"
    followed by the transaction layout. Follow the transaction design
    layouts found in the *LDAS Technical Reference Manual.* For example:

> "A\|61\|23-FEB-1993 08:01:04\|45\| \|450\| \|" for the animal weight
> transaction in the Change Trans, No Rec Found Update error above.

2.  If the original data is found during the search, the following data
    will be displayed on the screen:

-   Transaction set filename example:

    STARTRX\$ROOT:\[1993.FEB\]SRE_MAS_11111_11_032_EI.UPL;1

-   Transaction record

> The original transaction file probably encountered problems during the
> receive process. Using the transaction set number found in the
> Transaction set filename (032 in the above example), run a Stattran
> report for the study. Check the verification for all categories on the
> Stattran report. If it is determined that the set containing the
> original data did not update properly, proceed to step 4.

3.  If the original data cannot be found during the search, the
    transaction file containing the data may not have been submitted or
    processed before the change transaction was processed. Run a
    Stattran report to be sure all In-Life or Pathology transaction sets
    for the study have been transmitted. If the missing set is in this
    transaction set, it will be added to the database during Update.
    After Update, proceed to step 4.

4.  Copy the file that did not update from the STARTRANSACTIONS
    directory to the STARRECEIVEERROR directory. Edit the file deleting
    all unneeded data. Rename the file following the instructions below,
    and resubmit it to Receive.

    NOTE

    > The edited transaction file is renamed by retaining the original
    > filename but changing the set number. For example: original
    > filename: sre_aaa_bbbbb_bb_xxx.upl new filename:
    > sre_aaa_bbbbb_bb_yyy.upl where aaa = three-character lab code
    > bbbbb_bb = seven-digit experiment/test number xxx or yyy = set
    > number

    The transaction file is located in STARTRANSACTIONS if submitted in
    the current month.

```{=html}
<!-- -->
```
5.  After the resubmitted transaction file is processed and updated
    correctly, the liaison and the data administrator should run the
    appropriate report to make sure the data is correct.

# 2.3 DEL Trans, No REC Found

This error occurs when a delete transaction is performed on a segment
that does not exist on the database.

An example of the *DEL Trans, No REC Found Error* is shown in Appendix
A.

NOTE

> The probable cause of the error is either

-   The data to be changed is in a transaction file that was submitted
    > after the change transaction

-   The data to be changed is in a transaction file that was not
    > processed successfully by RECEIVE

Follow these steps to resolve the problem:

1.  On the Hazel mainframe, search for the original data by doing the
    following:

```{=html}
<!-- -->
```
a)  At the \$ prompt, type

    Set Default STARTRANSACTIONS (or STARTRXMMMYY)

b)  At the \$ prompt, type

    Search SRE_lab_xxxxx_xx\_\*.upl

    where lab = three character lab code

    xxxxx_xx = experiment/test number

```{=html}
<!-- -->
```
c)  At the "\_String(s)*:"* prompt, type the transaction layout for the
    original data. The string should be in quotes and begin with "A\|,"
    followed by the transaction layout. Follow the transaction design
    layouts found in the *LDAS Technical Reference Manual.* For example:

> "A\|61\|23-FEB-1993 08:01:04\|45 \|450\| \|" for the animal weight
> transaction in the DEL Trans, No REC Found Update error above.

2.  If the original data is found during the search, the following data
    will be displayed on the screen:

-   Transaction set filename

    For example:

    STARTRX\$ROOT:\[1993.FEB\]SRE_MAS_11111_11_032_EI.UPL;1

-   Transaction record

> The original transaction file probably encountered problems during the
> receive process. Using the transaction set number found in the
> Transaction set filename (032 in the above example), run a Stattran
> report for the study. Check the verification for all categories on the
> Stattran report. If it is determined that the set containing the
> original data did not update properly, proceed to step 4.

3.  If the original data cannot be found during the search, the
    transaction file containing the data may not have been submitted or
    processed before the delete transaction was processed. Run a
    Stattran report to be sure all In-Life or Pathology transaction sets
    for the study have been transmitted. If there is a missing set, ask
    the Data Administrator to transmit the set. If the missing record is
    in this transaction set, it will be added to the database during
    Update. After Update, proceed to step 4.

4.  Copy the file that did not update from the STARTRANSACTION directory
    to the STARRECEIVEERROR directory. Edit the file, deleting all
    unneeded data. Rename the file following the instructions below, and
    resubmit it to Receive.

    NOTE

> The edited transaction file is renamed by retaining the original
> filename but changing the set number. For example: original filename:
> sre_aaa_bbbbb_bb_xxx.upl new filename: sre_aaa_bbbbb_bb_yyy.upl where
> aaa = three-character lab code bbbbb_bb = seven-digit experiment/test
> number xxx or yyy = set number

The transaction file is located in STARTRANSACTIONS if submitted in the
current month.

5.  After the resubmitted transaction file is processed and updated
    correctly, the liaison and the data administrator should run the
    appropriate report to make sure the data is correct.

# 2.4 Add Trans, Rec Exists

This error occurs when an *Add transaction* is performed for a segment
that already exists on the database. More specifically, the error occurs
when a record to be updated has the same fields as an existing record
(for example, date/time on an animal weight record or CID on a removal
record).

This error generally occurs when duplicate data collection occurs on the
microcomputer. The duplicate segment of data will not append to the
HAZEL mainframe.

This error may occur if a user on the mainframe ECS system attempts to
add a record for an animal that contains the same data, date, and time
stamp as an existing record.

An example of the *Add Trans, Rec Exists Error* is shown in Appendix A.
Follow these steps to resolve the problem:

**If ECS generated the error:**

1.  Log on to ECS, and verify that duplicate data exists. If the
    duplicate data is due to duplicate CIDs on a removal record, verify
    that the existing record on the database contains the correct animal
    identification data and animal data. If this data is not known,
    obtain the information from the lab.

2.  Do the same type of check for other ECS generated records that are
    in error. Proceed to step 4.

    **If Micro generated the error:**

```{=html}
<!-- -->
```
3.  Perform a search on the HAZEL mainframe for the transaction file(s)
    containing the data to determine how the duplicate data was
    collected.

```{=html}
<!-- -->
```
a)  At the \$ prompt, type

    Set default STARTRANSACTION

```{=html}
<!-- -->
```
b)  At the \$ prompt, type:

> Search SRE_lab_xxxxx_xx\_\*.upl
>
> where lab = three-character lab code
>
> xxxxx_xx = experiment/test number

c)  At the "\_String(s):" prompt, type the transaction layout for the
    original data. The string should be in quotes and begin with
    "A\|,"followed by the transaction layout. Follow the transaction
    design layouts found in the *LDAS Technical Reference Manual.*

NOTE

> It is also possible that the original data was deleted and then added
> on the micro. The add transaction may have been sent to HAZEL before
> the delete transaction, resulting in the *ADD Trans, Rec Exists
> Error*. To check for this possibility, search the transaction files to
> make sure that a delete transaction for the original data is not
> present.

4.  Once you have determined the source of the duplicate data, make sure
    the HAZEL mainframe is correct and that the micro is synchronized
    with the mainframe.

# 2.5 ADABAS

This error is a result of the Natural "On Error" clause. The error can
affect all segments except the D micro animal segment. The information
given for this error is usually insufficient; however, this error is a
high priority and it should be resolved as soon as the problem can be
identified.

An example of the *ADABAS Error* is shown below in Appendix A. Follow
these steps to resolve the problem:

1.  Inform the Database Administrator (DBA) that the error has occurred.
    The DBA will then inform you of the cause of the problem.

2.  Alert the lab that a software error has occurred

-   when the DBA determines the cause of the error, **or**

-   if the DBA cannot determine the cause of the error within 24 hours
    (continue to keep the lab posted on the investigation).

3.  Instruct lab personnel, in writing, to thoroughly check their
    reports and transactions for lost data, incomplete transactions, or
    any other indication of software malfunction.

# 2.6 Duplicate Carcass ID

The *Duplicate Carcass ID Error* occurs when a carcass identification
number that already exists in the database is assigned to another
animal. The problem most likely occurs when a user corrects animal
removal data using HAZEL ECS.

For example: While correcting animal removal data, animal number 2 is
incorrectly assigned carcass identification number 1, which already
exists in the database. This generates an error. The entry for animal
number 2 should be corrected. This is a high priority problem and should
be attended to immediately.

An example of the *Duplicate Carcass ID Error* is shown in Appendix A.
Follow these steps to resolve the problem:

1.  Find the source of the error by reviewing the record on the database
    that has the same CID number as the record that failed Update.

2.  Determine which record contains the correct CID number. If the
    record in the database contains the correct CID number, find out the
    correct CID number for the record that failed, correct it using ECS,
    and resubmit. If the record in the database contains an incorrect
    CID number, correct it using HAZEL ECS, then resubmit the record
    that failed.

# 2.7 Trans not ADD, Change, Delete

The *Transaction Not ADD, Change, Delete Error* can affect all segments
and is caused by an invalid transaction. The process flag for the
transaction is not A, C, or D (Add, Change, or Delete).

An example of the *Trans, Not ADD, Change, Delete Error* is shown in
Appendix A. Follow these steps to resolve the problem:

1.  Examine the error report for the experiment, test, cage or animal
    identifier, and the type of data involved.

2.  If the error is related to EIS or PEIS, notify the lab of the error
    by phone, by e-mail, or in writing.

> If the error is caused by a mistake in the HAZEL error correction
> system, examine the entries you made in the system, and make the
> necessary corrections.

# 2.8 Neoplastic Flag Not Found

The Neoplastic Flag Not Found Error involves the micro observation
segment only. The record in the HAZEL database is missing the neoplastic
flag. This is a high priority problem because pathology reports will not
display data missing the neoplastic flag.

An example of the *Neoplastic Flag Not Found Error* is shown in Appendix
A. Follow these steps to resolve the problem:

1.  Ask the DBA to review the problem.

2.  Notify the lab of your findings.

3.  Coordinate with the DBA in getting the problem resolved.

4.  Inform the lab when the problem is resolved.

# 2.8 Rec Exists or PE Group Full

The *Rec Exists or PE Group Full Error* only affects the micro site
segment and occurs when a maximum of 20 statuses is exceeded.

An example of the *Rec Exists or PE Group Full Error* is shown in
Appendix A. Follow these steps to resolve the problem:

1.  Notify the lab that they have used the maximum number of statuses,
    and tell them which status(es) did not update.

2.  Ask the lab to delete the status from their micro to keep HAZEL
    micro synchronized. The lab decides which statuses to keep, change,
    or delete.

# 2.9 Not ADD and Record Not Found

Update generates the *Not ADD and Record Not Found Error* when it cannot
find a record in the database to match a non-add transaction. The only
segments that can be affected are:

-   any animal

-   animal transfer

-   animal removal

-   cage identification

-   histology

An example of the *Not ADD and Record Not Found Error* is shown in
Appendix A. Follow these steps to resolve the problem:

1.  Examine the error report for the experiment, test, cage or animal
    identifier, and the type of data involved.

2.  If the error is related to EIS or PEIS, notify the lab of the error
    by phone, by e- mail, or in writing.

# 2.10 Maintaining the Update Error Notebook

An *Update Error Report* is produced each evening after Update has
completed. The *Update Error Reports* are kept in a notebook for
reference. The steps for maintaining the *Update Error Notebook* are as
follows:

1.  Obtain the *TDMS Update Report* from TDMSPRINT after Update has
    completed.

2.  Check the report to see if any update errors occurred.

3.  If an *Update Error* occurred, make a photocopy of the report, and
    give the copy to the liaison for the lab that had the error.

4.  File the original report in the front of the *Update Error
    Notebook*.

[]{#__RefHeading___Toc475510499 .anchor}Error Examples

The following are examples of each possible error.

## Update Error

  ---------- -------- --------------- ----- ---------- ------ -------- ----- -------- ----------
  STUDY      LAB      ERROR           M/E   SEGMENT    CAGE   ANIMAL   CID   DATE     TIME
                                            NAME                                      

  11111-11   Xyzlab   Change Trans,   M     Feeder Wt  77                    052593   12:02:12
                      No Red                                                          
  ---------- -------- --------------- ----- ---------- ------ -------- ----- -------- ----------

## No EIS Data for PEIS Update Error

  ---------- -------- ---------------- ----- ---------- ------ -------- ---------------- -------- ----------
  STUDY      LAB      ERROR            M/E   SEGMENT    CAGE   ANIMAL   CID              DATE     TIME
                                             NAME                                                 

  11111-11   Xyzlab   No EIS Data for  M     Any Micro                  05111111100415   022593   08:01:04
                      PEIS Update            Organ                                                
  ---------- -------- ---------------- ----- ---------- ------ -------- ---------------- -------- ----------

## Change Trans, No Rec Found Error

  ---------- -------- ----------------- ----- --------- ------ -------- ----- -------- ----------
  STUDY      LAB      ERROR             M/E   SEGMENT   CAGE   ANIMAL   CID   DATE     TIME
                                              NAME                                     

  11111-11   Xyzlab   Change Trans, No  M     Animal Wt 61     61             022393   08:01:04
                      Rec Found                                                        
  ---------- -------- ----------------- ----- --------- ------ -------- ----- -------- ----------

##   {#section .unnumbered}

## DEL Trans, No REC Found Error

  ---------- -------- ----------------- ----- --------- ------ -------- ----- -------- ----------
  STUDY      LAB      ERROR             M/E   SEGMENT   CAGE   ANIMAL   CID   DATE     TIME
                                              NAME                                     

  11111-11   Xyzlab   DEL Trans, No REC M     Animal Wt 61     61             022393   08:01:04
                      Found                                                            
  ---------- -------- ----------------- ----- --------- ------ -------- ----- -------- ----------

## Add Trans, Rec Exists

  ---------- -------- -------------- ----- ---------- ------ -------- ---------------- -------- ----------
  STUDY      LAB      ERROR          M/E   SEGMENT    CAGE   ANIMAL   CID              DATE     TIME
                                           NAME                                                 

  11111-11   Xyzlab   Add Trans, Rec M     Any Micro                  05111111100436   060590   08:01:00
                      Exists               Organ                                                
  ---------- -------- -------------- ----- ---------- ------ -------- ---------------- -------- ----------

## ADABAS Error

  ---------- -------- -------- ----- ----------- ------ -------- ------- -------- ----------
  STUDY      LAB      ERROR    M/E   SEGMENT     CAGE   ANIMAL   CID     DATE     TIME
                                     NAME                                         

  11111-11   Xyzlab   ADABAS   M     Animal Wt   61     61               060590   08:01:00
  ---------- -------- -------- ----- ----------- ------ -------- ------- -------- ----------

## Duplicate Carcass ID Error

  ---------- -------- ------------ ----- ----------- ------ -------- ---------------- -------- ----------
  STUDY      LAB      ERROR        M/E   SEGMENT     CAGE   ANIMAL   CID              DATE     TIME
                                         NAME                                                  

  11111-11   Xyzlab   Duplicate    M     Any Micro                   05111111100403   020593   10:10:06
                      Carcass            Organ                                                 
  ---------- -------- ------------ ----- ----------- ------ -------- ---------------- -------- ----------

## Trans Not ADD, Change, Delete Error

  ---------- -------- ------------------- ----- --------- ------ -------- ----- -------- ----------
  STUDY      LAB      ERROR               M/E   SEGMENT   CAGE   ANIMAL   CID   DATE     TIME
                                                NAME                                     

  11111-11   Xyzlab   Trans Not ADD,      M     Animal Wt 61     61             060590   08:01:00
                      Change, Delete                                                     
  ---------- -------- ------------------- ----- --------- ------ -------- ----- -------- ----------

## Neoplastic Flag Not Found Error

  ---------- -------- ---------------- ----- --------- ------ -------- --------------- -------- ----------
  STUDY      LAB      ERROR            M/E   SEGMENT   CAGE   ANIMAL   CID             DATE     TIME
                                             NAME                                               

  11111-11   Xyzlab   Neoplastic Flag  M     Micro Obs                 0511111110023   071193   08:20:00
                      Not Found                                                                 
  ---------- -------- ---------------- ----- --------- ------ -------- --------------- -------- ----------

## Rec Exists or PE Group Full Error

  ---------- -------- -------------------- ----- --------- ------ -------- --------------- -------- ----------
  STUDY      LAB      ERROR                M/E   SEGMENT   CAGE   ANIMAL   CID             DATE     TIME
                                                 NAME                                               

  11111-11   Xyzlab   Rec Exists or PE     M     Micro                     0511111110015   092395   12:30:00
                      Group Full Error           Site                                               
  ---------- -------- -------------------- ----- --------- ------ -------- --------------- -------- ----------

## Not ADD and Record Not Found

  ---------- -------- ------------------ ----- --------- ------ -------- --------------- -------- ----------
  STUDY      LAB      ERROR              M/E   SEGMENT   CAGE   ANIMAL   CID             DATE     TIME
                                               NAME                                               

  11111-11   Xyzlab   Not ADD and Record M     Any Micro                 0511111110330   081393   15:50:30
                      Not Found                Organ                                              
  ---------- -------- ------------------ ----- --------- ------ -------- --------------- -------- ----------

END OF DOCUMENT