Is it possible to create manually a dump?
I have a question about Dumps created in SAP while programs run with unpredicted errors.
I have a specific table defined in the dictionary which has two coloumns progId and path.
The first one is a unique identifier given to a program and the second column is an absolute path on the
unix server where SAP is installed.
MyProg | /usr/tmpbatch/data/E200
Means that the ABAP program named 'MyProg' will run and its output file (the output of the program) and the
log file are created in /usr/tmpbatch/data/E200.
In each of my programs, first of all I check the content of this table in order to ensure that the path is defined for the
given program (and therefore I may be able to create avec success both output and log files). If there is no entry
in the table for the given program, I leave the program by calling the STOP instruction.
My programs run at night, so the next day the corresponding users read the content of the generated output/log files.
As a result, if the path is not defined properly for a given program in the table, the program is not run and therefore
there will be no output/logfile the next day.
My question is How can I inform the user who arrives the next day observing that one program has not been run? How
can I tell him by some kind of system message that the program exited because the path for the files had not been defined in
Each morning, we can analyse the dumps which were produced during the precedent day. So that we may know
(approximately) what went wrong. But as far as I know, dumps are generated automatically by the system. Is it possible
to generate a dump (by calling some fucntion) with an appropriate error message for my problem?
Thanks in advance,
Thomas Zloch replied
If you really want to create dumps for such purpose, you could issue a MESSAGE of type X, which will lead to a short dump MESSAGE_TYPE_X that will also show the message text. Another way would be to use the statement ASSERT, which would create a dump ASSERTION_FAILED when the condition is false.
Check ABAP documentation for these statements.
But maybe there is a "softer" way to alert your users, like job logs, emails, ...