Admind 3

D3 Linux System Administration Guide
TigerLogic Corporation 25A Technology Dr. Suite 100 Irvine, CA 92618 www.tigerlogic.com
949 442-4400
D3 Linux System Administration Guide Overview

The System Administration Guide includes topics for configuring and administering D3 Linux, including discussions about the D3 utilities and how to use them. Use the table below as a guide to this document: Topic Document Conventions Creating a Turnkey System Administering UNIX ODBC Servers Hot Backup D3 Configuration File Tape Statements Peripherals Description Describes the different typefaces and type styles that are used throughout this document. How to set up your system so users only get a D3 logon message, not a UNIX login message. A menu-driven utility for administering an ODBC Server from the TCL prompt. Provides an overview and describes the implementation of the D3 UNIX Hot Backup utility. Information specific to the tape portion of the D3 configuration file. Various types of peripherals used by D3 including: Disksincluding SCSI, (E)IDE, and floppy disks, as well as partition names Printershow to add, remove, and troubleshoot reserved and shared printers, how to spool directly to UNIX and printing to Netware printers. Tapesincluding SCSI, multireel saves, 4mm and 8mm tapes
D3 File Sizer Utility
Use the D3 File Sizer Utility to resize D3 NT or D3 UNIX files automatically or manually.
TigerLogic Corporation
Document Conventions
Different typefaces and type styles are used throughout this document to indicate specific information.
Syntax Conventions
Convention Mono and Mono Bold Description Code examples, syntax, commands, menu items, screen text, and other keywords recognized by the system. All such text is displayed in Mono Bold to allow for quick identification when the text is referenced within general descriptive text. Additionally, Mono Bold is used in code, syntax and screen text boxes to distinguish between typed text and text that is displayed or returned by the system. For example: Typed Text Returned Text Italic n{-m} Variables to be replaced by the value. It can be an actual name, word, or number. For example, file.name might be replaced with CUST.FILE. Non-linked references to other documents or topics within this document. Emphasis for impact or the first time a word is used. For example, resources and information make up the state of the application.
The letters n and m represent numbers. Numbers are usually input as a single string without commas. Numbers can also be used to define a range designation. The starting and ending numbers are typed with a hyphen between. For example, n{-m} could be replaced by 10 or by 1-31. Braces ( {} ) delimit a mutually exclusive set of options. The vertical line or pipe sign ( | ) separates a mutually exclusive set of options. Brackets ( [ ] ) indicate optional entries.
{} on | off [0 | line | ?]
D3 Naming Conventions
Throughout this guide there are references to D3, D3, and d3. This is fully intentional and care was taken that every reference is correct. D3 d3 Proper name of the DBMS software product that is referred to as D3 throughout this document. The name can appear as d3 when the name appears in the command language or file names.
D3 Terms
These D3 terms are used throughout: Term log in connect Description This term refers to the Linux log in. A user logs in using the UNIX user name and optional password. ALinux user establishes a connection with a virtual machine. The default virtual machine name is pick0. If several virtual machines exist on the same system, the user identifies the virtual machine using a symbolic name such as d3_newyork_branch. Normally, this displays the D3 logon message. As noted elsewhere, the D3 log on and connect steps can be made automatic so a D3 user does not need aLinux login name and password. This is a logical connection, and has nothing to do with the serial port. There is no process-to-process communication or data movement of any kind. log on This term refers to logging on to D3. A user logs on by giving a D3 user name, and an optional master dictionary and password. On a turnkey system, this is the only interface the end-user sees. Generally, to disconnect from the D3 environment, execute the exit command. On a default, non-turnkey system, disconnecting releases the user to the UNIX shell and terminates the D3 session. On a turnkey process, disconnecting returns the user to the D3 logon prompt. A user logged on to the D3 virtual machine can disconnect temporarily, dropping to the Linux shell. The user is still logged on to the D3 virtual machine, suspending the D3 environment until they reconnect to the virtual machine and resume activity. Each D3 user process is an operating system process, making data exchange between the D3 environment and the operating system simple and efficient.
disconnect
process
Related Documentation
To download or order related documentation published by TigerLogic Corporation, please refer to the TigerLogic Web site at: http://www.tigerlogic.com/tigerlogic/pick/support/documentation/index.jsp
Creating a Turnkey System

This section describes what turnkey systems are and how they are created. The following topics are discussed: Turnkey Systems Using Increased Functionality Configuring Blocks of Telnet Ports on D3 Maintaining Compatibility Changing inittab
Turnkey Systems
The system may be set up so users only get a D3 logon message, not a UNIX login message. This type of system is called turnkey. Turnkey systems should allocate no more than 85% of the total physical memory to shared memory. Non-turnkey systems should allocate no more than 50% of the total physical memory to shared memory. As the number of users reaches 100 or more, a 50/50 memory split is recommended for best performance. Before creating a turnkey system, decide which devices will be UNIX terminals and which devices will be D3 terminals. Both serial tty connections and network Telnet connections can be reserved for D3 ports. Various methods to create a turnkey system are discussed below. Review these sections to determine the method that best fits your needs.
Using Increased Functionality

Setting up the turnkey system using either of the next two methods provides increased Telnet functionality, but does not maintain compatibility with other D3 platforms and releases. The following methods are the recommended methods for setting up a turnkey system.
Connecting to the Next Available D3 Port

Configuring Telnet in this manner sends the user directly to the D3 logon prompt. It does not display the Telnet login prompt. 1. Create a copy of the /etc/xinetd.d/telnet file. For example: cp /etc/xinetd.d/telnet /etc 2. Create an executable script to execute D3 and place the script in the /usr/bin directory. This is a sample script. We will name it tnet for our example: #!/bin/bash exec /usr/bin/d3 -dcdon 3. Open the Telnet configuration file. /etc/xinetd.d/telnet 4. Add a reference to the script you created in the this configuration file. NOTE This instructs the Telnet configuration file to run the D3 program when connection is established and instructs the D3 logon to open immediately when a Telnet connection is requested.
For example, add this line under the server option line. server_args = -L /usr/bin/tnet Before the Telnet file is modified to add the script under the server_args option, the file looks like this: { flags = REUSE socket_type = stream wait = no user = root server = /usr/sbin/in.telnetd log_on_failure += USERID disable = no } After the Telnet file is modified to add the script under the server_args option, the file looks like this:
{ flags = REUSE socket_type = stream wait = no user = root server = /usr/sbin/in.telnetd server_args = -L /usr/bin/tnet log_on_failure += USERID disable = no } 5. Restart the xinetd daemon (so the modification you performed in step three will take effect) by typing this script: /etc/rc.d/init.d/xinetd restart
Connecting to a Specific D3 PIB

Configuring Telnet in this manner bypasses a UNIX log in, providing a direct login to a D3 PIB. 1. Create a permanent directory to hold both the following script and the symbolic links to that script. For this example the directory name is d3net. It is placed in the /usr/bin directory. The full path is /usr/bin/d3net. Set the permissions to read and execute (rx) for all users.
This example creates the directory named d3net in the /usr/bin directory, and changes the permissions to read and execute for all users. mkdir /usr/bin/d3net chmod a+rx /usr/bin/d3net 2. Select a range of port numbers not currently in use on your system, and large enough for all your D3 PIBs. This example uses PIBs 1 through 20. The port range is 16001 to 16020. 3. Create a script to calculate the PIB from the port number and place it in the directory created in step 1. The script executes d3 passing the result of the subtraction as the only argument on the command line. The following sample script does this. For this example, assume the script name is netcon and the directory name is /usr/bin/d3net, the full path is /usr/bin/d3net/netcon. Enter: #!/bin/bash PIB=$(basename $0) PIB=$(($PIB 16000)) exec /usr/bin/d3 $PIB 4. Change the permissions to read and execute for all users. chmod a+rx /usr/bin/d3net/netcon 5. Create a symbolic link (ln s) for each port in the range, using the port number as the name of the link, and the script you created as the source. Remember, in our example the script name is netcon, and the port range is 16001 to 16020.
ln ln ln ln ln ln
s s s s s s
/usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon
/usr/bin/d3net/16001 /usr/bin/d3net/16002 /usr/bin/d3net/16003 /usr/bin/d3net/16018 /usr/bin/d3net/16019 /usr/bin/d3net/16020
When all the links are created, a long listing (ls l) of the directory looks like: total 50 lrwxrwxrwx lrwxrwxrwx lrwxrwxrwx lrwxrwxrwx lrwxrwxrwx lrwxrwxrwx -rwxr-xr-x 1 1 1 1 1 1 1 root root root root root root root root root root root root root root 6 6 6 6 6 6 72 Jan Jan Jan Jan Jan Jan Aug 14 14 14 14 14 14 7 18:47 18:47 18:47 18:47 18:47 18:47 14:03 16001 -> 16002 -> 16003 -> 16018 -> 16019 -> 16020 -> netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon
To operate the nailed Telnet feature

For every file that is put into the /usr/bin/d3net directory, a corresponding file must be created in the /etc/xinetd.d directory. This assures proper operation of the Telnet feature. Create a file in the /etc/xinetd.d directory, like the one shown below, for each of the ports that will be used for log in. For Example: service d316001 { type socket_type protocol wait server server_args port }
= = = = = = =
UNLISTED stream tcp yes /usr/sbin/in.telnetd -L /usr/bin/d3net/16001 16001
In the example above, note that the: Name of this file is d316001 (d3+ port number). The name of each file in your range of ports will be d3 + the next port number in the sequence of numbers chosen for your range of ports. For instance, the next file name for this example will be d316002. service d316001 line of our example uses the same name as the file name. server_args line must end with the same number used in the file name and the service d316001 line. port line of our example must reflect the same number as the service d3, and the server_args lines; note that in our example the port number is also 16001.
After all of the files in your range of ports have been created, issue this command to restart the deamon. /etc/rc.d/init.d/xinetd restart
Configuring Blocks of Telnet Ports on D3

The auto-xinet command is used to configure one or more blocks of telnet ports on D3. NOTE You must have root privilege to use this utility. You must start a D3 session using the -l option (d3 -l) prior to using this command.
Syntax auto-xinet <start_port> <port_count> <start_pib> <vmname> <pool_name> <(options> Parameter(s)
start_port port_count start_pib vname pool_name options
Network port at which to start (must be greater than 1024). The available TCP ports can be verified from the etc/services file. Number of telnet ports to start (1-65536). Starting D3 PIB (defaults to 1). Virtual Machine name (configuration file name). Name that defines this group of telnet sessions. Multiple pool names can be specified. d l r s Enables Data Carrier Detect (DCD) protocol handling. Displays a list of defined pools. Removes all nailed telnet ports. Suppresses killing existing telnet processes. Must be specified in conjunction with the (r option.
Maintaining Compatibility
These sections discuss creating a turnkey system while maintaining consistency and compatibility with other D3 platforms and releases.
Boot File /etc/inittab

The UNIX file /etc/inittab contains information on how each device is to be initialized and what has been modified. The /etc/inittab file can be modified so the desired tty devices boot directly to the D3 virtual machine. To modify the entries in the /etc/inittab script file, use the Update Processor, the Editor, or the UNIX command vi. See the man pages for more information on inittab entries.
Serial Turnkey
A port designated as a serial turnkey process maintains compatibility. To create a turnkey system in this manner, include an entry similar to the example below in the inittab file. An example entry to respawn tty2 to D3 port 1 is: a1:2:respawn:d3 -n pick0 1 -t tty2 The label a1 is a unique two character ID. The d3 command follows the standard syntax defined in the D3 Reference Manual where: -n pick0 identifies the D3 configuration file 1 specifies the D3 PIB or port number -t tty2 identifies the tty to which the D3 process is attached
Setting Parameters for Serial Lines

There is a new way to configure a serial line. In the /usr/lib/pick directory, create a new subdirectory named pick_term. The pick_term directory will contain files that have serial configuration parameters for D3 lines. The name of each file is the PIB number that it represents. If the PIB is number 5, the file name is 5, and the full path to the file is: /usr/lib/pick/pick_term/5 The files within the newly created pick_term directory contain all of the configuration parameters needed for the serial line they represent. To set a nailed serial line to use the default parameters: If a file has not been created to use the pick_term directory for a nailed serial line, the system assigns the default parameters. Both examples use a serial line on tty5 and PIB5. 1. Starting a nailed serial line to use the default parameters, for example: a5:2:respawn:/usr/bin/d3 -n pick0 5 -t tty5
10
Omitting the -T option from the command line in the inittab sets the serial line to use the default parameters. 2. Starting a nailed serial line to use the configuration parameters stored in the pick_term directory, for example: a5:2:respawn:/usr/bin/d3 -n pick0 5 -t tty5 -T Adding the -T option to the command line in the inittab sets the serial line to use the configuration stored in the pick_term directory. To create the files in the pick_term directory using the set-port command: The files in the pick_term directory contain stty serial configuration commands, and can be created and populated manually using the set-port command. When you use the set-port command to create the files for the pick_term directory, if a file does not already exist one will be created. If a file does exist, the existing configuration will be overwritten. Listed below are several commands that are supported: Baud Rate 110 150 300 600 1200 2400 4800 9600 19200 38400 Description = 110 baud = 150 baud = 300 baud = 600 baud = 1200 baud = 2400 baud = 4800 baud = 9600 baud = 19200 baud = 38400 baud
Word Length cs7 cs8
Description = 7 bits = 8 bits
Parity -parenb parenb parodd
Description = no parity = odd parity
11
parenb -parodd
= even parity
Stop Bit -cstopb cstopb Examples
Description = 1 stop bit = 2 stop bit
TCL Command 9600,8,N,1 4800,7,0,2 38400,7,E,1
Serial Line Configuration Command (as it appears in the file) = 9600 cs8 -parenb -cstopb = 4800 cs7 parenb parodd cstopb = 38400 cs7 parenb -parodd -cstopb
An example of this command at the TCL prompt is: set-port 5,9600,8,N,1 where 5 is the PIB 9600 is the Baud Rate 8 is the Word Length N is no Parity 1 is one Stop Bit
12
Changing inittab
When the serial port is not in use, a single D3 turnkey respawn can be disabled. Comment out the inittab entry with the # sign, as in: #a1:2:respawn:d3 -n pick0 1 -t tty2 Another way to do this is to delete the entry in question, or replace the process information for a tty with a valid /etc/getty command sequence, rather than d3. Execute the command init q to activate any changes to the inittab file. WARNING The file /etc/inittab is a highly sensitive UNIX system configuration script. Any changes made to this file must be accurate before exiting from the editor. Invalid entries can cause unpredictable events to occur in UNIX, including system hangs and rapidly respawning processes.
13
Administering UNIX ODBC Servers

The D3 ODBC account MAIN MENU is available for administering a UNIX ODBC server from the TCL prompt. This menu provides options for configuring, starting, stopping, and monitoring the ODBC server. MENU MANAGER: Enter Number of Choice or <ESC> to exit menu D3 ODBC account Main Menu 0 Exit to TCL 1 Configure ODBC 2 Start ODBC 3 Stop ODBC 4 ODBC Status To display the menu: 1. Log on to the dm account from the TCL prompt by typing: to dm 2. Type: ODBC If the message odbc.menu is not a menu item displays, this method for administering the ODBC server is not available. When the menu displays, select one of the five options: Exit to TCL Configure ODBC The TCL prompt displays. Allows the setting of ODBC server parameters. For each of the ODBC parameters, the current settings display. If this is the first time configuring the server through this utility, the default settings display. To change the setting: 1. Use the BACKSPACE key to delete the current setting. 2. Enter the new setting. 3. Press ENTER to move to the next parameter. To return to a parameter once the cursor has moved beyond that line: 1. Continue pressing ENTER until the Main menu displays again. 2. Select the Configure ODBC option to return to the ODBC server parameters. The ODBC Server parameters are:
14
cache.flat
Sets the caching strategy of the ODBC server. The default is no, which indicates progressive caching. For flat caching, set the parameter to yes. Sets the maximum cache size of the ODBC server. If left blank, the default maximum cache size of 200 rows is used. Tells the ODBC server to provide debugging messages. The default is no. Debugging messages are directed to the file specified in the logfile parameter. Specifies the file where error messages will be logged. The default is /dev/null/, which indicates that messages are not logged to a file. Specifies the file where debugging messages will be logged. The default is /dev/null/, which indicates that messages are not logged to a file. Sets the TCP port number on which the ODBC client and server operates. The default is 1603. Specifies the number of minutes of inactivity to wait before disconnecting the process and logging off the server.
cache.rows debug
errorfile logfile
port timeout Start ODBC Stop ODBC
Starts the ODBC server using the parameters set in the Configure ODBC option. Displays a list of running servers and the prompt below: Enter port number to stop, <Enter> to stop all servers, or c to cancel: Enter the port number of that server (the rightmost number under the COMMAND column) to stop a particular server. Press ENTER to stop all ODBC servers. Type C to cancel the stopping of servers.
ODBC Status
Displays a list of servers running on the system.
15
Hot Backup
This section provides an overview and describes the implementation of the D3 UNIX Hot Backup utility. The topics discussed are: Hot Backup Introduction Requirements Configuring Hot Backup Starting Hot Backup Using Hot Backup Hot Backup Errors
16
Hot Backup Introduction

It is often necessary to employ a strategy that significantly limits down-time due to hardware or software failures. A solution, often more affordable than fault tolerance, is to double your hardware resources by maintaining your database on two separate servers. Hot Backup is a D3 UNIX feature that employs a backup server in standby mode, ready to handle the workload should a system failure occur. The Hot Backup configuration involves two servers: Master Slave The main server in operation. The backup server. Runs concurrently with the master and maintains a mirror copy of the database on the master server.
These servers are connected via a TCP/IP connection. During normal operations, some or all updates to the database on the master server can be applied to the slave server, over the network. If the master server fails, users can be switched to the slave server, and the application restarted. Down-time is limited to the time it takes to switch servers (usually the time required for terminal connectors to establish an Ethernet connection to the slave server). Data loss is limited to any updates that have not been transmitted to the slave server (typically, this is limited to the updates that occurred in the last few seconds before the failure).
Definitions
server master slave transaction log queue A background process. Hot Backup servers work in pairs: one on each machine. Main server on which users normally work. The server running on the master system is called the master server. Backup for the master server. The server running on the slave system is called the slave server. Updates to the master server are placed in the transaction log queue on the master server, which is emptied regularly to the slave server in a FIFO manner. In normal operation, this queue should remain minimal in size. When a transaction is extracted from the queue, it is assigned a transaction number. Transactions are physically removed from the queue only when the slave server acknowledges them. This ensures that if an error occurs before the item is stored in the remote file, the transaction can be sent again to the slave. Updates to the slave server itself are not logged in the slave servers transaction log queue. However, it is possible to set up the system so that a slave server acts as a master server to another slave (to cascade updates). This type of Hot Backup configuration is set up using the Log slave update option in the Setup Server utility. It is possible to instruct a slave server not to modify the database on the slave server. Updates received from the master server are not applied to the slave database. Instead they are stored in a temporary file. The purpose is to have a quiescent database on the slave server without stopping the master server (for example, to allow a full save of the database). Updates can then be applied to the slave database at a later time.
log slave updates
apply updates
17
file and account auto-create helper
Normal operation of Hot Backup is to have an exact image of the master database. Optionally, the slave server attempts to create any nonexistent accounts or files on the slave server. On the slave server, long operations, such as clearing large files, are not processed by the slave server itself, since it would not be able to process any incoming data. The slave server creates helpers (phantom processes) to perform these operations. Files with modulos larger than 100 are initially created by the slave server with a modulo of 101. A helper process then resizes the file to its actual size. This allows you to instantly create the file, making it available on the slave system without stopping the slave server. The slave server performs periodic checks on the helper to ensure that it completes. Slave systems sometimes create temporary files on the slave server to hold data that cannot be transmitted to its destination immediately. For example, when a clear-file command is run, a helper performs the actual clearing and a temporary hold file holds any updates to the file being cleared that are received after the clear command. This ensures that the updates are not deleted.
large file creation
temporary hold files
18
Requirements
The following section described the requirements and restrictions for Hot Backup.
Hardware Requirements
The master and slave servers used in a Hot Backup configuration should be of equal performance and operating systems. The servers are connected using TCP/IP via Ethernet cards. It is recommended that Hot Backup transmissions use a different network card than the card used for normal user traffic.
Software Requirements
The servers involved in a Hot Backup configuration must be running the same base release of D3, and must be patched to the same level with the latest public patches from TigerLogic.
Restrictions
These restrictions apply to Hot Backup implementations.
save Command
Special care must be taken when using the (k option of the save command in a Hot Backup implementation. Additionally, the queue on the master server should be empty. Enqueuing on the master should be stopped until the save completes. The (k option reorganizes all file-of-files numbers sequentially on the tape. To use the (k option of the save command, you must ensure that Hot Backup is stopped on both servers. Once Hot Backup is stopped, you must run the save with the (k option on both servers.
File-of-Files D-Pointer
If the D-Pointer for the file-of-files is not set to DX, it is possible that, following a restore, updates to the slave server may not update the correct files. Additionally, transaction processing performance may degrade. These problems occur because the process cannot correctly identify the file-of-files record. If the process cannot identify the file-of-files record, a temporary file (servername*file-offilenumber) is created in the data section of the hb.log file where servername is the Hot Backup server name and file-of-filenumber is the file-of-files number for the file concerned. These files are created with a modulo of 31, and thus can quickly fill up with data and overflow, resulting in performance degradation. To avoid this problem, set the D-Pointer for the file-of-files to DX and perform a file-save and restore.
Loading ABS Patches

WARNING If you are running a Hot Backup setup that logs all files, it is very important to shut down Hot Backup and to stop queuing updates when performing an ABS patch.
19
Configuring Hot Backup

There are four steps to configuring a Hot Backup implementation: Database Configuration Hot Backup Master Server Configuration Hot Backup Slave Server Configuration Synchronizing the Servers
20
Database Configuration
The database accounts and files to be backed up with a Hot Backup configuration must be specified. There are two options for this specification: All files in the database (Not Recommended) Select Accounts/Files in the database
It is recommended that you only log those files that need to be logged to the slave server. To specify the account and files to log, the D-Pointers on these accounts and files must be changed using the set-dptr command. Various attribute types can be set and unset using the set-dptr command. The L attribute instructs the database to log the file. To turn the logging attribute on for an account: 1. Enter: set-dptr +L accountname (A where accountname is the name of the account. The example below illustrates running the set-dptr command on the hbtest account. Attribute 1 in all D-Pointers in the hbtest account is changed from D to DL for both dictionary and data levels. set-dptr +L hbtest Selecting files in 'hbtest' ... hbtest bp bp hbdata hbdata 5 file(s) changed (A account : : : : : D D D D D > > > > > DL DL DL DL DL
NOTE
The set-dptr command changes any item in the MD or dictionary level of a file whose attribute 1 value starts with a D. The (d option of the set-dptr command (when used with the +l attribute) ensures that newly logged files are synchronized with the Hot Backup slave or a Transaction Log tape.
To change multiple accounts, you can: or build a list containing the account names that you wish to process and run the set-dptr command on the active select-list. For example: :get-list acclist >set-dptr +L (A run the set-dptr command on each account.
21
The example below illustrates the set-dptr command working with an active select-list containing file names. List 'filelist' in file 'pointer-file' saved. :get-list filelist [404] 9 items selected out set-dptr +L (P data5 : D > data5 : D > data6 : D > data6 : D > data7 : D > data7 : D > data8 : D > data8 : D > bp : D > bp : D > hbdata : D > hbdata : D > data2 : D > data2 : D > data3 : D > data3 : D > data4 : D > data4 : D > 18 file(s) changed :_ of 1 items. DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL
22
Hot Backup Master Server Configuration

In order to run Hot Backup, the master server must be defined. The hot-backup utility is used for this purpose and can be run from the dm or another account. To configure the Hot Backup Master Server: 1. Log on to the dm account. 2. Run Hot Backup. Enter: hot-backup The Setup Server menu displays. NOTE This screen displays when no Hot Backup servers have been defined. If servers are defined, the Hot Backup Main Menu displays.
3. Press ENTER to begin the server configuration. The Setup Server utility displays.
4. Enter the appropriate value for each of these fields: Server Name Name for the master server. Can be any alphabetical string up to eight characters.
23
Server Type
Specifies whether the server is to be the Master or the Slave server. M = master S = slave
Type M for master. Remote Host name Name of the UNIX host where the associated slave server is located. Can also be the IP address of the remote host. NOTETo ensure that you use the correct host name or IP address, use the UNIX ping command from a UNIX prompt to ensure that you can communicate with the remote host. For example: ping [hostname|IP Address] TCP port number TCP port number, from 1024 to 32767, of the associated slave server. The default is 2000. NOTEUse the UNIX netstat command to locate a free port number. The required options for netstat are different per UNIX platform. Please consult the UNIX documentation for your system to obtain the correct options. Target VME name Protocol Log slave update Check period Name of the VME server on the slave machine. inet. Cannot be modified. For slave servers only. For master servers only. The master server routinely performs a variety of system tests. This value represents the time (in seconds) to wait between tests. For example, if set to 60, a test record is sent every 60 seconds to the slave server to ensure that the link is functioning. If no response is returned from the slave server, an error is reported. A value of 0 disables all tests. A period of 300 seconds (5 minutes) is suitable for most systems. For master servers only. Time (in seconds) the master server waits (after emptying the transaction log queue) to restart the process of emptying the transaction log queue again. A value of two or three seconds is suitable. List of D3 users (as defined in the D3 users file) or D3 port numbers to notify in case of error, separated by commas. The port numbers are expressed in a syntax similar to the TCL command msg. For example, to notify the users dm and bob, and line 0 (regardless of whether it is logged on): dm,bob,!0 Apply updates Auto create Comments For slave servers only. For slave servers only. Any comments.
TxLog timer
Notify list
24
5. Type Y to confirm your changes. NOTE You can also type N to return to the above menu to make additional changes, or Q to quit without saving your changes.
The Transaction Log menu displays.
6. (Optional) To limit the amount of free frames (the default is unlimited) to allocate to the transaction logger for processing record updates, select the Set Queue Limit option from the Transaction Log menu, then enter the new limit in frames. NOTE This value must be reset after a full restore (a full restore automatically sets the value to unlimited).
7. Type X to exit to TCL. The master server is configured.
25
Hot Backup Slave Server Configuration

The slave server must be defined. The hot-backup utility is used for this purpose and can be run from the dm or another account. To configure the Hot Backup Slave Server: 1. Log on to the dm account. 2. Run Hot Backup. Enter: hot-backup The Hot Backup Main Menu displays.
3. Select the Special Operations option. The Special Operations menu displays.
4. Select the Setup Server option. The Setup Server menu displays (on the right side of the screen).
26
5. Select the New Server option. The Setup Server utility displays (on the right side of the screen). This is the same menu that was used when creating the master server.
6. Enter the appropriate value for each of these fields: Server Name Server Type Name for the slave server. Can be any alphabetical string up to eight characters. Specifies whether the server is to be the Master or the Slave server. M = master S = slave
Type S for slave. Remote Host name TCP port number For master servers only. TCP port number, from 1024 to 32767, of the associated slave server. The default is 2000. NOTEThis should be the same port number defined on the master server. Target VME name Protocol Log slave update For master servers only. inet. Cannot be modified. This option is for Hot Backup implementations that employ multiple cascading servers. If set to ON, all updates received by the slave are logged in the transaction log queue, to be sent to another system. If set to OFF (default), the updates are not enqueued. For master servers only. For master servers only.
Check period TxLog timer
27
Notify list
List of D3 users (as defined in the D3 users file) or D3 port numbers to notify in case of error, separated by commas. The port numbers are expressed in a syntax similar to the TCL command msg. For example, to notify the users dm and bob, and line 0 (regardless of whether it is logged on): dm,bob,!0
Apply updates
Instructs the slave server to apply the updates it receives from the master server immediately (ON) or delay them (OFF) until it receives an explicit command. Normally, this option should be set to ON. NOTEWhen the slave server starts, it reports the status of this option. Applying updates should not be disabled long, since the slave and master databases can be become out-of-sync when updates are not applied.
Auto create
Automatically creates any missing accounts and files on the slave server. NOTEIt is a good precaution to leave this option set to ON.
Comments
Any comments.
7. Type Y to confirm your changes. NOTE You can also type N to return to the above menu to make additional changes, or Q to quit without saving your changes.
The slave server is configured.
28
Synchronizing the Servers

Before running Hot Backup, you must synchronize the master and slave servers. To synchronize the servers: 1. Perform a full file-save on the master server. 2. Load the save onto the slave server. The servers are synchronized.
29
Starting Hot Backup

This section contains instructions for: Starting the Master Server Starting the Slave Server Testing the Servers Testing D3 Processes WARNING It is very important that Hot Backup is started as the dm user. If not, Hot Backup could fail under certain conditions and drop into the debugger or log itself off.
30
Starting the Master Server

Complete these instructions to start the master server. WARNING Although safeguards exist to avoid such a situation, it is very important that a master server is not started when there is a master server already running. This can lead to corruption of the transaction queue. Use the test in Testing the Servers to verify whether or not the process is already running. If you have any doubts, contact TigerLogic Customer Support for further assistance.
To start the master server: 1. Log on to the dm account on the master server. 2. At TCL, enter: hot-backup 3. If multiple servers are defined, select the server to start, then press ENTER. The Hot Backup Main Menu displays. 4. Select the Start Server option. 5. Select Yes when prompted for confirmation. The master server process starts.
31
Starting the Slave Server

Complete these instructions to start the slave server. To start the slave server: 1. Log on to the dm account on the slave server. 2. At TCL, enter: hot-backup 3. If multiple servers have been defined, select the server to start, then press ENTER. The Hot Backup Main Menu displays. 4. Select the Start Server option. 5. Select Yes when prompted for confirmation. The slave server process starts.
32
Testing the Servers

Use the procedure below from the master server to confirm that a server is running. To confirm that a server is running: 1. Log on to the dm account on the server to test. 2. At TCL, enter: hot-backup 3. If multiple servers are defined, select the server to test, then press ENTER. The Hot Backup Main Menu displays. 4. Select the Query Server option. A message displays confirming whether or not the server is running. The example below illustrates a confirmation that the hbslave server is running:
33
Testing D3 Processes
Use the procedure below to verify that D3 processes are running. To verify D3 processes are running: 1. Verify on which line the spooler process is running. At TCL, enter: !cat /usr/lib/pick/pick0 | grep npibs The number of PIBs (ports) defined to D3 displays. npibs 16 In the example above, 16 PIBs (PIBs 0 to 15) are defined. Thus, the spooler process is on line 16. The Hot Backup process starts on the last available PIB on the system. Therefore, in this example, the Hot Backup process runs on PIB 15. 2. Confirm the processes by entering the PIB numbers. Enter: where 15-16
NOTE
The above command is for this specific example. If, for example, 32 PIBs are defined, enter instead. where 31-3 2
The where command statistics for the specified PIBs display. :where 15-16 Ln PCB PIB 06 Mar 2004 FID Stat 0015 0000072F FF10 0016 00000730 BF10 sp.spoolout:086 ABS Stat P R1 & Return stack contents 12:50:09
Base 000018 000018
br.unix.bix:000 sleepsubx:062 sp.sleep:035
The example above confirms that the Hot Backup process is running on PIB 15. The P displayed in the Stat column indicates it is running as a phantom process.
34
Using Hot Backup

These topics are discussed in this section: Navigating Hot Backup Menus Server Selection Main Menu Special Operations Menu Transaction Log Menu Setup Server Utility Querying Servers Additional Information
35
Navigating Hot Backup Menus

Hot-Backup menus are divided in two sections: TIP Menu section, where menu options display. Message section, where results, messages, or help display. When moving the cursor to a new field, a short help message displays in the message section.
All Hot Backup operations are controlled through menus. If your terminal allows, use arrow keys where indicated. Otherwise, use these keys and key-combinations to move through the menus: CTRL+N CTRL+B CTRL+X Moves cursor down (down arrow). Moves cursor up (up arrow). Cancels. Applicable only when input is requested.
Use these keys to quit or exit Hot Backup or Hot Backup menus: ESC Q X Quits and returns to previous menu or back to TCL. This key also terminates all menus. Quits and returns to previous menu. Exits and returns to TCL from any menu.
36
Server Selection
If there is more than one server defined in Hot Backup, the Select a Current Server menu displays when first entering Hot Backup:
After making a selection, the Hot Backup Main Menu displays. Note that the current server name displays at the top of the screen. To select another current server, press ESC or Q to return to the server selection menu.
37
Main Menu
The Hot Backup Main Menu provides the ability to start and stop a server, display various statistics, and open other Hot Backup menus.
Menu Status
Description Displays the last messages displayed by the selected server. The title of the message section on the screen indicates the server name and additional information. The messages display in reverse chronological order (most recent first). The server does not need to be running to use this command. Queries the selected server. The server must be running. See Querying Servers for more information. Starts the selected server. NOTEDuring a coldstart, D3 automatically starts the last Hot Backup server that was started before the coldstart.
Query Server Start Server
Stop Server Show Server Show statistics
Stops the selected server. Displays the current configuration of the selected server. Type Y to return to the Hot Backup Main Menu. Displays transaction statistics. Both servers must be running. If run on the slave server, the result displays immediately. If run on the master server, a request is sent to the slave server, and statistics display later. The response time depends on how busy the slave server is. The slave server accumulates the statistics. Statistics are cleared with each slave server restart. NOTEYou can use this option from the master server to determine whether communication is established.
38
Display queue
For master servers only. Displays the status of the transaction log queue. The information below displays: Number of frames in queue. This is a rough indication of the amount of data not yet transmitted. Whether the system is set up to log all files or only DL files. Whether file updates are enqueued for all processes. Current transaction number being transmitted, if nonzero. Last acknowledged transaction number. This is the last transaction that was received and successfully processed by the associated slave server. If the last ACK number is not reported, the query was performed at a moment when all transactions are acknowledged. First transaction not yet acknowledged by the associated server. This can be an update item, a delete item, and so on. In case of a problem, this is the first transaction that is retransmitted.
Special Operations Transaction log menu
Opens the Special Operations Menu which allows you to perform miscellaneous operations such as setting up traces, servers, permanent log files, and applying updates. Opens the Transaction Log Menu which allows you to perform several transaction log operations.
39
Special Operations Menu

The Special Operations menu provides the ability to turn traces on or off, create or configure and delete servers, display various statistics, and start and stop the application of updates to the slave. To enter this menu, select the Special Operations option from the Hot Backup Main Menu.
Menu Option Status
Description Displays the last messages displayed by the selected server. The title of the message section on the screen indicates the server name and additional information. Messages display in reverse chronological order (most recent first). The server does not need to be running to use this command. Turns traces ON for debugging purposes on the selected server. Traces can considerably slow server performance and should set to OFF in normal operations. Disables traces on the selected server. Opens the Setup Server Utility which allows you to create or edit a Hot Backup server. Deletes the selected server definition. If more than one server exists, the list of available servers displays. Lists the permanent log of all messages logged by all servers. These keystrokes allow you to navigate the log: CTRL+N to scroll forward through the logs CTRL+B to scroll backward through the logs T to jump to the top of the log B to jump to the bottom of the log : to enter a special command line that allows searching for the first log entry entered after a given date or time, and searching for a string Q or ESC to return to the Special Operations menu
Turn traces ON Turn traces OFF Setup server Delete Server List permanent log
40
Clear Permanent log
Clears the permanent log file. Three clear options are available: 1 Clear all entries 2 Clear entries older than 1 week 3 Clear entries older than 1 month
Stop Applying Updates
For slave servers only. Instructs the selected server to stop applying updates coming from its associated master server, and instead stores the updates in the hb.log,apply temporary hold file. Selecting this option also updates the server configuration. Thus, the next time the server is started, updates are not applied. To display the number of pending updates, select the Query Server option from the Hot Backup Main Menu. To re-apply updates, select the (Re)start applying updates option. NOTEIf Hot Backup is not running from the dm account, the apply data level must be created in the hb.log file in the dm account on both the master and slave servers before using this option. To create the apply data level, enter the command below in the dm account at TCL: create-file hb.log,apply 301 (x
(Re)Start Applying Updates Close opened files
For slave servers only. Applies any pending updates to the database and restarts the normal state of applying new updates as they arrive. Selecting this option also updates the server configuration. Thus, the next time the server is started, updates are applied. For slave servers only. If it becomes necessary to delete a file on the slave server (for example, after recovering from a missing file-of-files item on the master server (see the error message Cannot read FOF item)), the slave server must be instructed to close all the files it opened. If the files are accessed again, the slave server reopens them.
41
Transaction Log Menu

Use the Transaction Log menu on a master system to control what and how updates transmit to the associated slave server. To enter this menu, select the Transaction Log Menu option from the Hot backup Main Menu.
Menu Option Display queue Log DL files only Log ALL files
Description Displays the status of the transaction log queue. This option is the same as the Display queue option in the Hot Backup Main Menu. Specifies to log only those files that contain a DL attribute in their D-Pointer. This option is applied to the entire system. Specifies to log all files on the system. Not recommended. NOTEAfter a full file-restore, the logging of files is automatically changed to DL type files only (even when the Log All files option is enabled). To re-instate, add the startlog (eo command to the user-coldstart macro to initiate the logging of all files during startup. NOTEThe slave server does not apply any modifications to selected files in the dm account on the slave server: ABS, accounts, alarm.file, backgrounds, devs, errors, file-of-files file, hb.log (Hot Backup control files), jobs, PIBs, resizing, and tcl-stack. NOTEIf the T flag is removed from the tcl-stack data-level D-Pointer, the logging of updates depends on the compatibility mode. For AP compatibility, updates from TCL are not logged (only updates from other channels, such as BASIC programs, are logged). For nonAP compatibility, updates from TCL and from other channels are logged
However, changes to the tcl-stack made from standard update channels are logged. CAUTIONUse this option with caution, since the slave server can create accounts and files to receive data. Stop enqueuing Stops enqueuing updates. NOTEThis option should be used with extreme care. If selected, updates to the master database do not transmit to the slave server. The only legitimate use of this option is to stop enqueuing updates following a major problem on the master server that requires switching users to the slave server. This event is logged in the errors file.
42
Start enqueueing Clear Log Queue Set Queue Limit
Starts (or restarts) enqueuing updates. This event is logged in the errors file. Clears the transaction log queue. All queued updates are lost. This event is logged in the errors file. Allows you to specify the amount of free frames the transaction logger uses to record updates. The default is unlimited. NOTEThis value must be reset after a full restore (a full restore automatically sets the value to unlimited). NOTEA warning is sent when the queue size exceeds 50% of the specified value and the enqueueing of updates is disabled when it reaches the specified queue limit. The queue size is checked at the frequency set in the Check Period value (specified in the master server configuration). If the queue size exceeds the specified limit between checks (and subsequently diminishes prior to the next scheduled check), no warning is sent.
43
Setup Server Utility

The Setup Server utility displays automatically the first time Hot Backup is installed, or by selecting the Setup Server option from the Special Operations menu. This utility creates and configures servers.
Field Server Name Server Type
Description Name for the server. This name references the server in all the other menus. If there is only one server defined on the D3 virtual machine, this server is implied in all commands. Specifies whether the server is to be the master or the slave server. m = master s = slave
Remote Host name
Name of the UNIX host where the associated slave server is located. Can also be the IP address of the remote host. The master and slave servers should both be set to the same value. NOTETo ensure that you use the correct host name or IP address, use the UNIX ping command from a UNIX prompt to ensure that you can communicate with the remote host. For example: ping [hostname|IP Address]
TCP port number
For a slave server, TCP port number, from 1024 to 32767, on which it is listening. For a master server, TCP port number of the associated slave server.
NOTEYou can use the UNIX netstat command to locate a free port number. The required options for netstat are different per UNIX platform. Please consult the UNIX documentation for your system to obtain the correct options. Target VME name Protocol For master servers only. Name of the VME server on the slave machine. inet. Cannot be modified.
44
Log slave update
For slave servers only. This option is for Hot Backup implementations that include multiple cascading servers. If set to ON, all updates the slave receives are logged in the transaction log queue, to be sent to another system. If set to OFF, the updates are not enqueued. The default is OFF. For master servers only. The master server routinely performs a variety of system tests. This value represents the time (in seconds) to wait between tests. For example, if set to 60, a test record is sent every 60 seconds to the slave server to ensure the link is functioning. If no response returns from the slave server, it reports an error. A value of 0 disables all tests. A period of 300 seconds (5 minutes) is suitable for most systems. For master servers only. Time (in seconds) the master server waits (after emptying the transaction log queue) to restart the process of emptying the transaction log queue again. A value of two or three seconds is suitable. List of D3 users (as defined in the D3 users file) or D3 port numbers to notify in case of error, separated by commas. The port numbers are expressed in a syntax similar to the TCL command msg. For example, to notify the users dm and bob, and line 0 (regardless of whether it is logged on): dm,bob,!0
Check period
TxLog timer Notify list
Apply updates
For slave servers only. Instructs the slave server to apply the updates it receives from the master server immediately (ON) or delay them (OFF) until it receives an explicit command. Normally, this option should be set to ON. NOTEWhen the slave server starts, it reports the status of this option. Applying updates should not be disabled long, since the slave and master databases can be become out-of-sync when updates are not applied.
Auto create
For slave servers only. Automatically creates any missing accounts and files on the slave server. NOTEIt is a good precaution to leave this option set to ON.
Comments
Any comments.
45
Querying Servers
This information displays when running the Query Server option from the Hot Backup Main Menu. Note that the message format may differ depending upon whether this option is run on the master or the slave server: Server 'hbslave'. PIB 14. PID 40774. Server type Slave. Traces OFF Total Recvd O K. Cur trans 1. ACK'ed trans 1. Updates applied Status: Reading network
Name of the server. D3 port number of the server (PIB). UNIX process ID of the server (PID). For slave servers only. Current transaction number received by the slave server. This number should increase as data is exchanged between the servers. Current transaction number successfully acknowledged by the slave server. Unless the queue is empty, the acknowledged transaction number should be slightly less than the transaction number received by the slave. For slave servers only. Indication of whether updates received from the master server have been applied to the slave database. Total size, in kilobytes, received for the current day. The master reports a slightly higher number than the slave, due to additional protocol information. For slave servers only. Indication of whether the slave server received requests to open files and was not able to do so. The number of files that do not open displays. At any given time, there may be a few pending open files, so repeat the command to verify whether or not problems exist. Examine the permanent log file to obtain more information. For slave servers only. Indication of whether updates to the slave database are currently disabled, and the number of pending updates. Server status Possible status value: Reading network Wait response to call Wait incoming call Stopped Connected Normal state of the slave server. For master servers only. Master server is attempting to call its associated slave. For slave servers only. Slave server is waiting for its associated master server to establish communication. Server has stopped. The previous message in the status or permanent log file indicates the reason for the termination. Indicates that a connection is established.
46
Writing to network
Sending data to the associated server. If this state persists and no data transfer occurs, this indicates that the receiver is not reading data. A 30-second time-out occurs, after which the connection is shut down and restarted. For master servers only. Waits for an acknowledgment from the associated slave server. For master servers only. Queue is empty and there is no traffic. For master servers only. Intermediate state while the master server is extracting messages from the transaction log queue.
Waiting for ACK Idle Reading queue
NOTE
Additional information on the slave server is available in the hb.log,stats file. The item datetime.pib, where datetime is the date and time when the server was last started, and pib is server on which it is running, contains statistics for number of updates, deletes, file creates, file deletes, file clears, file renames, index creates, index deletes and index clears since the last server start.
47
Additional Information
Resizing Files Online D3 files can be resized using the on-line file resizing utility on the master server. The files are resized on both the master and slave server. D-Pointer Controls To write data to files, the slave server performs controls on the file-defining D-Pointers located on the slave server. The slave server does not automatically change the file-defining D-Pointers. Some of the controls the slave server performs include: Update protections are removed to ensure that the slave server is able to write to the file. callx correlatives are changed to use explicit path names to the subroutines. The account and file name where the subroutine resides is found in the cataloged object in the master dictionary of the account where the file is located. If the subroutine is not found, the callx correlative is removed. Bridges to other files are controlled to use an explicit path name to the target file. If the file cannot be found, the bridge is removed. The amount of control is limited. For example, references to files in FlashBASIC and a correlatives are not controlled. Therefore, if precautions are not taken, it is possible that the slave server will abort trying to update such a file. Note that no data loss occurs because the offending transaction acknowledges and retransmits. Starting the server with the traces feature set to ON identifies which items and files cause the problem.
CAUTION
lost+found File When a slave server is unable to process a transaction (for example, the account does not exist and the automatic creation of missing accounts is disabled), the transaction is stored in the hb.log,lost+found trash file. The item-IDs of these files are unique timedate stamps. This file can be used to recover the salvaged data. The format of an item is:
48
Item type. Can be one of these: Unknown transaction code. Slave server was reset. Internal error. Time out on transaction can occur when stopping the master server. Bad network message. Cannot perform the operation. An error message usually indicates the cause of the problem. Cannot update D-Pointer. There is a D-Pointer-like element in the master dictionary or file dictionary preventing the creation of the file. This item was deleted to allow the file creation and its content written starting at the attribute 10. Master dictionary of the account in which the slave server is running (for example, dm) contains an item that collides with the name of an account. Though this is normally authorized, this is not a good practice. The server removes this item and dumps the content of this item. Slave server removed a correlative from a D-Pointer because it could not resolve a reference to a callx subroutine or to a bridge. The lost+found item contains the removed correlative. Transaction could not be processed when applying delayed updates. Incorrect transaction length.
Transaction opcode, if applicable, or question mark. Server name. Log internal time. Log internal date. Transaction number. Last ACK transaction number. Message. Time and date in external format. Body of the transaction that could not be processed or any data the server could not handle, in hexadecimal.
NOTE
The data in the lost+found item may be incomplete.
49
Hot Backup Errors

This topic lists the main error or warning messages that either display in the message section of the Hot Backup menus or log to the permanent log file. Error ERROR: This command applies only to Slave servers Not a phantom. Running on PIB xxx. PID yyy Terminated abnormally Notice from server servername Waiting for server servername to start Waiting for server servername to initialize FAILED: Cannot start phantom process FAILED: Server servername encountered an error and stopped Description Command can only be performed against the slave server. Certain functions cannot be performed by master servers. Displays when interrogating a server which is either started in foreground (for debugging purpose) or, more likely, which has aborted, or was killed, leaving an inconsistent status in the jobs file. Server phantom process has terminated without finishing properly. The process was probably logged off, or encountered a fatal error. Signifies that the message in the message section of the Hot Backup menu is coming from the specified server. Waiting for the phantom process to start.
Phantom process started and is waiting for the server to initialize itself.
Phantom process failed to start. Check the scheduler to verify there are not too many queued jobs and use list-jobs to determine the cause of the abort. Phantom process started normally, but the server could not complete its initialization. Use the status option from the Hot Backup Main Menu to verify the cause of the failure. The most common cause is a BIND error, indicating that the TCP port is already in use. Often, when stopping a server, the TCP connection is not purged immediately and the TCP port remains in use. This usually cleans itself up after the various TCP protocol time outs have expired. Stop the master server and re-attempt a few minutes later. If the BIND error persists, change the port number using the Setup Server option from the Special Operations menu in Hot Backup. The port must be changed on both the master and the slave servers. A start server failed because the server appears to be already running. This has no action on a running server. If the server is not running, and this message continues to display, this might indicate a corruption of the Hot Backup control file. Make sure the server is not running (using the where command) and run: delete hb.log servername
WARNING: Server servername is already running on PIB xxx
50
WARNING: Transactions are not enqueued WARNING: Transaction queue has grown to xxx frames malloc error. err=xxx
Issued by the master server to indicate that updates to the database are not being enqueued, and therefore are not being transferred to the slave server. The databases are now out of sync. Periodically, the master server checks if the queue has grown to more than 500 frames above the previous value, indicating that the slave server is not able to keep up with the load. Ensure that the input server is not stopped, or has not aborted. This message may be normal in situations where massive updates are performed. System could not allocate memory. WARNINGThis is an indication of a serious UNIX problem. Check the swap space. Master server cannot establish a communication. The error code is implementation dependent. Ensure that the host is available by using the UNIX command ping hostname. If available, the most likely reason is that the slave server has encountered an error or is not started. Use the status option from the Hot Backup Main Menu on the slave server to verify. Due to a corruption in the file-of-files file on the master server, the system is unable to identify the file being updated. 'xxx' is the file number (as known on the master server). Data is normally transferred to the slave server, but stored in a temporary hold file named hb.missing,master.name*xxx, where master.name is the name of the master server, and xxx the file number. To correct this situation, rebuild the file-of-files file on the master server by performing a full file-save (possibly a dummy save), with the (s option. The missing file-of-files file item can also be rebuilt manually if the file name can be identified from the content of the file being stored in the temporary hold file on the backup system. The data can then be copied to the real file. Instruct the slave server to close its opened files using the Close opened files option from the Special Operation menu to force it to open the new file.
Cannot call host hostname. Errno=xxx
Cannot read FOF item xxx
51
D3 Configuration File Tape Statements

Information specific to the tape portion of the D3 configuration file, typically pick0, is discussed here. For a complete explanation of the pick0 configuration, see the D3 Reference Manual. Tape statements define the tape devices available for use by the D3 virtual machine. Tape devices are numbered (for use in the set-device and other commands) starting at 0 (zero) from the top of the list. The first device in the list is the default device. tape tape tape tape tape tape tape tape tape /dev/fd0H1440 500 f lq #3.5 floppy 1.44M high density /dev/fd0H720 500 f ld #3.5 floppy 720K low density /dev/nst(x) 16384 q lh #SCT high density /dev/nst(x) 16384 q ls #SCT low density /dev/nst(x) 16384 v l #8mm tape /dev/nst(x) 16384 d 1 #4mm tape /home/tmp/floppy 500 f lx #temporary floppy device /dev/pipein 500 c lx #data in/out from/to 'some other source' /tmp/pseudo 1000000 p lx #compressed pseudo tape
Parameter First Second
Description Tape. UNIX file path of the tape device. This device must already exist (with any drivers already loaded) for D3 to properly use the device. The device paths listed above are examples only; your device paths can be different. Note that these file paths refer to the no rewind devices, which are required for all D3 tape devices. For example, tape /dev/pipein where the device code = c. Block size of the device. NOTEThird parameter no longer serves a useful purpose, other than marking a space during parsing of the configuration file, and is required. The exception is the compressed pseudo tape device. The block size is set according to these conventions: For floppy devices, this is usually 500. For half inch tape devices, this is usually 4096 or 8192. For other tape devices, this is usually 16384.
Third
The block size is used only for compressed pseudo tape devices. It contains the number of 1 KB (1024 byte) blocks to write prior to compression before the file is closed and the tape operation cascades to a new file. If this number is less than 1000, the device does not cascade and may run into UNIX file size limitations. Fourth Specifies the type of tape (magnetic media) device code. Valid types are: f q d Floppy disk or uncompressed pseudo tape Quarter-inch streaming tape 4mm digital tape
52
v h c p Fifth
8mm digital tape Half-inch tape No rewind device (pipe) Compressed pseudo tape (cascading)
Specifies the read/write density of the device. Device q d v h Default Density l l l l Low Density ld . . ld Medium Density . . . lm High Density lh lh lh lh
The above device type parameters are ignored by the system and used as a place marker. c f (floppy) p, f (pseudo) lx lx lx . ld . . . . . lq .
53
Peripherals
This section provides information to set up different D3 peripheral devices after installation. The following topics are discussed: Disks Printers Tapes
54
Disks
Review the information below regarding disks.
SCSI Disks
SCSI disk names depend on the particular controller used and the SCSI ID of the disk. For most controllers, the name is ordered according to either ascending SCSI ID or descending SCSI ID. The name of a SCSI disk is /dev/sd x where x can be a, b, c, d, e, f, g, /dev/sda would be the first SCSI disk, /dev/sdb would be the second SCSI disk, and so on. SCSI disks share the same naming structure for partitions as all other disks.
(E)IDE
(E)IDE disk names depend on their location and configuration (Master or Slave) on the (E)IDE bus. Unlike SCSI devices, (E)IDE disk names are shared with (E)IDE CD-ROM devices. /dev/hda /dev/hdb /dev/hdc /dev/hdd The master on the first IDE bus. The slave on the first IDE bus. The master on the second IDE bus. The slave on the second IDE bus.
Partition Names
The partition naming scheme is the name of the disk, with a suffix designating the partition. The first 4 partitions are the primary or extended partitions and any partition number greater than 5 is an extended partition. So, /dev/hda1 would be the first partition on the master hard drive on the first IDE bus.
Floppy Disks
Writing to a Floppy Disk
The UNIX designation of the floppy disk in Linux is /dev/fd0H1440. This is a 1.44 MB floppy disk drive.
Device is write-protected
When Linux is installed, the permissions are set to 660 for the 3.5 inch 1.44 floppy device /dev/fd0H1440 and for the tape device /dev/nst0. Because the user pick is not a root user, the permissions are not sufficient for D3. As a result, when a D3 process attempts to write to the floppy, a message displays indicating that the drive is write-protected. To write to the device from D3 execute the command:
55
If using floppy: chmod 666 /dev/fd0H1440 If using tape: chmod 666 /dev/nst0
WARNING
When writing to a floppy disk (for example, if you are performing an account-save or a t-dump), you must execute either the t-det (detach the tape) or t-rew (rewind the tape) command and wait for the device light to turn off before removing the floppy disk from the device. The floppy device may not clear the last buffer if one of the two commands is not executed. Consequently, some of the data may not be written to the floppy disk.
56
Printers
The following topics are presented: D3 Printers Reserved Printers Shared Printers
57
D3 Printers
For a D3 virtual machine, all printers are treated as serial printers, even if they are parallel. The difference is handled transparently by UNIX. Therefore, the D3 startptr command must always use the s printer type, and never use the p printer type.
58
Reserved Printers
A reserved printer is a printer to which only D3 can print. A printer can be attached to a serial or parallel port and reserved for a D3 virtual machine. Reserved printers are managed by the D3 spooler which submits jobs to D3 printer processes serving specified form queues. A reserved printer can be defined and started in a user-defined macro called user-coldstart in the dm account. This macro is used automatically during a coldstart or the normal boot process.
Adding a Reserved Printer

Complete these instructions to add a reserved printer. Parallel Port When starting the system, the parallel printer must be online. 1. Log on to D3. Enter user-ID dm and master dictionary dm. 2. Select an unused D3 line number on which to start the printer. In the example below, for a 128 user system, the last line number (127) is used. 3. Insert the statements below in the user-coldstart macro in the master dictionary of the dm account. !exec d3 -127 -t lp0 -pprinter & startptr 0,0,0,s127
NOTE
If no items have been previously placed in the user-coldstart, it opens as a new item.
In this example, theLinuxparallel printer device name is /dev/lp0. NOTE The options to the TCL startptr command, such as the form queue number, printer number, and so on may vary.
Serial Port 1. Log on to D3, then enter user-ID dm and master dictionary dm. 2. Select any unused D3 line number on which to start the printer. In the example below, for a 128 user system, the last line number (127) is used. 3. Insert the statements below in the user-coldstart macro in the master dictionary of the dm account. Note that the options to the startptr TCL command, such as the form queue number, printer number, and so on may vary. !exec d3 -127 -t ttyxx startptr 0,0,0,s127 -printer &
These statements define a serial printer on line 127 that is associated with /dev/ttyxx with a baud rate of 9600 (the default). The first line describes the printer port for UNIX. UNIX will start a D3 process (D3 PIB 127) on ttyxx.
59
The second line describes the printer for D3. D3 will start printer 0, use D3 spooler form queue 0, with 0 page ejects on serial line (D3 PIB) 127. Note that the printer number and output queue number are set to zero.
Removing a Reserved Printer

The D3 command sp-kill returns the serial (or parallel) port to a user process state. To allow UNIX to use the printer attached to this port, the D3 process using it must be killed. To kill the process: 1. Log on to D3 and enter user-ID dm and master dictionary dm. 2. Type: sp-kill dprinter.number kill pport.number These commands kill the UNIX process associated to the printer on port port.number.
60
Shared Printers
A printer can be shared between UNIX and D3, so that both D3 and UNIX users can access it transparently. On a D3 virtual machine, both shared and reserved printers can coexist. This approach allows users to take advantage of D3 spooler features like alignment, hold files, and multiple copies, while still utilizing the UNIX spooler for final output. If such D3 spooler functionality is not required, it is possible to spool data directly to the UNIX spooler bypassing the D3 printer processor altogether. The general principle of a shared printer consisting of a system with one reserved printer, two shared printers, and a remote printer is shown in the next figure. Shared printers look the same as reserved printers to D3 users; they are managed by the D3 spooler which submits jobs to D3 printer processes serving specified form queues. Instead of sending the output directly to a device, as is the case for reserved printers, the shared printer process output is redirected to a filter which interfaces to UNIX and sends the job to the UNIX spooler. Another difference is that spooling out of the virtual machine is nearly instantaneous since the filter writes the print job to a UNIX print file. It is almost impossible to use sp-kill to cancel a job from D3; it must be performed using the UNIX cancel command. The association between the D3 form queue and the printer follows these rules: A form queue is associated to a printer process. A D3 printer process is associated to a filter when the shared printer is started. A filter is associated to one UNIX queue. A UNIX queue is serviced by one or more printers.
This mechanism is controlled by the TCL startshp command.
61
The following topics are presented: Adding and Removing Shared Printers Troubleshooting
62
Adding and Removing Shared Printers

This topic presents instructions for: Adding a Shared Printer Removing a Shared Printer Adding a Shared Printer When adding a shared printer, watch for these caveats: Test the UNIX printer command to verify that the /etc/inittab file went to a specific printer, for example: lpr -Pprinter19 /etc/inittab Before issuing the startshp2 command, type the command: pid {port#} The PID should be 0 (zero) and nothing should be started on that port yet. Make sure port# is a real, usable port not a phantom PIB. The port# must be a port number less than the spooler port number. Always use lp.unix as the form queue device name because that device is what appends the text End of Job to each D3 spooler job. The End of Job text tells the lppick daemon when to route the job to the proper UNIX print queue, the same UNIX print queue tested in Step 1 above. NOTE If the UNIX print queue is the default UNIX print queue (for example, you can type lpr /etc/inittab), the lpr... argument is not needed in the startshp command.
Printer should start successfully after the startshp command is issued. Typing pid {port#} should return a process ID. Shared printers must specify a device name for the printer. lp.unix (located in the file devices in the account dm) is provided for simple ASCII printers. The purpose of this form queue is to define an inter-job sequence that the filter uses to cut the D3 printer process data stream into UNIX print jobs. The inter-job sequence is defined as function @(-269).
To add a shared printer: 1. Ensure that the UNIX spooler is started and at least one UNIX queue is started. Type: lpc status 2. Ensure that the printer works with UNIX. For example, type: lpr -P[unix.formqueue.name] unix.file.name When the unix.file.name prints on the printer, the printer is shared in UNIX and is ready to be shared in D3.
63
3. Insert these statements in the user-coldstart macro in the dm account: startshp 1,1,0,s126,lp.unix startshp 2,2,0,s127,lp.unix,(lpr -Plp1) These statements use the previous example to show how two shared printers are set up. First statement starts the printer on the shared printer servicing the default UNIX queue (lp0 in this example, which is the default). Second statement specifies a complete lpr command since the output is sent to the non-default UNIX queue.
The startshp command uses the syntax:
printer#,formqueue#,page.eject,S{port#},lp.unix,(lpr command)
where printer#,formqueue#,page.eject,S{port#} are all the same values as used with a regular startptr command. For more information, see the D3 Reference Manual. NOTE In UNIX, it is always a Serial (S) printer, and the port# must be less than npibs (never put a printer on D3 port 0).
The startshp command: Creates a process on port#. Assigns the form queue lp.unix to that shared printer. Sets up the routing of print jobs to whatever UNIX print command was specified.
To use a more complex printer definition item: 1. Locate the line containing =x in the item. This entry corresponds to @(-99). 2. Locate the line which should be associated to @(-269), 170 entries later. Note that a line starting with an exclamation mark is a comment and does not count. 3. Add the line: d,c'End of Job',< -269 4. Compile the form queue item, then enter: assignfq formqueue,device (c With this setting, the printer process sends an End of Job string between each job. The filter scans the data stream, looking for this inter-job sequence to separate the data into different UNIX print jobs. The inter-job sequence can be any character or sequence of characters that does not occur in a normal print job. NOTE It is strongly advised to include a nonprintable character in the inter-job sequence, such as: d,x'ff',c'End of Job',x'ff',< -269 Never use the TCL command startptr on a shared printer as it does not spawn the necessary filter process.
64
Removing a Shared Printer A shared printer can be stopped with the shp-kill command. This command executes an sp-kill of the D3 printer and kills the underlying D3 process and the filter.
65
Troubleshooting
Shared printers can be difficult to maintain because of the multiple processes that interact before the job is output. For this section, a shared printer had been previously started with the command startshp 3,1,0,s17,lp.unix. When a problem occurs, follow this troubleshooting list: 1. Verify that the UNIX queue is started by typing: lpc status The designated queue should display as Ready. 2. Verify the D3 printer status at TCL by typing: shp-status This command displays some information on the status of the D3 printer process and its associated filter. 3. Verify if there is a UNIX process started on the D3 line number at TCL by typing: pid line.number The result should display a nonzero PID. 4. Verify that the filter process is running by typing: ps aux | grep lppick The filter program and some of its options should display. 5. (Optional) Kill the shared printer by executing the steps below if the shared printer cannot be restarted after using shp-kill. startshp 3,1,0,s17,lp.unix a. Use the sp-kill command to kill the printer. sp-kill d3 b. Manually kill the UNIX printer process. kill p17 c. Remove the file /tmp/lppick. !rm /tmp/lppick/pick0_3_17 d. Restart the printer. 6. If any of these steps do not provide the expected result, try to restart the shared printer with the startshp command. NOTE The startshp command has some tracing facility. See the D3 Reference Manual for more details.
66
Tapes
Review this topic for more information on tapes.
Pseudo Tape Devices

Since pseudo tape devices are UNIX file names, specifying a separate UNIX file as a device provides the ability to read and write data to it at a high speed. Such uses can be: NOTE A copy of the ABS disks in a pseudo tape for fast reloading. High-speed file-save backups to a UNIX file. A serial device or network link for transmitting data to some other destination. The underscore character is a reserved character and is not valid in a pseudo tape device name.
Pseudo tape devices do not need to be compressed. For compressed pseudo tape devices, data is written compressed and read uncompressed using gzip utilities (to eliminate the 2 GB file size limitation on compressed tape devices). At user specified limits (before compression), the UNIX file name changes and cascades the pseudo tape device to the new file name. For example, given this tape definition in the pick0 configuration file: tape /tmp/pseudo 10000 p lx # compressed tape If a data save has more data than the limit specified (10,000 1024 byte blocks, on 10 MB), the device /tmp/pseudo is closed and the save cascades to /tmp/pseudo-1. After the second 10 MB is written, the device /tmp/pseudo-1 is closed and the save cascades to /tmp/pseudo-2. This process continues until the save is finished. NOTE There must be space in the UNIX file system, /tmp in this example, to store these compressed files.
Changing the Compression Method

Use the !SwitchZip.sh program to change your compression method (either Compress or Gzip). 1. Navigate to the /usr/lib/pick directory. For example: cd /usr/lib/pick 2. Run the SwitchZip.sh program. For example: !SwitchZip.sh The Choose compression method menu displays. 3. Select your compression method and press ENTER. The compression method is changed.
67
SCSI Tapes
SCSI tapes in D3 Linux all share the same naming convention regardless of type. Names prefixed with n refer to the non-rewinding version of the device, which will be used in D3 Linux. Device names use the format: /dev/nstN where N is a number. The mapping between the number and the actual tape drive depends on the SCSI ID and the SCSI controller used.
Multireel Saves
By default, D3 Linux does not support multireel saves. However, it can be configured to support multireel saves. If there is no intention to ever use multireel saves, do not enable this feature. Enabling multireel saves produces more wear on the tape. Multireel tape processing takes considerably longer than single-reel processing. NOTE The user must have root privileges and the D3 port must be started by entering d3 -0 l (lowercase L).
To enable multireel saves: 1. Insert the media into the drive. 2. Execute these commands from line 0 (the console) at TCL, where device.name is the UNIX device name listed in the TCL command: !mt -f device.name drvbuffer 0 !mt -f device.name stoptions 4 list-device This disables the internal buffers, ensuring reliable end-of-media detection. As such, it may reduce tape streaming. To restore the original state of tape operations: 1. Insert the media into the drive. 2. Execute these commands from line 0 (the console) at TCL, where device.name is the UNIX device name listed in the TCL command: !mt -f device.name drvbuffer 1 !mt -f device.name stoptions 7 list-device This re-enables drive buffering to assist streaming and reduce tape drive wear, but prevents reliable end-of-media detection.
4mm and 8mm Tape

To ensure proper operation of 4mm and 8mm tape devices, the block size of the drive must be set to variable block size mode. The variable block size mode setting is zero (0). After first setting the block size to the variable zero (0), you can change it to any size you choose.
68
However, when you change the block size to anything other than the variable zero (0), that change becomes the default block size for all other tape drives on the system. NOTE It is highly recommended that the default block size always be set to variable block size mode (0) because you can only perform a file restore when the block size is set to 0. In order to restore multireel tape saves, the block size should be set to variable block size mode (0).
Setting the Default Block Size for the Tape Drive

To use these methods you must ensure that there is not a tape in the drive. NOTE The user must have root privileges and the D3 port must be started by entering d3 -0 l (lowercase L).
There are three methods available to set the block size for a tape that is not in the tape drive. Method 1 Execute this command from the TCL prompt (or place the command in the dm,md, usercoldstart item (to ensure that the command is executed at system start up) by typing: set-def-tape-blk block.size tape.number For example, the tape device number is 5 and the physical block size is 0. set-def-tape-blk 0 5 Choosing 0 sets the physical block size to a variable value. If you want to set the physical block size to a specific numeric value you can. In this instance, replace the variable value (0) with a numeric value. For example, the variable block size 0 in the first example is replaced by the numeric value 512. set-def-tape-blk 512 5 Method 2 Method 3 Execute these commands from the TCL prompt by typing: set-device tape.number set-def-tape-blk block.size The last way to set a numeric value to a block size is to execute this command from the TCL prompt by typing: !mt -f device.name defblksize block.size
Setting Block Size of a Tape Already in the Tape Drive

Ensure that there is a tape in the drive. There are three methods available to set the block size for a tape that is already in the tape drive: Method 1 Execute these commands from the TCL prompt by typing: list-device set-tape-blk block.size tape.number
69
Method 2
Execute these commands from the TCL prompt by typing: set-device tape.number set-tape-blk block.size If you do not designate a tape number in step one, the block size will be set for the tape device to which the TigerLogic user is currently attached.
Method 3
Execute this command from the TCL prompt by typing: !mt -f device.name setblk block.size
70
D3 File Sizer Utility

Use the D3 File Sizer Utility to resize D3 files automatically or manually. The D3 File Sizer Utility uses the file-of-files, which is updated by the file-save command. The file-of-files contains statistical information for each file on the system. Whenever a file is created, restored, or deleted this file is updated. If you are already familiar with the D3 File Sizer Utility, see D3 File Sizer Utility Commands as a quick reference. Automatic Resizing The D3 File Sizer Utility automatically resizes D3 database files through the use of the Background Monitor. At user specified intervals, the Background Monitor analyzes the size of files in: Specified account Individual files Entire system
and automatically resizes them to ensure proper system performance. Manual Resizing The D3 File Sizer Utility also allows the manual resizing of files at any time. The user can build a list of selected files to resize, and view information about individual files. Files can be resized manually regardless of Background Monitor status. The Background Monitor tracks files on your database daily, weekly, or monthly (depending on how often you specify) to ensure that they are sized according to the default maximum ratio or according to individually set maximum ratios. The following options may be edited by the user: Resizing Individual Files Wake-up date Wake-up time Check files (specifies how frequently the files are checked) Day of month Day of week Monitor Default Maximum Fill Default Action
Resizing Files with the Background Monitor
Files can be resized on an individual basis at any time. To track the files being resized, build a list of selected files. Using the list of selected files, you can view individual file information, search the list for a specific character string, or resize a file. File statistics displayed within the various D3 File Sizer screens are regenerated by performing a file-save or account-save, running the D3 File Sizer Utility, then performing another file-save or account-save. Detailed instructions are provided in the remaining pages of this document (see Viewing File Information).
71
The following topics are presented: Accessing the Background Monitor Starting the D3 File Sizer Utility Viewing File Information Modifying Individual File Entries Using the Log File D3 File Sizer Utility Commands
72
Accessing the Background Monitor

Access the Background Monitor from the D3 File Sizer Utility Main Menu. NOTE Oversized files cannot be resized using the D3 File Sizer Utility.
Use the Background Monitor for: Starting the Background Monitor Stopping the Background Monitor Displaying the Background Monitor Status Modifying the Wake-up Date and Time Modifying Background Monitor Options
73
Starting the Background Monitor

Files cannot be resized automatically unless the Background Monitor is running. To start the Background Monitor: 1. Start the D3 File Sizer Utility. 2. Type file-sizer at the TCL prompt. The Main Menu displays.
3. Select the Start Background Monitor option from the Main Menu. This message displays. Start Background Monitor. Confirm (<y>/n)? 4. Do one of the following: Press Y to start the Background Monitor. Press N to return to the Main Menu without starting the Background Monitor.
74
Stopping the Background Monitor

To disable file monitoring, stop the Background Monitor. To stop the Background Monitor: 1. Select the Stop Background Monitor option from the Main Menu. This message displays. Stop Background Monitor. Confirm (<y>/n)? 2. Do one of the following: Press Y to stop the Background Monitor. Press N to return to the Main Menu without stopping the Background Monitor.
75
Displaying the Background Monitor Status

The Wake-up Date and Wake-up Time parameters can be modified when the Background Monitor Status is displayed. Several fields display in the Background Monitor Status screen. The number of fields that display depend on the status of the Background Monitor. To display the Background Monitor Status: Select the Background Monitor Status option from the Main Menu. The Background Monitor Status screen displays.
To exit the Background Monitor Status: Press ESC to exit the Background Monitor Status screen and return to the Main Menu without making any changes. To modify these options, see Modifying the Wake-up Date and Time. This table lists the Background Monitor status fields, including the parameter, editable fields, default values, and how it is generated. Parameter Status Editable Field No Default Value and How it is Generated Depends on the Background Monitor. Possible statuses include: RunningBackground Monitor is actively checking the files specified in Background Monitor Options. SleepingBackground Monitor is running but inactive, waiting until the time specified in Background Monitor Options to wake-up and check files. StoppedBackground Monitor is disabled. Start RequestedBackground Monitor is in the process of being started. Stop RequestedBackground Monitor is in the process of being stopped.
Running on PIB Wake-up Date No Yes
PIB number where the background Monitor is running. Date that the Background Monitor is scheduled to wake-up and check files.
76
Wake-up Time Started By Started On Started At
Yes No No No
Time that the Background Monitor is scheduled to wake-up. Last user who started the Background Monitor. Date when the Background Monitor was last started. Time when the Background Monitor was last started.
77
Modifying the Wake-up Date and Time

On the Background Monitor Status screen, only the Wake-up Date and the Wake-up Time can be adjusted. NOTE The Wake-up Date and Wake-up Time can only be modified while the Background Monitor is running.
To modify the Wake-up Date and Time: 1. Select the Background Monitor Status option from the Main Menu. 2. Select the Wake-up Date field. 3. Change the date, then press ENTER. The date can be entered MM/DD/YY or DD/MM/YY (depending on the international date setting), where MM is the month, DD is the day, YY is the year. You must type the slash (/). 4. Select the Wake-up Time field. 5. Change the Wake-up Time. The time must be entered HH:MM, where HH is the hour, MM is the minutes. You must type the colon (:). Enter either military or standard time; however, AM or PM must be specified for standard time. This message displays. Make these changes to the schedule (<y>/n)? 6. Do one of the following: Press Y to save any changes and return to the Main Menu. Press N to return to the Main Menu without saving the changes.
78
Modifying Background Monitor Options

This lists the Background Monitor options, how the values are generated, and if the field can be edited. Parameter Check Files Editable Field Yes Explanation and Default Value/First Choice Value Specifies how often the Background Monitor should wake-up and check the files. The first choice value is Daily. Options include: Day of Month Day of Week Wake-up Time Monitor Yes Daily Weekly Monthly
Sets the day of the month the Background Monitor checks the files when Monthly is selected at the Check Files field. The default value is 5. Sets day of the week the Background Monitor checks the files when Weekly is selected at the Check Files field. The default value is Saturday. Defines what time of day the Background Monitor is scheduled to wake-up and check files. The first choice time can be changed. The first choice value is 6:00 PM. Displays the list of files to monitor. This value can be set to either All Files on System or List of Selected Files. The first choice value is All Files on System. Displays the maximum ratio allowed before the Background Monitor considers the file to be undersized. The Maximum Fill Ratio is the extent to which the allocated space for a file is filled. The default value is 125. Displays the action to take when a file becomes undersized. The default value is Write Entry in Log File.
Yes
Yes
Yes
Default Max. Fill
Yes
Default Action
Yes
NOTE
First choice values are not defaults. They are values placed in the field by the D3 File Sizer Utility when the Background Monitor Options screen is first accessed.
To modify the Background Monitor Options: 1. Select the Background Monitor Options option from the Main Menu. The Background Monitor Options screen displays.
79
2. Press ENTER to move to the desired field. 3. Press TAB to display options. 4. Select and make changes to options you want to modify. 5. Do one of the following: Press ENTER to move to the next field. Press ESC at any field to exit the Background Monitor Options screen.
80
Starting the D3 File Sizer Utility

The D3 File Sizer Utility is automatically installed with any of the D3 Server products and is accessed from the TCL prompt. CAUTION If update and/or retrieval locks exist on files that will be resized, the file-sizer should be started under the DM user.
To start the D3 File Sizer Utility: 1. Log on to the dm account. 2. Run the D3 File Sizer Utility. At the TCL prompt, type: file-sizer The Main Menu displays. Use the navigation commands listed on the bottom of the Main Menu to move within the screen. If the Arrow and ESC keys do not work on your terminal emulator, use these as an alternative: CTRL+B CTRL+N or ENTER CTRL+X Move up a field. Move down a field. Return to the Main Menu.
81
Viewing File Information

The View File Information option allows you to view lists of files and information about individual files. There are four different methods to view file information: Displaying All Files Displaying Selected Files Displaying Undersized Files Displaying Monitored Files When a display is selected, the appropriate files for that option display in the File Statistics Generated screen. NOTE The screen headers can vary with option selected.
Add, clear, delete, resize, and search list the characteristics of the files displaying. Change the Maximum Fill Ratio or the action that is taken when that ratio is met. Use the commands below the File Statistics Generated screen to edit the list of files.
Use the TAB key to view additional information on a specific file. The dm account is used in this example.
82
Only the individual file displayed changes when the editable fields are modified. A global change can be made only when the Background Monitor Options are specified. The following table defines the fields in the File Statistics Generated screen. Parameter Account Filename Dataname Last Saved Bytes Suggested Modulo Current Modulo Cur. Fill Ratio Max. Fill Ratio Action Editable Field No No No No No No No No Yes Yes Explanation of Parameter Account where monitored file resides. Dict name of monitored file. Data name of monitored file. Date when file was last saved. Number of bytes in the file. Recommended modulo for the file, based on the Maximum Fill Ratio specified. Current modulo of the file. Current fill ratio of the file. Ratio of file that is considered undersized (List of Selected Files only). Action to take if file becomes undersized (List of Selected Files only).
83
Displaying All Files

The File Statistics Generated screen displays every file stored in the system, despite the status, when Display All Files is selected. To display all files: 1. Select the View File Information option from the Main Menu.
2. Select the Display All Files option from the File Information Menu. The File Statistics Generated screen displays.
84
Displaying Selected Files

Only files previously selected by the user display (see Adding a File to the List of Selected Files). While displaying a list of selected files, you can: List the characteristics of the selected files Change the Maximum Fill Ratio Delete from list
To display selected files: 1. Select the View File Information option from the Main Menu. 2. Select Display List of Selected Files option from the File Information Menu. The File Statistics Generated screen displays.
85
Displaying Undersized Files

Only files that have not reached the designated Maximum Fill Ratio display. To display undersized files: 1. Select the View File Information option from the Main Menu. 2. Select the Display Undersized Files option from the File Information Menu. The Select Account screen displays.
NOTE
The Select Account screen displays after a file-save is performed. Anytime after the first file-save is performed, to modify the account, the File Statistics Generated screen for undersized files must be cleared. For details on clearing the list, see Clearing the List of Selected Files.
3. Select the account that contains the undersized files you want to view in the Select Account screen, then press ENTER. A list of files contained in the selected account displays.
86
Displaying Monitored Files

All of the files being tracked by the Background Monitor are presented in a list when the Display Files Being Monitored option is selected. NOTE If the Background Monitor is stopped, this option continues to list the files that are currently set to be monitored.
To display monitored files: 1. Select the View File Information option from the Main Menu, then press ENTER. 2. Select the Display Files Being Monitored option from the File Information Menu, then press ENTER.
87
Modifying Individual File Entries

The following sections explain the procedures for changing the contents of the File Statistics Generated screen. Adding a File to the List of Selected Files Clearing the List of Selected Files Deleting Files from the List of Selected Files Resizing an Individual File Searching the List for a Specific Character String
88
Adding a File to the List of Selected Files

Files can be added to the list of selected files from the File Statistics Generated screen. To add a file to the List of Selected Files: 1. Select the file to add from the complete file list, then press A. This message displays at the bottom of the screen. Add this entry to the list of selected files (<y>/n)? 2. Do one of the following: Press Y to add the entry to the list of selected files. This message displays at the bottom of the screen. Entry added. Press <Enter>: Press ENTER to return to the Information screen. Press N to return to the Information screen without adding the file.
89
Clearing the List of Selected Files

The list of selected files can be clearer from the File Statistics Generated screen. To clear the List of all Selected Files: 1. Press C from the File Statistics Generated screen. This message displays at the bottom of the screen. Clear list (y/<n>)? 2. Do one of the following: Press Y to clear the list of all entries. Press ESC, then ENTER to return to the previous screen. Press N to return to the File Statistics Generated screen without clearing the list of all entries.
90
Deleting Files from the List of Selected Files

Files can be deleted from the list of selected files from the File Statistics Generated screen. To delete selected files: 1. Select the file to delete from the complete file list, then press D. This message displays at the bottom of the screen. Remove this entry from the list of selected files (<y>/n)? 2. Do one of the following: Press Y to delete the entry from the list of selected files. Press N to return to the Information screen without deleting the file.
91
Resizing an Individual File

To determine which files to resize, compare the Current Fill and Maximum Fill columns for each file. When the Current Fill exceeds the Maximum Fill, resize the file. NOTE Files in the FSI:dm cannot be resized. Attempting to resize a file in the FSI:dm results in the message: This file cannot be resized. To resize a file: Use the commands at the bottom of the File Statistics Generated screen. 1. Select the file to resize in the File Statistics Generated screen, then press R. Oversized files cannot be resized using the D3 File Sizer Utility.
This message displays. Resize file file.name from A to B (y/n)? The file.name represents the name of the file to be resized, A represents the old file size, and B represents the new file size. 2. Do one of the following: Press Y to resize the file. Press N to return to the File Statistics Generated screen.
This message displays (if you pressed Y). Do you want to use a phantom process to resize this file (<y>/n)? 3. Do one of the following: Press Y to use a phantom process, then press ENTER to return to the File Statistics Generated screen and continue working while the file is resized.
92
Using a phantom process enables you to continue working in the D3 File Sizer Utility while the file is being resized. This message displays. Phantom process spawned. Press <Enter>: Press N to resize the file without using a phantom process. If you decide not to use a phantom process, you must wait for your file to be resized before continuing to use the D3 File Sizer Utility. NOTE The system displays ** until the resize is complete. Files can only be optimized by File Sizer after a file-save because the File Sizer Utility uses the file-of-files which contains statistical information for each file on the system, and is only updated by performing a file-save or an account-save (s.
4. Perform a file-save using the (s option to update statistics.
93
Searching the List for a Specific Character String

Use the D3 File Sizer Utility to search for a specific character string in a filename, within a file list. Searching for a specific character string is useful for navigating through an extensive list of files. NOTE Searching for a specific character string does not generate a new list, but takes you to the first occurrence in the file list of the character string entered.
To search a list for a specific character string: 1. Press S from the File Statistics Generated screen. 2. Enter a search string, then press ENTER. The D3 File Sizer locates the next occurrence of the string you specified.
94
Using the Log File

All of the files that were found to be undersized by the Background Monitor, based on the Maximum Fill Ratio specified, display in the log file. Displaying the Log File Clearing the Log File
Displaying the Log File

The log file provides the: Date and time that the files were found Filepath Old modulo New/suggested modulo Action taken User and PIB that started the Background Monitor
To display the Log File: 1. Select the Display Log File option from the Main Menu, then press ENTER. This message displays. Send Log to (T)erminal, (P)rinter, or (C)ancel 2. Enter one of the following: T P C To display the log file on screen. When finished viewing the log file, press ENTER to return to the Main Menu. To send the log file as a print job to the printer which is currently set through spassign. After the print job is sent, the utility returns to the Main Menu. To cancel and return to the Main Menu without displaying the log file.
NOTE
A null value defaults output to the terminal.
Clearing the Log File

Clear the log file to keep it at a manageable size. To clear the Log File: 1. Select the Clear Log File option from the Main Menu. This message displays.
95
Clear log file (y/<n>)? 2. Do one of the following: Enter Y to clear the log file, then press ENTER to return to the Main Menu. This message displays. Monitor log cleared. Press <Enter>: Enter N to return to the Main Menu without clearing the log file.
96
D3 File Sizer Utility Commands

If you are already familiar with the D3 File Sizer Utility, use this table as a quick reference. This table lists the commands and their functions: TAB ESC CTRL+D CTRL+F CTRL+N CTRL+Z CTRL+T CTRL+X Display the details of the selected file. Exit the Information screen. Display the previous page of the list. Display the next page of the list. Move down one line. Display the last page of the list. Display the first page of the list. A C D R Exit to the Main Menu from the File Statistics Generated screen. Deletes the current field in the Background Monitor Options screen.
Add a file to the List of Selected Files. Clear the list of all entries (available for List of Selected Files only). Delete the selected file from the list (available for List of Selected Files only). Resize the file. If the file needs to be resized, type the new size of the file. If the file does not need to be resized, a message indicating that the file is appropriately sized displays. Search the list for the first appearance of a specified character string that you specify.
97
Copyright
Copyright (c) 1982, 2012. TigerLogic Corporation. All rights reserved. TigerLogic, D3 (D3), Pick, Omnis, mvDesigner, and mvEnterprise are trademarks of TigerLogic Corporation. This product may include or be accompanied by software developed by third parties, including those listed below. Software from third parties may be subject to additional or different license terms. For details, please see the TigerLogic End User License Agreement, the third party license agreements that accompany the product, and the products documentation. Customers of TigerLogic may find the following third party open source programs of use ("Open Source Programs"): These Open Source Programs are publicly available at no charge. As a convenience to you, TigerLogic may provide you with copies of these Open Source Programs in the same package as TigerLogic products. However, these Open Source Programs are not part of TigerLogics product and are not subject to the TigerLogic End User License Agreement. Rather, these Open Source Programs are free software; you can redistribute them and/or modify them under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License or (at your option) any later version. These Open Source Programs are distributed in the hope that they will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You will find a copy of the GNU General Public License accompanying these Open Source Programs. If you do not, please contact TigerLogic. For those Open Source Programs that are provided, source code should also be included on the accompanying media. If not, please contact TigerLogic at any time within three (3) years after you acquire this TigerLogic product to request a free copy the source code for these Open Source Programs. D3 Version: 9.0 Linux Doc Version: April 2011
98
99
Index
( (E)IDE Disks ......................................... 57 / /etc/inittab file ...............................12, 15 4 4mm Tapes ......................................... 69 8 8mm Tapes ......................................... 69 A ABS Patches, Loading ............................. 21 Accessing the Background Monitor ............. 75 Adding...................................... 61, 65, 91 A File to the List of Selected Files ........... 91 Reserved Printers............................... 61 Shared Printers ................................. 65 Administering UNIX ODBC Servers .............. 16 Apply Updates .................................19, 46 Auto Create ........................................ 46 B Background Monitor........ 75, 76, 77, 78, 80, 81 Accessing ........................................ 75 Displaying the Status........................... 78 Modifying Options .............................. 81 Modifying the Wake-uo Date Time ........... 80 Starting .......................................... 76 Stopping.......................................... 77 Boot File ............................................ 12 C Changing the inittab file ......................... 15 Check Files ......................................... 81 Check Period ....................................... 46 Clear Log Queue ................................... 44 Clear Permanent Log ............................. 42 Clearing .........................................92, 97 List of Selected Files ........................... 92 Log File........................................... 97 Close Opened Files ................................ 42 Commands, D3 File Sizer Utility ................ 99 Comments .......................................... 46 Compatibility, Maintaining ...................... 12 Configuration File Tape Statements, D3 ...... 54 Configuring .....................................11, 22 Blocks of Telnet Ports on D3 .................. 11 Hot Backup ...................................... 22 Connected .......................................... 48 Connecting ........................................... 8 Next Available D3 Port .......................... Specific D3 PIB ................................... Conventions ......................................... Creating a Turnkey System ....................... D D3 .............................. 3, 11, 54, 56, 60, 73 Administration Guide Introduction ........... 3 Configuration File Tape Statements ......... 54 Configuring Blocks of Telnet Ports ........... 11 D3 File Sizer Utility............................. 73 Peripherals ...................................... 56 Printers ........................................... 60 D3 File Sizer Utility .. 73, 75, 76, 77, 78, 80, 81, 83, 84, 86, 87, 88, 89, 90, 91, 92, 93, 94, 96, 97, 99 Accessing the Background Monitor ........... 75 Adding a File to the List of Selected Files .. 91 Clearing the List of Selected Files ........... 92 Clearing the Log File ........................... 97 Commands ....................................... 99 Deleting Files from the List of Selected Files .................................................. 93 Displaying All Files ............................. 86 Displaying Monitored Files .................... 89 Displaying Selected Files ...................... 87 Displaying the Background Monitor Status .. 78 Displaying the Log File ......................... 97 Displaying Undersized Files ................... 88 Modifying Background Monitor Options ..... 81 Modifying Individual File Entries ............. 90 Modifying the Wake-uo Date Time ........... 80 Resizing an Individual File..................... 94 Searching the List for a Specific Character String .......................................... 96 Starting ........................................... 83 Starting the Background Monitor ............. 76 Stopping the Background Monitor ............ 77 Using the Log File .............................. 97 Viewing File Information ...................... 84 D3 Processes, Testing ............................. 36 Database Configuration, Hot Backup ........... 23 Day of Month ....................................... 81 Day of Week ........................................ 81 Default Action ..................................... 81 Default Max.Fill .................................... 81 Deleting Files from the List of Selected Files. 93 Disks ................................................. 57 (E)IDE ............................................. 57 Floppy ............................................ 57 SCSI ............................................... 57 8 8 4 6
100
Display Queue..................................40, 44 Displaying.................... 78, 86, 87, 88, 89, 97 All Files .......................................... 86 Background Monitor Status.................... 78 Log File........................................... 97 Monitored Files ................................. 89 Selected Files ................................... 87 Undersized Files ................................ 88 Document Conventions ............................. 4 D-Pointer Controls, Hot Backup ................. 50 E Errors, Hot Backup ................................ 52 F File and Account Auto-Create ................... 19 File Information, Viewing ........................ 84 File-of-Files D-Pointer ............................ 21 Files .. 73, 86, 87, 88, 89, 90, 91, 92, 93, 94, 96 Adding a File to the List of Selected Files .. 91 Clearing the List of Selected Files ........... 92 Deleting from the List of Selected Files .... 93 Displaying All .................................... 86 Displaying Monitored ........................... 89 Displaying Selected ............................ 87 Displaying Undersized Files ................... 88 Modifying Individual Entries .................. 90 Resizing .......................................... 73 Resizing Individual ............................. 94 Searching for a Specific Character String .. 96 Floppy Disks ........................................ 57 H Hardware Requirements, Hot Backup .......... 21 hbmaster ........................................... 39 hbslave .............................................. 39 Helper ............................................... 19 Hot Backup ... 18, 19, 21, 22, 23, 25, 28, 31, 32, 33, 34, 35, 37, 38, 39, 40, 42, 44, 46, 48, 50, 52 Configuring ...................................... 22 Database Configuration........................ 23 Definitions ....................................... 19 D-Pointer Controls.............................. 50 Errors ............................................. 52 Introduction ..................................... 19 lost + found File ................................ 50 Main Menu ....................................... 40 Master Server Configuration .................. 25 Menu Navigation ................................ 38 Querying Servers................................ 48 Requirements ................................... 21 Resizing Files Online ........................... 50 Restrictions ...................................... 21 Server Selection Menu ......................... 39 Setup Server Utility ............................ 46
Slave Server Configuration .................... 28 Special Operations Menu ...................... 42 Starting ........................................... 32 Starting the Master Server .................... 33 Starting the Slave Server ...................... 34 Synchronizing the Servers ..................... 31 Testing the Servers ............................. 35 Transaction Log Menu .......................... 44 Using .............................................. 37 I Idle .................................................. 48 inittab File, Changing............................. 15 Introduction ......................................... 3 L Large File Creation ................................ 19 List Permanent Log ............................... 42 Loading ABS Patches .............................. 21 Log All Files ........................................ 44 Log DL Files Only .................................. 44 Log File ............................................. 97 Clearing .......................................... 97 Displaying ........................................ 97 Using .............................................. 97 Log Slave Updates ............................ 19, 46 lost + found File, Hot Backup ................... 50 M Main Menu, Hot Backup .......................... 40 Maintaining Compatibility........................ 12 Master ............................................... 19 Master Server Configuration ..................... 25 Hot Backup ...................................... 25 Master Server, Starting ........................... 33 Maximum Fill Ratio ................................ 81 Menu Navigation, Hot Backup ................... 38 Modifying ...................................... 80, 90 Individual File Entries .......................... 90 Wake-up Date Time ............................ 80 Monitor .............................................. 81 Multireel Saves..................................... 69 N Notify List .......................................... 46 O ODBC Servers, Administering .................... 16 Options, Background Monitor .................... 81 P Peripherals ......................................... 56 Printers .......................... 59, 60, 61, 63, 65 Adding Reserved ................................ 61 Adding Shared ................................... 65 D3 ................................................. 60 Removing Reserved............................. 61
101
Removing Shared ............................... 65 Shared ............................................ 63 Protocol............................................. 46 Pseudo Tape Devices ............................. 69 Q Query Server ....................................... 40 Querying Servers, Hot Backup................... 48 R Readign Network .................................. 48 Reading Queue..................................... 48 Remote Host Name ............................... 46 Removing Reserved Printers ..................... 61 Removing Shared Printers ....................... 65 Reserved Printers ................................. 61 Adding ............................................ 61 Removing ........................................ 61 Resizing .........................................73, 94 Files .............................................. 73 Individual Files .................................. 94 Resizing Files Online, Hot Backup .............. 50 Restart Applying Updates ........................ 42 S save Command..................................... 21 SCSI Disks ........................................... 57 SCSI Tapes .......................................... 69 Searching the List for a Specific Character String ............................................. 96 Serial Turnkey ..................................... 12 Server ............................................... 19 Server Configuration, Hot Backup Master ..... 25 Server Configuration, Hot Backup Slave ....... 28 Server Name ....................................... 46 Server Selection Menu, Hot Backup ............ 39 Server Type ........................................ 46 Servers ..................................... 31, 35, 48 Querying Hot Backup .......................... 48 Synchronizing Hot Backup ..................... 31 Testing Hot Backup ............................ 35 Set Queue Limit ................................... 44 Setup Server ....................................... 42 Setup Server Utility, Hot Backup ............... 46 Shared Printers ........................... 63, 65, 68 Adding ............................................ 65 Removing ........................................ 65 Troubleshooting ................................ 68 Show Server ........................................ 40 Show Statistics..................................... 40 Slave ................................................ 19 Slave Server Configuration, Hot Backup ....... 28 Slave Server, Starting ............................ 34 Software Requirements, Hot Backup........... 21 Special Operations ................................ 40 Special Operations Menu, Hot Backup ......... 42
Start Enqueueing .................................. 44 Start Server ........................................ 40 Starting .......................... 32, 33, 34, 76, 83 Background Monitor ............................ 76 D3 File Sizer Utility............................. 83 Hot Backup ...................................... 32 Hot Backup Master Server ..................... 33 Hot Backup Slave Server....................... 34 Status .......................................... 40, 42 Stop Applying Updates............................ 42 Stop Enqueueing ................................... 44 Stop Server ......................................... 40 Stopped ............................................. 48 Stopping the Background Monitor .............. 77 T Tape Statements, Configuration File........... 54 Tapes ................................................ 69 4mm .............................................. 69 8mm .............................................. 69 Multireel Saves .................................. 69 Pseudo ............................................ 69 Scsi ................................................ 69 Target VME Name ................................. 46 TCP Port Number .................................. 46 Telnet Ports on D3, Configuring ................ 11 Telnet Turnkey Increased Functionality ........ 8 Temporary Hold Files ............................. 19 Testing ......................................... 35, 36 D3 Processes ..................................... 36 Hot Backup Servers ............................. 35 Topic Description ................................... 3 Transaction Log Menu ....................... 40, 44 Hot Backup ...................................... 44 Transaction Log Queue ........................... 19 Troubleshooting Shared Printers ................ 68 Turn Traces Off .................................... 42 Turn Traces On .................................... 42 Turnkey System .................................. 6, 7 Creating ........................................... 6 TxLog Timer ........................................ 46 U UNIX ODBC Servers. Administering ............. 16 Using ........................................... 37, 97 Hot Backup ...................................... 37 Log File ........................................... 97 V Viewing, File Information ........................ 84 W Wait Incoming Call ................................ 48 Wait Response to Call ............................ 48 Waiting for ACK .................................... 48 Wake-uo Date Time, Modifying ................. 80
102
Wake-up Time ..................................... 81
103

Admind 3

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Admind 3

Hochgeladen von

Copyright:

Verfügbare Formate

D3 Linux System Administration Guide

D3 Linux System Administration Guide

D3 Linux System Administration Guide Overview

D3 File Sizer Utility

D3 Linux System Administration Guide

D3 Linux System Administration Guide

D3 Linux System Administration Guide

Creating a Turnkey System

D3 Linux System Administration Guide

D3 Linux System Administration Guide

Using Increased Functionality

Connecting to the Next Available D3 Port

D3 Linux System Administration Guide

Connecting to a Specific D3 PIB

D3 Linux System Administration Guide

/usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon /usr/bin/d3net/netcon

/usr/bin/d3net/16001 /usr/bin/d3net/16002 /usr/bin/d3net/16003 /usr/bin/d3net/16018 /usr/bin/d3net/16019 /usr/bin/d3net/16020

To operate the nailed Telnet feature

UNLISTED stream tcp yes /usr/sbin/in.telnetd -L /usr/bin/d3net/16001 16001

D3 Linux System Administration Guide

Configuring Blocks of Telnet Ports on D3

Syntax auto-xinet <start_port> <port_count> <start_pib> <vmname> <pool_name> <(options> Parameter(s)

start_port port_count start_pib vname pool_name options

D3 Linux System Administration Guide

Boot File /etc/inittab

Setting Parameters for Serial Lines

D3 Linux System Administration Guide

Word Length cs7 cs8

Description = 7 bits = 8 bits

Parity -parenb parenb parodd

Description = no parity = odd parity

D3 Linux System Administration Guide

Stop Bit -cstopb cstopb Examples

Description = 1 stop bit = 2 stop bit

TCL Command 9600,8,N,1 4800,7,0,2 38400,7,E,1

D3 Linux System Administration Guide

D3 Linux System Administration Guide

Administering UNIX ODBC Servers

D3 Linux System Administration Guide

port timeout Start ODBC Stop ODBC

Displays a list of servers running on the system.

D3 Linux System Administration Guide

D3 Linux System Administration Guide

Hot Backup Introduction

log slave updates

D3 Linux System Administration Guide

file and account auto-create helper

large file creation

temporary hold files

D3 Linux System Administration Guide

Loading ABS Patches

D3 Linux System Administration Guide

Configuring Hot Backup

D3 Linux System Administration Guide

D3 Linux System Administration Guide

D3 Linux System Administration Guide

Hot Backup Master Server Configuration

D3 Linux System Administration Guide

D3 Linux System Administration Guide

The Transaction Log menu displays.

7. Type X to exit to TCL. The master server is configured.

D3 Linux System Administration Guide