Skip to main content

- - Knowledge base overview
Product Updates
Events
Groups
My Support Cases

Home
Search

Recently active topics

47 Topics

Andrea DowningSMA Community Team

published in REST API

Set OpCon API certificate

Set API certificate:This article will show you how to set an auto-signed certificate or your own signed certificate to your OpCon Rest. You'll find three scenarios :1. Generate a new self-signed certificate if no certificate found.2. Generate a new self-signed certificate if the existing certificate is expired.3. Set your own signed certificate. 1. No certificate found:In some cases the OpCon API is not reachable because the certificate is not find by the API, in this case you may only have to apply this procedure to allow the API to use it own auto-generated self-signed certificate : 1. Stop the RestAPI service: SMA OpCon RestAPI 2. Open a command prompt as Administrator 3. Navigate to the SAM folder (for installation on the system drive C:\Program Files\OpConxps\SAM) 4. Run the following command SMAOpConRestApi.Controllers.exe -setcertificate (for older version replaceSMAOpConRestApi.Controllers.exe by SMAOpConRestApi.OwinService) 5. Verify the process completed successfully, the log

Andrea DowningSMA Community Team

published in Basic Support

AIX System/Symitar Upgrade Preparation for OpCon

Use this document if performing one of the following functions:AIX upgrades Applying firmware updates Setting up a backup or failover system Applying a Symitar UpgradeOverviewPerform the following procedures for each Symitar box you are upgrading.💥DangerInstalling AIX completely replaces the operating system, including the /(root) file system in addition to /usr, /var, and /opt. You will need to reinstall any software placed in these file systems by third parties (including software by third-party web developers) that was not obtained through Symitar. If you do not copy the /ops/bin and /usr/local/lsam directories into an area saved by the AIX install (e.g., /SY</OP or a home directory), you will need to reinstall RSJ and the LSAM software to your host before attempting to run OpCon jobs on the upgraded server.💥DangerSimply performing a rcp copy will not properly install and configure SMA’s software. Failure to follow proper procedures will result in downtime. Validate sufficient

Andrea DowningSMA Community Team

published in Basic Support

Basic Troubleshooting Steps

Introduction to OpCon troubleshootingThis article is designed to introduce you to the basic troubleshooting of OpCon. It will provide you some tips to perform a first analysis of your environment if you encounter some troubles with OpCon or an agent based on Windows. This article will also provide you some reflexes with OpCon and will help you to identify faster what the issue is and eventually how to solve it.OpCon log filesOpCon log files are located under C:\ProgramData\OpConxps\SAM\Log if the installation is performed on the C: drive . If it's on a different drive, the log files are located under D:\OpConxps\SAM\Log for example.The log files will provide useful information about everything related to OpCon and it's important to start the troubleshooting from here. Every process has it own log file.FoldersArchives : last 10 days of OpCon log files are stored in this folder (default setting). Report : generated BIRT reports and associated log files are in this folder. SMASchedMan : c

Andrea DowningSMA Community Team

published in Basic Support

Cannot Retrieve a Job Log

When SAM attempts to process job starts and receives an arithmetic overflow:What is the issue?When you click on your job and "View Job Output", you may encounter a JORS error and not be able to retrieve your job log.If you see this error message, then your machine is not correctly configured.How to solve this?It's quick and simple! Just navigate on your Enterprise Manager to the Machines page, then select your machine.For this operation you'll need to stop the communication for a short moment, please make sure that you can briefly cut the communication without impacting your plan!Once the communication is stopped, click on "Open Advanced Settings Panel" and go to the second tab "Communication Settings". At the bottom of the page, you'll see "JORS Port Number". Just enter on this field the JORS Port Number of your LSAM. Usually, the JORS Port is the Communication port of your machine + 10 (e.g., 3100 for the communication, 3110 for the JORS).Once the modification is done, just save and

Andrea DowningSMA Community Team

published in Enterprise Manager

Enterprise Manager Report Takes Too Much Time to Load

You try to display the "Reports" page on your Enterprise Manager and you are stuck with a blank page after several minutes:How Enterprise Manager works with the reportsEnterprise Manager uses the Eclipse RCP framework behind the scene to run the app. EM is only made of plugins, that are dynamically loaded on demand when a plugin is opened. The Eclipse RCP framework use a plugins mechanism named OSGi to load plugins (JARs) - this controlled by the framework and EM have no control on it.When a plugin is loaded it means the JAR (which is an archive file, like a zip) is dynamically extracted in-memory (and some part may be extracted on the disk as well) for usage. When this happens, anything that filters I/O (e.g. virus protection softwares) slow things down, then how slow it is relative the software that filters for analysis.What are the solutions?BIRT Report Viewer plugins in EM is relatively heavy, so the plugin loading might be slow in case every file dynamically extracted is analyzed

