other members of the WG21 SG5 Transactional Memory Sub-Group Abstract. The OpenMP specification lacks a shared memory concurrency mechanism that is composable. None of the OpenMP concurrency mechanisms, such as OMP critical, locks, or atomics support composition. In this paper, we motivate the need for transactional memory (TM) in OpenMP chiefly to support composition of realistic programs. However, we also consider whether TM is easier to program than locks; the use-case for TM; and whether a software-only TM can outperform traditional locking through a survey of recent publications. This paper advances upon previous proposals of OpenMP TM by introducing a new construct specifically to handle irrevocable actions, which is also composable. It also proposes a pure atomic transaction construct as well as the concept of transaction safety. Further, we examine how our proposed construct integrates with current OpenMP constructs.