CA Workload Automation AE

Release Notes
r11.3 SP1, Second Edition
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to
as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without
the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed
by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing
your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and
CA.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may
print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your
employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced
copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY
KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright © 2012 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
CA Technologies Product References
This document references the following CA Technologies products:
■ CA Embedded Entitlements Manager (CA EEM)
■ CA Workload Automation AE (formerly named CA AutoSys Workload Automation)
■ CA Workload Automation Agent for UNIX (CA WA Agent for UNIX)
■ CA Workload Automation Agent for Linux (CA WA Agent for Linux)
■ CA Workload Automation Agent for Windows (CA WA Agent for Windows)
■ CA Workload Automation SE (formerly named CA 7 Workload Automation)
■ CA Workload Control Center (CA WCC)

Contact CA Technologies
Contact CA Support

For your convenience, CA Technologies provides one site where you can access the
information you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following:
■ Online and telephone contact information for technical assistance and customer
services
■ Information about user communities and forums
■ Product and documentation downloads
■ CA Support policies and guidelines
■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you

can send a message to techpubs@ca.com.

If you would like to provide feedback about CA Technologies product documentation,

complete our short customer survey, which is available on the CA Support website at
http://ca.com/docs.
Contents
Chapter 1: Changes to Existing Features 9
Alarm Removed ............................................................................................................................................................ 9
Creating a Forecast Report for Multiple Days .............................................................................................................. 9

Chapter 2: Known Issues 11

Application Server Shuts Down .................................................................................................................................. 11
Application Server Not Starting Automatically (Windows only) ................................................................................ 11
CA Workload Automation AE Processes Fail to Start on Red Hat Linux Enterprise 6 (UNIX only) ............................. 12

Chapter 3: Fixed Issues 13

Agent Log Retrieval Failed .......................................................................................................................................... 15
Arguments Not Passed in Command Jobs .................................................................................................................. 15
autoping –s Failed ...................................................................................................................................................... 15
autorep Command Displayed Unnecessary Information ........................................................................................... 16
autorep Failed To Generate Global Blob Report ........................................................................................................ 16
autosys_secure Option 5 Not Displayed .................................................................................................................... 16
Blob or Glob Attribute Not Updated as Expected ...................................................................................................... 16
CA Workload Automation SE Jobs Held in READY State ............................................................................................. 17
CA EEM Servers List was Limited to 64 Characters .................................................................................................... 17
Changed Status Set to Blank ...................................................................................................................................... 17
chase Command Did Not Display the Status of All Jobs ............................................................................................. 17
Cross-Instance Communication Issue ........................................................................................................................ 17
Cross-Platform Manager Did Not Work as Expected ................................................................................................. 18
Datamover Issue......................................................................................................................................................... 18
Datamover Metadata Corrected ................................................................................................................................ 18
Documentation Typo Corrected ................................................................................................................................. 18
Error Messages in z/OS Job ........................................................................................................................................ 18
exclude_calendar Attribute Ignored .......................................................................................................................... 18
Exit Code Not Displayed on the Console .................................................................................................................... 19
Forecast Command Failed .......................................................................................................................................... 19
Forecast Command Displayed Duplicate Output ....................................................................................................... 19
Forecast Report Did Not Consider exclude_calendar ................................................................................................ 19
FQDN Names Not Obtained During a Reverse Lookup .............................................................................................. 19
Global Variable Name Not Enclosed in Braces ........................................................................................................... 19
Global Variable Names with a Period or a Space Not Properly Resolved .................................................................. 20
Incorrect Forecast Command for Box Job .................................................................................................................. 20

Contents 5
IP Address Cached ...................................................................................................................................................... 20
Issue with SNMP Traps ............................................................................................................................................... 20
Jobs Held in STARTING Status .................................................................................................................................... 20
Jobs Held in ACTIVATED, STARTING, or RUNNING State ............................................................................................ 20
Busy Jobs with Override on Virtual Machine Were Held in STARTING State ............................................................. 21
Jobs with Look-Back Condition Did Not Start Automatically...................................................................................... 21
Memory Leak Detected .............................................................................................................................................. 21
Primary Scheduler Did Not Respond .......................................................................................................................... 21
Redirection Operators Failed in std_out and std_err Attributes ............................................................................... 21
sap_step_parms Attribute Value Not Updated .......................................................................................................... 22
Scheduler Did Not Respond for Jobs with Long Global Variables .............................................................................. 22
Scheduler Log Did Not Respond ................................................................................................................................. 22
Scheduler Deadlock on DBMaint................................................................................................................................ 22
sendevent –E CHANGE_PRIORITY Command Did Not Work ...................................................................................... 23
sendevent Command Did Not Work As Expected ...................................................................................................... 23
Slow Data Migration ................................................................................................................................................... 23
ujo_sendevent Failed ................................................................................................................................................. 24
Update Job Condition ................................................................................................................................................. 25
Average Run Delay Column Displayed Negative Values (Oracle Application Server only) ......................................... 25
Datamover Failed to Validate Oracle Real Application Cluster (RAC) Database (Oracle only)................................... 25
ujo_sendevent with Time Failed (Oracle only) ........................................................................................................... 26
autosyslog –e Command Reported Error (Windows only) ......................................................................................... 26
Build Number Not Updated When Upgraded (Windows only) .................................................................................. 26
Default DCA URL Setting Blank (Windows only)......................................................................................................... 26
Default DCA URL Location Not Populated After the Upgrade (Windows only) ......................................................... 26
Excess EVENT_HDLR_ERROR Alarm (Windows only) ................................................................................................. 26
Incremental 2 Patch Installation Failed (Windows only) ............................................................................................ 27
Installation Failed (Windows only) ............................................................................................................................. 27
Instance Administration Window Disappeared (Windows only) ............................................................................... 27
Patch Not Applied To All Agents (Windows only) ...................................................................................................... 27
Agent Installation Failed (Solaris only) ....................................................................................................................... 27
Database Password Update in the Configuration File (UNIX only) ............................................................................ 27
SSA Installation Created Circular Links (UNIX only) .................................................................................................... 28
Installation Error (UNIX only) ..................................................................................................................................... 28
Timezone Information Not Determined (UNIX only) ................................................................................................. 28

Chapter 4: Documentation 29
Alarms ........................................................................................................................................................................ 30
autorep Command—Report Job, Machine, and Variable Information ...................................................................... 30
autotrack Command—Tracks Changes to the Database ............................................................................................ 30
STARTJOB (107) .......................................................................................................................................................... 30

6 Release Notes
std_err_file Attribute—Redirect the Standard Error File ........................................................................................... 31
Enable IP Address Caching on UNIX ........................................................................................................................... 31
Enable IP Address Caching ......................................................................................................................................... 33
sql_command Attribute—Specify an SQL Statement to Run ..................................................................................... 34
Specify the Scheduler or Application Server Log Rollover on UNIX ........................................................................... 34
Environment Variables ............................................................................................................................................... 34
forecast Command—Report Job Flow ....................................................................................................................... 35
Create a Forecast Report............................................................................................................................................ 38
Upgrade CA Workload Automation AE r11.3 to the Current Release on UNIX .......................................................... 39
Upgrade CA Workload Automation AE r11.3 to the Current Release on Windows ................................................... 42

