Ok -
we don't generate ipclogs on Windows - just UNIX systems. so...
1) Try running the program from a console session to see if there is a
screen message that doesn't get a chance to display before your telnet
disconnect.
2) Also - you can monitor the program's memory use from another session (or
periodic EXECUTE in your program).
- get the PID from 'listuser' output (USRNBR column)
- from the shell: 'sms -L <pid>'
Watch the entries in the 'Memory Info' table section of that output.
Do you fill the table? (table size is shown in parens in the heading to
that section - reflects udtconfig SHM_LMINENTS setting)
Does one entry continue to grow to some point?
This output is what we would be looking at in an ipclog. You just need to
catch it as close to the abort as possible.
Do you have an open support case on this topic?
Regards,
Wally Terhune
SWG Client Support - Information
Management Software
U2 Support Architect b IBM U2
Client Support Team
4700 S. Syracuse St., Denver, CO
80237
Tel: (303) 773-7969 T/L
656-7969
Mobile: (303) 807-6222
[EMAIL PROTECTED]
Register today for the premier
U2 technical event!
[demime 1.01d removed an attachment of type image/jpeg which had a name of
27364313.jpg]
[demime 1.01d removed an attachment of type image/jpeg which had a name of
27683844.jpg]
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
