User Tools

Site Tools


vms_getting_started_info

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
vms_getting_started_info [2018/09/17 16:21]
lricker Initial commit
vms_getting_started_info [2018/09/17 17:03]
lricker tweaks
Line 1: Line 1:
 ===== Basic Operating System Information -- VMS (OpenVMS) ===== ===== Basic Operating System Information -- VMS (OpenVMS) =====
  
-**1.** Is the system with the problem you're reporting actually on a current support contract?+**1.** Is the system with the problem you're reporting actually on a //current support contract//?
  
-  ​* If **yes**, proceed to step 2 below... +  * If **no**, contact your PARSEC Account Representative before contacting the PARSEC Technical Support Team.\\   See [[How To Initiate a PARSEC Tech Support Call]] for full information.\\ 
-  ​* If **no**, contact your PARSEC Account Representative before contacting the PARSEC Technical Support Team.+ 
 +  * If **yes**, proceed to Step 2 below...
  
 **2.** What is the: **2.** What is the:
Line 15: Line 16:
   - How long has the system been up?   - How long has the system been up?
  
-All of the above can be displayed with either of these commands:+All of the above can be displayed with either of these commands ​--
  
-Command symbol (for your LOGIN.COM) and its invocation:​ +Just cut-&​-paste the following long line (all of it) onto your DCL command line, then hit ''​Enter'':​
- +
-  $ sysin*fo ​ == "PIPE show system /noprocess " - +
-               + "; write sys$output "" ​ Architecture ​ = ''​F$GETSYI("​ARCH_NAME"​)'""​ " - +
-               + "; show cpu /full | SEARCH sys$pipe ""​Serial Number""​ " - +
-               + "; show memory /physical | SEARCH sys$pipe ""​Physical Memory""​ /​WINDOW=(0,​1)"​ +
-  $ sysinfo +
- +
-__or__: +
- +
-Just cut-&​-paste the following long line onto your DCL command line (all of it; this command is identical to the one above), then hit ''​Enter'':​+
  
   PIPE show system /noprocess -   PIPE show system /noprocess -
Line 35: Line 26:
  
 //Hint//: Use your mouse to select all four lines above. ​ When the whole command is selected, enter ''​Ctrl/​C''​ to copy it to your paste-buffer. ​ Then go to your terminal window logged into VMS (e.g., your PuTTY session), and enter ''​Shift+Insert''​ to paste this text into the command line... hit ''​Enter''​ to execute the command. //Hint//: Use your mouse to select all four lines above. ​ When the whole command is selected, enter ''​Ctrl/​C''​ to copy it to your paste-buffer. ​ Then go to your terminal window logged into VMS (e.g., your PuTTY session), and enter ''​Shift+Insert''​ to paste this text into the command line... hit ''​Enter''​ to execute the command.
 +
 +__or__:
 +
 +Use this command symbol/​alias (define it in your LOGIN.COM; this command is identical to the one above):
 +
 +  $ sysin*fo ​ == "PIPE show system /noprocess " -
 +               + "; write sys$output "" ​ Architecture ​ = ''​F$GETSYI("​ARCH_NAME"​)'""​ " -
 +               + "; show cpu /full | SEARCH sys$pipe ""​Serial Number""​ " -
 +               + "; show memory /physical | SEARCH sys$pipe ""​Physical Memory""​ /​WINDOW=(0,​1)"​
 +
 +//Hint//: Copy/paste the four lines above into the ''​INTERACTIVE:''​ stanza of your LOGIN.COM file.  Rerun this script with ''​$ @SYS$LOGIN:​LOGIN''​ -- Then you can use the command symbol interactively,​ as follows:
 +
 +  $ sysinfo
  
 In either case, you'll see something like this: In either case, you'll see something like this:
Line 50: Line 54:
      Main Memory (1.99GB) ​           262096 ​      ​46466 ​     211634 ​       3996      Main Memory (1.99GB) ​           262096 ​      ​46466 ​     211634 ​       3996
  
-When you run either of these commands, just cut-&​-paste the resulting output into an email message for us, typically in response to the PARSEC'​s introductory email, ''​Subject:​ Case //XXXX// has been logged for //​YourCompanyName//​ by //VMStechName//''​.+When you run either of these commands, just cut-&​-paste the resulting output into an email message for us, typically in response to the PARSEC'​s introductory email, ''​Subject:​ Case //XXXX// has been logged for //​YourCompanyName//​ by //TechName//''​.
  
 Be sure that all of your email correspondence about this case includes the "Case //​XXXX//"​ (where //XXXX// is your case number) as the first two words of the Subject: line. Be sure that all of your email correspondence about this case includes the "Case //​XXXX//"​ (where //XXXX// is your case number) as the first two words of the Subject: line.
vms_getting_started_info.txt · Last modified: 2018/09/17 17:03 by lricker