Re: [netrexx-pipelines] LOCATE Stage name abbreviation: No

[René J. <rvj...@xs...>]

 pipe literal aap noot mies | locate /aap/ | cons           
aap noot mies                                               
Ready; T=0.01/0.01 00:53:16                                 
 pipe literal aap noot mies | split | locate /aap/ | cons   
aap                                                         
Ready; T=0.01/0.01 00:53:33                                 
 pipe literal aap noot mies | split | locat /aap/ | cons    
aap                                                         
Ready; T=0.01/0.01 00:53:41                                 
 pipe literal aap noot mies | split | loca /aap/ | cons     
aap                                                         
Ready; T=0.01/0.01 00:53:48                                 
 pipe literal aap noot mies | split | loc /aap/ | cons      
aap                                                         
Ready; T=0.01/0.01 00:53:58                                 
 pipe literal aap noot mies | split | lo /aap/ | cons       
aap                          
Ready; T=0.01/0.01 00:54:35                            
 pipe literal aap noot mies | split | l /aap/ | cons   
aap                                                    
Ready; T=0.01/0.01 00:54:58      

So here the implementation is different from the manual, or the manual is incorrect.

 pipe q version                                                                                                  
PIPINX086I CMS/TSO Pipelines, 5654-030/5655-A17 1.0112 (Version.Release/Mod) - Generated 30 Jul 2015 at 16:26:54.
Ready; T=0.01/0.01 00:57:17                                                                                      
                                                                                                                 


> On 26 Jun 2022, at 03:00, hp...@we... wrote:
> 
> Jeff!
> 
> Am 25.06.2022 um 22:21 schrieb Jeff Hennick:
>> Right now I can not find your message dealing with the *LOCATE* stage and, in
>> NetRexx Pipelines, not being able to abbreviate its name down to "L", to be able
>> to respond to it.
> 
> No problem, I remember well my complain.
> 
>> I have just spent several hours going through the IBM *CMS Pipelines User's
>> Guide and Reference /Version 7 Release 1/* (which as far as I can see is the
>> most recent) checking each documented stage and its aliases to be sure our
>> system matched and was documented correctly.  (The manual hides aliases in
>> different places for different stages and does not index them.  And on some
>> stages puts the name in all lowercase instead of all upper.)  I found a couple
>> of stages where we do not yet have the shortened name aliases, and will be
>> committing them and updated tests & documentation soon.
> 
> You spent several hours? Why didn't you use Pipelines? ;)
> It took me two minutes to access "my mainframe" and take the
> attached screen shot.
> 
>> As for using Hercules to look in the corners where the CMS documentation is not
>> clear, I want to work against the current VM/CMS Pipelines.  I don't think the
>> Hercules edition would help much if at all.  I'd like to be proven wrong on that.
> 
> You'd like it, you said. Is the screen shot sufficient enough?
> 
>> But, *LOCATE* is not one of them.  This is what the manual has:
>> [...]
> 
> You probably know, every program with more than 15 lines has at
> least one error, without fail. Same holds true for documentation.
> Alas, up to now I did not see an errata for 'the Book'.
> 
>> (I have not tried this myself.)  But adding it to the release now would likely
>> break some existing pipes.
> 
> Woot? Likely a lame excuse, methinks. Please present an example
> that explains when, how, why, and more about that break you suspect.
> 
> Best,
> M.
> <Locate.png>