I'm just getting started on MVS after all these years.  I was happy to
find BatchPipes installed on my system, even if it's ancient:

> pipe query level
> BatchPipes/MVS BatchPipeWorks, 5655-065/SCPSP level 1109001A        
> ***                                                                 

but less happy when a simple pipe failed:

> PIPE < t093.list|cons|specs
 ,listds ', 1 w3 n ,' members, n|tso
> |locate ,CEASAPI,|cons         

After listing 20 datasets, it gets:
                                                                     
> System abend code 0C4, reason code 00000004.                        
> Abend in host command RXG or address environment routine LINK.      
>      1 *-* address link "RXG" arg(2) || d2c(x.0, 4)                 
>        +++ RC(-196) +++                                             
> ABEND 000000 at 21898FD4; PSW 078D2000 A1898FD4                     
> ... Issued from stage 6 of pipeline 1                               
> ... Running "locate ,CEASAPI,"                                      
> ... In TESTRANG; offset 00000DC4 in BPWPAT   10/13/97 20.32         
> ... GPR0: 2181C540 00000000 000000C3 00000025                       
> ... GPR4: 431D63D4 0000001F 21767FF0 00000006                       
> ... GPR8: 2181C540 21811B30 00000000 2181C4D8                       
> ... GPRC: A1898FA0 2181C658 A1898FAE 00000001                       
> ... Store 21898FC8: 41F00001 47D0C080 5820B0E8 BD214000 4770C074    
> Abend 0C4000 hex occurred processing command 'PIPE    '.            
> ISPD210  CMD abended - 'PIPE' terminated abnormally.                
> ***                                                                 

Doesn't matter what stages follow TSO, it abends the same way at the same
point.  If I stick in a DROP 19 to start at the 20th data set, it runs
fine from there to the end, but even with DROP 18 it fails.  If I reverse
the list, it abends the same way but at different points in the list.

¬R

Reply via email to