MVSFORUMS.com

[dr_te_z]

Please discuss with me:

I've worked for various companies both on mainframe and dinky-toy (unix/windows) environments. At my present customer's they have both cobol and java/webpshere on z/OS.
Source/version mangement is always an issue. For java they develop on the PC and use clear-case to manage their sources. For cobol they develop on the mainframe and they have a terrible (my personal opinion) home-made-tool which controls the prod/test/accepance cycle of the sources. Now they are investating if they can modernise development and they are looking into WD4Z and (suprise surprise) their tool is not compatible.

My argument: life coud be sooo easy when you decide to let clear-case (or any other tool ) manage all the mainframe-objects.

This would mean that
- -cobol sources
- copybooks
- jcl's
- dbrm's
- etc etc (you name it)
would exist on the mainframe-pds's, but only the current prodcution version. The history and the ones being modified would exist in clear-case or in the development tool running on a dinky-toy.

This is too much for us, mainframe grandpa's. The idea of mainframe components, not present on the mainframe itself, is unthinkable.

Do you recognize yourself in this? Am I wrong? Are there plenty mainframe sites in the world where they have offloaded the mainframe components whitout sending "goose pickels" to cobol programmers with grey hair?