You are on page 1of 18

CONTROL-M Server and Agent for Unix Release Notes

Version 6.0.01 (FD4000/FD4001) April 24, 2001


*100037286* *100037286* *100037286* *100037286*
*100037286*

These release notes supplement information found in the CONTROL-M/Server and CONTROL-M/Agent Administrator Guides. These release notes also provide information about problems resolved in this release. The following topics are discussed: Topic Page

Compatibility .......................................................................................................................................................... 2 Whats New ............................................................................................................................................................. 3

CONTROL-M/Server ......................................................................................................................................... 3 CONTROL-M/Agent.......................................................................................................................................... 6


Whats Changed ..................................................................................................................................................... 6 Corrected Problems............................................................................................................................................... 7

CONTROL-M/Server Problems......................................................................................................................... 7 CONTROL-M/Agent Problems........................................................................................................................ 13 Documentation Problems.................................................................................................................................. 14


Open Problems .................................................................................................................................................... 15 Installation Procedure ......................................................................................................................................... 16 Product Documents ............................................................................................................................................. 18 Where to Get the Latest Product Information ................................................................................................... 18

BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. IBM and DB2 are registered trademarks of International Business Machines Corp.; Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corp. All other registered trademarks or trademarks belong to their respective companies. Copyright 2001 BMC Software, Inc., as an unpublished work. All rights reserved. Condential and Proprietary Information of BMC Software, Inc. 2101 CityWest Blvd., Houston, TX 77042-2827 713 918 8800 Technical Support: 800 537 1813 (USA and Canada) or contact your local support center

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Compatibility
CONTROL-M/Server version 6.0.01 is compatible with the following Unix platforms and operating systems:
Solaris 2.6, 2.7, and 2.8 HP-UX 9000 10.20 (Sybase only), 11.0 (with 64-bit support), and HP-UX11i (B. 11.11) Digital Unix (OSF) 4.0f (with 64-bit support), 5.0a, 5.0b, and 5.1

AIX 4.3.2 and 4.3.3 (with 64-bit support)

CONTROL-M/Agent version 6.0.01 is compatible with the following Unix platforms and operating systems:
Solaris 2.6, 2.7, and 2.8 AIX 4.3.2 and 4.3.3 HP-UX 9000 10.20, 11.0, and HP-UX11i (B. 11.11) Digital Unix (OSF) 4.0f, 5.0a, 5.0b, and 5.1 Data General 4.2 (Intel Processor) Reliant Unix (Pyramid DC-OSx 1.1-94c079 or Siemens SINIX) 5.43, 5.44, and 5.45 Linux Red Hat 5.2 and 6.2 Sequent Dynix 4.4.5, 4.4.6, 4.4.7, and 4.4.8 NCR 3.02

IRIX (Silicon Graphics) 6.5 UnixWare SCO 7.1

Note CONTROL-M/Server for Unix version 6.0.01 is not supported on HP machines in the 98xx series which are running a 32-bit O/S version. Only this combination of components is not supported. All other combinations of these components with other machines or platforms are supported.

Page 2 of 18

Condential and Proprietary Information of BMC Software, Inc.

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Whats New
These topics describe enhancements made in this release.

CONTROL-M/Server
The more signicant enhancements in this release are listed here as bulleted items. These items are followed by a table that lists all enhancements. Group Scheduling. Jobs to be processed together can now be dened in Group Scheduling tables. Each Group Scheduling table contains denitions for scheduling criteria, submission criteria, and post-processing parameters to be applied to all jobs in the group. For more information about Group Scheduling, see: The ctmgrpdef utility in Chapter 2 of the CONTROL-M/Server for Unix Administrator Guide. Group Scheduling Tables in Chapter 2 of the Enterprise Controlstation User Guide. The Adjust Conditions, Relationship, and Schedule Tag parameters in Chapter 5 of the Enterprise Controlstation User Guide. The defgroup and deftags utilities in Chapter 8 of the Enterprise Controlstation User Guide. Chapter 4 of the CONTROL-M/Desktop User Guide.

Global AutoEdit Variables. Using a new naming convention, AutoEdit variables can be dened as global by adding the \ character to the variable name (for example, %%\varname). The range of these global variables is conned to the data center (the CONTROL-M installation) in which the variable is dened. Support for ERP jobs in the ctmcreate and ctmdene utilities. Special ERP specic parameters can now be specied in the command line for these utilities. For this release, parameters can be specied for R/3 jobs and for Oracle Applications jobs. For more information, see the descriptions of these utilities in Chapter 2 of the CONTROL-M/Server Administrator Guide. Advanced Problem Detection Tools (APDT). These tools include utilities that help maintain productivity and protect data. These tools enhance system monitoring to help avoid failures, and provide various methods for safeguarding data in case of a crash.