Andrea DowningSMA Community Team

published in Enterprise Manager

Export an Enterprise Manager Profile

Enterprise Manager connection profileTo access OpCon for the first time from the Enterprise Manager interface, you'll need to create a connection profile to link your "EM" to the OpCon SQL Database.If you need to set up multiple workspaces, it can be easier to share a predefined profile to user. The profile information is stored in an profiles.xml file located under the Windows user and then .entrerpriseManager. For example : C:\Users\mbagard\.enterpriseManagerYou just need to share this profiles.xml file to another user and drop it to the same folder. When the user will start is EM, the profile will be available for connection.✏NoteThe profiles.xml does not contain any connection information about a specific user, it does only contain a SQL user and encrypted password to connect to the OpCon Database.

Andrea DowningSMA Community Team

published in Basic Support

External Event Password

External Event Passwords ( < 20.0.0 )Before the release of OpCon 20.0.0, the password for external events was automatically created at the same time as the user account and set to a default value of 20 stars (********************).This system wasn't flexible as it was impossible for an admin to disable a user external event password and it was also difficult for a user who had forgot his password to retrieve it. External Tokens ( > 20.0.0 )Since the version 20.0.0, External Event Passwords have been replaced by an "External Tokens" system offering more flexibility and more security.External Token values are now salted and hashed for storage in the database. The ability to use External Tokens may now be disabled. By default, this is disabled for all new users. External Tokens are now system-generated values. Pre-existing users will not have their existing token values updated, but if the value needs to be changed or for any new user this will no longer be a user provided value. Th

Andrea DowningSMA Community Team

published in Enterprise Manager

History Management Timeout

The Enterprise Manager contains Management tools to retrieve OpCon data about the History of the jobs or to Audit all the modification performed for a selected time period.What is the issue?You may encounter a "Query Exception" error while retrieving the requested information after waiting a moment. Most of the time, this is a timeout issue because you're trying to look on a huge period of time (e.g., a year).Below an example of the Query Exception error for the History Management:And an example for the Audit error:How to solve thisTwo ways to solve this issue: Reduce the time frame of your research. Instead of searching for information on a whole year for a job that ran a month ago, reduce to 2 months. The second option is to increase the Timeout of your profile, this is usually solving all the timeout issue. Click on the Enterprise Manager button on your top-left EM Preferences > Connection Profiles Select your profile and click "Edit" Increase the Timeout (sec) to 60 or

Andrea DowningSMA Community Team

published in Basic Support

How to Install MSLSAM On A Cluster

Clustering purpose?This article describes how to install the MSLSAM on a Microsoft Cluster, the purpose here is to set your agent in High Availability mode, so if one node crash or the service come down, another node will take the communication with the OpCon server, and your jobs will continue to run without any manual actions.RequirementsMSLSAM installation source Windows servers with Failover Cluster Manager feature Basic understanding of Windows Server clusteringHow to installProceed to a normal MSLSAM installation on both servers.Start the Failover Cluster Manager tool and import the MSLSAM services (Agent and JORS) to the Cluster with shared disk:You can add the JORS service or other resources by clicking on add Resource.You can add a Dependency, a dependency is a resource you have to bring online to have your Roles(Generic Service) online.Change the SMACommon.ini to the Shared disk to centralize logs:Start the service in Failover Cluster Manager:Connect to the EM and configure t

Andrea DowningSMA Community Team

published in Basic Support

How to Perform a Restart Point in a Symitar Job

What is the issue?If you're encountering issues with a Symitar job that has failed and needs to be restarted at a specific point, this article will guide you step by step to troubleshoot the problem.TroubleshootingDetermine the Episys jobfile you would like Opcon to begin processing. If the jobfile is part of a series of nested jobfiles, Opcon will run this jobfile and any subsequent jobfiles. Add the comment to the job inside of the main job.So if PAYROLL.POSTING is the point where you want to restart, then the RESTART will run that jobfile and all subsequent jobfiles in this sequence. Add the comment to the PAYROLL.POSTING job.Add the RESTART_POINT flag to the comments section of the Episys Jobfile: Add the corresponding flag to the Daily job in OpCon:Do not add the words RESTART_POINT b. If you are not using a sub type, add the comment to end of the start image: Restart the job in Opcon. Once the job is complete, remove the RESTART_POINT flag in Episys. ✏NoteIf you have any SEQ jo

