PDS Deployment

In this section:

 

The topics in this section describe how to install your server in a partitioned data set (PDS) environment.


Top of page

x
Installation Requirements for PDS

In this section:

Before beginning server installation, review all requirements.



x
Operating System Requirements

The server runs on any supported release of z/OS. For current information about supported releases:

  1. Go to http://techsupport.informationbuilders.com.

    The Information Builders Technical Support home page opens.

  2. In the Quick Links section on the right side of the page, click Supported Systems/Adapters.

    The Supported Systems and Adapters page opens.

  3. Click the link for the server release you want.

    The Supported Systems and Adapters page for that release opens.

  4. Click the link for your platform.

    The support chart for that platform opens.

In general, the operating system should have the latest cumulative patch levels applied.

Confirm that your server installation software is labeled for your operating system level.



x
JVM Requirements for Java Services

If JVM-based adapters, server-side graphics, XBRL, or user-written CALLJAVA applications are to be used, a Java Runtime Environment (JRE) JVM must be installed on the machine, and the server must be configured to use it

As of 7.7.05 and 8.0.01 production releases, the minimum JVM release level is 1.6 or higher, due to required internal components of the server. The Java Listener will not start unless 1.6 (or higher) is in use. Prior 7.x releases would allow the listener to start with any release, and sub-components would fail if they required a higher Java Level. The primary reason for this change is that Java 1.5 (and prior releases) are past their End of Service Life (EOSL) dates, and, as such, are unsupportable, in addition to lacking newer functionality. The following URL has Java EOL and EOSL information:

http://java.sun.com/products/archive/eol.policy.html

Installing maintenance updates to the EDAHOME of an existing server running releases prior to production 7.7.05 will also have the requirement of moving up all dependent configurations to use Java 1.6 (as instructed in this section).

You may install a Java JRE or a Java SDK. When you install a Java SDK, the JRE component (where the JVM lives) is included, so either is allowed. If using servlet, the Java SDK is required for the jar command, so it is generally preferred over the Java JRE. The SDK or JRE build type must also match the 32-bit or 64-bit bit type of the server. If an appropriate JVM from a JRE or SDK is not found on the library path or using variables as described below, or is not the appropriate bit type, a Failed to find JVM message will be displayed. Debugging information will be written to the start log indicating a failed JSCOM3 service.

The JDK JRE bin and server (or client) subdirectories must be specified in the load library path environment variable. A server restart is required, plus the appropriate JVM must be on the path if switching JRE levels. The load library path will be prompted at install time if JVM-based adapters or features are required. Otherwise, it can be manually set by editing the EDAENV file using any of the following methods.

To change or add operating system environment variables, set and export the variable in a .profile or script that always gets called during a server start. It is very common to place variables in the server edastart script, but it is recommended that they be placed in a script that in turn calls edastart (so that the edastart script remains vanilla).

To change or add a variable in a server environment start up file (EDACONF bin\edaenv.cfg), either edit the filein a text editor before starting the server or:

  1. Start the server (services like Java Listener may fail until configured and the server is restarted).
  2. Open the Web Console and login using an administrator ID.
  3. Select Workspace from the main menu.
  4. In the navigation pane, open the Configuration Files and Miscellaneous folders.
  5. Right-click Environment - edaenv.cfg and select Edit.
  6. Make the desired edit.
  7. Save the file.
  8. Restart the server (changes are not effective until server is restarted).

The format of edaenv.cfg variables is one per line in name=value pairs. Spaces before and after the equal sign are optional. Values with embedded spaces do not require quoting. Variables are always upper case.

If JVM-based adapters or features are not required, the message Failed to find JVM is normal and can be ignored.

To add classes to the JVM class path for customer-written CALLJAVA applications, set and export the CLASSPATH variable to the operating system level before server start-up or use the Web Console to set the Java Listener IBI_CLASSPATH property.



x
IP Port Number Requirements

The install process prompts for two IP port numbers: the TCP Listener and HTTP Listener. It also uses the next two consecutive ports after the supplied HTTP Listener port for FDS use. This results in a total of four IP ports.

The supplied IP port numbers must be above the IANA registered well-known reserve range (numbers under 1024) and not over the maximum legal number (65535). Do not use IP port numbers already used by other applications or products. Netstat, or netstat like commands, should reveal what actual ports are in use.



x
Browser Requirements

The Web Console server requires one of the following web browsers:

The Opera™ browser does not support RIA (Rich Internet Application), the default appearance mode of the 7.7.x Web Console. Opera 5.0 or higher seems to operate properly in HTML mode, and the Web Console detects this and switches to this mode automatically. Since HTML mode is less extensively tested, Opera is considered unofficially supported at this time. Please report any issues you find to customer service.



x
Disk Space Requirements

The server disk space requirements are:

Supplied (EDAHOME) Data Sets

3390 Cylinders

high_level_qualifier.P.HOME.ACX

2

high_level_qualifier.P.HOME.BIN

250

high_level_qualifier.P.HOME.CICS.LOAD

10

high_level_qualifier.P.HOME.ERR

100

high_level_qualifier.P.HOME.ETC

70

high_level_qualifier.P.HOME.FEX

25

high_level_qualifier.P.HOME.LOAD

400

high_level_qualifier.P.HOME.MAS

3

Configuration (EDACONF) Data Sets

3390 Cylinders

high_level_qualifier.server_type.CONF.ACX

2

high_level_qualifier.server_type.CONF.CFG

2

high_level_qualifier.server_type.CONF.MAS

2

high_level_qualifier.server_type.CONF.PRF

2

Installation Data Sets

3390 Cylinders

high_level_qualifier.HOME.DATA

5

high_level_qualifier.server_type.DATA

2

Application Data Sets

3390 Cylinders

approot.IBISAMP.type.DATA

38 (across 14 data sets)

approot.BASEAPP.type.DATA

56 (14 data sets using 4 cylinders per file)

Deferred Execution Data Sets (Optional)

3390 Cylinders

high_level_qualifier.server_type.CONF.DFM.DEL

5

high_level_qualifier.server_type.CONF.DFM.REQ

5

high_level_qualifier.server_type.CONF.DFM.RPE

5

high_level_qualifier.server_type.CONF.DFM.RPF

5

high_level_qualifier.server_type.CONF.DFM.RPI

5

high_level_qualifier.server_type.CONF.DFM.RQD

5

high_level_qualifier.server_type.CONF.DFM.RQF

5

high_level_qualifier.server_type.CONF.DFM.RQP

5

high_level_qualifier.server_type.CONF.DFM.RSP

20

Note: Deferred Execution Datasets are not created by the install procedure. They are created when the Scheduler/Deferred service starts. By default, the Scheduler/Deferred service auto starts at server startup. To disable the feature, enter dfm_autostart = n in the EDASERVE administration control file.

Supplementary Data Sets

3390 Cylinders

high_level_qualifier.server_type.SYSRPC.FOCUS

1

high_level_qualifier.server_type.ETLLOG.FOCUS (DataMigrator configurations only)

1

high_level_qualifier.server_type.ETLSTATS.FOCUS (DataMigrator configurations only)

1

high_level_qualifier.server_type.CONF.SMARTLIB.DATA

1

Sample Files

3390 Cylinders

approot.IBISAMP.CAR.FOCUS

1

approot.IBISAMP.EMPLOYEE.FOCUS

1

approot.IBISAMP.EDUCFILE.FOCUS

1

approot.IBISAMP.JOBFILE.FOCUS

1

where:

high_level_qualifier

Is the high-level qualifier to be used for all output libraries. You specify the high-level qualifier during server installation, as described in Step 4. Run ISETUP, in Step 4.

server_type

Is one of the following:

FFS

for a Full-Function Server

DM

for a DataMigrator Server

WFS

for a WebFOCUS Reporting Server

WFM

for a Shared Application Server for WebFOCUS Maintain

approot

Is the default location for storing applications. You specify approot during server installation, as described in Step 4. Run ISETUP,



x
Memory Requirements

Memory usage of a configured environment consists of the following elements:

Actual memory usage depends on application features, and varies depending on the application. The SHRLIBRGNSIZE parameter (defined on SYS1.PARMLIB, member BPXPRMxx) can affect the amount of memory that the server address space will allocate. For SHRLIBRGNSIZE, we recommend the default MVS installation value of 64Mb:

SHRLIBRGNSIZE(67108864)

Server memory usage:

The minimum amount of memory for a newly installed server with no workload is 250Mb. However, depending on usage, workload, and configuration options, 500Mb is recommended to start, to be adjusted as needed.



x
Communication Requirements

You need four TCP/IP ports for each server instance that you configure. Three of these ports must be consecutive. You specify these port numbers during installation. You may require additional ports depending on which options you configure later.

The server supports only IBM TCP/IP. It does not support Interlink or any other third-party TCP/IP.



x
USS Segment Requirements

PDS deployment requires each user of the server to be identified to USS by means of a default segment definition. This default OMVS segment is defined when USS is installed as a part of z/OS. Please refer to your IBM UNIX System Services documentation for more information about this subject.



x
HFS Home and Configuration Directory Requirements

Libraries and the APIs supporting them must reside in the HFS file system to enable the following features:

They are also required for the following Java-based and SAP-based adapters:

At installation time, a panel with a list of adapters to be configured will be displayed. If any of the above adapters are selected, the installation will require the path for two HFS locations as follows:

If no data adapters were selected, the next panel will allow an optional configuration for the JSCOM3 listener. If server-side graphics and/or Adobe® Flex® support are desired, the listener must be configured and all three paths are required (edahome_dir, edaconf_dir, plus the path to Java passed to either JDK_HOME or IBI_JNIPATH).

If edahome_dir is not defined at installation time, it will not be possible to configure it later using the Web Console. The server will have to be re-installed, configuring the JSCOM3 listener.


Top of page

x
Installing a New Server for PDS

In this section:

To install a new Server for z/OS deployed using partitioned data set (PDS) libraries, perform the following steps.



x
Step 1. Set Up User IDs

You can use any user ID to install and run the server. Whichever ID you use becomes the first server administrator ID (sometimes referred to as iadmin).



x
Step 2. Collect Required Information for Adapters

For current information about which adapters are supported:

  1. Go to http://techsupport.informationbuilders.com.

    The Information Builders Technical Support home page opens.

  2. In the Quick Links section on the right side of the page, click Supported Systems/Adapters.

    The Supported Systems and Adapters page opens.

  3. Click the link for the server release you want.

    The Supported Systems and Adapters page for that release opens.

  4. Click the link for your platform.

    The support chart for that platform opens.

You must provide information to configure the adapters that you are licensed to install. The installation procedure automatically prompts you for this information. When you are prompted for an optional steplib, ddname, or environment variable, the installation procedure will indicate this with an OPT> prompt.

After you have installed and configured the server, you will be able to further configure your adapters using a web-based server configuration tool called the Web Console.

The following table describes what information you need to provide for each adapter that you have. (If an adapter is not listed, no information needs to be provided for it.) Note that the table refers to:

Adapter

Information you must provide

Adabas

Provide the data set name for the following STEPLIB allocation:

  • load library

This is required only for the synonym creation process. For example, in a production environment in which all synonyms already exist, you can omit this.

When you configure the adapter, you will need to provide the name of the Adabas source library and the associated data set name.

CA-DATACOM

Provide the data set names for the following STEPLIB allocations:

  • CUSLIB load library
  • CAILIB load library
  • utility library
  • URT library

CA-IDMS

(both DB and SQL)

Provide the data set names for the following STEPLIB allocations:

  • load library
  • DBA load library

Provide the data set names to which the following ddnames are allocated:

  • SYSIDMS. Check with your CA-IDMS DBA regarding this ddname.
  • SYSCTL. Is the library corresponding to the central version you want to use.

CICS Transaction

Provide the data set name for the following STEPLIB allocation:

  • CICS EXCI load library

Call Java

You must have the JDK installed.

Provide a value for the following environment variables:

  • CLASSPATH. Provide the paths of the .jar files that you want to access. These paths will be appended to CLASSPATH.

This adapter requires configuration of the JSCOM3 listener. Provide three required paths:

EJB

You must have the JDK installed.

Provide a value for the following environment variables:

  • CLASSPATH. Provide the paths of the .jar files that you want to access. These paths will be appended to CLASSPATH.

If you are deploying the adapter to access an EJB on a:

  • WebLogic server, specify the following path:
    /pathspec/weblogic.jar
  • WebSphere server, specify the following paths:
    /pathspec/websphere.jar

    /pathspec/ejbcontainer.jar (one for each EJB container)

This adapter requires configuration of the JSCOM3 listener. Provide three required paths:

JDBC

You must have the JDK installed.

Provide a value for the following environment variables:

  • CLASSPATH. Provide the paths of the .jar files that you want to access. These paths will be appended to CLASSPATH.

This adapter requires configuration of the JSCOM3 listener. Provide three required paths:

Microsoft SQL Server

You must select Call Java adapter in addition to the Microsoft SQL Server adapter.

Provide a value for the following environment variables:

  • CLASSPATH. Provide the paths to the following files; these paths will be appended to CLASSPATH.
    • msbase.jar
    • mssqlserver.jar
    • msutil.jar

This adapter requires configuration of the JSCOM3 listener. Provide three required paths:

DB2 CAF

Provide the data set names for the following STEPLIB allocations:

Provide the following information for DB2 BIND:

  • DSNCLIST dataset name.
  • DB2 REL type either 8 or 9 or 10.
  • DB2 plan name.
  • DB2 SSID.

The installation will generate a fully customized DB2 BIND job and configure the adapter. DB2 CAF will be ready to use once the BIND job is executed. The configuration can be modified later using the Web Console, if necessary.

DB2 CLI

Provide the data set names for the following STEPLIB allocations:

Provide the data set name (including member name if applicable) for the following DDname:

  • DSNAOINI, which contains the DB2 CLI ini file.

IMS

Provide the data set names for the following STEPLIB allocations:

  • DFSPZP load library (optional; not needed if PZP modules are stored in the DFSRESLB library)
  • DFSRESLB load library

IMSBMP

Provide the data set names for the following STEPLIB allocation:

  • DFSRESLB load library

Provide the data set names for the following FOCPSB allocation:

  • FOCPSB library containing FOCPSB definitions

Millennium

Provide the data set name for the following STEPLIB allocation:

  • load library

Model 204

Provide the data set name for the following STEPLIB allocation:

  • load library

MQSeries

Provide the data set names for the following STEPLIB allocations:

  • SCSQLOAD load library
  • SCSQAUTH load library

NATURAL Batch

Provide the data set name for the following STEPLIB allocation:

  • NATURAL load library

SAP (SQL)

Provide values for the following environment variables:

  • LIBPATH, which contains the path to SAP RFC SDK.
  • SAP_CODEPAGE=0126, or the correct SAP code page for your language environment.

This adapter requires configuration of two required paths:

Is recommended that the code page conversion tables be created under directory edaconf_dir.

SAP BW

Provide values for the following environment variables:

  • LIBPATH, which contains the path to SAP RFC SDK.SAP_CODEPAGE=0126, or the correct SAP code page for your language environment.

This adapter requires configuration of two required paths:

Is recommended that the code page conversion tables be created under directory edaconf_dir.

Supra

Provide the dataset name for the following STEPLIB allocations:

  • LINKLIB load library.
  • INTERFLM load library.
  • ENVLIB load library.

