| |
ORPG System Administration Information
Last Updated: |
November 29, 2001 |
Applicability: |
ORPG System Administrators |
General Information: The ORPG adaptation data files are arranged significantly different
from the legacy RPG files. On the Legacy RPG, there were 6 files that made up your site
specific adaptation data. They were:
- ADAPT.DAT
- ADAPTONE.DAT
- ADAPTTWO.DAT
- BACKGRND.DAT
- HYOCCULT.DAT
- HYSECTRS.DAT
The BACKGRND.DAT file held your site's background maps. When a PUP dialed into your RPG,
they could request a copy of your maps. This file was used to supply the requested maps.
Note that the background map file is not currently part of the ORPG software.
The HYOCCULT.DAT and HYSECTRS.DAT files are used by the precipitation algorithms to specify
your radar's beam blockage and hybrid scan. These same files exist on your ORPG, but with
a slightly different name.
The other three files stored all the rest of the adaptation data. The ADAPT.DAT stored your
"baseline" adaptation data as delivered by the ROC. Any changes made to this baseline were
written to the ADATPONE.DAT and ADAPTTWO.DAT files (it would alternate between these two files).
On the ORPG, there are many more files that hold portions of the adaptation data. And these
files are stored in different subdirectories. So, to make it easier when backing up these
files, a command called save_adapt_floppy has been created
which will backup all the site specific adaptation data to a single file on a 3 ½" floppy.
There is also a command called restore_adapt_floppy for
restoring the adaptation data stored on a 3 ½" floppy.
Baseline Files: The concept of "baseline" adaptation data has changed. While on the legacy RPG the
baseline adaptation data file (ADAPT.DAT) did not change, on the ORPG you can update the
baseline files.
On screens where adaptation data can be changed, there are two buttons labeled "Restore"
and "Update" [e.g.,  ].
If, after making changes to the adaptation data, you click on the "Update" button and
click "Yes" on the confirmation popup dialog box, then the changes you made will be saved
to the baseline set of adaptation data files. The next time you save the adaptation data
to floppy disk (via the save_adapt_floppy command), these changes will be saved to the floppy too.
However, if you make a change and don't click the "Update" button, then your changes are only
saved temporarily. The next time you save the adaptation data to floppy disk (via the
save_adapt_floppy command), these changes will NOT be saved to the floppy. Also, if you click
the "Restore" button, these temporary changes will be changed back to the values stored in
the baseline files.
Note: After you make a change to an adaptation data parameter, you must save your change
by clicking on the "Save" button before you can "Update" the baseline files.
Last Updated: |
November 29, 2001 |
Applicability: |
ORPG System Administrators |
Background Information: The command save_adapt_floppy is used to save all
site specific adaptation data files to a floppy disk as a single file. This command
keeps you from having to save each of the adaptation data files individually. Below are
several important items pertaining to this command:
- There is adaptation data at both the Open RPG and MSCF that needs to be saved
using this command. There is no adaptation data for the BDDS.
- You can run this command on one computer and save adaptation data for the
other computer. See examples below.
- You can store both RPG and MSCF adaptation data files on the same floppy.
The file names generated by this command indicate which system the data is for and
when the data was saved.
- After you give the save_adapt_floppy command, you will be prompted
to place a floppy disk in the floppy drive. Insert the floppy and press
<Enter>.
- After the command finishes, remove the floppy, label it with type of
adaptation data on this floppy (RPG, MSCF, or Both) and the date. Place the
floppy in a safe place (i.e., where the RPG software CD-ROM is stored).
- This command only takes a few seconds to run. So run it
often!!!
- You must be logged in as a normal RPG user to issue this command. You can
not run this command while logged in as the root user.
- You can issue this command at any open terminal window. If no
terminal window is open, right-click anywhere on the background (i.e., outside
any open window) and select Tools and then Terminal.
- The floppy disk used should have already been formatted. Standard DOS
formatting is okay.
- If you get the error message "Command not found", then your path is not
correct for the current terminal window. Open a new terminal window and try
again.
Examples: The following examples show the most useful save_adapt_floppy
options. For a full list of the options, see the man page.
- To save MSCF adaptation data to the MSCF floppy drive, issue the following command
at a terminal window on the MSCF:
save_adapt_floppy<Enter>
- To save RPG adaptation data to the RPG floppy drive, issue the following command at
a terminal window on the RPG:
save_adapt_floppy<Enter>
- To save RPG adaptation data to the MSCF floppy drive, issue the following command at
a terminal window on the MSCF:
save_adapt_floppy -o rpg<Enter>
- To save MSCF adaptation data to the RPG floppy drive, issue the following command at
a terminal window on the RPG:
save_adapt_floppy -o mscf<Enter>
- To save both the RPG and MSCF adaptation data to the MSCF floppy drive, issue the
following commands at a terminal window on the MSCF:
save_adapt_floppy -o rpg<Enter>
After the first save is complete, issue the command
save_adapt_floppy<Enter>
- To save both the RPG and MSCF adaptation data to the RPG floppy drive, issue the
following commands at a terminal window on the RPG:
save_adapt_floppy<Enter>
After the first save is complete, issue the command
save_adapt_floppy -o mscf<Enter>
Last Updated: |
November 29, 2001 |
Applicability: |
ORPG System Administrators |
Background Information: The command restore_adapt_floppy is used to restore all
site specific adaptation data files from a floppy disk. See above for information on
saving data to the floppy disk. Below are several important items
pertaining to this command:
- There is adaptation data at both the Open RPG and MSCF that may need to be
restored using this command. There is no adaptation data for the BDDS.
- You can run this command on one computer and restore adaptation data for the
other computer. See examples below.
- After you give the restore_adapt_floppy command, you will be prompted
to place a floppy disk with the saved data in the floppy drive. Insert your
adaptation floppy in the drive and press <Enter>.
- You must be logged in as a normal RPG user to issue this command. You can
not run this command while logged in as the root user.
- This command only copies the adaptation data files over to the RPG or MSCF,
but they are not used immediately. For the RPG, this adaptation data will be used
after the RPG software is stopped and restarted. Likewise for the MSCF, the
restored data will be used the next time the MSCF or HCI is run.
- You must be logged in as a normal RPG user to issue this command. You can
not run this command while logged in as the root user.
- You can issue this command at any open terminal window. If no
terminal window is open, right-click anywhere on the background (i.e., outside
any open window) and select Tools and then Terminal.
- If you get the error message "Command Not Found", then your path is not
correct for the current terminal window. Open a new terminal window and try
again.
Examples: The following examples show the most useful restore_adapt_floppy
options. For a full list of the options, see the man page.
- To restore MSCF adaptation data from the MSCF floppy drive, issue the following command
at a terminal window on the MSCF:
restore_adapt_floppy<Enter>
- To restore RPG adaptation data from the RPG floppy drive, issue the following command at
a terminal window on the RPG:
restore_adapt_floppy<Enter>
- To restore RPG adaptation data from the MSCF floppy drive, issue the following command at
a terminal window on the MSCF:
restore_adapt_floppy -o rpg<Enter>
- To restore MSCF adaptation data from the RPG floppy drive, issue the following command at
a terminal window on the RPG:
restore_adapt_floppy -o mscf<Enter>
- To restore both the RPG and MSCF adaptation data from the MSCF floppy drive, issue the
following commands at a terminal window on the MSCF:
restore_adapt_floppy -o rpg<Enter>
After the first restore is complete, issue the command
restore_adapt_floppy<Enter>
- To restore both the RPG and MSCF adaptation data from the RPG floppy drive, issue the
following commands at a terminal window on the RPG:
restore_adapt_floppy<Enter>
After the first restore is complete, issue the command
restore_adapt_floppy -o mscf<Enter>
Note: As stated above, this restore_adapt_floppy command only
copies the adaptation data files over to the RPG or MSCF, but they are not
used immediately. For the RPG, this adaptation data will be used after the
RPG software is stopped and restarted. Likewise for the MSCF, the restored
data will be used the next time the MSCF or HCI is run.
Last Updated: |
March 11, 2002 |
Applicability: |
ORPG System Administrators |
General Information: The following items provide information on ORPG user accounts
and their password requirements.
- There will be user accounts on all three ORPG computer systems (i.e., the RPG,
MSCF, and BDDS). Typically, the same user accounts will be created on all three systems.
- The passwords for these accounts have the following settings/restrictions:
- The password must be 8 characters long with at least 2 alphabetic characters
and 1 numeric or special character. The password is case sensitive.
- If the password is longer than 8 characters, only the first 8 characters are
significant.
- The password is set to expire after 90 days.
- When you change the password, at least 3 characters must change from your
last password. For comparison purposes, upper and lower case characters are
equivalent.
- The password must differ from the login user name. For comparison purposes,
upper and lower case characters are equivalent.
- When you need to change the password on a user account and you enter the passwd
command, you may get a error message saying "Permission denied". If you do, this is because of
an effective user issue which is discussed below. To get around this
problem, use the following procedure at a normal terminal window at whichever system the account
is on (e.g., RPG, MSCF, or BDDS):
- exit<Enter>
- passwd<Enter>
- Enter the new password and press <Enter>
- Enter the new password again and press <Enter>
- exit<Enter>
- While the security concept for the Open RPG says that each person on-site should have
their own user account, most early ORPG sites have not implemented this. Instead, they have a
single user account for use by all the operational staff. If you do use this method,
ALL staff members need to know the password for this account. Also, be sure to
define this account on all three systems (e.g., RPG, MSCF, and BDDS).
- The root password should only be known by a few people. At the very least, both the
operations and maintenance focal points should know this password.
- If a user account password is lost, the System Administrator can reset this password
by using the following procedure at any terminal window for that system (e.g., RPG, MSCF, or BDDS):
- su<Enter>
- Enter the root password when prompted
- passwd user_account<Enter> where user_account is the account to be reset.
- Enter the new password and press <Enter>
- Enter the new password again and press <Enter>
- exit <Enter>
- Not only are the user account passwords is set to expire after 90 days, but the root password
is also set to expire every 90 days. If the root password expires, you will no longer be able to
issue the su command to change to the root user! To change the root password after it
has expired, you will have to logout of the CDE and log back in as root. You will be prompted
to change the root password.
- If you forget the root account on one of the Open RPG systems (e.g., RPG, MSCF, or
BDDS), there is a procedure for resetting that password. Contact the Hotline and we will
fax the procedure to you.
- There are several predefined user accounts already on your Open RPG when it is
installed. For example, there is a Version Account that is used by the RPG software
and must not be changed. These predefined accounts should not be changed. However, if there
is an account called inco or incoteam still on your system after the INCO Team departs, then this
account should be deleted!
Last Updated: |
November 29, 2001 |
Applicability: |
ORPG System Administrators |
The procedure for adding a new user account is given in NWS EHB 6-525 (a.k.a., AF TO
31P1-4-108-452-1 and FAA TI 6345.1 V49), Paragraph 4-6.9.2 and must be followed completely!
The new user must be in a specific group and have a specific Login Shell. Also, there is
a special command (update_users) that must be run after the user is added so that
user can run the ORPG software. The above reference gives each step needed.
Note that this procedure, in a slightly different form, is also given in NWS EHB 6-526
(a.k.a., AF TO 31P1-4-108-451-1 and FAA TI 6345.1 V50), Paragraph 2-9.3.3.3.
Last Updated: |
November 29, 2001 |
Applicability: |
ORPG System Administrators |
General Information: On the RPG and MSCF, but not the BDDS, an "effective user"
is used to ensure all the environmental variables needed by the ORPG software are set
properly. This "effective user" is set to a "version user account" which is named based on
the version of ORPG applications software loaded on your system. Most of the time you will
neither know nor care that this effective user is being used. However, if this effective
user gets changed, some of the RPG "command line" commands will not work properly.
The best way to understand how this "effective user" comes into play is by some example
commands. This example uses two fictitious user accounts: a regular RPG user account
called test1 and a version account called Ver1. Neither one
of these fictitious user accounts should actually exist on your system.
- Open a new terminal window by right-click anywhere on the background (i.e.,
outside any open window) and select Tools and then Terminal.
- Notice that the command line prompt is the system name followed by the
current directory. Since in this example you are logged in as the fictitious user
test1, the current directory is listed as /export/home/test1.
- Issue the command who am i<Enter>. Note that it tells you that
you are logged in as test1.
- Now issue the command whoami<Enter>. Note that it now displays
the effective user. In our example it would be Ver1. So, with the effective
user set properly, you can use any needed RPG commands.
- Another way to ensure the effective user is set properly is to issue the command
cd<Enter>. The prompt changes to, in our example, /export/home/Ver1.
The command pwd<Enter> would verify that the current directory has changed
to your RPG version directory. Most of the RPG software is stored under the version directory.
- Now let's "unset" this effective user by entering the command
exit<Enter><Enter>. Note that the prompt is now back to
/export/home/test1.
- Now issue the commands who am i<Enter> and whoami<Enter>.
Both will now respond with test1.
- At this point, most RPG commands would respond with the error Command not found.
For example, on the RPG there is a command rpg_ps that lists the status of RPG
processes. This command only works at the RPG, not the MSCF, and ONLY when the effective user
is set properly.
- If you do accidently type exit<Enter> at a terminal window and "unset"
this effective user, there are three ways to reset it, listed here in the preferred order
of use:
- Close the terminal window and open a new one
- Enter the command csh<Enter>
- Enter the command source .cshrc<Enter>
An Additional Note: This "effective user" actually hampers a user trying to reset their
password. See User Accounts - General Information above for the procedure
on resetting a user account password.
Last Updated: |
November 29, 2001 |
Applicability: |
All ORPG Users |
General Information: There are several methods that can be used to open a new
terminal window. Below are three methods:
Last Updated: |
November 29, 2001 |
Applicability: |
All ORPG Users |
General Information: There are several methods that can be used to open a new
terminal window. Below are two methods:
Last Updated: |
November 29, 2001 |
Applicability: |
All ORPG Users |
General Information: While not immediately obvious, there are differences between
a Terminal window and a Console window. Because of these differences, the following general
guidelines should be followed:
- When logged in on a system (RPG, MSCF, or BDDS), you will normally want to keep
a Console window opened at all times (it can be minimized). Many of the system errors
generated by Unix are displayed on the Console. The system will run fine without a
Console window open, but any errors that occur will not be seen if a console window
is opened "after the fact". Having the Console open will ensure the messages are
available for review when needed.
- You should only have one Console window open at any one time.
- While you can enter Unix or ORPG commands in a Console window, it is best not to.
If the system is trying to display system messages at the same time you are trying to
enter a command, unexpected results may occur.
- Always use a Terminal window for entering commands.
- Care must be taken when opening a new Terminal window. Most of the menu items
for opening a Console window are actually labeled "Terminal Console" while the items
to open a Terminal window are labeled "This Host". See above for the proper procedures
for opening a new Terminal or Console
window.
- If you are unsure whether a window is a Terminal window or a Console window, check
the header bar. It will normally say either "Terminal" or "Console".
|
