On 2019-06-20 6:36 PM, Paul Gilmartin wrote:
> In your example, what causes stage1, stage2, and stage3 to
> run consecutively rather than concurrently? Would FANIN rather
> than FANINANY make a difference?
FILLUP causes the input to be provided to each in order until it severs
its input (or
On Jun 20, 2019, at 4:20 PM, Glenn Knickerbocker wrote:
>
> On 2019-06-19 2:29 PM, Paul Gilmartin wrote:
{ stage1; stage2; stage3; } | stage4
>> Stages run in order, sharing input. So what isn’t consumed by
>> the first stage is available to the second, etc. But if a stage buffers
>>
On 2019-06-19 2:29 PM, Paul Gilmartin wrote:
>>>{ stage1; stage2; stage3; } | stage4
> Stages run in order, sharing input. So what isn’t consumed by
> the first stage is available to the second, etc. But if a stage buffers
> reads and doesn’t process the data, the effect is unpredictable.
> On Jun 19, 2019, at 2:00 AM, Rob van der Heij wrote:
>>{ stage1; stage2; stage3; } | stage4
>
> I understand this concatenates the output of the first three programs (in
> order?)
> and passes it as input to the fourth one. Cute. So what about input (it seems
> the
> first program in that
> On Jun 16, 2019, at 10:27 AM, Rob van der Heij wrote:
>
> On Sat, 15 Jun 2019 at 17:58, Phil Smith III wrote:
>
>> Gil wrote:
>>> No, you're thinking of ISPF.
>>
>> As infrequently as possible!
>
> LOL
>
> You will not believe how proud I felt when I finally got one John’s FMTP
> XEDIT
Gil noted:
>And I wished they had done likewise for synonyms and PF keys; everything.
Wow. In all the time I spent writing XEDIT mods and XEDIT applications, I never
even thought about this. I think I'd wish for it to be *possible* but not
*mandatory*. That is, a SETLOCAL command (or something
On Sat, 15 Jun 2019 at 17:58, Phil Smith III wrote:
> Gil wrote:
> >No, you're thinking of ISPF.
>
> As infrequently as possible!
LOL
You will not believe how proud I felt when I finally got one John’s FMTP
XEDIT macro working on TSO (it actually is tri-langual) with a bit of
plumbing to
Gil wrote:
>No, you're thinking of ISPF.
As infrequently as possible!
>Item: CMS ISPF is worse.
Well, yeah. Without even any details, we know this to be true!
>Item: I could leave my office, inadvertently leaving an XEDIT session
>running. At home I reconnected with a different terminal
On 2019-06-14 1:46 AM, Kris Buelens wrote:
> What about inserting a new line in the XEDITed file to indicate the end of
> the range (obviously a very special line that is unique).
> Then you'd use something like PIPE XEDIT ... | ToTarget
Still vulnerable if I may issue subcommands that change,
What about inserting a new line in the XEDITed file to indicate the end of
the range (obviously a very special line that is unique).
Then you'd use something like PIPE XEDIT ... | ToTarget
Kris Buelens,
--- VM/VSE consultant, Belgium ---
To explain my motivation more clearly in words here: I'm writing an
XEDIT macro and I want it to act on a range of lines between the current
line and a target just like native XEDIT subcommands. I want to do my
work in the pipeline, line by line as it reads the file from XEDIT, and
write output
On 2019-06-11 6:55 PM, Rob van der Heij wrote:
> On Tue, 11 Jun 2019 at 23:00, Glenn Knickerbocker wrote:
>> The "better handle" part is what I don't know enough about the guts of
>> XEDIT to know where to find, if there is one: some marker that stays
>> with the line as lines are moved, added,
You can have more than one instance of XEDIT, but only the “innermost”
instance has ownership of the XEDIT subcom environment. The other
instances are invisible. (Subject to cowboy programming.)
Regards,
Alan Altmark
IBM
> On Jun 12, 2019, at 10:13 AM, Paul Gilmartin
wrote:
>
>> On
On 2019-06-12, at 06:45:59, John P. Hartmann wrote:
>
>
> Bottom line: since cms 5.5, you can have only one XEDIT session within
> a virtual machine. (I could before, but the new storage management
> broke things.)
>
I had believed:
o ADDRESS CMS XEDIT starts a new XEDIT session; ADDRESS XEDIT
But suppose the record gets deleted by someone else? There really is no
answer here. Even if you do SAVE/RESTORE to isolate changes to scope
Bottom line: since cms 5.5, you can have only one XEDIT session within
a virtual machine. (I could before, but the new storage management
broke
Rob wrote:
>You're not looking for SET POINT are you? If your LOCATE is followed by a
>SET POINT .ABC you can find that line even when you insert or delete lines
>above it.
Exactly what I think he wants. SET POINT is way powerful, a great thing to have
in your XEDIT toolbox. I use it daily.
This is very close to silly, but it kept nagging until I had it working.
https://rvdheij.wordpress.com/2019/06/12/exploring-xedit-with-cms-pipelines/
On Tue, 11 Jun 2019 at 23:00, Glenn Knickerbocker wrote:
> The "better handle" part is what I don't know enough about the guts of
> XEDIT to know where to find, if there is one: some marker that stays
> with the line as lines are moved, added, or deleted above (maybe even
> including) it.
>
On 2019-06-11 7:43 AM, Rob van der Heij wrote:
> Right. I'm not aware of an interface to XEDIT that would allow a CMS
> Pipelines stage to access the content of the file without positioning it.
That sounds like the reverse of what I'm looking for. I want to ask
XEDIT where the target is in the
On 2019-06-10, at 22:45:37, Glenn Knickerbocker wrote:
>
>
> But the whole point is that I may want to issue XEDIT subcommands
> affecting lines beyond the target while the pipeline is running.
>
That sort of concurrency is unlikely to be supported; it's akin
to expecting two different users to be
On Tue, 11 Jun 2019 at 06:46, Glenn Knickerbocker wrote:
> On 2019-06-10 4:13 PM, Kris Buelens wrote:
> > There is also SET RANGE to limit which lines are available.
>
> But the whole point is that I may want to issue XEDIT subcommands
> affecting lines beyond the target while the pipeline is
On 2019-06-10 4:13 PM, Kris Buelens wrote:
> There is also SET RANGE to limit which lines are available.
But the whole point is that I may want to issue XEDIT subcommands
affecting lines beyond the target while the pipeline is running.
¬R
On 2019-06-10 3:39 PM, Donald Russell wrote:
> Pipe ahelp xedit
>
> Use it to read starting at the current line, use subsequent stages to
> select/do what you want.
As I said:
>> If I know I'm not going to add or delete
>> anything past the current line or change DISPLAY or SCOPE, I can use
>>
There is also SET RANGE to limit which lines are available.
Op ma 10 jun. 2019 21:40 schreef Donald Russell :
> See the XEDIT stage.
>
> Pipe ahelp xedit
>
> Use it to read starting at the current line, use subsequent stages to
> select/do what you want.
>
> Don
>
>
>
> On Mon, Jun 10, 2019 at
See the XEDIT stage.
Pipe ahelp xedit
Use it to read starting at the current line, use subsequent stages to
select/do what you want.
Don
On Mon, Jun 10, 2019 at 12:35 Glenn Knickerbocker wrote:
> Looking for an example of how to get a range of lines from XEDIT into a
> pipeline, I went to
25 matches
Mail list logo
