Preparing to customize
Before you start to customize Db2® Analytics Accelerator Loader for the first time, determine all of the customization values that you need to specify during the customization process, and familiarize yourself with all of the customization tasks.
The following checklist lists and describes each significant customization step. Use this checklist to guide you through the entire customization process.
| Task | Link to detailed instructions | Status |
|---|---|---|
| Tools Customizer basics | ||
| Prior to the customization process, familiarize yourself with Tools Customizer terminology and data sets, and other essential information about Tools Customizer. | Tools Customizer terminology and data sets | |
| Hardware and software requirements | ||
| Verify that your environment meets the minimum hardware requirements. | Hardware requirements | |
| Verify that your environment meets the minimum software requirements. To install and use Db2 Analytics Accelerator Loader, your environment must be running a supported version of the z/OS operating system and of Db2 for z/OS. Additionally, you'll need to ensure you are using minimum levels of maintenance. | Software requirements | |
| SMP/E installation | ||
| Verify that Db2 Analytics Accelerator Loader has been installed correctly. Db2 Analytics Accelerator Loader is installed by using standard SMP/E processing. | Verify that Db2 Analytics Accelerator Loader has been installed successfully | |
| Verify that Tools Customizer for z/OS is installed correctly by using standard SMP/E processing. | Verify that Tools Customizer has been installed successfully | |
| Code page requirement | ||
| Ensure that your BIND JCL uses the correct code page. | Changing the BIND JCL to ENCODING(500) (optional) | |
| Region size requirements | ||
| Ensure that the correct minimum region size is used. | Verify that your environment meets minimum region size requirements | |
| Started task requirements and considerations | ||
| Ensure that the Accelerator Loader started task runs under a user ID that has the required authority. | Authorization requirements for the Accelerator Loader started task | |
| Data sharing considerations | ||
| Review deployment and configuration issues for Db2 data sharing environments. | Considerations for Db2 data sharing environments | |
| Workload Manager requirements | ||
| Ensure that the dispatching priority for the Accelerator Loader started tasks is set correctly with respect to other dispatching priorities. Review considerations for defining the server to WLM. | WLM requirements for Accelerator Loader | |
| WTO messages for automated operations | ||
| Consider whether to use the write-to-operator (WTO) messages that Accelerator Loader issues for automated operations. | WTO messages for automated operations | |
| Gather data set names | ||
During the customization process, you must specify
data set names for the following things:
|
Worksheets: Gathering required data set names | |
| Gather parameter values | ||
| During the customization process, you must specify parameter values for Db2 Analytics Accelerator Loader, for Db2, and for your LPAR. | Worksheets: Gathering parameter values for Tools Customizer | |
| Customize Db2 Analytics Accelerator Loader | ||
Start Tools Customizer by running a REXX EXEC from the ISPF Command Shell panel. |
Starting Tools Customizer | |
Set up Tools Customizer user settings. If you are running Tools Customizer for the first time, you must modify several user settings to suit your environment. If the user settings that you have already established are still appropriate, skip this step. |
Modifying Tools Customizer user settings | |
Complete steps in the customization roadmap based on the type of customization that you are performing. |
||
Customizing Db2 Analytics Accelerator Loader for the first time Follow this roadmap if you do not have a customized version of the product and you need to customize it for the first time. |
Roadmap: Customizing Db2 Analytics Accelerator Loader for the first time | |
Customizing a different version of Db2 Analytics Accelerator Loader Follow this roadmap if you have already customized a version of the product and you want to use the same parameter values to customize a different version. |
Roadmap: Customizing a new version of Db2 Analytics Accelerator Loader from a previous customization | |
Recustomizing Db2 Analytics Accelerator Loader Follow this roadmap if you have a customized version of the product and want to change parameter values and regenerate jobs. |
Roadmap: Recustomizing Db2 Analytics Accelerator Loader | |
After using Tools Customizer to perform customization, complete the following required tasks. |
||
| APF authorization | ||
Ensure the following data sets have APF authorization:
|
APF-authorizing the load libraries (required) | |
| Make the started task address spaces available to user interfaces | ||
| Copy the Accelerator Loader and server started task PROCs to your system PROCLIB to ensure the started task address spaces are available to the product user interfaces. | Copying the started task PROC (required) | |
| Copy the DSNUTILF module | ||
| The DSNUTILF module must be in an APF-authorized library in the STEPLIB or JOBLIB concatenation for the Db2 LOAD utility jobs and the WLM application environment. | Copying the DSNUTILF module (required) | |
| Set up the WLM-managed address space | ||
| This step enables the Accelerator Loader started task to perform DSNUTILB interception services. | Setting up the WLM application environment (required) | |
| Start the started task | ||
| Before you can use the product, you must start the started task. | Starting the started task (required) | |
| Accelerator Loader server requirements and considerations | ||
| You can use a security product such as IBM RACF®, ACF2, or Top Secret. You must define the Accelerator Loader server name for the security product and authorize the data set. | Authorization requirements for the Accelerator Loader server | |
| Start and stop the Accelerator Loader server running on z/OS. Under normal circumstances, Accelerator Loader server starts at system startup and stops before the system shuts down. | Starting and stopping the server (required) | |
| Enable access to mainframe data sources | ||
| Accelerator Loader server supports access to many data sources, and you must configure access to mainframe data sources. Refer to the sections for those data sources you want to use. | Configuring access to data sources (required) | |
| Configure rules and events | ||
| If you use SMF, configure access to SMF files and set conditions for SMF. | ||
| Install and configure the Accelerator Loader studio plug-in | ||
| Accelerator Loader studio is an IBM Data Studio plug-in. Use Accelerator Loader studio to generate JCL to load data directly to the accelerator, without first extracting the data and writing it to a file. | Installing the Accelerator Loader studio (required) | |
| Set the Accelerator Loader studio connection to the Accelerator Loader server. | Connecting to the Accelerator Loader server | |
| Create a source library. A source library is a fully-qualified partitioned data set (PDS) on z/OS that contains the information required to map the data source to the target Db2 table on the accelerator. |
Creating virtual source libraries | |
| Create a virtual table. A virtual table extracts information from the data definitions. |
Creating virtual tables | |