Skip to main content

Job Initiation/Monitoring Troubleshooting

Job Stuck in "QUEUED" State​

Full Description​

Job stays in "QUEUED" state.

Possible Cause:​

The MIXLIMIT or TASKLIMIT attribute of the queue through which the job starts is preventing the job from being run.

Operator Response:​
  1. Check the MIXLIMIT and TASKLIMIT values for the job queue to confirm the values.

  2. Verify the job is in the queue.

  3. Increasing the MIXLIMIT or TASKLIMIT value, or changing the queue through which the job is run may be appropriate. For more information on this response, refer to MCP Agent Operation.

Job Stuck in "Start Attempted" State​

Full Description​

Job stays in a "Start Attempted" state.

First Possible Explanation:​

Communication with the agent has been lost.

First Operator Response:​

Verify the agent modules *SMA/COMM/xxx, *SMA/TCPIP/xxx, and *SMA/MCP/INTERFACE/xxx are up and running. For more information on this response, refer to *SMA/TCPIP.

Second Possible Explanation:​

*SMA/MCP/INTERFACE has left the active mix with the following error: "F-DS INVALID INDEX @ 02412000". The cause of this situation is failure to remove the *SMA/CP/MCS/= and *SMA/TRACKING/FILE file after changing the "max number of concurrent jobs" configuration variable.

Second Operator Response:​

After changing the configuration variable "max number concurrent jobs", remove the following files before starting the agent:

  1. *SMA/TRACKING/FILE/xxx ON <packname>

  2. *SMA/CP/MCS/xxx/= ON <packname>

  3. *SMA/CP/LIB/= ON <packname>

Be sure to check ALL families on the system - not just the family on which the agent runs.

This is one of several errors produced by the same cause. For the full list of errors, the module that reports each one, and the complete list of files to remove, refer to Update the "Max Number Concurrent Jobs" Field.

Job Stuck in "Wait Machine" State​

Full Description​

Job stays in "Wait Machine" state.

Possible Explanation:​

The maximum number of jobs is being run.

Operator Response:​

No action required. When the number of active jobs falls below the maximum for which the agent is configured, additional jobs are initiated by SAM. The agent may be configured for a maximum of 500 jobs. For more information on this response, refer to Update the "Max Number Concurrent Jobs" Field.

Job Status "0SNTX/SECRTY" Error​

Full Description​

Receiving a 0SNTX/SECRTY ERR status.

First Possible Explanation:​

The agent is running under a usercode without the correct privileges to run the job.

First Operator Response:​

Stop the agent and then start the agent under a usercode with correct privileges. For more information on this response, refer to Stop the MCP Agent.

Second Possible Explanation:​

The usercode being used to start the job does not have the privileges needed.

Second Operator Response:​

Verify the job's usercode on the Enterprise Manager's Job Details screen. For more information on this response, refer to MCP Job Details in the Concepts online help.

Third Possible Explanation:​

The queue through which the agent WFL runs has a TASKLIMIT.

Third Operator Response:​

Change the WFL CLASS attribute to a queue that does not have a TASKLIMIT value set. For more information on this response, refer to Using *SMA/WFL/COMMAND.

Job Status "NOT JOB FILE" Error​

Full Description​

Receiving a NOT JOB FILE error.

Possible Explanation:​

The WFL file's FILEKIND is not JOBSYMBOL, DATA, or SEQDATA. The MCP Agent accepts all three for a job initiated with the START command.

Operator Response:​

Using CANDE or DUMPALL, change the FILEKIND attribute of the WFL file to JOBSYMBOL, DATA, or SEQDATA. Contact the MCP-platform system administrator to request this action.

caution

Change the FILEKIND only when the file holds WFL source. Because the agent accepts DATA, a File Title that names a genuine data file passes this check and the agent compiles the data as WFL. The job then fails with WFL SYNTAX ERR rather than NOT JOB FILE. Verify the File Title names the intended WFL before changing any file attribute.

Job Status "INV PARM LOC" or "PARAM/ATTR" Error​

Full Description​

Receiving an INV PARM LOC or a PARAM/ATTR ERR status. Which of the two the agent sends depends on what the File Title field contains.

First Possible Explanation:​

On Enterprise Manager's Job Details screen, the job's "File Title" field contains a parameter in parentheses. Effective with MCP Agent 04.12, the agent detects the opening parenthesis and reports INV PARM LOC.

First Operator Response:​

On the Enterprise Manager's Job Details screen, place the parameter in the job's "Arguments" field. For more information on this response, refer to MCP Job Details in the Concepts online help.

Second Possible Explanation:​

The "File Title" field contains text following the file title that is not a parenthesized parameter, or a character that is not valid in a ClearPath MCP file title. The agent reports PARAM/ATTR ERR.

Second Operator Response:​

Remove the extra text from the "File Title" field, leaving only the file title of the process to start, and verify the title against the rules for entity names. Place any parameter in the job's "Arguments" field.

Note

Both statuses carry the mix number 00000, because the agent rejects the request before starting anything on the ClearPath MCP. For more information, refer to Machine Messages.

PROCESSCHECK not Working​

Full Description​

*SMA/WFL/PROCESSCHECK/xxx does not find WFL jobs that are active.

Possible Explanation:​

The target process is incorrectly identified using the name of the WFL file. When searching for a WFL job in the mix using *SMA/WFL/PROCESSCHECK, one must use the job name (from the ?BEGIN JOB line within the WFL file) and not the name of the WFL file. If the presence of the WFL file is in question, then the appropriate tool is *SMA/WFL/FILECHECK.

Operator Response:​

In the *SMA/WFL/PROCESSCHECK <Process Name>, replace the name of the WFL with the job name in the search criteria.