About this role
JD for COBOL developer Required Technical Skills: • Strong hands-on experience with COBOL development • Good knowledge of JCL, batch processing, and job scheduling • Experience working with VSAM / flat files / Oracle DB (or other relational databases) • Good exposure to mainframe utilities (SORT, IDCAMS, IEBGENER, IEFBR14 etc.) • Strong understanding of file layouts, copybooks, and data transformations • Experience performing impact analysis and code remediation • Proficiency in debugging and resolving issues in large, complex mainframe applications Additional specific technical skills needed for D0 to F6 conversion: • Strong experience handling field length changes in legacy mainframe systems during format conversions • Expertise in analyzing copybook and file layout changes, including increases or decreases in field size • Ability to identify and remediate field length dependencies across: o COBOL data definitions (PIC clauses, REDEFINES) o Database columns (DB2, relational DBs) o VSAM and flat file records • Proficient in updating COBOL PIC definitions (alphanumeric and numeric fields) to align with new standard requirements • Hands-on experience handling numeric vs alphanumeric field conversions caused by length or format changes • Skilled in managing leading/trailing spaces, zero padding, truncation, and alignment issues • Experience resolving buffer overruns, data truncation, and record mismatch issues due to field length changes • Ability to perform impact analysis for field size changes across: o Input and output interfaces o Downstream and upstream systems • Expertise in validating mandatory, conditional, and situational fields impacted by length changes • Experience updating and testing SORT, extract, and report programs affected by modified record layouts • Proficient in testing field length changes through: o Unit testing o Regression testing o Parallel run comparisons (old vs new formats) • Strong debugging skills using mainframe utilities (File-AID, SORT utilities, dumps) to validate data integrity after changes