This section describes problems that can occur when you use the supplied warehouse programs, and suggests solutions to resolve them.
Verify that the VWxxxxxxxx.VWPRCPY trace file contains a message that says the FTP command file could not be created, AS/400 error = 3021.
If this is the case, the user profile under which the agent process was running does not have the authority to create members in the QIWH/FTPCMD source physical file.
To fix this problem, either use a different user profile to run the agent or grant the agent user profile authority to access the QIWH/FTPCMD file.
The library or physical file name that you supplied with the FTP command file member does not exist or is invalid. Because of this, FTP executes successfully, but cannot execute the stream of commands in the file. As a result, FTP does not transfer the data. The FTP message log does not get generated.
To resolve this problem, ensure that the library, physical file, and command member actually exist. If they do, check for typographical errors in the command file parameter value passed to VWPFTP. The VWPFTP trace lists the parameter values that were passed to it.
You are running one of the OLAP Server warehouse programs from the Data Warehouse Center, and you receive an error message stating that the (rules or load) file cannot be found.
The location of the rules file or load file is unknown.
When you define the step that uses these warehouse programs, specify whether the load file or rules file exists on the client workstation or on the server workstation. If you specify that the file is on the client workstation, you need to fully qualify the file name (drive, path, file name, and extension) when you define the warehouse source. If you specify that the file is located on the server workstation, you need to specify only the file name (do not include the drive, path, or extension) and verify that the file is located in the appropriate directory on the server workstation.
You are running user-defined programs, and receive an error that indicates that they are not found, or other errors.
One possible cause as that the user-defined program, or services used by the program, are installed in a directory that is not listed in the PATH statement. For example, the user-defined program could be installed on a LAN drive. Another possible cause is that the user-defined program requires access to environment variables that are defined as user variables. The environment variables must be defined as system variables for the user-defined program to access them.
Verify that the user-defined program is installed in a directory listed in the PATH statement. Verify that any directories that contain programs or services that the user-defined program will use are also listed in the PATH statement. Verify that all environment variables used by the user-defined program are defined as system variables, not user variables.
Use the trace level setting to validate the path and variables that the user-defined program has access to under the warehouse agent:
Two files, AGNTxxxx.SET and AGNTxxxx.LOG, are created at the agent site, where xxxx is the process ID of the agent. For some user-defined programs, a third log file will be created, trcxxxx.log.
If you encounter problems using DB2 Universal Database batch programs, verify that the long form of the DB2 UDB CONNECT statement is used:
CONNECT TO <database> USER <user ID> USING <password>
Do not use:
CONNECT TO <database>
Use the long form because the warehouse agent is running as a system process and does not have access to any of the user information.