Programming Guide

Changes the transaction manager to update mode

int sm_tm_command ("COPY_FOR_UPDATE");

COPY_FOR_UPDATE changes the current mode to update. This allows the data currently displayed on the screen to be modified, as though it had been fetched from the database. After you select COPY_FOR_UPDATE, the transaction manager initializes before image processing.

If you edit the data and select SAVE, the transaction manager generates statements as if the data now on the screen had come from a SELECT command. If corresponding data is not in the database, the results might not be what you expect.

Push buttons and menu selections for the COPY_FOR_UPDATE command can choose to set the class property to continue_button since, by default, continue_button is active in view or update modes.

COPY_FOR_UPDATE is available from any mode. Select SAVE after you finish your edits.

The following requests can be generated by the COPY_FOR_UPDATE command to ascertain whether the changes from the previous command have been saved and, if desired, discard those changes:

• TM_PRE_CLOSE (described under CLOSE)

• TM_CLOSE (described under CLOSE)

• TM_QUERY (described under CLOSE)

• TM_DISCARD (described under CLOSE)

• TM_POST_CLOSE (described under CLOSE)

  Table 8-16 Request events for COPY_FOR_UPDATE

  Request	Traversal	Typical Processing
  TM_PRE_COPY_FOR_UPDATE	By table/server view from the specified table view	Do nothing
  TM_COPY_FOR_UPDATE	By table/server view from the specified table view	Do nothing (sm_bi_initialize and sm_bi_copy are called for the table view by the transaction manager after this request)
  TM_POST_COPY_FOR_UPDATE	By table/server view from the specified table view	Do nothing

---

---