- Friday, 12 August 2016
- Written by Rene De Vleeschauwer
A standard development process on mainframe looks similar to the one below:
Requirements and Issue Tracking
Application requirements and issues are stored in Collabnet’s Teamforge, BMC’s Remedy or Atlassian’s JIRA.
Mainframe developers use to work with 3270 screens and store their code in mainframe PDS's (Partitioned Data Sets) instead of in standard Windows directories. In a PDS you can’t version your files or members. That is why library management systems like Librarian or Panvalet, and later on more sophisticated systems with additional functionality like CA’s Endevor or Serena’s Change Man, were developed.
Nowadays, mainframes are often no longer seen as development environments, but mainly as machines able to cope with massive amounts of data and transactions. A major challenge is to make them part of today’s new ecosystem where distributed environments and mobile play an important role.