Contents 7
Chapter 1: Changes to Existing Features
This section contains the following topics:
Alarm Removed (see page 9)
Creating a Forecast Report for Multiple Days (see page 9)

Alarm Removed
The APP_SERVER_COMM alarm is removed from CA Workload Automation AE.

Creating a Forecast Report for Multiple Days

In the current release, you can specify any time frame when creating a forecast report.
You can specify the time frame for a forecast report using the -F and -T attributes of the
forecast command. In the previous release, you could specify a time frame up to 24
hours. There are now no limits on the number of days you can specify; however, reports
with longer time frames consume more memory and time.

Chapter 1: Changes to Existing Features 9

Chapter 2: Known Issues
The chapter details the known issues in CA Workload Automation AE r11.3 SP1.

Note: For CA Workload Automation AE patch information, see http://support.ca.com.

Important! If you have already applied individual fixes for known issues and you
upgrade to CA Workload Automation AE r11.3 SP1, the upgrade will regress these
issues. These issues will be addressed in the upcoming cumulative or incremental patch.
For assistance, contact Technical Support at http://ca.com/support.

This section contains the following topics:

Application Server Shuts Down (see page 11)
Application Server Not Starting Automatically (Windows only) (see page 11)
CA Workload Automation AE Processes Fail to Start on Red Hat Linux Enterprise 6 (UNIX
only) (see page 12)

Application Server Shuts Down

The application server shuts down after CA Workload Automation AE installation.
However, the ustat command incorrectly shows that the application server is running.

Application Server Not Starting Automatically (Windows only)

Even though the service is set to start automatically, the application server is not
starting automatically after the product installation or server reboot. This happened
only if the Oracle database listener was not up when the application server started.

As a workaround, restart the application server after the Oracle database listener is
available and the normal operation is resumed.

Chapter 2: Known Issues 11

CA Workload Automation AE Processes Fail to Start on Red Hat Linux Enterprise 6 (UNIX only)

CA Workload Automation AE Processes Fail to Start on Red Hat

Linux Enterprise 6 (UNIX only)
CA Workload Automation AE processes exit with Signal SEGV error if the CA Workload
Automation AE user does not have read and execute permissions to the
$ORACLE_HOME directory. The CA Workload Automation AE processes exit without
displaying any error messages.

As a workaround, the CA Workload Automation AE user must be granted read and

execute permissions to the $ORACLE_HOME directory.

12 Release Notes
Chapter 3: Fixed Issues
The chapter details the issues that have been fixed in CA Workload Automation AE r11.3
SP1.

Chapter 3: Fixed Issues 13

CA Workload Automation AE Processes Fail to Start on Red Hat Linux Enterprise 6 (UNIX only)

This section contains the following topics:

Agent Log Retrieval Failed (see page 15)
Arguments Not Passed in Command Jobs (see page 15)
autoping –s Failed (see page 15)
autorep Command Displayed Unnecessary Information (see page 16)
autorep Failed To Generate Global Blob Report (see page 16)
autosys_secure Option 5 Not Displayed (see page 16)
Blob or Glob Attribute Not Updated as Expected (see page 16)
CA Workload Automation SE Jobs Held in READY State (see page 17)
CA EEM Servers List was Limited to 64 Characters (see page 17)
Changed Status Set to Blank (see page 17)
chase Command Did Not Display the Status of All Jobs (see page 17)
Cross-Instance Communication Issue (see page 17)
Cross-Platform Manager Did Not Work as Expected (see page 18)
Datamover Issue (see page 18)
Datamover Metadata Corrected (see page 18)
Documentation Typo Corrected (see page 18)
Error Messages in z/OS Job (see page 18)
exclude_calendar Attribute Ignored (see page 18)
Exit Code Not Displayed on the Console (see page 19)
Forecast Command Failed (see page 19)
Forecast Command Displayed Duplicate Output (see page 19)
Forecast Report Did Not Consider exclude_calendar (see page 19)
FQDN Names Not Obtained During a Reverse Lookup (see page 19)
Global Variable Name Not Enclosed in Braces (see page 19)
Global Variable Names with a Period or a Space Not Properly Resolved (see page 20)
Incorrect Forecast Command for Box Job (see page 20)
IP Address Cached (see page 20)
Issue with SNMP Traps (see page 20)
Jobs Held in STARTING Status (see page 20)
Jobs Held in ACTIVATED, STARTING, or RUNNING State (see page 20)
Busy Jobs with Override on Virtual Machine Were Held in STARTING State (see page 21)
Jobs with Look-Back Condition Did Not Start Automatically (see page 21)
Memory Leak Detected (see page 21)
Primary Scheduler Did Not Respond (see page 21)
Redirection Operators Failed in std_out and std_err Attributes (see page 21)
sap_step_parms Attribute Value Not Updated (see page 22)
Scheduler Did Not Respond for Jobs with Long Global Variables (see page 22)
Scheduler Log Did Not Respond (see page 22)
Scheduler Deadlock on DBMaint (see page 22)
sendevent –E CHANGE_PRIORITY Command Did Not Work (see page 23)
sendevent Command Did Not Work As Expected (see page 23)
Slow Data Migration (see page 23)
ujo_sendevent Failed (see page 24)
Update Job Condition (see page 25)
Average Run Delay Column Displayed Negative Values (Oracle Application Server only)
(see page 25)

14 Release Notes
 Agent Log Retrieval Failed

Datamover Failed to Validate Oracle Real Application Cluster (RAC) Database (Oracle
only) (see page 25)
ujo_sendevent with Time Failed (Oracle only) (see page 26)
autosyslog –e Command Reported Error (Windows only) (see page 26)
Build Number Not Updated When Upgraded (Windows only) (see page 26)
Default DCA URL Setting Blank (Windows only) (see page 26)
Default DCA URL Location Not Populated After the Upgrade (Windows only) (see page
26)
Excess EVENT_HDLR_ERROR Alarm (Windows only) (see page 26)
Incremental 2 Patch Installation Failed (Windows only) (see page 27)
Installation Failed (Windows only) (see page 27)
Instance Administration Window Disappeared (Windows only) (see page 27)
Patch Not Applied To All Agents (Windows only) (see page 27)
Agent Installation Failed (Solaris only) (see page 27)
Database Password Update in the Configuration File (UNIX only) (see page 27)
SSA Installation Created Circular Links (UNIX only) (see page 28)
Installation Error (UNIX only) (see page 28)
Timezone Information Not Determined (UNIX only) (see page 28)

Agent Log Retrieval Failed

