About the COMS Configuration File

The COMS Configuration file stores information in Station and Installation Data records. This information is accessed by Runtime, and is used to identify:

These records are available to the user to store installation-specific data using the COMS Utility. Refer to the Communication Management System (COMS) documentation for more information.

To define Station and Installation Data records in COMS, perform the following:

  1. Sign on to COMS with a valid usercode/password, using an ODT-capable station.

  2. Enter the following from the HOME position to access the COMS Utility:

     ?ON UTILITY
  3. Enter GO ID to access the Installation Data Activity screen. Create the Installation Data record.

  4. Enter GO S to access the Station Activity screen. Create the Station Data record.

The Station and Installation Data records are described in the following tables.

Terminal Information

Station record

 

Station name

Terminal name

Window name

MARC or default window

Trancode position

1 for others

Installation Data name

Terminal name

Installation Data record

 

Installation Data name

Host name

Integer1

Type:

  • 1 = MT983 or MT985

  • 2 = ITI

  • 4 = Noform

  • 0 = Everything else (default T27)

Integer2

ODT level:

  • 0 = Standard

  • 1 = ODT

  • 2 = Controller

Integer3

Privilege (1–15)

String1

Associated printer (characters 1–17)

Optional model (character 18–27)

String2

Language

Printer Information

Installation Data record

 

Integer1

Type:

  • 98 = Workstation printer

  • 99 = Non-workstation printer

Integer3

Privilege (0–15)

String1

Host name (characters 1–17)

Model (character 18–27)

Host Information

Installation Data record

 

Installation Data name

Host name

Integer1

100

Notes:

  • In view of the reliance that is placed on the COMS Configuration file, it is important to back up this file on a regular basis.

  • As the interface is via the COMS Utility, syntax and usage rules cannot be enforced. properties such as ODT levels, privilege levels, etc, cannot be verified at the time they are entered.

  • Station attributes are assigned based on station name. Therefore any network that dynamically allocates station names to sessions cannot be guaranteed to acquire the correct station record, and assign the correct attributes.

  • If the Integer3 value for your station is less than the set for the UserPrivilege Ispec/Event configuration property under the Environment category, you will see the error message:

     Insufficient privilege for ispec

    when you try to access the Ispec from your station.

Example Installation Data and Station for a printer

 CREATE ID MYID
		INTEGER1 = 99,
		STRING1 = "MYHOSTNAME MYMODELNAME";
CREATE STATION MYPRINTER
		ID = MYID;

CREATE ID LASERMODEL
		INTEGER1 = 99,
		STRING1 = " LASERJET";
CREATE STATION LASERP1
		ID = LASERMODEL;
CREATE STATION LASERP2
		ID = LASERMODEL;