Converter execution

Top  Previous  Next

Once the converter has been compiled, it may be run according to the instructions below. During its execution, the program reports :

input and output paths
record size
record converted number
last record read, if an error

Program will issue an error and stop if :

it can't convert a record because no rule for that record type is available
file size and record size are not compatible (this check is not applied for variable length record file)

Note: when using xvsamRts to start conversion programs, remember, by default, xvsamRts looks for files in the current XVSAM repository path by $XVSAM. Therefore it prefixes the path of input and output files by the repository path, unless the specified path is absolute (i.e. /some/where, C:\some\where), or is relative to the current directory iindicators "." and ".." (i.e. ../myfile, .\file.txt).

With Microfocus COBOL

On UNIX/Linux (Server Express)

To run the converter program, you have to use xvsamRts. On the command line, you have to provide input filename and output filename , eventually specifying paths.

xvsamRts <program> <input> <output>

I.e.:

xvsamRts FILE01 ../ebcdic/FILE01.EBCDIC ../ascii/FILE01.ASCII

On Windows (Net Express)

To run the converter program, you have to run the executable produced by cbllink. On the command line, you have to provide input filename and output filename , eventually specifying paths.

<program> <input> <output>

I.e.:

FILE01.exe ..\ebcdic\FILE01.EBCDIC ..\ascii\FILE01.ASCII

With ACUCOBOL

On UNIX/Linux

To run the converter program, you have to use runcbl. Before to execute it, you have to set the following environment variables:

export SHARED_LIBRARY_LIST=$XFRAMEHOME/lib/libxconv.so
export ERRORS_OK=1

Afterwards, on the command line, you have to provide the "-b" option, input filename and output filename , eventually specifying paths.

runcbl -b <program> <input> <output>

I.e.:

export SHARED_LIBRARY_LIST=$XFRAMEHOME/lib/libxconv.so
export ERRORS_OK=1
runcbl -b FILE01 ../ebcdic/FILE01.EBCDIC ../ascii/FILE01.ASCII

On Windows

To run the converter program, you have to use crun32. Before to execute it, you have to set the following environment variables:

set SHARED_LIBRARY_LIST=%XFRAMEHOME%\bin\libxconv.dll
set ERRORS_OK=1

Afterwards, on the command line, you have to provide the "-b" option, input filename and output filename , eventually specifying paths.

crun32 -b <program> <input> <output>

I.e.:

set SHARED_LIBRARY_LIST=%XFRAMEHOME%/lib/libxconv.dll
set ERRORS_OK=1
ccbl32 -b FILE01 ..\ebcdic\FILE01.EBCDIC ..\ascii\FILE01.ASCII

With OpenCOBOL

On UNIX/Linux

To run the converter program, you have to use xvsamRts. On the command line, you have to provide input filename and output filename , eventually specifying paths.

xvsamRts <program> <input> <output>

I.e.:

xvsamRts FILE01 ..\ebcdic\FILE01.EBCDIC ..\ascii\FILE01.ASCII

On Windows

To run the converter program, you have to use xvsamRts. Before to execute it, you have to set the following environment variables:

set COB_PRE_LOAD=libxconv
set COB_LIBRARY_PATH=%XFRAMEHOME%\bin;.

Then, on the command line, you have to provide input filename and output filename , eventually specifying paths

xvsamRts <program> <input> <output>

I.e.:

set COB_PRE_LOAD=libxconv
set COB_LIBRARY_PATH=%XFRAMEHOME%\bin;.
xvsamRts FILE01 ..\ebcdic\FILE01.EBCDIC ..\ascii\FILE01.ASCII

Overriding Codepage

Alternate codepages may be loaded by the XCONV library by exporting the XCONVCODEPAGE environment variable.

This environment must contain an absolute path name to an XFRAME codepage file.

I.e. (UNIX/Linux):

export XCONV_CODEPAGE=$XFRAMEHOME/etc/IBM930.tbl

I.e. (Windows):

set XCONV_CODEPAGE=%XFRAMEHOME%\etc\IBM930.tbl

Setting a DBCS conversion table

If the conversion requires a DBCS conversion table, the environment variable XCONVDBCSTABLE must be exported and and set to the full path of an XFRAME codepage table file.

I.e. (Unix/Linux):

export XCONV_DBCSTABLE=$XFRAMEHOME/etc/IBM-Kanji.tbl

I.e. (Windows):

set XCONV_DBCSTABLE=%XFRAMEHOME%\etc\IBM-Kanji.tbl

For further information about XFRAME codepage and DBCS tables, please refer to the XCICS/TS configuration documentation.