I suppose the return code means that the mode of the file in the AFT and the parameter list are different, which would indicate a storage overlay.
I've stored a NXPIPE at Marist that has message 120 enablet for trap. Refer to http://vm.marist.edu/~pipeline/nxpipe.vmarc for the updated module and to http://vm.marist.edu/~pipeline/traps.html for information on how to enable a trap. R11+B8 points to the FSCB. So, the trap could D TB8.80;BASEB. You cannot specify a CMS command to run (pipe aftfst would have been handy--I might think about that). You could also try >sfs. j. On 2 November 2010 01:40, Ian S. Worthington <[email protected]> wrote: > I have a largeish multistage pipeline which filters the input into separate > files. After running for a while it's started giving: > > PIPDSR120E Return code 16 from parameter list Vblockw MV0888 09 Z1. > > which seems to mean: > > 16 Record format specified not the same as file. > > which makes little sense to me from a ">" stage. > > viz: > > 16:32:18: 400000 records read > 16:32:30: 410000 records read > 16:32:42: 420000 records read > 16:32:55: 430000 records read > 16:33:10: 440000 records read > 16:33:28: 450000 records read > PIPDSR120E Return code 16 from parameter list Vblockw MV0888 09 Z1. > PIPMSG004I ... Issued from stage 2 of pipeline 49 name "AnalyseMsgs". > PIPMSG001I ... Running "> MV0888 09 Z". > PIPDSR120E Return code 16 from parameter list Vblockw MV0888 14 Z1. > PIPMSG004I ... Issued from stage 2 of pipeline 54 name "AnalyseMsgs". > PIPMSG001I ... Running "> MV0888 14 Z". > > From filelist: > > MV0888 09 Z1 V 133 245 9 11/01/10 > MV0888 14 Z1 V 312 107 6 11/01/10 > > I see that rc=15 may mean that the file has been erased, but that doesn't > seem > to be the case here. Any suggestions would be most welcome. > > i >
