EnterpriseSCHEDULE
Installation Notes

Chapter 2
Installing EnterpriseSCHEDULE for Solaris

Before starting the installation procedures described in Section 5.6, you should complete the preparation requirements outlined in this chapter. It provides the information necessary to make your installation run smoothly, including your installation options. Read this chapter to determine the following:

Whether you need to read the Release Notes
Whether you need superuser privileges for the system on which you will be installing SCHEDULE software
If the system on which you will install SCHEDULE for Sun Solaris software meets SCHEDULE for Sun Solaris hardware, software, and disk space requirements
How much disk space you will need
Whether you have to back up your system disk

2.1 Release Notes

The SCHEDULE for Sun Solaris distribution kit includes hardcopy release notes. ISE strongly recommends that you read the release notes before using the product.

2.2 Installation Procedure Requirements

This section discusses various requirements for installing EnterpriseSCHEDULE for Sun Solaris software.

2.2.1 Time required for Installation

EnterpriseSCHEDULE for Sun Solaris takes approximately 10-15 minutes to install.

2.2.2 Checking Login Privileges

You must be able to log in as superuser on the system on which you are installing EnterpriseSCHEDULE for Sun Solaris software. Only when you are logged in as superuser, do you have sufficient privileges to install the EnterpriseSCHEDULE for Sun Solaris software.

2.2.3 Hardware Requirements

To perform the installation, you need the following hardware:

Software distribution device (if installing from media)
You need a distribution device that corresponds with the software distribution media. You must know how to load the media supplied with the software distribution kit on the appropriate drive. The documentation for the tape or disk drive that you are using explains how to load media.

2.2.4 Software Requirements

The following are the requirements for EnterpriseSCHEDULE for Sun Solaris:

2.2.4.1 Operating System

The following Operating System is required to be installed:

SunOS 5.8
Sun Solaris 8 or greater

2.2.5 Determining Disk Space Requirements

The disk space requirements discussed in this section apply to the disks on which you load the SCHEDULE for Sun Solaris subsets.

Table 2-1 lists the disk space requirements for loading SCHEDULE for Sun Solaris software. This table specifies disk space requirements for the convenience of those doing installations on systems on which these file systems are mount points for different disk partitions.

Table 2-1 Disk Space Requirements
Name Description Kilobytes

catalogs Catalog files 64

control0 Control files - Group 0 141

dat Data files 438

executables Executable files 7294

man Man pages 248

scripts Script files 606

**Table 2-1 Disk Space Requirements**
Name	Description	Kilobytes
catalogs	Catalog files	64
control0	Control files - Group 0	141
dat	Data files	438
executables	Executable files	7294
man	Man pages	248
scripts	Script files	606

Using the disk space requirements listed in Table 2-1 for an system that applies to your system, total the values for the subsets that you plan to load in each file system.

Compare the space required for subsets with the free space currently on the disks on which SCHEDULE for Sun Solaris files will reside.

To determine the current amount of free space for a directory path, log in to the system on which you plan to install SCHEDULE for Sun Solaris software and check the amount of space available in the /usr/opt directory using the Sun Solaris df utility:

#df -k /usr/opt File system Total kbytes kbytes % node kbytes used free used Mounted on /dev/rd0g 122598 544478 55892 49% /user

The previous display indicated that 55892 Kb are free. This free space must accommodate subset requirements listed in Table 2-1.

2.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 Sun Solaris documentation.

2.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.

2.5 Installing SCHEDULE for Solaris

This chapter describes the procedures for installing SCHEDULE for Solaris software.

This section describes the methods for obtaining the .rpm file required to install EnterpriseSCHEDULE for Solaris.

The methods for obtaining the software:

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

2.5.1 Obtaining the installation file using the ISE Support Site

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/sun/

There is a direct link on the page to the latest version of the software for both the x86 and SPARC version of the install file. This example assumes the file has been downloaded to the /tmp directory

2.5.2 Obtaing the installation file using the ISE FTP Site

The ISE FTP Site has a directory containing latest version of the install file for EntepriseSCHEDULE. To download the file:

# ftp ftp.i-s-e.com ftp> cd latest_sun_x86 (for x86 Solaris) or ftp> cd latest_sun_sparc (SPARC Solaris) or ftp> cd latest_sun_amd (AMD) ftp> bin ftp> get sch7312.gz

2.5.3 Copy the install file from the CD

Follow the steps below to copy EnterpriseSCHEDULE from the CD:

Log in as root.
Insert the software media into the appropriate drive.
Mount the drive.
Copy /solaris/schedule/kit/sch7312.gz from the cd to a local temporary directory on your Solaris machine.

2.5.4 Performing the installation

Once the file has been FTP'd or downloaded perform the unzip and install procedure from the install directory:

To unzip the install file
# gunzip sch7312.gz
To run the install:
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:
# /usr/sbin/pkgadd -d /tmp/sch7312
This example assumes the file has been downloaded to the /tmp directory
Select Schedule7312 from the installation prompt. This command will create the subdirectory /usr/local/ise/schedule and install the SCHEDULE files there. For advanced installation options, view your man pages.

Note
If this is an upgrade, skip to step 6. Otherwise, load the PAS license 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-installation}/sch0_parameter.dat
Merge /opt/{previous-installation}/sch1_parameter.dat with /opt/{current-installation}/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

Chapter 3
Installing EnterpriseSCHEDULE for AIX

This chapter describes the procedures for installing EnterpriseSCHEDULE for AIX running on a PowerPC.

3.1 Setting up the License PAS

Before EnterpriseSCHEDULE will run on your system, you must set up the product license. This can be accomplished by adding the appropriate entry to the /schedule_library/sch0_license.dat file after your SCHEDULE installation.

3.2 Obtaining the installation file

This section describes the three methods of obtaining the .rpm file required to install EnterpriseSCHEDULE for Solaris.

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

3.2.1 Obtaining the .rpm.gz file using the ISE Support Site

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/aix/

Download schedule7312.rpm.gz to a local temporary directory on your AIX machine.

3.2.2 Obtaining the .rpm.gz file using the ISE FTP Site

The ISE FTP Site has a directory containing latest version of the install file for EntepriseSCHEDULE. To download the file:

# ftp ftp.i-s-e.com ftp> cd latest_aix ftp> bin ftp> get schedule7312.rpm.gz

Download schedule7312.rpm.gz to a local temporary directory on your AIX machine.

3.2.3 Copy the .rpm.gz file from the CD

Follow the steps below to copy EnterpriseSCHEDULE from the CD:

Log in as root.
Insert the software media into the appropriate drive.
Mount the drive.
Copy /aix/schedule/kit/schedule7312.rpm.gz from the cd to a local temporary directory on your AIX machine.

3.3 Installing the RPM

This section explains the installation options of the RPM utility. RPM will install all EnterpriseSCHEDULE files under /usr/local in the /ise/schedule subdirectory. The most simple installation command would be:

Unzip the rpm file using the following command:
# gunzip schedule7312.rpm.gz
Install the rpm
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:
# rpm --install schedule7312.rpm
This will install all files in the default location (/usr/local/ise/schedule). RPM supports several command line options that will alter this default installation behavior. The following options for SCHEDULE installation are summarized here:
excludedocs
This option will exclude all documentation from the installation. Documentation includes man pages, HTML files, Postscript files, and PDF help files.
Example:
# rpm --install --excludedocs schedule7312.rpm
prefix (path)
This option will change the directory prefix where the schedule files are installed. The default prefix is "/opt/ISESCH7312". The following example loads SCHEDULE to "/opt/ISESCH7312".
Example:
# rpm --install --prefix /opt schedule7312.rpm -hv
These options together provide a verbose installation
Example:
# rpm --install -hv schedule7312.rpm
ignoresize
This option tells rpm not to check the mount file system for sufficent disk space before installing the package
Example:
# rpm --install --ignoresize schedule7312.rpm
test
This option tells rpm to simply check for and report potential conflicts without actually installing the package.
Example:
# rpm --install --test schedule7312.rpm
Installing the package
Example:
# rpm --install --ignoresize schedule7312.rpm
test
This option tells rpm to simply check for and report potential conflicts without actually installing the package.
Example:
# rpm --install --test schedule7312.rpm
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