Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
G'day, One of our customers has a problem with INDEX's going into a loop. ALL-IN-1 Version 2.4 and VMS Version 5.4. The nature of the problem is as follows :-( 1. From the EM (always EM) a user does an index II,IR or IO 2. In one case II it displays the messages on the index form and nothing else happens. The system manager does a show proc and see that the process is in compute state eating up the cpu. Does a control c and "process activity stopped" is displayed and the user can carry on working. 3. Customer reads a message then wants to answer enters A. When the prompt "Do you wish to send to [S] send etc." comes up they do an exit screen the process goes into compute state. Same as 2. The customer once a week reorganises the SDAF, user filing cabinets, etc. and not errors are ever reported. This occures once a day or more. Any suggestions would be welcomed. Sunil
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
408.1 | Some more information | GIDDAY::SETHI | Man from Downunder | Fri Apr 03 1992 09:13 | 21 |
Hi, The customer has provided me with some more infomation :-) 1. The document that was sent out had a long Distribution List afew 100 users. 2. A person answered the message to all the addresses. 3. When the message in 2. was read and the user went to answer (A) it process when into a loop. 4. If a user does a MCD the user can answer the message with any problems. I have suggested that the customer does an ANALYZE/RMS/CHECK on the SDAF to make sure it is not corrupted. It's 100,000 block. I hope this gives you some more clues. Sunil | |||||
408.2 | Site defined function caused the problem | GIDDAY::SETHI | Man from Downunder | Thu May 07 1992 04:41 | 10 |
G'day, The customer had a site defined function that was causing the problem. As soon as the function was removed no more looping and when it was included the problem came back. I wish customers would let you know what customizations they have carried out. Sunil |