11.2.4 Responding to response-waiting events
You can respond to response-waiting events from JP1/IM - View. For example, a message might ask the operator if he or she wants to continue batch processing, to which the operator can respond yes in text format. You can enter responses in the Enter Response window displayed from a response-waiting event.
You can display the Enter Response window by clicking a response-waiting event in the list of events in the following pages:
-
Response-Waiting Events page
-
Search Events page
You can only respond to events from this page if the events in the search results are found on the logged-in manager host.
-
Related Events window
You can respond to events in this window if the window was displayed from the Response-Waiting Events page. If you displayed the Related Events window from the Search Events page, you can only respond if the events in the search results are on the logged-in manager host.
- Organization of this subsection
(1) Framework in which responses are made to response-waiting events
You can only respond to response-waiting events if the process that issued the event still exists and is in a status that allows it to accept the response. You can view the status of the source process as the value of the Status attribute in the Response attributes area of the Enter Response window. JP1/IM - Manager checks the status of the source process when you open the Enter Response window. If a communication error prevents it from contacting the process and identifying its status, the message KAVB0555-E appears and the Enter Response window does not open.
|
The following table lists the statuses that appear as the value of the Status attribute in the Response attributes area:
Source process status |
Description |
Can response be entered |
---|---|---|
READY TO RESPOND |
The job that issued the event is waiting for a response. |
Y |
NO LONGER MANAGED BY BJEX or NO LONGER MANAGED BY JP1/AS |
One of the following applies:
|
N |
RESPONDED SUCCESSFULLY |
You have successfully responded to the response-waiting event in the Enter Response window. This status appears only in the Enter Response window when you have just entered a response. |
N |
ALREADY RESPONDED |
An operator has already responded to the event. This status appears when you display or refresh an Enter Response window for an event for which a response has already been entered. |
N |
- Legend:
-
Y: A response can be entered.
N: A response cannot be entered.
You can enter a response if the status of the source process is READY TO RESPOND. You cannot respond to response-waiting events in any other status, because the event has either already been responded to or the source process no longer exists.
When you respond to a response-waiting event, the response you entered is sent to the process that issued the event. If the response reaches the source process and is successful, the status of the response-waiting event changes to Processed. The response-waiting event is then released from the hold-and-accumulate state and disappears from the Response-Waiting Events page.
A timeout occurs if JP1/IM - Manager has not successfully communicated with the source process after 60 seconds when attempting to check its status or provide a response. You can change the timeout time. Consider extending the timeout time if you frequently encounter an error message (KAVB0554-E or KAVB0555-E) due to heavy loads on the source server or network congestion. For details about how to set the timeout time, see 11.3.4(1) Setting the timeout time for connections.
(2) Conditions for responding to response-waiting events
You can respond to response-waiting events under the following conditions:
-
The operating permission of the responding JP1 user is JP1_Console_Operator or higher.
-
You have not yet responded to the event.
You can only respond once to a response-waiting event, even if you acquire the event again by changing the event acquisition start location of the event acquisition filter.
-
The response-waiting event was received after you enabled the response-waiting event management function.
You cannot respond to response-waiting events received while the response-waiting event management function is disabled.
-
When searching for events, the logged-in manager host is specified as the search target.
(3) Using the response command of BJEX or JP1/AS
If a communication error between the source process and JP1/IM - Manager prevents you from responding to an event from JP1/IM - View, you can use the response command (bjexchmsg or adshchmsg) provided by the source process on the source host. You can also use this approach to respond to events that were released from the hold-and-accumulate state and removed from the event database. For details about how to respond using the response command (adshchmsg) of JP1/AS, see JP1/Advanced Shell Description, User's Guide, Reference, and Operator's Guide.