System Administration Guide
- Introduction
- Introduction to WebSphere MQ
- WebSphere MQ and message queuing
- Time-independent applications
- Message-driven processing
- Messages and queues
- What is a message?
- Message lengths
- How do applications send and receive messages?
- What is a queue?
- Predefined queues and dynamic queues
- Retrieving messages from queues
- Objects
- Object names
- Managing objects
- Object attributes
- WebSphere MQ queues
- Define queues
- Queues used by WebSphere MQ
- WebSphere MQ queue managers
- Process definitions
- Clusters
- Namelists
- Authentication information objects
- Channels
- Client connection channels
- Listeners
- Services
- System default objects
- Clients and servers
- WebSphere MQ applications in a client-server environment
- Extending queue manager facilities
- User exits
- API exits
- Installable services
- Security
- Object Authority Manager (OAM) facility
- User-written or third party channel exits
- Channel security using SSL
- Transactional support
- Use WebSphere MQ for Windows
- Use WebSphere MQ for UNIX systems
- The calls MQCONN and MQCONNX
- Summary of changes
- Changes for this edition (plug-in version 6.0.2.12)
- Changes for the previous editions (plug-in version 6.0.2.12) and (SC34.6584.01 and SC34.6584.02)
- An introduction to WebSphere MQ administration
- Local and remote administration
- Performing administration tasks using commands
- Control commands
- WebSphere MQ Script (MQSC) commands
- PCF commands
- Further methods of administration
- WebSphere MQ Explorer
- Windows Default Configuration application
- Microsoft Cluster Service (MSCS)
- WebSphere MQ file names
- Queue manager name transformation
- Object name transformation
- Administration using WebSphere MQ commands
- Managing queue managers
- Use control commands
- Use control commands on Windows systems
- Use control commands on UNIX systems
- Use the WebSphere MQ Explorer
- Creating a queue manager
- Guidelines for creating queue managers
- Creating a default queue manager
- Making an existing queue manager the default
- Windows and WebSphere MQ for Linux (x86 platform) systems
- UNIX systems
- Backing up configuration files after creating a queue manager
- Windows and WebSphere MQ for Linux (x86 platform) systems
- UNIX systems
- Starting a queue manager
- Starting a queue manager automatically
- Stopping a queue manager
- Quiesced shutdown
- Immediate shutdown
- Preemptive shutdown
- If you have problems shutting down a queue manager
- Restarting a queue manager
- Delete a queue manager
- Administering local WebSphere MQ objects
- Supporting application programs that use the MQI
- Performing local administration tasks using MQSC commands
- WebSphere MQ object names
- Case-sensitivity in MQSC commands
- Standard input and output
- Use MQSC commands interactively
- Feedback from MQSC commands
- Ending interactive input of MQSC commands
- Run MQSC commands from text files
- MQSC command files
- MQSC command reports
- Run the supplied MQSC command files
- Use runmqsc to verify commands
- Run MQSC commands from batch files
- Resolving problems with MQSC commands
- Work with queue managers
- Display queue manager attributes
- Altering queue manager attributes
- Work with local queues
- Define a local queue
- Define a dead-letter queue
- Display default object attributes
- Copying a local queue definition
- Changing local queue attributes
- Clear a local queue
- Delete a local queue
- Browsing queues
- Monitoring local queues with the Windows Performance Monitor
- Enabling large queues
- Work with alias queues
- Define an alias queue
- Use other commands with alias queues
- Work with model queues
- Define a model queue
- Use other commands with model queues
- Work with services
- Define a service object
- Managing services
- Additional environment variables
- Replaceable inserts on service definitions
- Common tokens
- Examples on using service objects
- Use a server service object
- Use a command service object
- Use a command service object when a queue manager ends only
- More on passing arguments
- Autostarting a Service
- Managing objects for triggering
- Define an application queue for triggering
- Define an initiation queue
- Define a process
- Display attributes of a process definition
- Automating administration tasks
- PCF commands
- PCF object attributes
- Escape PCFs
- Use the MQAI to simplify the use of PCFs
- Active Directory Services Interfaces
- Client connection channels in the Active Directory
- Administering remote WebSphere MQ objects
- Channels, clusters, and remote queuing
- Remote administration using clusters
- Remote administration from a local queue manager
- Preparing queue managers for remote administration
- Preparing channels and transmission queues for remote administration
- Define channels, listeners, and transmission queues
- Starting the listeners and channels
- Automatic definition of channels
- Managing the command server for remote administration
- Starting the command server
- Display the status of the command server
- Stopping a command server
- Issuing MQSC commands on a remote queue manager
- Work with queue managers on z/OS
- Recommendations for issuing commands remotely
- If you have problems using MQSC commands remotely
- Creating a local definition of a remote queue
- Understanding how local definitions of remote queues work
- Example
- Purpose
- How it works
- An alternative way of putting messages on a remote queue
- Use other commands with remote queues
- Define a transmission queue
- Default transmission queues
- Use remote queue definitions as aliases
- Queue manager aliases
- Reply-to queue aliases
- Data conversion
- When a queue manager cannot convert messages in built-in formats
- File ccsid.tbl
- Default data conversion
- Converting messages in user-defined formats
- Changing the queue manager CCSID
- Administration using the WebSphere MQ Explorer
- Administration using the WebSphere MQ Explorer
- What we can do with the WebSphere MQ Explorer
- Remote queue managers
- Deciding whether to use the WebSphere MQ Explorer
- Set up the WebSphere MQ Explorer
- Prerequisite software
- Required definitions for administration
- Cluster membership
- Security
- Authorization to use the WebSphere MQ Explorer
- Security for connecting to remote queue managers
- Use a security exit
- Use SSL security
- Use the WebSphere MQ Explorer to connect to a remote queue manager using SSL enabled MQI channels
- Connecting through another queue manager
- Data conversion
- Use the WebSphere MQ Explorer
- Showing and hiding queue managers and clusters
- Use the WebSphere MQ Taskbar application (Windows only)
- Use the WebSphere MQ alert monitor application (Windows only)
- Starting the WebSphere MQ Explorer in Rich Client Platform (RCP) mode
- Security on Windows
- Use Active directory (Windows only)
- User rights required for AMQMSRVN
- Changing the user name associated with WebSphere MQ Services
- Controlling access (Windows only)
- Use DCOMCNFG.EXE to change access permissions
- Changing the password of the AMQMSRVN user account
- Extending the WebSphere MQ Explorer
- Who this chapter is for
- What we need to know to understand this chapter
- Introduction
- Importing the simple Eclipse plug-in
- Writing an Eclipse plug-in for the WebSphere MQ Explorer
- Accessing Javadoc
- Utilizing extension points
- Register
- Enabling and disabling a plug-in
- Notify events
- Add tree node
- Add content page
- Add context menu item
- Applying plug-ins to the WebSphere MQ Explorer
- Configuring WebSphere MQ
- Configuring WebSphere MQ
- Changing configuration information on Windows systems
- Viewing configuration information
- Changing configuration information on UNIX systems
- Editing configuration files
- When do we need to edit a configuration file?
- Configuration file priorities
- The WebSphere MQ configuration file, mqs.ini
- Queue manager configuration files, qm.ini
- Attributes for changing WebSphere MQ configuration information
- All queue managers
- Client exit path
- Default queue manager
- Exit properties
- Log defaults for WebSphere MQ
- Advanced Configuration and Power Interface (ACPI)
- API exits
- Queue managers
- Changing queue manager configuration information
- Installable services
- Service components
- Queue manager logs
- Restricted mode
- XA resource managers
- Channels
- LU62, NETBIOS, TCP, and SPX
- Exit path
- API exits
- Queue manager error logs
- Queue manager default bind type
- WebSphere MQ security
- Authority to administer WebSphere MQ
- Managing the mqm group
- Authority to work with WebSphere MQ objects
- When security checks are made
- How access control is implemented by WebSphere MQ
- Identifying the user ID
- Principals and groups
- Windows security identifiers (SIDs)
- Alternate-user authority
- Context authority
- Connecting to WebSphere MQ using Terminal Services
- Configuring additional authority for Windows applications connecting to WebSphere MQ
- Creating and managing groups
- Windows 2000
- Creating a group and adding users
- Display who is in a group
- Removing a user from a group
- Windows XP and Windows 2003
- Creating a group
- Adding a user to a group
- Display who is in a group
- Removing a user from a group
- HP-UX
- Creating a group
- Adding a user to a group
- Display who is in a group
- Removing a user from a group
- AIX
- Creating a group
- Adding a user to a group
- Display who is in a group
- Removing a user from a group
- Solaris
- Creating a group
- Adding a user to a group
- Display who is in a group
- Removing a user from a group
- Linux
- Creating a group
- Adding a user to a group
- Display who is in a group
- Removing a user from a group
- Use the OAM to control access to objects
- Giving access to a WebSphere MQ object
- Examples of using the command
- Use the command with a different authorization service
- Use OAM generic profiles
- Use wildcard characters
- Profile priorities
- Dumping profile settings
- Display access settings
- Changing and revoking access to a WebSphere MQ object
- Preventing security access checks
- Channel security
- Protecting channel initiator definitions
- Transmission queues
- Channel exits
- Protecting channels with SSL
- How authorizations work
- Authorizations for MQI calls
- Authorizations for MQSC commands in escape PCFs
- Authorizations for PCF commands
- Guidelines for Windows 2000 and Windows 2003
- When you get a 'group not found' error
- When you have problems with WebSphere MQ and domain controllers
- Windows 2000 domain with non-default, or Windows 2003 domain with default, security permissions
- Configuring WebSphere MQ Services to run under a domain user
- Applying security template files
- Nested groups
- Transactional support
- Introducing units of work
- Scenario 1: Queue manager performs the coordination
- Database coordination
- Restrictions
- Switch load files
- Configuring your system for database coordination
- Installing and configuring the database product
- Database connections
- Client/server configuration
- Creating switch load files
- Adding configuration information to the queue manager
- Writing and modifying your applications
- Testing the system
- DB2 configuration
- Checking the DB2 environment variable settings
- Creating the DB2 switch load file
- Adding resource manager configuration information for DB2
- Changing DB2 configuration parameters
- Oracle configuration
- Checking the Oracle environment variable settings
- Creating the Oracle switch load file
- Adding resource manager configuration information for Oracle
- Changing Oracle configuration parameters
- Informix configuration
- Ensuring Informix databases are created correctly
- Checking the Informix environment variable settings
- Creating the Informix switch load file
- Adding resource manager configuration information for Informix
- Sybase configuration
- Checking the Sybase environment variable settings
- Enabling Sybase XA support
- Creating the Sybase switch load file
- Adding resource manager configuration information for Sybase
- Use multi-threaded programs with Sybase
- Multiple database configurations
- Security considerations
- Administration tasks
- In-doubt units of work
- Display outstanding units of work with the dspmqtrn command
- Resolving outstanding units of work with the rsvmqtrn command
- Mixed outcomes and errors
- Changing configuration information
- Removing database manager instances
- XA dynamic registration
- Error conditions
- Summarizing XA calls
- Scenario 2: Other software provides the coordination
- External syncpoint coordination
- The WebSphere MQ XA switch structure
- Use CICS
- The CICS two-phase commit process
- Requirements of the two-phase commit process
- Switch load files
- Building libraries for use with CICS
- WebSphere MQ XA support and Tuxedo
- Enabling the CICS two-phase commit process
- Enabling CICS user exits
- Sample task termination exit
- Use the Microsoft Transaction Server (COM+)
- The WebSphere MQ dead-letter queue handler
- Invoking the DLQ handler
- The sample DLQ handler, amqsdlq
- The DLQ handler rules table
- Control data
- Rules (patterns and actions)
- The pattern-matching keywords
- The action keywords
- Rules table conventions
- How the rules table is processed
- Ensuring that all DLQ messages are processed
- An example DLQ handler rules table
- Supporting the Microsoft Cluster Service (MSCS)
- Introducing MSCS clusters
- Set up WebSphere MQ for MSCS clustering
- Setup symmetry
- MSCS security
- Use multiple queue managers with MSCS
- Cluster modes
- Active/Passive mode
- Active/Active mode
- Creating a queue manager for use with MSCS
- Creating a queue manager from a command prompt
- Creating a queue manager using the WebSphere MQ Explorer
- Moving a queue manager to MSCS storage
- Putting a queue manager under MSCS control
- Removing a queue manager from MSCS control
- Taking a queue manager offline from MSCS
- Returning a queue manager from MSCS storage
- Hints and tips on using MSCS
- Verifying that MSCS is working
- Use the IBM MQSeries Service
- Manual startup
- MSCS and queue managers
- Creating a matching queue manager on the other node
- Default queue managers
- Delete a queue manager
- Support for existing queue managers
- Telling MSCS which queue managers to manage
- Queue manager log files
- Multiple queue managers
- Always use MSCS to manage clusters
- Work in Active/Active mode
- PostOnlineCommand and PreOfflineCommand
- Use preferred nodes
- Performance benchmarking
- WebSphere MQ MSCS support utility programs
- Recovery and problem determination
- Recovery and restart
- Making sure that messages are not lost (logging)
- What logs look like
- The log control file
- Types of logging
- Circular logging
- Linear logging
- Use checkpointing to ensure complete recovery
- Checkpointing with long-running transactions
- Calculating the size of the log
- Managing logs
- What happens when a disk gets full
- Managing log files
- Log file location
- Use the log for recovery
- Recovering from power loss or communications failures
- Recovering damaged objects
- Media recovery
- Recovering from media images
- Recovering damaged objects during start up
- Recovering damaged objects at other times
- Protecting WebSphere MQ log files
- Backing up and restoring WebSphere MQ
- Backing up queue manager data
- Restoring queue manager data
- Use a backup queue manager
- Creating a backup queue manager
- Updating a backup queue manager
- Starting a backup queue manager
- Recovery scenarios
- Disk drive failures
- Damaged queue manager object
- Damaged single object
- Automatic media recovery failure
- Dumping the contents of the log using the dmpmqlog command
- Problem determination
- Preliminary checks
- Has WebSphere MQ run successfully before?
- Are there any error messages?
- Does the Windows Application Event Log show any WebSphere MQ errors? (Windows only)
- Are there any return codes explaining the problem?
- Can you reproduce the problem?
- Have any changes been made since the last successful run?
- Has the application run successfully before?
- If the application has not run successfully before
- Common programming errors
- Problems with commands
- Does the problem affect specific parts of the network?
- Does the problem occur at specific times of the day?
- Is the problem intermittent?
- Have you applied any service updates?
- Looking at problems in more detail
- Have you obtained incorrect output?
- Messages that do not appear on the queue
- Messages that contain unexpected or corrupted information
- Problems with incorrect output when using distributed queues
- Have you failed to receive a response from a PCF command?
- Are some of your queues failing?
- Are you receiving an error code when creating or starting a queue manager? (Windows only)
- Does the problem affect only remote queues?
- Is your application or system running slowly?
- Tuning performance for nonpersistent messages on AIX
- Application design considerations
- Effect of message length
- Effect of message persistence
- Searching for a particular message
- Queues that contain messages of different lengths
- Frequency of syncpoints
- Use of the MQPUT1 call
- Number of threads in use
- Error logs
- Error log files
- Early errors
- An example of an error log
- Error log access restrictions under UNIX systems
- Ignoring error codes under UNIX systems
- Ignoring error codes under Windows systems
- Operator messages
- Dead-letter queues
- Configuration files and problem determination
- Tracing
- Tracing WebSphere MQ for Windows
- Selective component tracing on WebSphere MQ for Windows
- Trace files
- An example of WebSphere MQ for Windows trace data
- Tracing WebSphere MQ for UNIX systems
- Selective component tracing on WebSphere MQ for UNIX systems
- Example trace data for WebSphere MQ for UNIX systems
- Trace files
- Tracing Secure Sockets Layer (SSL) iKeyman and iKeycmd functions
- Tracing with the AIX system trace
- Selective component tracing on WebSphere MQ for AIX
- SSL trace
- An example of WebSphere MQ for AIX trace data
- First-failure support technology (FFST)
- FFST: WebSphere MQ for Windows
- FFST: WebSphere MQ for UNIX systems
- Problem determination with WebSphere MQ clients
- Terminating clients
- Java diagnostics
- Use com.ibm.mq.commonservices
- Java trace and FFDC files
- WebSphere MQ control commands
- How to use WebSphere MQ control commands
- Names of WebSphere MQ objects
- Example syntax diagram
- Syntax help
- Examples
- The control commands
- amqccert (check certificate chains)
- amqmdain (WebSphere MQ services control)
- amqtcert (transfer certificates)
- List the contents of certificate stores
- Manually migrating certificate stores
- Automatically migrating certificate stores
- List the contents of registry entries
- Removing state information
- crtmqcvx (data conversion)
- crtmqm (create queue manager)
- dltmqm (delete queue manager)
- dmpmqaut (dump authority)
- dmpmqlog (dump log)
- dspmq (display queue managers)
- dspmqaut (display authority)
- dspmqcsv (display command server)
- dspmqfls (display files)
- dspmqrte (WebSphere MQ display route application)
- dspmqtrc (display formatted trace output)
- dspmqtrn (display transactions)
- dspmqver (display version information)
- endmqcsv (end command server)
- endmqlsr (end listener)
- endmqdnm (stop .NET monitor)
- endmqm (end queue manager)
- endmqtrc (end trace)
- mqftapp (run File Transfer Application GUI)
- mqftrcv (receive file on server)
- mqftrcvc (receive file on client)
- mqftsnd (send file from server)
- mqftsndc (send file from client)
- rcdmqimg (record media image)
- rcrmqobj (recreate object)
- rsvmqtrn (resolve transactions)
- runmqchi (run channel initiator)
- runmqchl (run channel)
- runmqdlq (run dead-letter queue handler)
- runmqdnm (run .NET monitor)
- runmqlsr (run listener)
- runmqsc (run MQSC commands)
- runmqtmc (start client trigger monitor)
- runmqtrm (start trigger monitor)
- setmqaut (grant or revoke authority)
- Authorizations for MQI calls
- Authorizations for context
- Authorizations for commands
- Authorizations for generic operations
- setmqcrl (set certificate revocation list (CRL) LDAP server definitions)
- setmqprd (enroll production license)
- setmqscp (set service connection points)
- strmqcfg (start WebSphere MQ Explorer)
- strmqcsv (start command server)
- strmqm (start queue manager)
- strmqtrc (Start trace)
- Managing keys and certificates
- Preparing to use the gsk7cmd and gsk7capicmd commands
- gsk7cmd, runmqckm, and gsk7capicmd commands
- Commands for a CMS key database only
- Commands for CMS or PKCS #12 key databases
- Commands for cryptographic device operations
- gsk7cmd, runmqckm, and gsk7capicmd options
- WebSphere MQ installable services and the API exit
- Installable services and components
- Why installable services?
- Functions and components
- Entry-points
- Return codes
- Component data
- Initialization
- Primary initialization
- Secondary initialization
- Primary termination
- Secondary termination
- Configuring services and components
- Service stanza format
- Service stanza format for Windows systems
- Service component stanza format
- Creating your own service component
- Use multiple service components
- Example of using multiple components
- What the components do
- How the component is used
- Omitting entry points when using multiple components
- Example of entry points used with multiple components
- Authorization service
- Object authority manager (OAM)
- Define the service to the operating system
- Refreshing the OAM after changing a user's authorization
- Migrating from MQSeries V5.1
- Authorization service on UNIX systems
- Configuring authorization service stanzas: UNIX systems
- Authorization service on Windows systems
- Configuring authorization service stanzas: Windows systems
- Authorization service interface
- Name service
- How the name service works
- Name service interface
- Installable services interface reference information
- How the functions are shown
- Parameters and data types
- MQZEP . Add component entry point
- Syntax
- Parameters
- Hconfig (MQHCONFIG) . input
- Function (MQLONG) . input
- EntryPoint (PMQFUNC) . input
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQHCONFIG . Configuration handle
- C declaration
- PMQFUNC . Pointer to function
- C declaration
- MQZ_AUTHENTICATE_USER . Authenticate user
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- SecurityParms (MQCSP) . input
- ApplicationContext (MQZAC) . input
- IdentityContext (MQZIC) . input/output
- CorrelationPtr (MQPTR) . output
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_CHECK_AUTHORITY . Check authority
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- EntityName (MQCHAR12) . input
- EntityType (MQLONG) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- Authority (MQLONG) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_CHECK_AUTHORITY_2 . Check authority (extended)
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- EntityData (MQZED) . input
- EntityType (MQLONG) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- Authority (MQLONG) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_COPY_ALL_AUTHORITY . Copy all authority
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- RefObjectName (MQCHAR48) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_DELETE_AUTHORITY . Delete authority
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_ENUMERATE_AUTHORITY_DATA . Enumerate authority data
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- StartEnumeration (MQLONG) . input
- Filter (MQZAD) . input
- AuthorityBufferLength (MQLONG) . input
- AuthorityBuffer (MQZAD) . output
- AuthorityDataLength (MQLONG) . output
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_FREE_USER . Free user
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- FreeParms (MQZFP) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_GET_AUTHORITY . Get authority
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- EntityName (MQCHAR12) . input
- EntityType (MQLONG) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- Authority (MQLONG) . output
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_GET_AUTHORITY_2 . Get authority (extended)
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- EntityData (MQZED) . input
- EntityType (MQLONG) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- Authority (MQLONG) . output
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_GET_EXPLICIT_AUTHORITY . Get explicit authority
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- EntityName (MQCHAR12) . input
- EntityType (MQLONG) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- Authority (MQLONG) . output
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_GET_EXPLICIT_AUTHORITY_2 . Get explicit authority (extended)
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- EntityData (MQZED) . input
- EntityType (MQLONG) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- Authority (MQLONG) . output
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_INIT_AUTHORITY . Initialize authorization service
- Syntax
- Parameters
- Hconfig (MQHCONFIG) . input
- Options (MQLONG) . input
- QMgrName (MQCHAR48) . input
- ComponentDataLength (MQLONG) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- V(MQLONG) . input/output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_INQUIRE . Inquire authorization service
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- SelectorCount (MQLONG) . input
- Selectors (MQLONG×electorCount) . input
- IntAttrCount (MQLONG) . input
- IntAttrs (MQLONG×ntAttrCount) . output
- CharAttrCount (MQLONG) . input
- CharAttrs (MQLONG×harAttrCount) . output
- SelectorReturned (MQLONG×electorCount) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_REFRESH_CACHE . Refresh all authorizations
- Syntax
- Parameters
- C invocation
- MQZ_SET_AUTHORITY . Set authority
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- EntityName (MQCHAR12) . input
- EntityType (MQLONG) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- Authority (MQLONG) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_SET_AUTHORITY_2 . Set authority (extended)
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- EntityData (MQZED) . input
- EntityType (MQLONG) . input
- ObjectName (MQCHAR48) . input
- ObjectType (MQLONG) . input
- Authority (MQLONG) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_TERM_AUTHORITY . Terminate authorization service
- Syntax
- Parameters
- Hconfig (MQHCONFIG) . input
- Options (MQLONG) . input
- QMgrName (MQCHAR48) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZAC . Application context
- Fields
- StrucId (MQCHAR4)
- V(MQLONG)
- ProcessId (MQPID)
- ThreadId (MQTID)
- ApplName (MQCHAR28)
- UserID (MQCHAR12)
- EffectiveUserID (MQCHAR12)
- Environment (MQLONG)
- CallerType (MQLONG)
- AuthenticationType (MQLONG)
- BindType (MQLONG)
- C declaration
- MQZAD . Authority data
- Fields
- StrucId (MQCHAR4)
- V(MQLONG)
- ProfileName (MQCHAR48)
- ObjectType (MQLONG)
- Authority (MQLONG)
- EntityDataPtr (PMQZED)
- EntityType (MQLONG)
- Options (MQAUTHOPT)
- C declaration
- MQZED . Entity descriptor
- Fields
- StrucId (MQCHAR4)
- V(MQLONG)
- EntityNamePtr (PMQCHAR)
- EntityDomainPtr (PMQCHAR)
- SecurityId (MQBYTE40)
- CorrelationPtr (MQPTR)
- C declaration
- MQZIC . Identity context
- Fields
- StrucId (MQCHAR4)
- V(MQLONG)
- UserIdentifier (MQCHAR12)
- AccountingToken (MQBYTE32)
- ApplIdentityData (MQCHAR32)
- C declaration
- MQZFP . Free parameters
- Fields
- StrucId (MQCHAR4)
- V(MQLONG)
- Reserved (MQBYTE8)
- CorrelationPtr (MQPTR)
- C declaration
- MQZ_DELETE_NAME . Delete name
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- QName (MQCHAR48) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_INIT_NAME . Initialize name service
- Syntax
- Parameters
- Hconfig (MQHCONFIG) . input
- Options (MQLONG) . input
- QMgrName (MQCHAR48) . input
- ComponentDataLength (MQLONG) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- V(MQLONG) . input/output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_INSERT_NAME . Insert name
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- QName (MQCHAR48) . input
- ResolvedQMgrName (MQCHAR48) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_LOOKUP_NAME . Lookup name
- Syntax
- Parameters
- QMgrName (MQCHAR48) . input
- QName (MQCHAR48) . input
- ResolvedQMgrName (MQCHAR48) . output
- ComponentData (MQBYTE×omponentDataLength) . input/output
- Continuation (MQLONG) . output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- MQZ_TERM_NAME . Terminate name service
- Syntax
- Parameters
- Hconfig (MQHCONFIG) . input
- Options (MQLONG) . input
- QMgrName (MQCHAR48) . input
- ComponentData (MQBYTE×omponentDataLength) . input/output
- CompCode (MQLONG) . output
- Reason (MQLONG) . output
- C invocation
- API exits
- Why use API exits
- How you use API exits
- How to configure WebSphere MQ for API exits
- How to write an API exit
- What happens when an API exit runs?
- Configuring API exits
- Configuring API exits on UNIX systems
- Attributes for all stanzas
- Sample stanzas
- Changing the configuration information
- Configuring API exits on Windows systems
- API exit reference information
- General usage notes
- MQACH . API exit chain header
- Fields
- StrucId (MQCHAR4)
- V(MQLONG)
- StrucLength (MQLONG)
- ChainAreaLength (MQLONG)
- ExitInfoName (MQCHAR48)
- NextChainAreaPtr (PMQACH)
- C declaration
- MQAXC . API exit context
- Fields
- StrucId (MQCHAR4)
- V(MQLONG)
- Environment (MQLONG)
- UserId (MQCHAR12)
- SecurityId (MQBYTE40)
- ConnectionName (MQCHAR264)
- LongMCAUserIdLength (MQLONG)
- LongRemoteUserIdLength (MQLONG)
- LongMCAUserIdPtr (MQPTR)
- LongRemoteUserIdPtr (MQPTR)
- ApplName (MQCHAR28)
- ApplType (MQLONG)
- ProcessId (MQPID)
- ThreadId (MQTID)
- C declaration
- MQAXP . API exit parameter
- Fields
- StrucId (MQCHAR4)
- V(MQLONG)
- ExitId (MQLONG)
- ExitReason (MQLONG)
- ExitResponse (MQLONG)
- ExitResponse2 (MQLONG)
- Feedback (MQLONG)
- APICallerType (MQLONG)
- ExitUserArea (MQBYTE16)
- ExitData (MQCHAR32)
- ExitInfoName (MQCHAR48)
- ExitPDArea (MQBYTE48)
- QMgrName (MQCHAR48)
- ExitChainAreaPtr (PMQACH)
- Hconfig (MQHCONFIG)
- Function (MQLONG)
- C declaration
- MQXEP . Register entry point
- Syntax
- Parameters
- Hconfig (MQHCONFIG) . input
- ExitReason (MQLONG) . input
- Function (MQLONG) . input
- EntryPoint (PMQFUNC) . input
- Reserved (MQPTR) . input
- pCompCode (PMQLONG) . output
- pReason (PMQLONG) . output
- C invocation
- MQ_BACK_EXIT . Back out changes
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- C invocation
- MQ_BEGIN_EXIT . Begin unit of work
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- ppBeginOptions (PPMQBO) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- C invocation
- MQ_CLOSE_EXIT . Close object
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- ppHobj (PPMQHOBJ) . input/output
- pOptions (PMQLONG) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- C invocation
- MQ_CMIT_EXIT . Commit changes
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- C invocation
- MQ_CONNX_EXIT . Connect queue manager (extended)
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pQMgrName (PMQCHAR48) . input/output
- ppConnectOpts (PPMQCNO) . input/output
- ppHconn (PPMQHCONN) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- Usage notes
- C invocation
- MQ_DISC_EXIT . Disconnect queue manager
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- ppHconn (PPMQHCONN) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- C invocation
- MQ_GET_EXIT . Get message
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- pHobj (PMQHOBJ) . input/output
- ppMsgDesc (PPMQMD) . input/output
- ppGetMsgOpts (PPMQGMO) . input/output
- pBufferLength (PMQLONG) . input/output
- ppBuffer (PPMQVOID) . input/output
- ppDataLength (PPMQLONG) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- Usage notes
- C invocation
- MQ_INIT_EXIT . Initialize exit environment
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- Usage notes
- C invocation
- MQ_INQ_EXIT . Inquire object attributes
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- pHobj (PMQHOBJ) . input/output
- pSelectorCount (PMQLONG) . input/output
- ppSelectors (PPMQLONG) . input/output
- pIntAttrCount (PMQLONG) . input/output
- ppIntAttrs (PPMQLONG) . input/output
- pCharAttrLength (PMQLONG) . input/output
- ppCharAttrs (PPMQCHAR) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- C invocation
- MQ_OPEN_EXIT . Open object
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- ppObjDesc (PPMQOD) . input/output
- pOptions (PMQLONG) . input/output
- ppHobj (PPMQHOBJ) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- C invocation
- MQ_PUT_EXIT . Put message
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- pHobj (PMQHOBJ) . input/output
- ppMsgDesc (PPMQMD) . input/output
- ppPutMsgOpts (PPMQPMO) . input/output
- pBufferLength (PMQLONG) . input/output
- ppBuffer (PPMQVOID) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- Usage notes
- C invocation
- MQ_PUT1_EXIT . Put one message
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- ppObjDesc (PPMQOD) . input/output
- ppMsgDesc (PPMQMD) . input/output
- ppPutMsgOpts (PPMQPMO) . input/output
- pBufferLength (PMQLONG) . input/output
- ppBuffer (PPMQVOID) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- C invocation
- MQ_SET_EXIT . Set object attributes
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pHconn (PMQHCONN) . input/output
- pHobj (PMQHOBJ) . input/output
- pSelectorCount (PMQLONG) . input/output
- ppSelectors (PPMQLONG) . input/output
- pIntAttrCount (PMQLONG) . input/output
- ppIntAttrs (PPMQLONG) . input/output
- pCharAttrLength (PMQLONG) . input/output
- ppCharAttrs (PPMQCHAR) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- C invocation
- MQ_TERM_EXIT . Terminate exit environment
- Syntax
- Parameters
- pExitParms (PMQAXP) . input/output
- pExitContext (PMQAXC) . input/output
- pCompCode (PMQLONG) . input/output
- pReason (PMQLONG) . input/output
- Usage notes
- C invocation
- System and default objects
- Windows default configuration objects
- Directory structure (Windows systems)
- Directory structure (UNIX systems)
- Stopping and removing queue managers manually
- Stopping a queue manager manually
- Stopping queue managers in WebSphere MQ for Windows
- Stopping queue managers in WebSphere MQ for UNIX systems
- Removing queue managers manually
- Removing queue managers in WebSphere MQ for Windows
- Removing queue managers from the automatic startup list
- Removing queue managers in WebSphere MQ for UNIX systems
- File Transfer Application
- Introduction
- Advantages
- Components
- Installing and configuring
- Installing the File Transfer Application on a WebSphere MQ server
- During the initial installation
- Modifying the installation
- Installing the File Transfer Application on a WebSphere MQ client
- During the initial installation
- Modifying the installation
- Setup tasks
- Sending files between remote queue managers
- Sending files between a queue manager and a remote WebSphere MQ client
- Configuring the GUI
- File Transfer Application channel security
- Use the File Transfer Application
- Sending a file
- Receiving a file
- List all sent and received files
- File status
- Use the command line
- Comparing command sets
- Queue manager commands
- Command server commands
- Authority commands
- Cluster commands
- Authentication information commands
- Channel commands
- Listener commands
- Namelist commands
- Process commands
- Queue commands
- Service commands
- Other commands
- WebSphere MQ and UNIX System V IPC resources
- Clear WebSphere MQ shared memory resources
- Shared memory on AIX
- WebSphere MQ and UNIX Process Priority
- Common Criteria
- Trademarks