Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Need Recommendations for Enterprise Software Post 302087923 by jim mcnamara on Thursday 7th of September 2006 07:23:59 AM
Old 09-07-2006
We had a similar environment - the mainframe is now gone.
I have some items for you to consider:
Code:
Here's what we think we need:

- a tool for writing and testing scripts
Once you learn more about scripting, you'l find that ksh has a lot of builtin 
functionailty to do some of this.  We don't have a script testing tool per se.
For java consider something like junit for unit testing.

- a SORT utility that can be executed from a script
Syncsort is a very robust but expensive sort tool
- a script scheduler that supports predicate/dependancy requirements (restart features would be nice too)
AppWorx is VERY good. 

- source control tool
See: Serena ChangeMan and  Serena TeamTrack.  They Automate change control really well, and TeamTrack lets you customize and control each step of the Change Control Process

- ISAM editor that supports the use of record layouts
No suggestion

- tool for comparing files
UNIX has these already.

- tool for accessing the Oracle database
Toad, PL/SQL Developer, Oracle has a free add-on with similar functionality

- 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)
No suggestions.  

- report generation tool, perhaps two, a very powerful one for the developers, and a simpler, more user-friendly one for the end-users

UNIX has these already.  perl is an excellent tool that is designed to work
agaoinst loads of data sources, including Oracle. It is a defacto standard.  ruby & python are also great for this.

The really big point is: UNIX has a LOAD of builtin tools for things. Our mainframe guys have never really gotten good with those tools, and are amazed that I can write literally less than 5 lines of code that does what hundreds of lines of COBOL and JCL used to do.

Don't underestimate UNIX tools.
 

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... (2 Replies)
Discussion started by: keelba
2 Replies
GIT-MERGETOOL(1)						    Git Manual							  GIT-MERGETOOL(1)

NAME
git-mergetool - Run merge conflict resolution tools to resolve merge conflicts SYNOPSIS
git mergetool [--tool=<tool>] [-y|--no-prompt|--prompt] [<file>...] DESCRIPTION
Use git mergetool to run one of several merge utilities to resolve merge conflicts. It is typically run after git merge. If one or more <file> parameters are given, the merge tool program will be run to resolve differences on each file (skipping those without conflicts). Specifying a directory will include all unresolved files in that path. If no <file> names are specified, git mergetool will run the merge tool program on every file with merge conflicts. OPTIONS
-t <tool>, --tool=<tool> Use the merge resolution program specified by <tool>. Valid merge tools are: araxis, bc3, diffuse, ecmerge, emerge, gvimdiff, kdiff3, meld, opendiff, p4merge, tkdiff, tortoisemerge, vimdiff and xxdiff. If a merge resolution program is not specified, git mergetool will use the configuration variable merge.tool. If the configuration variable merge.tool is not set, git mergetool will pick a suitable default. You can explicitly provide a full path to the tool by setting the configuration variable mergetool.<tool>.path. For example, you can configure the absolute path to kdiff3 by setting mergetool.kdiff3.path. Otherwise, git mergetool assumes the tool is available in PATH. Instead of running one of the known merge tool programs, git mergetool can be customized to run an alternative program by specifying the command line to invoke in a configuration variable mergetool.<tool>.cmd. When git mergetool is invoked with this tool (either through the -t or --tool option or the merge.tool configuration variable) the configured command line will be invoked with $BASE set to the name of a temporary file containing the common base for the merge, if available; $LOCAL set to the name of a temporary file containing the contents of the file on the current branch; $REMOTE set to the name of a temporary file containing the contents of the file to be merged, and $MERGED set to the name of the file to which the merge tool should write the result of the merge resolution. If the custom merge tool correctly indicates the success of a merge resolution with its exit code, then the configuration variable mergetool.<tool>.trustExitCode can be set to true. Otherwise, git mergetool will prompt the user to indicate the success of the resolution after the custom tool has exited. -y, --no-prompt Don't prompt before each invocation of the merge resolution program. --prompt Prompt before each invocation of the merge resolution program. This is the default behaviour; the option is provided to override any configuration settings. TEMPORARY FILES
git mergetool creates *.orig backup files while resolving merges. These are safe to remove once a file has been merged and its git mergetool session has completed. Setting the mergetool.keepBackup configuration variable to false causes git mergetool to automatically remove the backup as files are successfully merged. GIT
Part of the git(1) suite Git 1.7.10.4 11/24/2012 GIT-MERGETOOL(1)
All times are GMT -4. The time now is 04:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy