For SCHEDULE for Tru64 UNIX installations into the diskless environment, the disk on which SCHEDULE for Tru64 UNIX subsets reside are on a server system. Therefore, for installations into diskless environments, log in to the server system to check disk space requirements.

Inspect the free space in the environment(s) that you want to install the client. For example, if you have only one diskless installation environment set up on your system, it is found on the path /var/adm/dms/dms0.alpha.

This free space must be large enough to hold the subset requirements listed in Table 5-2. Consult the Tru64 UNIX document entitled, Sharing Software on a Local Area Network, for more information on sizing disk space necessary for a DMS installation.

5.3 Backing Up Your System Disk

You should back up your system disk before installing any software. Use the backup procedures established at your site. For details on performing a system disk backup, see your Tru64 UNIX documentation.

5.4 Stopping the Installation

You can stop the installation procedure at any time by using [Ctrl]-C. However, files created up to that point are not deleted. You must delete files interactively. Appendix A lists the files and directories created during the installation procedure.

5.5 Error Recovery

There is not enough file system space for subset SCHBPR1711. SCHEDULE Group 1 executable files (SCHBPR711) will not be loaded.

Errors can occur during the installation if any of the following conditions exist:

• The operating system version is incorrect.
• The prerequisite software version is incorrect.
• The system parameter values for successful installation are insufficient.

For descriptions of error messages generated by these conditions, see the DIGITIAL UNIX documentation on system messages, recovery procedures, and Tru64 UNIX software installation. If you are notified that any of these conditions exist, take the appropriate action described in the message. For information on system requirements, see Section 5.2.3

5.6 Installing SCHEDULE for Tru64 UNIX

This chapter describes the procedures for installing SCHEDULE for Tru64 UNIX software. Before you start, read Chapter 5, which describes the general options and requirements that apply to installing SCHEDULE for Tru64 UNIX software.

5.7 Selecting the installation method

SCHEDULE for Tru64 UNIX software can be installed in a number of ways:

• Downloading the file from the ISE Support website.
• Downloading the file using the ISE FTP site.
• Copying the file from the ISE CD.

The ISE Support Site has a direct link to the latest version of the Installation file required to install EntepriseSCHEDULE. The URL to access the download is:

http://support.i-s-e.com/software_downloads/unix/

Download SCH7312.tar or SCH7312.tar to a local temporary directory on your Tru64 UNIX machine and uncompress the file.

5.7.2 Option 2: Obtaining the .tar or .tar.gz file using the ISE FTP Site

To download the software, you must have FTP access to the internet from a Tru64 UNIX session. Start by changing to the root directory:

cd /

Start by entering the following FTP command:

# FTP ftp.i-s-e.com

Use ftp to download the file to an empty directory:

ftp> cd /latest_tru64 ftp> bin ftp> get SCH7312.tar.gz or ftp> get SCH7312.tar

5.7.3 Option 3: Copying the .tar file from the CD

If you are installing SCHEDULE for Tru64 UNIX software from disk, start the installation procedure as follows:

1. Insert the media into the appropriate CD-ROM disk drive.
2. Log in as a superuser (login name root) to the system on which you are installing SCHEDULE for Tru64 UNIX
3. Make sure you are at the root (/) directory by entering the following command.

   # cd /

4. Specify the /mnt directory to the mount point for the distribution file system on the drive. If your drive is ra1, enter the following command:

   # mount -t cdfs -o noversion,rrip /dev/ra1c /mnt

5. Copy /unix/schedule/kit/SCH7312.tar from the CD to a local temporary directory

   # cp /unix/schedule/kit/SCH7312.tar /tmp

This installation procedure loads SCHEDULE for Tru64 UNIX files on a disk that belongs to the system on which you perform the installation. When SCHEDULE for Tru64 UNIX is run, its executable images are mapped into memory on this system.

5.8.1 Running the install

To unzip the .gz file:

# gunzip SCH7312.tar.gz

To explode the tar container:

# tar -xvf SCH7312.tar

Note: To install the software:

• You must Login as root.
• If this is an upgrade, shutdown any running SCHEDULE servers by using the following commands:

  # /schedule_library/schedule_start.ksh display # /schedule_library/schedule_start.ksh stop 0 # /schedule_library/schedule_start.ksh stop 1

You can now run the installation. The most simple installation command would be:

# setld -l ./sch7312

(or /usr/sbin/setld)

5.8.2 Responding to Installation Procedure prompts

After you enter the setld command for local (non-specific) installations or after you start the dms or ris utility for server installations, the installation procedure displays the names of SCHEDULE for Tru64 UNIX subsets and asks you to specify the subsets that you want to load:

*** Enter Subset Selections *** The subsets listed below are optional: The may be more optional subsets that can be presented on a single screen. If this is the case , you can choose subsets screen by screen, or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) SCHEDULE Group 0 initial database 2) SCHEDULE Group 1 executable images 3) SCHEDULE Group 1 initial database Or you may choose one of the following options: 4) All mandatory and all optional subsets 5) MANDATORY subsets only 6) Cancel selections and redisplay menus 7) Exit without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 3

When installing form a RIS server, note that the subset numbers may vary depending on what products are available in the RIS area.

If you specify more than one number at the prompt, seperate each number with a space, not a comma.

Next, the script lets you verify your choice. For example if you enter 3 in response to the previous prompt, you will see the following display:

You are installing the following optional subsets: Is this correct?: (y/n):

