IBM Support

Updates to Db2 Analytics Accelerator Loader V2.1 User's Guide

Product documentation


Abstract

Updates that apply to IBM Db2 Analytics Accelerator Loader for z/OS V2R1 User's Guide (SC27-6777-00)

Content

The most recent update is listed first.



Update 28
Date of change: March 2018
Topic: Multiple
Change description: Documentation changes made in support of APAR PI89079 – Enhancements for Accelerator Loader server

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI89079.pdfDB2AALoader_PI89079.pdf



Update 27
Date of change: December 2017
Topic: Multiple
Change description: Documentation changes made in support of APAR PI90862 – Improve discard support in External Load

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI90862.pdfDB2AALoader_PI90862.pdf



Update 26
Date of change: December 2017
Topic: Multiple
Change description: Documentation changes made in support of APARs PI88521 and PI90296 – DETECT_DATA_CHANGES updates REFRESH_TIME of tables not refreshed; unreachable accelerators treated as offline

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI88521 PI90296.pdfDB2AALoader_PI88521 PI90296.pdf



Update 25
Date of change: November 2017
Topic: Multiple
Change description: Documentation changes made in support of APARs PI85070 and PI86772 – Support for translating EBCDIC sources to Unicode AOTs; support for compressed SMF log stream data

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI85070 PI86772.pdfDB2AALoader_PI85070 PI86772.pdf



Update 24
Date of change: November 2017
Topic: Multiple
Change description: Documentation changes made in support of APAR PI84052 – Started task auto attach enhancement

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI84052.pdfDB2AALoader_PI84052.pdf



Update 23
Date of change: September 2017
Topic: Multiple
Change description: Documentation changes made in support of APARs PI85815 and PI86642 – Provide return code option when rows are discarded on a load; Enhance External load to offload more CPU cycles to the zIIP processors.

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI85815_PI86642.pdfDB2AALoader_PI85815_PI86642.pdf



Update 22
Date of change: August 2017
Topic: Multiple
Change description: Documentation changes made in support of PI84115 and PI85219 – Stop target table space before Dual type load, Reduce the TCB CPU Time of External load

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI84115_PI85219.pdfDB2AALoader_PI84115_PI85219.pdf




Update 21
Date of change: August 2017
Topic: Multiple
Change description: Documentation changes made in support of APARs PI76778, PI80385, PI80386, PI80783, PI81983, and PI83170 – Enhancements for Accelerator Loader server.

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI76778_PI83170.pdfDB2AALoader_PI76778_PI83170.pdf



Update 20
Date of change: January 2018
Topics: Multiple
Change description: Documentation changes made in support of APAR PI65840 – High availability support for Consistent and Image Copy loads.

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI65840.pdfDB2AALoader_PI65840.pdf



Update 19
Date of change: July 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI82046 – Using HALOAD to load only tables or partitions that have changed since the last load.

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI82046.pdfDB2AALoader_PI82046.pdf



Update 18
Date of change: July 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI81870 – Support for HLORESET on the EXEC statement for the DSNUTILB program.

See the following PDF for detailed User's Guide changes:
DB2AALoader_PI81870.pdfDB2AALoader_PI81870.pdf



Update 17
Date of change: June 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI80838 – Allow a single BSDS defined for a subsystem.

See the following PDF for changes:
Techdoc_PI80838.pdfTechdoc_PI80838.pdf



Update 16
Date of change: June 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI80293 – Delimited file format support.

See the following PDF for changes:
Techdoc_PI80293.pdfTechdoc_PI80293.pdf



Update 15
Date of change: June 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI79574 – Rollback support for Dual type loads.

See the following PDF for changes:
Techdoc_PI79574.pdfTechdoc_PI79574.pdf



Update 14
Date of change: June 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI79055 – Support for loading SYSREC records in EBCDIC into UNICODE system.

See the following PDF for changes:
Techdoc_PI79055.pdfTechdoc_PI79055.pdf



Update 13
Date of change: June 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI79298 – Load accelerator and Db2 from a virtualized data source or remote DBMS.

See the following PDF for changes:
Techdoc_PI79298.pdfTechdoc_PI79298.pdf



Update 12
Date of change: June 2017
Topics: Multiple
Change description: Documentation changes made in support of APARs PI72331 and PI70677 – Enhancements for Accelerator Loader server.

