When running a Perl or Python script on a Unix/Linux host using in a Control-M job with the "What" attribute set to Embedded Script, the job fails with the error "command not found".

Executing a job on a Unix/Linux host as an Embedded Script such as with:  perl (#!/usr/bin/perl) or python (#!/usr/bin/env python), the following error occurs in the job output: 

"command not found"

The Control-M/Agent is expecting a common shell script as a the Embedded Script.
The header containing the interpreter is ignored and the commands are not parsed using a perl or python interpreter.

The embedded script can run perl or python with small modifications

Rather than specifying  #!/usr/bin/perl in the header, execute the perl script by redirecting STDIN to the perl interpreter.
For example, set the Embedded Script to use a redirect similar to the example below:
==========
/usr/bin/perl << EOF
print "Testing Embedded Scripts \n";
exit
EOF
==========

This can also be used with Python