Solution : https://service.sap.com/sap/support/notes/642464 (SAP Service marketplace login required)
Summary :
The SAP Note explains that issues with the sapevt program's inability to initiate batch events are often due to the absence of essential parameters defining the message server host (mshost) and service name (msserv). It refers to settings in the default profile, `default.pfl`, which should ideally contain these parameters if they are not explicitly provided via the command line. For proper program functionality, users should either specify these parameters directly or ensure their presence in the default profile located at system-specific paths noted within the document. Additionally, it emphasizes the sensitivity of path and file names, particularly in cluster environments, and suggests always verifying the correct profile path as per DIR_PROFILE in transaction AL11.
Key words :
rdisp/mshost = <mshost>rdisp/msserv = <msserv>commentsremark 1, \\<localhost>\sapmnt\<sid>\sys\profile\default, /usr/sap/<sid>/sys/profile/default, sap message server host, profile pf=<profile file>, rdisp/msserv_internal reason, parameter rdisp/msserv_internal, pf=<pathname>\<filename>, suitable profile file, determine mshostthis means
Related Notes :
| 1468187 | IBM i: Installing SAPEVT without SAP system |
| 835483 | Background kernel corrections (composite SAP note) |
| 826779 | sapevt (Version 5): Security settings in the Msg. |
| 821875 | Security settings in the message server |
| 802172 | sapevt (Version 4): Release-independent version |