/ TEAMS · IBM i / RPG Engineering
Specify IBM i release, RPG/ILE, Db2 for i, CL programs, integration APIs and batch operations. IBM i is not the same platform as IBM z/OS mainframe.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
IBM i · Power Systems · Jobs
RPG IV / ILE · Free-form RPG
Db2 for i · DDS · SQL
REST · APIs · Data queues
CL · Batch · Security · Releases
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Senior IBM i / RPG Engineer — Db2 for i & Modernization
Available9+ years of experience · Czechia
IBM i / RPG Engineer — Db2 for i & Modernization with 9 years in production systems, focused on IBM i / RPG Engineer — Db2 for i & Modernization and Production systems.
Languages: Czech, English B2+
Senior IBM i / RPG Engineer — Db2 for i & Modernization
Available12+ years of experience · Lithuania
IBM i / RPG Engineer — Db2 for i & Modernization with 12 years in production systems, focused on Production systems and Technical delivery.
Languages: Lithuanian, English B2+
Mid-level IBM i / RPG Engineer — Db2 for i & Modernization
Available3+ years of experience · Poland
IBM i / RPG Engineer — Db2 for i & Modernization with 3 years in production systems, focused on Technical delivery and IBM i / RPG Engineer — Db2 for i & Modernization.
Languages: Polish, English B2+
Mid+ IBM i / RPG Engineer — Db2 for i & Modernization
Inquire availability7+ years of experience · Bulgaria
IBM i / RPG Engineer — Db2 for i & Modernization with 7 years in production systems, focused on IBM i / RPG Engineer — Db2 for i & Modernization and Production systems.
Languages: Bulgarian, English B2+
/ Specialist sourcing
Specify IBM i release, RPG/ILE, Db2 for i, CL programs, integration APIs and batch operations. IBM i is not the same platform as IBM z/OS mainframe.
Ask for a real RPG modernization or Db2 for i performance issue, with change control and preserved business processing.
Role-specific sourcing, not a promise of current candidate availability.
/ Engineering teams
Onectus sources engineering roles against the real operating environment rather than treating all legacy systems as one market. An IBM i specialist search should verify ownership of RPG business workflows, Db2 for i data access, batch processes and safe interface modernization. Candidates are assessed for the exact system release and responsibilities.
/ Technical specializations
Production IBM i work combines application language, database records, batch operations, job behavior and secure integrations. Differentiate long-term modernization from simple maintenance.
RPGLE, ILE modules, service programs, activation groups, procedural refactoring and modern syntax.
Embedded SQL, DDS and SQL-defined tables, record-level access, journaling and indexing tradeoffs.
CL commands, job queues, schedulers, message handling, spool files and operational recovery.
REST APIs, service programs, data queues, integration gateways and stable external contracts.
Incremental RPG modernization, refactoring, integration boundaries and coexistence with new systems.
Authority management, library lists, deployment controls, regression tests and production diagnostics.
/ Project scenarios
Extract interfaces and refactor carefully while preserving established business behavior.
Define secure service contracts and reliable calls into existing programs or Db2 for i data.
Investigate locks, job queues, journaling, data integrity and restart behavior.
Document business rules, build tests and reduce dependencies on undocumented RPG routines.
/ Practical evaluation
Recruiting should test concrete source-level, database and job-control scenarios—not rely on general COBOL or mainframe experience as a substitute.
Can the engineer explain their own service programs, activation groups, data structures and free-form migration?
How have they handled embedded SQL, locking, commitment control, access paths and journaling?
Can they investigate job logs, queues, message handling and failure recovery under production constraints?
How do they expose APIs, test older workflows, control authorizations and sequence changes?
/ Sourcing process
IBM i release, RPG/DDS footprint, Db2 for i, CL, workload and integration goals.
Identify IBM i/RPG engineers with relevant application and operations experience.
Discuss existing code, data access, CL jobs, business controls and modernization examples.
Agree access, security controls, timezone, documentation and availability.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
No. IBM i, RPG and Db2 for i differ materially from z/OS and COBOL mainframe environments. We screen against the actual platform.
Yes, when required. Specify code generations, ILE usage, release level and whether migration or ongoing support is the priority.
Yes. Define the IBM i service boundary, API security, data consistency and which programs or Db2 records need integration.
Yes. Share CL workloads, job scheduling, commitment control, journaling, recovery and on-call responsibilities.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
