XLATOR

XLATOR is designed to function in conjunction with a specially configured Remex paper tape reader/punch.

The XLATOR program performs two basic functions:

This allows you to edit the stored file. You can then punch the paper tape.

The baudrate for the paper tape punch is controlled by the environment variable UGII_TAPEBAUD in all operating systems. If this variable is undefined, the system defaults to 1200.

 

Editing the Punch File

The GPM punch file is stored as an ASCII text file until sent to the paper tape punch. This file accepts the full set of ASCII characters. The unprintable characters can be used by enclosing the octal value of the unprintable character within angle brackets.

The punch file can be edited in the same manner as any text file.

 

XLATOR File Formats

Intermediate ASCII format file - An intermediate ASCII formatted file is created which represents an EIA, ISO, or 7 BIT MCD tape format. This intermediate file is used as a storage medium for paper tape representations and can be edited as an ASCII file.

There are several ways this file can be created:

EIA Machine Control Data (MCD) format - Through the XLATOR the ASCII file can be translated to EIA format. This data then exists as an NC tape EIA MCD image. EIA MCD image has an odd number of bits. The image can be stored as a binary file or it can be output directly to the paper tape punch. The binary file cannot be edited.

ISO MCD format - Through the XLATOR the ASCII file can be translated to an NC tape ISO MCD image. ISO MCD image has an even number of bits. The image can be stored as a binary file or output to the paper and tape punch. The binary file cannot be edited.

7-BIT MCD format - Through the XLATOR the ASCII file can be translated to a 7-Bit ASCII MCD image and stored in a binary file or it can be sent directly to the punch or some DNC file.

 

XLATOR Punch and Render Structure for VS

Since every system can have their punch and reader connected in different ways the translator uses specific queues to the devices. The punch queue is 'PTP' and the user must have created this as a link to the actual punch. For the reader the queue is 'TAPEIN' and this must be linked to the reader. These links are created during installation. To punch, the queue must be started with the following commands.

CONTROL @EXEC START PTP @CONXX

CONTROL @EXEC PRI/PRE @CONXX 1

CONTROL @EXEC CONTINUE @CONXX

The TERM and PUNCH buttons on the REMEX paper tape controller should be depressed for punching. The user can now punch but cannot read. To read, the punch queue must be stopped.

CONTROL @EXEC STOP @CONXX

On the REMEX the TERM, REMOTE and READ buttons must be depressed. If the tape does not start to read when the XLATOR read command is given then momentarily take the remote button off and then depress again. The tape should start to read. To punch after reading start the punch queue again.

 

XLATOR Punch and Render Structure for VMS

To punch a tape, the PUNCH and TERM buttons on the REMEX should be depressed. To read, the tape must be loaded before the XLATOR is executed. The TERM, REMOTE and READER buttons on the REMEX should be depressed. The logical, 'UGPTR', must be linked to the system paper tape punch and reader. If the reader/punch is connected as a modem, MODEM should be depressed instead of TERM. For more information on the paper tape on VMS refer to the VMS Installation and System Management manual.

 

XLATOR Punch and Render Structure for UNIX

To punch, the PUNCH and TERM buttons on the REMEX must be depressed. To read, the tape must be loaded before the XLATOR is executed. The TERM, REMOTE, and READER buttons on the REMEX should be depressed. The file, "ptp", must be linked to the system paper tape punch and reader. The link is a file with the equivalent address of the line which the user wishes to use for the paper tape punch connection. This file must be in the default UGII directory, which is identified with the "UGII_ROOT_DIR" environment variable. Refer to the Installation and System Management guides for additional information.

 

XLATOR Punch and Render Structure for Windows NT

To punch, the PUNCH and TERM buttons on the REMEX must be depressed. To read, the tape must be loaded before the XLATOR is executed. The TERM, REMOTE, and READER buttons on the REMEX should be depressed. The communications resource to which the paper tape punch and reader is attached and must be defined. The mechanism to do this is the environment variable UGII_PTPCOM. If this variable is undefined, the system defaults to COM1.

 

XLATOR Execution

VAX/VMS - There are three ways in which XLATOR can be called in the VAX operating system. An operating system command line utilizing an assigned logical name can be called. A macro can be created with its own logical assignments. Finally, the filename can be substituted in place of the GPM name in the NX postprocessor menu.

Define symbols in the LOGIN macro

$ XL*ATOR :== "UGII_ROOT_$DIR:XLATOR"

XLATORU

Will call in XLATOR.

XL/

Will call in XLATOR with interactive login prompts. This is equivalent to 'R XLATOR' for XLATOR.EXE(V4.1)

$POST:==UGII$DIR:XLATOR

$EXIT

UNIX - There are three ways in which XLATOR can be called in the UNIX operating system. The file name can be typed to call XLATOR with interactive logon. The second method is to create a macro with these switches which can include input from a file. Finally, the file name can be substituted in place of the GPM name in the NX postprocessor menu.

