We would expect to see the dmemail.exe and dmschedule.exe processes started but they are not. In the dmpool trace file there is an error similar to the following:
(Note that if you define a work area with the same location in admin console (see slide 2) and tape the area-id:: in the work area field in desktop client then we can see the contents (see slide 3)) step 4 : remove DM_SDP_ TRACE in dm.cfg on the server and stop/start the listener
The above error can occur for numerous reasons. In order to aid in debugging this error, please set DFS tracing within the listener .dat file as follows:
a. An SDP trace reveals that the metadata creation routine RPC is sent to the build agent twice during target collection. This was probably the result of a failed attempt to fix metadata for placeholders. b. despite this, the resulting metadata is invalid.
The metadata processing is doing work which is wrong (not required, in error) on MVS, as shown in the trace file below: - 07:41:38.045678Z 0.000057 T405313664 rpc: RPCSrv: 18(RFREMOVEDIR)
In the old System Administrator tool when you clicked on the Workflows tab there was a Triggers button on the right that you could press and see the Triggers currently deployed to the App Engine. In the new Application Admin tool I can't seem to find any trace of the Triggers button or any way to see the triggers installed.
