Exceptions

The following cases are exceptions to z/TPF transaction services processing.
  • Unsupported functions
    • Processing of general files or general data sets is not considered part of the commit scope and is not affected by commit scope processing. All updates to general files are made at the time of the macro request using standard z/TPF logic. A rollback transaction will not undo these updates.
    • Processing of find/file single and find/file special macros is not supported in the commit scope and causes the transfer of control to the system error routine.
  • Functions that do not work
    Applications that do any of the following must ensure that data is committed; that is, the commit scope is ended before using any of the following:
    • Pass file address or file chains to other application functions or system functions that run either on a separate ECB or without an ECB
    • Use techniques that coordinate updates to both core and file records without relying on find-and-hold processing for concurrency control
    • Use hold techniques other than DASD holds.
  • The following system functions will not work when called from a commit scope:
    • ROUTC, SENDC, and CVIx, where the ROUTC macro is issued. System error CEC136I is taken in this case. System error CEC137I is taken when the chain message is sent using CVIx.
    • Systems Network Architecture (SNA) message recovery.