TD/OMS 4GL Interfaces


The strength of TD/OMS 4 GL interfaces is that the development of all interfaces is done by our development team in The Netherlands. Our interfaces are based on a powerful concept that enables us to adopt and develop new development environments quickly. As a result of the close relationship between Remain and her technology partners we offer up to date interfaces to maximize the benefits of TD/OMS in combination with the customer’s 4GL development platform.

TD/OMS LANSA interface

Software Change Management support for LANSA Software Development Platform for IBM i and Windows

The hallmark of the LANSA software development platform for IBM i (iSeries or AS/400) and Windows is business agility. The LANSA software development platform is used by many small and medium sized companies to support their entire business systems infrastructure, and also by divisions of larger enterprises to run business critical applications.

With our TD/OMS LANSA interface we offer a high quality Software Change Management environment that enables software developers to adapt software changes quickly.

The TD/OMS LANSA interface enables you to manage your application development life cycle. By managing important information items such as Incidents, Change Requests and Tasks, you are able to control the various aspects of application development. The TD/OMS LANSA interface utilizes the LANSA task mechanism to exchange information between LANSA and TD/OMS. In most situations TD/OMS will be configured to automatically generate a corresponding task within LANSA when a task is generated within TD/OMS. The result is a 1-to-1 relation between the LANSA task and the TD/OMS task which removes the requirement for the developer to select a LANSA task when connecting components to the TD/OMS task. The TD/OMS LANSA interface supports any other LANSA task implementation (such as a general task for each developer) when the automatic 1-to-1 task creation is not acceptable.

After the assignment of a TD/OMS task, your developers are able to select and connect components from the TD/OMS configuration database. The TD/OMS configuration database contains component information retrieved from all the locations (LANSA partitions, Libraries and IFS folders) defined. It also contains information regarding the relations between the components (using and used by). These ingredients (together with the optional impact analysis definitions) greatly simplify the connection of all required components to the TD/OMS task. Connecting components works for all your LANSA software components.

With a push of the button the required components are copied to the development environment. The authorised developer(s) can perform the required development activities within (visual) LANSA and connect new components to the LANSA task. At any moment during the development activities, your developers can connect new and/or generated components to the TD/OMS task through the TD/OMS LANSA interface wizard. Expected generated components (e.g. DLLs) are searched for and color coding is used to indicate success/failure of the search. The developer can decide to select only a few of the components connected to the LANSA task to be connected to the TD/OMS task or to simply connect all components. Depending on the component type (eg FILE) addtitional (generated) components will be added to the TD/OMS task automatically.

After completing their tasks the developers move the components to the next step in the lifecycle (eg the test environment). 

After successful completion of the tests, authorised staff members (eg application manager or operations department member) promote the components to the production environment. Everything in this process is automated within TD/OMS. Depending on how TD/OMS distribution has been setup, this can include deployment to and implementation on remote IBM i systems, Unix/Linux and Windows PC's.

TD/OMS CA Plex interface

CA Plex is a multi-platform, model-based, architected rapid application development tool.

Develop applications in a Windows environment and then compile and test them in the target environment which might be Windows/.NET, Java/J2EE or the IBM i. CA Plex supports the development of many different types of applications including client/server, web-based, service-oriented, character-based, batch and wireless device-based, all from a single set of skills and development techniques.

The CA Plex development process on the IBM i platform is fully supported by TD/OMS, Remain’s Software Change Management solution.

The TD/OMS CA Plex interface enables you to manage your application development life cycle. By managing important information items such as Incidents, Change Requests and Tasks, you are able to control the various aspects of application development. CA Plex-TD/OMS works for all your CA Plex software components: native i OS and PC Components.

After the assignment of a task, your programmers are able to select and connect components from the configuration database. With a push of the button the required components are copied to the development environment. Your programmers complete their tasks and move the components to the next step in the lifecycle (eg the test environment). 

After a successful completion of the tests, your application managers promote the components to the production environment. Everything in this process is automated by CA Plex-TD/OMS. Depending on how TD/OMS distribution has been setup, this can include deployment to and implementation on remote IBM i systems, Unix/Linux and Windows PC's.

TD/OMS CA 2E interface

The solution allows work in the CA workbench and, when needed, access to desired functionality in TD/OMS. The 2E object registration and management is supported on the local side of a TD/OMS installation i.e. the development platform where all the TD/OMS administration is done. The 2E objects are never an active part of the distribution to a remote machine or partition of an IBM i. Once a TD/OMS application is configured to work with the 2E interface, TD/OMS functions will work with the 2E definitions as if they are standard IBM i objects.

Using the solution, the CA 2E definitions and specifications are registered in TD/OMS as objects and they can be copied from one 2E model repository to another. While changing the CA application, TD/OMS informs other developers that the component is already locked in the maintenance cycle and prevents overwriting the changes. When the TD/OMS task is started, the associated IBM i components will be selected automatically, which makes it easier for developers to manage the change.

