• Validman Improvements
• An alternative to using LISTPGM
• Validation Kick Back
  • Validations Where Used
  •  File Where Used
• Carried Forward Accounting Updates
• Secondary Update - Field Moves
• DIALOGUE Boxes
• Point & Click (P&C)
• More Program Logic Override features
• Multi-Lingual Software
• F1 = HELP
• Use of the DUP key
• Access Map from spec
• Source Debugger
• Improved Spec. Export / Import
• Group Total Reports
• Drawing Flowcharts
• File Where Used Improvements
• Parameter Data Structure
• Field Where Used In Program
• GROUPS - A reminder
• Auto-Specifying Windows
• Screen Heading / Trailer Displayed in Formatters

Parameter Data Structure
@@PMDS

Sites that have set up a Parameter Data Structure have found that when they are setting up program call parameters they are constantly warned that the PMDS field they are priming with a move does not exist and it asks you tou define it in section 4 as FLDNAM *DSF. This impacts on productivity somewhat, so we have introduced a way of avoiding this hold up. If you define a file spec named 'GV@@PMDS' with the field names that make up your parameter data structure, the parameter entry field will not give warnings if you move a field to a FLDNAM that has been specified in GV@@PMDS. When this file is Generated and Compiled, it will be used by Genesis V as an external definition, so that the Source definition in GVMACROS or QGENSRC (which was the old way of using @@PMDS) can be deleted.