CPSM should allow multiple events to be named in a WLMSPEC and in a TRANGRP

Description: Dave Williams and Mayur Raya did take a look at the batchrep dump of the WLM definitions and, as discussed during today's call, we noticed that although two RTADEFs had been defined (one called MAKESICK and the other called DB2DEFCO), WLMSPEC T0WPS33P named event MAKESICK while the associated TRANGRP T0WPTRN did not name any events in the EVENTNAME field. We did consider naming DB2DEFCO in the TRANGRP but this would not work as FI requires since the event specified at the TRANGRP level would override the event specified at the WLMSPEC level. FI needs both events to be active at the same time, but based on their associated period definitions. In the RTADEF, you can specify multiple evaluation expressions (like: EVALEXPRTEXT(MAKESICK|DB2EVACO)) but this still would not address FI's scenario since it is not possible to associate multiple period definitions with a single RTADEF. We concluded that CPSM does not currently support the function that FI is trying to achieve. What FI really needs is to be able to name multiple events on a WLMSPEC or a TRANGRP. This would ensure that the associated period definitions are taken into account.
Suggested Solutions: What FI really needs is to be able to name multiple events on a WLMSPEC or a TRANGRP. This would ensure that the associated period definitions are taken into account.