| Title: | POLYCENTER AssetWORKS + Microsoft Systems Management Server |
| Notice: | See note 937.1 for kit access information access |
| Moderator: | RDVAX::LEVY D |
| Created: | Wed Feb 23 1994 |
| Last Modified: | Fri May 30 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 977 |
| Total number of notes: | 3989 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 935.1 | LJSRV2::JC | Where's the snow? | Thu Jan 30 1997 14:01 | 8 | |
Yes, PAWCOMM can manage parallel transmissions. Each SRQ is processed by an individual thread on NT. IT is configurable using paw.ini ... looking in the [comm_service] section, sender_max is the max number of concurrent SRQs, and receiver_max is the max # of receivers. crank these up to 100 and it should handle your 80 node situation. also, to improve turnaround, set send_Scan_freq_secs to 1 second. this will increase the CPU load negligibly, but really speed up pawcomm. | |||||
| 935.2 | LJSRV2::JC | Where's the snow? | Thu Jan 30 1997 14:02 | 2 | |
BTW, when you make changes to paw.ini, you must stop and restart the pawcomm service. | |||||
| 935.3 | Many Thanks | ESSB::RJOYCE | Fri Jan 31 1997 10:29 | 7 | |
JC,
Many thanks for the help,
Have a good weekend,
Richard
| |||||