Tips and notes on generation

If WebAdmin is to be used as a "message destination", you should make sure that the UTM application is able to meet the resulting resource requirements. You must set suitable generation parameters, in particular the size of the page pool and the restart area. It is important to bear the following points in mind:

• Each message that is present in the queue occupies an entire page in the page pool. It is advisable to configure a suitably large page pool via the PGPOOL parameter of the MAX statement. The number of page pool pages specified here should be at least as large as the generated queue level for the message queue.
• You can limit the maximum number of messages that can be held in a queue via the QLEV parameter. This prevents a page pool overload. It is also advisable to set QMODE=WRAP-AROUND in order to ensure that openUTM continues to accept new messages and discards old messages from the queue when the specified queue level is reached.
• WebAdmin reads messages from the queue in the KDCWADMI program unit by means of a loop of DGET calls at the KDCS interface. On each DGET call, openUTM writes information to the restart buffer. If the size of the restart area is insufficient, the loop is interrupted and an additional communication step is necessary. For performance reasons, you should therefore use the RECBUF=(..., length) parameter of the MAX statement to set up a sufficiently large restart area: approximately 30 bytes per message are required for restart information.

Tip:
It can be very useful to use WebAdmin as a message destination for messages generated by the program units themselves. However, the best solution here is probably to set up a separate UTM queue for this purpose, e.g. a Tac OWNMSGQ. Diagnostic messages, statistical application data, status messages etc. can then be sent to this queue and can be displayed directly by WebAdmin. Here again it is advisable to send the messages to the queues in printable form. To do this you should set the message type to 'printable text' in the associated message collector.

Note:
When using this functionality offered by WebAdmin and openUTM, you should remember that the messages that WebAdmin fetches from the UTM queues actually disappear from the queues if the default value 'Consume Message=Yes' is set for the message collector. WebAdmin should therefore only poll queues with 'Consume Message=Yes' that are intended precisely for this purpose, i.e. whose messages have been sent to the queue specifically for WebAdmin. If any other queues are polled by WebAdmin then this is sure to create havoc with the logic of the UTM application since important messages will suddenly disappear.

Additional note:
If read access to the selected UTM queue is protected by an access list (generation parameter Q-READ-ACL of the Tac or User queue), then you must make sure that WebAdmin possesses the privileges required to read from the queue.