Handling program start request failures for APPC
When a program start request is received by an i5/OS® subsystem on the application server (AS), the server attempts to start a job based on the information sent with the program start request. The application requester (AR) user's authority to the application server (AS), existence of the requested database, and many other items are checked.
If the AS subsystem determines that it cannot start the job (for example, the user profile does not exist on the AS, the user profile exists but is disabled, or the user is not properly authorized to the requested objects on the AS), the subsystem sends a message, CPF1269, to the QSYSMSG message queue (or QSYSOPR when QSYSMSG does not exist). The CPF1269 message contains two reason codes (one of the reason codes might be zero, which can be ignored).
The nonzero reason code gives the reason why the program start request was rejected. Because the remote job was to have started on the AS, the message and reason codes are provided on the application server, and not the application requester. The user at the AR only knows that the program start request failed, not why it failed. The user on the AR must either talk to the system operator at the AS, or use display station pass-through to the AS to determine the reason why the request failed.
Parent topic:
Working with distributed relational database users
