Login:
  • Home
  • →
  • Desktops
  • →
  • Free manual HP   HP NonStop G-Series
Votes - 0, Average rating: 0 ( )

User manual HP, model HP NonStop G-Series

Manafacture: HP
File size: 101.31 kb
File name:
Language of manual:en
Free link for this manual available at the bottom of the page



Other manuals for this model:

manual abstract


Developing Queue Manager Applications
Application Development Steps
After the user logs on, the application produces a menu screen from which the
user can select groups of functions, such as those making up a purchase order.
After a group of functions is selected, the application allows the user to execute the
function. Part of the execution could consist of enqueuing the purchase order on a
Queue file. Later, another process in the application will retrieve the order from
Queue Manager and process it.
Screen design should be consistent. You can provide consistency by selecting a
standard screen layout, with headings, fields, body, and error messages always
appearing in the same locations on each screen:
If you are adding Queue Manager functionality to an existing application, decide how
to integrate the new functions, screens, and keys into the existing application.
Step 4: Dividing
Consider how the work performed by the application should be divided among users,
Application Tasks
processes, and other application programs. Refer to Section 1 in this manual, and to
the PATHWAY manuals referenced in the Preface.
As you define how Queue Manager will interact with other processes, try to balance
the number of enqueued requests with the number of servers to be triggered by the
Wait Manager to handle those requests. If just one request is enqueued and ten
servers are available to handle that type of request, all ten will attempt to dequeue the
request when triggered by Wait Manager. Only the first server will successfully
dequeue the entry, while the others will go back to sleep, having wasted nine system
I/Os. Balancing requester and server processes avoids inefficient use of system
resources, that is, excessive polling of the Queue file by server processes.
Step 5: Defining the UOW
Design the content of the Queue Manager UOWs and responses, and determine how
Content
processes should interpret them. A single application uses many UOWs containing
different types of information.
Bear in mind that Queue Manager provides just one physical Queue file on which all
processes enqueue requests. The physical Queue can be divided into logical Queues
by Queue name. A Queue file read by a server process typically will search on Queue
name, but not always. Other keys can include priority or time enqueued. Thus,
designing a UOW entails not only deciding what the content will be, but also whether
to define such parameters as the Queue Name (the primary key), time stamp, priority,
CPU name/identifier, response requirement, and Wait Manager notification, if any.
Step 6: Planning High-Level
Because Queue Manager requires TMF, the following guidelines should be taken into
Transactions with TMF
account as you decide what to include in each transaction:
Issue an END-TRANSACTION immediately or almost immediately after a ENQ
UOW to prevent a lockout on the enqueued request.
A lengthy transaction could maintain locks long enough to reduce dramatically
the number of concurrent operations on the Queue file.
In general, include only one UOW in each IPC. This also helps avoid lengthy
record locks that prevent other operations from being performed.
46517 Tandem Computers Incorporated
3–3

...

Other models in this manual:
Desktops - HP NonStop L-Series (101.31 kb)

Reviews



Your review
Your name:
Please, enter two numbers from picture:
capcha





Category