Provide the data set name to which the following ddname is allocated:

  • CSIPARM containing the CSIPARM definition, which in turn points to the Central PDM you are accessing.
  • CSISYSIN containing the parameters used for connecting the multi-session adapter to the Central PDM.

VSAM CICS

Provide the data set name for the following STEPLIB allocation:

  • CICS EXCI load library


x
Step 3. Access the Installation Software

You can choose to access the server installation software using either:



x
Procedure: How to Unload the Installation Software From Tape

The software is provided on a cartridge in 3490 or 3590 format with MVS PDSs. Perform the following to unload the installation data set from the tape:

  1. Log on to TSO.
  2. Run an IEBCOPY job to allocate and unload the qualifier.HOME.DATA data set. This PDS contains the members needed for the actual installation.

    It is recommended that you use HOME.DATA as the low-level qualifier for the target data set. Although you can specify any low-level qualifier, HOME.DATA enables the installation procedure to generate default data set names, simplifying your installation.

    Note: If you do not use HOME.DATA, then change the following line to reflect the value you used.

    //         SET  EDAUSSD='HOME.DATA'

    Do this before you run ISETUP.

    The following sample JCL is for the initial unload to a new data set:

    //IEBCOPY  EXEC PGM=IEBCOPY,REGION=0M
    //SYSPRINT DD SYSOUT=*
    //SYSUT1   DD UNIT=workunit,SPACE=(CYL,(5,1))
    //OUT1     DD DISP=(NEW,CATLG,DELETE),
    //         DSN=qualifier.HOME.DATA,
    //         DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200),
    //         SPACE=(CYL,(5,5,25)),
    //         UNIT=SYSDA
    //IN1      DD DISP=(OLD,PASS),
    //            DSN=HOME.DATA,
    //            UNIT=cart,
    //            VOL=(,RETAIN,,SER=volser),
    //            LABEL=(1,SL)
    //SYSPRINT  DD  SYSOUT=*
    //SYSIN     DD  *
      COPY INDD=IN1,OUTDD=OUT1

    where:

    workunit

    Is the unit for the work data set.

    qualifier

    Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the server. However, you can use any site-specific value.

    For PDS, we recommend retaining the low-level qualifier HOME.DATA, but you can change this to any site-specific value. If you use a low-level qualifier other than HOME.DATA, you must then edit member PDSSNAME to change the string “HOME.DATA” to the low-level qualifier you specify here.

    cart

    Is the unit type of the tape drive. Common names include 3490, TAPE, and 3590. Change as needed.

    volser

    Is the value shown on the media label.

    After this job has run, qualifier.HOME.DATA is allocated, cataloged, and populated with the members needed to continue the product installation.

For details, see Optional Low-Level Qualifier Changes.



x
Procedure: How to Download the Installation Software Using FTP

To download the installation software:

  1. Go to http://techsupport.informationbuilders.com.

    The Information Builders Technical Support home page opens.

  2. Click My Downloads in the My Account section on the right side of the page.

    The Downloads, Upgrades, Service Packs, and PTFs page opens.

  3. Click the link for your product (for example, WebFOCUS and iWay Server and iWay Client).

    The Downloads by Release page for your product opens.

  4. Click your release from the Current Production Releases list.

    The Software Downloads page for your release opens.

  5. Scroll down and find the platform on which you want to install the server, and then click Download to the right of the platform name.
  6. Fill in the registration form and then click Continue.

    The Software Download Agreement page opens.

  7. Select I agree... to consent to the Download Agreement, and then click Continue.

    The Download Instructions page opens. Select AUTOMATIC or MANUAL and follow the relevant instructions.

    A copy of the instructions is automatically emailed to you for later reference.

  8. Log on to TSO.
  9. Follow the instructions on the Download Page in your TSO session.

Continue with Optional Low-Level Qualifier Changes.



x
Reference: Optional Low-Level Qualifier Changes

We recommend retaining the default low-level qualifiers that are supplied for the installation libraries. However, if you need to change any of them (for example, to conform to site-specific naming conventions), you can do so by editing them in member PDSSNAME of high_level_qualifier.HOME.DATA. You can see a list of the qualifiers in Default Low-Level Qualifiers.

Caution: If you change any low-level qualifiers and do not reflect those changes exactly in PDSSNAME, you will experience problems with the server installation and operation.

Do not change the value of &CONFTYPE.

Once you have finished changing any names, continue with Step 4. Run ISETUP.



x
Reference: Default Low-Level Qualifiers

The following low-level qualifiers are set in high_level_qualifier.HOME.DATA(PDSSNAME):

//         SET  PDSFFSD='PDS.FFS.DATA'         Full Function server
//         SET  PDSWFSD='PDS.WFS.DATA'         WebFocus Reporting server
//         SET  PDSDMD='PDS.DM.DATA'           DataMigrator
//         SET  PDSWFMD='PDS.WFM.DATA'         WebFocus Maintain Server
//         SET  EDACCFG=&CONFTYPE..CONF.CFG    Configuration files
//         SET  EDACACX=&CONFTYPE..CONF.ACX
//         SET  EDACMAS=&CONFTYPE..CONF.MAS
//         SET  SMARTLIB=&CONFTYPE..CONF.SMARTLIB.DATA
//         SET  EDACPRF=&CONFTYPE..CONF.PRF    Profiles
//         SET  EDAHDAT='HOME.DATA'            Installation library
//         SET  EDAHETC='P.HOME.ETC'           Server html and text files
//         SET  EDAHACX='P.HOME.ACX'           Access files
//         SET  EDAHFEX='P.HOME.FEX'           RPCs
//         SET  EDAHMAS='P.HOME.MAS'           Master files
//         SET  EDAHBIN='P.HOME.BIN'           Server binary files
//         SET  EDAHERR='P.HOME.ERR'           Server NLS and error files
//         SET  EDALOAD='P.HOME.LOAD'          Load Library
//         SET  EDACICS='P.HOME.CICS.LOAD'     CICS Load Library
//         SET  SYSRPC=&CONFTYPE..SYSRPC.FOCUS
//         SET  FOCUSSU=&CONFTYPE..FOCUSSU.FOCUS
//         SET  ETLLOG=&CONFTYPE..ETLLOG.FOCUS
//         SET  ETLSTATS=&CONFTYPE..ETLSTATS.FOCUS


