View changes, fixed and known issfixedues, supported platforms, and system requirements.
- If you are new to the Workload Automation System Agent, see Getting Started.
- For installation, upgrade, and software requirements, see Installing and Upgrading and Workload Automation System Agent Platform Support Matrix.
This Release Notes article explains the key features for each release of CA Workload Automation System Agent Version 11.5.
The following sections describe the new features that are included in each 11.5 release of the agent.
Ability to restrict the use of a cryptkey.txt to a particular machine
Option now when creating a cyrptkey.txt file to restrict that file to only be valid on the machine where it was created.
Added the ability to specify the owner and group accounts for installed files
Agent installation now allows for owner and group accounts to be specified. This affects all installed files.
Restrict the access to the cryptkey.txt file to just owner and group on UNIX platforms
Generated cryptkey.txt files on UNIX platforms now have their permissions set so that only the owner and group of the file can access it.
New agentparm.txt File Parameter Deals with the limiting the maximum size of a log message
A new parameter, log.maxmsglen has been added to the agentparm.txt file to specify the maximum length that an individual log message may be before having the message truncated.
The default is to perform no truncation.
Installation supports pre-existing Java Runtimes on all Agent platforms
On platforms where the agent install provided its own bundled Java runtime, there is now an option to install the bundled Java runtime (AdoptOpenJRE8 for Windows/Linux) or specify an alternate Java runtime.
On platforms where no bundled Java runtime is provided, the install continues to require a Java runtime to be specified.
File scanning algorithm has been modified to improved performance
A new file monitoring algorithm has been implemented to improve performance. The previous algorithm’s performance would degrade significantly under some conditions.
The default is to now use the new algorithm. A new parameter, filemon.use_pooled_dispatcher, has been added to allow disabling of the new algorithm.
New agentparm.txt File Parameter dealing with the JVM settings on external file transfers
A new parameter, ftp.external.jvm.x.options, has been added to allow the specification of JVM options when a file transfer job is specified to run externally.
The default is to pass no additional JVM settings.
Agent Installer with AE-mode now defaults the Number of Managers option to 0
To better match the typical scenario of an Autosys(AE) user installing an agent, the default for the “Number of Manager” to specify during install has been changed to 0 instead of 1.
Non AE-mode installations will continue to default to 1.
Added support for AES-CTR encryption
Support for AES-CTR encryption has now been added to the agent. It can be specified during installation or as a new cipher value when executing the keygen program.
Certified Agent support for new Operating System versions
Certified the Agent functionality on three new OS releases:
- Windows 2019
- SUSE Linux 15
- RedHat Linux 8
Updated bundled JRE and 3rd party library versions
Updated to newer versions of the Java runtimes (JREs) and 3rd party libraries that the agent bundles/installs with itself. These updates are to make sure the agent is using components that are actively supported by their vendors and are up to date to reduce the security vulnerabilities.
CPU monitoring on Multiple CPU machines without manually setting scalefactor
Agent checks for the number of CPUs on the machine dynamically whenever it calculates the machine CPU utilization and will report the CPU usage based off the load average by default. The workload automation engines no longer require manual configuration of the objmon.cpu.scalefactor setting for accurate CPU information. If objmon.cpu.scalefactor is specified in agentparm.txt, then this scale factor will take precedence.
New agentparm.txt File Parameter Allows Agent to Decrypt Passwords Generated in Other Encoding Standards
A new parameter, oscomponent.password.encoding, has been added to the agentparm.txt file to allow the System Agent to process passwords encoded in a standard other than UTF-8.
By default, the System Agent assumes that the characters used in passwords are encoded as UTF-8. In situations where a different encoding standard is used, such as ISO-8859-1, used by some CA schedulers, you can use this parameter to specify that the System Agent decrypt the password into characters that match the original encoding.
New communication.agenttoken_n File Parameter Used as an Alternate Agent Identifier
A new parameter, communication.agenttoken_n, has been added to the agentparm.txt file. It is an alternate agent identifier used in cases where the agent might be behind a load balancer. Typically. this value is automatically managed by the agent and the manager.
Default: not present
Profile Files Now Accessible By Job User
On Windows, when the following are true, the System agent will now perform the profile file validation after switching to the job user. This ensures that profile file validation and reading take places with the correct user:
- The job is configured to run as a different user.
- The agent is running as yet another user, possibly the SYSTEM user.
- The job user has the required permissions to access the profile file, but the Agent user does not.
Similarly, if the Agent user (for ex: SYSTEM) has permission to the profile file and not the user that is configured to run the job, then the job will fail since the user configured to run the job does have access to the profile file.
The following sections include the known issues for each 11.5 release of the agent.
SYSAGT-347: Windows Agent Installation onto the Non-primary Drive (C:) Fails
Installation of the Windows agent onto the non-primary drive (C:) will fail. The non-primary drive can be either a second installed/partitioned drive or a mounted drive (net use).
When choosing an agent installation folder on a Windows machine, if the folder chosen was not on the primary drive then the install would fail.
The agent will be partially installed, there will be an empty 'wla_jre' folder and a missing 'jre' folder/symbolic link.
The install makes use of both the TMP and TEMP environment variables. These typically default to primary drive but could vary by user.
The default drive letter for the install is determined based on these two environment variables. The agent will only be able to be installed on the drive referenced by these environment variables.
So, to install an agent on a non-primary drive, the install needs to be done where the following environment variables have been modified to use the desired drive letter where the agent will be installed.
For example, to install the agent onto the D: drive, open a command prompt or create a .bat file that does the following:
set TMP=D:\temp set TEMP=D:\temp setup.exe
SYSAGT-345: After Starting the Agent, It Consumes an Excessive Amount of CPU on the Machine
After starting agent, the agent consumes an excessive amount of CPU on the machine. The CPU usage by the agent will approach the maximum amount allowed by the operating system for that process the entire time the agent is running. Also, the runner_spool_cleaner.log file will be full of messages containing:
Jobs will fail to run properly due to the lack of a specified spooldir in the agentparm.txt file.
The agent will not be able to effectively process jobs due to the lack of a defined spooldir in the agentparm.txt file. .
Additionally, other processes on the machine may be slowed due to the excessive amount of CPU being used by the agent process. .
Workaround:Modify the agentparm.txt file to correctly define the 'spooldir' parameter and restart the agent. This will prevent the high CPU usage and also allow jobs to execute appropriately.
SYSAGT 342: Restarting a Windows agent can result in LOST CONTROL of jobs that were running without having had a user specified
On a Windows Agent, a restart of the agent can result in LOST CONTROL of jobs that were running without having had a user specified.
RUN jobs unexpectedly return a status of LOST CONTROL after an agent restart on Windows. Inspection of the agent machine shows the job process is still executing, however.
Jobs must be restarted or manually verified and a forced complete execute within the scheduler.
Workaround:The job may be executed with a user defined.
Nonstop System Agent Fails Submit STATE COMPLETE Messages to the Manager Even Though Jobs Complete Successfully
Due to known timezone issues with the OSS and Guardian, runtime libraries no STATE COMPLETE messages are sent back to the Scheduling Manager hours before the Spring DST (Daylight Savings Time) transition takes place. There are no known issues during the Fall DST (Daylight Savings Time) transition.
Workaround:Edit the agent's startup script located in the root/base installation folder. The default full name of the startup script is /opt/CA/WA_Agent/cybAgent. Add a line like the following:
The value of <tz-value> can be any of the following, depending on your timezone:
You must stop and restart the agent for this change to take effect.
Installer Indicates Success when Installation Fails Due to Invalid JVM Version
On the iSeries, NonStop, z/Linux , PPC, and PPCLE platforms, the installer returns an exit code of 0, indicating a successful installation, even though the installation fails due to an invalid JVM version.
A version of Java 1.8 or higher is required for installation. If a version lower than 1.8 is used, the installation fails with the following error: The installer cannot run with the given JVM. Java 1.8+ is required. However, the output reflects an exit code of 0. See the following example output from an iSeries v5 installation:
$ /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/bin/java -jar setup.jar =============================================================================== CA WA Agent 11.4.00.00 (created with InstallAnywhere) ------------------------------------------------------------------------------- The installer cannot run with the given JVM. Java 1.8+ is required. $ echo $? 0
Some Agent Files Remain After Uninstallation
(UNIX and Linux platform only) When you run the uninstaller to uninstall an agent, the following message is generated:
Uninstall Complete ------------------ Some items could not be removed.
In some cases, such as with a new installation of an agent that has never been started, the message displays even though the agent and agent directory are removed. In other cases, such as with an agent that has been run or is running jobs, some files and directories remain in the agent directory, such as /log, nohup.stderr, and nohup.stdout.
This message is generated by the installation application and currently has no fix. If you see this message, and your agent installation is not completely removed, manually remove the remaining files.
Workload Automation AE Command Jobs That Start with Double Parentheses Might Fail
Jobs that contain a command that begins with two parentheses, for example, “((“ can fail. This issue occurs with 11.3 SP4 Incremental 2 of the Workload Automation agent running Workload Automation AE jobs. When the parentheses are used to group commands and are not part of the executable or batch file name, the job fails. These same jobs run successfully with versions of the agent prior to 11.3 SP4 Incremental 2.
When the job fails, the job log contains a line at the end similar to the following:
Command to be executed: "C:\Windows\system32\cmd.exe" /c "("("
To retrieve the job log, use the command "autosyslog -j jobname -tA")
To work around this issue, change the syntax of the command to begin with "cmd.exe /c" followed by the original command.
Text File Monitor Jobs Do Not Support ISO-2022 File Encodings
Text file monitor jobs do not support files encoded with encodings in the ISO-2022 family, such as ISO-2022-CN, ISO-2022-JP, and ISO-2022-KR.
The Agent Can Report Back That It Is Running on Windows 2012 When the Agent Is Installed on a Windows 2016 Server
Under certain scenarios, the agent reports back that it is running on Windows 2012, when in fact the agent is installed on a Windows 2016 server. This is a known bug in the version of Java shipped with the agent, AdoptOpenJDK8. This has been fixed in the new release of AdoptOpenJDK11 which will be shipped with the agent at a later date.
System Agent on AIX is not sending 'Status' information When a Job Is Killed by a User
The System agent on AIX is not sending 'Status' information when a job is killed by a user.
The following issues have been resolved:
11.5.00 P4 for WA Agent Linux
SYSAGT-344 Autoping -S Fails if Autosys Encryption Is Disabled
Autoping with -S fails with "Program can, only be run from within the agent" error if Autosys encryption is disabled.
SYSAGT-346 iSeries Completion Code Incorrect
When a *SEVERITY error is returned, the response would not include the completion code.
SYSAGT-349 iSeries FTP Download Large Files
FTP download jobs to native filesystem will fail if the file exceeds 13000 records in size.
SYSAGT-351 High Vulnerability in Jackson
High security vulnerabilities were detected in the jackson library provided in the initial release.
SYSAGT-352 Abort Signal 6
On systems using PowerBroker software run jobs will first report success followed by abort signal 6.
SYSAGT-353 Shell Specified for a Script May Not Be Used
When running command jobs in UNIX the shell directive (first line in shell script) is not honored by the agent. Unable to handle Perl scripts correctly.
SYSAGT-316 Shell specified for a script may not be used
A RUN job where a specific shell was specified to run a script with, may not have been used during the job execution. This could have occurred if either of the following agent parameters had been configured within the agent:
SYSAGT-323 File Watcher jobs do not go to running state on Unix
File watcher jobs may not have gone to RUNNING state, even though they were successfully monitoring and detecting file creation. Only occurred on Unix/Linux when the full path of the file(s) being watched were greater than 114 characters in length.
SYSAGT-324 Environment Variable Names on Windows Converted to Uppercase
(Windows only) For Workload Automation System Agent releases between 11.3.06 and 11.4.01, variable names in environment variables that were sent to the agent were converted to uppercase.
Even though Windows is case-insensitive, problems could occur when other programs or scripts expect the variable name in environment variables to be lowercase or mixed case.
SYSAGT-325 FTP upload jobs can create an empty target file
FTP upload jobs could create an empty upload file if the source file being uploaded did not exist.
SYSAGT-326 Some ISeries jobs did not change a READY or INPUT state correctly
The agent did not correctly report the STATE EXEC status of a job once the job status within the OS became INPUT or ACTIVE HLD.
SYSAGT-327 The ‘chkusr’ utility program would fail to execute properly on 64bit HP-UX Itanium agents
On agents installed onto a 64bit HP-UX Itanium machine, running the chkusr program would result in an error: "Unable to load pam library: Unable to find library libpam.sl"
SYSAGT-328 iSeries File Triggers That Use ASP Not Activated
iSeries file triggers that used an ASP (Auxiliary Storage Pool) were not correctly activated when a new native iSeries file arrived. These iSeries triggers did not correctly look for native files, which appeared to be directories to the Java code.
For example, the following file name would not have worked correctly: path /QAS/QSYS.LIB/PAGVEN_MEX.LIB/BA*
SYSAGT-329 iSeries with ASP: FTP Incorrectly Identifies Native Files
When using ASP (Auxiliary Storage Pool), native files were not correctly identified during FTP transfer and were received with no end of line markers. So a file that is transferred from iSeries to UNIX appears as a single long record instead of individual lines.
Native iSeries files that were sent to non-iSeries boxes cannot be processed.
SYSAGT-330 KILLJOB commands could return success incorrectly
In situations where the program for a RUN job traps the signals used by the agent to terminate a job when the user requested the job to be killed, the job may have been reported as killed incorrectly.
SYSAGT-331 Command jobs may have failed the profile file validation
In cases where the job user had permission to access a profile file, but the System Agent user did not, the job would have been failed by the Agent profile file checks.
SYSAGT-332 Agent could crash on UNIX due to concurrent KILLJOB commands
The agent process could crash with a SIGSEGV if multiple KILLJOB commands were received concurrently.
SYSAGT-333 Agent could crash on Windows due to a FILE TRIGGER request where the user had no domain specified
If a FILE TRIGGER job contained a user specified without a domain, the agent running on a Windows machine would crash. A cold-start of the agent was required to allow the agent to restart again.
SYSAGT-334 Agent uninstall on the i5 platform would not uninstall the LIBRARY
Performing an uninstall of an agent on the i5 platform would not remove or delete the associated LIBRARY for the agent.
SYSAGT-335 A Windows Agent would not allow the ‘Euro’ character
A Windows agent would not accept job requests where a ‘Euro’ character was specified in a command, argument and/or a filename.
SYSAGT-336 STATE COMPLETE status could be sent before STATE EXEC status
On multi-CPU unix machines, when the CPU loads are heavy, it is possible for the agent to send the STATE COMPLETE to the scheduler, prior to sending the STATE EXEC.
SYSAGT-337 Agent process can hang processing job cancels
When a RUN job is being cancelled, it is possible for the Agent to hang if the job(s) being cancelled were executed with a specific User specified.
SYSAGT–338 Agent Process Consumes Excess Memory
The System Agent would consume an excess amount of memory after having been receiving scans from unexpected sources such as a vulnerability scanning tool.
SYSAGT-339 ESP users were not able to retrieve spool files correctly
ESP users were not able to retrieve spool files correctly that contained binary or UTF-8 data.
SYSAGT-340 Agent status shown as AGENT DOWN after retrieving spoolfile in AE
AE (Autosys) schedulers would incorrectly report an agent status as DOWN after retrieving a spoolfile that contained binary data.