Condential and Proprietary Information of BMC Software, Inc.

Page 3 of 18

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Tracking Number
IMPM000006

Description
A transparent database layer has been provided to support Sybase and Oracle. CONTROL-M database servers were upgraded to support Sybase 11.9 and Oracle 8i. Data transfer between CONTROL-M and ENTERPRISE/CS has been enhanced. These enhancements include transferring Start and End times for the active job, increasing the maximum DSECT size to 32K, and downloading the User Daily eld when the Scheduling table is downloaded. Timestamps and user IDs are added to the Job Denition record of each job. Both Creation Date and Last Modication Date timestamps are maintained. AutoEdit variables can now be dened as global by adding a \ to the variable name. See the bulleted item at the beginning of this topic. A timestamp is now inserted in a condition name if the condition name adheres to the Dynamic Naming Pattern. This enables condition names ordered from a specied table to be uniquely identied. When a Scheduling table is ordered, all its conditions that adhere to the Dynamic Naming Pattern will have a unique name identifying the table that was ordered. The ctmlog utility can now be congured to protect the delete option from all users except the CONTROL-M administrator. Full support for AutoEdit variables is now provided in the job's script. See WMPM005675. Group Scheduling is now provided. See the bulleted item at the beginning of this topic. The value STAT can be specied in a prerequisite condition's date eld. This value prevents the New Day procedure from removing the condition. The installation procedure automatically calculates the size of tempdb (the temporary storage area of a CONTROL-M database) based on the size denition of the controlm database. The size of tempdb can be changed during the installation. Note: This enhancement is relevant only for installations using a Sybase SQL server. Cyclic jobs can now be stopped by using a new post-processing parameter, DO STOPCYCLIC. New AutoEdit variable %%PRECMD denes a command that runs immediately before the job dened by MEMNAME. New AutoEdit variable %%POSTCMD denes a command that runs immediately after that job ends. The length of the Condition Name eld has been increased to 39 characters. The ctmfw utility can now return a different exit code on condition when the lewatcher command line mode request will time-out. In Unix, the return code for timeout is 2. This value is effective only when the ctmfw utility is executed in command line mode.

IMPM000009

IMPM000021

IMPM000030

WMPM001092

WMPM001164

WMPM001351

WMPM005002

WMPM005032

WMPM005085

WMPM005162

WMPM005203

WMPM005257

WMPM005301 WMPM005373

Page 4 of 18

Condential and Proprietary Information of BMC Software, Inc.

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Tracking Number
WMPM005374

Description
E-mail addresses can be specied directly in a message using the DO MAIL option in the post-processing parameters instead of dening e-mail addresses in the Shout Destination table. Multiple addresses, separated by a semicolon ;, can be specied. Messages specied using DO MAIL have a maximum length of 4096 characters. In CONTROL-M and ENTERPRISE/CS, the length of the command line has been increased to 512 characters. The length of the command line after resolving AutoEdit variables has been increased to 999 characters. If a command exceeds 999 characters after AutoEdit variables are resolved, a message is sent to the joblog and the command is truncated. Advanced Problem Detection Tools are now available. See the bulleted item at the beginning of this topic. See IMPM00009 above. The maximum length for job denition records was increased from 6K to 32K. Failover and mirroring are now supported for Sybase and Oracle databases. AutoEdit variables can now be passed to CONTROL-M/Agent and used in existing job scripts.You can pass all job AutoEdit variables to the temporary script that CONTROL-M creates. This feature is enabled by setting the AUTOEDIT_INLINE variable in the Agent conguration le to Y (Yes). Default: N (No). The AutoEdit facility and the AUTOEDIT_INLINE conguration parameter incorporate AutoEdit variables into existing job scripts. All job AutoEdit variables can be passed to the temporary script that CONTROL-M creates. The syntax depends on the script shell. AutoEdit variables that are local to a job can be used inside the script. Their value is resolved at runtime. For example, you can create a backup le and use the variable name %%Current _Time inside it. The variable set by CONTROL-M is passed to the script. It is then passed by the environment variable and is dened in the users environment. The job selection algorithm has been improved. It now allows more jobs to be handled during a given time interval. The backup and restore procedure for database conguration parameters can now handle the conguration parameters of a Sybase Database server. Support for ERP jobs is now provided by the ctmcreate and ctmdene utilities. For more information, see Whats New on page 3.

WMPM005381

WMPM005392

WMPM005527 WMPM005548 WMPM005581 WMPM005675

WMPM005718

WMPM005740

WMPM005759

Condential and Proprietary Information of BMC Software, Inc.

Page 5 of 18

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

CONTROL-M/Agent
The table below includes a comprehensive list of all enhancements made for the CONTROL-M/Agent.
Tracking Number
WMPM005236

Description
Some CONTROL-M les on Agent platforms are now Read only if accessed from outside the Agent. Previously, these les had Read/Write permission. Agent les can now be modied only by the owner of the Agent directory. When changing the CONTROL-M/Server hostname in ag_menu on CONTROL-M/Agent for Unix, the specied host name must already be in the authorized CONTROL-M Servers le. If you try to specify an unlisted host, you now receive the following more user-friendly message: Host: <name> is not permitted. Please update the Authorized CONTROL-M Servers list by choosing the option Backup CONTROL-M/Server Host Name: Press Enter to continue. Agent availability has been increased by subscribing the service in the /etc/inetd.conf le as NOWAIT. Previously, it was subscribed as WAIT. Example: ctm_agtcp3 stream tcp nowait root/ /home/ctmagent/ctm/exe_AIX/p_ctmag p_ctmag -e /home/ctmagent/ctm

WMPM005752

WMPM005790

Whats Changed
The items in the following table describe features that work differently from the way they functioned in previous versions.
Tracking Number
IMPM000012

Description
CONTROL-M/Server now maintains a database that contains information about Server and Agent availability. This enables the CONTROL-M/Server to keep track of available Agents and the communication protocol for each Agent. The polling process for Agent availability is called Discovery. When Discovery connects to an Agent, that Agent can receive jobs. In conditions can now be joined by Boolean expressions. A specic job can be ordered or forced when a Scheduling table contains two or more jobs with identical jobnames. The jobs are differentiated by unique job sequence numbers. If a job sequence number is not specied when a job is ordered or forced, CONTROL-M submits the rst job found in the table with the specied jobname (instead of submitting all the jobs with that jobname). The time interval between runs of a cyclic job can now be calculated from either the start or end of the job.

WMPM001184 WMPM001485

WMPM005184

Page 6 of 18

Condential and Proprietary Information of BMC Software, Inc.

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Tracking Number
WMPM005209

Description
AutoEdit variable %%DATACENTER now resolves to the data center name specied in the Enterprise Controlstation GUI. Previously, this variable resolved to the host name of the computer where CONTROL-M was installed. The user can now choose which editor should be invoked by the ctmpsm utility for sysout viewing. Installation is no longer performed by the root user. All root activity has been placed in a script le that is executed by the system administrator.

WMPM005310

WMPM005337

Corrected Problems
The following problems in earlier releases of CONTROL-M have been corrected in this release:

CONTROL-M/Server Problems
Tracking Number
BMPM001566 BMPM001712 BMPM005215 BMPM005381 BMPM005443 BMPM005476 BMPM005493

Corrected Problem
The installation of CONTROL-M/Server improperly modied the /etc/copyright le. A protocol type (upd/tcp) was not specied in the /etc/services le when a socket number was updated using ctm_menu. An incorrect start time was recorded in ENTERPRISE/CS after changing the clock for daylight savings time.This resulted in inaccurate job statistics. CONTROL-M did not download the User Daily eld to Enterprise Controlstation. If more than one job in a scheduling table had the same jobname, the ctmpsm utility could not be used to order one of those jobs. The ctmpsm utility ignored security restrictions. Timing problems which occurred while tracking a running job caused certain jobs to disappear, and caused their status to be recorded as ended NOTOK in the jobs logle. During installation the user was able to place the master, data, and log database elements on the same raw device. This is no longer allowed. A syntax error in the ctm_passwd utility caused the CONTROL-M password to not be updated on the AIX platform. The ctmrpin utility generated the message Segmentation fault (core dumped) if a year value greater than 2037 was specied. An AutoEdit variable was not resolved if only a single percent sign % was included in the message. This occurred in shout messages, command lines, and job scripts. No error messages were displayed.

BMPM005487 BMPM005610 BMPM005696 BMPM005707

Condential and Proprietary Information of BMC Software, Inc.

Page 7 of 18

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Tracking Number
BMPM005729 BMPM005752 BMPM005761 BMPM005799 BMPM005821 BMPM005829 BMPM005830 BMPM005879 BMPM005895

