This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

<span class="iconify mr-1 svg-loading" data-icon="mdi:arrow-left"></span>{{tag>category:"AREV32" author:"Donald Bakke" author:"bshumsky"}} [[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]] ==== Odd Characters in PDISK Output (AREV32) ==== === At 04 FEB 2023 09:52:34AM Donald Bakke wrote: === <QUOTE> So far only tested in OI 9.4.6 / AREV32. We are working on a new Arev 3.12 to AREV32 conversion. We recently noticed odd characters appearing in PDISK filename output. We tracked this down to using CATALYST("W", WinName) after the PDISK command was started. Upon closer inspection, the odd characters appear to be AREV screen commands, like color codes. This reminds me very much of the problem we encountered when using PUSH.SESSION/POP.SESSION in our OECGI calls. You had pointed out that those are AREV commands and they send screen commands to the engine and this was getting captured in the response stream. Is this a variant of the same problem? Is there a workaround or potential fix? [url=mailto:dbakke@srpcs.com]Don Bakke[/url] [url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url] </QUOTE> ---- === At 05 FEB 2023 06:50PM bshumsky wrote: === <QUOTE> <QUOTE>So far only tested in OI 9.4.6 / AREV32. We are working on a new Arev 3.12 to AREV32 conversion. We recently noticed odd characters appearing in PDISK filename output. We tracked this down to using CATALYST("W", WinName) after the PDISK command was started. Upon closer inspection, the odd characters appear to be AREV screen commands, like color codes. This reminds me very much of the problem we encountered when using PUSH.SESSION/POP.SESSION in our OECGI calls. You had pointed out that those are AREV commands and they send screen commands to the engine and this was getting captured in the response stream. Is this a variant of the same problem? Is there a workaround or potential fix? [url=mailto:dbakke@srpcs.com]Don Bakke[/url] [url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]</QUOTE> Hi, Don. Yes, the CATALYST "W" call also uses PUSH.SESSION and POP.SESSION, which means that it also sends out the commands to the engine to "do stuff", and those commands are (again) getting captured in the response stream. I guess you could call WINDOW() yourself, after setting @SENTENCE to be "WINDOW <parameter_name>" - thus avoiding the CATALYST's call to PUSH.WINDOW and POP.WINDOW, though I don't know what other implications that might have for your screen i/o...? - Bryan Shumsky [url=https://www.revelation.com]Revelation Software, Inc.[/url] </QUOTE> [[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=2AEAF4996E6E2C47B5920BCE4C817426|View this thread on the Works forum...]]