Here at PARSEC Group, our Technical Support Teams – OpenVMS, Unix and Linux – receive many new trouble/support calls from customers daily.
We – your Technical Team specialists – want to provide timely and efficient feedback and resolutions for any and all technical issues, but we need your help to do so, as you'll be our “eyes-&-hands” with your computer system.
Here's how you can help us to make each case resolutions effective and efficient…
firstname.lastname@example.org, or inquire at www.parsec.com/about/inquire.php.
For immediate assistance, and especially for urgent issues (system down, performance or operational impact, etc.),
call PARSEC's 24×7 Support Line:
866-372-7732 (or 866-3PA-RSEC)
If you've registered as a PARSEC Member, you can also log a new case at www.parsec.com/members.
This call will be answered quickly by a non-technical support representative; their job is to get basic contact information, a quick problem description, and then get you in contact with the next-available tech-support specialist from the PARSEC Support Team for your operating system.
Have the following contact information at-the-ready:
For less-than-urgent issues – things that you want to check out or ask a question about – send an email message to one of these:
Include the same contact information and brief problem description as above.
A specialist from the Tech Support team for your operating system will get back to you either by email (likely) or telephone.
Be prepared to provide a few basic items of “getting started” information to the PARSEC VMS Tech Support specialist who answers your call – Click on the following link for your operating system for the list of this information:
Your initial communication of the problem, whether by phone-conversation or email message, to the VMS Tech Support specialist who answers your call must include:
1. A simple, concise and focused description of the problem.
Stay objectively focused on what's happening, on symptoms, not on what you want fixed, or on what you “think is wrong.”
a) Good: "When a user attempts a directory command on disk DQA1:, he gets an error message, device not ready." Bad: "We're getting a not-ready message."
b) Good: "Last night's routine BACKUP command file failed, and when I investigated this morning, I've found a flashing red-LED light on disk DKA100. I've got the BACKUP command file script for you if needed." Bad: "I guess backups are failing... Can you fix it for me?"
c) Good: "One of my authorized users, JSMITH, cannot login to VMS using SSH from her PC and a PuTTY terminal emulator. She last logged in two days ago using Telnet. Can you help me troubleshoot this?" Bad: "Users can't login, my system's down."
2. Where available (and this is nearly all the time), be ready to provide exact operating system error messages, or error message text from whatever layered software or third-party software is failing.
Also, where possible, provide the exact command (command line text) which is generating the error. Can the problem be reproduced at-will?
a) Good: $ directory /size /date $32$dqa1:[bjones] %DIRECT-E-OPENIN, error opening $32$DQA1:[BJONES]*.*;* as input -RMS-E-DNR, device not ready, not mounted, or unavailable Bad: "We get a bad-directory error."
3. The PARSEC Technical Support specialist will contact you within your support contract's SLA window, either by phone or by email. Your specialist will likely follow your case all the way through to resolution, although s/he will likely consult with the rest of the operating system team as needed, and draw on the team's overall experience and expertise.
Because you've previously provided the basic information specified above, exchanging this additional information will be much more efficient.
During the initial contact, your specialist will likely ask questions to clarify understanding of the problem, and will also ask you to provide and/or generate additional information about the problem, the operational environment, and the system itself.
You may be asked to execute one or several commands at the command-line prompt – it is always best to do these commands from the privileged account (SYSTEM or root), or from another sys-admin account (such as your own) which can activate the necessary privileges.
Your tech specialist will rely on you for “eyes-&-hands” on the system, so be careful to execute the commands/requests s/he makes and to cut-&-paste all relevant output, plus any other information which can help shed light on the problem and its solution/resolution.
Your specialist may send additional email requests for more information as the overall picture of the problem emerges and builds. Be patient, but also be forthcoming with additional information if/as things do occur to you which might help. More information is (usually) better than less…
4. As soon as a clear picture of the problem emerges from this conversation, your specialist – backed by the PARSEC Tech Support team – will usually offer a best-effort diagnosis of what the underlying problem is, what may have caused it, and how to remedy or repair the problem. Proscriptive (preventive) steps may also be offered. It will be up to you to implement whatever steps and/or remedies your specialist will offer.
5. Your Tech Support specialist will likely ask you for permission to close the case when you both agree that a successful resolution has been reached. It's okay to confirm permission to close at this point.
Of course, any previously closed case can be re-opened with a future recurrence of the problem, or to supply more newly-available information if/as needed.