Corrected Problem
Attempts to View Doc and View Sysout failed if the line size exceeded 200 characters. CONTROL-M could not handle multiple CS processes. The checksum was not updated when the ctmdene utility was used to modify scheduling tables. days parameter values with a -Ln format (for example, -L1) could not be specied without a Days calendar in the input for the ctmdene utility. The ctmdbrst utility did not return the correct exit code. Running the ctmudly utility with a nonexistent User Daily caused a new entry to be created in CMR_UDLAST. The exit option was not displayed on the ctmlog utilitys option menu. Utilities could not be run by any Unix user except a user who logged in to the CONTROL-M/Server account. Certain administrative utilities were executable by users without administrator authority. These utilities included: ctmjsa, ctmdbbck, ctmdbrst, ctmruninf, ctmshtb, ctmsuspend, ctmudlst, and ctmudly. During the New Day procedure, the CD process sent redundant triggers to itself. The full physical name in the Shout destination table was limited to 90 characters. If the user specied more than 90 characters for an email address, user name, or terminal name, CONTROL-M truncated the eld to 90 characters without issuing an appropriate message. If a job was not ordered because the owner did not have permission to order it, an incorrect message, indicating that the job had been successfully ordered, was sent to the IOALOG. The TR process hung when trying to locate a job ID that did not exist in the Active Jobs le. Under certain conditions, a locked le in the ctm/tmp directory caused the New Day procedure to hang. The ctmdiskspace utility ended with a return code of 0 even if there was less free disk space than the specied minimum. Under certain conditions, a table upload failure caused a le to remain locked in the CONTROL-M user tmp directory. At sites using a Sybase database server, the prerequisite conditions table was not cleaned up if a user attempted to modify the conditions table during the run of the New Day procedure. When running routine OS_IPC_send() in debug level 4, the SL process crashed (under certain circumstances) and produced a core dump. A scheduling problem occurred when specifying >n or <n in job processing parameter DAYS. If the indicated day was not a working day because parameter MONTH was set to N, and the closest preceding working day when using <n (or next working day when using >n) was in another month, the job was scheduled. A previous or next day should not be searched for if the job should not be ordered during the current month.

BMPM005904 BMPM005905

BMPM005926

BMPM005962 BMPM005980 BMPM005981 BMPM005982 BMPM005984

BMPM005988 BMPM006035

Page 8 of 18

Condential and Proprietary Information of BMC Software, Inc.

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Tracking Number
BMPM006044

Corrected Problem
When using ctm_menu to change the debug level for the CS process, an error message was generated even though the change was performed successfully. The TR process did not free allocated memory. Invoking DOFORCEJOB for a nonexistent job caused the invoking job to be placed in Hold status. Deleting prerequisite conditions in batch mode caused degradation of CONTROL-M performance. When running the ctmrpln utility during the year 2000, specifying a 2-digit year in the range 70-99 produced the result 2070-2099 instead of 1970-1999. Jobs whose DAYS specication included a less than sign (<n) were improperly ordered on the last day of the year regardless of the calendar denition for the following year. CONTROL-M users were not given permission to access the mirror database. During mirror installation, the user was instructed to give read permission to the controlm le to users other than the CONTROL-M owner. However, similar instructions were not provided for the controlm_mirror le that is used for the encrypted passwords of the mirror database. Job tracking did not work properly when a large number of jobs were running. When a dummy job was dened as cyclic, the Next Time eld was not calculated when the job details screen was viewed. Also, the NEXTTIME eld was NULL in the CMR_AJF for these cyclic jobs. Intermittent network problems caused CONTROL-M/Server to identify the CONTROL-M/Agent as Unavailable. Jobs migrated from CONTROL-M version 2.2.4 were not ordered if they specied a periodic calendar and more than one value for parameter Days. The -updateajf addcondin and addcondout commands in the ctmpsm utility did not work. The upgrade to FD3501 (the previous release) using an existing Sybase version 11.9.2 database server failed if the same DBO (database owner) and device names were used. If more than one address was specied in a domail statement, the message was not sent to all of the specied addresses. This problem occurred only on HP-UX platforms. The ctmlog utility failed with the error message

BMPM006055 BMPM006068 BMPM006121 BMPM006129 BMPM006173

BMPM006294

BMPM006507 BMPM006520

BMPM006553 BMPM006568 BMPM006589 BMPM006607

BMPM006621

BMPM006632

Select init status = FAIL


