| version | Version of structure format |
| argc | Parameter count of loaded service |
| service_type | Type of client request |
| flags | Request context control flags |
| argv | Parameter list of loaded service |
| service_name | Name of loaded service |
| pgm_name | Name of the main program associated with the service |
| epoint_name | Name of the entry point to invoke |
Comments:
This exit gives you the opportunity to handle an unmapped named external input parameter that has been specified in the client request. The exit program would typically handle the parameter by setting an appropriate value in one or more of the data areas addressed by argv, setting up data to be used for ANSI ACCEPT statements (accept_buf), or setting up the application’s command line (cmd_line). The exit should use the fn_alloc_mem support function of the exit_info funcs structure to allocate any memory used for the setting up of accept_buf or cmd_line. If the exit chooses to override any of the request context fields, it must return IDP_EXIT_HANDLED.
The user exit program owns the exit_data field of the IDP_EXIT_INFO structure. You would typically use it to preserve context information between exit point invocations. You can use it when returning any of the IDP_EXIT_ return values.