Explanation: The requested job FileName cannot be submitted due to a specific reason (reason). The reasons include:
For UNIX platforms:
File Path does not exist - the path/library is not found
Mem Name memName does not exist - the script is not found
User userName does not exist - there is a security violation
Run_As User % does not exist - there is a security violation
Run_As User % is not allowed to execute this script - there is a security violation
The script scriptName does not have execute permissions - there is a security violation
For Windows platforms:
There are currently no log in servers available to service the login request
Log in failure: unknown user name or bad password
Log in failure: user account restriction
Log in failure: account login time restriction violation
Log in failure: user not allowed to log on to this computer
Log in failure: the specified account password has expired
A specified privilege does not exist
A required privilege is not held by the client
The name provided is not a properly formed account name
The specified user already exists
The specified user does not exist
Log in failure: the user has not been granted the requested login type at this computer
A specified log in session does not exist. It may have been terminated
For all Platforms:
Control-M/Server hostName is not authorized to run jobs on this Agent - the Control-M/Server specified is not listed in the Authorized Control-M Servers list for the Agent platform
The job is not submitted.
Corrective Action: Examine the job processing definition to verify the information that caused the problem. Either make the necessary corrections, provide the necessary security authorizations, or add the Server platform to the Authorized Control-M Servers list. Rerun the job.