if the requested information was too large for CONTROL-M to display. BMPM006635 Changing a password while failover was enabled caused reinitialize failover to fail. After specifying a new password for the $CONTROLM_PASSWD parameter and then performing initialize mirroring on the primary server, CONTROL-M came up only after performing init_prag. The result was that the jobs did not appear on the mirror database. The message Mirroring is DAMAGED was displayed instead. When upgrading from FD3059 to FD3501, Oracle could not perform a necessary chmod command on the /home/ctm600/install/rootsh.log le.

BMPM006637

Condential and Proprietary Information of BMC Software, Inc.

Page 9 of 18

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Tracking Number
BMPM006653

Corrected Problem
Wild card characters were not checked when checking Entities authorization. For example, qauser$ was specied inside ctmsec but its authorizations were not checked when uploading calendars from ENTERPRISE/CS. The ctmrpln utility did not support the N calendar value (ignore calendars). When upgrading from FD3549 to an existing FD3501 Sybase, the NS process issued get_slot() failed messages. When the ctmorder utility was invoked with -ingrouporderid last or -ingrouporderid <order id> specied, the new job(s) were added to the Active Jobs le with a Held status. These jobs remained held until they were freed manually. The NS process showed an error message:

BMPM006654 BMPM006669 BMPM006688

BMPM006696 BMPM006714

GM_36_base_36_to_digit gets illegal input.


The user could not start CONTROL-M after a successful installation if CONTROL-M was installed using a new dedicated Oracle database server, and another Oracle installation already existed on that same machine. After messages indicating a successful Solaris installation, it was not possible to start CONTROL-M. The ucb lib path was not needed and was removed from .cshrc. The CONTROL-M database could not be restored from the mirror database. When CONTROL-M was installed on an AIX machine using an Oracle database server, jobs could not be viewed using the ctmpsm utility, or it took a long time for all jobs to be displayed (about 60 seconds to list 200 jobs). CONTROL-M could not be started on the Sybase mirror server after disabling mirroring on the primary server. There were problems performing a cold backup with an existing Oracle database on a remote server. The ctmjsa utility did not display the CMR_STATIS table. If a job group (a group entity) was still executing when the New Day procedure was run, the group was removed from the Active Jobs le, and post-processing was not performed for this group. The JOBNAME parameter to lter the statistics was missing in the ctmjsa utilitys list option. User exit 102 did not function properly. User exit 103 was not able to replace the User Daily name. Conditions that use parenthesis as part of their name were not handled correctly when upgrading from an earlier CONTROL-M release. The logical names of database extension devices were made more meaningful. There had been no difference in the logical names of log devices and data devices. For example, when the rst device was the extension for data and the second device was the extension for the log, both were called ctmrlm_extend<n>. CONTROL-M/Agent did not retain the sysout and ecf les for the number of days specied in the Maximum Days to Retain Sysout Files parameter on the server platform. Under certain circumstances, jobs that ended NOTOK were not removed from the Active Jobs le during execution of the New Day procedure.

BMPM006719

BMPM006720 BMPM006721

BMPM006722 BMPM006726 BMPM006727 BMPM006728

BMPM006730 BMPM006733 BMPM006734 BMPM006753

BMPM006755

BMPM006756

Page 10 of 18

Condential and Proprietary Information of BMC Software, Inc.

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Tracking Number
BMPM006757 BMPM006763 BMPM006771

Corrected Problem
Running a stress test of 1000 CONTROL-M Agent jobs on a Linux machine caused some jobs to disappear and some jobs to end NOTOK. The user could type LISTALL without entering any other required elds when using the ctmpsm utilitys LISTALL parameter. During cold backup, the ctmdbbck utility automatically shut down CONTROL-M. If CONTROL-M was running during cold backup, an error message was displayed and CONTROL-M exited. The ctmkilljob utility did not function on HP machines. The ctmpsm utility -updategroup rerun did not work properly. Running the ctmdene command from a script (batch) caused the following error message: Failed to create new job!, retrying... This also occurred when one job had two tags with the same name. The ctmstats utility displayed data that was not in the specied cell. The format of the ctmpsm utility in -CHILD mode was not correct. When using -CHILD mode, the tasktype parameter is optional. Therefore, the format was changed to: ctmpsm -CHILD <orderid> [<tasktype>] When performing a silent installation with an existing Sybase, there was a validation script problem. Problems with the validation script and the Oracle installation script were xed. The number of sysout records did not match the number of runs. This happened when a cyclic job ran on a number of Agents and disappeared during one of its runs. Selecting CTM_MENU: option 9 Troubleshooting and then selecting option 17 Troubleshooting Report caused error messages to be generated with both Oracle and Sybase databases Jobs remained in Wait resource status for a long time without any cause. The Server was not updated when Agent became available The ECF le contained corrupt information. The status of a cyclic job remained in submit mode, even though the job ran to completion. The hour of the New Day procedure was not translated correctly by the program that stores data in the database. For example, the hour of the New Day procedure was set to 15:00, but the hour was translated as 0300. An existing Oracle 8.1.6 database could not be backed up from a remote platform using the ctmdbbck utility. When an NS process became defunct, the SU process did not recognize it and did not bring it down. The Check Database option in the CONTROL-M menu did not work properly. When using an existing Oracle 8.1.6 database, the following message was generated twice: JServer Release 8.1.6.0.0 - Production In some circumstances, a job would hang if the WD process timed out on a user exit. The JOB FORCE utility failed and generated the error message invalid job sequence number when it was invoked from the CLI (Command Language Interface) in ENTERPRISE/CS.