If a job’s std_out_file or std_err_file contained a Windows UNC (Universal Naming
Convention) name, the CA Workload Automation AE server did not send the AFM to the
agent correctly. Therefore, those logs could not be viewed from the command line
(autosyslog), CA WCC, or the SDK application. For example, if a job named test_unc_log
had a standard output file named \\remote_nt\test_unc_out.log, the following error
messages were displayed when you tried to retrieve it using autosyslog -j test_unc_log
-t O:

CAUAJM_E_10682 Requested log file for the specified job could not be found.
CAUAJM_E_50138 *** No agent files found for job_name test_unc ***

Arguments Not Passed in Command Jobs

The job failed if command name and arguments were enclosed in quotes separately.
Now, you can use quotes for both the command name and arguments.

Note: If the command name has spaces, the quotes cannot be used for arguments. For
example, you cannot use command "C:\Program files\test.bat" “20” “In Progress”.

autoping –s Failed
The agent on the specified machine went down if you executed the autoping -s
command, for example, autoping -m machine_name -s.

Chapter 3: Fixed Issues 15

autorep Command Displayed Unnecessary Information

autorep Command Displayed Unnecessary Information

The autorep command displayed unnecessary information about an overridden
filewatcher job.

The following messages were displayed:

autorep -j fw -q -o 1
override_job: fw
/*CAUAJM_I_10350 Over-Ride #1 Set by User: root@aadrh53-ora on [12/23/2010
17:05:27]*/
/*CAUAJM_I_10352 Was RUN on run_num=1,487, Started on: 12/23/2010 17:05:41*/
watch_file_min_size: -9223372036854775808
watch_interval: 240

The minimum size is not displayed now, when watch_file_min_size attribute was not
overridden.

autorep Failed To Generate Global Blob Report

The autorep command failed to generate the global blob report when you used an
asterisk character with the –z option. Also, the files containing the blob data were not
stored in the directory specified using the -f option.

autosys_secure Option 5 Not Displayed

If you did not have execute rights for the CA EEM as-control SECADM default policy,
option 5 (manage users@host) of the autosys_secure command was not displayed.

Blob or Glob Attribute Not Updated as Expected

When the blob was uploaded to the database and the job was defined, the blob or glob
attribute was updated as expected. If the job was redefined (using update_job or
override_job commands) to update the blob or glob with a new value, the blob or glob
was taking the old value instead of picking the new value.

16 Release Notes
 CA Workload Automation SE Jobs Held in READY State

CA Workload Automation SE Jobs Held in READY State

When CA Workload Automation SE jobs were submitted to CA Workload Automation
AE, the jobs were held in READY state. This happened when the CA Workload
Automation AE scheduler was running and the cross-platform application was recycled.
The mainframe application sent a setup request which was ignored by the scheduler
because of a bug.

CA EEM Servers List was Limited to 64 Characters

When you enabled external security using the autosys_secure command, the CA EEM
servers list that you could specify was limited to 64 characters.

You can specify a comma-separated list of CA EEM servers if you configure multiple CA
EEM servers for the failover. The entire list of CA EEM servers can now be up to 255
characters.

Changed Status Set to Blank

When you ran a SQL stored procedure for SENDEVENT (ujo_sendevent) to send a
CHANGE_STATUS event to Success, it was setting the status to a blank instead.

chase Command Did Not Display the Status of All Jobs

The chase command stopped processing the job status after it received the following
status message:

CAUAJM_I_50175 An event for this job has come in during examination. Everything is
fine.

The chase command verifies the status of jobs based on the job object ID (joid) order.
Any job with a joid higher than that of the job that received the above status message
did not get processed by chase command, that is, did not display a status message.

Cross-Instance Communication Issue

The cross-instance communication from a CA Workload Automation AE r11.3 instance
to a Unicenter AutoSys JM 4.5 instance was not successful if you changed the database
password using the autosys_secure command. The autosys_secure command did not
update the encrypted password in the ujo_alamode table.

Chapter 3: Fixed Issues 17

Cross-Platform Manager Did Not Work as Expected

Cross-Platform Manager Did Not Work as Expected

When the CA Workload Automation AE secondary scheduler took over while a CA
Workload Automation AE job was in flight, the status of the in-flight job was not sent to
the cross-platform scheduling manager.

Datamover Issue
When you ran the datamover utility, the following error messages were displayed
intermittently:

RowCounter failed on table ujo_asbnode --java.sql.SQLException: ORA-00942:

table or view does not exist

RowCounter failed on table ujo_afm_strings --java.sql.SQLException:

ORA-00942: table or view does not exist

This happened because the RowCounter thread failed to shut down properly and ran
over the truncator thread space.

Datamover Metadata Corrected

The Metadata definitions of Datamover are corrected to reflect the current database
schema.

Documentation Typo Corrected

Remote Note is corrected to Remote Node in the application server log file.

Note: Every instance of this typo was corrected in the application server log file.

Error Messages in z/OS Job

The error messages of the zos_dsn_updated and zos_dsn_renamed attributes had the
values of 0, 1, or both. The error messages are updated to Y, N, or both.

exclude_calendar Attribute Ignored

The job schedule information based on the exclude_calendar attribute was displayed in
scheduler log even if the date_conditions attribute of that job was set to zero.

18 Release Notes
 Exit Code Not Displayed on the Console

Exit Code Not Displayed on the Console

The exit code was not displayed on the console while inserting all jobs that were
successful using the jil command.

Forecast Command Failed

The forecast command failed to report the following while the autorep command
reported them as running:
■ When you specified the end of the run window to fall in the next day in the
run_window attribute of the job definition, forecast failed to recognize this and did
not report the job.
■ When you defined a day-based box job with children that are dependent on each
other and are also day-based jobs, forecast did not report these dependencies.

Forecast Command Displayed Duplicate Output

If the parent box job had date-time condition and the child job had starting condition,
the forecast command displayed the output of the child job twice.

Forecast Report Did Not Consider exclude_calendar

The report generated by the forecast command did not consider the calendar specified
in the exclude_calendar attribute of the given job.

FQDN Names Not Obtained During a Reverse Lookup

When you perform a reverse lookup, the FQDN names were not obtained for machines
that failed.

Global Variable Name Not Enclosed in Braces

The global variable name specified in a job definition was not enclosed in braces.

As a workaround, manually enclose the global variable in braces, for example,

$${env.var}.

Chapter 3: Fixed Issues 19

Global Variable Names with a Period or a Space Not Properly Resolved

Global Variable Names with a Period or a Space Not Properly

Resolved
If the global variable name specified in a job definition contained a period or a space
character, the global variable name was not resolved properly.

To fix this problem, help ensure that you enclose the period or space in braces, for
example, $${env.var}.

Incorrect Forecast Command for Box Job

When you generated a forecast report of a child box job, the report was generated for
the child job without considering the parent job's schedule.

IP Address Cached
When CA Workload Automation AE failed over, the scheduler continued to run jobs on
the old IP address of the agent machine, even when the address of agent machine was
changed. This happened because of the cached IP address.

