My AS version is V7R2. If so it does not support syntax checking for IBM i 7. What you need to do is to turn off syntax checking in SEU. This post describes how to do it here. Thank you very much for Reply. Will try this option under change default settings. Hi Simon, Great article! Can you please also let us know, how to define a program described and primary files in RPG all free.. Neither the Input nor the Output specification has been converted to free format.
I had a great deal of trouble figuring out how to define a program defined printer file. Turns out, all you have to do is add the length as a parameter of Printer ex: dcl-f qsysprt printer ;. I believe is simple, defining the headers, details and totals lines in data structures and to print, only has to use the write command, using the structures previously defined and indicating the number of lines to skip before or after writing I think that is not hard to made Can someone put a little pgm source-code with these new definitions in it.
We are on V7. The question I have to ask is what are you "missing"? The code given above can be copy-n-pasted into the editor of your choice, therefore, you can take the definitions without a separate source with them all listed. Is there availability of declaring file in full free-form which is used for pre-run time array? If yes, can you please provide an example for the same.
Alas, this is not supported in free format RPG I was trying this a couple of weeks ago. To prevent "comment spam" all comments are moderated. Learn about this website's comments policy here. Some people have reported that they cannot post a comment using certain computers and browsers. If this is you feel free to use the Contact Form to send me the comment and I will post it for you, please include the title of the post so I know which one to post the comment to.
In the move to RPG all free the following specifications have been replaced: Control header specifications with ctl-opt File specifications with dcl-f Definition specifications with dcl-s and dcl-ds Procedure specifications with dcl-pr , dcl-pi , dcl-proc , end-proc Input and Output specifications remain in fixed format, I think this is a big hint from IBM that we should no longer be using these specifications.
Labels: programming , rpg. Buck February 12, at AM. Damery World February 12, at PM. Joe Baumgarten February 12, at PM. Simon Hutchinson February 12, at PM. Buck February 13, at AM. Rocky Marquiss February 13, at AM.
Russell Khoury February 13, at PM. Simon Hutchinson February 13, at PM. Vineet Kakroo February 13, at PM. Amit Sharma February 17, at PM. Simon Hutchinson February 17, at PM. Jim Mitchell February 17, at PM. Vern February 18, at PM. David Westaway February 20, at AM. Simon Hutchinson February 20, at AM. I have found that if I just use the underline it hides the column heading text when I view the spool file on the IBM i.
If I use the highlight the column heading text is displayed. The record format to print the detail lines is very simple, see below. There is nothing in it that should now be a surprise. I always add these to each report. This way the user knows if they have all the report or not by the presence of the "end of report" line. I know that there are other tools available from other vendors, but as I mentioned at the top of this post this is for a "vanilla" IBM i. I have given a link to the RLU manual at the bottom of this post as you are going to need help to use it.
And now to the RPG code to write my report using the printer file. I wrote this program in fully free RPG. For those of you still stuck with having to use fixed form definitions can see the equivalent of the definitions here.
If you think about it printer files are always output only. Lines 4 — 6: This is the indicator data structure. Lines 7 — This is the Program data structure. I am getting the procedure and user names to use in the printer file from here. Line If the indicator Pageoverflow is on the page headings are written and the indicator is set off.
Lines 23 — If the state code is "XX" then the indicator InvalidState is set on, as the Indicator data structure is qualified I need prefix the indicator's name with the data structures name. Line The write to the Detail record format has the error operation extender E. Without the operation extender an error would happen, and the program will halt.
I do need the operation extender just in case this line causes the page to overflow. By using printer files I can use the same file in multiple programs, or I can have variations of the same printer file in different libraries to produce reports with different layouts that all use the same RPG program.
I hope that with this very simple example you will refer to the IBM resources below, and make your own move from O-specs to printer files. You owe it to yourself if you are going to keep your RPG skills current. Print files is still DDS which really need to go away. There is always UIM as an alternative to display files.
It's helpful, I think, to have "source" definition for a file granted DDL contains a definition but it doesn't seem as absolute, somehow. Sorry that this went off topic. Nice overview, Simon. Thanks for sharing it here. I can see the post that I was looking for last three years!
Also, did the same for Internal DB files. This means that the file, record, and field descriptions are defined internally within the data division. Externally described printer file. Printer files that contain report specifications can be defined externally to any program that uses them. Two ways of making Externally described printer file:. Example Program described printer file. Display Spooled File File.
Columns 1 - Find. The designed screen by this DDS entry is as shown below.
0コメント