Open topic with navigation

ibi™ Open Data Hub for Mainframe Connectors 1.0.8

# Run isetup

Server installation consists of a series of ISPF panels, which gather the required information. After the panel dialog is complete, JCL is created and optionally submitted to install and configure the server.

1. Execute the isetup member of your high_level_qualifier.HOME.DATA using ISPF option 6.

   The first Installation and Configuration panel opens.

   Complete the panel as follows.

   Field | Instructions
   --- | ---
   Enter selection | Accept the default value 1, Install and Configure, for a new installation. For option 2, Add Additional Configuration Instance, see Adding a Configuration Instance for PDS.
   Installation Userid | Shows the current logon ID. It cannot be changed.
   PTH Administrator Userid | An ID is required to administer the server immediately after initial installation. This ID is defined and maintained solely in the realm of the server. It defaults to srvadmin, and it can be changed here. For more information about running the server in secure mode, see Configure Security.
   PTH Administrator Password | Password for the PTH Administrator ID. It cannot be left blank and must be matched at the Retype field.
   Customer ID | Enter the Customer ID that was provided to you with your WebFOCUS software.
   Enter Job Card information | To provide JOB card information for submitting jobs to the JES queue, provide a valid job name (a maximum of seven characters following the 2 forward slashes `//` on the first JCL line), which defaults to the user ID that you are currently using. This job name is used for multiple submissions (for example, jobnameA, jobnameB, jobnameC, and so on) in the JCL that is generated by the installation procedure.
   Override JOB name checking | To provide your own JOB card information, including JOB name, enter Y and provide valid JOB card information in the Enter Job Card information field. The JOB card information that you enter is used for each job that is submitted.

2. Press Enter to continue to the next panel.

   The following panel opens.

   In this and some later panels, you can see a field's default value (if one exists) by blanking out the field and pressing Enter. Complete the panel as follows.

   Field | Instructions
   --- | ---
   EDAHOME Libraries HLQ (EDAHOME) | Enter the same HLQ value you provided when you processed the .run file.
   EDACONF Libraries HLQ | EDAHOME libraries HLQ with additional qualifier .P.
   EDACONF Libraries Attributes Unit | Follow your site's rules. For most sites, Unit is SYSDA and Volume is left blank.
   HTTP Listener Port | This is the port number that the server uses for HTTP. It is the first of three connection ports that must be available to the server. For example, if you choose port 8101, then ports 8101, 8102, and 8103 are used by the server. Ensure that you choose ports that are not currently being used.
   TCP Listener Port | This is the port number of the TCP Listener. The default is one less than the port specified for the HTTP Listener, but it can be any port number other than the three reserved for HTTP.
   Installation JCL Library | Data set where installation JCL and other files are written.

3. Press Enter to continue to the next panel. The Data Adapters panel opens. It lists adapters that require the allocation of MVS libraries in IRUNJCL or environment variables in the EDAENV member. To select specific adapters:
   1. Type Y next to the required adapters and press Enter.
   2. Supply the requested information, which is described in Collect Required Information for Adapters.

      After you have finished installing and configuring the server, you can use the WebFOCUS Reporting Server browser interface to finish configuring these adapters, and to configure adapters that do not have MVS JCL requirements.

4. Press Enter to continue to the next panel.

   The JSCOM3 Listener configuration panel opens.

   1. This panel prompts for a value for JDK_HOME. For more information see Installation Requirements for PDS. It also prompts for values for `edahome_dir` and `edaconfi_dir`, as described in ZFS Home and Configuration Directory Requirements.

   2. Configuration of the JSCOM3 Listener is either optional or mandatory depending on which adapters were selected. If any Java-based adapters were selected (EJB, Call Java, JDBC, Microsoft SQL Server), the configuration of all three paths listed above is mandatory. If SAP-based adapters were selected (SAP or SAP BW), only `edahome_dir` and `edaconf_dir` are required.
   3. If no Java-based or SAP-based adapters were selected, this configuration might still be desirable to enable the server-side graphics feature. To skip the configuration, leave the path blank.

5. Press Enter to continue to the next panel.

   The Confirmation panel opens.