BMPM006775 BMPM006778 BMPM006779

BMPM006780 BMPM006781

BMPM006784 BMPM006785 BMPM006791

BMPM006800

BMPM006812 BMPM006814 BMPM006822

BMPM006832 BMPM006833 BMPM006834 BMPM006837 BMPM006840 BMPM006847

Condential and Proprietary Information of BMC Software, Inc.

Page 11 of 18

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Tracking Number
BMPM006880

Corrected Problem
Cyclic jobs with from time and until time did not continue after midnight. For example, a cyclic job with from time 10:00 and until time 11:00 did not continue the next day at 10:00. Jobs that ran the ag_ping utility as the last step ended NOTOK. The utility did not fail but the exit status was NOT OK. AutoEdit variables with a prex of %%\$ were not validated. This caused nonexistent AutoEdit variables to be accepted. Reset_gd asked for conrmation when using a Sybase database but not when using an Oracle database. On Code/Statement comparisons were incorrect if multiple On Statements occurred on the same sysout line. No match was found because the algorithm searched the second line and not the continuation of the rst line. When the rst On statement was matched, the algorithm did not look for the second On statement on the same sysout line. Instead, the next sysout line was searched for the second On statement. As a result, if the second On statement appeared in the rst line, no match was found. Dostopcyclic did not revert to cyclic after rerun. If stop cyclic ended NOTOK, it did not revert to its normal cyclic interval after the error was corrected and the job was restarted. The install hung with the make_db script running if the TNS listener was not active. Now you can check that the TNS listener is active and that connectivity to the database is available. When using an existing Oracle database, you should check that the TNS listener is active and that connectivity to the Oracle database is available before attempting to install. System AutoEdits were not passed to the Agent. Only local job AutoEdits were passed to the Agent. Now system AutoEdits are also passed to the Agent. Shout messages were not properly handled by CONTROL-M/Server on certain 64-bit operating systems (e.g., Solaris 2.8).

BMPM006982 BMPM006987 BMPM006991 BMPM007005

BMPM007013

BMPM007021

BMPM007043

BMPM007079

Page 12 of 18

Condential and Proprietary Information of BMC Software, Inc.

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

CONTROL-M/Agent Problems
Tracking Number
BMPM005259 BMPM005493

Description
Filename wildcards were not properly resolved in the ctmfw utility. Timing problems which occurred while tracking a running job caused certain jobs to disappear and their status to be recorded as ended NOTOK in the jobs logle. CONTROL-M/Agent crashed and produced a core dump while performing a sysout analysis. Cookies generated by CONTROL-M perform background operations as a script executes. These cookies disrupted the KSh and SH script syntax. Now, cookies are not added to KSh and SH scripts and these scripts are not copied into a temporary le during parsing. The ctmfw utility hung when it could not access a directory. A security breach could occur when running a job with task type command because the Agent created a temporary script in directory /tmp with permission 777. When a job had a user ID of 6 digits or more, CONTROL-M/Agent treated this user ID as the owner and did not allow the sysout to be viewed. The shout to program did not accept hostname input. Shout to program now accepts 3 parameters: 1. hostname, 2. severity, and 3. message. For example: parameter1=tiger, parameter2=U, and parameter3=<message text>. If a user attempted to edit a JCL script le using ENTERPRISE/CS, the JCL le was corrupted if the user only had permission to modify the JCL le and did not have permission to modify the directory where the JCL le resides. When determining if a user should be allowed to edit JCL using ENTERPRISE/CS, permissions were checked for the job owner. Now, permissions are checked for the ENTERPRISE/CS user.

