Procomm Plus (or ASPECT) stability ??

[fechen]

I am using Procomm Plus 4.8/4.7 and with Windows NT/2000 doing some Stress testing. We ran a few Procomm plus scripts for at least 20 hr or so. During this period, the script goes out to reset some devices and waits for some strings coming back on the ports.

Procomm Plus sometimes work great, sometimes it just didn't catch the string. The worse thing is the problem happens spontaneously. Everytime, we rerun the scripts with same setting and equipment and try to repeat, just in vain.

In short, the script does:
1. reset device A
2. waitfor "sodMain complete" in 10 minutes (the device will transmit this string after reset finishes)
3. If can't find, stop for debug
4. If found, sleep for 10 minutes, go back to step 1, and repeat

In the most recent occurence, the testing ran good for ~14hrs (reset devices ~40 times). "sodMain complete" are all caught in these 40 time reset. Then at the last time, Procomm plus misses "sodMain complete", and fail out. I rerun the testing within 30 minutes with the same equipment, works fine.
Also, we have other problems that can't be reproduced, but we are seeing it multiple times, such as capture doesn't work, etc.

Anyone in this forum running same kind of stress testing and seeing the same problem? Any thought, any trick, any ASPECT fix, any information?

If your script only runs for a few minutes, probably won't have this problem anyway.

Thanks in advance for any info

 

[knob]

Have you applied any patches to your installs, particularly version 4.7? You can grab the 4.7 patches here:

http://www.symantec.com/techsupp/files/procomm/procomm47-9598nt.html

I would get at least the pwdll.dll and pw4.exe updates, as well as aspfix.exe. Keep in mind that these patches only apply to 4.7.

There is an updated file (fapi32.dll I think) available here:

http://service4.symantec.com/SUPPORT/procomm.nsf/pfdocs/2001051413173326

but I was unable to connect to that site at this time. This file was for version 4.8 only and is the only updated file I am aware of for that version.
aspect@aspectscripting.com

http://www.aspectscripting.com

 

[fechen]

Patches for PWDLL.DLL and PW4.EXE don't seem fitting into my test environment. Neither fapi32.dll for version 4.8
They are all connection related.

My connection looks fine. When the script fail out, it tries to send out commands and put devices into debug mode for debug. This part works fine, didn't see any failure.
Maybe incoming connection is down?

ASPFIX.exe already installed on some of our 4.7 versions.

The embarassing thing is the problem happens on 4.8 version after I promised our test engineers that the problem was fixed. :-(

 

[knob]

I would still recommend updating to those patches to see if that resolves your problem. I'm not certain that Symantec adequately documented what went into those files, and all three files are at the core of Procomm.

Other things I would try to do is remove as many global variables as possible (if you are using any). If the script is relatively simple though, you shouldn't be seeing this problem.
aspect@aspectscripting.com

http://www.aspectscripting.com

 

[hankm3]

Hello,

I don't know if this has any bearing on this; but I have a Script that runs on an OlderCompaq 1750 (366 Mhz) for 24 + Hours. It Opens a Capture File to Collect Data every 30 Minutes.

I have seen Zero Problems.. This Script runs Constantly but sends No Transmits. I'll modify the Code so that it will Login to the System I am Monitoring every 20 Minutes and Have it Transmit some commands and Logout and see if I have any problems. Will Let you Know.

I'm using Procomm Plus 4.8.

Hank

 

[fechen]

Thanks for suggestion. I still have to do some experiment on my own equipment before I distributed it. The script is just a part of a tool that I made. I have to convince myself first and then convince the internal users.

In fact, the scripts are also doing other things. Several scripts work together to reset two devices alternatively, not at the same time. The scripts are also monitoring some exception string sent by the devices if any (a lot of When command). The scripts are ~4k lines in total. We have VBA code (about 12K lines) to provide GUI, coordination between scripts, etc, ... ...

So about Global variables, I have about ten and two global array (size <15) within a script of 700 lines. Will that possibly be any problem?
Also, I have an include file, which defines some constants (using #Define), some public shared function/proc. A lot of parameters are passed into the main script, the num already passed the Procomm command-line limit. So we have to save them into a file, and then the script reads and parses them. Things just getting complicated to explain without a picture.

The global variables reminds me some programming practices may lead problem in ASPECT. I have seen string output such as &quot;complete after (null) seconds&quot; (again not always). (null) should be an integer I provide.

 

[knob]

The amount of global variables you mention shouldn't be a problem. There definitely seems to be something going on though if the variables are not being displayed correctly at times.
aspect@aspectscripting.com

http://www.aspectscripting.com