Browse Prior Art Database

Translator/ Validator Program

IP.com Disclosure Number: IPCOM000122432D
Original Publication Date: 1991-Dec-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 3 page(s) / 120K

Publishing Venue

IBM

Related People

Thompson Jr, SW: AUTHOR

Abstract

During the development of OfficeVision*/MVS (OV/MVS) it became apparent that current customers of pre-existing products who wished to migrate to OV/MVS would need utilities to migrate their users and their data to OV/MVS. Userids, in some cases, would need to be translated from one code page to another and the resulting names would have to be acceptable to OV/MVS. These requirements dictated the need for a translator and validator routine which would be flexible enough to handle a variety of translations and validations.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 44% of the total text.

Translator/ Validator Program

      During the development of OfficeVision*/MVS (OV/MVS) it
became apparent that current customers of pre-existing products who
wished to migrate to OV/MVS would need utilities to migrate their
users and their data to OV/MVS. Userids, in some cases, would need to
be translated from one code page to another and the resulting names
would have to be acceptable to OV/MVS.  These requirements dictated
the need for a translator and validator routine which would be
flexible enough to handle a variety of translations and validations.

      It was decided to design and implement a routine which was non-
specific and input driven so that it could accommodate many varied
translate and validation requests. This routine utilizes tables which
are tailored to translate for any combination of input to output data
streams and to validate input data streams to identify user specified
invalid data.  A master table is used to identify a specific
translate table when a parameter match is made in the master table.
When the specific translate table is loaded, it is used as a
translate table against data passed to the translator. When
indicated, an input data stream is checked for validity by using a
translate and test function against an identified translate and test
table.

      Input to the translator consists of an 11-character code page
identifier of the data format which is to be translated and an
11-character code page identifier of the final data format.  After a
master table is loaded, these "from" and "to" format indicators are
matched in the master table to identify the name of the table which
is to be loaded for translations.  Part of the input to the
translator consists of a "from" and a "to" address set which points
to the data to be translated and to where the translated data is to
be returned.

      One of the advantages of the translator is that only the name
of the master table needs to be known by the translator so that it
may be loaded to reference other tables.  These other tables may be
built to accomplish the necessary translation.  They are simply
256-byte tables, each byte referenced by offsetting from the table
base by the value of the "from" data stream byte.

      By examining the input parameters to the translator some of the
other advantages of its use may be seen.  Up to four separate
parameter sets may be processed in one request, each set being
comprised of "from" and "to" code sets, "from" and "to" data
addresses and flag settings.  By allowing four sets, the requestor is
able to translate through intermediary stages prior to the final
stage translation.
      INPUT:        CL11  From code page ID     (00000-00500)
 (up to four sets)  CL11  To code page ID       (00281-00277)
                    CL1   First or next call    (F/N)
                    CL1   Another list flag     (Y/N)
       ...