at 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
---
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
>
> ---
Les Koehler wrote:
>Isn't there an SPF macro package in the VM Download Library?
>In the old days of IGS in Tampa we had a lot of folks that
>had the same problem you have and I know I saw it resolved
>more than once. But maybe none of those solutions found
>their way to the Library (sigh).
Ye
time.
...phsiii
* Insert religious editor war here
-Original Message-----
Bob
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 S
siii
* Insert religious editor war here
-Original Message-----
Bob
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
lot of the XEDIT details have faded from my memory, so you
might have to experiment or wait for a post from a more
active XEDIT user. These days I pretty much use it to
compare THE on the pc against it.
Les
Bob wrote:
I'm struggling trying to write an XEDIT macro and hoping someone can hel
I'm struggling trying to write an XEDIT macro and hoping someone can help
me
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 se
"Huegel, Thomas" wrote:
>I have a simple question about a XEDIT macro.
>I have a macro that does a locate and select on some lines and then
>displays the selected lines.
>My question, is there a way to find the number of lines that have been
>selected without count
k.edu] On Behalf
Of Roy, Bruce
Sent: Tuesday, May 12, 2009 12:35 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: XEDIT macro question
Check out the SET SCOPE command (ie, SET SCOPE DISPLAY) and 'EXTRACT
/NBSCOPE/'. While many of the EXTRACT options can be QUERY'd, the NBSCOPE
optio
Check out the SET SCOPE command (ie, SET SCOPE DISPLAY) and 'EXTRACT
/NBSCOPE/'. While many of the EXTRACT options can be QUERY'd, the NBSCOPE
option can only be used through EXTRACT. I assume the code below is part of
some larger XEDIT macro since by itself it would have
I have a simple question about a XEDIT macro.
I have a macro that does a locate and select on some lines and then displays
the selected lines.
My question, is there a way to find the number of lines that have been selected
without counting them as I select them?
EXTRACT '/selected
gt; [mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij
> Sent: Thursday, March 19, 2009 1:46 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: XEDIT Macro
>
> On Thu, Mar 19, 2009 at 7:41 PM, Schuh, Richard
> wrote:
>
> > That gives a list of line numbers and prefix areas fo
On Thu, Mar 19, 2009 at 7:41 PM, Schuh, Richard wrote:
> That gives a list of line numbers and prefix areas for the changed lines.
But only for the ones that don't have a meaning or are not complete
yet, right? So using an "i" in the prefix area would be executed and
not returned to you as a pen
aflamme
Sent: Thursday, March 19, 2009 11:10 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: XEDIT Macro
On 3/19/2009 12:54 PM, Schuh, Richard wrote:
Problem solved. Thanks to all who replied.
You think you'
On 3/19/2009 12:54 PM, Schuh, Richard wrote:
Problem solved. Thanks to all who replied.
You think you're going to get off that easy? A few of us are curious
about what worked or what had to change for anything to work. After all,
you were rather detailed about what didn't work, we can't help bu
@LISTSERV.UARK.EDU
Subject: Re: XEDIT Macro
the "XEDIT User's Guide" might help you; it has examples and
guidance on writing prefix macros and using READ
From: The IBM z/VM Operating System
[mailto:ib...@listserv.uark.edu] On Behalf Of
the "XEDIT User's Guide" might help you; it has examples and guidance on
writing prefix macros and using READ
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Schuh, Richard
Sent: Wednesday, March 18, 2009 4:45 PM
To: IBMVM@LISTSERV.UARK.EDU
Subje
Rob van der Heij wrote:
>When you issue the READ you get control back when the user hits an AID
>key. At that point there's one line stacked for each change on the
>screen. You can decide whether XEDIT should update the file being
>edited or not. When you have processed the stacked lines, you issue
em
>> [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens
>> Sent: Wednesday, March 18, 2009 3:22 PM
>> To: IBMVM@LISTSERV.UARK.EDU
>> Subject: Re: XEDIT Macro
>>
>> By default, the values in the prefix areas are the line numbers, no?
>> Or, if you&#
I think it would stil be wise to precede a READ by
address command 'CONWAIT'; address command 'DESBUF'
This assures that the terminal input buffer is emptied, with PARSE
PULL one only empties the program stack.
Alternatively: codedo queued()+externals() ; parse pull ; end
2009/3/19 R
On Thu, Mar 19, 2009 at 12:48 AM, Schuh, Richard wrote:
> No. I have not figured out how to use READ to do what I want. So far, I
> have succeeded only in getting the command line stacked; none of the
> file lines, changed or not. So how is it done?
When you issue the READ you get control back wh
mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij
> Sent: Wednesday, March 18, 2009 4:20 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: XEDIT Macro
>
> On Thu, Mar 19, 2009 at 12:10 AM, Schuh, Richard
> wrote:
> > Do not assume that normal defaults are in
n the prefix area which has been set to NULLS by the profile.
And you don't control the entire navigation with an XEDIT macro using
the READ subcommand?
If you can do that, you get the entries back tagged with a PRF
Rob
Schuh
> -Original Message-
> From: The IBM z/VM Operating System
> [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens
> Sent: Wednesday, March 18, 2009 3:22 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: XEDIT Macro
>
> By default, the values in the p
> Sent: Wednesday, March 18, 2009 1:48 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: XEDIT Macro
>
> Schuh, Richard wrote:
>
> Is there any way to access the prefix area of a line from an XEDIT Macro? I
> see nothing in the EXTRACT command. Am I missing something there? Is ther
] On Behalf Of Rich Smrcina
Sent: Wednesday, March 18, 2009 1:48 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: XEDIT Macro
Schuh, Richard wrote:
Is there any way to access the prefix area of a line
from an XEDIT Macro? I see nothing in
On Wed, 18 Mar 2009 13:45:05 -0700, Schuh, Richard wrot
e:
>Is there any way to access the prefix area of a line from an XEDIT
>Macro? I see nothing in the EXTRACT command. Am I missing something
>there? Is there some other way to access it?
Here is a more complete example which
On Wed, 18 Mar 2009 13:45:05 -0700, Schuh, Richard wrot
e:
>Is there any way to access the prefix area of a line from an XEDIT
>Macro? I see nothing in the EXTRACT command. Am I missing something
>there? Is there some other way to access it?
If you are looking to see what commands a
SET 'PREFIX SYNONYM CD PREFIXCD'
SET 'PREFIX SYNONYM CCD PREFIXCD'
SET 'PREFIX SYNONYM MD PREFIXMD'
SET 'PREFIX SYNONYM MMD PREFIXMD'
SET &
Title: XEDIT Macro
Schuh, Richard wrote:
Is there any way to access the prefix
area of a line from an XEDIT Macro? I see nothing in the EXTRACT
command. Am I missing something there? Is there some other way to
access it?
Regards,
Richard Schuh
That begs a question: What
Is there any way to access the prefix area of a line from an XEDIT
Macro? I see nothing in the EXTRACT command. Am I missing something
there? Is there some other way to access it?
Regards,
Richard Schuh
Thanks to everyone - the Box macro from Fran is the closest to what I'm
looking for. I'll take that and adjust for my purposes.
Thanks again - as usual this list is very helpful
Lionel B. Dyck, Consultant/Specialist
Enterprise Platform Services, Mainframe Engineering
KP-IT Enterprise Enginee
Oh, and shipped on the CMS disks, as far as I recall, is SCM XEDIT
that aligns the comment in REXX code.
You may find a slightly more recent SC XEDIT on the CMS Pipelines
homepage (along with the left-handed FMTP which is is huge help).
Rob
The PRFMINE XEDIT macro, part of
http://www.vm.ibm.com/download/packages/descript.cgi?GD-XEDIT
has a CMTB prefix command to make a new, empty, comment box. But,
when entered one a label line like this
MySubroutine: /* perform a check */
it gets converted to
I have an XEDIT macro that operates as a prefix command. It turns specified
lines into comments. It has the ability to turn blocks of lines into comments,
as well. Here is an example using a snippet of code from SMTPNOTE EXEC:
Before - note the asterisks in the prefix area. That is the synonym
/** BOX XEDIT
**
** Inserts a comment box at the line the BOX command entered.
**
** Author: [EMAIL PROTECTED]
** Date: 15-Sep-2005
**
**/
trace off
parse source . . . . . name .
arg pref func pline op extra
if pref \= 'PREFIX' then call error1,
'This macro must be invoked
I don't know about what "anyone" did, the best I
can offer is my "change all of these lines to comments"
macro.
Shimon
Original message
>Date: Tue, 15 Apr 2008 13:57:46 -0700
>From: "Lionel B. Dyck" <[EMAIL PROTECTED]>
&
Has anyone developed a xedit command similar to the comment z/os ispf
command (from the cbt tape) that they would be willing to share?
The ISPF Comment command syntax is something like this:
Comment comment-text
with an A (for after) or B (for before) on the desired line within the
ISPF edit t
38 matches
Mail list logo
