Skip to main content
Ex Libris Knowledge Center

Custom services -- check input file

  • Article Type: General
  • Product: Aleph
  • Product Version: 20
  • Relevant for Installation Type: Dedicated-Direct; Direct; Local;


When making a custom service how can the xml (or other) file be designed to
A. check for the existence of a file before allowing user to submit
B. Check if specific characters do or do not exist before allowing user to submit

For example, in the case below the first field called “first name”
A. can be empty and the job can still be submitted. How can this be prevented?
B. can have characters such as [ and { and the job can still be submitted. How can this be prevented?

Resolution:
When making a custom service how can the xml (or other) file be designed to
A. check for the existence of a file before allowing user to submit
B. Check if specific characters do or do not exist before allowing user to submit

Neither option is currently available.

About A, nothing can be done. All the files existence checks in Aleph services are done by COBOL programs (named b_[service_name]_check_param.cbl), we do not have a script for this.

About B, same thing. The only characters that are always forbidden are the following ones, hard-codingly checked at submitting time: ? { ' ` ^ > ,

But, thoiugh it is not possible to confirm the existence of a specified input file prior to submission, it *is* possible to produce an error message in the job log file if the input file parameter is blank. Lines such as the following would be added to the $aleph_proc procedure:

if ($p_input_file == "") then
echo " *******************Error: Input file cannot be blank************************* "
endif

[Note: in some procs the input file parameter may be "p_input_file_name" rather than "p_input_file".]

Additional Information

You have requested that the functionality of Aleph be enhanced. Experience has shown that enhancement requests submitted through the ELUNA or IGeLU enhancement processes have a much greater chance of being included in new versions of Aleph than those submitted through the eService. These processes provide a means for gauging the importance of enhancement requests, the impact that they would have, and the best way to implement these for the entire customer base. Enhancement requests in the eService have none of these features, so the Product Manager is usually not able to determine their relative priority vis-a-vis others when planning for new releases. For these reasons, we strongly recommend that you submit your enhancement request through one of these channels.

Category: Background processing


  • Article last edited: 10/8/2013