EXPORT configuration command

The EXPORT command is useful for multiple purposes, such as backing up configuration information and cloning a configuration for a Classic data server.

Description

You can use the EXPORT and IMPORT process to restore a specific configuration environment to a previous point in time. By using the EXPORT command, you can create a command file that is based on the configuration environment of a running Classic data server. You can then use this command file to update a different configuration file by using the IMPORT command.

The target of the EXPORT command is a PDS member or a sequential file. If the file or member that you specify in the EXPORT command already exists, it is rewritten. If the file or member does not exist, it is created.

If you predefine the EXPORT target:
  • The minimum record length is 80 bytes.
  • The format can be either fixed or variable length records.

The EXPORT command does not support GDGs.

The owner ID associated with the Classic data server job must have authorization with an external security manager (ESM), such as the Resource Access Control Facility (RACF®), to create or access the EXPORT target data set (sequential file or PDS member).

When a PDS member is specified as the target of the EXPORT command, an attempt to run the EXPORT command fails if another user or job accesses the PDS member at the same time. To avoid this situation, you create a PDS member to use for the IMPORT and EXPORT process only.

Exporting configuration information

EXPORT command format:
EXPORT,CONFIG,FILENAME=DSN:dsname | DSN:dsname(member) | DDN:ddname
 | DDN:ddname(member)

Example

The following example shows sample file contents of an EXPORT file:
--SET,CONFIG,SERVICE=GLOBAL,MESSAGEPOOLSIZE=67108864;
--SET,CONFIG,SERVICE=GLOBAL,DATACONVERRACT=1;
--SET,CONFIG,SERVICE=GLOBAL,FETCHBUFSIZE=32000;
--SET,CONFIG,SERVICE=GLOBAL,DECODEBUFSIZE=8192;
--SET,CONFIG,SERVICE=GLOBAL,STATICCATALOGS=0;
--SET,CONFIG,SERVICE=GLOBAL,TASKPARM='';
--SET,CONFIG,SERVICE=GLOBAL,DATAVALIDATEACT=0;
--SET,CONFIG,SERVICE=GLOBAL,REPORTLOGCOUNT=0;
ADD,CONFIG,SERVICE=CNTL,SERVICECLASS=CNTL;
--SET,CONFIG,SERVICE=CNTL,INITIALTHREADS=1;
--SET,CONFIG,SERVICE=CNTL,MAXTHREADS=1;
--SET,CONFIG,SERVICE=CNTL,MAXUSERS=100;
--SET,CONFIG,SERVICE=CNTL,TRACELEVEL=4;
--SET,CONFIG,SERVICE=CNTL,RESPONSETIMEOUT=5M;
--SET,CONFIG,SERVICE=CNTL,IDLETIMEOUT=5M;
SET,CONFIG,SERVICE=CNTL,SEQUENCE=1;
In the example, the export operation produces a command file of all overridden parameters as active SET commands. SET commands are also generated for all parameters that use default values. These particular SET commands are generated as comments. The prefix "– –" in the first two columns of the command identifies comments.

Parameters

ddname
The DD statement defined in the JCL that starts the Classic data server. The DD name points to the target of the EXPORT command.
dsname
The name of the EXPORT data set.

Usage notes

The following rules apply to the format of command files:
  • Commands must end with a semicolon.
  • A comment begins with two dashes ("– –") in columns 1 and 2.
  • A single command can span multiple lines. You can break a line after a comma or a space. You cannot break a keyword or value across multiple lines. For example:

Example

This EXPORT command creates the file USER.TEST.FILE if the file does not already exist. 
EXPORT,CONFIG,FILENAME=DSN:USER.TEST.FILE