Previous Topic: Resolve Conflicts between Rule ActionsNext Topic: Errors Requiring CA Support


Rules Summary Status Messages

The following error messages may appear on the Rules Summary panel and the Rules Applied During Run panel after running a test stream.

<APPLIED>

Reason:

This rule or rule action has been applied.

<CONFLICT>

Reason:

One or more rule actions applied to the same location and a conflict occurred.

<ERROR>

Reason:

This is a general error code set when the reason code is unknown.

<INCOMPLETE RULE>

Reason:

The rule does not have any rule actions defined to it.

<INV DATE MASK-ERROR>

Reason:

The data in the specified data generation field does not match the mask specified in the date aging format field.

<INV NUMBER-ERROR>

Reason:

The data specified in the data generation field is not numeric.

<M,D,Y IS NOT NUM-ERROR>

Reason:

The month, day, or year in the data generation field location is not numeric.

<MULTI ACTION-ERROR>

Reason:

More than one delete screen or insert test stream rule action was specified for the same screen.

<NEGATIVE DATE-ERROR>

Reason:

The date generated has a negative value.

<NESTED ACTION-ERROR>

Reason:

A nested delete or insert test stream rule action was specified, which is not allowed.

<NO ATTR ROW-COL-ERROR>

Reason:

An attribute byte was missing for this row-column location.

<NO CUT DATA-ERROR>

Reason:

The requested cut data does not exist, so it cannot be pasted.

<NO MODEL SCREEN>

Reason:

No model screen applies to this rule.

<NOT APPLICABLE DURING RUN>

Reason:

This is a LOGGING rule action and is ignored during a run.

<NOT APPLIED>

Reason:

This rule or rule action has not been applied.

<NOT RECOGNIZED>

Reason:

The recognition criteria did not match.

<NOT RECOGNIZED-NOT APPLIED>

Reason:

The recognition criteria did not match, so the rule was not applied.

<NUM OVERFLOW-ERROR>

Reason:

An overflow condition occurs when the value of a field is too large to fit in the field length specified on the data generation rule action. Either re-specify the length or set OVERFLOW equal to YES.

<OUTBOUNDS-ERROR>

Reason:

The row, column, and length coordinates of this rule action are outside the screen size of the terminal used by Run.

<OUTBOUNDS-NOT RECOGNIZED>

Reason:

The row, column, and length coordinates of the recognition criteria are outside the screen size of the terminal used by Run.

<RECOGNIZED>

Reason:

The recognition criteria matched.

<SCREEN FAILURE-ERROR>

Reason:

A screen failure occurred because the attributes for the expected screen did not match those of the current screen. Check that all rules for deletes, moves, and changed fields are correct. The row, column, and length coordinates of this rule action overlap the position where the attribute mismatch was detected.

<SCREENID NOT EQ-NOT APPLIED>

Reason:

The specified screen ID did not match, so the rule was not applied.

<T/S EMPTY-ERROR>

Reason:

The test stream to be inserted is empty.

<T/S IN USE-ERROR>

Reason:

The test stream to be inserted is in use.

<T/S I/O-ERROR>

Reason:

An I/O error occurred reading the test stream.

<T/S IS MTTS-ERROR>

Reason:

The test stream to be inserted is a multiple terminal test stream.

<T/S NOTAUTH-ERROR>

Reason:

The test stream to be inserted is READ protected.

<T/S NOTFOUND-ERROR>

Reason:

The test stream to be inserted is not in the TCADS.

<T/S REC#1 NOT OUTPUT-ERROR>

Reason:

The first record in the test stream is not an output record.

VARIABLE CONFLICT - WARNING

Reason:

A variable rule action overlapped row and column location with a non-variable rule action; an informational warning.

Action:

Verify that the overlap is what you intended, then continue the Run. The conflict does not have to be resolved or bypassed.

WARNING

Reason:

An informational warning.

Action:

Verify that the overlap is what you intended, then continue the Run. The conflict does not have to be resolved or bypassed.