Basis Errors and Solutions

Symptom

This Note only describes the new process of using the load utility with USS fifos. If you are looking for the old fastload process, see Note 1296510.
This Note conatins additional information to the SDN articleSAP Unicode Conversion on DB2 for z/OS – Cookbook. An up-to-date version of the cookbook is appended to this Note. Additional informations include:
SAP patch versionDB2, z/OS and USS PTFsSupported parameters for the fast load configurationError handling information and workaroundsUnsupported szenariosOther terms

DB2 z/OS Load Utility
Fast Load
Unicode Conversion
USS Fifos
Reason and Prerequisites

————————————————————————

Solution
SAP fixes
db2radm.jar#6
Fixes for db2radm.jar are documented in SAP Note 1297362. Please take needed fix from there.
SAP kernel 7.00
R3load#101
This fix adds USS fifo support and support for DB2 V8 REORG format.R3ldctl#20
Use DB2 managed storage allocation for all objects, see Note 1295945.lib_dbsl#194
This fix adds USS fifo support and support for DB2 V8 REORG format.db2radm#21
This fix adds USS fifo support.db2jcllib#5
This fix adds USS fifo support.
SAP kernel 7.01
Fast load with USS fifos and SAP kernel 7.01 is still in beta status. Please open a customer message for further guidance.
R3ldctl#2
Use DB2 managed storage allocation for all objects, see Note 1295945.db2jcllib#2
This fix adds USS fifo support.db2radm#4
This fix adds USS fifo support.
————————————————————————

IBM fixes
LOAD UTILITY LOADING ROWS IN WRONG PARTITION WITH VARGRAPHIC PARTITIONING KEYS AND UNICODE TABLE: APARPK78713NEW FILE FORMAT BIT(8): APAROA27728FILEDATA=RECORD support for JCL: APAROA25280FILEDATA=RECORD support for DFSMS: APAROA25204and
APAROA25206z/OS USS named pipe support for FTP: APARPK71213FILEDATA=RECORD support for the DB2 TEMPLATE utility: APAR
PK70269Trusted record format support: APARPK61759With DB2 V8, an additional enhancement for DB2 LOAD is needed:
APARPK67754RUNSTATS FREQVAL hits Abend 0C4: APARPK50279MSGDSNU1250I DURING UNLOAD WITH OPTION CCSID: APARPK55077NEW FUNCTION: support 100k open datasets per DB2: APARPK29281ABEND04E RC00C90101 IN DSNONLLE ERQUAL5063: APARPK63781RTS ABEND04E RC00C90101 DSNKFTCH ERQUAL 1006 INVALID
PARENT TOKEN RECEIVED FROM IRLM ON A LOCK REQUEST: APARPK62953SERVICEABILITY APAR: APARPK70351IGD17036I DIRECTORY SPACE BEING REQUESTED IS
GREATER THAN PRIMARY SPACE (DB2 V8 only): APARPK70344IN DB2 V9 NFM, WHEN RUN LOAD UTILITY WITH SORTKEYS >= 2147483648,
DSNU048I MESSAGE WILL BE ISSUED: APARPK80477
————————————————————————

Parameters

These parameters influence the fast load process:
Parameters for R3load:dbs_db2_uss_pipes
Environment variable; set to 1 to request USS fifo usage which is recommended.dbs_db2_hlq
Environment variable; it defines the high level qualifier used for XSYSUT1, XSORTOUT, XSYSERR and XSYSMAP datasets.R3LD_FLD_FORCE_USS
Environment variable; set to 1 to force USS pipe usage during beta shipment.R3LD_FLD_STATS_SAMPLE
Environment variable; it defines the SAMPLE parameter for inline statistics performed by the load utility during fast load; default is 5.dbs_db2_uss_dir
Environment variable; directory where fifos on USS are created; default is /tmp.R3LD_FLD_SORTNUM
Environment variable; is used for the SORTNUM parameter in the load statement; defaul is 10.dbs_db2_fastload_tracedir
Environment variable; directory where all the fast load log files are written. Default is relative pathfldlogsfrom SAPinst installation directory.R3LD_FORCE_SET_UTILFORMAT
Parameter only needed for the beta shipment with kernel 7.01. You need to set this parameter to 1 until official patches of dbsl and R3load are available on SMP.Parameters for db2radm:FIFOOPENTIME
Environment parameters defining the timeount (in seconds) for opening a USS fifo (default 600 secs). We strongly recommend to set this parameter higher than DB2 parameter STORTIME. For STORTIME NOLIMIT, use 86400 (1 day).FIFOIOTIME
Environment parameters defining the timeount (in seconds) for performing IO on a USS fifo (default 300 secs). We strongly recommend to set this parameter higher than DB2 parameter STORTIME. For STORTIME NOLIMIT, use 86400 (1 day).
————————————————————————

Error handling information and workarounds
DB2_R3LD_DBG :Trying to create fastload_tracedir “”
ERROR occured on mkdir() for dir “ File existsThis Error occurs due to a race condition in the fldlogs directory create code. A fix will be provided soon. Until then, please create the fldlogs directory "” manually as a subdirectory of your sapinst installation directory. Or you set environment variabledbs_db2_fastload_tracedirto an existing directory with write permissions for your sidadm. R3load and db2radm will write their fast load logs into that directory.UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X’00E40071′ with
DSNU032E I/O ERROR ON WORKFILE … BSAM read error:This error occured if LOAD was scheduled by WLM after USS fifo is timed
out already. Please increase FIFOOPENTIME and FIFOIOTIME accordingly.
————————————————————————

Unsupported szenarios
Fast load on Windows is not supported yetFast load and BRF format on DB2 V9 (see SAP Note 1309153) is not supported yet. Please note that BRF with UTS (for example if you plan to implement partition-by-growth table spaces) is not supported by IBM.Fast load is not supported for splitted tables that have lobs. Setting of dbs_db2_serialized and defining package groups has then not the effect of loading the table with RESUME YES. If you really need to split a table that has lobs you will need to import the table with parallel SQL inserts, see Note 1039120.
————————————————————————