USERREPLY_WAIT_MAXCOUNT parameter (specifies the maximum number of concurrent reply-request messages that can be output for a physical or logical host)
- Organization of this page
Format
#-adsh_conf USERREPLY_WAIT_MAXCOUNT maximum-number-of-concurrent-reply-request-messages-to-be-output
Description
This parameter specifies the maximum number of concurrent reply-request messages to be output for each physical or logical host when the user-reply functionality is used.
Operands
- maximum-number-of-concurrent-reply-request-messages-to-be-output ~<unsigned integer>((1 to 100))<<5>>
-
Specifies the maximum number of concurrent reply-request messages to be output for each physical host or logical host. This specification limits the number of reply-request messages that can exist for each physical host and logical host.
Because a maximum of 2,000 reply-waiting events can be accumulated in JP1/IM - View, specify a value (to be applied to each host that sends reply-waiting events) that ensures that the following condition is satisfied:
Maximum number of concurrent reply-request messages that can be output by each host times the number of hosts that send reply-waiting events to the same JP1 event destination (HOSTNAME_JP1IM_MANAGER parameter value)
+ total number of other products' reply-waiting events that can be accumulated
< 2,000
Notes
-
Do not specify this parameter in the job environment file. If this parameter is specified in both the system environment file and the job environment file, the specification in the job environment file will be ignored.
-
If output of more reply-waiting events than is specified in this parameter is attempted, the processing will be placed on wait status until enough space becomes available in the shared memory. Available space in the shared memory is checked every three minutes for up to three times. If there is still not enough space after three attempts, an error will result. Therefore, if multiple jobs output reply-request messages concurrently, specify an appropriate value so that the number of reply-waiting events will not exceed that value.
-
This parameter is ignored when debug execution is performed with the standard input and output specified as the input source and output destination, respectively, of the user-reply functionality.