The ksc_capture_output special command is only used in validations. It is used to get data from an alternate source, and use that data to populate an auto-complete field. This functionality provides additional flexibility when designing auto-complete lists.

Many enterprises have found that they need to use alternate sources of data within their applications. Examples of these sources might be a flat file, an alternate database source, or output from a command line execution. The ksc_ capture_output command may be used in conjunction with these alternate data sources, in the context of a validation, to provide a list of values on the fly.

The syntax for the ksc_capture_output is:

ksc_capture_output <command>

In the Validation Workbench, under Validated By, choose either Command With Delimited Output or Command With Fixed Width Output and input the delimiting character or field length information. Then, under New Command, enter the steps. The example below would put the validations into the address.txt file, then run the ksc_capture_output against the address.txt file:

ksc_capture_output cat[AS.PKG_TRANSFER_PATH]address.txt      

In this case, the entire sequence of commands would be executed on the local machine where the PPM Server is running. This is the preferred method of invoking ksc_capture_output. The ksc_capture_output command may be embedded between ksc_connect and ksc_exit commands, but the time delay is significant depending on network load (because the validation actually requires an entire TELNET, SSH or SSH2 session to be generated to the remote machine). It is recommended that ksc_capture_ output only be used in a local execution scenario.

ksc_capture_output may be called more than once. Each call will append the results to the previous call.