Differences when you edit a related table

A File Manager/Db2 Edit session for a related table is similar to a typical Edit session, with the following exceptions:

• The new session starts with the display of data for the related table.
• You cannot change the edit options. The current global edit options apply.
• There is no opportunity to edit the template before displaying the data.
• The panel title shows Table Edit (related) (instead of Table Edit).
• The location information is replaced with either PARNT or DPDNT and the name of the other object in the relationship. PARNT indicates that the other table is the parent table in the relationship. DPNDT indicates the other table is the dependent table in the relationship.
• For a dependent table, the template includes a WHERE clause that limits the data displayed to only those rows that match the primary key value in the parent table. If the parent table is subject to a self-referencing constraint, all rows might be displayed.
• The template includes information about the order in which columns are displayed. Columns that comprise the primary or foreign key are displayed (in order) at the left (TABL display format), or top (SNGL display format), of the other object in the relationship.
• In TABL display format, columns that form part of the relationship's key are identified with a K in the sixth character of the scale header line.
• If an Edit session has active dependent Edit sessions (that is, you have used either the REDIT primary command or the RE prefix command to start another FM/Db2 edit session of a related table, and that Edit session is still active), you cannot save any changes you have made to data until you end all dependent Edit sessions.
• If you cancel an Edit session that has active dependent Edit sessions, FM/Db2 also cancels all dependent Edit sessions. Any uncommitted changes in the canceled dependent Edit sessions are lost.