PRO:MAN
End-User Documentation [System Administration] [Utility]
[System Administration]version 7.x
[Module Objectives]
We will cover in detail the items needed by a system administrator. Many of these commands are database commands rather than Pro:Man commands. As such, you may want to review your D3 manual for more details on these topics
CONTENTSPAGE
SectionI.System Setup and Maintenance
Your D3 service3
Device Manager6
File Manager11
PRINTERS17
SPOOLER commands24
BACKUPS24
User Maintenance32
Checking system related phantoms33
How to properly shutdown your system
and your UPS34
Night Time Processor34
Sync36
Section II.User Setup
USERS_MAINT1
PROFILES_MAINT3
PDM_ACC_MAINT6
PIB_MAINT8
PDM_FUNC_KEY_MAINT9
RESET_PASSWORD13
CONTENTSPAGE
Section III.Security
CREATE-ACCOUNT2
PDM_MAINT5
UPDATE_ACCT_MENU9
FS_UPDATE15
TRX_LOG_RPT13
Section IV.Reference Sheets
Tape Backup Log Sheets
Check-off Sheet for new users
Incident Report
Flow chart for Primary System Set-Up
Flow chart for Add New User(s)
Flow chart for Updating Existing User
Flow chart for Deleting a User
Flow chart for Renaming a User(s)
System Setup and Maintenance
This section covers how to set up your D3 system and how to maintain it. This should be performed by your system administrator only.
Services
D3 is now a service under Windows 2003/2008. This means that you need to set some parameters for your service. The services manager can be found under START, SETTINGS, CONTROL PANEL, Administrative Tools, Services. After installing D3, two entries should show up in this window. These are D3 Virtual Machine Environment and D3 ODBC Server. These are shown as :
Your D3 ODBC Server should be set to “Manual” under Startup Type. This will be started inside of D3 as shown later in the section listed below under ‘USER-COLDSTART’. You will want to set your D3 Machine Environment to be “Automatic” under most circumstances. This means that when Windwos starts, D3 will start automatically. You set this by highlighting the service, D3 Machine Environment, and right click your mouse. Highlight the “PROPERTIES” and click.
The property dialog box will be displayed. The startup flag is in the middle of the screen with a drop down box. Set this to “automatic”. Please see the notes below regarding shutting down D3 along with a system reboot. If you are working on an Windows issue that requires a number of reboots, you may want to set this service to “manual”, so that you do not have to wait for the service to stop each time you reboot.
There is also a “Log On” tab on this screen. You will probably want to set this to log on as “administrator”. Any change made on this screen must have an identical change made to the same tab on the D3 ODBC service. The two services MUST be logged on the same way as they share memory space and they must have the same permissions.
The D3 default for this tab is “Local System Account”. You may not have sufficient permissions to print or back up your machine, depending on how you have set up your domain. If all of the printers are defined locally, and your backup devices are on this machine, and your pseudo floppies are on this machine, and you have no other web services running, you may be able to leave this as “local system account”.
Also NOTE ! If you change the password on your administrator account, you must change the password in this tab. Otherwise, D3 will not start.
Click “APPLY” and “OK”.
If you have set the service to manual, you must highlight the service and then click the “Start” button. This screen will respond with “started” very quickly. In reality, the environment is not completely started for users to log in. This takes anywhere from a few seconds to a couple of minutes. If you open the task manager (right click on your task bar on bottom of the screen), click on the heading that says “Mem Usage”. That will sort the running services by memory usage. D3Vme.exe should be near (or at) the top of the list. The memory usage should stop counting when the service is fully functional and user can log in. Have your users wait until the service is fully functional.
D3 Device Manager
The device manager allows you to setup a number of system-related parameters. We will not provide the entire functionality for this tool, as your installer should have set some of these parameters. Our Knowledge Base contains other rarely used functionality.
All changes made in the Device Manager are registry type settings. They only take effect upon start of your D3 service. Therefore, you may make changes while D3 is running, but they will not take effect until the next time you start D3.
This tool must be run from the console of your D3/NT server. You need to click START, PROGRAMS, D3. You must then click on “Device Manager”. You should see a screen similar to the following:
While the first tab might list printers, NEVER set your printers up on this page. See the PRINTERS section below for the proper way define and start your printers.
You should, however, start your tape devices using the second tab.
The available tape devices are listed in the left-hand window. The number of entries will depend on the equipment in your machine, and may not match what is shown above. This machine has a “A” floppy drive. All systems have a pre-built “pseudo” tape device that allows you to use a file on your hard drive as a tape device. You must have your tape devices defined in Windows before they will show up in this window. Hence, your tape devices should be installed and configured before attempting to set them up in D3.
The right side of the screen lists devices that have been configured for use in D3. There is a maximum of 15 devices in versions of D3 prior to 7.5.5 that can be defined. In our example above, we can see that our floppy drive “A” is set as device “0”. Devices 1 and 2 will be setup by D3 automatically during the installation process and should be left alone. You are free to define all the remaining devices. In our case device 3 is our pseudo for nightly backups. If you have Tape devices in your server (and most today do not) the tape names , Tape0 and Tape1, should correspond to the tape property pages in Windows. These will be assigned by Windows automatically.
The balance of the tape devices are pseudo tape devices. They refer to files that can be used on a temporary basis to save information and then restore information back from.
To configure a new device, click on the available device in the left pane, and then click on an unused device number in the right pane.
If you select a “pseudo” type device, you will be prompted for the file to use. You must then click the “add” button on the right side of the screen. This will look something like:
This is the standard Windows type dialog box. You can create new directories. We suggest that you create a directory and place all your pseudos in it. These can grow quite large and if they are all in the same directory, it is quite easy to review and delete any to reclaim disk space. The pseudo file name can be any name that you like. We suggest using names that indicate what is in the pseudo. Sometimes “junk” is just that, a temporary file that is used like the TEMP directory in Windows. It could be deleted at any time and would not affect system integrity. Othertimes, a file called “acct_save” would indicate that some account was saved in it, and should not be deleted without careful consideration. Other creative pseudo names include monthend, yearend, fs2001_12, etc.
The file can exist or can be new. It is your choice. If it exists, the system asks “do you want to use the existing file”. You should answer “Y”. It does nothing to the information in the file when you do this. Hence, you can copy a pseudo back in from an Windows backup, create a pseudo to it, using the newly restored file name, and you will be able to read the data from it.
Any changes made on this tab will take effect the next time that you start the service. If you need a new pseudo when D3 is already running, you can see the directions below that describe making a psuedo on the fly.
The third tab should normally be left alone.
You should not change the name on you server once you have installed D3. All of your FSI data will seem to disappear. The MDS server name in the left panel shows the machine name that D3 is expecting. If you have changed your machine name, call your Pro:Man representative and get assistance. This may very well require a call to Raining Data, so you should be on support contract with them.
The VME disk size can be of some importance. The default size, when you install your D3 database is 254 Megs. This is the working space for the database (not your actual data). Typically this can be fine. However, over time this space is not recovered from normal processes. If you ever loose power to the server, or if you log off users, space can be lost. You can safely increase this to 1 gig (as shown above) as needed. If you have problems (some described below), you will need to restore your work area (this is called DISK0 retore). There are documents on the Knowledge Base, should this ever be necessary.
Problem: users are receiving a message “out of disk space”
Answer:
Make sure that disk drive that your data is stored on has free space. You can check the properties of the drive with “my computer” or “disk management on “computer management”. If you have enough space here, the problem is most likely your work space. Log into the D3 and go to CMD_LINE, in the command box, type FREE and click process. You will then see your free space. Now you can either:
Increase your VME size (shown above), stop D3 service and restart it
or
Do a DISK0 restore
Problem: users are prompted for their user ID, once entered the system does not respond.
Answer:
stop D3 service, restart D3. If the problem persists, or it will not stop correctly, you must do a DISK0 restore
On older versions of the database, older than 7.5.0, this memory loss occurs more frequently. On older versions, the loss occurs less frequently. Typically, even with releases 7.5.x, we find that a Disk0 is required once a year.
Finally, you may elect to disable telnet port 23 from being a D3 database port. There a couple of reasons to consider this. First, security !! It is normal for someone to telnet to a server on port 23 as an industry standard. Hence, if this is disabled, they will not be able to telnet to the server and hack into it as easily. The hacker can still do a port scan and find other open ports, but it will be a bit harder. Second, you may have another service running that requires port 23. Some remote administration programs require standard telnet services. We normally suggest that you disable port 23 and “nail” all of the ports to specific users. There are a couple of reasons for this, but if you nail a port, the users will be on the same database port all the time. This will allow us to define certain parameters for that user by port.
This “nailing” of ports is done on the fourth tab. It looks like:
Your screen may not look like this. In our case, we have skipped some “nailed” ports to allow for standard COM ports. This may be setup for a dumb terminal, or more likely a modem.
We have then nailed telnet ports “3030 through 3050” to D3 ports 30 through 50. This means that if a user telnets to the machine on port “3030”, they will always be port 30 inside of D3.
To add nailed ports, you must follow this procedure (like it or not). First highlight some available port numbers in the left pane by clicking and holding down your mouse button. Highlight as many ports as you like. This need not match the number of port that you have purchased. We typically configure more as this is the number of devices that MAY attach to the server, while your licenses are the number of people actually logged on concurrently.
With the port numbers highlighted, move the slide bar using the arrows called “NailedTelnetPort Configuration”. You cannot enter the port number;you must slide the bar until the corresponding telnet port is displayed. You need to pick port numbers that typically are not used by other telnet services on your machine. Typically the 3000 or 4000 range is ok. You may find that this is not the case in your environment. Go back into this screen and change the telnet ports. You can use numbers up to 65000. Note that if you have installed VNC as your remote support tool, it uses ports 5800 and then 5900,5901, etc. up to 5999. So stay away from these port numbers.
Finally, highlight anything that is shown in the “text box” on the right side, bottom of the screen. This defaults to something similar to “,,dm,dm,term j,”. This means that when the port shows up, execute <enter> <enter> and then log into the system using the DM user and then log into the DM account, using “J” terminal emulation. WE NEVER want this to happen. So always highlight this and press “delete” key.
At this point you can click on the ADD button.
There are a couple of exceptions to this format. The system has the ability to automatically open certain fastkeys (menu options) when a user logs in. However, there are times that we want the system to simply open directly to specific screen when the PC is first booted up. There is a separate document in the KB describing this setup, however, we will note the way to set this port up here.
You may have specific ports designated to run certain fastkeys or functions.
The first high lighted port “100” is how an RF bar code gun will look like. Set your bar code gun to log into port 100 and this server for this functionality.
The next section, ports “101-104” are for time and attendance clock stations. These ports will run the clock time application automatically.
The last section, port 105, is how a port would look for a labor collection stations on the shop floor. In this case, it was for a station that only runs MST_ENTRY.
See the KB for specific directions on setting up the PC and how to set these up.
The last tab on the device manager looks like:
You can leave all of these items alone, unless your instructed to do so by your PROMAN representative.
Click on EXIT to save your changes and close the window. You must stop the service and restart it before you can use these ports.
D3 File Manager
Typically you do not need to use this item. It is found in the same folder as the device manager discussed above. All of the features in this program can be done inside of D3 at a later time. Some people find the file sizing to be a bit easier to use in this program. It is a matter of preference. For reference sake, we will review it here.
This program will open a window similar to:
You will need to click on the “open” folder on the toolbar. Under normal circumstances, your only VME will immediately display. If you have a rare multiple VME environment, select the machine you are looking at. Otherwise, you will immediately see our database accounts show up as shown below:
Your accounts will be different than shown. You will have at least one account called PROMAN.
Click the small + next to the account name. It will explode out to “synonyms” and “tables”. Your table directory contains all of your data files in this account. Click the + next to the tables to see your files. With “Tables” highlighted, right click on it. You will see a dialog box pop up. The last entry in that box is “check overflow” Click on that. The system will respond immediately by flashing through each file. When all of the files have been reviewed (less than 60 seconds on most machines), you will see a new dialog box, similar to this: