COMMAND_NOT_FOUND

Former Member — Tue, 23 Oct 2007 16:14:59 GMT

Hi all,

while i am executing one of my Z-Program cursor goes to standard SAP program SAPLSSXP and gives me runtime error like

A RAISE statement in the program "SAPLSSXP" raised the exception

condition "COMMAND_NOT_FOUND".

Since the exception was not intercepted by a superior

program, processing was terminated.

Please help me out...

Regards,

Siva.

Re: COMMAND_NOT_FOUND

JozsefSzikszai — Tue, 23 Oct 2007 16:29:32 GMT

hi Siva,

check if OSS Note 947331 is relevant for you.

Re: COMMAND_NOT_FOUND

Former Member — Tue, 23 Oct 2007 16:32:46 GMT

Hi Siva,

Send the dump information for proper understanding.

Regards,

Sagar

Re: COMMAND_NOT_FOUND

Former Member — Wed, 24 Oct 2007 06:47:34 GMT

Hi sagar,

This is the short dump information.

Runtime Errors RAISE_EXCEPTION

Date and Time 22.10.2007 09:00:27

Short text

Exception condition "COMMAND_NOT_FOUND" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

A RAISE statement in the program "SAPLSSXP" raised the exception

condition "COMMAND_NOT_FOUND".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

How to correct the error

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"RAISE_EXCEPTION" " "

"SAPLSSXP" or "LSSXPF01"

"PROPAGATE_EXCEPTION"

"SAPLSSXP" "COMMAND_NOT_FOUND"

"COMMAND_NOT_FOUND"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

System environment

SAP-Release 700

Application server... "R3SDSNAA"

Network address...... "10.216.0.83"

Operating system..... "OS400"

Release.............. "5.3"

Hardware type........ "001000043PKM"

Character length.... 8 Bits

Pointer length....... 64 Bits

Work process number.. 3

Shortdump setting.... "full"

Database server... "R3SDSNAA"

Database type..... "DB400"

Database name..... "D03"

Database user ID.. "R3D03DATA"

Char.set.... "en_US.ISO8859-1"

SAP kernel....... 700

created (date)... "Aug 31 2006 21:07:20"

create on........ "AIX 2 5 005DD9CD4C00 (iSeries)"

Database version. "DB4_53"

Patch level. 75

Patch text.. " "

Database............. "V5R3, V5R4"

SAP database version. 700

Operating system..... "OS400 3 5, OS400 4 5"

Memory consumption

Roll.... 16128

EM...... 12569760

Heap.... 0

Page.... 57344

MM Used. 2292224

MM Free. 1895168

User and Transaction

Client.............. 215

User................ "SPADALA"

Language key........ "E"

Transaction......... "SE38 "

Program............. "SAPLSSXP"

Screen.............. "SAPMSSY0 0120"

Screen line......... 8

Information on where terminated

Termination occurred in the ABAP program "SAPLSSXP" - in "PROPAGATE_EXCEPTION".

The main program was "Z_DOWNLOAD_SPOOLFILE ".

In the source code you have the termination point in line 1890

of the (Include) program "LSSXPF01".

Source Code Extract

Line SourceCde

1860 ID 'PAR2' FIELD str.

1861 CALL 'WriteTrace'

1862 ID 'CALL' FIELD obj_external_program

1863 ID 'PAR1' FIELD ' Message texts:'. "#EC NOTEXT

1864 PERFORM trc_prot TABLES p_log USING ' '. "#EC NOTEXT

1865 ENDIF.

1866

1867 CALL 'WriteTrace'

1868 ID 'CALL' FIELD obj_external_program

1869 ID 'PAR1' FIELD '----

end -

1870 ENDIF.

1871

1872 ENDFORM. "trc_end_stat

1873

1874 &----

1875 *& Form propagate_exception

1876 &----

1877 * text

1878 ----

1879 * -->P_RC text

1880 ----

1881 FORM propagate_exception

