> # Installing SequeLink® Server on z/OS

> Installing SequeLink Server for DB2 UDB for z/OS involves the following steps:

> - "Step 1. Unpacking the Product Files"
> - "Step 2. Registering Your License"
> - "Step 3. Allocating the SequeLink® ISPF Libraries to a TSO Session (Optional)"
> - "Step 4. Modifying the APF List"
> - "Step 5. Configuring SequeLink® Server"
> - "Step 6. Configuring the DB2 Environment"
> - "Step 7. Starting the SequeLink® Server for DB2 for z/OS Service"
> - "Step 8. Configuring SequeLink® Service Security (Optional)"
> - "Step 9. Configuring Security for the SequeLink® Manager for z/OS Operator Interface (Optional)"

> Read the readme.txt file for the latest information of this SequeLink 6.0 Server for DB2 on z/OS release.

> ### Data Sets Created During Installation

> Prior to SequeLink Server for DB2 on z/OS version 5.5, both the SequeLink installation data sets and the specific SequeLink Server data sets used a high-level qualifier (HLQ) prefix.

> The naming convention now gives the SequeLink administrator more control and flexibility over naming data sets:

> - Deployment, for example, from development to production, is easier.
> - SequeLink installation libraries are read-only.
> - Multiple server environments, such as Production, Development, and Quality Assurance, can be administered separately. For example:
> - User-specific data set names can be made unique for each environment
> - The data sets can be allocated on separate volumes.
> - RACF data set security can be set for each environment.

> Two new data set prefixes have been introduced:

> - HLQ is the installation data set prefix. The HLQ prefix is required at install time.
> - USR is the server-specific data set prefix. The USR prefix and the server name (USR.servername) are required when a SequeLink Server is added.

> The maximum length for each qualifier is 24 characters; the name must be compliant with the operating system data set naming convention.

> The installation libraries are copied to data sets prefixed with the installation data set prefix (HLQ). The SequeLink servers generated and configured with the SequeLink Server Manager for z/OS (SSMC) reside in the data sets prefixed with a server-specific data set prefix (USR.servername), so that data sets related to one SequeLink Server can be grouped, where USR specifies the SequeLink Server environment and servername is the name of the SequeLink server.

> The list of SequeLink servers that will be managed using the SSMC is maintained in the server list data set. The name consists of the server-specific data set prefix USR suffixed with '.SERVERS'.

> Example:

> A company installs SequeLink and configures three SequeLink Servers, one for the production environment and two for the test and development environment. The production server accesses DB2V8 and the testing/development servers access DB2 v8 and DB2 V9.

>     HLQ = SQLNK.V6R0M0
>     USR1 = COMPANY.PROD
>     servername1 = SQLDB2V8
>     USR2 = COMPANY.DEV
>     servername1 = SQLDB2V8
>     servername2 = SQLDB2V9

> This results in the following data sets on your system:

> SequeLink installation data sets | SQLNK.V6R0M0.CLIST SQLNK.V6R0M0.DBRM SQLNK.V6R0M0.IPE SQLNK.V6R0M0.LINKLIB SQLNK.V6R0M0.LOADLIB SQLNK.V6R0M0.MSGS SQLNK.V6R0M0.PANELS SQLNK.V6R0M0.SKELS SQLNK.V6R0M0.TABLES SQLNK.V6R0M0.SWANDM.INI SQLNK.V6R0M0.README
> Serverlist data sets | COMPANY.PROD.SERVERS COMPANY.PROD.SQLDB2V8.SWANDM.INI COMPANY.PROD.SQLDB2V8.SWEVLOG COMPANY.PROD.SQLDB2V8.CNTL COMPANY.DEV.SERVERS COMPANY.DEV.SQLDB2V8.SWANDM.INI COMPANY.DEV.SQLDB2V8.SWEVLOG COMPANY.DEV.SQLDB2V8.CNTL COMPANY.DEV.SQLDB2V9.SWANDM.INI COMPANY.DEV.SQLDB2V9.SWEVLOG COMPANY.DEV.SQLDB2V9.CNTL

