Data set and file names in configuration files
File names for UNIX and Windows
The file names that you specify in UNIX and Windows configurations must refer to files that can be accessed or created by the user ID that issues the apply request. If the file does not reside in the current directory, you must specify the complete path as part of the parameter value.
High-speed Apply Engine processes file names exactly as they are specified for UNIX and Windows configurations. If your operating system is case sensitive, you must specify file names with the appropriate case.
You can simplify High-speed Apply Engine operations by using the default configuration file name for your apply requests. The default configuration file name for UNIX and Windows is apeconfig.ini (lowercase characters).
High-speed Apply Engine uses these file names if no other configuration file is specified for the request. If the default configuration file contains all of the necessary configuration information, you can initiate apply processing by typing the appropriate command with no parameter qualifiers. For more information, see Creating and running an apply request for Oracle.
Data set names for mainframe targets
The data set names that you specify in the configuration information for existing data sets must be catalogued or in the JCL. Any new data sets will be catalogued. Data set names must be fully qualified and conform to the naming rules for data sets on your operating system. If you specify an invalid data set name, the apply request terminates when it attempts to allocate the data set.
For mainframe targets, the High-speed Apply Engine processes file names exactly as they are specified. BMC Software recommends that you do not specify mixed case or lowercase data set names.
Some file-name parameters default to DD statements in the JCL if you do not specify a file name. The default for the configuration file is the SYSIN DD statement. The default for the Library parameter is the data set that the APTDBRM DD statement specifies. For more information, see Creating and running an apply request for DB2 on mainframe targets.