Andrea DowningSMA Community Team

published in Basic Support

Integration Error After Upgrade of AIX on a Symitar Host

What is the issue?Jobs that run Episys PowerOn that transfer files are now failing after upgrading AIX to 7.1 TL5 SP9 or beyond on a Symitar host. The job in OpCon will fail with the following error message:Integration error: No such file or directoryHow to solve the issueLog into the AIX machine as root Navigate to the location of the SMA_DEFAULTS file. cd /SYM/SYM000/BATCH Once there cat the file to verify the contents of the SMA_DEFAULTS file cat SMA_DEFAULTS Example of what you may see: ;MAX_EXCEPTIONS = 99999999= ;ERROR_LEVEL 1-4,6,10-13= ;CREATE_OPCON_REPORTS_LINKS = false= ;JAVA_HOME "/usr/java7"= If you already have ;JAVA_HOME specified then update accordingly. If ;JAVA_HOME isn't there, you will need to add it. You will need to locate the most current version of Java by navigating to the /usr directory in AIX. Once there you'll likely see multiple versions of Java, locate the most current version then proceed. Use vi editor to add or modify the SMA_DEFAULTS fi

Andrea DowningSMA Community Team

published in Basic Support

Job Dependency and Auto Restart

What is the issue?One behavior you may encounter with OpCon is that a Job dependency is not resolved even if the previous job is "finished ok". In this particular case, the job targeted by the job dependency has a restart "when Job Finishes Ok"Just like in the example below:Looking at your Job History, you can see that the job is indeed Finished OK but the dependency is still not solved. Why?Let's take a complete example:Both jobs have a frequency with an automatic restart when the job is finished ok. The Second_Job has a dependency on the First_Job on Requires Finished Ok.What happens in this case is that once the First_Job is finished, it's submitted again for a restart and waits its new start time. The job is very briefly in a "Finished OK" state and quickly changes for Wait Start Time. The dependency doesn't have the time to get the information that the First_Job is Finished OK.What you can doThe solution is simple, you can just put the 2 jobs into a Sub_Schedule, remove the restar

Andrea DowningSMA Community Team

published in Basic Support

Locked Resource in OpCon That Cannot Be Freed

A resource is a user-defined value consisting of a name and a numeric limit. Resources are used to manage and limit the number of concurrently running jobs across schedules and machines in OpCon, they're flexible because they are platform independent and easy to manage.What is the issue?It can happens that a resource remains locked because a job dependency on a resource has been defined to use all resources available and then the job is not able to release the resource once completed.You can try to manually unlock the resource by following these steps: Restart the Job in question to "On-Hold" Mark the job finished ok, and that should release the lock. If the lock is not released, please create a support case. The support will look at the OpCon Database to remove the lock.Advice when using resourcesIt's better to use a defined value instead of "All" to avoid any lock issue:

Andrea DowningSMA Community Team

published in Basic Support

Arithmetic Overflow Occurred

When SAM attempts to process job starts and receives an arithmetic overflowThe following stack trace appears within the logs:11/25/2022 08:22:41.762 Error in ExecuteNonQuery. Error: 8115: System.Data.SqlClient.SqlException (0x80131904): Arithmetic overflow error converting IDENTITY to data type int.Arithmetic overflow occurred.at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskComp

Andrea DowningSMA Community Team

published in Basic Support

Troubleshooting OpCon Files Locked

