Extracting persistent data store data to flat files

The format of the data is converted to tab-delimited columns. The data is written to separate files for each table; therefore, the data format for all rows in each data set is consistent. The program also generates a separate file. This file contains a single row that provides the column names in the order in which the data is organized. This file is also delimited for ease of use. An option (NOFF) on the KPDXTRA program bypasses creating the separate file and places the column information as the first record of the data file.

This file is not tailored by the PARMGEN or Configuration Manager at installation time and must be modified to add pertinent information.

The output from this job is written to files with the following naming standard:

&hilev.&rte.tablename.D
&hilev.&rte.tablename.H

The tablename is the first eight bytes of the actual table with any invalid characters changed to "#". The "D" suffix is for the data file and the "H" suffix is for the header file. Note that the NOFF parameter can be passed to the KPDXTRA program to merge the data from the header file into the data file and therefore not create a unique header file. The high level and mid level qualifiers are passed as a parameter to the KPDXTRA program (PREF=xxxx) and are therefore controlled by the KPDPROCC member in the RKANSAMU data set.

All data sets are kept in read/write state even if they are not active. This makes the data sets unavailable if the monitoring server is running. Jobs cannot be run against the active data sets and the inactive data sets must be taken offline.

You can remove a data set from the monitoring server by issuing the modify command:

F stcname,KPDCMD QUIESCE FILE=DSN:data set

If you must run a utility program against an active data store, issue a SWITCH command prior to issuing this QUIESCE command.