Dave
Clist means "command list" and is a generic term. REXX is an interpretive
language, in principle, consisting of commands which do something and
commands which direct logic - to describe it loosely. Thus REXX is a
particular example of a clist language.
Probably you have in mind the original TSO clist language as distinct from
REXX. The original TSO clist language is another specific example of a clist
language. I have also worked with VM and NetView which also have their own
clist languages and I am vaguely aware of many others. Actually, there's
even one I use on my PC which is very clever in manipulating "windows".
You'll note I used the expression "in principle" above - since I'm aware
that REXX can be compiled and so isn't simply interpretive, the usual
characteristic of a clist language.
I also used the expression " in principle" in the post to which you refer
when stating that logmodes and related matters are irrelevant. The reason I
contend that it is irrelevant is that the possibility to create a nondisplay
field is part of the *original* 3270 data stream. It's possible that there
is some sort of indirect relationship and your experience is that there
would appear to be such a relationship. I have a "gut feeling" it may be
related to those top two bits in the 3270 byte. I'd have to go pouring
through the manual to try to follow up on that idea.
Since you can reproduce the circumstances where Tomas's clist works and
doesn't work, you are ideally placed to determine what the difference in
specifically the "start field" "order" character is in the two cases using
the blunt instrument of the VTAM buffer trace or the fine instrument of the
NetView Session Monitor TRACE command with CPIU (complete PIU). Naturally,
it would be of great interest to know which of the fields in the logmode
table entry was actually responsible for allowing Tomas's "start field"
"order" character to be recognised, how it was set to allow recognition and
how it was set to disallow recognition.
We all await your discoveries - on tenterhooks.
Incidentally, I checked your previous posts in this thread and I don't see
you saying you got it to work.
Chris Mason
----- Original Message -----
From: "Dave Salt" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Sunday, March 25, 2007 5:13 AM
Subject: Re: REXX Question (subject too broad)
>From: Chris Mason <[EMAIL PROTECTED]>
What is being talked about here is a feature of the *original* 3270 data
stream, namely the creation of a nondisplay field.
In principle, this means that logmodes and related issues are totally
irrelevant.
I think you're mistaken. I couldn't get the non-display field to work
until I changed my logmode.
It works with some emulators and not others and - I think - when it
doesn't
work, it's because the 3270 "order" characters are not being recognised.
I didn't change my emulator; all I changed was my logmode.
Pouring through the 3270 manual mentioned earlier might solve this but
another way - for someone with a working setup and NetView Session Monitor
to hand - using TRACE CPIU of course - could be to check that the start
field
sequences used in the usual output from TSO are using the same character
values as the REXX Clist.
FYI: There is REXX, and there is CLIST. But never the twain shall meet.
Dave Salt
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
