- Components of a BTS application
- A sequence of activations
- Comparison between a terminal-related pseudoconversation and a BTS activity that is activated multiple times
- Activity mode transitions
- Composite events
- Sub-event queues
- An event pool
- A reattachment queue
- Handling reattachment events
- Handling atomic events
- Data flow in the Sale example application
- Pseudocode for the SAL001 program
- Pseudocode for SAL002, the root activity program for the Sale business transaction
- Creating the Delivery activity
- Pseudocode for the Delivery activity
- Requests to create and activate an activity
- Data flow for parallel activities
- The SAL002 root activity program, with modifications for parallel activities highlighted
- Example client program, PRG001
- Example server program, SRV001
- Acquiring an activity
- Data flow in the Sale example application, showing user-related activities
- The SAL002 root activity program, with user-related modifications highlighted
- Pseudocode for the CON001 program, that implements the Confirm activity
- Pseudocode for the USRCON program, that implements the USRX transaction
- Process flow with compensation actions included
- The SAL002 root activity program, including compensation actions
- Running a 3270-based transaction as a BTS activity
- Pseudocode for running a 3270-based transaction as a BTS activity
- Running a 3270 conversational transaction as a BTS activity
- Pseudocode for running a 3270 conversational transaction as a BTS activity
- Pseudocode for running a 3270 pseudoconversational transaction as a BTS activity
- Pseudocode for dealing with an abend of the 3270 transaction
- Example JCL for defining a BTS repository data set
- Example JCL for defining a BTS local request queue data set
- The supplied, default, FILE definition for the LRQ
- PROCESSTYPE definitions, FILE definitions, and repository data sets
- The DEFINE panel for PROCESSTYPE
- CBAM transaction: initial screen, showing the process-types defined to this region
- CBAM transaction: processes screen
- CBAM transaction: activities screen
- CBAM transaction: activity details screen
- CBAM transaction: containers screen for a process
- CBAM transaction: containers screen for an activity
- CBAM transaction: events screen
- CBAM transaction: timers screen
- CEMT INQUIRE PROCESSTYPE screen
- The expanded display of an individual entry
- CEMT INQUIRE TASK screen
- The expanded display of an individual entry
- Dynamic routing using a hub routing model
- Dynamic routing using a distributed routing model
- A sysplex containing two BTS-sets
- When and where the distributed routing program is invoked
- Example audit trails
- Sample job to run the DFHATUP utility program
- Example control statements, to format all the records for the SALES1234567890 process
- Example audit trail, showing the types of record written for process-level auditing
- Example audit trail, showing the types of record written for activity-level auditing
- Example audit trail, showing the types of record written for full auditing
- Sample job to run the DFHBARUP utility program
- Example control statements, to format all records on the SALEREP repository for the SALES1234567890 process
- Example output from the DFHBARUP utility
- CETR screen for specifying component trace options
- Format of the descriptions of the data fields
- Browsing example 1
- Browsing example 2
- Browsing example 3
[[ Contents Previous Page | Next Page Index ]]