Sample Processes, Shell Scripts, and API Programs
Connect:Direct® for UNIX provides sample Processes and shell scripts in d_dir/ndm/src, where d_dir indicates the destination directory of the Connect:Direct for UNIX software. You can create similar files with a text editor. In addition, instructions for creating sample Processes and shell scripts are in the README file in the same directory.
The following list displays the file names of sample Processes and the type. Modify the Processes as required.
The following table displays the names of sample shell scripts. Modify the shell scripts as required.
|File Name||Type of Shell Script|
|wildcard||send multiple files to a PDS|
|statarch.sh||archive statistics files|
|staterestore.sh||restore statistics files that have been archived|
|lcu.sh||launch the Local Connection Utility tool|
|spadmin.sh||launch the Secure+ Admin Tool|
|spcli.sh||launch the Secure+ CLI|
|spcust_sample1.sh||configure Secure+ for the SSL or TLS protocol|
The following information displays the names of sample programs and a description:
- apicheck.c - Submits a Process to copy a file to a remote system. MAXDELAY is used in this example, which means that the program will not finish execution until the file has been transferred. A standard c compiler is used to compile this module.
- apicheck.C - Same as apicheck.c, except that it is compiled with one of the C++ compilers listed in the Connect:Direct for UNIX User Guide.
- exit_skeleton.c - This program is a skeleton of a user exit program that works in conjunction with Connect:Direct for UNIX. It demonstrates usage of all three user exits.
- exit_skeleton.C - Same as exit_skeleton_c, except that it is compiled with one of the C++ compilers listed in the Connect:Direct for UNIX User Guide.
- exit_sample.c - This is the same program as the skeleton user exit program, except that the security exit is demonstrated with code that approximates PassTicket functionality.