> ### Security Requirements for SequeLink® Data Sets

> This section describes the minimum RACF permissions required by the SequeLink administrator and the ServerUID (the user ID connected to the SequeLink Server's started task or job) for the data sets that are created by SequeLink during your SequeLink installation and subsequent configuration. These include:

> - Installation data sets
> - Data sets that are used during the creation of a new SequeLink Server
> - Data sets that are allocated during the configuration of a new server
> - Hierarchical file system (HFS) file directory for error reporting and debugging

> #### Installation Data Sets

> Installation data sets are prefixed with HLQ, where HLQ is the high-level qualifier. Set RACF permissions for these data sets as shown in the following table:

> Table 2-12. Setting Security Permissions for Installation Data Sets
> Data Sets | Required Permissions
> --- | ---
> CLIST, MSGS, PANELS, SKELS | READ for administrator
> DBRM | READ for administrator
> IPE | READ/WRITE for administrator and ServerUID
> LINKLIB, LOADLIB | READ for administrator and READ for ServerUID
> SWANDM.INI | READ for administrator
> TABLES | READ for administrator
> README | READ for administrator
> NOTE: ServerUID is the user ID connected to the SequeLink Server's started task or job.

> #### Data Sets Allocated During the Server Configuration

> Data sets that are allocated during the server configuration are prefixed with USR.ServerName, where USR specifies the SequeLink Server environment, and ServerName is the name of the SequeLink server. The data sets include data sets that are created during JCL generation and data sets created by the EVLDEF job.

> Set RACF permissions for data sets created during JCL generation as shown in the following table:

> Table 2-13. Setting RACF Permission for Data Sets Created During JCL Generation
> Data Sets (JCL Generation) | Required Permissions
> --- | ---
> CNTL | ALTER for administrator
> SWANDM.INI | ALTER for administrator UPDATE for ServerUID
> NOTE: ServerUID is the user ID connected to the SequeLink Server's started task or job.

> Set RACF permissions for the SWEVLOG data set created by the EVLDEF job to ALTER for administrator and UPDATE for ServerUID. In this case, ServerUID is the user ID connected to the SequeLink Server's started task or job.

> #### Data Sets Used in the Creation of a New SequeLink® Server

> SequeLink Server Manager for z/OS tracks all of the installed SequeLink Servers for a specific environment. The list of SequeLink servers is maintained in the server list data set USR_prefix.SERVERS, where USR_prefix is the server-specific data set prefix.

> Set RACF permissions for the SERVERS data set to ALTER for administrator.

> NOTE: When the SequeLink Server Manager is started with a new USR environment, the corresponding serverlist data set is automatically allocated.

> #### HFS File Directory for Error Reporting and Debugging

> You must create an OMVS segment for the RACF user id that represents the SequeLink Server. Set RACF permissions to allow this user id to write to the UNIX HFS filesystem directory, as specified in the ServiceDebugLogPath attribute. The default value is the directory /tmp. For information about the ServiceDebugLogPath attribute, refer to the SequeLink Administrator's Guide.

> This OMVS segment must also exist to allow the SequeLink Server to use the TCP/IP OpenEdition interface.

> ### Gathering Information for the Installation

> Table 2-14 lists the information that you must supply during installation of SequeLink Server for DB2 for z/OS. The table also provides an example of a value for each attribute.

> Table 2-14. Required Information for SequeLink Server for DB2 for z/OS Installation
> Attribute | Example
> --- | ---
> Installation data set prefix | SQLNK.V6R0M0
> Server-specific data set prefix | COMPANY.PROD
> Server name | SQLD2V8
> Volume for data set creation | VOL(DDIR02) | VOL(SMS)
> Port for SequeLink Server | 19996
> Name | Sales
> Company | CompanyXYZ
> Serial Number | 1
> IPE Key | *

> 1NOTE: Provided by DataDirect Technologies for registered users

> ### Step 1. Unpacking the Product Files

> The installation package for SequeLink Server for DB2 for z/OS is delivered as a zip file, sldb2zos.zip.

> - If downloading the file from the DataDirect DVD, insert the DVD into the DVD-ROM drive. If you have a local DVD-ROM drive, this typically is drive D. If the DVD-ROM drive is on a network, mount the DVD and create a mapping to the DVD-ROM drive. Save sldb2zos.zip to a temporary directory.
> - If downloading the file from the Web site, download instructions are available on the DataDirect Technologies Web site. Save sldb2zos.zip to a temporary directory.
> - Unzip the file sldb2zos.zip to a directory on your PC. Make sure that the unzip program you are using supports long filenames.

> The batch file ftpsldb2zos.bat and the installation files in xmitted format described in Table 2-15 are unzipped to your PC.

> Table 2-15. SequeLink Server for DB2 on z/OS Installation Files
> Data Set | Description
> --- | ---
> CLIST | A data set that contains REXX executables used by the SequeLink Manager for z/OS.
> DBRM | A partitioned data set that contains the DB2 Database Request Module (DBRM) used to create the packages for the DB2 service.
> IPE | A data set that contains JCL to customize the license information.
> LOADLIB | A partitioned data set that contains all the system load modules for SequeLink Server.
> LINKLIB | The SAS/C runtime library.
> MSGS | A data set that contains ISPF messages generated by the SequeLink Manager for z/OS.
> PANELS | A data set that contains ISPF panels used by the SequeLink Manager for z/OS.
> README | A README data set containing installation information for SequeLink Server for z/OS.
> SKELS | A data set that is used to generate JCL.
> SWANDM.INI | The SequeLink configuration file used for all SequeLink services on the z/OS machine. Do not alter this file.
> TABLES | A data set containing ISPF tables used by the SequeLink Manager for z/OS.

> 1. At a command line, run the batch file ftpsldb2zos.bat:

> ftpsldb2zos hostname userid password

> where hostname, userid, and password are the host name, user ID, and password for your z/OS system??? This batch file sends the files listed in Table 2-15 to your z/OS system using ftp, and stores them in an intermediate xmit format. The target data sets are created if they do not exist.

> 2. Before the transferred files can be used, they must be received on the z/OS machine. On TSO, issue the following command for each file that was transmitted in Step 2:

> RECEIVE INDATASET(XMIT.filename)

> 3. When prompted by the message `INMR906A Enter restore parameters or 'DELETE' or 'END'` `+`, enter:

> DA(`HLQ_prefix`) UNIT(unit) VOLUME(volume)

> where `HLQ_prefix` is the SequeLink installation data set high-level qualifier. The UNIT() and VOLUME() operands are optional.

> ### Step 2. Registering Your License

> The HLQ.IPE data set contains two members that you use to work with your license for the SequeLink Server for DB2 on z/OS:

> - Use IPEREG to register your license.
> - Use IPERPT to print out a report about your license in case of problems with the product registration.

> When you execute the IPEREG job to register your license, the register job requires you to enter your product registration information. Enter your name, company name, serial number, and key. The serial number and key are provided to you by DataDirect Technologies. If you are installing an evaluation copy of SequeLink Server, leave the IPE Key field empty.

> After a successful registration, a registration file, HLQ.ISLVINI, is added in the SequeLink installation data sets. The registration information is displayed in the output of the IPEREG job.

>     DATADIRECT Product Registration:
>     Name: My Name  CO:  My Company  SER#: snsnsnsnsnsn  IPE: ipeipeip
>     DATADIRECT Product Registration successful based on the key provided.

> where snsnsnsnsnsn is the serial number you provided and ipeipeip is the IPE key you provided.

> NOTE: SequeLink Server for DB2 on z/OS must be registered correctly or the installation and configuration will not work.

> ### Step 3. Allocating the SequeLink® ISPF Libraries to a TSO Session (Optional)

> Allocating the SequeLink ISPF libraries to your TSO session allows you to use a simpler command syntax for starting the SequeLink Manager for z/OS (as described in "A. Starting the SequeLink® Manager for z/OS").

> If you are planning to use the SequeLink Manager for z/OS regularly, we recommend that you allocate the SequeLink ISPF libraries to the TSO session as shown in Table 2-16.

> Table 2-16. SequeLink ISPF Library Allocation (z/OS)
> SequeLink ISPF Libraries | Allocate to...
> --- | ---
> SequeLink_HLQ.CLIST | SYSPROC or SYSEXEC
> SequeLink_HLQ.LOADLIB | ISPLLIB
> SequeLink_HLQ.MSGS | ISPMLIB
> SequeLink_HLQ.PANELS | ISPPLIB
> SequeLink_HLQ.SKELS | ISPSLIB
> SequeLink_HLQ.TABLES | ISPTLIB
> NOTE: SequeLink_HLQ is the SequeLink high-level qualifier identifying the libraries.

> ### Step 4. Modifying the APF List

> Before you can use the SequeLink Server for DB2 on z/OS, you must modify the APF list to contain entries for the following items:

> - LOADLIB data set containing the executable modules of the SequeLink Server.
> - LINKLIB (the SAS/C runtime library distributed with SequeLink). It must be APF-authorized.

> To authorize LOADLIB and LINKLIB:

> 1. Locate the SYS1.PARMLIB data set.
> 2. To APF-authorize the libraries dynamically, modify the PROGxx member of the SYS1.PARMLIB to include an entry for each SequeLink Server data set LOADLIB and LINKLIB SAS/C runtime library. Enter the operator command `/SET PROG=xx` to activate the change.

> ### Step 5. Configuring SequeLink® Server

> Configuring SequeLink Server for DB2 on z/OS involves the following stages:

> - "A. Starting the SequeLink® Manager for z/OS"
> - "B. Creating a SequeLink® Server"
> - "C. Reviewing the SequeLink® Server Configuration"
> - "D. Configuring a Server Using the DB2 CAF Attachment"
> - "E. Generating JCL"
> - "F. Creating the EventTrace Data Set"
> - "G. Configuring Additional SequeLink® Features"

> IMPORTANT: Do not directly edit the SequeLink_HLQ.SWANDM.INI file (where SequeLink_HLQ is the SequeLink high-level qualifier). When you define a SequeLink Server, copies of these master files are created for the SequeLink Server definition using the name of the SequeLink Server. The server-specific configuration file must be maintained by the SequeLink Manager for z/OS and must not be edited directly.

> #### A. Starting the SequeLink® Manager for z/OS

> 1. Start the SequeLink Manager for z/OS. How you start the SequeLink Manager for z/OS depends on whether you allocated the SequeLink ISPF libraries to the TSO session as described in the previous section.
> - If you allocated the ISPF libraries, continue with Step 2.
> - If you did not allocate the ISPF libraries, continue with Step 3.
> 2. Starting the SequeLink Manager When ISPF Libraries Are Allocated:

> Type the following command:

> TSO %SSMC [HLQ(HLQ_prefix) USR(USR_prefix)]

> where HLQ_prefix is the installation data set prefix, and USR_prefix is the server-specific data set prefix. Then, press ENTER. When using this format to start the SequeLink Manager for z/OS, you must always pass the HLQ parameter. We recommend passing the USR parameter as well. If you do not specify the USR parameter, SequeLink retrieves the last passed value from your SSMC profile. If neither parameter is passed, and no value can be retrieved from your profile, the default value HLQ is used.

> For example:

> `TSO %SSMC HLQ(SQLNK.V6R0M0) USR(COMPANY.DEV)`

> 3. Starting the SequeLink Manager When ISPF Libraries Are Not Allocated:

> Type the following command:

> TSO EX '`HLQ_`prefix.CLIST(SSMC)' '[HLQ(`HLQ_prefix`)] [USR(USR_prefix)]'

> where HLQ_prefix is the installation data set prefix, and USR_prefix is the server-specific data set prefix. Then, press ENTER. You do not have to explicitly specify the HLQ prefix. If it is not specified, the prefix is set to the high-level qualifier of the data set from which the SSMC CLIST is executed. We recommend passing the USR parameter as well; the parameter will be saved in the user's SSMC profile. If you do not specify the USR parameter, SequeLink retrieves the last passed value from your SSMC profile. If neither parameter is passed, and no value can be retrieved from your profile, the default value HLQ is used.

> For example:

> `TSO EX 'SQLNK.V6R0M0.CLIST(SSMC)' 'HLQ(SQLNK.V6R0M0) USR(`COMPANY.DEV)`'`

