Skip to main content

AsyscoAMT ACS Reference

Theme: Troubleshoot | Audience: System Administrator, Automation Engineer

What is it?​

This page provides reference information for the AsyscoAMT ACS connector, including completion codes returned by the AMT Batch Server, administration and security guidance, and troubleshooting information.

Use this page when:

  • You need to look up the meaning of an AMT completion code returned in a job log.
  • You are administering the integration or reviewing security requirements.
  • You are troubleshooting a failed or unexpected job result.

Failure criteria​

The Asysco AMT ACS integration returns a success or failure completion status. The actual Asysco AMT completion code is displayed in the job log. Error information about a task execution will also be displayed in the job log.

CodeStatusDescription
0IDLEJob is idle
1QUEUEDJob is queued for future start in current timeframe
2RUNNINGJob was started manually or by the scheduler
3KILLEDJob was terminated by a 'kill' command
4DONEJob completed normally
5SUSPENDEDQueued job has not started on time
6SKIPPED_BY_OPSSuspended job has been skipped by control center
7RUN_MANUALJob was started by control center
8RUN_FORCEDForced start manual; start this job even when job server halted
9RUN_DEBUGWhen a report is started from Visual Studio
10DEL_QUEUEJob is deleted from queue
11ERRORJob ended in error. When executing a script and the script does not exist, an error code of 11 is returned with a description of 'File not found'
12ABORTEDThe job was aborted on purpose in the business-logic
13WAIT FOR FILEWaiting for a file
14WAIT FOR INPUT REQUESTWaiting for request
15WAIT FOR JOBWaiting for another job to finish
16WAIT FOR REPORTWaiting for a report to finish; for future use
18RECOVER_CPThis job (report) is a request to recover from a saved critical point
19UNDEFINEDState is undefined
20WAIT_FOR QUEUEWaiting for queue start time
21WAIT_FOR_DEBUGGERWaiting for a LION Debugger to start debug session for the job
22ABORTED_WITH_RECOVERAborted with recover
23WEB_SERVER_ERROR—
24AUTHENTICATION_ERROR—
99INVALID AMT USERWhen executing an AMT script with a named AMT user and the user is invalid

Common errors​

Error 11 (ERROR) — The job ended in error. When executing a script, this often means the script file was not found on the AMT Batch Server. Verify the path specified in the Script Name field exists on the server.

Error 23 (WEB_SERVER_ERROR) — The connector could not reach the AMT Batch Server. Verify that the Batch Server URL is correct and that the server is running and accessible from the OpCon environment.

Error 24 (AUTHENTICATION_ERROR) — The API credentials were rejected by the AMT Batch Server. Verify that the Batch User identifier and password are correct and that the user exists in the AMT environment.

Error 99 (INVALID AMT USER) — The user specified in the User field of the script task does not exist in the AMT environment. Verify the user name or leave the field blank to use the Application user.

Administration​

Enable and disable the connection​

To enable the AsyscoAMT Batch Server connection, select Change Communication Status on the agent and select Enable Full Comm. To disable the connection, select Disable Full Comm. When disabled, OpCon cannot submit jobs to the AMT Batch Server.

Required roles​

Configuring the AsyscoAMT agent connection and Batch User requires OpCon role-based access to the Library administration area. Defining and editing AsyscoAMT jobs requires access to Master Jobs within Library.

Maintenance​

  • Log retention: Job log files are retained for the number of days specified in the Retain Log Files field on the agent connection. The default is 30 days.
  • Credential updates: If the AMT API user password changes, update the Batch User record in OpCon to restore authentication.

Kill job​

The Asysco AMT ACS integration supports the ability to terminate a task within the Asysco AMT Batch Server. When the Kill job status is selected within OpCon, an immediate kill request for the task is submitted to the AsyscoAMT Batch Server.

Security considerations​

Authentication — The AsyscoAMT connector authenticates with the AMT Batch Server using an API user name and password stored as a Batch User record in OpCon. The password is stored encrypted in the OpCon database.

Authorization — Access to the agent connection configuration and Batch User records is controlled by OpCon role-based permissions. Only users with appropriate Library administration access can configure the integration.

Data security — Job parameters, task values, and script parameters are transmitted to the AMT Batch Server through the REST-API. Use an HTTPS Batch Server URL in production environments to encrypt data in transit.

Sensitive data — The Batch User credentials provide API access to the AMT Batch Server. Store them using the OpCon Batch User mechanism and do not embed credentials in job parameters or task values.

Operations​

Monitoring​

The AsyscoAMT connector reports job status to OpCon in real time using AMT completion codes. Monitor jobs in Solution Manager for codes that indicate abnormal states: ERROR (11), ABORTED (12), AUTHENTICATION_ERROR (24), and WEB_SERVER_ERROR (23).

The agent connection status in Solution Manager indicates whether communication with the AMT Batch Server is active.

Alerts​

