10 Best Practices for a Successful Customer Solution Engagement


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS 10 Best Practices for a Successful Customer Solution Engagement
# 1  
Old 03-17-2010
10 Best Practices for a Successful Customer Solution Engagement

This paper discusses 10 key areas that frequently are not handled correctly and lead to customer dissatisfaction during customer solution engagements, and it provides recommendations for successfully handling them.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Shell Script to prompt customer for name etc

reposting How do I create a shell script called 'custinfo' to prompt a customer to enter and display back the following: name, age, address, phone number, product, price range. Thanks (1 Reply)
Discussion started by: SQLScript
1 Replies

2. UNIX for Dummies Questions & Answers

identify a customer under a UNIX server

Like many UNIX users, there is a small team that is connected to UNIX (under the same UNIX user) via putty from a Windows PC. Is there a way, once under UNIX, to know the address of the originating computer or anything that can differentiate initial users ? (7 Replies)
Discussion started by: popescu1954
7 Replies

3. HP-UX

Customer support engineer

Hi All, I need the help to deploy or implement HP MC service guard 2 node cluster step by step procedure is any1 who can help me to send me the step by step procedure. Thanks and Regards Jahangir (12 Replies)
Discussion started by: Jahangir
12 Replies
Login or Register to Ask a Question
STRMSGSZ(5)							File Formats Manual						       STRMSGSZ(5)

NAME
STRMSGSZ - maximum size of streams message data (bytes) VALUES
Failsafe Default Allowed values Recommended values DESCRIPTION
This tunable limits the number of bytes of message data that can be inserted by or in the data portion of any streams message on the sys- tem. If the tunable is set to zero, there is no limit on how many bytes can be placed in the data segment of the message. returns if the buffer being sent is larger than the current value of segments the data into multiple messages. Who Is Expected to Change This Tunable? Any customer. Restrictions on Changing Changes to this tunable take effect at next reboot. When Should the Value of This Tunable Be Raised? The tunable should be increased by any customer if the customer's STREAMS module/driver(s) require a longer message size in the data por- tion than the current value. What Are the Side Effects of Raising the Value of This Tunable? The kernel will use more memory. During low memory situations, it may bring down system performance due to frequent swapping. When Should the Value of This Tunable Be Lowered? The tunable could be lowered by any customer if the customer's STREAMS module/driver(s) do not require a longer message size in the data portion than the current value. What Are the Side Effects of Lowering the Value of This Tunable? Possible improper functioning in any of the STREAMS module/driver(s). Possible performance degradation, particularly in networking. What Other Tunable Should Be Changed at the Same Time as This One? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. Tunable Kernel Parameters STRMSGSZ(5)