> or

> `TSO EX 'SQLNK.V6M0.CLIST(SSMC)' 'USR(COMPANY.DEV)'`

> The HLQ used will be the HLQ from which the SSMC CLIST is fetched.

> NOTE: In the first example, the HLQ specified to locate the SSMC CLIST might be different from the HLQ argument passed. This is especially important when administering two different versions of SequeLink. In this case, we recommend that you always specify the HLQ argument explicitly.

> 4. When the Serverlist data set (USR_prefix.SERVER) has not been allocated for the environment USR, you are prompted for the necessary information. Press ENTER to continue. The SequeLink Manager for z/OS main menu appears.

> 5. If you select NO, you exit the SSMC application. If you select YES, the following panel appears. Enter VOL(vvvvvv) where vvvvvv is the volume on which you want to allocate the serverlist data set. This volume will be used to allocate server-specific data sets for SequeLink servers that are added to this environment. Press ENTER to continue.

> 6. When you start the SequeLink Manager for z/OS, copyright information appears. Press ENTER to continue. The SequeLink Manager for z/OS start panel appears.

> #### B. Creating a SequeLink® Server

> On z/OS, a SequeLink Server is a started task/job name that corresponds to a single data access service. You can define multiple SequeLink Servers on the same z/OS machine. Each SequeLink Server has SequeLink Agent functionality that is included in the data access service. When you add a SequeLink Server, you are prompted to add a DB2 interface and a service.

