Contact person: Business Client

Phone:Show

Email:Show

Location: Noida, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I’m looking for an experienced IBM i / AS400 developer who can extend our current application by building a rock-solid integration layer to external systems while also adding a few new user-facing features. The core platform is already stable; what I now need is code that lets it talk seamlessly to third-party services and data feeds so the business can retire several manual hand-offs.

You’ll be working directly on our production LPAR, so deep comfort with RPG IV/ILE, embedded SQL, CL, and the standard IBM i APIs is essential. If you prefer using tools such as RDi, ACS, or TurnOver for promotion management, that’s fine—just flag it early so we can configure access. I have REST and SOAP endpoints ready, along with field-level specs and sample payloads; your job is to marshal that data, enforce the existing business rules, and surface the new functionality inside the current menu structure.

Deliverables
• Compiled, operational RPG or COBOL modules that handle authentication, request/response processing, and error logging
• Updated data definitions (DDS or DDL) plus any necessary journaling changes
• CL commands or wrapper programs for nightly batch integration runs
• A concise deployment and rollback document, including all restore objects (SAVF)
• Unit test evidence showing each interface path exercising success, retries, and failure traps
Design, develop, and maintain applications on IBM i / AS400 using RPG (RPG IV / ILE RPG), CL, COBOL, SQL.
Troubleshoot and optimize performance of AS400 programs.
Manage and maintain database files, physical/logical files, and system configurations.
Understanding of Jobs and sub-systems is necessary.
Application Modernization (Good to Have)
Support modernization efforts leveraging Rocket Software’s CM Kit (CM Insights, CM MX, CM API).


Acceptance Criteria
1. Objects compile cleanly on V7R4 without level-check errors.
2. End-to-end interface tests return responses within the defined SLA.
3. No adverse impact on existing programs confirmed by our regression suite.
4. Clear, commented source stored in our Git repository with commit notes that map to the above deliverables.

If you’ve led similar AS400 integration efforts before, I’d love to see a short example or code snippet that demonstrates your approach to service calls or data mapping. Let’s make this connection bulletproof and keep our green-screen powerhouse humming for years to come." (client-provided description)