Issue with SNMP Traps

The machine name was not passed in the SNMP traps for the EP_SHUTDOWN and
EP_ROLLOVER alarms.

Jobs Held in STARTING Status

Jobs that were running on legacy adapters were held in the STARTING status
intermittently. This happened because the agent received the wrong job identifier, so it
could not send information back with the right job identifier.

Jobs Held in ACTIVATED, STARTING, or RUNNING State

Jobs were held in ACTIVATED, STARTING, or RUNNING status when a database fetch
failure occurred.

20 Release Notes
 Busy Jobs with Override on Virtual Machine Were Held in STARTING State

Busy Jobs with Override on Virtual Machine Were Held in

STARTING State
When you defined a new job on a virtual machine that included an agent that was busy
running jobs, the jobs with overrides were held in STARTING state. The scheduler
experienced a database arithmetic overflow error. The error messages were displayed in
the scheduler log.

Jobs with Look-Back Condition Did Not Start Automatically

A job was defined with a look-back condition did not start automatically even when the
job’s condition was met. This happened when the dependent job was updated or
recreated. Also, job_depends command displayed that the condition for the job did not
meet.

Memory Leak Detected

A memory leak was detected in the application server when access to delete a calendar
or a cycle was denied.

Primary Scheduler Did Not Respond

The primary scheduler stopped responding when an ORA-03126 (Oracle database) error
was encountered.

Redirection Operators Failed in std_out and std_err Attributes

When the oscomponent.noforceprofile, oscomponent.profiles.src.delay, and
oscomponent.profiles.global.override controlling options were enabled in the agent, the
job having the redirection operators in the std_out_file and std_err_file attributes
failed.

Chapter 3: Fixed Issues 21

sap_step_parms Attribute Value Not Updated

sap_step_parms Attribute Value Not Updated

When you updated an SAP job while autotrack was ON (autotrack level=1), the
sap_step_parms attribute value was not updated. The following error messages were
displayed:

CAUAJM_E_18416 Event Server: <autoprd> Failed Query: <BEGIN :RetVal :=

ujo_audit_msg_log (113, 74, 'variant', 'ZTEST_UNIX', 'N'); END;>
CAUAJM_E_18402 ORA-20870: Insert of ujo_audit_msg_log failed - -1 -ERROR-
ORA-00001: unique constraint (AEDBADMIN.XPKUJO_AUDIT_MSG) violated ORA-06512:
at "AEDBADMIN.UJO_AUDIT_MSG_LOG", line 27 ORA-06512: at line 1
CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
CAUAJM_E_18401 Function <doExecute> invoked from <execute> failed <761>
CAUAJM_E_10057 ERROR logging audit data//autotrack may have unpredictable results

Scheduler Did Not Respond for Jobs with Long Global Variables
The scheduler stopped responding when you started a job that used a global variable
with length greater than 64 characters, although the maximum length that can be
specified for a global variable is 100.

Scheduler Log Did Not Respond

When CA Workload Automation AE was running on a machine where OS was using
external authentication services like LDAP or VAS, the scheduler log stopped responding
immediately after the startup. The event processing was not affected.

Scheduler Deadlock on DBMaint

If you ran the DBMaint command to maintain the database while many jobs were
actively running, the scheduler stopped responding.

22 Release Notes
 sendevent –E CHANGE_PRIORITY Command Did Not Work

sendevent –E CHANGE_PRIORITY Command Did Not Work

The sendevent command failed when the queue priority for a job was changed to zero,
for example, sendevent –E CHANGE_PRIORITY –q 0 –J job_name.

The following error messages were displayed in the event_demon log file:

[09/23/2011 13:51:43] CAUAJM_I_40245 EVENT: CHANGE_PRIORITY

JOB: KG0-BU-LOG-01
[09/23/2011 13:51:43] CAUAJM_E_18802 Error from SQLExecute()
Failed with SQL_ERROR.
[09/23/2011 13:51:43] CAUAJM_E_18601 SQLSTATE: 42000, Native error: 102,
Message: [Microsoft][ODBC SQL Server Driver][SQL Server]
Incorrect syntax near '='.
[09/23/2011 13:51:43] CAUAJM_E_18601 SQLSTATE: 42000,
Native error: 8,180 , Message: [Microsoft][ODBC SQL Server Driver][SQL
Server]Statement(s) could not be prepared.
[09/23/2011 13:51:43] CAUAJM_E_18611 Event Server: <smicl02w2k3e:AEDB>
Failed Query: <UPDATE ujo_job_status SET run_priority=0 WHERE joid=105 and job_ver=>
[09/23/2011 13:51:43] CAUAJM_E_40225 Trouble processing Event [WAEz10000032]!
[09/23/2011 13:51:43] CAUAJM_I_40245 EVENT: ALARM ALARM:
EVENT_HDLR_ERROR JOB: KG0-BU-LOG-01
[09/23/2011 13:51:43] <event_hdlr error>

sendevent Command Did Not Work As Expected

When an alarm was sent for a job manually using the sendevent command, the job
object id (joid) for the job was not stored in the alarm table and was set to zero instead.

The alarm was not displayed in the detailed report for the job generated using the
following command:

autorep -J job_name -d

Slow Data Migration

Migrating data from CA Workload Automation AE 4.5.1 to CA Workload Automation AE
r11.3 was slow. In this release, the initial heap size and the maximum heap size are
increased to 512M and 1024M respectively, making the migration faster.

Chapter 3: Fixed Issues 23

ujo_sendevent Failed

ujo_sendevent Failed
A manual execution of the ujo_sendevent database procedure or function that failed for
the following database:

For Sybase and MS-SQL:

When you executed ujo_sendevent to generate a CHANGE_STATUS event, the following

error message was displayed:

Invalid STATUS

For Oracle:

When you executed ujo_sendevent with a date or time input to generate a

CHANGE_STATUS event, the following error message was displayed:

Invalid STATUS
aedbadmin.ujo_sendevent('CHANGE_STATUS','33713_hendry_test', 'INACTIVE','',
'01/12/2012 18:00','Reset for today');

Also, the ujo_sendevent generated the wrong event text. The following error message
was displayed:

ORA-06502: PL/SQL: numeric or value error: character to number conversion error.

24 Release Notes
 Update Job Condition

Update Job Condition

When a job in a box was updated after you specified a one-time override on the box job,
the following error messages were displayed:

CAUAJM_I_50323 Inserting/Updating job: test_job