1882 USING p_rc TYPE retcode.

1883

1884 CASE p_rc.

1885 WHEN 0.

1886 WHEN rc_no_permission OR

1887 rc_no_execute_authority.

1888 RAISE no_permission.

1889 WHEN rc_command_not_found.

>>>>> RAISE command_not_found.

1891 WHEN rc_parameters_too_long OR

1892 rc_parse_result_too_long.

1893 RAISE parameters_too_long.

1894 WHEN rc_security_risk OR

1895 rc_parse_opsys_conv_broken.

1896 RAISE security_risk.

1897 WHEN rc_wrong_check_call_interface OR

1898 rc_parse_wrong_interface OR

1899 rc_parse_cust_fm_doesnt_exist OR

1900 rc_parse_sap_fm_doesnt_exist.

1901 RAISE wrong_check_call_interface.

1902 WHEN rc_program_start_error.

1903 RAISE program_start_error.

1904 WHEN rc_program_termination_error.

1905 RAISE program_termination_error.

1906 WHEN rc_parameter_expected OR

1907 rc_parse_separator_missing OR

1908 rc_parse_par_expected.

1909 RAISE parameter_expected.

Contents of system fields

Name Val.

SY-SUBRC 801

SY-INDEX 0

SY-TABIX 1

SY-DBCNT 0

SY-FDPOS 40

SY-LSIND 1

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY ZDOSP

SY-UCOMM ZCHOOSE

SY-TITLE Handle Own Spool Files (alternative to SP02)

SY-MSGTY S

SY-MSGID Z_DOWNLOAD_SPOOLFILE

SY-MSGNO 003

SY-MSGV1

SY-MSGV2

SY-MSGV3

SY-MSGV4

SY-MODNO 1

SY-DATUM 20071022

SY-UZEIT 085854

SY-XPROG SAPFGUICNTL

SY-XFORM %_CONTROL_EXIT_DYNPRO

Active Calls/Events

No. Ty. Program Include Line

Name

5 FORM SAPLSSXP LSSXPF01 1890

PROPAGATE_EXCEPTION

4 FUNCTION SAPLSXPT LSXPTU03 74

SXPG_COMMAND_EXECUTE

3 FORM Z_DOWNLOAD_SPOOLFILE Z_DOWNLOAD_SPOOLFILE 576

RUNFAXER

2 FORM Z_DOWNLOAD_SPOOLFILE Z_DOWNLOAD_SPOOLFILE 525

CALL_TO_FAX

1 EVENT Z_DOWNLOAD_SPOOLFILE Z_DOWNLOAD_SPOOLFILE 225

ATUSER-COMMAND

Re: COMMAND_NOT_FOUND

JozsefSzikszai — Wed, 24 Oct 2007 06:51:44 GMT

hi Siva,

as I wrote, pls. check if the above OSS Note is relevant for you. You can do this in transaction SNOTE, you can even implement this note in this transaction as well. If does not help, you have to turn to OSS, because this is an error in the standard program.

Re: COMMAND_NOT_FOUND

Former Member — Wed, 24 Oct 2007 09:39:21 GMT

Hi Siva,

Thank you for sending the dump. It is not useful to analyze the code. If u don't mind send me the total code or part of the code under AT USER-Command.

Regards,

Sagar

Re: COMMAND_NOT_FOUND

Former Member — Fri, 26 Oct 2007 06:51:19 GMT

Thanks Sagar,

Problem was resolved and the solution is one command is not existed in Database Tables.

Regards,

Siva.

topic Re: COMMAND_NOT_FOUND in Application Development and Automation Discussions

COMMAND_NOT_FOUND

Re: COMMAND_NOT_FOUND

Re: COMMAND_NOT_FOUND

Re: COMMAND_NOT_FOUND

Re: COMMAND_NOT_FOUND

Re: COMMAND_NOT_FOUND

Re: COMMAND_NOT_FOUND