Configure OpCon notifications for jobs that return the following completion codes:

  • 11 (ERROR) — Job ended in error; review the job log for details.
  • 12 (ABORTED) — Job was aborted by application business logic.
  • 23 (WEB_SERVER_ERROR) — Connectivity issue with the AMT Batch Server.
  • 24 (AUTHENTICATION_ERROR) — API credential failure.

Performance and scaling​

The connector communicates with the AMT Batch Server REST-API synchronously. High concurrency of simultaneous AMT jobs may be subject to the AMT Batch Server's own queue and throughput limits. Job log files accumulate over time; the Retain Log Files setting controls disk usage.

Job log​

When a task is executing within the AMT environment, the job log is written to the database. This includes the information about the task as well as any children of the task. When the task completes, the ACS Integration retrieves the information from the database and adds it to the OpCon job log, making it available via JORS. JobLogs for AsyscoAMT ACS integration tasks can only be viewed within Solution Manager.

Frequently asked questions​

Why must Submit User remain set to BATCH and Station remain set to OPCON?

These values are required by the AMT Batch Server to correctly identify and route requests from OpCon. Changing them causes job submission to fail.

Can I define multiple AsyscoAMT agent connections for different AMT environments?

Yes. Each connection points to a different Batch Server URL. Jobs select their target connection through the Integration Selection field in the task definition.

How long are job logs retained?

Job log files are retained for the number of days specified in the Retain Log Files field on the agent connection. The default is 30 days.

What happens if the AsyscoAMT Batch Server is unreachable when a job runs?

The task receives a WEB_SERVER_ERROR (23) completion code. Check the Batch Server URL and network connectivity, then restart the job.

Can AsyscoAMT job logs be viewed in the OpCon Legacy Enterprise Manager?

No. JobLogs for AsyscoAMT ACS integration tasks can only be viewed within Solution Manager.

Examples​

Scenario: A Batch Job named REPORTTEST01 runs successfully in the DEMO2 application, completing in approximately 30 seconds. The job log shows progress messages and a final Done status.

---------------------------------------------------------------------------
Job Information -----------------------------------------------------------
Server          : http://10.1.29.5:9001
Application     : DEMO2
Submit User     : BATCH
Station         : OPCON
Queue Name      : 
Batch Job       : REPORTTEST01
Parameters      :
---------------------------------------------------------------------------
Completion Code : DONE
---------------------------------------------------------------------------
Job Log -------------------------------------------------------------------
"Started Rev: 1.3 AMT: 8.0.24223.0. Params: LOADINBATCHCONTROLLER /R:4280 /USEWORKINGDIR"
"Report test 01 is started"
"Report test 01 user BATCH"
"Report test 01 Value param []"
"Report test 01 is running 0 seconds"
"Report test 01 is running 10 seconds"
"Report test 01 is running 20 seconds"
"Report test 01 test is ended"
"Report execution time: 00:00:30:229"
"Done"
---------------------------------------------------------------------------

Scenario: A Script Job fails because the PowerShell executable (pwsh) is not found on the AMT Batch Server. The job log returns ERROR (11) with a file not found message. Verify that PowerShell is installed on the server at the expected path.

---------------------------------------------------------------------------
Job Information -----------------------------------------------------------
Server          : http://10.1.29.5:9001
Application     : DEMO2
Submit User     : BATCH
Station         : OPCON
Queue Name      : 
Script Job      : F:\Amt\Scripts\DEMO2\RUN_FILENAMETEST.ps1
Parameters      :
---------------------------------------------------------------------------
Completion Code : ERROR
---------------------------------------------------------------------------
Job Log -------------------------------------------------------------------
"Error starting job []"
"[An error occurred trying to start process 'pwsh' with working directory 'F:\\AMT\\SCRIPTS\\DEMO2'. The system cannot find the file specified.]"
---------------------------------------------------------------------------

Scenario: A long-running Batch Job is terminated by a Kill command issued from OpCon. The job log shows a KILLED completion code with no additional log entries.

---------------------------------------------------------------------------
Job Information -----------------------------------------------------------
Server          : http://10.1.29.5:9001
Application     : DEMO2
Submit User     : BATCH
Station         : OPCON
Queue Name      : 
Batch Job       : LONGRUNNINGREPORT
Parameters      :
---------------------------------------------------------------------------
Completion Code : KILLED
---------------------------------------------------------------------------
Job Log -------------------------------------------------------------------
---------------------------------------------------------------------------

Glossary​

AMT Batch Server — The Asysco LION component that receives, queues, and executes batch jobs and scripts. The AsyscoAMT ACS connector communicates with the server through its REST-API.

Batch User — An OpCon credential object that stores the API user name and password used to authenticate with the AMT Batch Server.

Completion Code — A numeric status returned by the AMT Batch Server indicating the final state of a job. Codes are mapped to named statuses such as DONE, ERROR, or KILLED.

JORS (Job Output Retrieval System) — The OpCon service that provides access to job logs after a task completes. AsyscoAMT job logs are retrieved from the AMT database and made available through JORS.

Task Values — Name=value pairs passed to an AMT Batch Job to modify, override, or extend predefined task attributes at execution time.

Related topics: