The QM database can be accessed in a number of ways. The simplest is use of a console session. This is entry into QM directly from the operating system command prompt on the system on which it is installed. Other methods allow direct connection over a network or via a serial port and are discussed later in this section.
Entering QM from the Operating System Command Prompt
On Windows systems, once QM has been successfully installed, the program group chosen during the install (usually QM) will contain an item titled "QM Console". Clicking on this item will open a console window. You will see a copyright line and a site specific licence line. You will then be asked to enter the name of the account you wish to work in.
On all platforms you can login to the operating system and then type qm at the command prompt (this assumes that the operating system PATH environment variable has been set appropriately). If your current directory when you entered QM was not already a QM account, you will be asked if you wish to make it into one. Creation of new accounts in this way may be barred for specific users by the system administrator. See Application Level Security for more details. When entering QM in this way, the account name is determined by looking for an account register entry with the pathname of the current working directory, giving priority to an account name which is the uppercase form of the directory name.
When using a console session, you can force entry to a specific account using a command line of the form
where xxx is the account name.
On Linux systems, the operating system profile script can be used to take the user directly into QM when they login without them seeing an operating system command prompt.
Entering QM Directly via a Network
TCP/IP network technology assigns each computer on the network a unique address, usually written as four numbers separated by dots (e.g. 18.104.22.168) for an IPV4 address or a series of colon separated hexadecimal values for an IPV6 address. Alternatively, the network name of the server can be used and this will be looked up to translate it to a network address internally. When a connection is made to a network address, the caller also specifies a "port number" which identifies the service to which they wish to connect. If networking is new to you, it may help to consider the concept of network addresses and port numbers as being similar to telephone numbers and extensions.
With its default configuration, QM listens for users entering via a network connection on TCP/IP port 4242. This can be changed to an alternative port or disabled completely by amending the QM configuration parameters. Windows users who do not have any other telnet software running on their system may wish to change this to port 23, the default telnet port. Note that because this is a telnet style connection, data on the network is not encrypted. For best security, Linux users should use an SSH connection to login to the operating system and then enter QM as described above.
You can connect to QM using most terminal emulators. A licence for the AccuTerm emulator is bundled with a commercial QM licence. This emulator includes several features specifically for QM. Although the licence is bundled, you will need to download the latest version of the emulator software from the AccuTerm website.
On USB installations of QM, the installation process installs a server program, QMUSBSrvr, in the bin subdirectory of the account. This must be started manually though this can be automated via the Startup folder. Due to a published defect in Windows, the server cannot detect a system shutdown and must be closed manually.
On other Windows installations, the QM installation process installs a Windows service (QMSvc) to manage the network. There should be no need to change anything as it will start and stop automatically as required.
On all Windows environments, there is a QM Network Control program in the QM program group that can be used to start and stop the appropriate network server.
On other platforms, the install process will make the necessary changes to the operating system files that control the network. There should be no need for any manual user intervention unless you decide to modify the default settings.
In all cases, a valid user name and password known to the operating system will be required to enter QM.
Some software originating in other multivalue environments relies on being able to connect via multiple telnet ports, each leading to creation of a process with a fixed user number related to the port number. QM supports this capability via a feature known as port mapping. For more details, see the PORTMAP configuration parameter.
Port mapping is not available on USB installations of QM.
Entering QM Directly via a Serial Port
On Windows, the QMSvc service can monitor one or more serial ports for incoming QM connections. This allows entry from directly connected terminals or via dial-up lines. See the SERIAL configuration parameter of QMSvc for more details.
It is also possible to login a serial port from another QM process using the LOGIN.PORT command. This will skip the user authentication described below as the new process runs with the user name and access rights of the user who established the connection. This style of login can be useful when connecting to automated data collection devices. The LOGIN paragraph would typically be used to enter the application.
Logging In to QM
Users entering QM directly from a network connection or via a serial port must provide a valid user name and password for authentication purposes.
On Windows, the user name must also be known to the operating system. Many users of Windows XP choose to operate their systems with login at the server screen disabled, however, Windows enforces use of a valid user name on network connections, including "loop back" to the host system from a terminal emulator running on the same machine. User names can be set up using the User Administration area of the Windows Control Panel. The QM process will run as the specified user and with that user's access rights.
When using domain style logins, the format is username@domain or the older domain\username.
USB installations of QM do not have access to a suitable user authentication system so QM provides its own. This can be disabled using the SECURITY command if required, leaving the system open for network users to connect with no authentication.
On all other installations, the user name must be known to the underlying operating system. The resultant QM process will run as this user and with the access rights of that user. Use the appropriate operating system administration tools to create and maintain user names.
Suppressing the Copyright and Licence Lines
The -quiet option to the QM executable suppresses display of the copyright and licence details. This is particularly useful in situations such as scripts using QM as part of a CGI web interface. The LOGIN.PORT command mentioned above, implies use of the -quiet option so that no data is sent to the port until the application starts execution.
Device licensing is an option that allows multiple connections from a single client to share a QM licence. If your system has this feature enabled, you will see a reference to it in the first few lines of output from the CONFIG command. QM may be licensed to share a maximum of 2, 4 or 8 sessions per licensed user.
Device licensing needs support in the client software. This is included in Windows QMConsole sessions, AccuTerm 2k2 version 5.3c or later, Winnix version 3 or later, QMTerm and QMClient. With AccuTerm, device licensing must be enabled via a checkbox in the Connection page of the Tools, Settings menu. Note that the Linux Terminal command does not support device licensing.
When connecting to QM directly via a network (port 4242 as described above), device licensing is totally automatic. For entry from the operating system command prompt, the -DL option of the QM command must be used to initiate the negotiation between the client and QM. Alternatively, setting an environment variable named QMDL will make QM behave as though this option is present. This option is necessary because the negotiation process may cause terminal emulators that do not support device licensing to behave erratically.
On Linux/Unix systems, device licensing for network connections is only available if the qmlnxd daemon is running as root.