Installing ibi FOCUS with FOCUS Studio

ibi™ FOCUS® and FOCUS Studio are installed by going to the eDelivery site, downloading the specific .run file to a USS directory, and then using the sh command to execute the .run file.

By selecting your product, version, and operating system, and accepting the EULA agreement, you may select to download the full product or individual files. If you choose individual files, you must then open the FOCUS® Software folder, select an IBI_focus_*_mvs_zseries.run file, where * indicates the release number, and start the download. The IBI_focus_*_mvs_zseries.run file is a self-extracting .run archive format file.

Once the desired .run file is downloaded and transferred to the actual machine where the installation will occur and into a temporary USS working directory, execute the .run file.

More specifically, change directory (cd) to the temporary directory and issue the following command, where the actual .run file name is the full file name that was downloaded.

sh IBI_focus_*_mvs_zseries.run 

During the execution of the .run file, you will be required to supply a high-level-qualifier (HLQ) string using a command line parameter or in response to a prompt. The default HLQ is the running user-id. Execution of the .run file will test whether existing libraries will be overwritten, and if so, it will prompt whether to proceed or quit. Successful execution of the .run file will create eight PDSE libraries starting with hlq.F.HOME.

The extracted files will be included in a temporary subdirectory of the current directory. After successful execution of the .run file, you need to run ISETUP from the hlq.HOME.DATA library in zOS. You must use the ISETUP procedure in order to install or apply maintenance to FOCUS.

Install FOCUS with FOCUS Studio

Procedure
1. Change directory (cd) to the temporary USS directory where the installation will occur.
2. Issue the following command, where the actual .run file name is the full file name that was downloaded. For example:

   sh IBI_focus_9.3.0_mvs_zseries.run 

   The following prompt appears:

   Enter datasets HLQ prefix:

3. Type your HLQ, for example:

   PMSSAE.MVS1.DF9999

   • If the datasets already exist, you will receive the following messages, along with a prompt asking whether you want to proceed:

     Installation datasets prefixed with PMSSAE.MVS1.DF9999 already exist. 
     They will be deleted and re-created.
     Do you want to proceed (Y/N)? 

     If you type Y to preceed, you will receive the following messages that all the temporary datasets are allocated and restored successfully:

     ALL TEMPORARY DATASETS ARE ALLOCATED SUCCESSFULLY -> PROCESSING
     ALL DATASETS ARE RESTORED SUCCESSFULLY

   • If the datasets do not already exist, the datasets will be allocated and you will receive a message that the datasets were allocated successfully.

sh IBI_focus_9.3.0_mvs_zseries.run
Enter datasets HLQ prefix: PMSSAE.MVS1.DF9999
Installation datasets prefixed with PMSSAE.MVS1.DF9999 already exist. 
They will be deleted and re-created.
Do you want to proceed (Y/N)? Y
13.33.11 STC47294  +IKJ56228I DATA SET PMSSAE.MVS1.DF9999.P.HOME.BIN NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
13.33.11 STC47294  +IKJ56228I DATA SET PMSSAE.MVS1.DF9999.P.HOME.ACX NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
13.33.11 STC47294  +IKJ56228I DATA SET PMSSAE.MVS1.DF9999.P.HOME.FEX NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
13.33.11 STC47294  +IKJ56228I DATA SET PMSSAE.MVS1.DF9999.P.HOME.MAS NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
13.33.11 STC47294  +IKJ56228I DATA SET PMSSAE.MVS1.DF9999.P.HOME.ERR NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
13.33.11 STC47294  +IKJ56228I DATA SET PMSSAE.MVS1.DF9999.P.HOME.LOAD NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
13.33.11 STC47294  +IKJ56228I DATA SET PMSSAE.MVS1.DF9999.P.HOME.DATA NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
13.33.11 STC47294  +IKJ56228I DATA SET PMSSAE.MVS1.DF9999.P.HOME.ETC NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
ALL TEMPORARY DATASETS ARE ALLOCATED SUCCESSFULLY -> PROCESSING
ALL DATASETS ARE RESTORED SUCCESSFULLY