Regardless whether users work with new or existing components, both types are automatically checked to development (start) stage in TD/OMS. This significantly reduces time needed for the work which previously required manual effort. Furthermore, components which are placed in the intermediate stages, such as for example testing, can be easily viewed in TD/OMS. The solution also provides an overview of the entire application environment including multiple CA2E models.

CA 2E users considering modernization projects can also benefit from the combination of CA 2E and TD/OMS with seamlessly integrated X-Analysis from Fresche Legacy, which brings additional value by providing in-depth automated application analysis and documentation capabilities.

TD/OMS IDDOS interface

The TD/OMS IDDOS interface enables you to manage your application development life cycle. By managing important information items such as Incidents, Change Requests and Tasks, you are able to control the various aspects of application development. IDDOS-TD/OMS works for all your IDDOS software components types  (eg programs, files, attributes, subsystems, macro’s, etc.).

After the assignment of a task, your programmers are able to select and connect components from the configuration database. With a push of the button the required components are copied to the development environment. Your programmers complete their tasks and move the components to the next step in the lifecycle (eg the test environment). 

After a successful completion of the tests, your application managers promote the components to the production environment. Everything in this process is automated by IDDOS-TD/OMS. This includes distribution to and implementation on remote IBM  i systems.

TD/OMS AS/SET interface

The TD/OMS AS/SET interface supports the management of information systems built with the AS/SET case tool. AS/SET is well known in the Infor BPCS/LX user community.

The AS/SET definitions are loaded in the TD/OMS repository using this module and they can be copied from one AS/SET application set to another.

The TD/OMS AS/SET interface enables you to manage your application development life cycle. By managing important information items such as Incidents, Change Requests and Tasks, you are able to control the various aspects of application development. AS/SET-TD/OMS works for all your AS/SET software components types  (eg Batch programs, Display programs, Model, Model files, etc.).

After the assignment of a task, your programmers are able to select and connect components from the configuration database. With a push of the button the required components are copied to the development environment. Your programmers complete their tasks and move the components to the next step in the lifecycle (eg the test environment). 

After a successful completion of the tests, your application managers promote the components to the production environment. Everything in this process is automated by AS/SET-TD/OMS. This includes distribution to and implementation on remote IBM  i systems.

TD/OMS Magic uniPaaS interface

Magic's uniPaaS is an application platform that simplifies the process of building and deploying business applications. Magic’s uniPaaS is used to build and deploy full client, rich internet applications (RIA), mobile applications and Software-as-a-Service (SaaS) offerings.

Applications developed using uniPaaS typically have fewer coding mistakes, undergo more thorough prototyping, benefit from greater business side input and optimization, and can be more easily adapted to changing business needs.

The uniPaas software development process on the IBM System i platform is fully supported by TD/OMS, Remain's Software Change Management solution.

TD/OMS EGL interface

Software Change Management support for EGL

EGL (Enterprise Generation Language) is a high level, modern business oriented programming language, designed by IBM to be platform independent. EGL is similar in syntax to other common languages so it can be learned by application developers with similar previous programming background. EGL application development abstractions shield programmers from the technical interfaces of systems and middleware allowing them to focus on building business functionality. EGL applications and services are written, tested and debugged at the EGL source level, and once they are satisfactorily functionally tested they can be compiled into Cobol, Java, or JavaScript code to support deployment of business applications that can run in any of the following environments:

TD/OMS-EGL Continuous Integration for Java

In a pioneering effort Remain has forged an automated build environment for the build, test and deploy of EGL web services.  Running EGL automated builds from within a builder server such as Continuum or Hudson instantly creates a Continuous Integration environment for EGL projects. With Continuous Integration in place, code and integration tests can be put to effective use, enhancing the overall software quality and reducing the risk of distributing failing software.

The EGL development process on the IBM i platform is fully supported by TD/OMS. The automated build environment takes the responsibility of automatically checking out the EGL web service and related projects from a source repository, for instance Rational Team Concert.

The following build steps are performed:

  • Generating java or java script from EGL sources,
  • Packaging the EGL generated resources into an EAR,
  • Deploying the EAR to a local WAS server,
  • Running integration test against the deployed EAR,
  • Connecting the web-service EAR to a TD/OMS task for further processing.

Once in TD/OMS the web-service ear and related components, such as RPG programs and SQL files will be processed and distributed to target systems, whereby the web-service EAR can be deployed directly into a WebSphere Application Server alleviating any tedious manual handling often required for a WAS EAR deployment.

The Benefits:

  • Rely on the EGL automated build environment to construct the EGL web-services and to run the essential test suites automatically.
  • Reduces the time normally required to release web service applications.
  • Pulls EGL into a more Agile development process.