|SAS/CONNECT User's Guide|
The queue manager is responsible for allocating the queues, maintaining access information for each of the queues, and administering the messages that belong to each queue.
Queues can be designated as permanent or temporary. Permanent queues remain until they are explicitly deleted. Temporary queues are implicitly deleted when they are closed.
Messages within permanent queues may be persistent or non-persistent. Persistent messages remain indefinitely until they are fetched, even if the DOMAIN server process is shutdown. Non-persistent messages are purged when a queue is closed.
The queue manager is solely responsible for maintaining the queues and for ensuring that the messages in the queues reach their destination when requested and are not lost. The queue manager is also responsible for establishing the information that is needed by the network protocols that are being used to transmit the messages to and from the queues.
The COLLECTION option must be specified in the PROC DOMAIN statement, in order to use indirect messaging. An example follows:
libname domain "."; proc domain collection id=/shr9; run;
After it is started, the collection manager continues to run until the PROC ADMIN statement is used to terminate it.
Administrator capabilities are an important part of message queueing functionality. Allowing an administrator to register queues provides centralized control of queue definition (how the queue functions as well as who can access it).
All queues are registered or defined, either dynamically or explicitly, through a registration process. A queue that is explicitly registered is known as an administrator pre-defined queue. This type of queue is a permanent queue. It can only be deleted by an administrator who uses the Administrator Procedure Interface. This section discusses how to define such a queue. Refer to either SAS Component Language (SCL) Interface to Indirect Messaging or CALL Routine Interface to Indirect Messaging for information about how to dynamically create a queue.
An administrator pre-defined queue can be registered
during the PROC DOMAIN collection initialization if proper steps are taken.
If a registration file has been created and a fileref of REGISTRY exists that
references this file, the DOMAIN server will parse, interpret, and process
this registry information.
Comments (/* ... */) can be included anywhere within
the file. Queue definition as well as administrator privilege registration
can be accomplished from four types of directives: USER, GROUP, QUEUE, and
USER username userid; USER username userid; USER username userid;
GROUP groupname username username username;
no. The default is
no, which means that messages do not persist.
default(fetch-mode operation) or
notice(notice-mode operation). The default is
default, which specifies the fetch-mode operation.
-1<=maxdepth<=maxint. The default is
-1, which indicates unlimited depth.
-1, which indicates unlimited message length.
Combinations of the above are also acceptable by separating values with
either a plus sign (
or a comma (
,). For example,
you could give DELIVER and BROWSE privileges to a user by specifying one of
QUEUE queue_name COLLECTION|C(collection_name) MSGPSIST(msgpsist) MSGDLVMODE(msgdlvmode) MAXDEPTH(maxdepth) MAXMSGL(maxmsgl) PRIVILEGES(username_or_groupname=permissions username_or_groupname=permissions username_or_groupname=permissions) REPLACE(replace) ;
ADMIN PRIVILEGES(username_or_groupname=permissions username_or_groupname=permissions username_or_groupname=permissions) REPLACE(replace) ;
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.