6. Ensure that all values on the Confirmation panel are correct, then select one of the following options
   - N to return to the initial panel so that you can change installation values.
   - C to create JCL which you can submit at a later time. The JCL is placed in your high_level_qualifier.PDS.WFS.DATA configuration library.
   - S to create JCL in high_level_qualifier.PDS.WFS.DATA, and submit the job immediately.

   where:

   high_level_qualifier

   Is the high-level qualifier to be used for all output libraries. This is the same high-level qualifier, which you specify during server installation.

7. As the job is processed, in SDSF, check JESLOG for errors and return codes.

The following is a table of the jobs created. All members are created in the configuration library.

Job | Description
--- | ---
ISETUPJ1 | Main JCL Job stream that is used to install the server.
ISOPTS1 | Options used to install.

All the following members call the IRUNJCL procedure, which is the main server JCL. If you need to change the server JCL, change member IRUNJCL.

Member | Description
--- | ---
ISTART | Starts the server.
ISAVEDIA | JCL to print a copy of configuration files for diagnostic purposes.
ITRCON | Starts the server with traces on.

The following members contain batch JCL for auxiliary functions, and are created in the configuration library.

Member | Description
--- | ---
CMRUN | JCL to run ibi Data Migrator batch jobs.
DB2VverPR | Db2 DBRM, where ver is your supported version of Db2 referenced in GENDB2 JCL.
GENDB2 | JCL to bind the Db2/CAF plan.
IRDAAPPC | Example CLIST to run RDAAPP Client test tool.
IRDAAPPJ | Example JCL to run RDAAPP Client test tool.

The following members contain sample started task JCL, and are created in the configuration library.

Member | Description
--- | ---
IWAYS | A started task that starts the server.
EDAENV | A parameter file used by the server. It contains all required environment variables.

# Overview of Manual Steps Following isetup

The following features are not installed by isetup. For these features, follow the instructions in the WebFOCUS Reporting Server Installation Guide for your current production version of WebFOCUS Reporting Server:

- Data Adapters (Interfaces, for example, Db2 or ADABAS).
  Important: All data adapter files are included and allocated in WebFOCUS Reporting Server after you run ISETUP. However, using the instructions in the relevant Installation Guides for those data adapters, you must reinstall every data adapter to which you want to have access in the installed version of WebFOCUS Reporting Server.

If you run WebFOCUS Reporting Server out of LPA libraries, perform the following steps:

1. Copy all the reentrant modules back into FOCLIB.LOAD from FOCLPA.LOAD. (Use JOB JFSCPBCK.)
2. Run isetup.
3. Copy the reentrant modules from FOCLIB.LOAD back into FOCLPA.LOAD. (Repeat JOB JFSCPLPA.)
4. Delete the reentrant modules FROM FOCLIB.LOAD. (Repeat JOB JFSDELPA.)

# ISETUP Processing Flow

The installation job should complete with 0 return codes for all steps, and additional libraries should be created under the high-level qualifier you entered on the ISETUP screen.

The following physical HOME libraries should exist.

    SYSADMIN1.P.HOME.BIN                                 USERM1
    SYSADMIN1.P.HOME.FEX                                 USERM1
    SYSADMIN1.P.HOME.ACX                                 USERM1
    SYSADMIN1.P.HOME.LOAD                                USERM1
    SYSADMIN1.P.HOME.ERR                                 USERM1
    SYSADMIN1.P.HOME.ETC                                 USERM1
    SYSADMIN1.P.HOME.DATA                                USERM1
    SYSADMIN1.P.HOME.MAS                                 USERM1
    SYSADMIN1.P.HOME.CICS.LOAD                           USERM1

The following physical CONF libraries should exist.

    SYSADMIN1.CONF.ACX                                   USERM1
    SYSADMIN1.CONF.CFG                                   USERM1
    SYSADMIN1.CONF.DATA                                  USERM1
    SYSADMIN1.CONF.SQL                                   USERM1
    SYSADMIN1.CONF.MAS                                   USERM1
    SYSADMIN1.CONF.PRF                                   USERM1

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

ibi™ Open Data Hub for Mainframe Connectors

Copyright © 2021-2025. Cloud Software Group, Inc. All Rights Reserved.