"The $64,000 questions about DB2/400"
Here are the $64,000 questions about DB2/400:
- Are you still creating database objects with DDS and operating system commands ?
- Are you still using Query for ad-hoc information retrieval ?
- Are you still writing "one-shot" programs to repair database files ?
- Are you still under the impression that physical and logical files are the only two types of database objects ?
If the answer to any of these is "yes", we'd like to know why?
iSeries Navigator, which comes with OS/400, contains a wealth of wizards and tools allowing you to create, manage and manipulate your database objects. It also gives you easy access to all FOURTEEN types of database objects, and lets you design your data with the TWENTY data types currently supported. It leverages the rich power of SQL and its wealth of built in functions - all ONE HUNDRED FIFTY ONE of them !
Yet somehow, inexplicably, vast legions of midrange professions still live and die by the Delorean-Esq database tools of the 1980's. Please share your thoughts on this topic (either pro's or con's) and if you have traded in the Delorean, your success stories and battle scars.
Thanks for sharing. Chris.
posted by Christopher F. Burns, Sr. @ 2:53 PM
6 comments
6 Comments:
It would be really nice if sombody gave a 1 or 2 day class on how to use Iseries Navigtor. I keep hearing about how great it is but it seems to me that it is just like other IBM systems. Lacks in user friendlyness and can be extreamly dangerous if used improperly.
Can you tell me why i5 is using a pc program to control important functions? Are there functions that can only be done using navigator?
There are a number of reasons why IBM is using a PC based client (iSeries Navigator) for database management:
1) 5250 screen driven interfaces are extremely restrictive, inflexible and costly to develop. They also require a desktop license of iSeries Access for Windows. Navigator does not.
2) 5250 interfaces require interactive CPW, which some iSeries models do not have. Navigator uses only batch CPW.
3) 5250 interfaces do not fully support many of the new DB2 features and data types introduced since V3R1. Many new operating system functions don't even have an OS/400 command associated with them and are only accessible via API's. Navigator supports them all.
4) 5250 interfaces are based on DDS - a proprietary technology which has not been enhanced since V3R1. iSeries Navigator is based on cross platform technologies (SQL & Java), which are makes it a better fit in multi platform environments. Navigator is also richly enhanced with each new release.
5) The iSeries Navigator interface is more consistent with the graphical tooling used on other platforms, and at this point IBM needs to cater to a more universal audience if the iSeries is to survive. In other words, Windows, Unix and Linux professionals are much more apt to embrace OS/400 as a viable environment if it can be managed graphically.
As with all things, if there is demand, the "market" will provide. Stay persistent. And yes, you can do a lot of damage with Navigator without the proper guidance.
I am a consultant. I work enhancing and modifying canned packages. I must follow the standards of these packages. So I use DDS for any/all file changes/ additions.
I work all over the country/world from my little desk. I connect to the various clients via multiple VPNs. WDSC and Iseries Navigator really do not work well in this multi-OS version environment. Loading source to my desktop would be a nightmare (sometimes my desktop is at a customer's location - connected remotely).
This is business model of using consultants is becoming more and more common.
So I use the easiest to use tools available......
Last comment: the split screen editting in WDSC is horrible!
Those are good points.
If your workload involves modifications to 3rd party software, following that package's guidelines is advisable. The creation of new or ancillary functions is where you could benefit from current SQL tooling.
GEMKO provides a solution concept known as Externalization for companies that must modify 3rd party software to meet their business needs. The idea is to reduce or eliminate the impact on the vendor's source code, such that future version updates will not require the mods to be reapplied. This is done though a combination of better iSeries technology and better programming practice. It does not require additional software.
I'd be happy to send you some info if you are interested in taking a look.
Post a Comment
<< Home