No, "10" and "11" are not exactly the same as "0" and "1" but it may be that your program is taking the rightmost position of the number.
In CMS Pipelines, the specification says that "implied field length is 10 characters" and does not say it's right justified. If you only want the first position it is a blank unless you have a lot of records (or start counting with a large number). If you would do "number 1.1 r" you would get the rightmost digit of the number. Rob On Wed, 15 Dec 2021 at 14:28, René Jansen <[email protected]> wrote: > When we consider: > > pipe "literal aa | dup 10 | specs recno 1.1 w1.1 nw | cons” > > 1 aa > 2 aa > 3 aa > 4 aa > 5 aa > 6 aa > 7 aa > 8 aa > 9 aa > 0 aa > 1 aa > Ready; T=0.01/0.02 14:21:31 > > And then: > > pipe literal aa | dup 10 | specs recno strip 1 w1.1 nw | cons > 1 aa > 2 aa > 3 aa > 4 aa > 5 aa > 6 aa > 7 aa > 8 aa > 9 aa > 10 aa > 11 aa > Ready; T=0.01/0.02 14:23:03 > > We see exactly the same output. > We have tried to implement the specs of specs (ha) to the letter. We come > out at: > > Ready; pipe literal aa | dup 10 | specs recno 1.1 w1.1 nw | cons > aa > aa > aa > aa > aa > aa > aa > aa > aa > aa > aa > Ready; > 0.106 s > > The specs says to put the 10 digit right justified record number into 1.1, > that is into column 1 with a length of 1, which in these cases is a space > character. That is exactly what we see in the first column of the output > records in our own implementation. If CMS is displaying a digit, it is > doing an undocumented uncalled for strip. Or is it? We would like to know, > so we can can properly document the behaviour. > > (With thanks to Herman Kramer for the example and Jeff Hennick for the > analysis). > > Best regards, > > René. >