What is the issue?You may encounter situation where OpCon or an LSAM is not working because a file such as a log or tracking file is locked or used by another process.For example in the picture below, the SAM.exe is not able to start because SAM.log is blocked by another process:The most common issues we're encountering are the following:"... File in Use. The action can’t be completed because the file is open in another program....." ".....The process XYZ cannot access the file abc.log because it is being used by another process....."Where to look The LSAM log if this is happening on a Machine (MSLSAM.log, SQLAgent.log, etc.) In the SMAServMan.log to identify the process affected (you'll see here which process is going down) OpCon Critical.log can provide information too Windows event viewer (application) can also display useful information How to solve it?To address the situation quickly and efficiently, it is important to find out what is locking the file (most of the time it i

Andrea DowningSMA Community Team

published in LSAM

UNIX LSAM Upgrade

How to Upgrade Unix LSAM?Learn how to keep your UNIX LSAM up to date by upgrading your existing instance.What you'll need for this: the latest release of the LSAM .tar file* the install_agent script an access to the UNIX machine your Enterprise Manager Please select the .tar file matching the version of your Operating System (RHEL, Ubuntu, Debian,...) Using the wrong .tar file may damage your instance!If you don't know which .tar to use, please review this article: UNIX LSAM choosing the right tar file to install.First stepMake sure that your LSAM is not currently running jobs, you can check the amount of running jobs in Operation > Machines StatusIf nothing is currently running on your machine, then you can stop the communication between OpCon and the LSAM: right-click on the machine > Stop CommunicationThe status of the machine is now "Not Responding".Second stepSend both install_agent script and your .tar file into an empty temporary folder on your UNIX machine.You may h

Andrea DowningSMA Community Team

published in IBM i

IBM i Maintenance

In this article, we'll see how to access the IBM i LSAM Parameters menu to configure the Maintenance.Access to the Parameters screenTo access the maintenance screen, from the LSAM main menu: Option 7 "LSAM Parameters", then page down to see the "LSAM Database Maintenance" section.Maintenance SettingsFrom this screen, you can configure the maintenance of your IBM i LSAM including when the daily maintenance task is started (Maintenance hour), the retention of the logs/backup in days, etc.You may encounter an issue where the maintenance task running by default at 04:00 AM is creating a conflict with one of your job or if for example you've two LSAM installed on your system starting the daily maintenance at the same hour. Another possible scenario is when you've two LSAM on your environment running the maintenance at different time but an IPL occurs during the maintenance period of both LSAM, when the IBM i LSAM will start, they'll start the maintenance at the same time creating a conflict

Andrea DowningSMA Community Team

published in IBM i

IBM i Job Messages

MessagesThe "Messages" function is designed to detect if a defined message is returned by your job. Then, following the message you can set up different actions like a reply or an OpCon event.How to use itLet's take an example to illustrate the usage of this feature. A simple job is created to perform a save of an object on the IBM i:The object has already been saved in QUSRTEMP/MBAGARD save file, so it will trigger a message saying that data are already present in the SAVF. We'll catch this message in our example.Message ID CPA4067 is returned as the SAVF is not empty. The job is stuck in a MSGW status and wait for an answer "C" for Cancel or "G" for Go.Message definition - OpCon sideLet's detect this in our job and send a "G" reply to the IBM i:In our example, we need to specify the Message ID : CPA4067, we also want to find "TESTKB" in the message. Position stay at 0 and is optional, no severity modification. For the Action, we'll just go with "Reply" and as a reply will send a Go t

Andrea DowningSMA Community Team

published in IBM i

IBM i Job Basic Troubleshooting

This article is designed to help you perform basic controls on your Enterprise Manager and IBM i LSAM to troubleshoot a job failed. It will give some tips about where you can find relevant information to help you understand why your job is failed.Initialization ErrorOne of the first issue you may encounter is an Initialization Error. It means that your job failed before it submission to the IBM i. As the job was never started on the IBM i, we can't retrieve a log from the LSAM.If you try to retrieve the log, you'll end with this message:No need to go further with the log if you've this message.To get information, you can right-click on your failed job > Job Information > Configuration tab > Operations Related Information. In the "Detailed Job Messages" field, you're likely to find details about the return code of your job.LSAM-side logsIt's possible to retrieve on the LSAM side precious information about what is submitted by OpCon.TXMMNG jobThe TXMMNG job performs the actual t

Andrea DowningSMA Community Team

published in LSAM

LSAM Not Communicating

What is the issue?When you install a new LSAM on a server, you need to create a new Machine in the Enterprise Manager to connect your new LSAM to OpCon.You'll find in this article some issues you may encounter with your new machine and some tricks to solve them.All the communication between OpCon and the agents (LSAMs) are handled by the process named SMANetCom. The SMANetCom.log is a good start to understand what's wrong with the communication.Most of the time, the log files are located here: C:\ProgramData\OpConxps\SAM\Log. But if your OpCon is installed on another disk, it will be something like D:\OpConxps\SAM\Log.Let's see 2 examples of the most common error messages in the SMANetCom.log : ConnectToMachine() -- Exception happens at machine [MSLSAM_Test]: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ConnectToMachine() -- Exception happens at ma

Andrea DowningSMA Community Team

published in Basic Support

Notifications Delayed

OpCon offers the possibility to create a wide range of notifications based on triggers (job, schedule and machine). Notifications allows you to send an email, to send a Windows event, to run a command, etc.However, as your environment grows you may notice that notifications are slower than before. We'll see in this article what the root cause and what you can do to improve the speed of the notification processing.Why this issue?You've probably defined a lot of notifications and your OpCon environment keep growing as you're adding more and more schedules and jobs into OpCon. At some point, you notice that your email notifications are delayed. You may also notice that the delay is even more important during the part of the day where there is an intense activity on OpCon (a lot of running schedules and jobs triggering notifications). The delay will reach a peak and then will decrease slowly.This delay is due to the congestion on the database table holding the notifications to send called

Andrea DowningSMA Community Team

published in Basic Support

OpCon Job History Management

OpCon stores information about the jobs that have run in its history. You have the ability to adjust the retention of the history at your convenience.Let's understand first where are stored the data.Job History DataOpCon job history data are stored in the OpCon Database in multiple tables:Data are stored in two different ways:Everything is in HISTORY and HISTORY_AUX tables Recent history is stored in HISTORY and HISTORY_AUX and the remaining data are archived in HISTARC and HISTARC_AUX✏Note "_AUX" tables are linked to the tables with the same prefixes, these tables contain accurate data such as command line or job parameters. In large environments, HISTORY tables are the largest in size and you may want to reduce the amount of data collected and stored or you may just want to refine your retention.Job History PurgeJob History Purge is a job provided by SMA in the SMAUtility schedule that manage OpCon job history. From this job, you can manage the behavior of the History program through

Andrea DowningSMA Community Team

published in Basic Support

Manage File Arrival Reaching End Time With Exit Code 1

When a File Arrival job reaches it end time and no file was found, its ends with an exit code 1 and a failed status.Sometimes, not finding a file is normal and you may want to manage this possibility and avoid your job ending as failed. However, exit code 1 is used not only for this special case but also for another reason that makes it a bit more difficult to just simply use the advanced failure criteria of your job.According to the documentation, the exit code 1 is not only returned for a file not found, more information below:"The file was not found. Reasons include an invalid filename, the file has not arrived yet, or permissions."This is also true for UNIX and IBM i file arrival jobs.How to manage this?Let's take an example, below my File Arrival definition:The job end time is 11:00 PM.The next step is to set an event to mark the job as Finished OK if the exit code is equal to 1 AND if the system time is superior to the end time of the job:The complex expression used:[[$JOB TERMIN

Andrea DowningSMA Community Team

published in Basic Support

OpCon Task Usage Utility FAQS

This article answers the most common questions regarding the OpCon Task Usage Utility. Detailed instructions and steps in configuring and setting up the Task Usage Utility job in OpCon can be found in this article.Frequently Asked Questions Why do I need to do this? With the SMA Technologies subscription agreement, your SMA Technologies Customer Success Team will be able to use this information to make sure that your automation needs are in line with your subscription plan. This automated solution removed any manual tasks in place to capture this information. Failure to have this true usage tracking may cause confusion and erroneous assumptions being made about your subscription model. This helps to have an informative discussion with your CSM. Is this required to provide SMA Technologies the TaskCount according to our current subscription plan? The purpose of sending us your statistics is to allow us to regularly monitor your automation needs and ensure that your subsc

Andrea DowningSMA Community Team

published in Basic Support

OpCon Task Usage Utility Installation and Configuration

Prerequisite This utility requires OpCon version 18.1 or above. Dockerbase.zip or Winbase.zip following your installation (.zip files are attached to this article). If you are on Windows Create a folder named "TaskCollection" at the same level as "SAM" installation folder within OpCon installation. Unzip the winbase.zip archive to that folder. E.g. locations - C:\Program Files\OpConxps\TaskCollection, or D:\MyAPplications\OpConxps\TaskCollection Create a folder named "TaskCollection" in the "ProgramData" folder for OpCon at the same level as "SAM". Copy the downloaded "Executables.json" file into that folder. E.g. location - C:\ProgramData\OpConxps\TaskCollection If you are on Docker Unzip the dockerbase.zip archive to a folder named "TaskCollection" on the host machine. From one level above this folder, use docker cp TaskCollection <container_name>:/app to copy the application to the container. Alternatively, you may map the above folder to the container when startin

1
2

Page 1 / 2

Badge winners

llvencillhas earned the badge SMA Employee
lucas-holderhas earned the badge SMA Employee
rlcarterhas earned the badge Founding Member
dcheleuittehas earned the badge Founding Member
jnortonhas earned the badge Founding Member

Show all badges

Powered by Gainsight

Terms & Conditions Cookie settings

Sign up

Already have an account? Login

Username *

E-mail address *

SMA products you use *

OpCon MAS Wripple VisualCron

Job Title *

Password *

I accept the terms & conditions

loginBox.register.email_repeat

Login to the community

No account yet? Create an account

Username or Email

Password

Remember me

Forgot password?

Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.

Enter your e-mail address

Back to overview

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

OK

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.

OK