CAUAJM_E_18416 SQL Query <BEGIN :RetVal := ujo_put_job
(0,63372,1,'','','',-1,0,
0,0,'test_box',0,0,'','Administrator@lodivm11vs1029',0,'','','',0,'','','',0
,0,0,0,0,0,0,0,'',0,'test_job','',0,99,'localhost',0,0,0,0,'','',0,102659911,'Adm
inistrator@lodivm11vs1029','',0,'','','',0,0,'','','','','',0,'','', :B_joid,
:B_job_ver, :B_over_num, :B_wf_joid); END;> failed
CAUAJM_E_18402 ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "AEDBADMIN.UJO_PUT_JOB", line 136
ORA-06512: at line 1
CAUAJM_I_18403 Processing OCI function ODEFIN(34)
CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
CAUAJM_E_18401 Function <doExecute> invoked from <nextRow> failed <860>
CAUAJM_E_19028 Trouble with database connection. Please manually delete the job
"test_job" and redefine it again.
CAUAJM_I_50205 Database Change WAS Successful!

The job is now updated when the RefreshAEDB script updates the database, the
tablespaces (for Oracle), and all the schema objects.

Average Run Delay Column Displayed Negative Values (Oracle

Application Server only)
In CA WCC, the Average Run Delay in Job Run report displayed negative values on an
Oracle application server.

Datamover Failed to Validate Oracle Real Application Cluster

(RAC) Database (Oracle only)
When you migrated data to an Oracle RAC database, the datamover utility failed to
validate the database. This happened because you cannot connect to the Oracle RAC
database using the JDBC thin client drivers.

As a workaround, you must run the datamover utility on individual nodes of the Oracle
RAC database.

Chapter 3: Fixed Issues 25

ujo_sendevent with Time Failed (Oracle only)

ujo_sendevent with Time Failed (Oracle only)

When you executed ujo_sendevent stored procedure manually with time as an input,
the procedure execution failed and displayed the following error:

ORA-06502: PL/SQL: numeric or value error: character to number conversion error.

autosyslog –e Command Reported Error (Windows only)

Even when the users with Administrators or Power Users group rights executed the
autosyslog -e command, the following error was displayed:

CAUAJM_E_50135 Only Administrators or Power Users can execute autosyslog

Build Number Not Updated When Upgraded (Windows only)

When you upgraded from CA Workload Automation AE r11.3 to CA Workload
Automation AE r11.3 SP1, the build number was not updated in the CA Workload
Automation AE Administrator GUI. The build number should be updated from 138 to
147.

Default DCA URL Setting Blank (Windows only)

The default URL location of DCA integration in the CA Workload Automation AE
Administrator was blank. The default URL location has been updated to
https://dcamgr:443/aip/sc; therefore, you need to change only your DCA host name
now.

Default DCA URL Location Not Populated After the Upgrade

(Windows only)
The default URL location https://dcamgr:443/aip/sc was not populated after the
upgrade to r11.3 SP1.

Excess EVENT_HDLR_ERROR Alarm (Windows only)

When the scheduler ran with heavy loads, it raised the EVENT_HDLR_ERROR alarm and
the jobs were not rescheduled. This happened because of the deadlocks in the
ujo_setup_next database table with ujo_batch_move_event and ujo_batch_get_event
stored procedures.

26 Release Notes
 Incremental 2 Patch Installation Failed (Windows only)

Incremental 2 Patch Installation Failed (Windows only)

An error was encountered while installing the incremental 2 patch in GUI mode on a
Windows server. The default paths were not populated.

Installation Failed (Windows only)

The CA Workload Automation AE installation that failed on Windows when it failed to
install SSA. The SSA installation that failed because the installer installed CAPKI 4.1.4,
while it requires CAPKI 4.1.6 or higher.

Instance Administration Window Disappeared (Windows only)

When you clicked either the Instance Wide Encryption or the zOS Encryption tab on the
Instance - CA Workload Automation AE Administrator window of CA Workload
Automation AE Administrator and pressed the Enter key, the tab disappeared.

Patch Not Applied To All Agents (Windows only)

When you upgraded from CA Workload Automation AE r11.3 to CA Workload
Automation AE r11.3 SP1, the patch was applied to only one agent per machine instead
of all agents.

Agent Installation Failed (Solaris only)

The agent Installation that failed on Solaris 8 and the following error message was
displayed:

!! Script executed with error: 1

Script or command "as_postinterview.sh" failed with exit code 1.

Database Password Update in the Configuration File (UNIX

only)
When you updated the database password using the autosys_secure command, the
password was updated on all lines that correspond to the DBAccess parameter in the
configuration file, irrespective of whether the lines were commented or not.

Chapter 3: Fixed Issues 27

SSA Installation Created Circular Links (UNIX only)

SSA Installation Created Circular Links (UNIX only)

The SSA installation created circular links. This issue was fixed with the SSA 2.1.44+
installer.

Installation Error (UNIX only)

If the time zone settings contained a space, for example, America/New York, the CA
Workload Automation AE installation log displayed the following error message:

/opt/CA/WorkloadAutomationAE/autouser.ACE/autosys.sh.rhel6x32: line 33: York:

command not found

The CA Workload Automation AE services failed to start automatically after the

installation.

Timezone Information Not Determined (UNIX only)

If the time zone settings contained a space, for example, America/New York, the
timezone information was not determined correctly because a shell script error
occurred.

28 Release Notes
Chapter 4: Documentation
This chapter includes documentation updates made as a direct result of the
functionality changes and fixed issues in this service pack.

Notes:
■ CA Workload Automation AE r11.3 SP1 includes the Release Notes only. This
chapter refers to and should be read in conjunction with the CA Workload
Automation AE r11.3 documentation set. For the CA Workload Automation AE r11.3
documentation set, visit http://support.ca.com.
■ The CA Workload Automation AE r11.3 SP1 Release Notes is included on the
product DVD and may be installed in your environment. However, we strongly
recommend that you go to http://support.ca.com for the latest version of the CA
Workload Automation AE r11.3 SP1 Release Notes to ensure that you are viewing
the most accurate and up-to-date information.
■ CA supports the subsequent operating systems for the duration of their lifecycle (as
determined by the operating system's manufacturer or until CA announces that we
are dropping support). The supported operating systems are subject to change. For
more information about compatibility and to see the latest operating systems
supported, visit http://ca.com/support.

This section contains the following topics:

Alarms (see page 30)
autorep Command—Report Job, Machine, and Variable Information (see page 30)
autotrack Command—Tracks Changes to the Database (see page 30)
STARTJOB (107) (see page 30)
std_err_file Attribute—Redirect the Standard Error File (see page 31)
Enable IP Address Caching on UNIX (see page 31)
Enable IP Address Caching (see page 33)
sql_command Attribute—Specify an SQL Statement to Run (see page 34)
Specify the Scheduler or Application Server Log Rollover on UNIX (see page 34)
Environment Variables (see page 34)
forecast Command—Report Job Flow (see page 35)
Create a Forecast Report (see page 38)
Upgrade CA Workload Automation AE r11.3 to the Current Release on UNIX (see page
39)
Upgrade CA Workload Automation AE r11.3 to the Current Release on Windows (see
page 42)

Chapter 4: Documentation 29
Alarms

Alarms
The APP_SERVER_COMM topic under the “Alarms” section in the “System States”
chapter of the Reference Guide is not applicable.

autorep Command—Report Job, Machine, and Variable

