NOTE: This function is not applicable to Banner defined repositories.

The security loader log provides detailed status/diagnostic messages on security loading, including the date and time of processing and outcome. These messages are listed below, along with the likely problem and a suggested course of action.

When interpreting the messages below, bear in mind that anything with a "$" in front of it is a substitution variable. In the log messages, the "$" will be replaced by appropriate data. Also, note that "$@" is a special Perl variable which contains the underlying error from the operating system.

"ONLINE repository update specified in config file. Cannot load batch file."

Problem: If the repository security update is configured as ONLINE, it cannot be loaded in batch. It can only be loaded and updated via the administrator interface page.

Solution: Change the update indicator in the security wizard or stop trying to load files to ONLINE repositories.

"File $filename does not verify: value $value not found"

Problem: When the security loader loads a file, it checks for the verification string on the first line of the file on the column indicated by the security configuration. If it is not there, the file is rejected with this message.

Solution: Check the input file on the host to make sure the verification value matches. If it does, make sure the correct file is being downloaded (i.e., check the ftp script). If it does not match, fix the verification string in the security configuration. Re-download the file after fixing definitions.

"This line has more data than the definition: '$line'"

Problem: The security loader tried to load a line of data according to the definition specified. However, the line was longer than the spec.

Solution: Check the output file on your host. Make sure it is correct. If it is, fix the security definition on the server and re-download the file. If the mainframe file is not correct, fix it and then re-download the file.

"Error parsing line $line -- too few elements"

Problem: This is the flip side of the above message -- not enough data was on the line.

Solution: Same as previous.

NOTE: If a message appears in your security loader log which is not included in this list, you may need to contact Banner ePrint's customer support personnel for assistance.

Related Topics

Using the Security Loader Log