Multi-trans programs should be trusted applications. They must do whatever cleanup is necessary between transaction programs to ensure that resources are released and programs are isolated from one another and from any resources used exclusively by the shell.

Except for the cleanup responsibilities, multi-trans scheduling provides the same security protection as standard scheduling (checking user IDs, passwords, and profiles passed on each inbound conversation request). Each conversation with a multi-trans program runs under a personalized security environment, based on the user ID associated with the inbound request, when the multi-trans shell issues Get_Transaction and Return_Transaction to process conversations.

Because the generic ID covers processing that typically must be isolated from the different conversation partners, the generic ID must be secure from unauthorized specification or modification. To protect the multi-trans TP profile, which contains the generic ID, you can use RACF® to control read and update access to the TP profile where the generic ID is specified. See Protecting Multi-Trans TP Profiles.