Information
The following note is added under the -w option in the “autorep Command—Report
Job, Machine, and Variable Information” topic in the “Commands” chapter of the
Reference Guide:

Note: To use this option, you must also specify the -q option.

autotrack Command—Tracks Changes to the Database

The following note is added under the –u level=2 option in the “autotrack
Command—Tracks Changes to the Database” topic in the “Commands” chapter of the
Reference Guide:

Note: The autotrack command writes the entire job definition for overrides and job
definition changes only when you use the level 2 option along with the -v option.

STARTJOB (107)
The following sentence is removed from the “STARTJOB (107)” topic in the “System
States” chapter of the Reference Guide:

You cannot send a STARTJOB event to a job that is in a box.

30 Release Notes
 std_err_file Attribute—Redirect the Standard Error File

std_err_file Attribute—Redirect the Standard Error File

You cannot set AUTOPID as an environment variable during job execution as it is no
longer supported.

Note: The AUTOPID environment variable is still valid for jobs that run on the legacy
agent.

The following example is updated in the “std_err_file Attribute—Redirect the Standard

Error File” topic in the “JIL Job Definitions” chapter of the Reference Guide:

Example: Create a Unique Identifier on Windows

This example redirects the job's standard error file to a file with a unique name.

insert_job: win_uniquename
job_type: CMD
machine: winagent
command: “C:\COMMON\Backup”
std_err_file: "C:\tmp\my_file.%environment_variable%"

Note: You can set environment variables and values for those variables at the system
level or in the job definition. The environment variable must specify a unique value
upon each job execution for the filename to be unique. For more information about
environment variables, see the User Guide.

Enable IP Address Caching on UNIX

The following procedure is added in the "Configuring CA Workload Automation
AE"chapter of the Administration Guide:

When the computer where the scheduler, agent, application server, or client utilities is
running is assigned a new IP address, it may adversely impact job processing because
the IP address of each component is cached by the other component.

Note: We recommend that you enable IP address caching (the default). However, in a
dynamic network environment, you may have to disable IP address caching so that the
IP address is resolved for every network request and this may impact performance.

Chapter 4: Documentation 31
Enable IP Address Caching on UNIX

To enable IP address caching on UNIX

1. Run the shell that is sourced to use CA Workload Automation AE.
2. Enter the following commands at the operating system prompt:
unisrvcntr status waae_sched.$AUTOSERV
unisrvcntr status waae_server.$AUTOSERV

The scheduler and application server process IDs are displayed as follows:
CA Services Status Report

Component Name Pid Status

------------------------------------ ------- --------------

WAAE Scheduler (ACE) 32220 running

CA Services Status Report

Component Name Pid Status

------------------------------------ ------- --------------

WAAE Application Server (ACE) 33330 running

3. Edit the following parameters in the configuration file, and save the file:
EnableIPCaching=0|1

0
Specifies that IP address caching is disabled.
1
Specifies that IP address caching is enabled. This is the default.
4. Enter the following commands at the operating system prompt:
kill –HUP scheduler_pid
kill –HUP applicationserver_pid

scheduler_pid
Defines the process ID of the scheduler that you want to pause and resume.
applicationserver_pid
Defines the process ID of the application server that you want to pause and
resume.
The scheduler and application server resume. The IP address caching is enabled.

Note: On Windows, you can enter the equivalent values using the Instance - CA
Workload Automation AE Administrator window of CA Workload Automation AE
Administrator. For information about configuring CA Workload Automation AE to enable
IP address caching on Windows, see the Online Help.

32 Release Notes
 Enable IP Address Caching

Enable IP Address Caching

The following procedure is added in the "Configuring a CA Workload Automation AE
Instance" chapter of the Online Help:

When the computer where the scheduler, agent, application server, or client utilities is
running is assigned a new IP address, it may adversely impact job processing because
the IP address of each component is cached by the other component.

Note: We recommend that you enable IP address caching (the default). However, in a
dynamic network environment, you may have to disable IP address caching so that the
IP address is resolved for every network request and this may impact performance.

To enable IP address caching

1. Click Start, Programs, CA, Workload Automation AE, Administrator.
The Instance - CA Workload Automation AE Administrator window opens.
2. Select the instance from the Instance drop-down list.
3. Click the Miscellaneous tab, select the Enable IP Caching check box, and click Apply.
The IP address caching is enabled.
Note: The Enable IP Caching check box is selected by default.
4. Click the Services icon on the toolbar.
The Services - CA Workload Automation AE Administrator window appears,
displaying a list of services installed on the selected instance.
5. Right-click the scheduler service, and click Pause.
The scheduler pauses.
6. Right-click the scheduler service, and click Resume.
The scheduler resumes.
7. Right-click the application server service, and click Pause.
The application server pauses.
8. Right-click the application server service, and click Resume.
The application server resumes. The IP address caching is enabled.

Chapter 4: Documentation 33
sql_command Attribute—Specify an SQL Statement to Run

sql_command Attribute—Specify an SQL Statement to Run

The following limits are updated in the "sql_command Attribute—Specify an SQL
Statement to Run" topic in the “JIL Job Definitions” chapter of the Reference Guide:
sql_statement
Specifies the SQL statement to run against a database table.
Limits: Up to 1000 characters; case-sensitive

Specify the Scheduler or Application Server Log Rollover on

UNIX
The following information is updated in the "Specify the Scheduler or Application Server
Log Rollover on UNIX" topic in the "Maintaining the Scheduler"chapter of the
Administration Guide:

You can specify when the scheduler or the application server log rolls over. The log can
roll over at midnight or when the log file size is equal to the specified size.

Environment Variables
The following information is updated in the "Environment Variables" topic in the
"Concepts" chapter of the Online Help:
LOGROLLOVER
Identifies when the scheduler or the application server log rolls over. The log can
roll over at midnight or when the log file size is equal to the specified size. The valid
values are OFF, SIZE(x), MIDNIGHT, and SIZE(x),MIDNIGHT.
Default: MIDNIGHT
Note: For more information about the LOGROLLOVER environment variable, see the
Administration Guide.

34 Release Notes
 forecast Command—Report Job Flow

forecast Command—Report Job Flow

The "forecast command—Report Job Flow" topic in the "Commands" chapter of the
Reference Guide is updated as follows:

The forecast command reports job flows based on a date or date range. Forecast
reports can help you predict the outcome for a set of predefined conditions. You can see
what happens when values are changed for each forecast period and use this
information to plan workflow. Based on the current job definitions, the reported job
flow displays a list of jobs predicted to run on the dates you specify.

The forecast report displays day-based jobs and event-based jobs expected to occur
during a specified time frame of any length. The memory the system uses to generate a
forecast report is directly correlated to the length of the time frame, the number of jobs
scheduled to run during that time frame, and the types of those jobs.

