Speaking of fingers being trained: I've always used an IBM
101 keyboard ever since IBM started using pc's and my
fingers *still* can't get used to where the arrow keys are
on it! I think they remember a 3279-3x.
My first laptop, in 2009, gave me conniption fits until I
modified a 101 keyboard to add footpads (for air
circulation) and a PS/2 to USB adapter for it so it can
bridge the laptop keyboard. A small fan to the right of my
recliner adds some extra circulation and a usb driven
portable fan goes with me when I'm traveling. So I have the
same keyboard for both the laptop and desktop. With THE as
my editor, in Xedit mode, it's just about like being back on VM!
Les
Bob wrote:
Phil,
Thanks. You are right. I was trying too hard. Checking queued() was exactly
what I needed.
And yes, I am trying to get my VM and MVS environments to behave somewhat
alike. Like you said "fingers get trained". And, after 30+ years my fingers are
very well trained! The problem is that over the years I have spent time in both
camps so I have issues either way I go. My co-workers laugh because
my MVS world has always understood "QQ" & "FILE". (And I always have
'autosave' turned off.)
Right now I'm starting to do more in the VM world and I find that by using
PF7/PF8 all I succeed in doing losing my place in my document.
Going the other way, I keep wanting to use "X" in ISPF 3.4 ... and my dataset
just disappears!
So, SCROLL is destined to be assigned to all the pf keys I expect to scroll
the screen and make it behave more like ISPF.
And I would be happy to collaborate on making this happen.
(And I know you suggested that I contact you off-list, but I'm betting we are
not the only ones that would like these capabilities. And, we are probably
're-inventing the wheel' in many cases. Perhaps, we will get some others
offering tools that they have already created.)
Bob
On Sat, Aug 6, 2011 at 7:23 AM, Phil Smith III <li...@akphs.com> wrote:
Bob,
You're actually trying too hard: your macro should just look at QUEUED() and
see if there's something stacked.
This is a crude example, because you probably want to do more than just a
"LOCATE *" for a M (like EXTRACT /SCREEN and divide by 2, then make it
'COMMAND * -'n
or some such), but:
/**/
if queued() > 0 then pull op
else op = ''
if abbrev('MAX', op, 1) then 'COMMAND LOCATE *'
else 'COMMAND FORWARD' op
BTW, are you trying to do an SPF-ish environment in XEDIT? If so, please
contact me off-list -- I'd be interested in helping. Not that I think SPF is
better*, but I understand that the fingers get trained (now that I'm doing
z/OS, I find myself doing FIND instead of / in XEDIT and KEDIT sometimes!),
and it's been something that folks have talked about for a long time.
...phsiii
* Insert religious editor war here
-----Original Message-----
Bob <mvs...@gmail.com>
Subject: XEDIT Macro and Command Line Input
I'm struggling trying to write an XEDIT macro and hoping someone can help=
me=20
over a tiny stumbling block.
I want a pfkey set to a macro. ie. SET PF6 BEFORE MACRO SCROLL
And I want to be able to accept an *optional* command line parameter.
If there is always a command line parameter I seem to be able to use
"READ CMDLINE" to get it. However, this does not seem to work=20
when there is no command line parameter at all. I just get hung
at the "READ CMDLINE" until I hit <enter>. Also, when there is a
parameter I not only what to read it, but I want to "consume" it so that
it is no longer on the command line after my macro.
Is there a way to do this?