> To create a SequeLink Server:

> 1. From the ServerList panel, type `A` at the Command prompt to create a SequeLink Server; then press ENTER. The Add Server panel appears.

> 2. Provide the following information, then press ENTER:

> Server name: Type the name of the new SequeLink Server definition. The server name you choose will be the job name or started task name.

> Description: Type a description for the new SequeLink Server definition.

> Hostname/IP-address: Type the TCP/IP host name or the TCP/IP address of the SequeLink Server definition. The HOME address of the local TCP/IP stack or the standard 127.0.0.1 TCP/IP loopback address will be inserted. In some instances, such as when the TSO session for the SequeLink Manager is running on another IP stack than the server, you must specify the TCP/IP address of the server machine.

> Portnumber: Type the port to be used by the SequeLink service.

> NOTE: When you create a server, a server-specific configuration file is created. If such a file already exists, you are prompted to confirm whether you want to overwrite the existing configuration file.

> 3. You are prompted to supply parameters to the DB2 interface.

> 4. Provide the following information; then, press ENTER.

> Interface ID: Type a Logical ID identifying the DB2 interface for the SequeLink Server, for example, DSN8. The corresponding service attribute is MVSServiceDB2InterfaceID.

> DB2 Subsystem Id: Type the SubsystemId of the DB2 subsystem you want to access, for example, DBR8. The corresponding service attribute is MVSDB2SubsystemName.