For example, a database containing 45,375 jobs (including 12,107 jobs with date-time
conditions) will have the following consumption (actual values may differ on your
system):
■ A one day (24 hours) forecast consumes 50 MB of memory and 80 percent CPU,
takes 14 seconds, and generates a 72,307 line report.
■ A one-week (168 hours) forecast consumes 130 MB of memory and 80 percent CPU,
takes 2 minutes and 22 seconds, and generates a 834,578 line report.

Syntax

This command has the following formats:

■ To report a job flow for a machine:
forecast –M machine_name -F "mm/dd/yyyy HH:MM" [-T "mm/dd/yyyy HH:MM"] [-s] [-h]
[-n] [-l]

■ To report a job flow for a specific job on a specific machine:

forecast –M machine_name -F "mm/dd/yyyy HH:MM" [-T "mm/dd/yyyy HH:MM"]
-J job_name [-s] [-h] [-n] [-l]

■ To report a job flow for a job :

forecast -J job_name -F "mm/dd/yyyy HH:MM" [-T "mm/dd/yyyy HH:MM"]

-J job_name
(Optional) Specifies the name of a job or a mask to report on. You can specify -J ALL
to report on all jobs.
Default: If you do not specify the -J option, the command reports on all jobs.
Note: You can use wildcard characters.

Chapter 4: Documentation 35
forecast Command—Report Job Flow

-m machine_name
Specifies the name of a machine to report on. You can specify –M ALL to generate a
report about all machines.
Note: This value cannot be masked.
-F "mm/dd/yyyy HH:MM"
Specifies the start date and time. The report displays workload that is expected to
occur starting from this specified date and time.
-T "mm/dd/yyyy HH:MM"
(Optional) Specifies the end date and time. The report displays workload that is
expected to occur up to this specified date and time.
Default: If you do not specify this value, the end date and time is set to 23:59 hours
following the start date and time.
-s
(Optional) Sorts the data by job names and start times.
-h
(Optional) Generates a report without header information.
-n
(Optional) Generates a report in narrow format.
-l
(Optional) Generates a report for successor jobs whose predecessors started a day
before the specified time range.
-?
(Optional) Displays the help for the forecast command.

Notes:
■ If the -l option is specified, the command considers all the jobs that start a day
before the specified time frame. Those jobs' successors are evaluated to identify
any jobs that occur within that time frame.
■ To determine which day-based jobs will occur in the specified time frame, the
forecast command considers the following job attributes:
– start_mins
– start_times
– run_window
– run_calendar

36 Release Notes
 forecast Command—Report Job Flow

– exclude_calendar
– days_of_week
To determine which event-based jobs will occur, the command then traces the
event-based jobs based on the box and child relationships, dependency
relationships and average run-time information of the predecessor job.
■ The forecast command interprets the logical operators specified in a condition (job
dependencies) as OR. For example, consider jobs A, B, and C. Suppose that jobs A
and B have start times of 10:00 and 11:00, and job C depends on the success of jobs
A and B. In an AND condition, the start time of job C in its first run would be
evaluated to whichever time occurs later (11:00 in this example). After both jobs A
and B run to SUCCESS, job C would start at both 10:00 and 11:00 in subsequent
runs. However, the forecast command interprets the condition as OR, so the
generated report shows the start time for job C as both 10:00 and 11:00 for all runs.
■ To project jobs during dependency traces, the forecast command uses the average
run time for the job. If no average run time information is available, the command
uses 1 minute.
■ The forecast command ignores global variables, job overrides, cross-instance
dependencies, DST changes, and the timezone attribute associated with a job. The
forecast report is based on the local time zone.

Example: Create a Forecast Report for Jobs Running on a Specific Machine

This example generates forecast report for all jobs on the testm machine. The report
forecasts when each job runs between 00:00 on January 16, 2012 and 23:59 on January
16, 2012.

forecast -m testm -F "01/16/2012"

Example: Create a Forecast Report for a Specific Job

This example generates a report that forecasts when test3 runs on the testm machine
between 00:00 on January 16, 2012 and 23:59 on January 16, 2012.

forecast -m testm –j test3 -F "01/16/2012"

Example: Create a Forecast Report for a Job for Multiple Days

This example generates report that forecasts when test2 runs between 00:00 on
January 1, 2012 and 23:59 on January 3, 2012.

forecast -F "01/01/2012" -T "01/03/2012" -J test2 -n

Chapter 4: Documentation 37
Create a Forecast Report

Create a Forecast Report

The "Create a Forecast Report" topic in the "Monitoring and Reporting Jobs" chapter of
the User Guide is updated as follows:

You can generate a report on future job flows based on a date or date range. Forecast
reports help you predict what occurs when a set of conditions are predefined. You can
see what happens when values change for each forecast period and use this information
to plan workflow. The reported job flow displays a list of future jobs based on the dates
you specify.

To create a forecast report

1. Do one of the following:
■ On UNIX, run the shell that is sourced to use CA Workload Automation AE.
The UNIX operating system prompt is displayed.
■ On Windows, click Start, Programs, CA, Workload Automation AE, Command
Prompt (instance_name).
The CA Workload Automation AE instance command prompt opens. The
command prompt presets all the environment variables for the instance.
2. Enter one of the following commands:
■ To report a job flow for a machine:
forecast –M machine_name -F "mm/dd/yyyy HH:MM" [-T "mm/dd/yyyy HH:MM"] [-s] [-h]
[-n] [-l]

■ To report a job flow for a specific job on a specific machine:

forecast –M machine_name -F "mm/dd/yyyy HH:MM" [-T "mm/dd/yyyy HH:MM"]
-J job_name [-s] [-h] [-n] [-l]

■ To report a job flow for a job :

forecast -J job_name -F "mm/dd/yyyy HH:MM" [-T "mm/dd/yyyy HH:MM"]

Notes:
■ If you omit the -J job_name option, the command reports on all jobs.
■ For more information about the forecast command, see the Reference Guide.

38 Release Notes
 Upgrade CA Workload Automation AE r11.3 to the Current Release on UNIX

Example: Create a Forecast Report for a Job

This example generates a forecast report that displays when testproc is expected to run
between 10:30 a.m. and 10:30 p.m. on December 1, 2010.

forecast –J testproc -F "12/01/2010 10:30" -T "12/01/2010 22:30"

Example: View the Duration and End Time of a Job

This example generates a forecast report for the test_4 job. The report displays when
test_4 will run between 11:40 p.m. on December 15, 2009 and 11:41 p.m. on December
15, 2009

forecast -F "12/15/2009 23:40" -n

The report output resembles the following:

CA Workload Automation AE Forecast Report
Generated on 12/13/2009 11:03AM
Forecast Date:12/14/2009

Box Name Job Name Machine Name Start Time Duration End
Time
_____________ _____________________ _______________________ ____________________ __________ _____
______________
--- test_4 localhost 12/15/2009 23:40 1 12/
15/2009 23:41

Upgrade CA Workload Automation AE r11.3 to the Current

