mq queue depth


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting mq queue depth
# 1  
Old 02-13-2008
mq queue depth

hi
how to find the queue depth of MQ Queue using unix
please its very urgent
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

find -depth ..How to use it ?

I tried to find a file lives within curent directory only, and typed $ find . -depth 1 -ls -name *.ini But it gave me, find: paths must precede expression: 1 Usage: find How'd I do it correctly ? Thanks in advance. (2 Replies)
Discussion started by: abdulbadii
2 Replies

2. Shell Programming and Scripting

MQ Queue depth.

Hi All, We have SuoOs and Linux servers. May i know how do we find the queue depth of IBM MQ from server. (2 Replies)
Discussion started by: Girish19
2 Replies

3. Windows & DOS: Issues & Discussions

Folder Depth in Samba

A few of our users are adept at creating folders like 2015\2015 something\event\2015 event\document\2015 which makes their documents close to impossible to find. Is there any way I can restrict the depth of the folders they are allowed to create? (1 Reply)
Discussion started by: Corona688
1 Replies

4. Shell Programming and Scripting

How to write Perl Script to Get MQ Queue Depth?

Hi , I got the following script from internet to display queue depth using Perl Script. However, when I execute it , im getting following error. Can anyone shed light on what is going wrong? #!/usr/bin/perl ## 07/23/01 ## Depth Inquiry sample program. ## Arguments: ## Connects to... (11 Replies)
Discussion started by: srkmish
11 Replies

5. Shell Programming and Scripting

MQ depth Periodically

Hi I am trying to a write a script which gives message queue depth for every 5 mins in a file. Commands that I use are runmqsc QM_Name display ql(*) curdepth Since I can use only MQSC commands I need help on how to fetch the output on to a file after executing display command. (3 Replies)
Discussion started by: jhilmil
3 Replies

6. Shell Programming and Scripting

Understanding find -depth

I was looking at a code and stumbled over the option -depth of find command After searching what -depth does I found the below: -depth Process each directory's contents before the directory itself. Does it mean the sub directories are processed before the current directory in the search... (1 Reply)
Discussion started by: zulfi123786
1 Replies

7. UNIX for Dummies Questions & Answers

rsync max depth?

Good Morning, I'm trying to write a command which copies the folder tree from a source directory to a target directory. The problem is I only want the first level of folders from the source directory, can I specify a maximum depth with rsync? Heres what I have so far: rsync -av -f"+ */"... (2 Replies)
Discussion started by: hermiker
2 Replies

8. Programming

find depth using ftw

Hello, I am looking for specific files in my tree directory using ftw(3). How do I know how deep I am in the file structure.. in other words, say I am looking for config.txt files, and my structure looks like this.. /some/directory/user1/config.txt /some/directory/user2/config.txt ....... (2 Replies)
Discussion started by: germallon
2 Replies

9. Shell Programming and Scripting

Controlling depth with find

I have the following script: Now they have added on a new requirement, they only want to go to a certain depth in the directories returned. How do I code it to only go say 3 directories deeper than $DIRECTORY? (12 Replies)
Discussion started by: la_womn
12 Replies
Login or Register to Ask a Question
scsi_max_qdepth(5)						File Formats Manual						scsi_max_qdepth(5)

NAME
scsi_max_qdepth - maximum number of I/Os that target will queue up for execution (OBSOLETE) VALUES
Failsafe Default Allowed values Recommended values Most SCSI-2 and above devices accept multiple commands and have enough internal memory to support the default queue depth set by HP. You may change the default value to tune devices for higher throughput or load balancing. DESCRIPTION
Note: This tunable is obsolete and is replaced by the attribute which can be set through the command. See scsimgr(1M). Some SCSI devices support tagged queuing, which means that they can have more than one SCSI command outstanding at any point in time. The number of commands that can be outstanding varies by device, and is not known to HP-UX. To avoid overflowing this queue, HP-UX will not send more than a certain number of outstanding commands to any SCSI device. This tunable sets the default value for that limit. The default value can be overridden for specific devices using Queue depth is synonymous to the tagged queuing. When supported by a target, it allows the target to accept multiple SCSI commands for execution. Some targets can allow up to 256 commands to be stored from different initiators. This mechanism can help optimization for better performance. Once the target command queue is full, the target terminates any additional I/O and returns a status to the initiator. Targets may support less than 256 commands to be queued, hence the factory defaults to If the system has a combination of devices that support small and larger queue depths, then a queue depth can be set to a value which would work for most devices. For specific devices, the system administrator can change the queue depth on a per device basis using See scsictl(1M) for more on how to use The values for both 32-bit and 64-bit kernel are the same. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Value of This Tunable Be Raised? SCSI devices that have enough memory to support higher queue depth than the default set by HP. Such devices may offer better performance if the queue depth is set to a higher value. What Are the Side Effects of Raising the Value of This Tunable? The queue depth applies to all the SCSI devices that support tag queuing. Setting the queue depth to a value larger than the disk can han- dle will result in I/Os being held off once a condition exists on the disk. A mechanism exists that will lower the queue depth of the device in case of condition avoiding infinite conditions on that device. Nevertheless, this mechanism will periodically try higher queue depths and conditions will arise. When Should the Value of This Tunable Be Lowered? When the connected SCSI devices support smaller queue depth or for load balancing. What Are the Side Effects of Lowering the Value of This Tunable? Devices that support higher queue depth may not deliver optimal performance when a lower queue depth value is set. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter has been obsoleted for HP-UX 11i Version 3. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
scsictl(1M), ioctl(2), scsi(7). OBSOLETE
Tunable Kernel Parameters scsi_max_qdepth(5)