BMPM005532

BMPM005756

BMPM005773 BMPM005921

BMPM006043

BMPM006631

BMPM006717

BMPM006718

Condential and Proprietary Information of BMC Software, Inc.

Page 13 of 18

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Documentation Problems
The following problems will be xed in the next release of the CONTROL-M/Server documentation.
Tracking Number
DMPM001989

Description
The note on page C-1 of the CONTROL-M/Server Administrator Guide refers to the x1C.rt library. This reference should refer to the x1C.rte library. In Table C-1 on page C-2 there is note indicating that, for dedicated Oracle installations, certain operating system utilities should be installed at /use/ccs/bin. The correct path should be /usr/ccs/bin. The following parameter should be added to Table D-3 on page D-8 of the CONTROL-M/Server for Unix Administrator Guide: maxdsiz minimum 256. Note: This parameter needs to be set to this value only if you are currently upgrading from a 32-bit to a 64-bit HP operating system. The following changes should be made to Table F-1 on page F-2 of the CONTROL-M/Server for Unix Administrator Guide:: The row entitled Operating System Utilities should be deleted. The following text should be used to replace the text in the line entitled Required Executables. For all Oracle installations the make, ar, ld, and nm executables must be present in the /usr/ccs/bin directory.

DMPM001990

DMPM001991

DMPM001992

DMPM001993

On pages 7-51 and 7-52 of the CONTROL-M/Server for Unix Administrator Guide, g should be replaced with r in the following text:

To return to the start of the Oracle installation, enter g.


DMPM001994 The following text should be added to page F-5 of the CONTROL-M/Server for Unix Administrator Guide:

Modifying Digital Unix Kernel Parameters


Use the following command to view the current values of the kernel parameters: /sbin/sysconfig -q ipc To change Digital Unix kernel parameters, under the root user, manually update the ipc section of the /etc/syscongtab le DMPM001996 On pages 7-45 and 7-50 of the CONTROL-M/Server for Unix Administrator Guide replace:

To continue the installation procedure, go to Post-Installation Tasks -Immediate on page 7-61.


with

Go to Running the Oracle Post-installation Script on page 7-59.

Page 14 of 18

Condential and Proprietary Information of BMC Software, Inc.

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Open Problems
The following problems will be corrected in a future release of CONTROL-M:
Tracking Number
BMPM006724

Problem Description
Under certain circumstances, the following message may appear during CONTROL-M startup:

CTMSU process tries to start another CTMSU process


This indicates that the prf (process ags) table has been corrupted. Workaround: If this problem occurs, issue the init_prag command to recreate the process ags table and then restart CONTROL-M. BMPM006675 BMPM007169 BMPM007193 The ctmkilljob utility does not work properly on the HP-UX platform. In certain circumstances, the User Daily does not successfully order all the jobs in a group scheduling table. Option 72 (Order Tables/Jobs) of the ctmpsm utility cannot be used to order a job from a group scheduling table. Workaround: Use the ctmorder utility to order this job. Job statistics are not automatically provided to ENTERPRISE/CS (e.g., for the Statistics option of the action menu). Workaround: Run the ctmjsa utility in CONTROL-M/Server before requesting job statistics in ENTERPRISE/CS. Silent installation of CONTROL-M/Server with a dedicated Oracle Database server fails if a non-default Oracle instance name is specied. Workaround: After running the install/orapreinst.sh script under the root user (during the installation procedure), you must update the ora_defs le in <CONTROL-M home directory>/tmp/ as follows: Find the DB_NAME_DEF variable and change its value to the desired Oracle instance name. Add the following line to this le: PROCESSES=100 Upgrade from CONTROL-M version 2.2.4 or 2.2.5 to 6.0.01 fails if the database owner name is changed during the upgrade procedure. Workaround: Change the database owner name only after the upgrade procedure is completed. Silent installation of CONTROL-M/Server with a dedicated Oracle Database server fails if a non-default system password is specied. Workaround: After the silent installation is completed, change the system password using the ctmdbapasswd script. If the Oracle database goes down and the CONTROL-M database session is therefore shut down, the connection is not automatically re-established when the database is reactivated. Workaround: Shut down and then restart CONTROL-M to re-establish the CONTROL-M connection to the database.

BMPM007196

BMPM007198

BMPM007202

BMPM007203

BMPM007207

Condential and Proprietary Information of BMC Software, Inc.

Page 15 of 18

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

Installation Media
The following CDs are provided with this release:
Volser
FD4000

Description
CONTROL-M/Server FD4000 (Sybase/Oracle) for Unix and CONTROLM/Agent FD4001 for Unix Oracle 8.1.6 for Solaris 32-bit Oracle 8.1.6 for Solaris 64-bit Oracle 8.1.6 for HP-UX 32-bit Oracle 8.1.6 for HP-UX 64-bit Oracle 8.1.6 for AIX 32-bit Oracle 8.1.6 for AIX 64-bit Oracle 8.1.6 for Digital Unix

FD4273 FD4274 FD4275 FD4276 FD4277 FD4278 FD4280

Note CONTROL-M/Server can also work with an existing Oracle Database server version 8.1.7 on all the above-mentioned platforms.

Installation Procedure
Use the FD4000 CD (CD1) for a new installation or to upgrade to CONTROL-M/Server version 6.0.01 and CONTROL-M/Agent version 6.0.01. For complete instructions on the installation and implementation of CONTROL-M, see the appropriate installation chapter in the CONTROLM/Server for Unix Administrator Guide.

Note CONTROL-M/Server and CONTROL-M/Agent can also be installed using the ICE Installer. For more information, see the ICE Installer Administrator Guide version 1.1.01 (available with FD4217). CONTROL-M/Agent version 6.0.01 (FD4001) can be installed as a new installation or as an upgrade for any of the releases: FD2768, FD3296, FD3747, FD3585, or FD3637.

Page 16 of 18

Condential and Proprietary Information of BMC Software, Inc.

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

CONTROL-M/Server version 6.0.01 (FD4000) can be installed as an upgrade for any of the releases in the following table.
Volser
FD2790 FD3295 FD3549 FD3059 FD3442 FD3636

CONTROL-M/Server for Unix Version and Level


Version 2.2.4 (Sybase) level 9807 Version 2.2.4 (Sybase) level 9901 Version 2.2.4 (Sybase) level 0001 Version 2.2.4 (Oracle) level 9901 Version 2.2.5 (Sybase) level 9901 Version 2.24.04 (Sybase)

Note Oracle 8.1.5 and Sybase 12 are supported only as existing servers. However, Oracle 8.1.6 and Sybase 11.9.2.1 are supported as either dedicated servers or existing servers. If you are upgrading from an earlier version of CONTROL-M/Server, you must either: Upgrade the CONTROL-M/Agents in your system before the CONTROL-M Server is upgraded.

-or Specify the necessary value for the COMVERSION parameter for communicating with the specic Agent platform. This parameter indicates the version of the Agent.

To specify the CONTROL-M/Agent version communication parameter:

1. Select ctm_menu => Parameter Customization => Parameters for Communicating with Specic Agent Platforms. The following prompt is displayed:
To view/modify communication parameters, enter node ID of Agent Platform:

2. Enter the node ID of the CONTROL-M/Agent, for example, diana. The Communicating with Specic Agent Platform menu is displayed.

Condential and Proprietary Information of BMC Software, Inc.

Page 17 of 18

Release Notes (continued)


CONTROL-M Server and Agent for Unix April 24, 2001

3. Select Communication Protocol Version: from the Communicating with Specic Agent Platform menu. The following prompt is displayed:
Communication Protocol Version (default: 03) :

4. Specify a value for the communication parameter and press Enter. See Table 1 for a list of the valid values.
Table 1 Communication Protocol Version Values

Parameter Name
COMVERSION

{Valid Values} Explanation


(01|02|03} 01 02 03 CONTROL-M/Agent version 2.2.4 CONTROL-M/Agent version 2.2.5 CONTROL-M/Agent version 6.0.01

Product Documents
The following documents support the product:
Publication Date
April 24, 2001 March 31, 2001 April 24, 2001 April 24, 2001 April 24, 2001 April 24, 2001

Document
CONTROL-M/Server for Unix Administrator Guide version 6.0.01 CONTROL-M/Agent for Unix Administrator Guide version 6.0.01 Enterprise Controlstation User Guide version 6.0.01 Enterprise Controlstation Administrator Guide version 6.0.01 Enterprise Controlstation Installation Guide version 6.0.01 CONTROL-M/Desktop User Guide version 6.0.01

Where to Get the Latest Product Information


To view the latest BMC Software documents, visit the support page on the BMC Software Web site at http://www.bmc.com/support.html. Log on and select a product to access the related documentation. (To log on, rst time users can request a user name and password either by registering at the support page or by contacting a BMC Software sales representative.)

Page 18 of 18

Condential and Proprietary Information of BMC Software, Inc.