From: <hp...@we...> - 2022-06-27 12:52:07
|
Hi! First, the good news: I replaced my simple attempt of > xlate 1 00-FF 3A 20-3F 20-3F 40-5F 00-1f 60-66 40-46 (what failed) by a even more simple 'a: xlate 1' and feeding the transliteration table (I prepared on another system) to secondary input. This option works as designed. Bad news, I have questions (one remark and a question): i) the NetRexx Pipelines Guide and Reference shows in the RRT diagram (RRT = Rail-Road-Track) for more than a single inputRange of XLATE to put it in brackets, but, as the repeat-track implies, to repeat also the brackets. That's wrong, same error in author's edition. > pipe literal aaaaaaa!xlate (1 5) a b!term > baaabaa > Ready; > pipe literal aaaaaaa!xlate (1) (5) a b!term > FPLXLA052E Unknown translate table "(5)". > FPLSCA003I ... Issued from stage 2 of pipeline 1. > FPLSCA001I ... Running "xlate (1) (5) a b". > Ready(00052); Same holds true for NetRexx Pipelines, with a slightly different error message and deviating RC. ii) the NetRexx Pipelines Guide and Reference shows as only "documentation" for XLATE a RRT-diagram, but no additional information than which of the default-table arguments are not implemented. (BTW, shouldn't 'UPper' stand above the "main track" since it's the default if no other arguments are entered?) Marked as not yet in Pipes for NetRexx are 'OUTput' and 'TO/FROM CODEPAGE n', but not 'INput'. For CMS input and output options of the XLATE stage are related to the input and output settings. Question: what is under Windows the corresponding parallel of CMS input setting? Best, M. |