This page is under construction; please write james.knight@galegroup.com if you have questions about VMS client installations.

The program works with a variety of terminal types and emulators (see note 1 below). Most common OPAC terminal types are supported, including Wyse native and AddsVP emulation, and DEC VT.

The InfoTrac EF client for VMS is available for both VAX and Alpha platforms. The program sets are available as VMS compressed tape archives from our FTP server at

ftp.iacenter.com/pub/iac/distribution/

The current builds for each platform are listed below. Detailed instructions for download, installation and configuration are also included. Support for the VMS implementation of the EF client is available at

Phone:  800 227 8431
Email:   technicalsupport@galegroup.com.

To obtain the location code(s) needed to run the InfoTrac EF client, contact the installation support group, at 800 877 4253, or the technical support desk at 800 227 8431. If you are upgrading an earlier installation of the client, you may be able to identify these location codes by reading the file

[...itef<nnn>.itefdata]userlist.txt

where <nnn> is the client version currently being used. We recommend simply copying this file to the new [..itefdata] directory after the upgrade is complete.

After logging onto the site's host using the TGG administration account, connect to TGG's FTP server and download the backup saveset:

(a) $ ftp ftp.iacenter.com
(b) ftp> user anonymous
(c) user anonymous: password> ident@host.net
(d) ftp> BINARY
(e) ftp> GET pub/iac/distribution/itef260b.sav    (VAX)
      or
    ftp> GET pub/iac/distribution/itef260b_alpha.sav     (Alpha)

Any local filename can be used; in the examples below, we use itef260b.sav. Extract the saves as follows;

(f) $ backup/log itef260b.sav/sav [...]

$ rename itef260b.sav itefb.sav

Locate and copy any text file that is available in the directory as a backup saveset. E.g., use the ftp log file:

$ backup/log whatever.log itef260.sav/sav/block=32256
  %BACKUP-S-COPIED, copied ...

Then, copy the renamed saveset over the new saveset with the correct block size:

$ copy/over itefb.sav itef260.sav

Using the fixed saveset, proceed with step (f) above.

(g) $ set file/prot=(s:re,o:rwed,g:re,w:re) [IAC...]*.*;*

Set the default directory to the first subdirectory created by the current saveset, and delete setup.com

(h) $ set def [.itef260]
(i) $ del setup.com;

If the IAC directories reside on a device other than SYS$SYSDEVICE, edit the ITEF_STARTUP.COM and ITEF_PROCESS_LOGICALS.COM, substituting the string SYS$SYSDEVICE with the correct device name. References to the home directory may also require adjustments.

For example, check the current device using the show default (sho def) command:

$ sho def
  DISK$DEVICE:[IACADM]

After editing the files, purge original versions:

$ purge

Move the ITEF_STARTUP.COM and ITEF_PROCESS_LOGICALS.COM files to the executables directory, and set as the default directory:

(j) $ backup/log/del itef_*.com; [.itefexe]*.*
(k) $ set def [.itefexe]

There are multiple itef*.exe program files installed in the [...itefexe] directory.

On a VAX or Alpha, running Multinet, only itef.exe is required; the remaining .exe files may be deleted:

$ del itef_*.exe;

On a VAX or Alpha running UCX (instead of Multinet), use the itef_ucx20.exe program file

$ del itef.exe;
$ rename/log itef_ucx20.exe itef.exe
$ del itef_*.exe;

Define process logicals for testing by executing the ITEF_PROCESS_LOGICALS.COM program:

$ @itef_process_logicals.com

Change the default directory to configure the userlist.txt file

$ set def [-.itefdata]

If an earlier version of the InfoTrac client is installed on the current host, copy the userlist.txt file from that version's [...itefdata] directory. E.g.,

$ copy [iac.itef252.itefdata]userlist.txt userlist.txt

Otherwise, edit the current userlist.txt file to remove extraneous entries and add, as needed, additional entries using the system's account names and InfoTrac location codes (see complete explanation below).

<device>:[<dir>.itef260.itefexe]itef_startup.com

Before releasing the program to users, testing can be done using

<device>:[<dir>.itef260.itefexe]itef_process_logicals.com
<device>:[<dir>.itef260.itefexe]itef.com