> DB2 Version: Type the version of DB2 to be used, for example, V810. The corresponding service attribute is MVSDB2Version.

> Description: Type a description of the DB2 interface. The corresponding service attribute is MVSDB2RootDescription.

> DB2 Loadlib: Type the name of the DB2 load library, for example, DB2.V8R1M0.SDSNLOAD. The corresponding service attribute is MVSDB2LoadLibrary.

> DB2 Exitlib: Type the name of the DB2 exit library, for example, DB2.V8R1M0.DB8R.SDSNLOAD. The corresponding service attribute is MVSDB2ExitLibrary.

> 5. You are prompted to supply parameters to define the service.

> 6. Provide the following information; then, press ENTER.

> Service name: Type the service name. The corresponding service attribute is ServiceName.

> Description: Type a description of the service. The corresponding service attribute is ServiceDescription.

> Portnumber: The port number entered in the Server Definition panel is displayed here.

> 7. The ServerList panel shows the SequeLink Server you just created.

> Once you have created a SequeLink Server, type `S` beside it to view the server management tree. The server management tree shows the DB2 interface, User ID (UID) maps, and SequeLink Service and its configuration settings.

> See "C. Reviewing the SequeLink® Server Configuration" for information about making modifications to this newly configured server. Refer to the SequeLink Administrator's Guide for more information about navigating through the server management tree.

