Figures

  1. Components of a BTS application
  2. A sequence of activations
  3. Comparison between a terminal-related pseudoconversation and a BTS activity that is activated multiple times
  4. Activity mode transitions
  5. Composite events
  6. Sub-event queues
  7. An event pool
  8. A reattachment queue
  9. Handling reattachment events
  10. Handling atomic events
  11. Data flow in the Sale example application
  12. Pseudocode for the SAL001 program
  13. Pseudocode for SAL002, the root activity program for the Sale business transaction
  14. Creating the Delivery activity
  15. Pseudocode for the Delivery activity
  16. Requests to create and activate an activity
  17. Data flow for parallel activities
  18. The SAL002 root activity program, with modifications for parallel activities highlighted
  19. Example client program, PRG001
  20. Example server program, SRV001
  21. Acquiring an activity
  22. Data flow in the Sale example application, showing user-related activities
  23. The SAL002 root activity program, with user-related modifications highlighted
  24. Pseudocode for the CON001 program, that implements the Confirm activity
  25. Pseudocode for the USRCON program, that implements the USRX transaction
  26. Process flow with compensation actions included
  27. The SAL002 root activity program, including compensation actions
  28. Running a 3270-based transaction as a BTS activity
  29. Pseudocode for running a 3270-based transaction as a BTS activity
  30. Running a 3270 conversational transaction as a BTS activity
  31. Pseudocode for running a 3270 conversational transaction as a BTS activity
  32. Pseudocode for running a 3270 pseudoconversational transaction as a BTS activity
  33. Pseudocode for dealing with an abend of the 3270 transaction
  34. Example JCL for defining a BTS repository data set
  35. Example JCL for defining a BTS local request queue data set
  36. The supplied, default, FILE definition for the LRQ
  37. PROCESSTYPE definitions, FILE definitions, and repository data sets
  38. The DEFINE panel for PROCESSTYPE
  39. CBAM transaction: initial screen, showing the process-types defined to this region
  40. CBAM transaction: processes screen
  41. CBAM transaction: activities screen
  42. CBAM transaction: activity details screen
  43. CBAM transaction: containers screen for a process
  44. CBAM transaction: containers screen for an activity
  45. CBAM transaction: events screen
  46. CBAM transaction: timers screen
  47. CEMT INQUIRE PROCESSTYPE screen
  48. The expanded display of an individual entry
  49. CEMT INQUIRE TASK screen
  50. The expanded display of an individual entry
  51. Dynamic routing using a hub routing model
  52. Dynamic routing using a distributed routing model
  53. A sysplex containing two BTS-sets
  54. When and where the distributed routing program is invoked
  55. Example audit trails
  56. Sample job to run the DFHATUP utility program
  57. Example control statements, to format all the records for the SALES1234567890 process
  58. Example audit trail, showing the types of record written for process-level auditing
  59. Example audit trail, showing the types of record written for activity-level auditing
  60. Example audit trail, showing the types of record written for full auditing
  61. Sample job to run the DFHBARUP utility program
  62. Example control statements, to format all records on the SALEREP repository for the SALES1234567890 process
  63. Example output from the DFHBARUP utility
  64. CETR screen for specifying component trace options
  65. Format of the descriptions of the data fields
  66. Browsing example 1
  67. Browsing example 2
  68. Browsing example 3
[[ Contents Previous Page | Next Page Index ]]