1. |
SOSMONJ isn't working correctly. We do
backups on our systems at 2 am which close all the jobs. |
2. |
message that says "Too many parameters
were given for this command. (CIERR 10002)". |
3. |
I would like to see a process list in
SOSLOGX. How do I go about doing this? |
4. |
What are SL and PR files? How much data
is contained per file? |
5. |
Is there a way to view the pr#####
logfiles? |
6. |
When extracting data for PG Gold, I get
this error: ***Range includes data from unlicensed susan ######
***Cannot proceed with extract.
|
7. |
I get an error "program failure
(SOSOPT.C.SOSFO4A, 480)" just after the "Display Key Indicators of
Performance (300)" line. How do I resolve this? |
8. |
Do I need to run both the INSTALL job and
the LPSINST job if I am just updating the products? |
9. |
What command do I need to use to see how
much virtual memory is configured on my system? |
10. |
"Log catalog could not be
saved" |
11. |
I am logging data, but I can't find my
log files! |
|
|
SOSMONJ isn't working correctly. We do backups on our systems at 2 am
which close all the jobs. |
|
Answer: |
Have your backup job restream SOSMONJ when the backup
is completed. |
|
|
I am having a minor problem with SOS/3000 version F.03d. What happens
is, occasionally at the bottom portion of the graphical display screen
where the recommendations are listed, it will display an message that
says "Too many parameters were given for this command. (CIERR 10002)".
I am not sure what command is being attempted, but it doesn't appear
to cause any adverse problems. |
|
Answer: |
Versions F.04a and later fix this problem. It can be safely ignored,
also. If you'd like to request an updated version of SOS/3000, contact
your account manager, call (541) 812-7600, or
write us. |
|
|
I would like to see a process list in SOSLOGX. How do I go about doing
this? |
|
Answer: |
Select Options (F1), then select #2, Display Process Information.
Type 'Y.' To exit this menu, select Exit Options (F8). You will be
asked if you want to save these settings permanently. |
|
|
What are SL and PR files? How much data is contained per file? |
|
Answer: |
SL files are the regular SOS log files containing information on
your hardware; CPU usage, Disk I/O per second, etc.
PR files are log files containing information on the processes.
There is one day's worth of data per file. If SOSMONJ goes down
during the day, there will be more than one file with the same Julian
date with a, b, c, after it. |
|
|
Is there a way to view the pr##### logfiles? |
|
Answer: |
You can run an SOSPRANL report from these files. Just log into the
LOGFILES group of LPS where the files are stored, then run the
SOSPRANL program and fill in the menu item (I suggest requesting a
FULL report at the first parameter). This report goes directly to a
spool file, so if you want to just read it, either redirect it to an
ASCII file or suppress your printing feature until you can read it on
the screen.
The PranL feature is documented in SOS/3000 Performance Advisor
User's Guide on or near page 168 (depending on which version manual
you have), under "Cumulative Process Tracking".
|
|
|
When extracting data for PG Gold, I get this error:
***Range includes data from unlicensed susan ######
***Cannot proceed with extract. |
|
Answer: |
This error is probably due to the fact that SOSLOGX is looking for
an earlier version of Performance Gallery. To fix this:
- In SOSLOGX, press F1 for the Options menu.
- Type 11 for the Performance Gallery Configuration submenu.
Press ENTER.
- Type 1 for Performance Gallery Version. Press ENTER.
- Type 2 for Performance Gallery Gold (as opposed to Parformance
Gallery "Original"). Press ENTER.
- Press F8 to exit the Options menu.
|
|
|
I installed the new version of SOS (F.04a) and when I execute SOS it
works , but when I execute the new version of SOSMONJ I get an error
"program failure (SOSOPT.C.SOSFO4A, 480)" just after the "Display Key
Indicators of Performance (300)" line. How do I resolve this? |
|
Answer: |
If you updated the SOS product while SOSMONJ was running, that
background job would not update. Therefore, the current program would
be asking questions in a different order than the older batch job you
are using, is answering them. In other words, these versions are not
compatible. Please re-install the SOSMONJ job from the tape and try
running it again. |
|
|
Do I need to run both the INSTALL job and the LPSINST job if I am just
updating the products? |
|
Answer: |
To be safe, yes, since the INSTALL job allows the user to pick and
choose which products he/she wishes to install.
INSTALL:
- Sets variables
- Sets file equations
- Restore files from tape to LPS account if necessary
- Shows installation interface to choose products to install
- Writes each step to "History" file (this even records what
product choices they made)
- Allows choice of volume set for installation
- Sets the products to be installed
LPSINST:
- Sets up accounts/groups, and users
- Deletes some files in favor of new ones
- Saves some config files
- Runs INSTOS and INSTMI
- Cleans up after itself
|
|
|
What command do I need to use to see how much virtual memory is
configured on my system? |
|
Answer: |
discfree e |
|
|
SOSLOGX gave this error message: "Log catalog could not be
saved" |
|
Answer: |
Just purge the SLLOGCAT file and allow the program to rebuild it on
initialization. |
|
|
I am logging data, but I can't find my log files! |
|
Answer: |
- Allow SOS to initialize and come up with a black screen.
- Go to the Options menu and select the first option.
- Type in "Logfiles.lps" and hit enter to accept the change.
- Press enter again to exit the Options menu. The program will
ask, "Should these changes be saved?" type a "Y" for yes, and the
program should begin to add the logfiles.
You can also log into LPS.PUB and start up LOGX. That would work as
well. |
|