home *** CD-ROM | disk | FTP | other *** search
-
- ΓòÉΓòÉΓòÉ 1. Using Command Line Parameters ΓòÉΓòÉΓòÉ
-
- The user can enter the parameters at the command prompt following the
- INSTALL.EXE, the EPFIDLDS.EXE or the EPFINSTS.EXE file. The information passed
- as values of these parameters is used by EPFINSTS.EXE during installation
- processing.
-
- You should document how to use these parameters if your users install your
- product differently from what you specified in your IIRC.RC resource file. Or,
- you can supply a command file to the user with the necessary parameters.
-
- If no parameters are specified when the executable file is started, the
- installation is attended. To install in an unattended mode, the /X parameter
- must be used. Unattended includes what is sometimes referred to as lightly
- attended. In the lightly attended mode, someone might have to start an
- executable file or insert diskettes.
-
- If the value of any of the parameters contains spaces, use double quotes to
- enclose the value.
-
- Values can be upper or lower case. Parameters can be in any order.
-
- <command> /A:<action>
- /C:<catalog file name>
- /G:<include path>
- /L:<xpos,ypos>
- /L1:<error log>
- /L2:<history log>
- /L3:<log file>
- /L4:<log file>
- /L5:<log file>
- /NMSG
- /O:<originating system>
- /P:<product name>
- /R:<response file>
- /S:<source location>
- /T:<install target directory>
- /TU:<update CONFIG.SYS directory>
- /X <interactive_flag>
-
- The /A, /C, and /P parameters are required for an installation that is started
- with the EPFINSTS command. If the action is an install or an update, the /O is
- also required. The /A, /C, /L, /O, /P, /R, and /S parameters override values
- you have set in the IIRC.RC.
-
- Note: The drive/directory/filename path is required for all log parameters
- specified with the INSTALL.EXE or EPFIDLDS.EXE commands. The directories for L1
- and L2 log files will be created if they do not exist. The directories for all
- other log files must exist before starting the commands.
-
-
- ΓòÉΓòÉΓòÉ 2. Parameter Definitions ΓòÉΓòÉΓòÉ
-
- The command prompt parameters are:
-
- /A:<action>
- Specifies the action of the EPFINSTS.EXE.
-
- If you use this parameter, the main window of the installation is not
- displayed.
-
- If you do not use this parameter, the installation starts normally with all
- windows displayed.
-
- Valid values for this parameter are:
-
- 'D' For delete
- 'I' For install
- 'R' For restore
- 'U' For update
-
- Software Installer sets the EPFIACTION installation variable to the action.
-
- /C:<catalog file name>
- Specifies the name and location of the catalog file that you want to be
- opened automatically.
-
- If the catalog file is located on a host session, the host session ID must
- precede the catalog file name. If the catalog file is located on a drive, a
- drive and directory must precede the catalog file name.
-
- Software Installer sets the EPFICATALOG installation variable to the name of
- the catalog file.
-
- The following examples show how to use this parameter for each installation
- source.
-
- o For Drive: /C:A:\DISK1.ICF
- o For MVS: /C:B:EPF.V1R2M0.SEPFBENU(EPFICAT)
- o For VM: /C:"B:EPFICAT ENUEPF12 *"
- o For VSE: /C:B:LIB.SUBLIB.MEMBERNAME.MEMBERTYPE
-
- If only the host session ID is specified, for example, B: then the Open
- catalog window is displayed with B: as the default session or drive.
-
- /G:<include path>
- Specifies the drive and directory of the general response files that are
- included by the specific response file.
-
- Software Installer sets the EPFIGENRESPDIR installation variable to the
- included path.
-
- Example:
-
- /G:L:\XYZ
-
- /L:<xpos,ypos>
- Specifies the initial horizontal and vertical coordinates of the initial
- installation window on the Workplace Shell* relative to the lower-left
- corner of the screen.
-
- If this parameter is specified, all previously saved default positions are
- overridden.
-
- Software Installer sets the EPFIWNDCOORDS installation variable to the
- coordinates of the Installation and Maintenance window.
-
- /L1:<error log>
- Specifies the drive, path, and file name of the error log file.
-
- Software Installer sets the EPFIERRORLOG installation variable to the name
- of the error log.
-
- Note: The drive/directory/filename path is required. The directory for the
- log file must already exist.
-
- All lines logged to the error file are prefixed with a time stamp. The time
- stamp has the following format:
-
- YYYY-MM-DD HH:mm:SS:cc
- Where:
-
- YYYY is the year.
- MM is the month.
- DD is the day.
- HH is the hour.
- mm is the minute.
- SS is the second.
- cc is the hundredth of a second.
-
- The date and time separators are the current user-defined settings in the
- Country object of the System Settings folder. The default separators are the
- hyphen and the colon, respectively.
-
- Example of using the /L1 parameter to create ERROR.LOG file in the C:\ABC\
- directory:
-
- /L1:C:\ABC\ERROR.LOG
-
- /L2:<history log>
- Specifies the drive, path, and file name of the history log file. Software
- Installer sets the EPFIHISTORYLOG installation variable to the name of the
- history log.
-
- Note: The drive/directory/filename path is required. The directory for the
- log file must already exist.
-
- If this parameter is not specified, no history log is maintained.
-
- All lines logged to the history file are prefixed with a time stamp. The
- time stamp has the following format:
-
- YYYY-MM-DD HH:mm:SS:cc
- Where:
-
- YYYY is the year.
- MM is the month.
- DD is the day.
- HH is the hour.
- mm is the minute.
- SS is the second.
- cc is the hundredth of a second.
-
- The date and time separators are the current user-defined settings in the
- Country object of the System Settings folder. The default separators are the
- hyphen and the colon, respectively.
-
- Example of using the /L2 parameter to create HISTORY.LOG file in the C:\ABC\
- directory:
-
- /L2:C:\ABC\HISTORY.LOG
-
- /L3: /L4: /L5:<log files>
- Each of these parameters specifies a drive, path, and file name of a log
- file. They are saved in installation variables EPFIL3LOG, EPFIL4LOG, and
- EPFIL5LOG for your use.
-
- Note: The drive/directory/filename path is required. The directories for
- the log files must already exist.
-
- /NMSG
- Specifies that the ending message will not be displayed.
-
- /O:<originating system>
- Specifies the originating system of the installation. Valid values are:
-
- o DRIVE
- o MVS
- o VM
- o VSE
-
- Software Installer sets the EPFISOURCE installation variable to one of these
- values.
-
- /P:<product name>
- Provides the name of the product for the specified action.
-
- If you do not use this parameter, the installation comes up normally with
- all windows displayed.
-
- The <product name> should match the value of the NAME keyword of the PACKAGE
- entry in the catalog file. If your product name string includes any spaces,
- use double quotes around the string. For example:
-
- /p:"product name with spaces"
-
- Software Installer sets the EPFIPRODUCT installation variable to the name of
- the product.
-
- /R:<response file>
- Specifies the drive, path, and file name of the specific response file.
-
- The following search order is used to find the response files.
-
- 1. The fully-qualified file specification
- 2. The current directory. The current directory is the temporary directory
- where epfinsts.exe is running. The response file can be placed in the
- current directory by packing it in INSTALL.IN_.
- 3. The file name together with the /G: invocation parameter
- 4. Each directory in the PATH environment variable
- 5. Each directory in the DPATH environment variable
-
- Software Installer sets the EPFIRESPFILE installation variable to the
- response file.
-
- Example:
-
- /R:L:\XYZ\RESPONSE.DAT
-
- /S:<source_location>
- Specifies the drive and path that contains the source files to install.
-
- Software Installer sets the EPFISOURCEDIR installation variable to the
- source_location.
-
- Specifying this parameter overrides the value of the HOSTLOC keyword in the
- product's catalog file PACKAGE entry.
-
- If this parameter is not specified, the value of the HOSTLOC keyword is not
- overridden.
-
- Example:
-
- /S:L:\XYZ
-
- /T:<install target directory>
- Specifies the drive and path where the product files are installed.
-
- This parameter only affects the value of the FILE directory (directory
- corresponding to the FILELABEL keyword). If this parameter is specified, it
- overrides the FILE paths that are specified in the response files and the
- package files.
-
- Software Installer sets the EPFITARGETDIR installation variable to the
- install target directory.
-
- Example:
-
- /T:C:\IBB
-
- /TU:<update target CONFIG.SYS directory>
- Specifies the drive and path of the target CONFIG.SYS to be updated.
-
- Software Installer sets the EPFITARGETCNF installation variable to the
- update CONFIG.SYS target directory.
-
- If this parameter is not specified, the CONFIG.SYS files are updated as
- specified in the product's package file.
-
- Example:
-
- /TU:C:\
-
- /X
- Specifies that the action is unattended.
-
- If you do not specify all of the information needed for the action to
- complete, an error occurs. When you specify the /X option, no progress
- indication is shown and all error messages are logged to the error file you
- specified using the /L1 parameter.
-
- If you do not specify this option, the user is prompted for any information
- that the EPFINSTS.EXE needs to complete the action. In this attended mode of
- action, progress indication is shown and error messages are displayed to the
- user in secondary windows.
-
- Software Installer sets the EPFINONINTERACT installation variable to YES if
- the /X parameter is specified.
-