Hello, Mike.
I think you have a valid gripe here. I'm not particularly keen to spend
time proving that ottoscr is not compatible with CMS MT, given that it
was written in the late '70s.
I need reproducible test cases, please.
On 01/05/2015 12:00 PM, [email protected] wrote:
Am 01.01.2015 um 19:53 schrieb John P. Hartmann:
[..] I cannot check that all is as it should be.
Holler
if no and I shall fix it.
It seems to me there is an interference with Fullscreen CMS.
With Fullscreen ON following line in a exec drops variable t and
displays the answer from the CMS command.
"PIPE cms q text!var t"
Similar behaviour with
pipe cms q disk!hole
directly entered on the command line or in window CMS. I'd expect
as response nothing but Ready; alas it makes no difference if last
stage is hole or term. Suspend fullscreen and it works as
expected. It is neither *PIPSYSF nor *PIPLOCF nor *PIPUSER nor
*PIPPTFF nor Ron Hoffman's OTTOSCR (what is IMHO the reason for
the hint "FPLINY1291I The field ADMSCWR in NUCON is incorrect;"
every now and then).
BTW, "PIPE literal q text!cms!var t" works.
Could somebody please prove it - or is it related to the hardware
I use?
Ciao.....Mike
--------------------------------------------
Kostenlose E-Mail-Adresse mit unbegrenztem Speicherplatz f|r E-Mails, Free SMS
und OK-Drive, der Online-Festplatte.
Sicher Dir jetzt Deine Wunschadresse @ OK.de: www.ok.de
