We use RDz 184.108.40.206 and use the host code page IBM-1141 (Germany). So we get the exclamation mark (!) as OR sign and the double exclamatation mark (!!) as concatenation sign e.g.:
DCL STR CHAR(120);
DCL TRC CHAR(1) INIT('1');
DCL 1 BUF,
2 ASA CHAR(001) INIT(' '),
2 OUT CHAR(125);
IF TRC = '1' ! TRC = '2'
OUT = 'TRACE'!!STR;
WRITE FILE (SYSPRINT) FROM (BUF);
The PLI parser in the LPEX editor has some problems with this and tells
1. for OR(!): "ERROR TOKEN" unexpected token(s) ignored unexpected character ignored
1. for Concatenation(!!): "InfixOperators" is invalid
I know the workaround to change the host code page to IBM-1140, but we do not want to change the host code page, because our developers also use the IBM-1141-Codepage in the 3270 terminal emulation.
Can anybody help with this issue?
Pinned topic RDZ PLI Parser - Problem with OR and Concatenation
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-15T08:43:32Z at 2012-11-15T08:43:32Z by EberhardRamm
SystemAdmin 110000D4XK1086 Posts
Re: RDZ PLI Parser - Problem with OR and Concatenation2012-11-07T22:57:58ZThis is the accepted answer. This is the accepted answer.Hi,
By default, the PL/I parsing in the RD/z editors expects | as the OR character rather than !.
You can specify another OR character by using the OR compiler option in a property group.
If you specify OR('!') in the PL/I compiler options in a property group, then associate the property group, the parsing should work correctly. This should also fix the concatenation problem.
The PL/I compiler options can be specified by clicking on the PL/I tab, select Procedures and Steps, then choose the PLI step in ELAXFPL1. The Compiler options: field appears in the Step options section.
EberhardRamm 270000N8XG15 Posts
Re: RDZ PLI Parser - Problem with OR and Concatenation2012-11-15T08:43:32ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
RDz V220.127.116.11 - Real-time syntax check problem in Debug Source view, dated Oct 05, 2012.
Best regards Eberhard Ramm, SIBRA GmbH