Are you using a source manager (Endevor, Changeman, home grown?) and could that be incorporated into the process?
Or could you use ISPF Search function (batch or foreground)? Or use something like IPOUPDTE (just to scan not to update)? I think there are many options. Have you looked on CBTTAPE.ORG to see if there are any COBOL Source scanners? Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Styles, Andy (SD EP zPlatform) > Sent: Monday, November 14, 2016 8:42 AM > To: [email protected] > Subject: OS/VS COBOL - FD DCB vs JCL DCB > > Classification: Public > > Hi all, > > We are converting some archaic programs written in OS/VS COBOL to Enterprise > COBOL (only to v4 at present). One of the issues that we've hit, well > documented in the migration guide, is that some programs have DCB information > that differs to that used in the JCL. OS/VS COBOL overrides any JCL DCB > information transparently, whereas Enterprise COBOL fails with an OPEN > failure. > > Whilst we can fix any failures as we go, questions are being asked whether we > can perform any scanning across programs and JCL and datasets to identify the > impact up front. > > We can obviously write some REXX to scan various components, but has anyone > already done anything like this that they are willing to share that would give > us a head start? > > Many thanks, > > Andy Styles > z/Series Systems Programmer > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
