CA Technologies Unicenter AutoSys JM r11 SP5 Readme ______________________________________________________________________ 1.0 Welcome 2.0 Unicenter AutoSys JM r11 SP5 Build Number 3.0 Known Issues 3.1 sendevent -F Does Not Process Double Quotes Correctly 3.2 Status Not Sent to Cross-platform Manager (Sybase and Microsoft SQL Server only) 3.3 Scheduler and Application Server Display Invalid TZ or TZ="" 3.4 Mainframe Dependencies Not Deleted 3.5 Data Migration Fails (UNIX only) 3.6 Database Creation Fails if the Database Server Resides on a Windows Computer (UNIX only) 3.7 Unicenter AutoSys JM Upgrade Fails (Windows only) 4.0 Fixed Issues from Previous Releases 5.0 Fixed Issues in Unicenter AutoSys JM r11 SP5 5.1 Primary Scheduler Stopped Responding 5.2 QuickView and Enterprise Command Line Displayed 'Login Failed' Message 5.3 ntgetdate Binary Was Not Available in Windows Agent Installation (Windows only) 5.4 as_info Did Not Display Expected Output (UNIX only) 5.5 Broker Memory Leaked 5.6 Cross Instance Dependency Error 5.7 Final "Exit Code = N" Not Displayed in JIL 5.8 Creation of stdout/stderr Failed (Windows only) 5.9 Agent Logs Did Not Display Error Message 5.10 File Watcher Did Not Work as Expected When Using * (UNIX only) 5.11 One-Time Override For Command Affected Condition Attribute (UNIX only) 5.12 Application Server Started Without Time Zone Set (UNIX only) 5.13 AutoInstWideAppend=1 Did Not Work As Expected (Server Fix) 5.14 AutoInstWideAppend=1 Did Not Work As Expected (Agent Fix) (UNIX only) 5.15 Internationalized Chase Messages 5.16 Scheduler Quit Processing Jobs 5.17 sendevent -F Option Failed 5.18 Application Server Reported UTF8 Errors 5.19 DBMaint Did Not Purge All Data From ujo_job_runs (Windows only) 5.20 Legacy Agents Reported EVENT_HDLR_ERRORS 5.21 Database Monitoring Tool Did Not Show Unicenter AutoSys JM FAT Client Programs 5.22 Cross-Platform Status Was Sent Only to One Node 5.23 Root User Cannot Start Scheduler Using Vintella/VAS 5.24 Uninstall Did Not Remove SSA (Windows only) 5.25 Agent Log Maintenance 5.26 Bookshelf Link Did Not Work (Windows only) 5.27 Installation Failed With Valid glibc Version (UNIX only) 5.28 as_owner Deny Policy Did Not Work When User Is Owner 5.29 Wrong OID in the MIB file (UNIX only) 5.30 Group and Application Fields Cannot be Modified 5.31 Installation Failed If /etc/profile Returned Non-Zero Exit Code(UNIX only) 5.32 Load Balance Usage Returned Zero (Windows only) 5.33 Shadow Scheduler Did Not Fail Over When Primary Scheduler Failed 5.34 Legacy Agents Failed To Process Events 5.35 Box Jobs Were Stuck in Running State 5.36 autosys_secure Option 7 5.37 Upgrading Multiple Instances 5.38 Lockout Issue After Installing Unicenter AutoSys JM 5.39 CA Common Components Installation Failed 5.40 Service Pack Post Upgrade Task Message 5.41 AS_EEM_AUTHUSER_MODE=TRUSTALL Authentication Mode 5.42 archive_events Documentation Update 5.43 autobcp Failed on Windows with Oracle 11g r2 5.44 getaddrinfo Retries Before Cancel 5.45 MDB Patches Missed 5.46 Status Not Sent to Cross-platform Manager (Oracle only) 5.47 Incorrect ujo_get_batch Event Stored Procedure (Microsoft SQL Server only) 5.48 Jobs in a Box Ran Twice 6.0 Published Fixes 7.0 Unicenter WCC Command Sponsor Installer Available on the Unicenter AutoSys JM r11 SP5 DVD 8.0 Contact CA ______________________________________________________________________ 1.0 Welcome Welcome to Unicenter(R) AutoSys(R) Job Management (Unicenter AutoSys JM) Release 11 SP5. This file contains the following information: * Known issues * Fixed issues * Published fixes * CA Technical Support contact information Unicenter AutoSys JM r11 SP5 includes installation DVDs for the following: * Unicenter AutoSys JM r11 SP5 for UNIX/Linux * Unicenter AutoSys JM r11 SP5 for Windows * CA Common Components r11.3 Note: For more information about the CA Common Components DVD, see the documentation provided on that DVD. * Unicenter WCC r11.1 SP3 Notes: * For the latest version of this Readme, visit http://support.ca.com. You can check this website for current information about supported operating systems, database releases, processors, and other third-party products. * For information about product installation considerations, operating system support, system requirements, new features, and changes to existing features, see the . * For information about how to upgrade Unicenter AutoSys JM to the current release, see the or the . We recommend that you also read the Upgrade Considerations and Post-Upgrade Tasks sections for additional information about the upgrade process. * In this Readme, the term refers to any Microsoft Windows operating system supported by Unicenter AutoSys JM. ______________________________________________________________________ 2.0 Unicenter AutoSys JM r11 SP5 Build Number The build number for Unicenter AutoSys JM r11 SP5 is 90. You can verify the build number by issuing the autoflags -i command. You can verify the database version by running the following query: select str_val from ujo_alamode where type='DB_VERSION' Your installation or upgrade is successful if the autoflag -i command returns 90 and the query output is SP5. ______________________________________________________________________ 3.0 Known Issues This section describes known issues, workarounds, and solutions for this release. Notes: * We recommend that you also read the Installation Considerations section in the for additional information about the installation process. * For Unicenter AutoSys JM patch information, see http://support.ca.com. Important! If you have already applied individual fixes for known issues and you upgrade to Unicenter AutoSys JM r11 SP5, the upgrade will regress these issues. These issues will be addressed in the upcoming cumulative or incremental patch. 3.1 sendevent -F Does Not Process Double Quotes Correctly The following command does not process double quotes correctly from the input file: sendevent -F This problem occurs when the sendevent commands are processed from a file. 3.2 Status Not Sent to Cross-platform Manager (Sybase and Microsoft SQL Server only) If a job is terminated, the status is not sent to the cross-platform manager in the following scenarios: * When you set up job scheduling managers for high availability, if the cross-platform manager rolls over when the Unicenter Autosys JM job is being executed, the termination status is not sent to the rolled over server as expected. * When a job terminates and is in TERMINATED status, the status is sent to the cross-platform manager, but it is not stored in the database. If the CCI sent to cross-platform manager fails, the status is not sent at the time of the next setup between the scheduling manager and Unicenter AutoSys JM. 3.3 Scheduler and Application Server Display Invalid TZ or TZ="" When you start the Scheduler or the Application Server with an invalid value or blank ("") for time zone, the scheduling is not affected because the Scheduler and the Application Server use the GMT time zone for scheduling. As a workaround, set the correct time zone before starting the Scheduler or the Application Server. 3.4 Mainframe Dependencies Not Deleted If you define Unicenter AutoSys JM jobs with a dependency on cross-platform jobs, the dependency is not deleted although you delete the cross-platform dependency from the Unicenter AutoSys JM jobs. 3.5 Data Migration Fails (UNIX only) When you upgrade from Unicenter AutoSys JM 4.5 or 4.5.1 to r11(including its service packs), the Target Database Machine Name field on the Data Migration Information page for the target database is disabled. The local host name is displayed in the Target Database Machine Name field by default. So, the database migration fails but the upgrade is successful. As a workaround, perform the data migration manually after the upgrade. 3.6 Database Creation Fails if the Database Server Resides on a Windows Computer (UNIX only) The Unicenter AutoSys JM installation fails to create the database if the database server resides on a Windows computer, and the data file path contains special characters like \n, \t, and so on, for example, C:\newdata or C:\tabdata. This problem occurs due to the UNIX/Linux shell interpretation of strings containing special characters. To resolve this issue, do one of the following: * Do not use special characters in the data file path. * Specify the data file path as c://newdata, c://tabdata, and so on. 3.7 Unicenter AutoSys JM Upgrade Fails (Windows only) When you upgrade Unicenter AutoSys JM r11 SP1, r11 SP2, r11 SP3, or r11 SP4 to r11 SP5 from a mounted ISO drive, the upgrade fails. If you copy the installer from the mounted ISO drive to the local hard disk and perform the upgrade, the upgrade is successful. However, if you cannot copy the mounted ISO drive to the local hard disk, you must follow these steps: 1. Open regedit and browse for the following registry key: HKLM\Software\Classes\Installer\Products\42A6D8D065720874F8BEB5C435113216\SourceList\Media 2. Add the MediaPackage string and set its value to AutoSys. 3. Upgrade Unicenter AutoSys JM r11 SP1 or r11 SP2 to r11 SP5. Note: For more information about this solution, refer to the Microsoft Knowledge Base article 299803. ______________________________________________________________________ 4.0 Fixed Issues from Previous Releases Unicenter AutoSys JM r11 SP5 includes all fixed issues from the following releases: * Unicenter AutoSys JM r11 * Unicenter AutoSys JM r11 SP1 * Unicenter AutoSys JM r11 SP1 Incremental 1 * Unicenter AutoSys JM r11 SP2 * Unicenter AutoSys JM r11 SP2 Incremental 1 * Unicenter AutoSys JM r11 SP2 Incremental 2 * Unicenter AutoSys JM r11 SP3 * Unicenter AutoSys JM r11 SP3 Incremental 1 * Unicenter AutoSys JM r11 SP4 * Unicenter AutoSys JM r11 SP4 Incremental 1 * Unicenter AutoSys JM r11 SP4 Incremental 2 For more information about the fixed issues in r11, r11 SP1, r11 SP2, r11 SP3, and r11 SP4 download the appropriate Readme from the Documentation section on CA Support (http://support.ca.com). For more information about the fixed issues in an incremental, download the appropriate Readme from the Download Center, Published Solutions section on CA Support (http://support.ca.com). ______________________________________________________________________ 5.0 Fixed Issues in Unicenter AutoSys JM r11 SP5 The following issues are fixed in Unicenter AutoSys JM r11 SP5: 5.1 Primary Scheduler Stopped Responding The Primary Scheduler stopped responding when the path for the gcc library was not included in LD_LIBRARY_PATH in Linux. 5.2 QuickView and Enterprise Command Line Displayed 'Login Failed' Message When searching for a job in the Unicenter WCC QuickView application or executing a Unicenter AutoSys JM command in the Unicenter WCC Enterprise Command Line (ECLI) application, the message, 'Login failed' was displayed. 5.3 ntgetdate Binary Was Not Available in Windows Agent Installation (Windows only) If you installed only the Unicenter Universal Job Management Agent on Windows, the ntgetdate binary did not install. This resulted in the failure of jobs in the test mode. 5.4 as_info Did Not Display Expected Output (UNIX only) The following as_info options did not display the expected result: as_info -? man as_info as_info -a as_info -x as_info -v 5.5 Broker Memory Leaked Memory leak was detected when box jobs were scheduled to the Job Management Option agent. 5.6 Cross Instance Dependency Error When a job had a condition field that included a cross instance dependency, and that field was updated, a new EXTERNAL_DEPENDENCY event was requested. This caused a unique constraint violation for the other instance and displayed the following errors in the event_demon log: CAUAJM_E_18402 ORA-00001: unique constraint(MDBADMIN.BASEIDX_UJO_REQ_JOB) violated CAUAJM_I_18403 Processing OCI function OEXEC, OEXN(3) CAUAJM_E_18400 An error has occurred while interfacing with ORACLE. CAUAJM_E_18401 Function invoked from failed <616> 5.7 Final "Exit Code = N" Not Displayed in JIL JIL did not display the message, "Exit Code = 0" when an insert, update, or delete operation was successful. The message, "Exit Code = n" was displayed only when an insert, update, or delete operation failed. 5.8 Creation of stdout/stderr Failed (Windows only) When stderr and stdout logs were created on Windows, if the stderr attribute had variable strings to expand and the expanded string length was the same as the original string, the job failed with an internal exit code of 123. 5.9 Agent Logs Did Not Display Error Message When a child agent process did not write to the tx or request folder, no relevant error message was included in the agent log file. The result of non-access was that the Scheduler timed out every time, and the job failed after restarting the number of times specified for max_restart. The absence of an error message in the agent log made it difficult to diagnose the cause of the problem. 5.10 File Watcher Did Not Work as Expected When Using * (UNIX only) When watching for the regular expression * on UNIX, Unicenter AutoSys JM matches any file that fits the expression. If it found a file that was deleted, it waited for the same file to arrive, and ignored any other file that satisfied the regular expression. 5.11 One-Time Override For Command Affected Condition Attribute (UNIX only) Suppose you have a box job on UNIX, with five command jobs in it, and each command job is dependent on the success of the command job before it. If you performed a one-time override for every command job to change only the command, it impacted the condition attribute also. Then, when you started the box job, all the command jobs ran at the same time, ignoring the job dependency condition. 5.12 Application Server Started Without Time Zone Set (UNIX only) The Application Server started even if time zone was not set. The server worked correctly until jobs with the time-zone attribute were run and then issues were encountered. 5.13 AutoInstWideAppend=1 Did Not Work As Expected (Server Fix) If the AutoInstWideAppend parameter value was set to 1 (the default), stderr and stdout logs were overwritten instead of being appended as they should have been. To append the stderr and stdout files, set the AutoInstWideAppend parameter value to 2. This issue was introduced in the Unicenter AutoSys JM r11 SP3 INC1 UNIX agent and fixed in the Unicenter AutoSys JM r11 SP5 UNIX agent. Note: For information about setting the AutoInstWideAppend parameter on UNIX or Windows, see the . 5.14 AutoInstWideAppend=1 Did Not Work As Expected (Agent Fix) (UNIX only) If the AutoInstWideAppend parameter value was set to 1 (the default), stderr and stdout logs were overwritten instead of being appended as they should have been. This issue was introduced in the Unicenter AutoSys JM r11 SP3 INC1 UNIX agent. 5.15 Internationalized Chase Messages The chase command displayed Unicenter AutoSys JM messages without message numbers. 5.16 Scheduler Quit Processing Jobs The Scheduler stopped processing events and displayed only timestamps. The Scheduler had to be restarted to continue processing. 5.17 sendevent -F Option Failed The following Unicenter AutoSys JM command failed: sendevent -F The following error message was displayed: CAUAJM_E_60388 One or more sendevent commands have invalid parameters specified 5.18 Application Server Reported UTF8 Errors When Unicenter AutoSys JM was used with CA EEM, the following problems were occasionally observed: * The Application Server log was filled up with the message "INVALID DATA in UTF8 string". This overloaded the disk space on the server and Unicenter AutoSys JM shut down. * UTF8 data format exceptions appeared in the CA EEM server log. This was due to cache corruption in the CA EEM SDK. 5.19 DBMaint Did Not Purge All Data From ujo_job_runs (Windows only) Unicenter AutoSys JM client archive_events archived ujo_job_runs events to file, but did not delete them from the database table ujo_job_runs. 5.20 Legacy Agents Reported EVENT_HDLR_ERRORS Jobs running on legacy agents sometimes got the following errors: CAUAJM_E_10194 Could not get row for joid=0 db_get_ jobNover will ret fail. CAUAJM_E_40044 Could not get row for joid [0]. CAUAJM_E_40225 Trouble processing Event [PRD004r2ou02]! 5.21 Database Monitoring Tool Did Not Show Unicenter AutoSys JM FAT Client Programs Database monitoring tool did not show Unicenter AutoSys JM FAT client programs when connected to database. 5.22 Cross-Platform Status Was Sent Only to One Node When multiple cross-platform managers requested status for a Unicenter AutoSys JM job, only one of the nodes received the job status. 5.23 Root User Cannot Start Scheduler Using Vintella/VAS The Scheduler did not start when run from /etc/rc startup scripts. The following error messages were displayed in the logs: CAUAJM_E_50006 Internal API error. CAUAJM_E_10004 Error retrieving current user and machine. 5.24 Uninstall Did Not Remove SSA (Windows only) The silent installation iss files could not be created after SSA was upgraded to version 2.1.43. If Unicenter AutoSys JM was uninstalled using the Windows Add/Remove Programs dialog, the following error message was displayed: Cannot un-install SocketAdapter This message appeared for both, Windows 2003 and Windows 2008 servers. 5.25 Agent Log Maintenance A large number of agent logs are stored in the agent log directory. To maintain disk space availability, you can set the AGENT_LOG_MAINTENANCE environment variable to delete the agent log files. By default, the agent deletes the agent log files that are older than 3 days. Note: For more information about setting the AGENT_LOG_MAINTENANCE environment variable on UNIX or Windows, see the . 5.26 Bookshelf Link Did Not Work (Windows only) When you accessed the Unicenter AutoSys JM bookshelf using Start, All Programs, Unicenter, AutoSys Job Management, Guides, Unicenter AutoSys Job Management Bookshelf, the link did not work and the bookshelf could not be accessed. 5.27 Installation Failed With Valid glibc Version (UNIX only) Unicenter Autosys JM failed to recognize glibc version glibc-2.12-1.2.el6.i686 although it is greater than the version that it requires, which is glibc-2.3.2-95.3. Note: The values are compared based on the following format: glibc-release.major_a-major_b.minor_a-minor_b; rest of the values are not compared. 5.28 as_owner Deny Policy Did Not Work When User Is Owner If the job owner was the same as the user sending the request, security check was not made for the owner attribute. For example, if you created a deny policy in the as-owner resource class for a user "testuser". When the testuser tried to insert a job without explicitly specifying the owner, the job was created successfully. However, the job creation should fail. 5.29 Wrong OID in the MIB file (UNIX only) The Unicenter AutoSys JM MIB file included an older object identifier (OID) 858. The SNMP traps generated by Unicenter AutoSys JM displayed 858. The OID in the Unicenter AutoSys JM MIB file is now updated to 791. 5.30 Group and Application Fields Cannot be Modified Group and application fields could not be modified using external validation. 5.31 Installation Failed If /etc/profile Returned Non-Zero Exit Code(UNIX only) The installation failed if a non-zero exit code value is returned when the /etc/profile file is sourced. You can now customize the Unicenter AutoSys JM installation to ignore the /etc/profile return code by setting the AS_PROFILECHECK_SKIP operating system environment variable. For information about setting the AS_PROFILECHECK_SKIP environment variable to ignore the /etc/profile return code, see the UNIX Implementation Guide. Note: This is not a recommended solution. We recommend that you fix the errors in the /etc/profile file before you install Unicenter AutoSys JM so that a zero exit code is returned when the /etc/profile file is sourced. 5.32 Load Balance Usage Returned Zero (Windows only) When a load balancing method was used to check the machine usage on Microsoft Windows 2003 or Microsoft Windows 2008 computers, the usage returned was zero. 5.33 Shadow Scheduler Did Not Fail Over When Primary Scheduler Failed In the high availability (HA) mode, the Primary Scheduler stopped responding when there is no disk space. The Shadow Scheduler did not takeover processing events when the Primary Scheduler stopped responding. 5.34 Legacy Agents Failed To Process Events The Scheduler marked the legacy agent as missing if it failed to respond. The Scheduler did not mark the legacy agent as online even after the legacy agent was restarted. So, jobs scheduled on the legacy agent were stuck in PENDING state. 5.35 Box Jobs Were Stuck in Running State Box jobs were stuck in RUNNING state although all jobs in the box completed successfully. The box jobs were stuck in RUNNING state because of the following Sybase errors: CAUAJM_E_18015 Client message: Message number: layer (1), Origin (1), text (ct_res_info(NUMDATA): user api layer: external error: This routine cannot be called after ct_results() returns a result type of CS_CMD_SUCCEED.), SEVERITY = (1), NUMBER = (41) 5.36 autosys_secure Option 7 A new option "[7] Authenticate AutoSys Security Utility with EEM." is added to the autosys_secure command. This option is available only if the Unicenter AutoSys JM instance is configured with CA EEM. Note: For more information about how to authenticate a user with CA EEM using option 7 of the autosys_secure command, see the . 5.37 Upgrading Multiple Instances If multiple instances of Unicenter AutoSys JM were installed on a computer and external security is enabled, only the first installed instance was upgraded successfully. 5.38 Lockout Issue After Installing Unicenter AutoSys JM You may encounter a situation where all Unicenter AutoSys JM users are locked out if you install Unicenter AutoSys JM on a computer where the autosys user account exists as a non-local account in an external user repository instead of being defined to the computer. To prevent this problem, we recommend one of the following steps: 1. Install Unicenter AutoSys JM r11 SP5 on computers where the autosys user account is defined locally. 2. Before upgrading to Unicenter AutoSys JM r11 SP5, run autosys_secure as a EDIT/EXEC superuser to add the user "autosys". After the upgrade, run autosys_secure to add "autosys@host.networkdomain" as a EDIT/EXEC superuser and optionally remove "autosys" as a EDIT/EXEC superuser. After you upgrade to Unicenter AutoSys JM r11 SP5, if you are locked out of autosys_secure, do of the following: * Create a local account for "autosys" if you have the rights to add users to the computer. Logging in to the computer with the local "autosys" account should let you run autosys_secure as a super EDIT/EXEC user, which allows you to add "autosys@host.networkdomain" as an EDIT/EXEC superuser. You can delete the local "autosys" account after completing this step. * Recreate the database by running the createnewdb Perl script located in the %AUTOSYS%/dbobj (on Windows) or $AUTOSYS/dbobj (on UNIX) directory or by running the Unicenter AutoSys JM r11 SP5 installation. 5.39 CA Common Components Installation Failed The CA Common Components installation failed on SUSE Linux Enterprise Server 11 with the following error message: ./ccc_setup.sh Preparing the setup environment. Please wait... Installation of CA Common Components has detected the following and cannot continue. An undetermined error has occurred attempting to validate your system. Return code= 19 The Installation of CA Common Components is terminating. !! Script executed with error: 1 SMX000007 Script or command "ccs_prestart.sh" failed with exit code 1. Reason: The script or command encountered a problem. Action: Review the installation log file for more details. 5.40 Service Pack Post Upgrade Task Message When you upgraded to a new service pack, the post-upgrade task was not displayed. 5.41 AS_EEM_AUTHUSER_MODE=TRUSTALL Authentication Mode A new value "TRUSTALL" is introduced for the AS_EEM_AUTHUSER_MODE environment variable. If you set the AS_EEM_AUTHUSER_MODE environment variable to TRUSTALL, it causes the security subsystem to represent all users (local or non-local) that are not authenticated with CA EEM as CA EEM policy identities represented in the form of . Note: For more information about the AS_EEM_AUTHUSER_MODE environment variable, see the . 5.42 archive_events Documentation Update The Unicenter AutoSys Job Management Reference Guide was updated with ujo_event2 database table archive. 5.43 autobcp Failed on Windows with Oracle 11g r2 The autobcp.pl script failed on Windows when Oracle 11g r2 database was used. The script ignored the exit code returned from the exp table when deferred segments were set to True by default. 5.44 getaddrinfo Retries Before Cancel The Scheduler stopped processing jobs and displayed the "Thread creation failed." error. The thread creation failed because there were many threads in hung state and the Scheduler could not start any more threads. While executing getaddrinfo, the threads were canceled although they were not actually timed out. 5.45 MDB Patches Missed Some of the CA MDB patches were missing in the database. 5.46 Status Not Sent to Cross-platform Manager (Oracle only) If a job is terminated, the status is not sent to the cross-platform manager in the following scenarios: * When you set up job scheduling managers for high availability, if the cross-platform manager rolls over when the Unicenter Autosys JM job is being executed, the termination status is not sent to the rolled over server as expected. * When a job terminates and is in TERMINATED status, the status is sent to the cross-platform manager, but it is not stored in the database. If the CCI sent to cross-platform manager fails, the status is not sent at the time of the next setup between the scheduling manager and Unicenter AutoSys JM. 5.47 Incorrect ujo_get_batch Event Stored Procedure (Microsoft SQL Server only) Incorrect ujo_get_batch event stored procedure caused SQL deadlock when fetching events from the database. 5.48 Jobs in a Box Ran Twice Occasionally, jobs running in QUE_WAIT status ran twice. The jobs had the same run_num and different entry numbers; they started immediately after the job was run for the first time. ______________________________________________________________________ 6.0 Published Fixes The complete list of published bug fixes for this product can be found through Published Solutions in the Download Center of the CA Support Online website, http://support.ca.com. ______________________________________________________________________ 7.0 Unicenter WCC Command Sponsor Installer Available on the Unicenter AutoSys JM r11 SP5 DVD The Unicenter AutoSys JM DVD ships the Unicenter WCC Command Sponsor installer and the corresponding readme files. The installer and readmes are available at the following locations on the Unicenter AutoSys JM r11 SP5 for UNIX/Linux DVD: * DVD/CommandSponsor/HPUX_i64 * DVD/CommandSponsor/Linux * DVD/CommandSponsor/Solaris * DVD/CommandSponsor/AIX * DVD/CommandSponsor/HPUX_parisc The installer and readme are available at the following location on the Unicenter AutoSys JM r11 SP5 for Windows DVD: * DVD/CommandSponsor Note: For more information about Unicenter WCC Command Sponsor and instructions on installing it, see the AutoSysSponsor_README.html file for your operating system. ______________________________________________________________________ 8.0 Contact CA 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. ______________________________________________________________________ Copyright (C) 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.