x
Step 4. 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 submitted to install the server on z/OS. This JCL job retrieves the remainder of the data sets from the media and configures a basic working server.

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

    The first Installation and Configuration panel opens.

  2. Enter 2 and press Enter to continue to the next panel.

    The following panel opens.

  3. Complete the panel as directed in the following table.

    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.

    For option 3, Refresh Installation, see Upgrading Your Server Release for PDS.

    Enter License Key

    Enter the license key that was provided with the software.

    Be sure to store this key in a safe place for future reference.

    Input source

    Enter the input source:

    • T for Tape - If you received your software on Tape media.
    • D for Disk - If you selected manual download from the download instructions.
    • F for FTP - If you selected automatic download from the download instructions.

    Number of CPUs online

    Shows the current number of general use processors currently online. It cannot be changed. This value is going to be matched with the licensed number of CPUs provided in the License Key, when the installation job is submitted. At this point this verification is not being enforced and if the licensed number does not match the actual number of CPUs currently online, a warning will be issued and the installation job will continue.

    Installation Userid

    Shows the current logon ID. It cannot be changed.

    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 // 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 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 will be used for each job that is submitted.

  4. Press Enter to continue to the next panel.

    This following panel only appears if FTP was previously selected. Otherwise, skip to Step 6.

  5. Complete the panel as follows.

    Field

    Instructions

    HLQ for downloaded files

    This value defaults to the high level qualifier of the HOME.DATA file that ISETUP is running from. If necessary, change the value to any other high level qualifier that is to be used to create the uncompressed version of the FTP files.

    FTP Userid

    Cut and paste from the download instructions.

    FTP Password

    Cut and paste from the download instructions.

  6. Press Enter to continue to the next panel.

    Note that in the current panel (and some later panels), if you are running ISETUP from:

    • high_level_qualifier.HOME.DATA, the panel will display default values for some fields.
    • Any other library, the panel will not display any default values.

    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

    Input Media (installing from tape only)

    Volume serial number

    Provide the volume serial number of the server media. The number is located on the tape supplied in you server package.

    Unit type

    Review the default value and change if necessary.

    Work unit type

    Review the default value and change if necessary.

    You can specify a UNIT= type value (for example, SYSDA), or you can direct work files to a specific volume serial number by specifying, in single quotation marks ('), 'SYSDA,VOL=SER=volume'.

    Input Media (installing from disk/FTP only)

    Input Libraries HLQ

    (EDAHOME)

    This is the high-level qualifier that you had specified when you manually downloaded the installation software from the FTP site. This is an input field if Disk input source was previously selected. Otherwise, it is a protected field.

    Copy to runtime libraries

    If you want to use the downloaded installation software as a backup, and create a new copy from which to run, enter Y. If the Input Libraries HLQ and the Output Libraries HLQ are the same, this value will be ignored and no copy will take place.

    Otherwise, accept the default N to run from the downloaded software.

    General Installation Parameters

    Output Libraries HLQ

    This is the high-level qualifier that the installation procedure will use to allocate output libraries.

    Unit/Volume

    These show the values that the installation process will use to allocate the output libraries. If necessary, you can change these to site-specific values.

    Approot value

    This is where application components will reside.

    Note that this high-level qualifier must differ from the output libraries high-level qualifier (EDACONF) that you entered at the top of the panel.

    To specify a different qualifier for application components, change the value for this field. It can be up to 21 characters.

    HTTP Listener Port

    This is the port number that the server will use 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.

    Deferred Execution req?

    For PDS deployment, the creation of the deferred execution files is optional at install time. For WebFOCUS Reporting Server the default is Y. If N is selected, no files are created and commented out DD entries are coded in the IRUNJCL member of the server's configuration file. Member IBATDEF is also created at install time and can be run at any time to physically create the deferred execution files. The feature can then be activated by un commenting the nine DD cards (//*EDACDxxx) in IRUNJCL and resubmitting the server JCL ISTART.

  7. Press Enter to continue to the next panel.

    Depending on your license key, the Data Adapter panel may open. If the Data Adapter panel opens, continue with Step 8; otherwise, skip to Step 9.

  8. The Data Adapter panel 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 Step 2. Collect Required Information for Adapters.

      After you have finished installing and configuring the server, you can use the Web Console to finish configuring these adapters, and to configure adapters that do not have MVS JCL requirements.

  9. Press Enter to continue to the next panel.

    The JSCOM3 Listener configuration panel opens.

    1. The panel will prompt for the path to the Java environment to be passed to either JDK_HOME or IBI_JNIPATH, as described in JVM Requirements for Java Services, and it will also prompt for edahome_dir and edaconf_dir, as described in HFS 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, MS 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 select, this configuration might still be desirable to enable server-side graphics and Adobe® Flex® features. To skip the configuration, leave the path blank.
  10. Press Enter to continue to the next panel.

    The confirmation panel opens.

  11. If you wish to review a list of the data sets to be allocated, type Y in the Review output allocations field and press Enter.

    A panel opens listing the data sets. You may need to page down to see the entire list. Press Enter when you are done to return to the confirmation panel.

  12. 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.server_type.DATA configuration library.
    • S to create JCL in high_level_qualifier.PDS.server_type.DATA, and submit the job immediately.

    Note: If FTP was selected, JCL will be created to download the server software and run the install and configuration process.

    where:

    high_level_qualifier

    Is the high-level qualifier to be used for all output libraries. You specified the high-level qualifier during server installation, as described in Step 4. Run ISETUP, in Step 4.

    server_type

    Is one of the following:

    FFS

    for a Full-Function Server

    DM

    for a DataMigrator Server

    WFS

    for a WebFOCUS Reporting Server

    WFM

    for a Shared Application Server for WebFOCUS Maintain

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

    Following is a table of the jobs created. All members are created in the configuration library (as described in Step 11).

    Job

    Description

    ISETUPJ1

    Main JCL Job stream that is used to install the server. For FTP processing, this JCL can be restarted at any step due to a previous failure. To do this, add RESTART = procname.stepname to the JOB card and resubmit the ISETUPJ1 JCL.

    ISOPTS1

    Options used to install the server.

    The following members all call procedure IRUNJCL, 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 also created in the configuration library.

    Member

    Description

    CMRUN

    JCL to run DataMigrator batch jobs. This is created only when installing a DataMigrator Server.

    IBATDEF

    JCL to create the deferred execution data sets, in case they were not created in the original install.

    DB2V8PRM

    DB2 version 8 DBRM referenced in GENDB2 JCL.

    DB2V9PRM

    DB2 version 9 DBRM referenced in GENDB2 JCL.

    DB2V10PR

    DB2 version 10 DBRM referenced in GENDB2 JCL.

    GENDB2

    JCL to bind the DB2/CAF plan.

    IIMSBMP

    Example JCL to run the IMS/XMI server job in BMP mode.

    IIMSDLI

    Example JCL to run the IMS/XMI server job in DLI mode.

    The following members contain sample started task JCL, and are also 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.



x
Step 5. Test the Server Installation

To test the server installation:

  1. Log on to TSO as iadmin.
  2. Submit the ISTART JCL from the configuration library to start the server. This executes the IRUNJCL proc. The configuration library is
    high_level_qualifier.PDS.server_type.DATA

    where:

    high_level_qualifier

    Is the high-level qualifier to be used for all output libraries. You specified the high-level qualifier during server installation, as described in Step 4. Run ISETUP, in Step 6.

    server_type

    Is one of the following:

    FFS

    for a Full-Function Server

    DM

    for a DataMigrator Server

    WFS

    for a WebFOCUS Reporting Server

    WFM

    for a Shared Application Server for WebFOCUS Maintain

  3. Check the job output for errors. Look for the EDAPRINT message:
    (EDA13023) ALL INITIAL SERVERS STARTED
  4. Start the Web Console by opening a browser pointed at the listener port of the server. The URL format is
    http://host:port

    where:

    host

    Is the name of the machine on which the server is installed.

    port

    Is one port higher than the port specified when installing the server. For example, if you specified port 8100 during installation, then use port 8101 to access the Web Console.

    The Web Console opens.

  5. Continue with adapter configuration, as described in the Adapter Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.

When you are finished using the server, you can use the Web Console to stop the server by going to the Web Console menu bar, selecting Workspace, and then Stop.

If you experience problems at start up, examine the job output for more information.



x
Step 6. Configure Server Security

You can run the server in any of the following security modes:

If you will be configuring your server with security mode OPSYS, you must perform the instructions in How to Configure Security With All Security Products, regardless of which security product you use. (For security modes PTH, DBMS, and LDAP, skip these topics.)

For a full description of all server security modes:

  1. From the Web Console menu bar, select Help, then Contents and Search.

    The Web Console Help window opens.

  2. In the left pane expand Server Administration.

Alternatively, see the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.



x
Procedure: How to Configure Security With All Security Products

To configure server security with RACF, eTrust CA-ACF2, or eTrust CA-Top Secret:

  1. Log on to TSO using the ID used to install the server.
  2. The libraries allocated to STEPLIB in IRUNJCL must be APF-authorized. Any non-APF-authorized libraries must be allocated to the TASKLIB DDNAME.
  3. Restart the server.

Note: If you want to use eTrust CA-ACF2 or eTrust CA-Top Secret, please contact Customer Support Services.



x
Procedure: How to Configure Security With eTrust CA-Top Secret

To use eTrust CA-Top Secret security, perform the following step:

  1. Create an eTrust CA-Top Secret facility entry for the server security module, R1SEC. The only need for permissions is for the RACROUTE call from the R1SEC program.


Example: Facility Entry Defining the Server to CA-Top Secret

The following is an example of a facility entry that defines the server to eTrust CA-Top Secret:

PGM=R1SEC ID=1 TYPE=099 
ATTRIBUTES=IN-USE,ACTIVE,SHRPRF,ASUBM,NOABEND,MULTIUSER,NOXDEF
ATTRIBUTES=LUMSG,STMSG,SIGN(M),INSTDATA,RNDPW,AUTHINIT
ATTRIBUTES=NOPROMPT,NOAUDIT,RES,WARNPW,NOTSOC,LCFTRANS
ATTRIBUTES=NOMSGLC,NOTRACE,NOEODINIT,IJU,NODORMPW,NONPWR 
ATTRIBUTES=LUUPD MODE=FAIL DOWN=GLOBAL LOGGING=ACCESS,INIT 
UIDACID=8 LOCKTIME=000 DEFACID=*NONE* KEY=8 
MAXUSER=03000 PRFT=003 


x
Procedure: How to Change the Security Mode From OPSYS to OFF

To change the security mode from OPSYS to OFF:

  1. Make sure the server is not running.
  2. In the high_level_qualifier.PDS.server_type.DATA(EDAENV) JCL, add the following setting:
    EDAEXTSEC=OFF
  3. Submit high_level_qualifier.PDS.server_type.DATA(ISTART). The server will now be running with security turned off.


x
Procedure: How to Change the Security Mode From OPSYS to PTH, DBMS, or LDAP

To switch the security mode from OPSYS to PTH, DBMS, or LDAP:

  1. From the Web Console's menu bar select Workspace and then Access Control.

    The Security Mode pane opens.

  2. In the Security Mode drop-down list, select the new security mode.

    For more information about configuring PTH, DBMS, and LDAP security modes, either:

    • Go to the Web Console menu bar, select Help, then Contents and Search, and in the left pane expand Server Administration.
    • For details, see the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.
  3. Click the Apply and Stop button.

    A message is displayed about restarting the server.

  4. Assign the new security setting to EDAEXTSEC by manually editing following server member.

    For HFS: high_level_qualifier.server_type.DATA(EDAENV)

    For PDS: high_level_qualifier.PDS.server_type.DATA(EDAENV)

    For example:

    EDAEXTSEC=PTH
  5. Restart the server by submitting the ISTART JCL.

Top of page

x
Starting and Stopping a Server for PDS

In this section:

This section provides information on operation and use of the server. Additional information on the server and how to configure adapters is available in the Web Console help. The Web Console help is also available as the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.



x
Starting the Server Using a Batch Job

To start the server, submit the ISTART member of the MVS configuration library (high_level_qualifier.server_type.DATA) for your server.



x
Starting the Server Using a Started Task

ISETUP creates started task JCL to start the server. This started task in a member of the MVS configuration library is IWAYS.

In order to execute the started task, you must:

To submit the started task from the MVS console, issue the following command:

S IWAYS

You can add the started task to any automation product that you run.



x
Stopping the Server

You can stop the server using any of the following methods:


Top of page

x
DB2 Security Exit Configuration for PDS

Customize the DB2 security exit to allow the Adapter for DB2 to run with user-level security enabled. If you do so, users will connect to DB2 with the authorization of the user ID with which they logged on to the server. The server must also be running with security turned on.

If you do not customize the DB2 security exit, all users will be assigned the connection ID to DB2 that is associated with the region, job submitter, or started task.

For DB2 CLI adapter, the connection to DB2 must be be configured as trusted for the exit to be invoked.

The changes that must be made to the IBM DB2 signon exit, DSN3SATH, differ for RACF and eTrust CA-Top Secret sites and eTrust CA-ACF2 sites.

The highlighted text and comments shown in the examples indicate the lines containing the recommended modification of DSN3SATH, which calls the module FOCDSN3 the supplied exit.

After you finish the edits, assemble the exit into an object file. This object file is input to the link JCL found in Modifying the Link JCL for DSN3SATH.

Note:



Example: Changing DSN3SATH for RACF and eTrust CA-Top Secret Sites

1. Search for the SATH001 label - add two lines (FOCDSN3):

SATH001  DS    0H  
         USING WORKAREA,R11        ESTABLISH DATA AREA ADDRESSABILITY 
         ST    R2,FREMFLAG                SAVE FREEMAIN INDICATOR
         XC    SAVEAREA(72),SAVEAREA CLEAR REGISTER SAVE AREA
         . 
         . 
         .  
*********SECTION 1:  DETERMINE THE PRIMARY AUTHORIZATION ID  ************
*                                                                       *
*  IF THE INPUT AUTHID IS NULL OR BLANKS, CHANGE IT TO THE AUTHID       *
*  IN EITHER THE JCT OR THE FIELD POINTED TO BY ASCBJBNS.               *
*  THE CODE IN THIS SECTION IS AN ASSEMBLER LANGUAGE VERSION OF         *
*  THE DEFAULT IDENTIFY AUTHORIZATION EXIT.  IT IS EXECUTED ONLY        *
*  IF THE FIELD ASXBUSER IS NULL UPON RETURN FROM THE RACROUTE          *
*  SERVICE.  FOR EXAMPLE, IT DETERMINES THE PRIMARY AUTH ID FOR         *
*  ENVIRONMENTS WITH NO SECURITY SYSTEM INSTALLED AND ACTIVE.           *
*                                                                       *
*************************************************************************        
SPACE 
    LA    R1,AIDLPRIM         LOAD PARM REG1             <--ADD 
    CALL  FOCDSN3             GO GET THE IBI EXIT        <--ADD 
    CLI   AIDLPRIM,BLANK      IS THE INPUT PRIMARY AUTHID NULL
    BH    SATH020             SKIP IF A PRIMARY AUTH ID EXISTS

2. Search for the SATH020 label - add a comment box, add one line, and comment out four lines:

SATH020  DS    0H                  BRANCH TO HERE IF PRIMARY EXISTS
*****OPTIONAL CHANGE @CHAR7:  FALLBACK TO SEVEN CHAR PRIMARY AUTHID***
*                                                                    *
*  IF YOUR INSTALLATION REQUIRES ONLY SEVEN CHARACTER PRIMARY        *
*  AUTHORIZATION IDS (POSSIBLY TRUNCATED) DUE TO DB2 PRIVILEGES      *
*  GRANTED TO TRUNCATED AUTHORIZATION IDS, THEN YOU MUST BLANK OUT   *
*  COLUMN 1 OF THE ASSEMBLER STATEMENT IMMEDIATELY FOLLOWING THIS    *
*  BLOCK COMMENT. THEN ASSEMBLE THIS PROGRAM AND LINK-EDIT IT INTO   *
*  THE APPROPRIATE DB2 LOAD LIBRARY AS EXPLAINED IN AN APPENDIX      *
*  OF "THE DB2 ADMINISTRATION GUIDE".                                *
*                                                                    *
*  OTHERWISE, YOU NEED DO NOTHING.                                   *
*                                                            @KYD0271*
**********************************************************************
*      MVI   AIDLPRIM+7,BLANK    BLANK OUT EIGHTH CHARACTER 
       SPACE 
       . 
       . 
       .
*   RACF IS ACTIVE ON THIS MVS 
****************************************************************** <--ADD 
*                                                                * <--ADD 
* The logic was modified because in DB2 V8 AIDLACEE is always not* <--ADD 
* NULL. We used to honor AIDLACEE first, FOCDSN4 second and then * <--ADD 
* AS ACEE. Now we honor FOCDSN4 first, AIDLACEE second and then  * <--ADD 
* AS ACEE.                                                       * <--ADD 
*                                                                * <--ADD 
* 03/11/05   ASK0                                                * <--ADD 
****************************************************************** <--ADD 
  USING ACEE,R6             ESTABLISH BASE FOR ACEE        @KYL0108
  L     R6,AIDLACEE         Get => caller ACEE if any             <--ADD 
* ICM   R6,B'1111',AIDLACEE CALLER PASSED ACEE ADDRESS? @KYL0108 <-COMMENT 
* BZ    SATH024              NO, USE ADDRESS SPACE ACEE  @KYL0108 <-COMMENT 
* CLC   ACEEACEE,EYEACEE    IS IT REALLY AN ACEE?       @KYL0108 <-COMMENT 
* BE    SATH027             YES, PROCEED NORMALLY       @KYL0108 <-COMMENT 
      SPACE 1   
SATH024  DS    0H                  USE ADDRESS SPACE ACEE      @KYL0108
    .
    .
    .

3. Search for the SATH025 label - replace sath025 and add sath026 (FOCDSN4):

SATH025  DS    0H
                                            
    CALL  FOCDSN4              GO GET THE IBI EXIT (4=GROUP AUTH) <--ADD 
    LTR   R6,R6                DOES AN ACEE EXIST?  IF NOT,       <--ADD 
    BZ    SATH026              CHECK ACEE IN ADDRESS SPACE        <--ADD 
    CLC   ACEEACEE,EYEACEE     DOES IT LOOK LIKE AN ACEE?         <--ADD 
    BE    SATH027              YES, GO DO GROUPS                  <--ADD 
SATH026  DS    0H                                                  <--ADD 
   L      R6,ASCBASXB          GET ADDRESS SPACE EXTENSION BLOCK  <--ADD 
   L      R6,ASXBSENV-ASXB(,R6) GET ACEE ADDRESS                  <--ADD 
   CLC    ACEEACEE,EYEACEE     DOES IT LOOK LIKE AN ACEE?         <--ADD 
   BNE    SATH049              NO, THEN CAN'T DO GROUPS           <--ADD 
   DROP   R8                   DROP ASCB BASE REG                 <--ADD 
   SPACE 1                                                        <--ADD
SATH027  DS    0H              CHECK LIST OF GROUPS OPTION
   TM     RCVTOPTX,RCVTLGRP   IS LIST OF GROUPS CHECKING ACTIVE
   BZ     SATH040             SKIP TO SINGLE GROUP COPY IF NOT 
   DROP   R7                  DROP RCVT BASE REG  
   SPACE 1  
* RACF LIST OF GROUPS OPTION IS ACTIVE
   EJECT 
    .
    .
    .


Example: Changing DSN3SATH for eTrust CA-ACF2 Sites

*DSN3SATH source is provided by ACF2.

1. Search for PRIMARY AUTHORIZATION ID - add two lines (FOCDSN3):

***************************************************************** 
*                                                               *
*           PRIMARY AUTHORIZATION ID                            *
*                                                               * 
*****************************************************************
*                                                               *
*      IF THE PRIMARY AUTHORIZATION ID IS NULL OR BLANKS        *
*      IF CA-ACF2 IS AVAILABLE                                  *
*      SET PRIMARY ID FROM ACFASVT (ASVLID)                     *
*      ELSE                                                     *
*      IF TSO FOREGROUND USER                                   *
*      SET PRIMARY ID FROM TSO LOGON ID (ASCBJBNS)              *
*      ELSE                                                     *
*      SET PRIMARY ID FROM JOB USER (JCTUSER)                   *
*                                                               *
*****************************************************************
      SPACE 2                                               04260000
      LA R1,AIDLPRIM LOAD PARM REG1                 <--ADD  
      CALL FOCDSN3 GO GET THE IBI EXIT              <--ADD 
       CLI   AIDLPRIM,C' '      PRIMARY AUTHID THERE ?      04270000
       BH    PRIMWTO            ..YES, EVERYTHINGS OK HERE  04280000
       L     R3,PSAAOLD-PSA(0)  CURRENT ASCB ADDRESS        04290000
       USING ASCB,R3            ASCB ADDRESSABILITY         04300000
       SPACE 2                                              04310000


Example: Modifying the Link JCL for DSN3SATH

This is sample link JCL for the IBM exit DSN3SATH. Modify the JCL to link the modules into the DB2 security exit as follows.

//LKED  EXEC PGM=IEWL,PARM='LIST,XREF,LET,RENT,AMODE=31'
//OBJECT    DD DSN=db2pref.SDSNSAMP.OBJ,DISP=SHR <--OUTPUT OF ASSEMBLE 
STEP
//EDAMOD    DD DSN=high_level_qualifier.HOME.LOAD,DISP=SHR
//SYSLMOD   DD DSN=db2pref.DSNEXIT,DISP=SHR
//SYSPRINT  DD SYSOUT=*
//SYSUT1    DD UNIT=SYSDA,SPACE=(100,(50,50))
//SYSLIN    DD *
  INCLUDE EDAMOD(FOCDSN3)
***********************************************************************
*** Omit the following line for eTrust CA-ACF2
***********************************************************************
  INCLUDE EDAMOD(FOCDSN4) 
          ENTRY DSN3@ATH
  NAME DSN3@ATH(R)
/*

where:

db2pref

Is the prefix for the DB2 data sets.

high_level_qualifier

Is the high-level qualifier for the data sets.

Once this job finishes successfully, you must recycle the DB2 subsystem in order for the changes to take effect.


Top of page

x
MSODDX: DDNAME Translation for User Subroutines

On z/OS, you can incorporate an additional routine called MSODDX into a user-written subroutine that needs to access ddnames allocated to a WebFOCUS Reporting Server, a Data Migrator Server, or a Full-function Server. MSODDX provides ddname translation services that enable external programs to access files under the ddname used by the Server.

For details, see Chapter 6, Platform-Specific Commands and Features, in the Stored Procedures Reference.


Top of page

x
Overriding the Time Zone Setting

By default, the server will use the system set value for Time Zone. This can be overridden by setting the TZ in the EDAENV member of the servers configuration library.

TZ = valid tz string

For more information about time zone values, see the IBM UNIX System Services Command Reference and search for TZ.


Top of page

x
Adding a Configuration Instance for PDS

In this section:

Adding a configuration instance allows you to run different server configuration instances using the same server binaries. For example, if you installed using a Full-Function Server license code, you can use a WebFOCUS license to add a second configuration for a WebFOCUS Reporting Server. You can also add up to nine additional servers of the same type.



x
Step 1. Run ISETUP

To add a configuration instance, perform the following steps.

  1. Execute ISETUP again. You should have a high_level_qualifier.HOME.DATA PDS unloaded from the installation tape. Use option 6 in ISPF to execute the ISETUP member of this PDS.

    Note: If this PDS is not available, run an IEBCOPY job to allocate and unload it from the installation tape.

    The first Installation and Configuration panel opens.

  2. Enter 2 and press Enter to continue to the next panel.

    The following panel opens.

  3. Complete the first Installation and Configuration panel as follows.

    Field

    Instructions

    Enter selection

    Choose option 2, Add Additional Configuration Instance.

    Enter License Key

    Enter the license key that was provided with the software for the type of server instance that you want to configure (for example, the license key for a WebFOCUS Reporting Server or for a Full-Function Server).

    Input source

    This is ignored for option 2, adding a configuration instance.

    Number of CPUs online

    Shows the current number of general use processors currently online. It cannot be changed. This value is going to be matched with the licensed number of CPUs provided in the License Key, when the installation job is submitted. At this point this verification is not being enforced and if the licensed number does not match the actual number of CPUs currently online, a warning will be issued and the installation job will continue.

    Installation Userid

    Shows the current logon ID. It cannot be changed.

    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 // 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 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 will be used for each job that is submitted.

  4. Press Enter to continue to the next panel.

    The following panel opens.

  5. Enter the current base high-level qualifier used for EDAHOME.

    This indicates where to install the configuration (EDACONF) and where the binaries (EDAHOME) are installed. The installation procedure checks whether the required set of EDAHOME data sets exist. If the test fails, you receive a message indicating the failure and available options.

  6. Press Enter to continue to the next panel.

    If you are configuring the first instance of a given server type, the following panel opens.

    Otherwise, if you are configuring an additional instance of a given server type, the following panel opens. In this sample panel, two Full-Function Server configuration instances (FFS and FFS1) already exist, and a third (FFS2) is being added.

  7. Complete the panel as follows.

    Field

    Instructions

    Configuration Parameters

    Approot value

    This indicates where application components will reside for this configuration. The default value is based on the value specified for Current Base HLQ (EDAHOME) on the previous panel. To specify a different location for application components, change the value of this field.

    Different configurations which use the same base HLQ (high level qualifier) libraries (EDAHOME) can share the same approot value (that is, the same application files). Alternatively, they can use different approot values so that they have different sets of application files.

    If you specify the approot value of an existing server configuration, the installation process will recreate the server supplementary data sets and sample files (see Disk Space Requirements). If you do not want them to be recreated, provide a different value for approot.

    Output Libraries HLQ (EDACONF)

    You are prompted for this information only if you are configuring the first instance of a server type (for example, if you are configuring the first instance of a WebFOCUS Reporting Server).

    This is the high-level qualifier that the installation procedure will use to allocate output libraries, that is, to allocate the configuration libraries for this server instance. This high-level qualifier is also known as EDACONF.

    Unit/Volume

    You are prompted for this information only if you are configuring the first instance of a server type (for example, if you are configuring the first instance of a WebFOCUS Reporting Server).

    These show the values that the installation process will use to allocate the output libraries. If necessary, you can change these to site-specific values.

    EDACONF suffix

    You are prompted for this information only if you are configuring an additional instance of a server type (for example, if you are configuring a second instance of a WebFOCUS Reporting Server).

    Each server instance must have its own set of configuration libraries. To guarantee this, and to prevent a new set of configuration libraries from overwriting an existing set, the suffix that you specify here will be appended to the name of the server type qualifier. For example, if you are configuring the second instance of a WebFOCUS Reporting Server, you could specify that the suffix "1" be added, so that the EDACONF high-level qualifier would be:

    IADMIN.SRV77.PDS.WFS1.DATA 

    You can add a new configuration as a numeric or string suffix to the base server type. If you supply a string, the installation procedure ignores any numeric suffix. For a:

    • Numeric suffix, enter a digit between 1 and 9. This will be added to the server type in the directory name and library name to distinguish it from other configuration instances.
    • String suffix, enter a string of between 1 and 5 characters (for example, TEST, PROD, or DEV). The string cannot contain embedded spaces.

    You can also use the string suffix to extend the numeric numbering past 9. Just supply a number greater than 9.

    If you change the suffix value, when you press Enter, the panel refreshes with a new value for EDACONF Library.

    HTTP Listener Port

    This indicates the port number that the server will use 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.

    Deferred Execution req?

    For PDS deployment, the creation of the deferred execution files is optional at install time. For WebFOCUS Reporting Server the default is Y. If N is selected, no files are created and commented out DD entries are coded in the IRUNJCL member of the server's configuration file. Member IBATDEF is also created at install time and can be run at any time to physically create the deferred execution files. The feature can then be activated by un commenting the nine DD cards (//*EDACDxxx) in IRUNJCL and resubmitting the server JCL ISTART.

  8. Press Enter to continue to the next panel.

    Depending on your license key, the Data Adapter panel may open before the confirmation panel. If the Data Adapter panel opens, continue with Step 9; otherwise, skip to Step 10.

  9. The Data Adapter panel lists adapters that require the allocation of 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 Step 2. Collect Required Information for Adapters.

      After you have finished installing and configuring the server, you can use the Web Console to finish configuring these adapters, and to configure adapters that do not have JCL requirements.

  10. Press Enter to continue to the next panel.

    The JSCOM3 Listener configuration panel opens.

    1. The panel will prompt for the path to the Java environment to be passed to either JDK_HOME or IBI_JNIPATH, as described in JVM Requirements for Java Services, and it will also prompt for edahome_dir and edaconf_dir, as described in HFS 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, MS 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 select, this configuration might still be desirable to enable server-side graphics and Adobe® Flex® features. To skip the configuration, leave the path blank.
  11. Press Enter to continue to the next panel.

    The confirmation panel opens.

  12. 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 configuration library.
    • S to create JCL and submit the job immediately.
  13. As the job is processed, validate the installation as described in Step 2. Validate the Installation.


x
Step 2. Test the New Configuration Instance

To test the configuration instance that you just added:

  1. Log on to TSO as iadmin.
  2. Submit the ISTART JCL from the configuration library to start the server. This executes the IRUNJCL proc. The configuration library is
    high_level_qualifier.PDS.server_type[suffix].DATA

    where:

    high_level_qualifier

    Is the high-level qualifier to be used for all output libraries. You specified the high-level qualifier during server installation, as described in Step 4. Run ISETUP, in Step 6.

    server_type

    Is one of the following:

    FFS

    for a Full-Function Server

    DM

    for a DataMigrator Server

    WFS

    for a WebFOCUS Reporting Server

    WFM

    for a Shared Application Server for WebFOCUS Maintain

    suffix

    If you are testing an additional instance of a server type for which an earlier configuration exists, the new configuration library server type qualifier will have a suffix (for example, FFS1 or FFSDEV). The suffix distinguishes the new configuration library from the original one.

  3. Check the job output for errors. Look for the EDAPRINT message:
    (EDA13023) ALL INITIAL SERVERS STARTED
  4. Start the Web Console by opening a browser pointed at the listener port of the server. The URL format is
    http://host:port

    where:

    host

    Is the name of the machine on which the server is installed.

    port

    Is one port higher than the port specified when installing the server. For example, if you specified port 8100 during installation, then use port 8101 to access the Web Console.

    The Web Console opens.

  5. Continue with adapter configuration, as described in the Adapter Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.


x
Upgrading Your Server Release for PDS

In this section:

Use this option to upgrade a server to a new maintenance level within the same major release or, starting with major release 77, upgrade to a higher major release level. A major release is indicated by the first two digits of the release number.

The purpose of the PDS server refresh option is to create a new set of EDAHOME libraries. It is recommended that you test the new libraries in a test environment before manually changing your production JCL (IRUNJCL) to point to the new software. The upgrade process can overwrite an existing set of EDAHOME libraries (not recommended) if both "Current Base HLQ" and "HLQ for downloaded files" or "Output Libraries HLQ" are the same value.



x
Step 1. Access the Installation Software

You can choose to access the server installation software using either:

Note: The above FTP steps are for the AUTOMATIC download instructions to MVS. If you downloaded the software to another platform, then transferred the files to MVS (following the manual FTP instructions), a new set of EDAHOME Libraries will already exist on MVS, therefore there will be no need to run ISETUP. The only process that needs to occur is the copying of the DB2VPRM members from the new HOME.DATA to the current HOME.DATA of the release to be upgraded. Complete the upgrade by following steps 3-5 in Step 2. Run ISETUP.



x
Procedure: How to Unload the Installation Software From Tape

The software is provided on a cartridge in 3490 or 3590 format with MVS PDSs. Perform the following to unload the installation data set from the tape:

  1. Log on to TSO.
  2. Run an IEBCOPY job to allocate and unload the qualifier.HOME.DATA data set. This PDS contains the members needed for the actual installation.

    It is recommended that you use HOME.DATA as the low-level qualifier for the target data set. Although you can specify any low-level qualifier, HOME.DATA enables the installation procedure to generate default data set names, simplifying your installation.

    Note: If you do not use HOME.DATA, then change the following line to reflect the value you used.

    //         SET  EDAUSSD='HOME.DATA'

    Do this before you run ISETUP.

    The following sample JCL is for the initial unload to a new data set:

    //IEBCOPY  EXEC PGM=IEBCOPY,REGION=0M
    //SYSPRINT DD SYSOUT=*
    //SYSUT1   DD UNIT=workunit,SPACE=(CYL,(5,1))
    //OUT1     DD DISP=(NEW,CATLG,DELETE),
    //         DSN=qualifier.HOME.DATA,
    //         DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200),
    //         SPACE=(CYL,(5,5,25)),
    //         UNIT=SYSDA
    //IN1      DD DISP=(OLD,PASS),
    //            DSN=HOME.DATA,
    //            UNIT=cart,
    //            VOL=(,RETAIN,,SER=volser),
    //            LABEL=(1,SL)
    //SYSPRINT  DD  SYSOUT=*
    //SYSIN     DD  *
      COPY INDD=IN1,OUTDD=OUT1

    where:

    workunit

    Is the unit for the work data set.

    qualifier

    Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the server. However, you can use any site-specific value.

    For PDS, we recommend retaining the low-level qualifier HOME.DATA, but you can change this to any site-specific value. If you use a low-level qualifier other than HOME.DATA, you must then edit member PDSSNAME to change the string “HOME.DATA” to the low-level qualifier you specify here.

    cart

    Is the unit type of the tape drive. Common names include 3490, TAPE, and 3590. Change as needed.

    volser

    Is the value shown on the media label.

    After this job has run, qualifier.HOME.DATA is allocated, cataloged, and populated with the members needed to continue the product installation.

Proceed to Step 2. Run ISETUP.



x
Procedure: How to Download the Installation Software Using FTP

To download the installation software:

  1. Go to http://techsupport.informationbuilders.com.

    The Information Builders Technical Support home page opens.

  2. Click My Downloads in the My Account section on the right side of the page.

    The Downloads, Upgrades, Service Packs, and PTFs page opens.

  3. Click the link for your product (for example, WebFOCUS and iWay Server and iWay Client).

    The Downloads by Release page for your product opens.

  4. Click your release from the Current Production Releases list.

    The Software Downloads page for your release opens.

  5. Scroll down and find the platform on which you want to install the server, and then click Download to the right of the platform name.
  6. Fill in the registration form and then click Continue.

    The Software Download Agreement page opens.

  7. Select I agree... to consent to the Download Agreement, and then click Continue.

    The Download Instructions page opens. Select AUTOMATIC or MANUAL and follow the relevant instructions.

    A copy of the instructions is automatically emailed to you for later reference.

  8. Log on to TSO.
  9. Follow the instructions on the Download Page in your TSO session.

    Continue with Step 2. Run ISETUP.



x
Step 2. Run ISETUP

Server upgrade consists of a series of ISPF panels, which gather information for the upgrade. After the panel dialog is complete, JCL is created and submitted (if required) to create a new set of EDAHOME libraries.

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

    The Installation and Configuration panel opens.

  2. Select 2 for PDS deployment and press Enter to continue to the next panel.
  3. Complete the panel as follows.

    Field

    Instructions

    Enter selection

    Choose option 3, Refresh Installation.

    Enter License Key

    Enter the 10-digit license key that was provided with the software.

    Input source

    Choose the Input source, T for tape or F for automatic FTP download direct to MVS.

    Number of CPUs online

    Shows the current number of general use processors currently online. It cannot be changed. This value is going to be matched with the licensed number of CPUs provided in the License Key, when the installation job is submitted. At this point this verification is not being enforced and if the licensed number does not match the actual number of CPUs currently online, a warning will be issued and the installation job will continue.

    Installation Userid

    Shows the current logon ID. It cannot be changed.

    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 // 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 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 will be used for each job that is submitted.

  4. If you selected input source T, skip to Step 5.

    If you selected F for automatic FTP only, complete the panel as follows.

    Field

    Instructions

    HLQ for downloaded files

    High level qualifier to be used as the target for the FTP files. If this is the same value as "Current Base HLQ" (see below) then files will be overwritten. Two warning messages will be given and the enter key must be pressed to continue.

    FTP Userid

    User ID provided on the download instructions.

    FTP Password

    Password provided on the download instructions.

  5. Press Enter to continue to the next panel, and complete the panel as follows.

    Field

    Instructions

    Current Base HLQ (EDAHOME)

    High level qualifier of the current server that is to be refreshed. This HLQ will be used to check if a full set of EDAHOME libraries exist. From this value, the current installation library name is obtained and this will be the location used to create the refresh JCL.

  6. Press Enter to continue to the next panel, and complete the panel as follows.

    Field

    Instructions

    Input Media (installing from tape)

    Volume serial number

    Provide the volume serial number of the server media. The number is located on the tape supplied in you server package.

    Volume unit type

    Review the default value and change it if necessary.

    Work unit type

    Review the default value and change if necessary.

    You can specify a UNIT= type value (for example, SYSDA), or you can direct work files to a specific volume serial number by specifying, in single quotation marks ('), 'SYSDA,VOL=SER=volume'.

    Output Libraries

    Output Libraries HLQ

    For tape input only: High level qualifier that will be used to allocate and load a full set of EDAHOME libraries. Change the value as necessary. If this is the same value as "Current Base HLQ" (see previous page) then files will be overwritten. Two warning messages will be given and the enter key must be pressed to continue.

    HLQ for downloaded files

    If FTP is selected, this "HLQ for downloaded files" was provided on the previous panel.

    Unit/Volume

    Values that the installation process will use to allocate the EDAHOME libraries on MVS. If necessary, you can change these to site specific values.

    Refresh IBISAMP?

    Select Y/N to refresh the contents of the IBISAMP application.

    APPROOT value

    If Y was selected above, enter the APPROOT HLQ for IBISAMP to be refreshed.

    Refresh edahome_dir?

    Select Y/N to refresh the contents of the edahome_dir directory.

    edahome_dir

    If Y was selected above, enter the path to edahome_dir.

    RA Active?

    If you are refreshing a 7.7, 7.7.01, or 7.7.02 installation, and Resource Management is configured, select Y to recreate RMLDATxx datasets, otherwise select N. The default value is N.

    Note: The installation JCL library name is where the refresh JCL will be created. This library is the current server installation library. The value cannot be changed.

  7. Ensure that all values on the 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 configuration library.
    • S to create JCL and submit the job immediately.
  8. As the job is processed, in SDSF, check JESLOG for errors and return codes.

    The following jobs are added to the current server configuration library:

    Job

    Description

    ISETUPJ3
    ISOPTS3

    Main JCL Job stream that is used to install the server.



x
Step 3. Test the Server Installation

To test the server installation:

  1. Log on to TSO as iadmin.
  2. Using a test server, replace all the EDAHOME libraries referenced in IRUNJCL with the new set.
  3. Submit the ISTART JCL to start the server.
  4. Check the job output for errors. Look for the EDAPRINT message:
    (EDA13023) ALL INITIAL SERVERS STARTED
  5. Start the Web Console by opening a browser pointed at the listener port of the server. The URL format is
    http://host:port              

    where:

    host

    Is the name of the machine on which the server is installed.

    port

    Is one port higher than the port specified when installing the server. For example, if you specified port 8100 during installation, then use port 8101 to access the Web Console.

    The Web Console opens.

  6. Click Test to run a sample report.

When you are finished using the server, you can use the Web Console to stop the server by going to the Web Console menu bar, selecting Workspace, and then Stop.

If you experience problems at start up, examine the job output for more information.



x
Step 4. Reconfigure Server Security

For information about configuring server security, see Step 7. Configure Server Security.

To reconfigure server security to OPSYS mode only:

  1. Log on to TSO.
  2. The libraries allocated to STEPLIB in IRUNJCL must be APF-authorized. Any non APF-authorized libraries must be allocated the TASKLIB DDNAME.
  3. Test server security by repeating the process described in Step 3. Test the Server Installation.

 



x
Preventing Unsecured Server Starts After Upgrades

If the explicit environment variable EDAEXTSEC is set to OPSYS (or ON) and the server cannot impersonate users because it lacks platform-specific authorization steps, the server start aborts and error messages are written to the edaprint log.

This feature prevents an unsecured server start after a software upgrade if any of the required post-upgrade, reauthorization steps are missed on a UNIX, IBM i, or z/OS HFS deployment. This is not applicable to other platforms. The setting may be placed in any normal server start-up shell or profile that a site is using or in the server edaenv.cfg configuration file. The messages vary slightly by platform.

The edaprint messages are:

Configured security is 'ON' as set by EDAEXTSEC variable.
Server is not APF-authorized.
Workspace initialization aborted.
(EDA13171) UNABLE TO START SERVER


x
Step 5. Reconfigure Adapters

While most adapters do not require additional steps after updating binary files, the following table notes the adapters that do require some consideration.

Adapter

Steps After Updating Binaries

Adabas

  • Change the value for EDALOAD in member EDAENV of your current server configuration library (qualif.PDS.servertype.DATA) to point to the new P.HOME.LOAD.
  • Re-enable the module containing SVC using the Web Console adapter configuration page.
  • Test the adapter from the adapter page before running your applications.

DB2 CAF

  • Rerun the IDB2BIND JCL found in your current server configuration library qualif.PDS.servertype.DATA. This needs to be done for each subsystem that is used.
  • Test the adapter from the adapter page before running your applications.

 



x
Migrating From an MVS Server to a PDS Deployment Server

In this section:

 

In this section, we will be describing the migration process by comparing both server architectures (Traditional MVS server versus the PDS Deployment server), so we will demonstrate where configurations were made in the MVS server and what is the corresponding place and/or syntax in the PDS server.

Throughout this section we will refer to the Traditional MVS Server as simply MVS or SSCTL and we will refer to the PDS Deployment Server as simply PDS.

Applications running on a traditional MVS server will not require any changes when migrated. The server supports read and write access to all PDSs, such as Master, Access, FOCEXEC, and data and it can read and write sequential files and FOCUS files, both locally and using the FOCUS Database Server (FDS).

The DYNAM command is fully supported, except for:



x
Installation Overview


x
MVS TCBs vs. PDS Processes

The following table illustrates how the PDS server has a more complex and enhanced architecture. All required components (processes) are preconfigured according to server license code and available from the ISETUP installation.

MVS TCB

PDS Process

Description

SSCTL

edapth

Main control

ATMTCP

edapgwy

TCP listener

ATMLU62

---

LU62 listener

DFMATM

edapgwy

Deferred listener

---

edapgwy

HTTP listener (WC)

EDACONS

---

LU2 console

TSCOM3

tscom3

Service Agent

HLISNK

hlisnk

Sink-machine (FDS)

---

tscom300

start, stop, savediag, traceon, etc.

---

scheduler

DataMigrator scheduler

---

edachkup

Monitors crashes, refreshes, shutdown, mrm (cpu_limit, agent_idle_limit, session_idle_limit)

---

edaplog

Writes edaprint.log

---

tsqprx

UNIX commands processor

Note:

  • On MVS, HLISNK runs in a separated JOB from the server.
  • The number of tscom3 processes/TCBs corresponds to the number of agents currently started.
  • PDS server does not use Shared Memory, so tscom300 process can not process commands originated from other jobs (like ISTOP, ITRCON, ITRCOFF). To issue commands to the server either use the Web Console or use Operator Modify commands.
  • Except for tscom3, all processes/TCBs of each type are unique (1 per server).



x
Typical Server JCL

MVS:

// <jobcard>
//EDASERVE   EXEC PGM=SSCTL
//STEPLIB    DD  DISP=SHR,DSN=qualif.EDALIB.LOAD
//ERRORS     DD  DISP=SHR,DSN=qualif.EDAMSG.DATA
//IBIFEX     DD  DISP=SHR,DSN=qualif.EDARPC.DATA  
//FOCEXEC    DD  DISP=SHR,DSN=userlib.FOCEXEC 
//IBIMFD     DD  DISP=SHR,DSN=qualif.EDAMFD.DATA 
//MASTER     DD  DISP=SHR,DSN=userlib.EDAMFD.DATA 
//ACCESS     DD  DISP=SHR,DSN=qualif.EDAAFD.DATA 
//           DD  DISP=SHR,DSN=userlib.EDAAFD.DATA 
//HTML       DD  DISP=SHR,DSN=userlib.HTML.DATA
//GIF        DD  DISP=SHR,DSN=userlib.GIF.DATA 
//IBISNAP    DD  SYSOUT=X
//EDAPRINT   DD  SYSOUT=*  
//CAR        DD  DISP=SHR,DSN=userlib.CAR.FOCUS
//QAVSM01    DD  DISP=SHR,DSN=userlib.QAVSM01.VSAM    
//EDACSG     DD  DISP=SHR,DSN=qualif.INSTALL.DATA(FFSCFG)
//EDASERVE   DD  DISP=SHR,DSN=qualif.INSTALL.DATA(FFSSERV)
//*EDACONS   DD  DISP=SHR,DSN=qualif.INSTALL.DATA(FFSCONS)

Note: SSCTL startup JCL corresponds to IRUNJCL member on iadmin.servertype.DATA on PDS server. The only lines that need to be copied to IRUNJCL are those containing userlib allocations (shown here highlighted).

This is just one example. You may create additional allocations according to need. In this example, allocations highlighted are customer allocations, while the others are using SSCTL installation and customization libraries. SSCTL JCL might have in-stream allocations replacing the data sets, for example:

//EDACSG  DD *
NAME        = iWay Data Adapter for MVS 5.x 
NODE = TCPIN
  BEGIN
    PROTOCOL      = TCP
    CLASS         = AGENT
    SERVICE       = 2426        ;Port number server is listening
;   CONNECT_INTERVAL = 50
  END
/*


x
Typical Server Configuration File

MVS (pointed by //EDASERVE DD)

*****************  Global Settings ***************************  
LONGSYNM      = ON
UNIQUE        = LOGID
EXTSEC        = ON
FASTLOAD      = **AUTO**
LICENSE       = 100-111-0422
SZERO=YES
IMSPZP=01
DBCTL=START
IMSSEC=ON
IMSCLASS=PCICSPSB  
***************  Service Level Settings ***********************  
SERVICE                = EDAUSER
PROGRAM                = TSCOM3
NUMBER_READY           = 0
REFRESH_LIMIT          = 100
MAXIMUM                = 2  
SERVINIT               = *,++ 
DYNAM ALLOC FILE EDASPROF DA qualif.EDAPROF.DATA(FEDAYHC) SHR REU 
DYNAM ALLOC FILE EDAPROF DA qualif.EDAPROF.DATA SHR REU 
DYNAM ALLOC FILE IBITRACE DA qualif.EDACTL.DATA(NOTRACE) SHR REU
 ++

//EDASERVE on SSCTL corresponds to EDASERVE member on iadmin.servertype.CFG on PDS server.

SERVINIT contains DYNAM ALLOC to be performed at Service initialization (like standard EDASPROF, EDAPROF, IBITRACE and STDOUT). Any additional customer allocations (like FOCUS or VSAM files) made on SSCTL SERVINIT must be copied to PDS SRVINIT member on iadmin.servertype.CFG.

Notice that SSCTL EDASPROF was not a server profile, but actually a service level profile. PDS EDASPROF member is a server profile. PDS server also has service level profiles pointed by profile= setting on EDASERVE member. For more information, see Service Level Settings.

If SSCTL server is running APP ENABLE, SERVINIT can also contain APPROOT=<applications HLQ>. On ISETUP installation, you should use the same existing SSCTL APPROOT value to install the PDS server.



x
MVS Global Configuration Settings and Their PDS Equivalents

PDS server should be configured using the Web Console. The purpose of the following chart is to provide information where settings reside so you can configure PDS accordingly.

MVS (EDASERVE DD)

PDS

EXTSEC=ON APFAUTH=INTERNAL
TASKLIB=<ddname>

EDAEXTSEC=OPSYS/PTH/DBMS/LDAP/OFF

SMFNUM=249

smf_recno=249

FASTLOAD=**AUTO**

Not applicable

LONGSYNM=ON

DYNAM SET LONGSYNM

LICENSE=xxx-xxx-xxxx

license=xxx-xxx-xxxx-xx

STORAGEABOVE = 4096
STORAGEBELOW = 512

Not applicable

CONSSEC=     CONSOPER=
CONSDTL=     CONSUSER=

admin_level=     admin_password=
(on admin.cfg through the Web Console)

IMSPZP=     DBCTL=
IMSSEC=     IMSCLASS=

node on odin.cfg (created automatically through the Web Console Adapter configuration)

UNIQUE=LOGID

max_connections_per_user=

Note:



x
Service Level Settings

The following table lists the MVS Service Level Configuration Settings and their PDS equivalents.

MVS (EDASERVE DD)

PDS

WLM_ENCLAVE_TRNAME=
PRTYGROUP=

wlm_enclave_trname=

LE_STACK=BELOW

Not supported

SERVINIT=

profile=<service_level_profile>

SZERO=YES

szero=y

MEMORY_LIMIT_ABOVE=
MEMORY_LIMIT_BELOW=

memory_limit=
memory_limit_below=

SOS_PERCENT=

Not supported

IDLELIM=
IDLE_AGENT_LIMIT=

idle_session_limit=
idle_agent_limit=

REFRESH_LIMIT=

agent_refresh=

CONNECT_INTERVAL=

queue_limit=     maximum_q=

APPROOT=

approot=

Note:

  • PDS setting resides on EDASERVE(//EDACCFG) file, unless otherwise noted below.
  • wlm_enclave_trname= has the exact same implementation on PDS as the MVS equivalent and performs the same function as the old PRTYGROUP= setting.
  • LE_STACK= is not supported under PDS. If you are running subroutines linked with AMODE(24), they must be re-linked with AMODE(31).
  • profile= can be used to specify a focexec file which will be executed during agent startup, for example, baseapp/myprof (myprof being of type focexec). Execution order is edasprof, service profile, group profile and finally user profile.
  • Regarding MEMORY_LIMIT_=, the MRM=ON setting in MVS became obsolete on PDS. The presence of the memory_limit= keywords enables the feature automatically.
  • The edaprint.log will display messages when memory available is insufficient, but they are currently not echoed to MVS system log. Also PDS server will only issue messages when there's no more memory available to start an agent. SOS_PERCENT= used to tell operators when a critical situation was about to occur.
  • CONNECT_INTERVAL resides on MVS //EDACSG file. queue_limit= is the equivalent and limits how long a connection waits in queue. maximum_q= limits how many connections can be queued.
  • approot= is a global configuration setting (not in the service level scope).
  • Keywords that did not change functionality or parameter names (other than uppercase to lowercase) are omitted. For example, DEPLOYMENT = deployment, NUMBER_READY = number_ready, and so on.



x
Typical Server Profile

MVS (pointed by //EDASERVE DD)

-* FF Server FEDAYHC Profile generated on 27 Sep 2001 at 14:23:59
-*************** Allocate the catalogue files ******************
   DYNAM ALLOC FILE SYSCOLLN SHR REU DA qualif.SYSCOLLN.FOCUS
   DYNAM ALLOC FILE SYSCOLLT SHR REU DA qualif.SYSCOLLT.FOCUS  
 DYNAM ALLOC FILE SYSRPC   SHR REU DATASET qualif.SYSRPC.FOCUS 
-*************** Allocate the synonym files ********************
-* DYNAM ALLOC FILE EDASYNA  SHR REU DATASET qualif.EDAAFD.DATA
-* DYNAM ALLOC FILE EDASYNM  SHR REU DATASET qualif.EDAMFD.DATA
-* DYNAM ALLOC FILE EDASYNR  SHR REU DATASET qualif.FOCEXEC
-***************************************************************
-* JOINTYPE sets the method of processing cross platform joins:
-*   NESTEDLOOP - Perform a nested loop join on second set.
-*   SORTMERGE  - Perform a merge of the second set.
-* SQL EDA SET JOINTYPE SORTMERGE
-***************************************************************
-* EXORDER is execution order for RPCs.  Possible values are:
-*   PGM     - Search for 3gl RPCs only
-*   FEX     - Search for 4gl RPCs only
-*   PGM/FEX - Search for 3gl RPCs. If not found search for 4gl.
-*   FEX/PGM - Search for 4gl RPCs. If not found search for 3gl.
   SET EXORDER=FEX/PGM  
-* End of profile generated on 27 Sep 2001 at 14:23:59

Catalog files are automatically added to IRUNJCL at installation and should be ignored as a migration task.

In this example, allocations highlighted are the only ones being executed. The lines that include "-*" characters are comments. If you never made customizations from the standard EDASPROF supplied with SSCTL, than there will be no settings to manually copy to EDASPROF member of iadmin.servertype.PRF on PDS.

JOINTYPE line would appear uncommented for HUB servers.

For APP ENABLE SSCTL servers, the following lines would also be present:

EDASYNM, EDASYMA and EDARPC allocations should be added to IRUNJCL as part of the concatenations for MASTER, ACCESS and FOCEXEC, respectively, as shown in the following example.

//IRUNJCL    PROC
//TSCOM300 EXEC PGM=TSCOM300
//STEPLIB    DD DISP=SHR,DSN=iadmin.P.HOME.LOAD
//*TASKLIB   DD DISP=SHR,DSN=iadmin.P.HOME.LOAD
//*SAMPLE MASTER, ACCESS, FOCEXEC
//MASTER     DD DISP=SHR,DSN=<qualif>.EDASYNM.DATA
//           DD DISP=SHR,DSN=<qualif>.MASTER.DATA
//ACCESS     DD DISP=SHR,DSN=<qualif>.EDASYNA.DATA
//           DD DISP=SHR,DSN=<qualif>.ACCESS.DATA
//FOCEXEC    DD DISP=SHR,DSN=<qualif>.EDARPC.DATA
//           DD DISP=SHR,DSN=<qualif>.FOCEXEC.DATA


x
Server Profile


x
User Profiles


x
PDS - DYNAM SET TEMP[ALLOC]

There is no migration task here as the default value is ideal for most applications. This topic is included here to give awareness of this new command. To determine the allocation for your temporary files, issue the following command:

DYNAM SET TEMP[ALLOC] {HFS|MVS|HIPER|MEMORY}

where:

HFS

Allocates temporary files to the hierarchical file system. (Default in HFS Server; not applicable for PDS server.)

MVS

Allocates temporary files to MVS data sets. (Default in PDS server.)

HIPER

Allocates temporary files to hiperspace. Limited implementation with no spill control (agent will crash if memory is exceeded).

MEMORY

Allocates temporary files to main storage.Limited implementation with no spill control (agent will crash if memory is exceeded).

Note: DYNAM SET TEMP command does not cause an allocation to be made, but simply determines where files should be allocated so that, when an allocation request is made, it will issue the proper command (DYNAM or FILEDEF) according to the location (MVS, HFS, HIPER or MEMORY). A DYNAM already in place for a given DDNAME will be respected.



x
Allocation Order

Allocations are searched in the following order:

  1. JCL ALLOCATION.
  2. DYNAM ALLOCATION.
  3. FILEDEF (for non-FOCUS data sources)

    or

    USE (for FOCUS data sources).

  4. DATASET= in MASTER file.
  5. APP PATH (server runs APP ENABLE by default).


Example: Reusing Temporary Allocations With Explicit DYNAMs and HIPER
DYNAM ALLOC FI MYHOLD SPACE 1 1
DYNAM ALLOC FI HOLDMAST SPACE 1 1 DIR 10
DYNAM SET TEMP HIPER
TABLE FILE CAR PRINT COUNTRY
ON TABLE HOLD AS MYHOLD
END

Note:



Example: Reusing Temporary Allocations With No Explicit Allocations

For future allocations in DASD:

DYNAM SET TEMP MVS
TABLE FILE CAR PRINT COUNTRY
ON TABLE HOLD AS MYHOLD
END

Note: The commands above will cause automatic DYNAM allocation for MYHOLD and HOLDMAST as MVS temporary files.

To issue DYNAMs for MYHOLD and HOLDMAST:

TABLE FILE CAR PRINT COUNTRY CAR 
ON TABLE HOLD AS MYHOLD
END

Note:



x
MVS - IBITABLA

Default sample IBITABLA is shipped on MVS qualif.EDALIB.DATA.

*...+....1....+....2....+....3....+....4....+  
HOLD     CYLS   5  10                      3, 
HOLDMAST TRKS   5   5 36         NOHIPER    , 
SAVE     CYLS   5  10                      3, 
REBUILD  CYLS   5  10                      3, 
FOCSML   CYLS   5   5                      2,  
FOCUS    CYLS   5   5                      1, 
FOCSTACK TRKS   5   5                      2,  
FOCSORT  CYLS   5   5                      1, 
OFFLINE  CYLS           A                  , 
SESSION  TRKS   5   5                      2,  
FOCCOMP  TRKS   5   5 12                    , 
HOLDACC  TRKS   5   5 12                    , 
FMU      TRKS   5   5 12                    ,
TRF      TRKS   5   5 12                    , 
FOCPOOLT CYLS   5  20            NOHIPER   4,
FUSION   CYLS   5  50            NOHIPER   4,
MDI      CYLS   5  20            NOHIPER   4,
FOC$HOLD CYLS   5   5                      2,
EXTINDEX CYLS   5   5                      2,

Note:

The following table lists and describes the columns in IBITABLA member.

Columns

Length

Description

01-08

8

Class of file - DD name

10-13

4

Allocation units (CYLS, TRKS)

15-17

3

Primary extent

19-21

3

Secondary extent

23-24

2

Number of directory blocks
(blank specifies a sequential file - 0 is invalid)

26-26

1

SYSOUT class

28-33

6

Volume serial on which to allocate

35-42

8

Type of unit to allocate (for example, 3390, DASD, NOHIPER*, and so on)

44-55

2

Unit count



x
PDS - DYNAM SET TEMP[ALLOC] FOR

To alter the default allocation parameters for temporary files for MVS data sets, issue the following command:

DYNAM SET TEMP[ALLOC] FOR type dynam_parms

where:

type

Is one of the following: HOLDACC, HOLDMAST, HOLD, SAVE, REBUILD, FOCUS, FOCSORT, OFFLINE, FOCCOMP, FMU or TRF.

dynam_parms

Are regular DYNAM ALLOC parameters to be used as default for that type. Note that DCB parameters, if provided here, will be ignored, since they must be compatible with the file type being written.

This is similar to the functionality of IBITABLA in the MVS Server. The defaults should be overwritten for all cases when, in older versions, a private copy of IBITABLA existed containing different values. DYNAM SET TEMP FOR commands can be issued in any focexec, but IBI recommends issuing them on either profiles or SRVINIT member.

Defaults for HOLDMAST, HOLDACC, FOCCOMP, FMU and TRF:

TRKS SPACE 5 5 DSORG PO DIR 36 NEW DELETE REU

Defaults for REBUILD:

TRKS SPACE 5 10 NEW DELETE REU

Defaults for HOLD, FOCSORT and all other types:

CYLS SPACE 5 10 DSORG PS NEW DELETE REU

Examples:

DYNAM SET TEMP FOR HOLD TRACKS SPACE 50 100
DYNAM SET TEMP FOR FOCUS DATACLASS xxx STORCLASS yyy
DYNAM SET TEMP FOR HOLDMAST DSNTYPE LIBRARY CYLS SP 1,1


x
MVS - IBIAPPLA

Default sample IBIAPPLA is shipped on MVS qualif.EDALIB.DATA.

class recfm lrecl blksz units prim sec dir postfix 
* 
FOCEXEC   VB  4096   27998  TRKS  50  50  50 FOCEXEC.DATA 
MASTER    FB  80     22000  TRKS  50  50  50 MASTER.DATA
ACCESS    FB  80     22000  TRKS  50  50  50 ACCESS.DATA 
FOCSTYLE  FB  80     22000  TRKS  50  50  50 FOCSTYLE.DATA 
HTML      VB  4096   27998  TRKS  50  50  50 HTML.DATA 
GIF       FB  1024   27648  TRKS  50  50  50 GIF.DATA 
MAINTAIN  VB  4096   27998  TRKS  50  50  50 MAINTAIN.DATA 
WINFORMS  VB  4096   27998  TRKS  50  50  50 WINFORMS.DATA  
FOCCOMP   VB  32756  32760  TRKS  50  50  50 FOCCOMP.DATA  
ETG       VB  4096   27998  TRKS  50  50  50 ETG.DATA  
XML       VB  4096   27998  TRKS  50  50  50 XML.DATA

Note:



x
PDS - DYNAM SET APP FOR

To create application libraries, issue the following:

DYNAM SET APP FOR filetype [SKIP|CREATE][POSTFIX a.b] [parms]

where:

filetype

Are the component types that may be affected by this command: ACCESS, DTD, ETG, FOCCOMP, FOCEXEC, FOCSTYLE, GIF, HTML, MAINTAIN, MASTER, SQL, WINFORMS, XML, XSD. You must issue a separate command for each component type you wish to affect.

SKIP

Indicates that the designated file type should not be created when the APP CREATE command is issued.

CREATE

Creates the designated file type when the APP CREATE command is issued. This is the default setting.

POSTFIX

Specifies the lower level qualifier of the DSN (data set name) for the component type. The APPROOT value is used to complete the full DSN, which is expressed as

approotvalue.appname.component_type

The default value for component_type is filetype.DATA.

parms

Are the allocation parameters you can set. The default parameter values are:

Filetype

Parms

ACCESS

RECFM FB TRKS LRECL 80 BLKSIZE 22000 SPACE 50 50 DIR 50

DTD

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

ETG

RECFM FB TRKS LRECL 80 BLKSIZE 22000 SPACE 50 50 DIR 50

FOCCOMP

RECFM VB TRKS LRECL 32756 BLKSIZE 32760 SPACE 50 50 DIR 50

FOCEXEC

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

FOCSTYLE

RECFM FB TRKS LRECL 1024 BLKSIZE 27648 SPACE 50 50 DIR 50

GIF

RECFM VB TRKS LRECL 1028 BLKSIZE 27998 SPACE 50 50 DIR 50

GIF type creates libraries for GIF and JPG files.

HTML

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

MAINTAIN

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

MASTER

RECFM FB TRKS LRECL 80 BLKSIZE 22000 SPACE 50 50 DIR 50

SQL

RECFM VB TRKS LRECL 32756 BLKSIZE 32760 SPACE 50 50 DIR 50

WINFORM

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

XML

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

XSD

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

This is similar to the functionality of IBIAPLA in the MVS Server. The defaults should be overwritten for all cases when, in older versions, a private copy of IBIAPPLA existed containing different values. DYNAM SET APP FOR commands can be issued in any focexec, but IBI recommends issuing them on either profiles or SRVINIT member.



Example: DYNAM SET APP FOR Syntax

Note: All attributes (DCB, space and low-level qualifier) could be changed at once for a given type. These are simple examples.



x
Long Synonym Support

These are the long names supported.

Long Name

Member Name (Master and/or Access)

EMPLOYEES_ACCOUNTING

EMPLOY{0

EMPLOYEES_DEVELOPMENT

EMPLOY{1

EMPLOYEES_DISTRIBUTION

EMPLOY{2

EMPLOYEES_FINANCE

EMPLOY{3

$VIRT=<long_name> as 1st line of MASTER and/or ACCESS. For example, EMPLOY{0).

$ VIRT=EMPLOYEE_ACCOUNTING$ Created from EMPLOYEE MASTER
  FILENAME=EMPLOYEE_DATA,
  SUFFIX=FOC
  SEGNAME=EMPINFO,SEGTYPE=S1
  FIELDNAME=EMP_ID, ALIAS=EID, FORMAT=A9, $
  FIELDNAME=LAST_NAME, ALIAS=LN, FORMAT=A15, $


x
Syntax: How to Implement Long Synonyms in MVS
  • Permanent FOCUS, FLAT, VSAM by LONGNAME keyword on DYNAM ALLOC/FREE:
    DYNAM ALLOC FI CAR LONGNAME CARFILELONG1
       DA qualif.CAR.FOCUS SHR REU
  • Permanent Adapter files, for example, DB2:
    CREATE SYNONYM DB2TABLELONG1 DBMS DB2
       FOR userid.DB2TABLELONG
    END
  • Temporary files, using ON TABLE HOLD FORMAT xxx AS <long_name>:
    • Feature enabled by LONGSYNM=ON on EDASERVE DD2.
    • No support for FDS (Sink) Focus Files or DATASET= on MASTER.

Note:

  • Long file names (synonyms) can be up to 64 characters long.
  • LONGSYNM=ON became default on MVS 5.3.x servers and no longer had to be coded.



x
Syntax: How to Implement Long Synonyms in PDS
  • Permanent FOCUS, FLAT, VSAM by long DDNAMES accepted on DYNAM and in ? TSO DDNAME:
    DYNAM ALLOC FI CARFILELONG1 DA qualif.CAR.FOCUS SHR REU
  • Permanent Adapter files, for example, DB2:
    CREATE SYNONYM baseapp/DB2TABLELONG2 DBMS DB2
       FOR userid.DB2TABLELONG
    END
  • Temporary files, using ON TABLE HOLD FORMAT xxx AS <long_name>:
    • Feature enabled by DYNAM SET LONGSYNM setting, explained in the next topic.
    • Support for PDS FDS(Sink) Focus Files and DATASET= on MASTER.

Note:

  • Long file names (synonyms) can be up to 64 characters long.
  • The CREATE SYNONYM syntax employed above was also available on MVS server, when running APP ENABLE mode. APP ENABLE is the default and recommended mode to run PDS server.
  • The PDS FDS service is automatically configured as part of the PDS server. Legacy MVS FDS (Sink Machine) does not support Long file names.



x
PDS - DYNAM SET LONGSYNM

To determine the allocation for your long synonyms (metadata), issue the following command:

DYNAM SET LONGSYNM {HFS|MVS|MATCH}

where:

HFS

Long synonyms will be created on HFS. (not applicable to PDS).

MVS

Long synonyms will be created on MVS (default in PDS).

MATCH

Is the same as for MVS, but short aliases must match between the Master File and the Access File (additional CPU processing to synchronize member names at creation).

Note: Setting is only required at creation time. For HOLD files, DYNAM SET TEMP MVS is also needed. In other words, a FOCEXEC running against existing long synonyms allocated in DD MASTER and ACCESS do not require this setting. To Create SYNONYMS through the Web Console, both DYNAM SET LONGSYNM MVS and DYNAM SET TEMP MVS must be set (they are the default values in PDS).



x
User Data File Allocations

The following topics describe how to allocate user data files.



x
Syntax: How to Allocate FOCUS Files

FOCUS files can be allocated in the following ways:

  • IRUNJCL:
    1. //CAR DD DISP=SHR,DSN=qualif.CAR.FOCUS
    2. //CAR DD DISP=SHR,DSN=qualif.GDG.FOCUS(0)
  • DYNAM:
    1. DYNAM ALLOC FI CAR DA qualif.CAR.FOCUS SHR REU
    2. DYNAM ALLOC FI CAR DA qualif.GDG.FOCUS(-1) SHR REU
  • USE command:
    1. Renaming a Master File:
      USE CAR1 AS CAR
      END
    2. Concatenating Master Files:
      USE CAR1 AS CAR
      CAR2 AS CAR
      END
    3. Accessing Files on FDS (Sink Machine):
      USE CAR1 ON FOCSU01
      END
    4. Application Allocation:
      USE baseapp/car.foc AS CAR
      END

Note:

  • CAR ddname was used arbitrarily.
  • When a DYNAM or JCL allocation is present, USE command is not required, unless some other operation is required, as shown in these examples.
  • Applications are mapped to PDS files, not HFS directories, despite notation used in the command.



x
Syntax: How to Allocate FLAT (Sequential) Files

Flat (Sequential) files can be allocated in the following ways:

IRUNJCL:

  1. //FLAT DD DISP=SHR,DSN=qualif.FLAT.DATA
  2. //FLAT DD DISP=SHR,DSN=qualif.GDG.DATA(-2)
  3. //FLAT DD DISP=SHR,DSN=qualif.PDS.DATA(MEMBER01)

DYNAM:

  1. DYNAM ALLOC FI FLAT DS qualif.FLAT.DATA SHR REU
  2. DYNAM ALLOC FI FLAT DS qualif.GDG.DATA(+1) NEW SPACE 1,1 -
    TRK REFDSN qualif.GDG.BASE NEW CATLG TRTCH COMP
  3. DYNAM ALLOC FI FLAT DS qualif.PDS.DATA(MEMBER01) SHR REU

FILEDEF Command:

  1. To MVS File:
    FILEDEF FLAT DISK “//’qualif.FLAT.DATA’”
  2. Application Allocation:
    FILEDEF FLAT DISK baseapp/flat.ftm

Note:

  • FLAT ddname was used arbitrarily.
  • FILEDEF is valid for sequential files, PDS members and GDG files instead of DYNAM or JCL allocation. VSAM files CANNOT be read using FILEDEF.
  • Applications are mapped to PDS files, not HFS directories, despite notation used in the commands.



x
Syntax: How to Allocate VSAM Files

VSAM files can be allocated in the following ways:

  • IRUNJCL:

    Requires szero=y on EDASERVE, member of iadmin.servertype.CFG, for concurrent access.

    //VSAM1  DD DISP=SHR,DSN=qualif.VSAM.CLUSTER
  • DYNAM:
    DYNAM ALLOC FI VSAM1 DS qualif.VSAM1.CLUSTER SHR REU

Note:

  • VSAM1 ddname was used arbitrarily.
  • You cannot use FILEDEF for VSAM files.



x
DATASET=keyword on MASTER

If a data set name satisfies one of the following conditions, the server assumes that it is an MVS fully qualified data set:

In all other cases, the name is interpreted as a as relative application reference name, translated internally by the server to the actual fully qualified data set name.

The following table shows all possible DATASET= syntaxes.

Keyword on MASTER FILE

Type

DATASET=APP1/physfile.ftm

Application relative file name

DATASET='qualif.ABC.DATA'

Fully qualified sequential data set

DATASET=qualif.ABC.DATA

Fully qualified sequential data set

DATASET=//'qualif.ABC.DATA'

Fully qualified sequential data set

DATASET=qualif.GDG.DATA(0)

Fully qualified GDG data set

DATASET=qualif.PDS.FILE(MEMBER)

Fully qualified PDS member

Note: Examples on rows 2, 3 and 4 are all equivalent.



x
Migrating Existing Applications to PDS


x
PDS - Allocating User MVS Libraries (Technique)

If each user (or a particular user) has his own set of FOCEXEC, MASTER, ACCESS, HTML, GIF, FOCPSB and FOCSTYLE, code the following on his user profile:

APP MAP userAPP mas=//dd:usermas;fex=//dd:userfex;acx=//dd:useracx;
  htm=//dd:userhtm;gif=//dd:usergif;sty=//dd:usersty;psb=//dd:userpsb;
DYNAM ALLOC FI usermas DA user.MASTER.DATA SHR REU
DYNAM ALLOC FI userfex DA user.FOCEXEC.DATA SHR REU
DYNAM ALLOC FI useracx DA user.ACCESS.DATA SHR REU
DYNAM ALLOC FI userhtm DA user.HTML.DATA SHR REU
DYNAM ALLOC FI usergif DA user.GIF.DATA SHR REU
DYNAM ALLOC FI usersty DA user.FOCSTYLE.DATA SHR REU
DYNAM ALLOC FI userpsb DA user.FOCPSB.DATA SHR REU
APP PREPEND PATH userAPP

where:

user, userfex, usermas, useracx, userAPP

Are all arbitrary names, used as examples only.

You only need to map the ddnames you are actually using. If you do not have FOCPSB libraries, for instance, you do not need to add DYNAM ALLOC commands for it.



x
FOCUS Database Server (FDS)

FOCUS Database Server is also referred to as Sink Machine. PDS Server comes pre-configured with its own Sink Machine process, and it is also able to communicate with the legacy MVS Sink machine.

This is useful as in the migration process, you may have applications already moved to the PDS server and others still running on the MVS server.

The following topics will show how Sink machines were used on MVS server as well as how to communicate with either one, using the PDS Server.

Note: You cannot manage the same file using both the legacy and current versions of the FOCUS Database Server, as it will cause enqueue conflicts.



x
MVS FOCUS Files (FDS/Sink Machine)

A DDNAME was allocated in the server JCL to point to the communications data set to be used to identify the FOCUS Database Server job on which the FOCUS files reside.

//FOCSU01 DD DSN=x.y.z,DISP=SHR

A USE statement was then issued to connect the FOCUS Master File to the DDNAME allocated to the communications file.

USE
   CAR ON FOCSU01
END


x
PDS - FOCUS Files Through the Legacy Sink


x
PDS - FOCUS Files Through the PDS FDS

If you want a FOCUS database to be managed by the current version of the FDS (FOCUS Database Server), you can allocate its data file in several ways:

Issue the following USE command in association with any of these allocation methods:

USE CAR ON FOCSU01
END


x
MSODDX: DDNAME Translation for User Subroutines

On z/OS, you can incorporate an additional routine called MSODDX into a user-written subroutine that needs to access ddnames allocated to a WebFOCUS Reporting Server, a Data Migrator Server, or a Full-function Server. MSODDX provides ddname translation services that enable external programs to access files under the ddname used by the Server.

For details see Chapter 6, Platform-Specific Commands and Features, in the Stored Procedures Reference.


Top of page

x
Accounting for PDS - SMF Records

How to:

Reference:

The server provides an optional facility to use for accounting purposes that enables you to log resource utilization on a per-user basis. This facility enables the server to generate SMF records for query-level and user-level accounting.

Server accounting requires that the server STEPLIB data sets be APF-authorized. When SMF records are generated, they contain:

You can process the SMF records using the accounting programs that exist at your site. Examples of SMF records are provided in SMF Record Format for RECTYPES 1 and 4.

In order to write SMF records, the server must be running APF authorized.

Two sample Master Files (SMFVSAM and SMFFIX) are provided for accessing accounting statistics. They reside in qualif.P.HOME.MAS.

Their difference is that SMFVSAM can be used to report directly from the system-live SYS1.MANx records, while SMFFIX can be used to report from a sequential file produced from running the SMFDUMP utility. These Master Files enable you to interpret the SMF records generated by the accounting facility using reporting requests or store procedures. Both Master Files are for logoff records only, as indicated by ALIAS=2 on the RECTYPE field entry.

A sample procedure report to query the SMF data is also provided in qualif.P.HOME.FEX(SMFMAN1).



x
Syntax: How to Enable Accounting

To enable accounting, insert the following statement into the server configuration file (edaserve.cfg):

smf_recno=smfnumber

where:

smfnumber

Is an integer in a range from 128 to 255, inclusive. This number represents the SMF number used by the accounting facility when it sends records to the SMF system.

By default, both RECTYPE pairs will be created when accounting is enabled. You can override the default by coding the following parameter on edaserve.cfg :

smf_subtype = {all|logon|query}

where:

all

Cuts all records. This is the default.

logon

Cuts logon records only (RECTYPE pair 1 and 2).

query

Cuts query records only (RECTYPE pair 4 and 5).



x
Syntax: How to Set the Accounting Field

Up to 40 characters can be supplied that appear in the SMF records field SMFOFA40. The SET BILLCODE command can be used in any support server profile to provide the account field information. The syntax is

SET BILLCODE=value              

where:

value

Is the 1–40 characters to be used on each SMF record produced.

This information can also be set dynamically from a client application by coding an RPC with the SET command and executing it with the value as a parameter. WebFOCUS users can send the SET command to the server.



x
Procedure: How to Report From SMF Data Using the Web Console

To report from SMF data using the Web Console:

  1. Go to the Web Console menu bar, select Procedures.
  2. In the left pane, open the Reports folder, then click System Management.

    The View as text and Run options are displayed.

  3. Click Run.

    You are prompted for the DSN of the SMF VSAM data set to be reported from and the smf_recno value used to produce the SMF records.

    The report is displayed.



x
Reference: SMF RECTYPES

There are five RECTYPE values defined to produce SMF records:

RECTYPE

Description

1

Indicates a start of task record. When included in a report, these statistics tell when a task initiation occurred, and are of no particular use in chargeback. By pairing start and end of task records for all tasks within a time period, statistics, such as average active time, peak task count, and average task count, can be determined. These values can be used for future capacity planning activities for the server.

2

Indicates the start of a task record. When included in a report, these statistics tell when a task termination occurred. These records are cut for both publicly and privately deployed services and contain statistics for the subtask as a whole.

For privately deployed services, RECTYPE (2) records contain statistics associated with a single user connection.

4

Begin query. (Record layout is the same as RECTYPE (1).

5

End query. (Record layout is the same as RECTYPE (2).



x
Reference: SMF Record Format for RECTYPES 1 and 4

The record format for RECTYPES 1 and 4 of the SMF records written by the server is defined below. The format is provided in the system 390 assembler DSECT form.

SMFON    DSECT
         SPACE
*----------------------------------------------------*
*  USAGE ACCOUNTING SMF RECORD LAYOUT FOR LOGON RECORDS.              *
*                                                                     *
*  THIS IS THE DSECT DESCRIBING THE SMF RECORD WHICH IS PASSED TO     *
*  YOUR EXIT ON AT USER LOGON TIME.  IT IS COMPLETELY READY TO BE     *
*  WRITTEN WHEN YOUR EXIT RECEIVES CONTROL.                           *
*----------------------------------------------------*
         SPACE
*----------------------------------------------------*
*  THE FIRST TWENTY FOUR BYTES OF THE RECORD ARE THE SMF HEADER.      *
*  THESE FIELDS ARE REQUIRED IN ALL SMF RECORDS (18 BYTES FOR RECORDS *
*  WITHOUT SUBTYPES; WE USE SUBTYPES, THE HEADER IS 24 BYTES).        *
         SPACE
SMFONLEN DS    H'116'            RECORD LENGTH
SMFONSEG DS    XL2'0000'         SEGMENT DESCRIPTOR (0 UNLESS SPANNED)
SMFONFLG DS    XL1               SYSTEM INDICATOR
SMFONRTY DS    XL1               RECORD TYPE
SMFONTME DS    XL4               TIME, IN HUNDREDTHS OF A SECOND
SMFONDTE DS    PL4               DATE, 00CYYDDDF, WHERE F IS THE SIGN
SMFONSID DS    CL4               SYSTEM IDENTIFICATION
SMFONSBS DS    CL4               SUBSYSTEM IDENTIFICATION
SMFONSBT DS    XL2'0001'         SUBTYPE OF RECORD - X'0001' INDICATES X
                                 THIS IS A LOGON RECORD
         SPACE
*----------------------------------------------------*
*  THE NEXT FIELDS ARE THOSE PRESENT IN THE LOGON                     *
*  RECORD FOR THE START OF A USER SESSION.                            *
*----------------------------------------------------*
         SPACE
SMFONMSO DS    CL8               JOBNAME
SMFONJID DS    CL8               JOBID (FROM SSIBJBID)
SMFONASI DS    Y                 ASID
SMFONRV1 DS    XL2               RESERVED
SMFONUID DS    CL8               SECURITY USERID
SMFONLID DS    CL8               USERID PRESENTED AT LOGON (SAME AS    X
                                 SMFONSID UNLESS CHANGED VIA MSIDTR    X
                                 SECURITY EXIT)
SMFONRSV DS    XL8               RESERVED FOR FUTURE EXPANSION
SMFONCTI DS    XL4               RESERVED FOR FUTURE EXPANSION
SMFONSRV DS    CL8               SERVICE NAME FROM SERVICE BLOCK
SMFONRS0 DS    XL4               RESERVED FOR FUTURE EXPANSION
SMFONCNT DS    XL1               CONNECTION TYPE
         SPACE
SMFONTSO EQU   1                 CONNECTION VIA TSO
SMFONCIC EQU   2                 CONNECTION VIA CICS
SMFONVTM EQU   4                 CONNECTION VIA VTAM
SMFONPSR EQU   8
         SPACE
SMFONRS1 DS    XL3               RESERVED
SMFONID1 DS    F                 SYSPLEX ID 1
SMFONID2 DS    F                 SYSPLEX ID 2
SMFOFPID DS	    XL8               POOLED USER ID
SMFONRS2 DS    XL12              RESERVED
SMFONL   EQU   *-SMFON           LENGTH OF THE SMF LOGON RECORD


x
Reference: SMF Record Format for RECTYPES 2 and 5

The record format for RECTYPES 2 and 5 of the SMF records written by the server is defined below. The format is provided in the system 390 assembler DSECT form.

SMFOF    DSECT
         SPACE
*----------------------------------------------------*
*  USAGE ACCOUNTING SMF RECORD LAYOUT FOR LOGOFF RECORDS.             *
*                                                                     *
*  THIS IS THE DSECT DESCRIBING THE SMF RECORD WHICH IS PASSED TO     *
*  YOUR EXIT ON AT USER LOGOFF TIME.  IT IS COMPLETELY READY TO BE    *
*  WRITTEN WHEN YOUR EXIT RECEIVES CONTROL.                           *
*----------------------------------------------------*
         SPACE
*----------------------------------------------------*
*  THE FIRST TWENTY FOUR BYTES OF THE RECORD ARE THE SMF HEADER.      *
*  THESE FIELDS ARE REQUIRED IN ALL SMF RECORDS (18 BYTES FOR RECORDS *
*  WITHOUT SUBTYPES; WE USE SUBTYPES, THE HEADER IS 24 BYTES).        *
*----------------------------------------------------*
         SPACE
SMFOFLEN DS    H'168'            RECORD LENGTH
SMFOFSEG DS    XL2'0000'         SEGMENT DESCRIPTOR (0 UNLESS SPANNED)
SMFOFFLG DS    XL1               SYSTEM INDICATOR
SMFOFRTY DS    XL1               RECORD TYPE
SMFOFTME DS    XL4               TIME, IN HUNDREDTHS OF A SECOND
SMFOFDTE DS    PL4               DATE, 00CYDDDF, WHERE F IS THE SIGN
SMFOFSID DS    CL4               SYSTEM IDENTIFICATION
SMFOFSBS DS    CL4               SUBSYSTEM IDENTIFICATION
SMFOFSBT DS    XL2'0002'         SUBTYPE OF RECORD - X'0002' INDICATES X
                                 THIS IS A LOGOFF RECORD
         SPACE
*----------------------------------------------------*
*  THE NEXT FIELDS ARE THOSE PRESENT IN THE LOGOFF                    *
*  RECORD FOR THE END OF A USER SESSION.                              *
*----------------------------------------------------*
         SPACE
SMFOFMSO DS    CL8              JOBNAME
SMFOFJID DS    CL8              JOBID (FROM SSIBJBID)
SMFOFASI DS    Y                ASID
SMFOFRV1 DS    XL2              RESERVED
SMFOFUID DS    CL8              SECURITY USERID
SMFOFLID DS    CL8              USERID PRESENTED AT LOGON (SAME AS    X
                                SMFOFSID UNLESS CHANGED VIA MSIDTR    X
                                SECURITY EXIT)
SMFMEMA  DS    XL4              MEMORY ABOVE THE LINE (IN KILOBYTES)
SMFMEMB  DS    XL4              MEMORY BELOW THE LINE (IN KILOBYTES)
SMFZIIP  DS    XL4              ZIIP CPU NORMALIZED (HUNDREDTHS OF A SEC)
SMFOFSRV DS    CL8              SERVICE NAME FROM THE SERVICE BLOCK
SMFZPOCP DS    XL4              ZIIP ON CP (HUNDREDTHS OF A SEC)
SMFOFCNT DS    XL1              CONNECTION TYPE
         SPACE
SMFOFTSO EQU   1                 CONNECTION VIA TSO
SMFOFCIC EQU   2                 CONNECTION VIA CICS
SMFOFVTM EQU   4                 CONNECTION VIA VTAM
SMFOFPSR EQU   8
SMFOFCC  DS    XL3               COMPLETION CODE FOR THE TASK
SMFOFACT DS    CL8               USER ACCOUNTING INFORMATION; THIS     X
                                 FIELD CURRENTLY PASSED AS LOW VALUE
SMFOFCPU DS    XL4               CPU TIME IN HUNDREDTHS OF A SECOND
SMFOFEXC DS    XL4               COUNT OF EXCP'S
SMFOFLTM DS    FL4               LOGON DURATION IN HUNDREDTHS OF A     X
                                 SECOND
SMFPRTY  DS    XL1               PRIORITY
SMFCOMPL DS    XL1               COMPLETION TYPE
         DS    XL2               RESERVED
SMFOFID1 DS    F                 SYSPLEX ID 1
SMFOFID2 DS    F                 SYSPLEX ID 2
SMFOPID  DS    XL8               POOLED USERID
SMFOFA40 DS    CL40              FULL 40-BYTE ACCOUNTING FIELD
         SPACE
SMFOFL   EQU   *-SMFOF           LENGTH OF THE SMF LOGOFF RECORD


x
Reference: Accounting for DB2 in a Server Task

When using a server to access DB2 data, certain processing takes place within the DB2 address space and is governed by DB2's chargeback system. If a user requests data from DB2, the server passes the request to the DB2 subsystem. The DB2 subsystem then processes the request, performing such tasks as retrieving rows and aggregating the data. It generates the answer set, and passes the output back to the server. The server then performs any joins and formatting which have not been performed by DB2 to satisfy the original request.

Charges incurred while the request was being processed by the DB2 subsystem are added to the charges accumulated in the server task that originated the request for processing. If the server accounting is enabled, these charges are associated with the user logon and security IDs in the SMF records described earlier.


Top of page

x
Performance Considerations for PDS

In this section:

There are several ways in which you can improve the server performance:



x
Server Initialization Commands Configured in SRVINIT Member

It is possible to specify DYNAM commands in member SRVINIT of the data set referenced by //EDACCFG DD in IRUNJCL. These commands will be executed during server startup and will be in effect until the server is shut down. You can execute the following DYNAM commands from SRVINIT:



x
Running the Server in a Non-Swappable Address Space

We recommend that you run the server in a non-swappable address space. In order to make the server address space permanently non-swappable, add the following entry to SYS1.PARMLIB(SCHEDxx):

PPT PGMNAME(TSCOM300)         /* PROGRAM NAME */
NOSWAP                        /* NON-SWAPPABLE */
CANCEL                        /* CAN BE CANCELLED */

Do not use the KEY 0 parameter, or any other parameter (such as NOPASS), unless the system programmer completely understands the consequences of adding the parameter.

All local spawn transactions will perform in the mode of the server. For example, if the server address space is non-swappable, all local spawn execute as non-swappable.

The server executes limited non-local spawn, such as when the user executes a UNIX system command. Non-local spawn execute as swappable.

The server never executes a fork subroutine. (A fork subroutine creates a new process. The new process, called the child process, is an almost exact copy of the calling process, which is called the parent process.)



x
Workload Manager

Although the server may run in a specific performance group, transactions submitted by server agents may perform differently than the server by adding the following keyword to edaserve.cfg:

wlm_enclave_trname = WLM_transaction_name          

where:

WLM_transaction_name

Can be up to 8 characters.

This is a service-level keyword.

Using this setting, the task will join a Workload Manager (WLM) enclave when a request starts, and leave the enclave when the request finishes. This gives WLM control of the dispatching priority of the task. The transaction rules defined on WLM will determine the default service class assigned to this transaction, and that service class will determine how the request runs.

This feature helps to balance a workload so that a long request will not affect a short request. This can be achieved through WLM rules designed to lower the priority of a long request after a certain period of time. Without this feature, all requests share the region priority.

The transaction name passed in this keyword must match one defined in the WLM Classification Rules for the Job Entry Subsystem (JES). A corresponding WLM Service Class pointed to by this rule will then be associated with this service.

The classification rules for JES must be used even if the server is started as a started task. The subtasks are always run under JES.

For example, you would include the following in edaserve.cfg:

SERVICE = DEFAULT
 
BEGIN
wlm_enclave_trname = IWAYFAST
.
.
.
END

The WLM definition is:

Subsystem Type JES - Batch Jobs
Classification:
 
Default service class is PRDBATLO
There is no default report class.
 
  Qualifier  Qualifier      Starting       Service   Report
# type       name           position       Class     Class
- ---------- -------------- ---------      --------- --------
1 TN         IWAYFAST                      EDAQRYHI

WLM sub-rules (levels 2 and above) are supported. For a server request to join an enclave in a particular service class, the names of all rule qualifiers below our transaction name are checked. For example, consider the following WLM definition:

Subsystem Type JES - Batch Jobs
Classification:
 
Default service class is PRDBATLO
There is no default report class.
 
  Qualifier Qualifier     Starting Service  Report
# type      name          position Class    Class
- --------- ------------- -------- -------- --------
1 SSC       PRDMVS                 PRDDFLT
2 TN        IWAYFAST               EDAQRYHI

In this particular case, the qualifier 1 type is SSC (Subsystem Collection), and a server request will only join the enclave IWAYFAST if it is running on a particular LPAR in the SYSPLEX. This qualifier (PRDMVS) must match the XCF group definition: issue $DMASDEF (for JES2) and check the value of XCFGRPNM field.

You can handle WLM scheduling environments by defining them to WLM and then adding the JOB statement parameter SCHENV=xxxxx to the ISTART JCL.


Top of page

x
Frequently Asked Questions for PDS

Q: Why might someone want to use the PDS deployment?

A: PDS deployment provides the same rich level of features as the HFS-deployed server, including the Web Console, but removes the requirement for interaction with Unix System Services at installation and run time. It deploys the server software in partitioned data sets. Configuration and user-created source files, such as procedures and metadata, are also stored in PDS libraries.

Administration of the server, from a systems perspective, has been streamlined to match that of the classic MVS version of the server (also known as the SSCTL server). There are fewer user ID requirements for installing and operating the PDS-deployed server than the HFS-deployed version, and security management has been simplified.

Q: Does this replace the older MVS server (also known as SSCTL)?

A: The z/OS server with PDS deployment is a migration path from the older MVS server.

Q: Can one refresh a server's installation software that had been deployed one way with software using other type of deployment?

A: No. Each deployment type is independent of the other with regards to installation.

Q: Can both deployments of the server coexist on one z/OS system?

A: Yes, if your license agreement allows for this.

Q: Can one configure two server instances of the same server, one instance an HFS/USS deployment, and the other a PDS deployment?

A: No. Although the media and installation are unified, once the base server software is installed, the two deployment types run separately.

As with the HFS/USS deployment, the PDS deployment can have many instances running from the same EDAHOME set of libraries.

Q: Can I monitor server startup by checking the MVS SYSLOG?

A: Yes.

The following messages are written to the SYSLOG when

Q: What, if anything, does the PDS deployment not support? In what installation implementation?

A: The PDS deployment of the server currently does not support the following functions:


Top of page

x
Third-Party Software and Licenses

In this section:

As of Version 7 Release 6.8, to address display of third-party software license requirements, a license option has been added to the Help menu located on the Web Console. This section describes the third-party software and includes references to the full licenses included in Information Builders and Third-Party Licenses.



x
OpenFlex SDK

OpenFlex SDK is included by Information Builders for use with its HOLD FORMAT FLEX feature. This distribution is subject to the terms and conditions of the Mozilla Public License Version 1.1.

For more information, see Zip Archiver License or visit our website http://www.informationbuilders.com.


Top of page

x
Troubleshooting for PDS

How to:

Reference:

If you have a problem and cannot resolve it yourself, contact Customer Support Services as described in Information You Should Have and Customer Support. In addition, supply the following information to Customer Support Services:

If you have a troubleshooting suggestion and you think others will find it helpful, we invite you to send it to us, as described in How to Add Your Problem to the Troubleshooting Guide. We will consider including your problem in a future release of this manual.



x
Reference: Problem: The Server Abends With a U4039 Code

Problem: The server abends with a U4039 code.

Cause: This is a generic abend.

Solution: Find out what caused the abend by checking the edaprint.log file, SYSOUT ddname, and the MVS system log.



x
Procedure: How to Generate a Server Trace

To generate a server trace:

  1. Turn tracing on by doing one of the following:
    • Going to the Web Console menu bar, selecting Workspace, and then Enable Traces.
    • Starting the server by running the ITRCON JCL member.
    • On the MVS Console or SDSF, issue the following operator MODIFY command

      F jobname , -traceon

      where jobname is the job under which the server is running.

  2. Reproduce the problem.
  3. Submit the ISAVEDIA member to produce additional diagnostic information.
  4. Send the server JES log, and the ISAVEDIA JES log, to Customer Support Services.


x
Procedure: How to Generate a System Dump

To generate a system dump:

  1. Allocate DDNAME SYSMDUMP pointing to the data set with the following DCB parameters:
    RECFM=FB,LRECL=4160,BLKSIZE=4160.
  2. To get the first dump, add the parameter FREE=CLOSE to your DD statement. The DD statement should appear as follows:
    //SYSMDUMP DD DISP=SHR,DSN=MYID.EDAPTH.SYSMDUMP,FREE=CLOSE
  3. To get the last dump, the statement should appear as follows:
    //SYSMDUMP DD DISP=SHR,DSN=MYID.EDAPTH.SYSMDUMP

    Only two IDs must have privileges to write into this data set: ISERVER and IADMIN. General server users DO NOT need read or write access to the SYSMDUMP data set.

  4. To prevent abendaid from intercepting the dump, add:
    //ABNLIGNR DD DUMMY
  5. To prevent Language Environment from intercepting the dump, specify:
    EDADUMPOPT=UAIMM in EDAENV DD

    This enables you to get more accurate information reflecting the moment the abend actually occurs.

  6. Save the entire job output for the server (including JES logs), and send it to Customer Support Services.

Instead of using JCL allocations to add SYSMDUMP, the procedure described below can be used alternatively.



x
Procedure: How to Add JCL Allocations to a Running Server

A z/OS operator can issue modify commands from the z/OS system console to allocate DDNAMES to the server without restarting it. This procedure is useful if you need to re-allocate a file that was freed to allow a batch overnight utility to run, or perhaps to add SYSMDUMP allocation to a running server.



x
Syntax: How to Allocate a Data set From the z/OS System Console
F <iway_server_jobname/started task>,DYNAM ALLOC FI <ddname> DA <dsname> 
<optional dynam parameters>


Example: Allocating a VSAM Data set
F IWAY2,DYNAM ALLOC F VSAMFILE DA VSAM.FILEA.CLUSTER SHR


Example: Allocating a SYSMDUMP Data set With FREE=CLOSE Option
F IWAY2,DYNAM ALLOC FILE SYSMDUMP DA PROD2.SYSMDUMP.DATA SHR CLOSE

Note: The examples above assume IWAY2 is the jobname/started task ID for the server.

All valid DYNAM ALLOC syntaxes are supported. For more information on DYNAM command, please refer to the Store Procedures Reference manual.

The following message will be issued in the server JESMSGLG indicating if the command was processed successfully or not.

Success:

+DYNAM COMMAND SUCCESFULLY PROCESSED Rc=0

Failure:

+DYNAM ERROR: IKJ56225I DATA SET IWAY.TEST ALREADY IN USE, TRY LATER


x
Procedure: How to Free Data sets Allocated to the Server

A z/OS operator can issue modify commands from the z/OS system console to free DDNAMEs or DSNAMEs allocated to the server. Both global allocations (made at the server ISTART JCL) and local ones (DYNAM ALLOC commands issued by user tasks) can be freed. This procedure is useful if you need to free an allocation to run a batch utility overnight, without restarting the server.



x
Syntax: How to Free a Data set From the MVS System Console

To free a single DDNAME:

F <iway_server_jobname/started task>,DYNAM FREE FI <ddname>

To free a single DSNAME (all occurrences in the server):

F <iway_server_jobname/started task>,DYNAM FREE DS <dsname>

To free multiple DDNAMEs, passing a pattern (free all DDNAMEs staring with AB):

F <iway_server_jobname/started task>,DYNAM FREE FI AB*

To free multiple DSNAMEs (all occurrences in the server), passing a pattern (free all allocations of data sets starting with IWAY.VSAM):

F <iway_server_jobname/started task>,DYNAM FREE DA IWAY.VSAM*

A message will be issued in the iway_server JESMSGLG indicating if the command was process successfully or not, as follows.

Success:

+DYNAM COMMAND SUCCESFULLY PROCESSED Rc=0

Failure:

+DYNAM ERROR: IKJ56225I DATA SET IWAY.TEST ALREADY IN USE, TRY LATER


Example: Freeing an Allocated Data Set

Suppose ISTART JCL (jobname IWAY2) has the following allocation:

//VSAMFILE DD DISP=SHR,DSN=VSAM.FILEA.CLUSTER

The operator can free this file using the command (from MVS console):

F IWAY2,DYNAM FREE FI VSAMFILE


x
Procedure: How to Initialize the RDAAPP Application

RDAAPP is an interactive client test application that facilitates the execution of SQL statements and stored procedures on the Unified server. During the installation process, JCL and REXX routines are created in the installation data set as members IRDAAPPJ and IRDAAPPC respectively.

The following installation data set is used for HFS deployment.

qualify.servertype.DATA

where:

servertype

Is determined by your license key.

The following installation data set is used for PDS deployment.

qualify.PDS.servertype.DATA

where:

servertype

Is determined by your license key.

Note: The RDAAPP application is not intended for use as a production tool.

  1. To use the IRDAAPPJ JCL, you must first edit the member IRDAAPPJ and add your request details.
    1. To edit the member IRDAAPPJ, change the following field,
      //STDIN DD *         
      Put your request here
      //     

      to

      //STDIN DD *         
      <enter blank line>
      <enter userid>
      <enter password>
      LOOPBACK
      <enter request>
      <enter optional parameters>
      Q
      Q
      //
    2. Complete the panel as follows.

      Field

      Instructions

      <enter userid>

      Enter a vailid userid or blank line if the userid of the user who submitted the job is to be used for a trusted connection.

      <enter password>

      Enter the password for the above userid or a blank line if the userid/password of the user who submitted the job is to be used for a trusted connection.

      LOOPBACK

      Match a node name in the EDACS3 allocation in the IRDAAPPJ JCL. Default is LOOPBACK.

      <enter request>

      Enter one of the following values:

      S

      To enter an SQL SELECT statement. Type the statement after you enter the value S (see the following example).

      P

      To enter an SQL PREPARE statement. Type the statement after you enter the value P.

      D

      To execute a prepared statement by supplying the ID. Type the ID after you enter the value E.

      Q

      To quit.

      ?

      For this list of commands.

      <enter optional parameters>

      Depending on the above command, you may be prompted for:

      Select engine (0/ENTER - EDA, 1 - DB2, 2 - TERADATA, and so on).

      Reclimit (Hit Enter for all records).

      Readlimit (Hit Enter for all records).

      Q

      Quit RDAAPP (It is needed twice).

    3. Once you have made the above edits, submit the JCL for execution.
  2. Type the following command at the TSO ready prompt to use the IRDAAPPC REXX routine:
    EX 'qualif.servertype.DATA(IRDAAPPC)'

    or

    EX 'qualif.PDS.servertype.DATA(IRDAAPPC)'

    where:

    servertype

    Is determined by your license key.

  3. After the prompts, enter the same information as specified in the above table.


Example: IRDAAPPC REXX Execution

The following is the screen output from a sample execution of the IRDAAPPC REXX routine:

********************************************************************
**                  RDAAPP Client test tool                       **
********************************************************************
<<< RDAAPP : Initializing EDA/API SQL, Version 7, Release 7 >>>
Default communications config file : //DD:EDACS3   
Override? (Press enter for default) :    <enter blank line> 
<<< Initialization Successful >>>
Enter User Name : <enter
userid or leave blank for current TSO userid> 
Enter Password : <enter password or leave blank for current
TSO userid  password> 
Enter server name, number, SELF, URL or ? (Hit return for 'LOOPBACK') :
<<< Successfully connected to synchronous server LOOPBACK >>>
Enter Command (? for command help):                            S
SELECT COUNTRY FROM CAR; 
Select engine (0/ENTER - EDA, 1 - DB2, 2 - TERADATA, etc) :
Reclimit (Hit enter for all records):
Readlimit (Hit enter for all records): 
Please Wait...                                                        
ENGLAND
FRANCE
ITALY
JAPAN
W GERMANY 
<<< 5 record(s) processed. (scb count 5) wait=4 secs, retrieval=0 secs>>>
<<< 5 record(s) processed. (scb count 5)>>> 
Q 
Enter Connect or Quit:
Q 
<<< RDAAPP : Exiting... >>> 
***                              
Enter Command (? for command help):


x
Procedure: How to Add Your Problem to the Troubleshooting Guide

If you have troubleshooting suggestions that you think others will find helpful, we invite you to send them to us so that we can consider including them in a future release. You can:


iWay Software