RPGLE EDIT WORD O SPEC HOW TO

Other codes become a bit cryptic as you have to know which column the code is in to know what it does. Fortunately I can position fields in relation others by using the likes of ' + 1'. When adding the individual fields to the O-specs I have to remember that the number I enter is the end of the field. The second was in RPGLE where I use the Except operation code: OFilename++DF.N01N02N03Excnam++++B++A++Sb+Sa+ The first was written in RPGIII and used the RPG cycle: OName++++DFBASbSaN01N02N03Excnam I wrote two programs to produce the same report. But this post is going to assume that this is a 'vanilla' configuration of IBM i with none of those tools present. I know that there are tools to convert O-specs to externally described printer files, and I have used a couple myself.

RPGLE EDIT WORD O SPEC HOW TO

I am writing this post in response to a couple of people who contacted me asking about the differences in coding printer files, to O-specs, and how to write the RPG to use them. So this is the time to move away from O-specs and embrace printer files. If you start programming in ' fully free' RPG, 7.2 TR1 and 7.1 TR11 November 2014, you will find that you cannot easily use non-free format code, such as O-specs.

The end of the usefulness RPG's Output specifications, O-specs, was signaled by IBM when they did not give a free format equivalent when they gave us ' free format definition' RPG, IBM i 7.1 TR7 in November 2013.

Rpgle edit word o spec