See the following PDF for changes:
Techdoc_PI72331_PI70677.pdfTechdoc_PI72331_PI70677.pdf



Update 11
Date of change: June 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI76856 – Support for new CHECK_DATA keyword.

See the following PDF for changes:
Techdoc_PI76856.pdfTechdoc_PI76856.pdf



Update 10
Date of change: May 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI77145 – Stored procedure support for high availability load

See the following PDF for changes:
Techdoc PI77145.pdfTechdoc PI77145.pdf



Update 9
Date of change: April 2017
Topics: Multiple
Change description: Documentation changes made in support of APAR PI70981 Accelerator data backup and recovery

See the following PDF for changes:
Techdoc_PI70981.pdfTechdoc_PI70981.pdf



Update 8
Date of change: October 2016
Topics: Multiple
Change description: Documentation changes made in support of APAR PI67020 Tools Customizer enhancements for Accelerator Loader.
See the following PDF for changes:
Techdoc_PI67020.pdfTechdoc_PI67020.pdf



Update 7
Date of change: October 2016
Topics: Multiple
Change description: Documentation changes made in support of APAR PI63948 and PTF UI40787 APAR PI65565 Direct access to Oracle via DRDA
See the following PDF for changes:
Techdoc_PI63948_PI65565.pdfTechdoc_PI63948_PI65565.pdf



Update 6
Date of change: September 2016
Topics: Multiple
Change description: Documentation changes made in support of APAR PI67510(+PI64557) Support Accelerator Groups.
See the following PDF for changes:
Techdoc_ PI67510.pdfTechdoc_ PI67510.pdf



Update 5
Date of change: August 2016
Topics: Multiple
Change description: Documentation corrections and updates in support of enhancements provided in APAR PI59666.

See the following PDF for changes:
HLO-1122_PI59666_8_24.pdfHLO-1122_PI59666_8_24.pdf


Update 4
Date of change: August 2016
Topics: Multiple
Change description: Documentation changes in support of the enhancement provided in APAR PI58663:

Topic: "What's new"
Add the following description.
Accelerator Loader supports Adabas as a selectable data source. To enable this feature, when customizing the product with Tools Customizer, specify the Adabas load library for the server to use to connect to the Adabas databases.

Topic: "Worksheets: Gathering parameter values for Tools Customizer; Task: Create the server and the server components (required)"
Add the following parameter.

ADABAS load library
Specifies the ADABAS load library that the server uses to connect to the ADABAS databases. If this value is defined, the server uses ADABAS as a data source. If this value is not defined, the server does not use ADABAS as a data source.

Required? No
Discovered? No
Default value: No default

Topic: "Configuring access to mainframe data sources (required)"
Add section "Configuring access to data in Adabas". See the following PDF for details:
configureAccess.pdfconfigureAccess.pdf

Topic: "Creating virtual source libraries"
Add to the following list of options.
The following virtual source library options are available:
– DDM Views (Data Definition Module) for Adabas. Run your Natural job to create a DDM View listing, and then use the output to create a data set member in the source library.

Topic: "Creating virtual tables to access data using SQL"
Add subsection "Creating virtual tables for Adabas". See the following PDF for details:
createVirtualTableAdabas.pdfcreateVirtualTableAdabas.pdf

Topic: Multiple in section " Administering the Accelerator Loader server"
Add and update multiple subsections. See the following PDF for details:
adminServerAdabas.pdfadminServerAdabas.pdf

Topic: "Messages and codes"
Add message.
HLOS0606I - DB2 SSID=<db2_ssid> has Db2 Sort enabled.
Explanation: Db2® Sort is either enabled (YES) or not enabled (NO) for the specified Db2 subsystem.
User response: No action is required.


Update 3
Date of change: August 2016
Topics: Multiple
Change description: Documentation corrections and updates in support of enhancements provided in the following APARs:
- PI56636
- PI57070
- PI58602
- PI57068

Topic: "What's new"
Add the following descriptions of enhancements.
Accelerator Loader can load data from a remote system, enabling you to load remote data sources that are not directly accessible from the local system (not configured to the accelerator). To perform this type of load, an Accelerator Loader server must be running on the remote LPAR and the local server must be configured to communicate with that remote server.
Accelerator Loader supports IBM z Systems Data Compression (zEDC) to optimize cross-platform exchange of data by reducing network flow between the two servers when loading from a remote server.