> #### C. Reviewing the SequeLink® Server Configuration

> 1. Type `S` beside the SequeLink Server that you want to configure; then, press ENTER. The server management tree for the selected server is displayed.
> 2. From the server management tree, type `/` beside the Service Settings node of the SequeLink service to expand it; then, press ENTER. The server management tree shows the attribute categories for the service.

> 3. Type `S` beside the attribute category for which you want to view attributes; then, press ENTER. The AttributeList panel appears for that category, listing all the attributes and their values.

> For example, if you selected the Administration Security category, the following AttributeList panel appears:

> NOTE: To display help about an attribute, type `?` beside the attribute; then, press ENTER.

> For instructions on adding, changing, and deleting attributes, including server data source attributes, refer to the SequeLink Administrator's Guide.

> We highly recommend using the DB2 RRSAF attachment, which allows you to fully exploit the threadpooling capabilities of SequeLink. However, If you do not wish to or cannot use the RRSAF attachment, you must make some additional changes. Continue to "D. Configuring a Server Using the DB2 CAF Attachment". Otherwise, skip to "E. Generating JCL".

> #### D. Configuring a Server Using the DB2 CAF Attachment

> We highly recommend using the DB2 RRSAF attachment, which allows you to fully exploit the threadpooling capabilities of SequeLink. If you do not wish to or cannot use the DB2 RRSAF attachment, you must change additional configuration settings.

> To configure a server using the DB2 CAF attachment:

> 1. Type `S` beside the Global Settings node for the server; then, press ENTER.
> 2. In the AttributeList panel, type `C` next to the MVSGlobalDB2Attachment service attribute. The service attribute panel appears.

> 3. Type `/` next to CAF to select it; then, press ENTER.
> 4. In the management tree of the SequeLink Service, expand the nodes. Type `/` next to the Advanced node; then, press ENTER. The AttributeList panel is displayed.

> 5. Type `S` beside the attribute you want to change; then, press ENTER. The Attribute Display window appears with the cursor positioned at the Value field of the attribute.
> 6. Type the new values of the following attributes; then, press ENTER:
> - Change ServiceConnectionModel to Thread/Connection
> - Increase ServiceMaxThreads to 256
> - Decrease ServiceMaxSessions to 250

> You are returned to the AttributeList panel, and the attribute values, if valid, are changed.

> 7. Press F3 to return to the server management tree.

> NOTE: We highly recommend that you use the ThreadPool connection model, which requires the RRSAF attachment. This setting allows you to have a large number of connections.

> #### E. Generating JCL

> After a SequeLink Server is created and configured for the first time, you must generate the JCL. The SequeLink Manager adapts the JCL from the SequeLink_HLQ.SKELS data set and saves the adapted output in a server-specific data set named USR.Servername.CNTL, where USR is the high-level qualifier and Servername is the name of the SequeLink Server.

> The following list shows the JCL members that are generated and the tasks they perform. Also, this list notes any tasks you must perform for the JCL member.

> - BINDxx: These members bind all required SequeLink packages and plans for your DB2 subsystems. Read the comments in this bind job carefully. The tailored job contains a job-step for the defined DB2 interface and bind statements for all data sources that use this interface.
> - BIND7: bind job for DB2 v7
> - BIND8C: bind job for DB2 v8, compatibility mode
> - BIND8N: bind job for DB2 v8, new function mode
> - BIND9: bind job for all DB2 v9 modes.

> NOTE: If data sources are added later, an interface is changed, or the collection-prefixes of a data source are changed, you must regenerate and submit these members.

> - CFGPRINT: A summary member you can use for debugging purposes that reports the content of all variables at the time of JCL generation. This member also lists the user and date and time of the last JCL generation.
> - EVLDEF: This member creates the event trace file for the server.
> - INIT: This member contains operator interface commands that will be executed after the successful startup of the server.

> NOTE: To add or delete operator interface commands you want to execute after the successful startup of the server, edit this member.

> - RUNSMF: This member is a sample job that allows SMF records to be printed.
> - RUNSRVR: This member is the started task or job that is used to start the server.

> NOTE: If the DB2 interface is changed, you must regenerate this member, and restart the server.

> - RUNCLUST: This member prints out the Sysplex registration information.
> - RUNWHAT: This member is a diagnostic job that prints all versions of the software components and can be used for debugging. Execute this job only on a specific request from DataDirect Technologies technical support.

> #### F. Creating the EventTrace Data Set

> Create the EventTrace data set by running the EVLDEF job you created in "E. Generating JCL". This job can be found in the data set USR.ServerName.CNTL, where USR is the high-level qualifier and Servername is the name of the SequeLink Server. By running EVLDEF, a VSAM data set is created that can be used by the Event Trace and Monitoring components of the SequeLink Server.

> #### G. Configuring Additional SequeLink® Features

> Refer to the SequeLink Administrator's Guide for information on configuring the following SequeLink features:

> - Support for SYSPLEX
> - Support for WLM enclaves
> - Support for terminal security

> ### Step 6. Configuring the DB2 Environment

> Configuring the DB2 environment for SequeLink Server involves:

> - "A. Binding the SequeLink® Package"
> - "B. Granting Access to the SequeLink® Server Package"
> - "C. Granting Cancel Thread Authorization to the SequeLink® Server (RRSAF Attachment Only)"
> - "D. Binding the SequeLink® Plan (CAF Attachment Only)"
> - "E. Granting Access to the SequeLink® Server Plan (CAF Attachment Only)"

> #### A. Binding the SequeLink® Package

> The server-specific CNTL library contains generated BIND jobs to bind the SequeLink DBRMs into packages.

> Because SequeLink Server for DB2 can change isolation level dynamically, each DBRM is bound into a package using a different isolation level for each package. The collection ID name of each package is created by concatenating the DB2 collection prefix and the DB2 collection suffix as shown in Table 2-17.

> Table 2-17. Isolation Levels of SequeLink DBRMs
> Data Source Transaction Isolation | Data Source DB2 Collection Prefix | Data Source DB2 Collection Suffix | Collection ID | Isolation
> --- | --- | --- | --- | ---
> Uncommitted | SWDB2 | U | SWDB2_U | UR
> Committed | SWDB2 | S | SWDB2_S | CS
> RepeatableRead | SWDB2 | T | SWDB2_T | RS
> Serializable | SWDB2 | R | SWDB2_R | RR
> NOTE: The collection prefix is set when you create the SequeLink data source (SequeLink service attribute DataSourceDB2CollectionPrefix). The collection suffix is set when you configure the transaction isolation level of the data source (SequeLink service attribute DataSourceTransactionIsolation). For a list of SequeLink service attributes, refer to the SequeLink Administrator's Guide.