Release on UNIX
Notes:
■ You can use the provided installation media to install CA Workload Automation AE
r11.3 SP1. For more information about installing CA Workload Automation AE r11.3
SP1, see the CA Workload Automation AE r11.3 UNIX Implementation Guide.
■ You can upgrade Unicenter AutoSys JM 4.5 or r11 (including service packs) to the
current release. For more information about upgrading Unicenter AutoSys JM 4.5 or
r11 (including service packs) to the current release, see the CA Workload
Automation AE r11.3 UNIX Implementation Guide.
■ Before you upgrade CA Workload Automation AE r11.3 to the current release, we
recommend that you take a backup of the current CA Workload Automation AE file
system.

Chapter 4: Documentation 39
Upgrade CA Workload Automation AE r11.3 to the Current Release on UNIX

Important! After you upgrade CA Workload Automation AE r11.3 to r11.3 SP1, you must
run the RefreshAEDB.pl Perl script to refresh, update, or add read-only data in the CA
Workload Automation AE database for each server installation. You do not need to run
the RefreshAEDB.pl script for a client-only, agent-only, or SDK-only installation. For
more information about refreshing the CA Workload Automation AE database using the
RefreshAEDB.pl Perl script, see the CA Workload Automation AE r11.3 UNIX
Implementation Guide.

This procedure describes the steps to upgrade CA Workload Automation AE r11.3 to the
current release.

To upgrade CA Workload Automation AE r11.3 to the current release on UNIX

1. Log in as root and enter the following command:
unisrvcntr stop CA-WAAE

The scheduler, agent, and the application server stop.

2. Insert the installation media into the drive and mount it.
3. Change directories to the mounted file system and run the installation program
using the following command:
./wa_setup.sh

The Maintenance Wizard Welcome page appears.

4. Select Update/Reinstall and click Next.
The Active Components page appears if a CA Workload Automation AE component
or a dependent CA Common Service is active. Otherwise, the Review Setting page
appears listing the components that will be updated. In that case, proceed to Step
6.
5. Click Next.
The active processes shut down. The Review Settings page appears, listing the
components that will be updated.
Note: Before you can update the installation or reinstall a component, all
dependent CA products must be shut down
6. Review the information and, if it is correct, click Next.
The Monitor Progress page appears and the progress is displayed. When the
upgrade completes, the Update Complete page appears.

40 Release Notes
 Upgrade CA Workload Automation AE r11.3 to the Current Release on UNIX

7. Click Finish.
The current release of CA Workload Automation AE is installed.
8. (server installation only) Enter the following commands:
cd $AUTOSYS/dbobj/DB
perl ./RefreshAEDB.pl

DB
Specifies the type of database in use: ORA (Oracle) or SYB (Sybase).
9. (server installation only) Enter the required information for each of the prompts
and enter Y when prompted to run the script.
The CA Workload Automation AE database is updated.
10. Enter the following command:
unisrvcntr start CA-WAAE

The scheduler, agent, and the application server start. CA Workload Automation AE
r11.3 is upgraded to r11.3 SP1.

Notes:
■ The setup program creates a log file in the /opt/CA/installer/log directory named
CAWorkloadAutomationAE.reinstall.YYYYMMDDHHMMSS.log. This file contains a
summary of the components you updated or reinstalled. Refer to this file if you
encounter problems during the upgrade.
YYYYMMDDHHMMSS
Indicates the year, month, day, hour, minute, and second when the upgrade
happened.
■ To verify the upgrade status:
– Execute the autoflags -x command. An output similar to the following is
displayed:
11.3.SP1.147

– (server installation only) Execute the following SQL query. The output displays
11.3.1.
select str_val from ujo_alamode where type='AEDB_VERSION'

Chapter 4: Documentation 41
Upgrade CA Workload Automation AE r11.3 to the Current Release on Windows

Upgrade CA Workload Automation AE r11.3 to the Current

Release on Windows
Notes:
■ You can use the provided installation media to install CA Workload Automation AE
r11.3 SP1. For more information about installing CA Workload Automation AE r11.3
SP1, see the CA Workload Automation AE r11.3 Windows Implementation Guide.
■ You can upgrade Unicenter AutoSys JM 4.5 or r11 (including service packs) to the
current release. For more information about upgrading Unicenter AutoSys JM 4.5 or
r11 (including service packs) to the current release, see the CA Workload
Automation AE r11.3 Windows Implementation Guide.
■ Before you upgrade CA Workload Automation AE r11.3 to the current release, we
recommend that you take a backup of the current CA Workload Automation AE file
system.

Important! After you upgrade CA Workload Automation AE r11.3 to r11.3 SP1, you must
run the RefreshAEDB.pl Perl script to refresh, update, or add read-only data in the CA
Workload Automation AE database for each server installation. You do not need to run
the RefreshAEDB.pl script for a client-only, agent-only, or SDK-only installation. For
more information about refreshing the CA Workload Automation AE database using the
RefreshAEDB.pl Perl script, see the CA Workload Automation AE r11.3 Windows
Implementation Guide.

This procedure describes the steps to upgrade CA Workload Automation AE r11.3 to the
current release.

To upgrade CA Workload Automation AE r11.3 to the current release on Windows

1. Log in as a user with Windows Administrators group privileges.
2. Stop the scheduler, agent, and the application server services from the Windows
Service Control Manager.
3. Insert the installation media into the drive and mount it.
Note: If autorun is enabled, the installation starts automatically.
4. Run the installation program using the following command:
setup.exe

The CA Workload Automation AE r11.3 Product Explorer appears.

5. Select CA Workload Automation AE and click Install.
The Welcome page appears.
6. Select Repair and click Next.
The Review Settings page appears, listing the components that will be updated.

42 Release Notes
 Upgrade CA Workload Automation AE r11.3 to the Current Release on Windows

7. Review the information and, if it is correct, click Next.

The Setup Status page appears and the progress is displayed. When the upgrade
completes, the Installation Complete page appears.
8. Click Finish.
The current release of CA Workload Automation AE is installed.
9. (server installation only) Enter the following commands:
cd %AUTOSYS%\dbobj\DB
perl RefreshAEDB.pl

DB
Specifies the type of database in use: MSQ (Microsoft SQL Server), ORA
(Oracle), or SYB (Sybase).
10. (server installation only) Enter the required information for each of the prompts
and enter Y when prompted to run the script.
The CA Workload Automation AE database is updated.
11. Start the scheduler, agent, and the application server services from the Windows
Service Control Manager.
CA Workload Automation AE r11.3 is upgraded to r11.3 SP1.

Notes:
■ The setup program creates a log file in the %TEMP% directory named
WAAE_Install.log. This file contains a summary of the components you updated or
reinstalled. Refer to this file if you encounter problems during the upgrade.
■ To verify the upgrade status:
– Execute the autoflags -x command. An output similar to the following is
displayed:
11.3.SP1.147

– (server installation only) Execute the following SQL query. The output displays
11.3.1.
select str_val from ujo_alamode where type='AEDB_VERSION'

Chapter 4: Documentation 43