AS400 / IBM i Application Developer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Position Overview paragraph: "The Office of Management and Enterprise Services (OMES), in coordination with the Oklahoma Insurance Department (OID), is seeking an experienced AS400 / IBM i Developer and Application Administrator for a long-term contract engagement. This role will support OID's core IBM AS/400 / IBM i environment, with responsibility for legacy application development and maintenance, DB2 database support, application-level system administration, integrations, production troubleshooting, and modernization activities. The ideal candidate will have strong hands-on experience with RPGLE, RPG IV/ILE RPG, Control Language (CL), DB2 for i, SQL, FTP/SFTP, and IBM i application administration. This individual will also serve as a key technical liaison between the agency, hosting providers, infrastructure teams, database administrators, and cloud modernization teams."
We'll put that in
under About the role.
Responsibilities: The "Key Responsibilities" section includes multiple bullet-like paragraphs. We need to convert each bullet to
- . The content includes subheadings like "AS400 / IBM i Application Development & Maintenance", then sentences. We could treat each major bullet as
- containing the description. Might need to preserve details.
Let's parse:
- AS400 / IBM i Application Development & Maintenance
Maintain, enhance, troubleshoot, and optimize legacy applications running within the IBM AS400 / IBM i environment.
Develop and maintain applications using:
RPG
RPG III
RPG IV / ILE RPG
RPGLE
Control Language (CL)
SQL
Analyze and resolve production defects, operational issues, batch-processing failures, and user-reported application problems.
Modify existing application logic to accommodate:
Regulatory changes
Licensing requirements
Agency policy changes
Business process enhancements
Perform code analysis, debugging, testing, and production support for existing AS400 applications.
- IBM i Application Administration
Provide application-level administration and operational support within the IBM i environment.
Manage and support:
IBM i user profiles
Application security
Object-level authorities
Job queues
Active subsystems
Application job schedulers
Review and verify IBM i system audit logs, including QAUDJRN, to help maintain system and application integrity.
Troubleshoot application-related IBM i operational issues and coordinate resolution with infrastructure teams when necessary.
- Hosting Provider & Infrastructure Coordination
Serve as a primary technical liaison between OID and its external AS400 hosting/managed-services providers.
Coordinate activities related to:
IBM i operating system maintenance
OS patching
Database utilities
Environmental changes
Storage operations
Backup activities
Disaster recovery
System restoration
Work closely with Ensono and other infrastructure/hosting teams to coordinate application backup windows and operational activities.
Participate in disaster recovery testing and verify successful application and data restoration.
- DB2 for i Database Management
Query, manage, troubleshoot, and optimize DB2 for i databases.
Develop and execute SQL queries for application support, data analysis, troubleshooting, and integration.
Analyze and optimize:
SQL queries
Database indexes
Database access patterns
Application/database performance
Assist with legacy table maintenance, data extraction, cleanup, migration, and archival activities.
- File Transfer & Systems Integration
Develop and support secure file-transfer integrations using:
SFTP
FTPS
Support interfaces between the hosted AS400 environment and downstream:
State systems
Regional systems
Partner systems
Third-party applications
Troubleshoot file-transfer failures and integration-related production issues.
Support automation of recurring data exchanges and file-transfer processes.
- Modernization & Migration Support
Collaborate with state database administrators, application teams, and cloud architects on modernization initiatives.
Assist with extracting, cleaning, transforming, and archiving legacy AS400 data.
Analyze existing legacy applications and business logic to support migration to modern platforms and cloud environments.
Document:
Application architecture
System workflows
Database schemas
Interfaces
Application dependencies
Business rules
Batch processes
Integration points
Help identify legacy system dependencies that must be addressed during application modernization and migration.
We need to output these as list items. Could group each major heading as a list item with sublist? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can have top-level
with each responsibility as - , and inside each
- we can have nested
for subpoints. That preserves detail.
Similarly for Requirements (Required Qualifications) we have a paragraph list of qualifications. We'll convert each bullet line to - . The content includes many sentences; we can treat each sentence or bullet as
- . Let's extract each line after "Required Qualifications". It starts with "Minimum 5 years of hands-on experience supporting and developing applications within an IBM AS400 / IBM i / iSeries environment." Then list of bullet points starting with "Strong hands-on development experience with:" then a list of items: RPGLE, RPG IV / ILE RPG, Control Language (CL), SQL, DB2 for i. Then "Strong experience maintaining and supporting legacy AS400 applications." etc.
We'll need to preserve all details. Could break into items:
- Minimum 5 years of hands-on experience supporting and developing applications within an IBM AS400 / IBM i / iSeries environment.
- Strong hands-on development experience with:
- RPGLE
- RPG IV / ILE RPG
- Control Language (CL)
- SQL
- DB2 for i
- Strong experience maintaining and supporting legacy AS400 applications.
- Experience debugging RPG programs and troubleshooting production application issues.
- Hands-on experience with DB2 for i database development, queries, and performance optimization.
- Experience with IBM i work management, including:
- Subsystems
- Job queues
- Job scheduling
- User profiles
- Object authorities
- Application security
- Experience supporting file transfers and system integrations using FTP and SFTP.
- Experience working within a hosted or managed AS400 environment.
- Ability to coordinate effectively with external hosting providers and infrastructure teams when resolving environmental or system-related issues.
- Experience supporting backup, recovery, and disaster recovery activities.
- Strong troubleshooting, analytical, and problem-solving capabilities.
- Ability to document existing legacy applications, database structures, interfaces, and system dependencies.
- Strong verbal and written communication skills.
That seems comprehensive.
Skills (Highly Relevant Skills) list: many items separated by line breaks. We'll make each as
- . Items: IBM AS400 / IBM i / iSeries, RPGLE, RPG IV / ILE RPG, RPG III, Control Language (CL), DB2 for i, SQL, IBM i Application Administration, IBM i Work Management, Subsystems, Job Queues, User Profile Management, Object-Level Security, QAUDJRN, SFTP, FTP, Batch Processing, Application Support, Production Support, Legacy Application Modernization, Data Migration, Disaster Recovery, Managed / Hosted AS400 Environments.
Schedule: "Work Schedule This is a part-time hybrid engagement requiring approximately 20 hours per week in support of the Oklahoma City-based environment." We'll put that in
under Schedule.
We must not repeat job title as heading. Already not.
We must not include Job ID etc. Not present.
We must not include boilerplate like Interview Process etc. Remove that.
We must not include Duration? Not required but could be part of About the role? The posting includes Duration: 12 Months. That's substantive. Should we include it? The instruction: include a section ONLY when posting has real, specific content for it. Duration is not a standard heading but we could fold into About the role paragraph. Since we already have About the role paragraph, we can add sentence about duration. The Position Overview didn't mention duration; but later there is "Duration: 12 Months". We should preserve that info. We can add to About the role paragraph: "This is a 12-month contract engagement." Let's incorporate.
Also Location: Oklahoma City, OK Hybrid Schedule: Part-Time Approximately 20 hours per week. We already have schedule and location. Location could be included in About the role or maybe separate? Not a standard heading. We'll add location to About the role: "Located in Oklahoma City, OK (hybrid)." Or we can add a separate section? Not needed.
We must not create Pay/Benefits sections unless present. Not present.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ... (with nested ul if needed)
...
Requirements
- ... (with nested ul)
...
Skills
- ...
...
Schedule
...
Make sure to close tags.
Now craft the About the role paragraph:
"The Office of Management and Enterprise Services (OMES), in coordination with the Oklahoma Insurance Department (OID), is seeking an experienced AS400 / IBM i Developer and Application Administrator for a long-term contract engagement. This role will support OID's core IBM AS/400 / IBM i environment, with responsibility for legacy application development and maintenance, DB2 database support, application-level system administration, integrations, production troubleshooting, and modernization activities. The ideal candidate will have strong hands-on experience with RPGLE, RPG IV/ILE RPG, Control Language (CL), DB2 for i, SQL, FTP/SFTP, and IBM i application administration. This individual will also serve as a key technical liaison between the agency, hosting providers, infrastructure teams, database administrators, and cloud modernization teams. Located in Oklahoma City, OK, this is a part-time hybrid engagement requiring approximately 20 hours per week and a 12-month contract duration."
Wait schedule part we will put in Schedule section, but we can still mention location and duration. To avoid duplication, maybe keep location and duration in About the role, and schedule separate. The schedule section will say "This is a part-time hybrid engagement requiring approximately 20 hours per week in support of the Oklahoma City-based environment." That's basically same as location+schedule. We'll keep schedule section as given. About the role can mention location and duration but not repeat schedule details. Let's include location and duration.
Thus About the role paragraph: "The Office of Management and Enterprise Services (OMES), in coordination with the Oklahoma Insurance Department (OID), is seeking an experienced AS400 / IBM i Developer and Application Administrator for a long-term contract engagement. This role will support OID's core IBM AS/400 / IBM i environment, with responsibility for legacy application development and maintenance, DB2 database support, application-level system
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Position Overview paragraph: "The Office of Management and Enterprise Services (OMES), in coordination with the Oklahoma Insurance Department (OID), is seeking an experienced AS400 / IBM i Developer and Application Administrator for a long-term contract engagement. This role will support OID's core IBM AS/400 / IBM i environment, with responsibility for legacy application development and maintenance, DB2 database support, application-level system administration, integrations, production troubleshooting, and modernization activities. The ideal candidate will have strong hands-on experience with RPGLE, RPG IV/ILE RPG, Control Language (CL), DB2 for i, SQL, FTP/SFTP, and IBM i application administration. This individual will also serve as a key technical liaison between the agency, hosting providers, infrastructure teams, database administrators, and cloud modernization teams." We'll put that in
under About the role. Responsibilities: The "Key Responsibilities" section includes multiple bullet-like paragraphs. We need to convert each bullet to
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can have top-level
- with each responsibility as
- , and inside each
- we can have nested
- for subpoints. That preserves detail.
Similarly for Requirements (Required Qualifications) we have a paragraph list of qualifications. We'll convert each bullet line to
- . The content includes many sentences; we can treat each sentence or bullet as
- . Let's extract each line after "Required Qualifications". It starts with "Minimum 5 years of hands-on experience supporting and developing applications within an IBM AS400 / IBM i / iSeries environment." Then list of bullet points starting with "Strong hands-on development experience with:" then a list of items: RPGLE, RPG IV / ILE RPG, Control Language (CL), SQL, DB2 for i. Then "Strong experience maintaining and supporting legacy AS400 applications." etc. We'll need to preserve all details. Could break into items: - Minimum 5 years of hands-on experience supporting and developing applications within an IBM AS400 / IBM i / iSeries environment. - Strong hands-on development experience with: - RPGLE - RPG IV / ILE RPG - Control Language (CL) - SQL - DB2 for i - Strong experience maintaining and supporting legacy AS400 applications. - Experience debugging RPG programs and troubleshooting production application issues. - Hands-on experience with DB2 for i database development, queries, and performance optimization. - Experience with IBM i work management, including: - Subsystems - Job queues - Job scheduling - User profiles - Object authorities - Application security - Experience supporting file transfers and system integrations using FTP and SFTP. - Experience working within a hosted or managed AS400 environment. - Ability to coordinate effectively with external hosting providers and infrastructure teams when resolving environmental or system-related issues. - Experience supporting backup, recovery, and disaster recovery activities. - Strong troubleshooting, analytical, and problem-solving capabilities. - Ability to document existing legacy applications, database structures, interfaces, and system dependencies. - Strong verbal and written communication skills. That seems comprehensive. Skills (Highly Relevant Skills) list: many items separated by line breaks. We'll make each as
- . Items: IBM AS400 / IBM i / iSeries, RPGLE, RPG IV / ILE RPG, RPG III, Control Language (CL), DB2 for i, SQL, IBM i Application Administration, IBM i Work Management, Subsystems, Job Queues, User Profile Management, Object-Level Security, QAUDJRN, SFTP, FTP, Batch Processing, Application Support, Production Support, Legacy Application Modernization, Data Migration, Disaster Recovery, Managed / Hosted AS400 Environments.
Schedule: "Work Schedule This is a part-time hybrid engagement requiring approximately 20 hours per week in support of the Oklahoma City-based environment." We'll put that in
under Schedule. We must not repeat job title as heading. Already not. We must not include Job ID etc. Not present. We must not include boilerplate like Interview Process etc. Remove that. We must not include Duration? Not required but could be part of About the role? The posting includes Duration: 12 Months. That's substantive. Should we include it? The instruction: include a section ONLY when posting has real, specific content for it. Duration is not a standard heading but we could fold into About the role paragraph. Since we already have About the role paragraph, we can add sentence about duration. The Position Overview didn't mention duration; but later there is "Duration: 12 Months". We should preserve that info. We can add to About the role paragraph: "This is a 12-month contract engagement." Let's incorporate. Also Location: Oklahoma City, OK Hybrid Schedule: Part-Time Approximately 20 hours per week. We already have schedule and location. Location could be included in About the role or maybe separate? Not a standard heading. We'll add location to About the role: "Located in Oklahoma City, OK (hybrid)." Or we can add a separate section? Not needed. We must not create Pay/Benefits sections unless present. Not present. Now produce HTML. Structure:
About the role
...
Responsibilities
- ... (with nested ul if needed) ...
Requirements
- ... (with nested ul) ...
Skills
- ... ...
Schedule
...
Make sure to close tags. Now craft the About the role paragraph: "The Office of Management and Enterprise Services (OMES), in coordination with the Oklahoma Insurance Department (OID), is seeking an experienced AS400 / IBM i Developer and Application Administrator for a long-term contract engagement. This role will support OID's core IBM AS/400 / IBM i environment, with responsibility for legacy application development and maintenance, DB2 database support, application-level system administration, integrations, production troubleshooting, and modernization activities. The ideal candidate will have strong hands-on experience with RPGLE, RPG IV/ILE RPG, Control Language (CL), DB2 for i, SQL, FTP/SFTP, and IBM i application administration. This individual will also serve as a key technical liaison between the agency, hosting providers, infrastructure teams, database administrators, and cloud modernization teams. Located in Oklahoma City, OK, this is a part-time hybrid engagement requiring approximately 20 hours per week and a 12-month contract duration." Wait schedule part we will put in Schedule section, but we can still mention location and duration. To avoid duplication, maybe keep location and duration in About the role, and schedule separate. The schedule section will say "This is a part-time hybrid engagement requiring approximately 20 hours per week in support of the Oklahoma City-based environment." That's basically same as location+schedule. We'll keep schedule section as given. About the role can mention location and duration but not repeat schedule details. Let's include location and duration. Thus About the role paragraph: "The Office of Management and Enterprise Services (OMES), in coordination with the Oklahoma Insurance Department (OID), is seeking an experienced AS400 / IBM i Developer and Application Administrator for a long-term contract engagement. This role will support OID's core IBM AS/400 / IBM i environment, with responsibility for legacy application development and maintenance, DB2 database support, application-level system