> #### B. Granting Access to the SequeLink® Server Package

> Grant access to the SequeLink Server package for all users that will be connecting to the SequeLink Server. When granting access to the SequeLink package, remember to include the user ID associated with the SequeLink Server for each DB2 subsystem to which the SequeLink Server will connect. To grant access to the SequeLink Server package for all users, you can use the following SQL statement:

>     GRANT EXECUTE ON PACKAGE collection-id.* TO PUBLIC

> where collection-id.* is a collection-id used in the SequeLink bind job. See Table 2-17 for the names of possible collection-ids.

> #### C. Granting Cancel Thread Authorization to the SequeLink® Server (RRSAF Attachment Only)

> SequeLink has enhanced the facility to kill a session. In previous versions of SequeLink, when a session was active into DB2, SequeLink had to wait until the session returned.

> SequeLink now automatically correlates output from DB2 with information from SequeLink. This means that the SequeLink administrator has more control over the SequeLink sessions, and can take action without spending time to investigate why a killed session does not end.

> To request the DB2 database to cancel a DB2 Thread, use the DB2 IFI call interface to route a -CANCEL THREAD(token) command to DB2. SequeLink only requests canceling a DB2 Thread that is owned by it. DB2 threads owned by any other application are never canceled.

> NOTE: This enhancement is not supported for the CAF attachment.

> To enable this feature, the USERID that represents the SequeLink Server address space needs one of the following DB2 authorizations:

> - SYSOPR
> - SYSCTRL
> - SYSADM

> Refer to your DB2 documentation for more information about the DB2 "COMMAND REFERENCE" -CANCEL THREAD(DB2) command.

> #### D. Binding the SequeLink® Plan (CAF Attachment Only)

> When you are setting up your server with the CAF attachment, you must bind the SequeLink plan. The server-specific CNTL library contains generated BIND jobs to bind the SequeLink Server packages into plans.

> The SequeLink plan name is set when you create the SequeLink data source (SequeLink service attribute MVSDataSourceDB2Plan). For a list of SequeLink service attributes, refer to the SequeLink Administrator's Guide.

> #### E. Granting Access to the SequeLink® Server Plan (CAF Attachment Only)

> When you are setting up your server to use the CAF attachment, you must grant access to the SequeLink plan for all users who will connect to the SequeLink Server. When granting access to the SequeLink plan, remember to include the user ID associated with the SequeLink Server for each DB2 subsystem to which the SequeLink server will connect.

> To grant access to the SequeLink plan for all users, you can use the following SQL statement:

>     GRANT EXECUTE ON PLAN planname TO PUBLIC

> where `planname` is the name of the SequeLink plan.

> ### Step 7. Starting the SequeLink® Server for DB2 for z/OS Service

> Use the generated RUNSRVR member in the server-specific CNTL data set to start the SequeLink Server for DB2 service. The startup JCL can be a batch job or a started task.

> ### Step 8. Configuring SequeLink® Service Security (Optional)

> For more information about configuring SequeLink's security features for z/OS, refer to the SequeLink Administrator's Guide.

> ### Step 9. Configuring Security for the SequeLink® Manager for z/OS Operator Interface (Optional)

> Some Operator Interface commands can be useful in performing administration tasks. These commands can be issued using the Operator Interface of the SequeLink Manager for z/OS. For more information about configuring security for the Operator Interface of the SequeLink Manager for z/OS, refer to the chapter on using the SequeLink Manager in the SequeLink Administrator's Guide.