xvsamExport

xvsamExport performs an opposite operation to xvsamImport; it saves the content of an XVSAM cluster in a UNIX flat file. Data can be stored in two different formats: binary form - each record is written at the end of the preceding one - or ASCII form, where a new line character is added at the end of each record.

Syntax

xvsamExport [-p][-d][-l<debug level>][-k<skip>][-c<count>][-b<from_key>]

[-B<from_key_hex>][-e<to_key>][-E<to_key_hex>]

<catalog> <cluster> [<data file> <B|T>]

Options

-k<skip> records number to skip

-c<count> records number to export

-b<from_key> define start key to export records from (char)

-B<from_key_hex> define start key to export records from (hex)

-e<to-key> define end key to export records to(char)

-E<to_key_hex> define end key to export records to(hex)

-p prints input parameters

Parameters

catalog	is the name of the catalog the cluster belongs to
cluster	is the name of the cluster to be deleted
flat file	is the complete absolute path of directories and the name of the UNIX file that must be exported
B\|T	output file type: B the file to be exported is a binary file T the file to be exported is an ASCII text file

A protocol file can be created during the file export, by specifying -d<name>. If no name is specified, the protocol file will be created as xvsamExport.log.

The level of detail with which XVSAM should report the sequence of operations on the protocol file, may be specified by means of the -l<level> optional parameter.

At the end of the export operation, xvsamExport reports how many records have been read from the XVSAM data set and how many of them have been written on the UNIX file.

Example

# xvsamExport TESTCAT SNICTHLP /some/where/else/snicthlp B
xvsamExport: Records read[159] written[159]

Return codes

0	Function correctly executed
12	error(s) trapped