I see many jobs listed with similar requirements for RPG, something like:
To be considered for this position, applicants need to meet the qualifications listed in this posting.
- 5+ years of development on IBM i (iSeries, AS/400) using all of the following: RPG-ILE, RPG-Free, SQL and CL
- 3+ years’ experience with SQL and the use of SQL constraints, stored procedures and cursors.
- 3+ years’ experience with SQL queries accessing large data sets. Proficiency in SQL performance analysis, indexing and embedded SQL is a plus.
- 3+ years of application design and writing technical design documents for RPG projects.
- 3+ years’ experience in full Software Development Life Cycle.
- 3+ years’ experience with a software change management (SCM) system for IBM iSeries development such as ALDON CMS, Aldon Lifecycle Manager, or Implementer, etc.
I cover these areas and more:
- I have been covering these areas considerably longer than the Minimum required years working with any of these subjects, RPG since before IBM i (iSeries, AS/400) existed.
- Very familiar with SQL (JOINS, INNER, OUTER, UNION etc).
- I would never use anything but dynamic, embedded SQL in an RPG program unless the Customer requested the use of standard file I/O, if an older program was being modified opposed to rewritten I would also check with the Customer as to which approach they would like me to take.
- One area of importance would be QA standards, in the UK my code/design/testing was audited to BS5750 standards and in the USA the same applied but for ISO 9000. That type of auditing requires writing technical design documents, test plans, test proof etc.
- I have designed, coded and implemented several major projects often involving IBM i Request/Response to a Web Service (placing sales orders in System/21, sending vehicle configurations to Visiprise MES, recreating MRP run without the update to gather the requirements to send notification to an off site warehouse so it could deliver components in time for them to be consumed by the manufacturing process and many more) these were often from scratch, starting with me attending the initial meeting, taking notes, raising issues then developing a solution.
- For (SCM) I am familiar with Turnover and Implementer.