3534565 - SUM stops at MOD_SELROADMAP/BEGIN phase with "SYSTEM MANAGER: system without sapcontrol is not allowed"

You are doing ABAP system upgrade via SUM.
An error occurred in phase "MOD_SELROADMAP/BEGIN". In phase log file "PHASE_BEGIN.LOG", there is following error.

1 ETQ399 SAPCONTROL MANAGER: call sapcontrol feature check
1 ETQ399 SAPCONTROL MANAGER: call (sapcontrol) failed with return code '-1' ()
1EETQ399 SAPCONTROL MANAGER: call (sapcontrol) failed with return code '-1' ()
1 ETQ399 SAPCONTROL MANAGER: getSystemInstanceList with dumpfile: ~/SUM/abap/log/SAPCONTROL_INSTANCELIST.OUT
1 ETQ399 SAPCONTROL MANAGER: call (sapcontrol) failed with return code '-1' ()
1WETQ399 SAPCONTROL MANAGER: call (sapcontrol) failed with return code '-1' ()
1WETQ399 SYSTEM MANAGER: initialize instance list has failed.
1EETQ399 Last generated error message is: SYSTEM MANAGER: system without sapcontrol is not allowed.
1EETQ204 Upgrade phase "BEGIN" terminated with severe errors ("<timestamp>").

The dump file SAPCONTROL_INSTANCELIST.OUT does not exist.

In ENVDUMP.LOG,  you find that kernel directory path is not included in the value of environment variable "PATH" or "LD_LIBRARY_PATH". However,  you can find the value with command "env".

NetWeaver ABAP system.

Red Hat Enterprise Linux 8.0 or 8.1

SYSTEM MANAGER: system without sapcontrol is not allowed, Red Hat Enterprise Linux, RHEL, 8.0, 8.1, setup , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-OP-LNX-RH , Red Hat Linux , Problem