Topic: "Features and benefits"
Add the following description:
Remote data load
Accelerator Loader can be configured to load data from a remote system, which allows for loading remote data sources that are not directly accessible from the local system. For example, you could load data from an IMS database on a remote LPAR. This type of load requires you to have an Accelerator Loader server running on the remote LPAR and the local server must be configured to communicate with that remote server.


Topic: "Components and interfaces"
Add information to the following description:
Accelerator Loader server
An Accelerator Loader server on one LPAR can communicate and share data with another Accelerator Loader server that is installed and configured on another LPAR in the z System.


Topic: "Scenarios"
Add the following scenario:
You have a z System infrastructure that has four LPARs configured. Adabas is running on LPAR D and you need to access Adabas from LPAR A. You can use Inter Data Communications (IDC) to enable communication between the LPARs and access to data on those systems. The Accelerator Loader server enables data processing to run on a z System Integrated Information Processor (zIIP) specialty engine for significantly reduced MIPS capacity usage. In the example, LPAR A can access Adabas data on LPAR D and use the zIIP processor to perform all processing.

Topic: "Generating JCL"
Replace topic. See the following PDF for details:
GeneratingJCL.pdfGeneratingJCL.pdf

Topic: "Syntax"
Replace topics in section "Loading data from non-Db2, remote Db2, and remote system sources". See the following PDF for details:
Syntax.PDFSyntax.PDF

Topic: "Administering the Accelerator Loader server"
Add subsection "Accessing data on a remote system". See the following PDF for details:
AccessDataOnRemoteSystem.pdfAccessDataOnRemoteSystem.pdf



Update 2
Date of change: July, 2016
Topics: Multiple
Change description: Documentation corrections and updates in support of enhancements.

Topic: "What's new"
Add the following descriptions of enhancements.
When performing an External load to only the accelerator, Accelerator Loader bypasses the Db2 LOAD utility when running a LOAD RESUME. This enhancement provides query access to the data while Accelerator Loader performs the load.

When performing a Consistent load, you can load image copy and log data as follows:
  • from a specified table into an alternate accelerator only table (AOT) on the same Db2 subsystem or an alternate target Db2 subsystem on the same LPAR
  • to the accelerator table of a standard Db2/accelerator table on an alternate target Db2 subsystem

This function is especially useful when you are consolidating data from different Db2 systems into a single Db2 system that is connected to an accelerator, such as a data warehouse.
When performing an Image Copy load, you can take an image copy of a regular Db2 table and load the data into an accelerator only table (AOT) with the same columns in the same order.
When loading data from non-Db2 and remote Db2 sources, when using the Accelerator Loader studio to generate the JCL, you can specify an accelerator only table (AOT).
When performing an External load, you can load data to an accelerator only table (AOT). VSAM objects do not exist in Db2 for AOTs; therefore, you cannot load to both Db2 and the accelerator (Dual load).

Topic: "Features and benefits"
Add the following information to the Image Copy load description:
This type of load [an Image Copy load] should not be confused with an enhanced load from an external file. Db2 image copies are registered within the Db2 catalog and are therefore not considered an external source.

Topic: "Scenarios"
Add the following scenario:
Loading a specific image copy into an object on the IBM Db2 Analytics Accelerator for z/OS
You want to load data from a specific Db2 image copy into a table on the accelerator that is either not the last registered image copy in SYSIBM.SYSCOPY, or is not registered in the SYSCOPY table at all. This scenario cannot be accomplished without the Accelerator Loader.
By using the Accelerator Loader, you can load data from a specific image copy into its corresponding table on the accelerator. With this option, only the data that are contained within the pages of the image copy are written to the table on the accelerator. No log records are applied and you do not need to specify the end point. The table in Db2 remains online during the update to the accelerator.
You have the following options to refresh image copy data:
  • Use the example JCL to create a batch job.
  • Use the Accelerator Loader ISPF interface to generate the batch job (if the image copy has only one table).

