[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::decmessageq

Title:NAS Message Queuing Bus
Notice:KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10
Moderator:PAMSRC::MARCUSEN
Created:Wed Feb 27 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2898
Total number of notes:12363

2885.0. "PAMS__IDXTBLFULL 'Selective Receive Index Table is full' question" by IRNBRU::MACKENZIE () Thu May 22 1997 06:25

Hi,

My customer is getting an error

PAMS__IDXTBLFULL 'Selective Receive Index Table is full'

from the pams_set_select call. He calls pams_cancel_select straight after the 
following pams_get_msgw. Can someone explain a bit more about this error and
where to look for the problem.

Thanks,
Dave M.
T.RTitleUserPersonal
Name
DateLines
2885.1Need background info...KLOVIA::MICHELSENBEA/DEC MessageQ EngineeringFri May 23 1997 15:075
  As always, you prefix your questions with platform type, MQ version, OS type
and version for all systems involved.


Marty
2885.2IRNBRU::MACKENZIEWed May 28 1997 09:575
Platform: Win16
DMQ : v3.0.006 using TCPIP
OS: Win95

sending to VMS/VAX - not sure of version, at least DMQ v3.2. 
2885.3KLOVIA::MICHELSENBEA/DEC MessageQ EngineeringWed May 28 1997 10:1722
re: .0

>PAMS__IDXTBLFULL 'Selective Receive Index Table is full'

>from the pams_set_select call. He calls pams_cancel_select straight after the 
>following pams_get_msgw. Can someone explain a bit more about this error and
>where to look for the problem.

	As the test implies, MQ has a maximum number of selection filters
	it tracks.  I see this as having one of two possible causes:

		1) pams_cancel_select is being called wrong and is
		   not freeing the selection filter

		2) pams_cancel_select is being called correctly and is
		   failing to free the resources.

	Can you reduce the your code down to a simple case which shows the
	problem?


	Marty
2885.4-184 and PAMS__RESRCFAIL errorsIRNBRU::MACKENZIEWed May 28 1997 12:2922
I'll try to reduce the code but I know it is being called and returns success.

The OS is actually Windows 3.1, not 95 in case that makes a difference. In 
addition they have been using the DECNET link instead of TCP.

I've requested logs and will post a pointer to them when I receive them. Basically
what the CLServer log file shows is a connect, get, and then another get with
psb status = -184. After that, all attempted communication with that CLS causes
a problem and the same error. If they change their dmq.ini to point to another
CLS they the problem disappears. 

Does the DMQCL.DLL stay in memory after an application has exited ? Their
application is written in VB and doesn't explicitly load/unload the DMQCL.DLL.

Also another problem they are seeing is the application getting PAMS__RESRCFAIL
when it attempts to communicate after a long period of inactivity. It stays
attached to the bus during this period. Is there any system settings that can
be used to remove this problem ?

Thanks,
Dave M.