You cannot trigger a batch event using the program sapevt. The trace file dev_evt contains the following line:
SAP message server host:
or
*** ERROR ***: Cannot determine mshost
This means that the program sapevt could not determine the name of the host in the target system on which the message server is running.
Apart from EventID, optional event parameters, and optional trace switches, the program sapevt requires two further parameters, which are used for structuring the communication to the target system. These parameters are:
1. The name of the message server (parameter mshost)
2. The name of a service on the message server (parameter msserv)
There are many ways of specifying these two parameters, both by using the command line and by specifying the parameters implicitly.
This note describes how to specify these parameters implicitly.
Each time the program sapevt cannot retrieve the parameters mentioned above from the command line, it accesses the default profile for sapevt. This is a file called default.pfl, which can be at any location in the file system, but whose path can be created by sapevt on the basis of the specified parameters.
!!! Important!!! :
The user of sapevt is responsible for ensuring that sapevt is supplied with the required information.
Especially in Microsoft cluster environments, the default profiles specified below are not always available.
Instead of relying on the existence of these default profiles, we recommend explicitly specifying the name of a suitable profile file in the parameter string of sapevt, that is (for Windows):
pf=<pathname><filename>
The path for the default profile for sapevt
sapevt only requires the name of the target system to create the path. This should be specified explicitly: either as the parameter name=<SID> in the command line or as one of the standard parameters in the profile pf=<profile file>. However, there are two different cases: Operating systems similar to Unix and operating systems from the Windows family.
- Operating systems similar to Unix:
/usr/sap/<SID>/SYS/profile/DEFAULT.PFL
Comment: This is case-sensitive. - Operating systems from the Windows family:
\<localhost>sapmnt<SID>sysprofiledefault.pfl
Remark 1: Note that this path refers to a global (shared) directory called "sapmnt".
Remark 2: Path names and file names are also case-sensitive in Windows operating systems.
The path name may also be as follows:
\<localhost>sapmnt<SID>SYSprofileDEFAULT.PFL
In particular, this is important if you want to transfer this path name to the configuration file of the transport system (parameter SYSTEM_PF, also see Note 449270).
We recommend that you use the spelling from DIR_PROFILE (transaction AL11).
The contents of the default profile for sapevt
As already mentioned at the beginning of this note, the default profile is only accessed if the parameters mshost and msserv are not specified explicitly. To be able to find these parameters in the default profile, they must be defined there as follows:
rdisp/mshost = <mshost>
rdisp/msserv = <msserv>
Comments
Remark 1: See Notes 826779 and 821875 to determine whether and how the parameter rdisp/msserv_internal has to be defined.
Remark 2: The last line of a profile must be a blank line.
Remark 3: msserv usually has a value that is as follows: sapms<SID> (see Note 802172). Since the parameter name (<SID>) is already known when the default profile is read, the parameter msserv can be omitted. It is then generated automatically.
Remark 4: Instead of creating a new file, you can use the default profile of the message server, where the parameters mentioned above are also defined. Copy this profile into the corresponding directory and rename it if necessary.