Chapter 9. Utilities with XML 231
DSNTIAUL generates in the SYSPUNCH data set the following LOAD control statement:
LOAD DATA LOG NO INDDN SYSREC00 INTO TABLE BK_TO_CSTMR_STMT
(MSG_ID POSITION( 1 ) VARCHAR NULLIF(38)='?',
MSG_CRE_DT_TM POSITION( 39 ) TIMESTAMP WITH TIME ZONE EXTERNAL(32)
BK_TO_CSTMR_STMT POSITION( 72 ) CLOBF )
Notice the DB2_GENERATED_DOCID_FOR_XML column is not included.
You should edit the LOAD control statement to include either RESUME YES or REPLACE, and
change INDDN SYSREC00 to INDDN SYSREC.
You may also perform the following tasks:
specify SQL as first PARM:
RUN PROGRAM(DSNTIAUL) PLAN(DSNTIB91) PARMS('SQL,LOBFILE(XMLR4)') -
Use an SQL statement as input to SYSIN:
SELECT BK_TO_CSTMR_STMT FROM XMLR4.BK_TO_CSTMR_STMT ;
In both cases, a sequential data set SYSREC00 containing the normal data fields and the
names of the XML output files is produced. All the XML output files have a name in the
following form (where xxxx can be in the range 0000 - 5882):
The files are dynamically allocated as sequential files with the values:
This BLKSIZE is the optimal for 3390 devices.
Use DSN1COPY to copy tables from one subsystem to another. When you copy tables from
one subsystem to another, you must ensure that the version information on the target
subsystem matches the version information on the source subsystem.
Restriction: DB2 XML data is condensed by substituting strings by unique IDs. These
unique IDs are stored in the catalog table SYSIBM.SYSXMLSTRINGS and they are not
available in the related XML table space. Therefore, do not copy XML table spaces from
one subsystem to another using DSN1COPY.