To configure message destination overrides, create a file called EDMMSGO.
A sample EDMMSGO member is provided in the SAMPLIB library on z/OS. You can copy and customize this member, or you can create a sequential data set and define the message destination override statements in this data set. In the JCL for tasks and jobs that produce messages with message destination overrides, add an EDMMSGO DD statement that points to the customized EDMMSGO member or sequential data set.
In the EDMMSGO file, specify message destination override statements. A message override statement includes the message number followed by one or more message destination options. To override an EDM message, the message number must exist within the context of the PowerExchange component issuing the message.
On z/OS, the following PowerExchange components can issue messages that have their destinations overridden by the EDMMSGO file.
PowerExchange Agent
Issues EDM messages to the EDMSLOG data set, provided that the SUBSYS option is specified as the override destination in the message destination override file. See the SUBSYS destination.
Issues the following messages with destinations
that cannot be overridden by the EDMMSGO file: PWXEDM172000 through
PWXEDM172299 and PWXEDM181200 through PWXEDM181299.
PowerExchange Logger
Log Read API (LRAPI)
Log Write API (LWAPI)
Environmental Change Capture Routines (ECCRs), including the Db2 for z/OS and IMS synchronous ECCR.