Topic: "Set up your environment prior to customization"
Update the software requirements:
Accelerator requirements
Ensure that you are using a supported version of IBM® Db2 Analytics Accelerator for z/OS:
  • Version 3.1.0 (5697-DAA ) or later for basic processing
  • Version 4.1.0 (5697-DAB) with PTF-5 applied or a later version to use all product features.
  • Version 4.1.0 (5697-DAB) with PTF-6 applied or a later version to use all product features.
Db2 requirements
Ensure that you are using one of the following supported versions of Db2 for z/OS at the latest maintenance level:
  • DB2 V10:
  • DB2 V10 (5605-DB2)
  • DB2 Value Unit Edition V10.1 (5697-P31)
    Required maintenance:
    • AI25214
    • PI10162
    • PI30376 (UI26404)
    • PI59910
    • PM93789
    • UI24305
    • UI24307
  • Db2 V11:
  • Db2 V11 (5615-DB2)
  • Db2 Value Unit Edition V11.1 (5697-P43)
    Required maintenance:
    • AI26321
    • PI10162
    • PI35818 (UI29037)
    • PI59910
    • UI24306
    • UI24308

Topic: "Worksheets: Gathering parameter values for Tools Customizer"
Revise the following parameter description:
Subsystem domain name
Specifies the fully qualified name that identifies the IP address of the Db2 subsystem that is being configured. The domain name is generated into the hlvidIN00 file. You can manually edit the file to specify the IP address instead.
For LUW, this value specifies the DNS name for the server on which the LUW database exists.
Required? Yes
Discovered? No
Default value: host.domain.com

Topic: "Customizing the server parameter file (optional)"
Add topic. See the following PDF for details:
customizeServerParmFile.pdfcustomizeServerParmFile.pdf

Topic: "Generating JCL"
Replace topic. See the following PDF for details:
generatingJCL.pdfgeneratingJCL.pdf

Topic: "Creating virtual tables for sequential data"
Revise option descriptions:
Data Set Name
Enter a name for the data set. To use a PDS member as the data source, specify the partitioned data set name. Otherwise, specify a sequential data set or a generation data group (GDG) data set using the GDG syntax such as HLQ.DATA.SEQ(-1). To verify that the data set name exists on the host, click Validate.
Member
If applicable, enter the PDS member name to use. To verify that the member name exists on the host, click Validate.
The DSN is not validated.

Topic: "Restrictions and considerations for loading from a Db2 image copy"
Add the following information.
When you perform any load from a Db2 image copy (Consistent load, Historical load, or Image Copy load), restrictions for loading an accelerator table or an accelerator only table (AOT) on the same or another Db2 subsystem are as follows:
  • The target table must be defined with the same columns, in the same order as the table from the image copy.
  • If you specify an AOT output table, then all of the objects that participate in the run must be AOT output tables.
    When you perform a Consistent load or a Historical load, because accelerator only tables (AOT) do not have partitions, the following requirements apply to partitioned objects:
  • Within a single job, every partition is loaded to the specified AOT if you specify the target creator and name for a partitioned table and do not specify a specific partition.
  • Every partition that you specify for the same source table must have a different target AOT if you specify the target creator and name for a partitioned table, and also specify the PARTITION keyword.
  • When you use the ISPF interface to specify target tables, you cannot specify the same target for some partitions. You must specify one target for all partitions, or specify different targets for each partition.
Image Copy loads only Using the ISPF interface, you can generate JCL for an Image Copy load profile when the image copy has a single table.
The batch job automatically gets the translation information from the Db2 catalog. If the image copy data set has multiple tables or is not registered in the Db2 catalog, the ISPF interface cannot generate JCL. The batch job uses translation information (DBID, PSID, OBID) that is provided in the JCL, and does not perform a lookup from the Db2 catalog.
For sample JCL, see the SHLOSAMP data set.

