AutoSys commands hang and fail on new client machine
Article ID: 205429
Updated On:
Products
Issue/Introduction
When attempting to execute various AutoSys commands that would connect with the application server (sendevent, autorep, jil, etc) the command hangs and times out.
The behavior does not impact functionality of the agent as jobs are running without issue.
Environment
Release : 11.3.6
Component : CA Workload Automation AE (AutoSys)
Resolution
AutoSys commands hang due to instance-wide encryption mismatch.
UseEncryption= parameter on the client machine must match what is defined in the AutoSys config file.
#+----------
#
# Keyword: UseEncryption=<0|1|2>
#
# Defines the instance-specific encryption key for all communication
# between the AutoSys Workload Automation components of the same
# instance. This key must be the same on all computers where the server
# and clients are installed for a particular AutoSys Workload Automation
# instance.
#
# The valid values are as follows:
#
# 0 = Specifies that no encryption is used.
#
# 1 = Specifies that the default encryption key is used to
# encrypt data. This key is created during the AutoSys
# Workload Automation installation.
#
# 2 = Specifies that a user-specified encryption key is used to
# encrypt data.
#
# Note: If you set the UseEncryption parameter to 2, you must
# specify the encryption key using the as_config command.
#
############## User Comments - Start. Keyword: UseEncryption #################
#
#
############## User Comments - End. Keyword: UseEncryption #################
UseEncryption=0
Validate and update the config (config.xxx, where xxx is your three character instance name) file on the client as needed and recycle agent.
Retry your commands.
Feedback
