2.
|
The environment variable COBCPY, which indicates to the Micro Focus COBOL Compiler-or COBOL-IT compiler where copybooks are stored, must be correctly set to include CICS Runtime copy files (cpylib) during compilation time.
|
•
|
KIX--DFHVALUE, if the DFHVALUE pseudo-function is used in the program or one of the copy files it includes;
|
prepro-cics.pl — A function that reads a COBOL program file from standard input, and outputs it with CICS instructions translated on standard output.
prepro-cics.pl takes a COBOL program as input, reads it line by line, and output a file with CICS instructions translated.
prepro-cics.pl performs only one pass and processes lines one by one. That is, it reads a line from the standard input, outputs one or several lines (it may output none depending on the output type), and then reads the next input line. This behavior enables it to be compatible for use as a preprocessor inside a compiler, but prohibits using the same file as input and output. Note that it will output lines at the end of the input file.
B indicates that the source is an EXCI program.
MQ_wrapper helps you migrate WebSphere MQ programs from mainframe to ART for CICS smoothly. On mainframe, programs explicitly do
MQOPEN and
MQCLOSE while mainframe implicitly does
MQCONN and
MQDISC. ART for CICS supports this way by enabling
MQ_wrapper. ART for CICS can translate WebSphere MQ four APIs (
MQCONN/MQOPEN/MQCLOSE/MQDISC) to its internal MQ API wrappers. Enabling
MQ_wrapper allows you to
•
|
Implicitly call MQCLOSE and MQDISC when an application transaction ABEND due to ERROR condition
|
If you do not specify MQ_wrapper, programs need to explicitly do all of the four APIs (
MQCONN/MQOPEN/MQCLOSE/MQDISC) to operate MQ.
notrec specifies the way instructions that are not fully supported are processed. (Some options of the instruction are not recognized, hence the "notrec"). There are two possibilities:
tsam determines whether the feature "TSAM call path for CICS and DB" is supported; recognized values are:
type_output determines the way that output is printed; recognized values are:
•
|
The two words EXEC and CICS must be on the same line for a CICS instruction to be recognized.
|
IGNORE and
HANDLE instructions messages are quite straightforward:
IGNORE should be constructed with
CONDITION.
•
|
<command> expects one of <keyword list>, but none is present.
|
•
|
<command> expects <keyword>, but couldn't find it.
|
•
|
In <command>, <keyword> expects either: … <keyword> (one of <keyword list>), … but none of them was found.
|
•
|
In <command>, <keyword> is present and not <keyword> even if they must be used at the same time.
|
•
|
In <command>, <keyword> and <keyword> cannot be used at the same time.
|
•
|
Default value of <keyword> is supposed to be computed with value of <keyword>, but its value (<value>) is not a charstring.
|
3.
|
If the program contains "EXEC SQL" statements, the preprocessor is asked to be executed ahead of db pre-complier commands (db2 prep for IBM UDB or pro*C for Oracle DB).
|
prepro-cics-C.pl — A function that reads a C program file specified by
source_file, and outputs the C program file with CICS instructions translated on
output file.
prepro-cics-C.pl takes a C program as input, reads it line by line, and outputs a file with CICS instructions translated.
prepro-cics-C.pl performs only one pass and processes lines one by one. That is, it reads a line from
source_file, outputs one or several lines, and then reads the next input line. This behavior enables it to be compatible for use as a preprocessor inside a compiler, but prohibits using the same file as input and output.
help shows the usage of
prepro-cics-C.pl.
source_format specifies the source format of C program. There are two possibilities:
•
|
fixed - (default) means that each line of a C program should be in fixed format.
|
•
|
free - specifies free style of C program.
|
Note:
|
Only fixed format is supported currently.
|
o specifies output file name and path.
B specifies that the source is an EXCI program.
•
|
/**/ is used for single line comments. Do not put a comment in the middle of an EXEC CICS command.
|
•
|
Keep EXEC CICS as a whole in one line.
|
•
|
#pragma will be automatically translated to comments.
|
•
|
Keep C main() function, its parameter list, and parenthesis in one line. For example,
|
•
|
PROGRAM should be constructed with EXCI LINK
|
•
|
LENGTH should be constructed with COMMAREA in EXCI LINK
|
•
|
DATALENGTH should be constructed with COMMAREA in EXCI LINK
|
•
|
RETCODE should be constructed with EXCI LINK
|