Topic: "Restrictions and considerations for loading data from an external file"
Add the following subsection.
Considerations and restrictions for accelerator only tables
You can perform a load to an accelerator only table (AOT) from an external file. The following considerations and restrictions apply:
Because VSAM objects do not exist in Db2 for AOTs, loading to both Db2 and the accelerator is not supported. If you attempt to load to both Db2 and the accelerator when the target is an AOT, the product changes the load to an accelerator only load and issues message HLOU5053W.
If you specify the ACCEL_ADD_TABLES or ACCEL_REMOVE_AND_ADD_TABLES option, the product silently ignores it. To add or remove an AOT from the IBM Db2 Analytics Accelerator for z/OS, use the Db2 CREATE/DROP TABLE SQL statements.
The product does not enable or disable acceleration on the table at the conclusion of the load. An AOT is always enabled for acceleration; therefore, the stored procedure calls to enable or disable acceleration cannot be used.
The IBM Db2 Analytics Accelerator for z/OS does not support LOAD REPLACE on an AOT; it supports only LOAD RESUME. However, Accelerator Loader provides LOAD REPLACE support by deleting all existing data from the accelerator before loading the new data. To use LOAD REPLACE, the user ID running the LOAD REPLACE utility must have DELETE authority on the AOT.

Topic: "Example JCL: Consistent load"
Add example JCL for loading data into an alternate accelerator table or an AOT on the same or another Db2 subsystem. See the following PDF for details:
exampleJCL.pdfexampleJCL.pdf

Topic: "Syntax diagram: Consistent load and image copy load"
Add the following options. For the syntax diagram, see the following PDF:
TARGET_SSID
TARGET_CREATOR
TARGET_NAME
syntaxDiagram.pdfsyntaxDiagram.pdf

Topic: "Syntax definitions: Consistent load and Image Copy load"
Add the following options and definitions.
TARGET_CREATOR
TARGET_NAME
The creator and name of the table that is to be loaded. If one value is specified, then both values must be specified to identify the target table.
TARGET_SSID <target_table_ssid>
The four-character Db2 subsystem ID that contains the table that is to be loaded. The TARGET_SSID (if specified) must be on the same LPAR as the SSID on which the source table resides.

Topic: "Accelerator Loader messages"
Add messages. See the following PDF for details:
msgs.pdfmsgs.pdf

Topic: "Load Accelerator with Consistent Data panel"
Add the following field description.
Target SSID
Specifies the four-character Db2 subsystem ID that contains the table that is to be loaded. The default value is the current SSID (that is, the SSID that was selected on the main menu). To select the target SSID, type “?” (question mark) and press Enter. The Db2 Subsystems panel opens, on which you can select the target SSID. If the specified target SSID differs from the current SSID, the product searches for the accelerator that is associated with the target SSID (not the current SSID) and uses it to populate Accelerator name.

Topic: "DB2 Table List panel"
Add the following command and field descriptions:
(on the editable panel, HLOLEDT): T: Type this command in the Cmd field next to the table name to specify the target table. This command opens the DB2 Table Selection panel, on which you can select the target table.
Target Name
The name of the table that is to be loaded.
Target Creator
The creator of the table that is to be loaded.

Topic: "DB2 Table Selection panel"
Add the following information.
The "Type" column displays the value "AOT" the when the object is an accelerator only table.



Update 1
Date of change: April, 2016
Topics: Multiple
Change description: Updates to the documentation in support of enhancements and corrections.

Topic: "What's new"
Topic: "Restrictions and considerations for loading from an external file"
Topic: "Syntax diagram: Load from an external file"
Topic: "Syntax definitions: Load from an external file"
Topic: "Messages and codes"
Topic: "Load Accelerator and Db2 from External File panel"
Topic: "Load Accelerator from External File panel"


Topic: In "Overview" section, "What's new"
    Add the following descriptions of enhancements.

    FORMAT INTERNAL support:
    When performing a load from an external file, you can load SYSREC data that is already in Db2 internal row format. The Db2 UNLOAD utility supports an option to unload the data from a table in FORMAT INTERNAL. This enhancement provides the benefits of reduced CPU consumption and elapsed time in both the UNLOAD and in Accelerator Loader jobs.

    Note: Restrictions that the Db2 LOAD utility imposes when FORMAT INTERNAL is specified also apply to Accelerator Loader.

    UNICODE support:
    When performing a load from an external file, you can use a UNICODE SYSREC file to load data to a UNICODE TABLE.


Topic: "Loading data from an external file" section, "Restrictions and considerations for loading from an external file"
    Add the following information.

    FORMAT INTERNAL support:
    Accelerator Loader does not verify the data in a FORMAT INTERNAL SYSREC data set. It passes the records to Db2 and the accelerator as-is.


    UNICODE support:
    Add the following information to subtopic "General restrictions and limitations".
    Only EBCDIC and Unicode code pages are supported.