If the displayed subsets are not the ones you intended to choose, enter n. In this case, the subset selection menu is again displayed and you can correct your choice of optional subsets.
If the displayed subsets are the ones you want to load, enter y.

Note If this is an upgrade, skip to step 6. Otherwise: load the PAS license number (instructions are in the file)

Load the PAS number

# vi /schedule_library/sch0_license.dat

Start the Schedule Server (on reboot this is automatic)

# /schedule_library/schedule_start.ksh bootall

Complete the installation by loading standard objects:

# /schedule_library/schedule_standard_loads.ksh

Note If this is a new install you are done.

Shutdown any running SCHEDULE servers by using the following commands:

# /schedule_library/schedule_start.ksh stop 0 # /schedule_library/schedule_start.ksh stop 1

Copy the license files from the previous installation to the new installation and merge the parameter files from the previous installation to the new installation:

# cp /opt/{prev-inst}/sch0_license.dat /opt/{curr-inst}/sch0_license.dat # cp /opt/{prev-inst}/sch1_license.dat /opt/{curr-inst}/sch1_license.dat

Merge /opt/{previous-installation}/sch0_parameter.dat with /opt/{current-inst}/sch0_parameter.dat
Merge /opt/{previous-installation}/sch1_parameter.dat with /opt/{current-inst}/sch1_parameter.dat
Start the server:

# /schedule_library/schedule_start.ksh start 0 # /schedule_library/schedule_start.ksh start 1

Optional Step - After the installation is complete and if you choose to remove the previous installation, the following procedure will only delete programs and data files installed when you last installed SCHEDULE. Jobs or other data that you have added since the installation will NOT be deleted. They will continue to be present and accessible after you install the new version. You may choose to skip this step and save this as a previous version of SCHEDULE. The new and previous versions are installed in separate directories in /opt.

# swremove Schedule<previous version number>

(e.g. Schedule7214 to remove Schedule version 7.2.14)
To see which version of Schedule is installed:

# swlist

Complete the installation by re-loading standard objects (ISE adds in new standard items):

# /schedule_library/schedule_standard_loads.ksh

These corrections apply to the OpenVMS, Tru64 UNIX, Windows, HP-UX, Sun Solaris, AIX and Linux versions.

6.1 Version 7.3.12 Changes and additions

6.1.1 General Changes

• Two pass preprocessing - Two passes of preprocessing are now made, allowing for nested includes. In addtion, a job parameter can now be defined as a "schedule variable" and portions of a job parameter can be a "schedule date string" such that a file path in a job parameter can have a date expression in the name.
• Web Client Redesigned - The Web Client has been redesigned for easier navigation and access to scheduling features.
• Enhanced Online Customer Support - Customers and demo users may generate licenses 24/7 by logging into the ISE Registrar site (http://registrar.i-s-e.com) and filling in the easy to use form. Customers may also generate Disaster Recovery Licenses for servers that may have short term issues such as recently expired licenses or machine hardware changes. A record of all company license information may also be obtained for record keeping. In addition the ISE Support Site (support.i-s-e.com) is available for the latest downloads, patches, documentation and FAQs.
• Multiple attachments in UNIX e-mail notifications - Allows multiple attachments to email notifications on UNIX systems.
• New Specialized prototype jobs - Centricity, Cbis, Module for GE Medical Users. Banner module for college Financial Aid Users.
• Cross platform log file inclusion - Expands send_log to allow a job's log to be sent by a separate job on a remote system.
• Option to bypass job connection check - An option has been added to load layouts faster by not checking job dependencies.
• Enhanced VMS cluster lock sharing - For VMS cluster environments, enhanced cluster lock sharing for heavily loaded systems
• Throttle Controls added - New controls added to prevent very high process creation rates.
• Logging for manual job submission including remote connections - The user name of a remote or local manual job submission is now logged in the server log.

• Preprocessing Preview Button - Added preprocessing preview button to Command, Notes and Notify property pages. Allows of current values of preprocessing directives.
• "View previous log" submenu added - A new submenu has been added when right clicking on jobs in the explorer view and layout, with "one earlier", "two earlier" etc. to view previous version of the log file.
• No job check option added - New layout option "no job check" added to the "layout control" window to speed up the loading and display of large layouts.
• Change in the display of Initiate line for ANY - Initiates with the ANY condition in the layout are displayed so that they use only the first color defined in the layout options while initiates on SUCCESS/INFO use both colors. This helps to distinguish the two types of initiates. The default second color for initiates on SUCCESS has also been changed to green.
• Second level prototype submenu - Added second level submenus to the "Job from" prototypes menus.
• Preset set tag and parameter values - Adds the ability to preset the tag and parameter values for the submit and complete dialogs. The following values can be set in the notes/options page of the job, For submit: "submit_tagdata_value=" and "submit_parameter_value=", For complete: "complete_tagdata_value=" and "complete_parameter_value="
• Enable/disable job menu item - Enable/disable menu item added for jobs in the explorer view and layout.
• New monitor option "Retention for Failed P entries" Ability to set the time a Failed P queue entry remains in the monitor.
• New layout option "Highest set id per job" added in the layout controls Combines "highest set id" and "all job sets". Displays the highest set id for every job and not just the latest event for every job as it is the case of "All job sets". This changes the display when jobs with different ids run concurrently.
• Increase the max number of monitor job entries - The monitor view in the Windows Client can now display 20,000 entries.
• Failed jobs displayed in red in Explorer view Display failed jobs in the right pane of the explorer view in a different color (default red).