Comment Record

Comment records store comment text about the member’s account.

This document contains the field name, field description, field number, mnemonic, data type, and default information for each field. Other pertinent information includes:

**Source**  
Indicates where the data in the field comes from:

    **User-entered**  
    The user creates the information in this field.

    **System-entered**  
    A system process populates the value for the field. This value can include data transmitted by the ATM network, when applicable.

    **System-calculated**  
    The system calculates but does not store the value of the field each time the field appears on an inquiry or file maintenance screen.

The Comment record includes the fields defined here:

Comment Type

This field stores a code that indicates how and when the system should display the comment.

Data Type Descriptions

(0) Inquiry Only

The system should display the comment only during account summary inquiries, according to the values in the Effective Date and Expiration Date fields.

(1) Display every access

The system should display the comment each time the account is accessed, according to the values in the Effective Date and Expiration Date fields.

(2) Tickler Report

The system should display the comment each time the account is accessed, and the comment should print on the Account Comments Journal produced by the Daily Posting batch program, according to the values in the Effective Date and Expiration Date fields.

(3) Tickler Report and Force Display

The system should display the comment each time the account is accessed, regardless of the values in the Effective Date andExpiration Date fields. The comment should print on the Account Comments Journal produced by the Daily Posting batch program, according to the values in the Effective Date and Expiration Date fields.

Comment

This field stores up to 40 characters comment text.

When using the PowerOn batch program to post a transaction comment that is 16 characters or fewer, the comment appears in the Description field of the associated transaction.

Effective Date

This field stores the date that the system should begin to display the comment.

This field defaults to the system date during creation of the Comment record. You can change the date, if desired.

Expiration Date

This field stores the date after which the system should no longer display the comment.

If you try to enter a value in this field before the value in the Effective Date field, the system displays the following message: You must either enter a date after the value in the Effective Date field or leave this field blank.

Expiration cannot be before effective

When the system date exceeds the value in the Expiration Date field, the comment does not display, unless you selected (3) Tickler Report and Force Display at the Comment Type field. In that case, the comment does not display on the Account Comments Journal produced by the Daily Posting batch program, but continues to display each time the account is accessed.

Record Change Date

The system stores the system date in this field when you create, change, or save the Comment record. Sometimes the system updates this field because the record was saved, even though there may not be any actual changes in the record.

Note: The system does not change the Record Change Date when a calculated field changes.

You cannot change the value of this field.

Non-Displayed Fields

These Comment fields do not appear in the system and are only accessed by PowerOn specfiles or SymXchange.

Locator

This field stores a unique number within each member account that can be used as a unique identification of this record.

The system automatically assigns the value in this field when the record is created, and you cannot change it. The value is a positive number greater than zero and up to about two billion.

This field can be used during PowerOn file maintenance (both on demand and batch) to uniquely identify a record. Using this field is recommended since a record’s ordinal sequence number may change if someone else inserts or deletes a record with a lower ordinal sequence number just before you post your file maintenance.