The xatmigen tool

The xatmigen tool creates a local configuration file (LCF) from a file containing the local configuration definition (LC definition file) and one or more files containing C or COBOL data structures (LC description files), see diagram below:

Figure 20: Working with xatmigen

The local configuration file is structured in the same way as the LC definition file, and differs from this only in the description of the buffer type, buffer length, and buffer syntax string. In other words, the operands LEN=, SYNTAX=, and possibly TYPE= are added to the BUFFER statements compared to the definition file.

If the buffer type is not specified in the LC definition file, xatmigen configures the “smallest” value range for the buffer type, i.e. first the type X_COMMON.

All file names must be specified explicitly. If desired, a file can be created which contains the configuration statements for UPIC.

On Windows systems, success and error messages are written to the program window.

On Unix and Linux systems, success and error messages are written to stdout and stderr.

On BS2000 systems, success messages and error messages are written to SYSOUT and SYSLST.

Although in principle it is possible to edit the LCF, you are strongly advised not to do this.

Calling xatmigen

• On Windows systems xatmigen is called with

  xatmigen[.exe] parameter

  xatmigen.exe is located in the upic-dir \xatmi\ex directory.

• On Unix and Linux systems, xatmigen is called with

  xatmigen parameter

  xatmigen can be found in the upic-dir /xatmi/ex directory.

• On BS2000 systems, you start xatmigen with the following command:

  /START-XATMIGEN
  % CCM0001 PARAMETER EINGEBEN:
  * parameter

  When entering the command, you can, of course, use lowercase letters in place of uppercase letters.

You can specify the following parameters; the switches (-d, -l, -i, -c) must be written in lowercase.
The option -d and, if specified, the options -l and -c must each be followed by the associated parameter. Specification of an option without a parameter is not permitted.

[ upic ]
 -d lcdf-name
[ -l lcf-name ]
[ -i ]
[ -c stringcode ]
[ descript-file-1 ] ... [ descript-file-n ]

upic

If specified, a file xtupic.def containing entries for the configuration of the upicfile is created. The file is written to the current directory.

If specified, upic must be the first parameter in xatmigen. If the parameter is omitted, No configuration statements are created.

-d lcdf-name

Name of the LC definition file; mandatory specification

-l lcf-name

Name of the local configuration file to be created. The name must comply with the conventions of the respective operating system. It is advisable to choose a name with a maximum of 8 characters and add the extension “.lcf”.

Any existing LCF of the same name is automatically overwritten.

If the option is omitted, xatmigen creates the file xatmilcf in the current directory.

-i

Interactive mode, i.e. the string code is queried for each typed buffer containing a character array. The possible specifications for the string code are described under the “-c” option.

The -i option takes priority over the -c option, if this is specified. If xatmigen is running in the background or in batch mode, the -i option must not be specified.

-c stringcode

The specified string type applies for the entire xatmigen run, i.e. for all character arrays. In interactive mode (“-i”), the “-c” option is ignored.

The following values can be specified for stringcode (see table on "Typed buffers"):

C C! T T!

octet string octet string, terminated by '\0' T.61 string T.61 string, terminated by '\0'

If no specification is made, T! is used.

Individual characters are also interpreted as T.61 strings (stringcode= T!). Lowercase letters c and t are also valid.

descript-file-1... descript-file-n

List of files containing the include or COPY elements with the data structures of the typed buffers.

If the list is omitted, only the type X_OCTET is allowed.