Macros - Create input file name: punch.txt

1

 ;comment Option 1 - Punch a tape

name.ptp

 ;comment filename

;comment In case file doesn't exist

8

 ;comment Option 8 - Exit XLATOR

Create file to run xlator using punch.txt for input tape :

xlator - <punch.txt

Windows NT - There are two ways in which XLATOR can be called in the Windows NT operating system. The file named xlator.exe can be typed to call XLATOR with interactive logon. Also, the file name can be substituted in the NX postprocessor menu.

 

XLATOR Menus

The user is presented with a series of questions outlining each function of the translator. At this point you can also exit. Below is an example of the XLATOR menu questions:

PUNCH a EIA or ISO MCD* text file
CONVERT a EIA or ISO MCD* text file to a mcd* binary file

PUNCH A 7-BIT MCD* text file

CONVERT A 7-BIT MCD* text file to a binary file

READ IN A EIA, ISO, or 7-BIT MCD* tape to a text file

CONVERT A EIA, ISO, or 7-BIT MCD* binary file to a text file.

VERIFY A EIA, ISO, or 7-BIT MCD* tape against a text file.

EXIT from XLATOR

 

MCD* = Machine Control Data (EIA, ISO, or 7-BIT FORMAT)

"binary refers to the punched tape image"

MCD* = Machine Control Data

"binary" refers to the punched tape image

For selections Punch A EIA Or ISO MCD* Text File or Punch A 7-bit MCD* Text File, you are asked for the name of the input text file.

For selections Convert A EIA Or ISO MCD* Text File To A MCD* Binary File or Convert A 7-bit MCD* Text File To A Binary File, you are asked for the names of the input text and the MCD output file.

For selection Read In A EIA, ISO, Or 7-bit MCD* Tape To A Text File, you are asked for the type of MCD input format and the name of the output text file.

For selection Convert A EIA, ISO, Or 7-bit MCD* Binary File To A Text File, you are asked the MCD input file name, the type of MCD input format, and output text file name.

The XLATOR identifies the type of MCD code when it reads the TEXT file. When reading from the paper or tape reader or converting a MCD file you have to specify the type of MCD code.

For selection Verify A EIA, ISO, Or 7-bit MCD* Tape Against A Text File, you are asked for the type of MCD input format and the name of the input text file to compare against.

The MCD input format for the tape parity and END OF BLOCK code is chosen by the use of the following three menus. The first menu appears for selections 5, 6, and 7 of the XLATOR main menu. It also appears for punching if XLATOR cannot find the standard END OF BLOCK codes to determine parity.

PUNCH OUTPUT CODE PARITY FORMAT
EIA (ODD PARITY PUNCHES)

ISO (EVEN PARITY PUNCHES)

7-BIT ASCII MCD

The second menu appears ISO is selected above.

PUNCH END-OF-BLOCK CODE FORMAT
ISO, CR ONLY

ISO, LF ONLY

ISO, CR,LF

ISO, LF,CR,CR

ISO, $

ISO, *

ISO, USER DEFINED

The third menu appears if EIA of the first menu is selected.

PUNCH END-OF-BLOCK CODE FORMAT
EIA, <EOB>

EIA, $

EIA, *

EIA, USER DEFINED

If a User Defined end of block code is selected, these menus come up. The desired code is typed in for entry 1. Non-printable characters are represented by octal numbers in angle brackets: <000> is a null code, <128> is the <EOB>. The length of the character string that represents the END OF BLOCK code is typed for EIA, $. Any string of characters within brackets is translated to a single punch code on a punched tape.

USER DEFINED END-OF-BLOCK
USER DEFINED END-OF-BLOCK CHARACTER STRING

LENGTH OF USR END-OF-BLOCK CHARACTER-STRING

ENTRY COMPLETE

DEFINE THE CHARACTER STRING FOR USER DEFINED END-OF-BLOCK CODE. SPECIFY UNPRINTABLE CHARACTERS BY ENCLOSING THEIR 3-DIGIT OCTAL VALUE IN ANGLE BRACKETS (EXAMPLE: ESCAPE = <033>).

ENTER CHARACTER VALUE:

If selection 2 was made above, this menu appears:

SPECIFY THE LENGTH OF THE USR END-OF-BLOCK CHARACTER STRING (LENGTH = NUMBER OF CHARACTERS. EXAMPLE: LENGTH OF <033> = 5).

ENTER NUMERIC VALUE:

When the verify function is executed, the tape is read into a temporary file and compared with the designated TEXT file. The program returns the message "tape verifies" if there are no discrepancies in the MCD blocks that are compared. It also outputs the number of blocks that are compared. LEADER and PARTNO characters before the first MCD block are ignored. If XLATOR finds discrepancies in the comparison, the program outputs the number of blocks that have been processed before the difference is encountered and the contents of the blocks for both files. After five error blocks are processed, the program returns to the XLATOR menu.