Panther/JAM is an event driven tool. Almost everything that happens during the life span of a Panther application is identified as a type of event. Below is a list of the events that are triggered in order from the time a screen opens until it loses focus.

Order of Panther Events
OPEN Processing: sm_jwindow(sm_*_window), examining LDB before screen for field references
1. The unnamed procedure of the screen
1.1 The unnamed procedure of any public or include file
2. Transaction Manager Initialization
EXPOSE Processing starts here
3. The default Screen Entry function
4. The named Screen Entry function
5. ##Active LDBS flush to screen
6. ##Contexts bits on fields initialized (On open only)
End Screen Entry
Examining the screen before LDB for field references
Begin Field entry: sm_input()
7. The default field entry function
8. The named field entry function
End Field Entry
9. The AUTO Control String of screen on top of stack processed
sm_getkey()
10. Keyboard opens, display updates if no unprocessed keys

## TM hook functions aren’t allowed to be added to these events.