Move BN ProgramCode

pgmdump/pgmload or metadumppgm only saves program definitions including all definition of workfiles, messages etc. You also need to copy the actual source file in bnsrc such as the .scr, .rpt, PD and WS files
and move them into the same bnsrc of different product line. If you have csv workfiles, you may have to manualy change the attributes in the new product line unless of course you know how to migrate the workfile definition from GEN.

Thanks Sam. I am not that familiar, however, we have a doc to do the pgmdump from the programmer who did it. And that includes moving all the files you have mentioned. One thing I have not look at is what you have mentioned "csv workfiles". Will look into this.

Any suggestiions or detailed steps is much appreciated.

Or my question should have been.. Since we are upgrading from 8.1 to 9.0.1, does this mean we have to change the code and recompile in the new system and not just a simple dump and load/qcompile?

Thank you,
Jude

Rule of thumb is always try to compile it first. If there are errors then do analysis. The errors could be due to different reasons like table structures or simply a new or syntax changes to the cobol/bismark compiler or simply that some new APIs supercede old ones, etc. Even if the program compiles without error you still need to verify the result. That is why when converting applications and environments TESTING is paradigm.

Another suggestion would be to let somebody knowledgeable about workbench tools and your environment should do this job like your programmers or admin.

You typically should determine what/why it is custom, "re-clone" the base code in the new version, and re-apply the customizations. Sometimes a dump/load/qcompile will work, but often it doesn't. This is where good documentation and coding standards for customizations become quite valuable.

All very good answers to the basic question - but take a step back and look at the original question: Custom code for Blue Cross. What is the invoking program that discovers or uses the code - is it related to your payroll and a deduction that is set up there? Take a look at the underlying reason that the Custom Code was written and any input files that your BN program is using within your HR deductions. What is the custom code doing for output - is it something that is then in turn passed to BC/BS for your employees, etc? Once you discover the original intent of the custom code, follow that through to its logical conclusion. Your starting steps should be PR/HR requirements that drove the creation of the custom code. Then, you can re-create (if needed) the custom code that is required. You may have a situation in that the required tables, etc in 8.1 are no longer available in 9.0.x - or an index or field was re-named, etc. Good Luck!

Thanks All