Topic: "Syntax" section, "Syntax diagram: Load from external file"
    Update the syntax diagram to add options FORMAT INTERNAL, EBCDIC, and UNICODE. See the following PDF for details:
    Update1_diagram.pdfUpdate1_diagram.pdf

Topic: "Syntax" section, "Syntax definitions: Load from an external file"
    Add new options as follows:

    FORMAT INTERNAL
    Specifies that the SYSREC data is in Db2 internal row format. This control card can be chosen in the ISPF interface by using the field "Format internal SYSREC" on the "Load Accelerator and Db2 from External File" panel or "Load Accelerator from External File" panel.

    UNICODE
    Specifies that the format of the SYSREC data set is UNICODE.

    EBCDIC
    (default) Specifies that the format of the SYSREC data set is EBCDIC.



Topic: "Troubleshooting" section, "Messages and codes"
    Update messages as follows.

    HLO628E: Invalid SYSREC encoding value. Enter a valid value: UNICODE or EBCDIC.

    Explanation: The value that was specified for the encoding scheme is not valid.

    User Response: Specify either UNICODE or EBCDIC.


    HLO629E: SYSREC encoding does not match encoding scheme of selected table.

    Explanation: The encoding scheme that is specified for the SYSREC data must match the encoding scheme of the specified table.

    User Response: Choose a table that has the same encoding scheme as the SYSREC data or, if possible, convert the SYSREC data to the encoding scheme that is
    used by the table.


    HLO630E: Column info DSN value must be empty when Format internal SYSREC is set to YES.

    Explanation: The field Column info DSN and the value YES for the field Format internal SYSREC are mutually exclusive.

    User response: Remove the value in Column info DSN or specify No for Format internal SYSREC.


    HLOP9867E: ACCEL_CURSOR, ACCEL_HLV_SSID, and ACCEL_HLV_GRPNAME are not valid on IDAA_DUAL type loads.

    Explanation: When you are loading data from the server, you can load only the accelerator (keyword IDAA_ONLY). For server data sources, the product does not support loading to both Db2® and the accelerator (keyword IDAA_DUAL).

    User response: Specify keyword IDAA_ONLY to load only the accelerator and resubmit the job.


    HLOP9959E: EBCDIC and UNICODE are mutually exclusive keywords.

    Explanation: To indicate the format of the SYSREC data specify either EBCDIC or UNICODE.

    User response: Correct the LOAD utility syntax and resubmit the job.


    HLOP9960E: The WHEN clause and field specs cannot be specified with FORMAT INTERNAL.

    Explanation: The FORMAT INTERNAL option cannot be specified in the LOAD statement with the WHEN option or field specifications.

    User response: Correct the LOAD utility syntax and resubmit the job.


    HLOU5815E: The SYSREC encoding scheme <encoding_scheme> does not match the table encoding
    scheme <encoding_scheme>.

    Explanation: The table encoding scheme must match the encoding scheme of the SYSREC data.

    User Response: Load the data to a different table that has the same encoding scheme as the SYSREC
    data. Alternatively if possible, convert the SYSREC data to the encoding scheme used by the target
    table and re-run the load job.



Topics: "Reference" section, "Load Accelerator and DB2 from External File panel" and "Load Accelerator from External File panel"
    Add fields as follows.

    SYSREC encoding
    Specifies the SYSREC encoding scheme. Valid values are as follows:
    - UNICODE: When UNICODE is specified, the UNICODE DB2 LOAD utility keyword is generated into the LOAD control cards.
    - EBCDIC: (default) When EBCDIC is specified, no additional keywords are added to the LOAD control cards. EBCDIC is the default for Accelerator Loader and Db2 LOAD.


    Format internal SYSREC
    Specifies whether the SYSREC data is in Db2 internal row format. Valid values are:
    - Yes: The FORMAT INTERNAL keyword is included in the LOAD utility control cards.
    - No (default)

Document information

More support for: DB2 Tools for z/OS
DB2 Analytics Accelerator Loader

Software version: 2.1.0

Operating system(s): z/OS

Reference #: 7041892

Modified date: 19 March 2018


Translate this page: