# /schedule_library/schedule_standard_loads.ksh

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

4.1 Setting up the License PAS

Before SCHEDULE for Linux 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.

4.2 Obtaining the installation file

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

There are two methods for obtaining the software:

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

4.2.1 Obtaining the .rpm file using the ISE Support Site

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

Download SCHEDULE7312.rpm to a local temporary directory on your Linux machine.

4.2.2 Obtaining the .rpm 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_linux_x86 ftp> bin ftp> get SCHEDULE7312.rpm

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

4.2.3 Copy the .rpm file from the CD

Follow the steps below to use swinstall to copy EnterpriseSCHEDULE from the CD:

1. Log in as root.
2. Insert the software media into the appropriate drive.
3. Copy /linux-intel/schedule/kit/SCHEDULE7312.rpm from the cd to a local temporary directory on your Linux machine.

4.3 Installing the rpm

1. Unzip the rpm file using the following command:
   

   # gunzip schedule7312.rpm.gz

2. This section explains the installation options of the rpm utility. rpm will install all EnterpriseSCHEDULE files under /usr/local in the /ise/schedule subdirectory.
   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:

   # 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)

3. Load the PAS number

   # vi /schedule_library/sch0_license.dat

4. Start the Schedule Server (on reboot this is automatic)

   # /schedule_library/schedule_start.ksh bootall

5. Complete the installation by loading standard objects:

   # /schedule_library/schedule_standard_loads.ksh

   
   

   Note If this is a new install you are done.

6. Shutdown any running SCHEDULE servers by using the following commands:

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

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

8. 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
9. Start the server:

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

10. 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)

11. To see which version of Schedule is installed:

    # swlist

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

    # /schedule_library/schedule_standard_loads.ksh

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 Tru64 UNIX software meets SCHEDULE for UNIX hardware, software, and disk space requirements
• Do you have the Product Authorization Serial(PAS) in order to register the software with the License Management Facility(LMF)
• Which optional SCHEDULE for Tru64 UNIX subsets you should install
• How much disk space you will need
• Whether you have to back up your system disk

The SCHEDULE for Tru64 UNIX distribution kit includes hardcopy release notes. Compaq strongly recommends that you read the release notes before using the product.

5.2 Installation Procedure Requirements

This section discusses various requirements for installing SCHEDULE for Tru64 UNIX software.

5.2.1 Checking Login Privileges

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

5.2.2 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.
• Terminal
  You can use a terminal to communicate with the operating system and respond to prompts from the installation procedure for SCHEDULE for Tru64 UNIX software.

SCHEDULE for Tru64 UNIX software requires Tru64 UNIX V3.2g or V4.0b to be installed. In addition, SCHEDULE for Tru64 UNIX software requires the following Tru64 UNIX software subsets to be loaded on the system on which you install SCHEDULE for Tru64 UNIX software:

• OSFBASE
• OSFINET

To install the optional SCHEDULE for Tru64 UNIX reference pages (manual pages), the Tru64 UNIX software subset OSFMANO must be installed on the system on which you install SCHEDULE for Tru64 UNIX software:

If you are installing SCHEDULE for Tru64 UNIX software in a local (node-specific) environment, perform the following steps to determine whether the preceding Tru64 UNIX subsets are loaded:

1. Log in to the system on which you plan to install SCHEDULE for Tru64 UNIX software.
2. Enter the following commands:

   # set1d -i | grep BASE # set1d -i | grep INET # set1d -i | grep MANOS

The version number associated with these subsets must be 410 or higher.

Check the displayed rows for the relevant subset name and for any related patch names. The word installed appears in a row after the subset identifier code when a subset is loaded. If the word installed does not appear (the second column in a row is blank), software before installing SCHEDULE for Tru64 UNIX software.

5.2.4 Determining Which Subsets to Load

You must choose the SCHEDULE for Tru64 UNIX subsets you want to load. Table 5-1 lists the product subsets.

Table 5-1 Determing Subsets to load

Subset	Name	Description
SCHA721	Core Files	Directory tree info
SCHAPR0721	Group 0 executable images	Image for Group 0 users
SCHBPR1721	Group 1 executable images	Image for Group 1 users
SCHADB0721	Group 0 initial database	Database for Group 0 users
SCHBDB1721	Group 1 initial database	Database for Group 1 users

5.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 Tru64 UNIX subsets.

Table 5-2 lists the disk space requirements for loading SCHEDULE for Tru64 UNIX software subsets. 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 5-2 Disk Space Requirements

Subset Name	Subset Title	Kilobytes
SCHA721	Core Files	800
SCHAPR0721	Group 0 executable images	1300
SCHBPR1721	Group 1 executable images	1300
SCHADB0721	Group 0 initial database	120
SCHBDB1721	Group 1 initial database	120

Using the disk space requirements listed in Table 5-2 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 Tru64 UNIX 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 Tru64 UNIX software and check the amount of space available in the /usr/opt directory using the Tru64 UNIX 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 5-2.