The TGG administration account should not be distributed to the general public. It is intended to be a maintenance account.

You will notice that the software has a print command ("P"). InfoTrac will print either the highlighted citation, a list of marked citations, or the fulltext of an article to what it believes is the locally attached slave printer of a dumb terminal. This print can be redirected to network printers at the customer's discretion. InfoTrac can also be configured to send twenty linefeeds at the end of each print job, a form-feed at the end of each print job, or no paper-motion command at the end of each print job.

Printing support is implemented via TERMPRN values. The TERMPRN options are listed below. In the VMS versions of InfoTrac they are implemented as logicals and can be defined at either the process or system level.

• generic No printer-motion commands are sent at the end of the print request. If any printing has taken place, the printer is turned back on and twenty line feeds are sent as the program exits back to the database menu.
  
• page_generic A form feed is sent after each print request whether it is a single citation, full record, or mark list. The message "Hint! Use mark to save paper." is displayed in the printing popup if a single citation is being printed. No formfeed is sent when exiting back to the Database menu. This will probably be the best setting for locally attached page printers.
  
• line_generic Twenty line feeds are sent after each print request whether it is a single citation, full record, or mark list. No form feed is sent when exiting back to the Database menu.
  
• network_generic No paper-motion command is sent at the end of a print request before sending the printer-off sequence. The message "Hint! Use mark to save paper." is displayed in the printing popup if a single citation is being printed.

The InfoTrac executable (ITEF.EXE) expects three parameters: userclass, keymap, and location. These parameters are all contained in the IAC_ITEF_DATA:USERLIST.TXT file. The first line of the file looks like:

iac$user_default, a, genericv, xxx_main

If the VMS username assigned to the user that is executing InfoTrac is not contained in the file, then the default configuration identified by the iac$user_default user will be used. If other values for userclass, keymap, or location are desired, additional lines can be added to the file for the appropriate VMS username.

Userclass specifies the delivery permissions of the particular invocation. Recommended values are a, b or c. Note that current implementations have rendered userclass codes roughly synonymous; userclass 'a' is recommended.

The keymap specifies the mapping between keyboard keys and InfoTrac functions. The 'genericv' keymap maps nearly all functions to printable characters, including "[" for page-up and "]" for page-down. By editing the text file IAC_ITEF_DATA:USERLIST.TXT you can substitute the word 'genericv' for otherkeymaps, such as 'vt200' or 'vt200f11'. The vt200 keymap is designed for DEC VT terminals that have the label on the keyboard identifying various function keys, such as "Esc" for F11. The vt200f11 keymap is designed for DEC VT terminals that do not have this lable. All keymaps are housed at the server. Custom keymaps can be created.

The location ID indicates to InfoTrac the location and library affiliation of the patron. The acceptable location identifiers for your library will be provided by TGG (see above). We use the location to separate individual database subscriptions and holdings.

The software can be executed directly from the DRA ONLINE_CATALOG, NISO, or INFORMATION_GATEWAY programs. For ONLINE_CATALOG and NISO access to InfoTrac,you need to add two logicals to DRA_SITE:PAC_CONFIGURATION_LOGICALS.COM:

$ DEFINE/SYSTEM/NOLOG DRA_PAC_IAC IAC_ITEF_EXE:ITEF.COM
$ DEFINE/SYSTEM/NOLOG IAC Y

With the above logicals defined, you can enter "CHOOSE IAC" at the ">>"prompt in DRAPGM:NISO.EXE or "IAC" at the ">>" prompt in DRAPGM:ONLINE_CATALOG.EXE to launch InfoTrac.

To configure access from INFORMATION_GATEWAY, you need to modify the DRAIG_PROFILE_FILE to add an option to execute InfoTrac from either the options or the databases menu. The following is an example of what the "DATABASES" section of the file might look like (don't forget to increment the number by the word "DATABASES" by one).

DATABASES 2
"Staff Catalog"    DRAUTL:MARION.DFA     1855
"InfoTrac 2000"    @IAC_ITEF_EXE:ITEF"

http://infotrac.galegroup.com/holdings/<locationID>

A password is required and can be obtained by contacting the support desk at 800 227 8431.