Need Recommendations for Enterprise Software Post: 302087890

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Need Recommendations for Enterprise Software Post 302087890 by efdqwfdw on Wednesday 6th of September 2006 11:31:36 PM

09-07-2006

Registered User

Need Recommendations for Enterprise Software

Hi all,

I work for a large corporation and I've become involved in a project that has been tasked with evaluating the feasibility, or otherwise, of the Unix platform for running some of our production system. Our background is predominantly mainframe and I need some help identifying 'best of breed' applications in the Unix environment. Some of the people who will end up developing on the Unix will be mainframe people who will be retrained. From our extensive mainframe experience we think we have a decent idea of which types of tools will be required on a day-to-day basis, but I expect there will be some gaps in our knowledge and I'm hoping that some of you can help me out.

For a number of years, we'll run the Unix and z/OS mainframe in parallel and data will have to be transferred back and forth between the two. The batch system will be written in COBOL. There's a front-end written in Java, running on websphere servers, that will need to access data on the Unix platform.

Here's what I know for sure:
- the hardware will be Sun Solaris
- we'll be using Korn shell
- the database on the Unix platform will be Oracle
- the COBOL IDE will very probably be Micro Focus Net Express, running on the developers WinXP workstations
- we'll run Samba

Here's what we think we need:
- a tool for writing and testing scripts
- a SORT utility that can be executed from a script
- a script scheduler that supports predicate/dependancy requirements (restart features would be nice too)
- source control tool
- ISAM editor that supports the use of record layouts
- tool for comparing files
- tool for accessing the Oracle database
- a tool for transferring/converting files between Unix and the mainframe (we're looking at Fileport for this, but would like another candidate or two)
- report generation tool, perhaps two, a very powerful one for the developers, and a simpler, more user-friendly one for the end-users

We would be ok with open source solutions, although licensing costs won't be an issue either. Our focus is on getting the best possible tools that will be robust and powerful enough to support an enterprise-level system.

Hopefully I've provided enough information for someone to give me some advice, but if I need to clarify anything, please let me know.

thanks for taking the time to read this, any advice you can offer will be much appreciated.

Last edited by efdqwfdw; 09-07-2006 at 12:34 AM.. Reason: added info

efdqwfdw

View Public Profile for efdqwfdw

Find all posts by efdqwfdw

We Also Found This Discussion For You

1. UNIX for Advanced & Expert Users

Enterprise backup software

My company has been an OmniBack shop for about 2 years now. We use it to backup both Unix and NT servers as well as a Network Appliance Filer. For the most part it has sufficed for what we do. However, management is considering changing to another backup software. We are considering either staying...

LEARN ABOUT SUSE

platform::shell

platform::shell(n)					       Tcl Bundled Packages						platform::shell(n)

__________________________________________________________________________________________________________________________________________________

NAME

       platform::shell - System identification support code and utilities

SYNOPSIS

       package require platform::shell ?1.1.4?

       platform::shell::generic shell
       platform::shell::identify shell
       platform::shell::platform shell
_________________________________________________________________

DESCRIPTION

       The platform::shell package provides several utility commands useful for the identification of the architecture of a specific Tcl shell.

       This  package  allows the identification of the architecture of a specific Tcl shell different from the shell running the package. The only
       requirement is that the other shell (identified by its path), is actually executable on the current machine.

       While for most platform this means that the architecture of the interrogated shell is identical to the architecture of  the  running  shell
       this  is  not generally true. A counter example are all platforms which have 32 and 64 bit variants and where a 64bit system is able to run
       32bit code. For these running and interrogated shell may have different 32/64 bit settings and thus different identifiers.

       For applications like a code repository it is important to identify the architecture of the shell which will  actually  run  the  installed
       packages, versus the architecture of the shell running the repository software.

COMMANDS

       platform::shell::identify shell
	      This command does the same identification as platform::identify, for the specified Tcl shell, in contrast to the running shell.

       platform::shell::generic shell
	      This command does the same identification as platform::generic, for the specified Tcl shell, in contrast to the running shell.

       platform::shell::platform shell
	      This command returns the contents of tcl_platform(platform) for the specified Tcl shell.

KEYWORDS

       operating system, cpu architecture, platform, architecture

platform::shell 						       1.1.4							platform::shell(n)

We Also Found This Discussion For You

1. UNIX for Advanced & Expert Users

Enterprise backup software

Discussion started by: keelba

LEARN ABOUT SUSE

platform::shell