JavaScript Web Designers Can Now Easily Integrate with the Mainframe Using Ivory Service Architect
ATLANTA, June 20, 2011 – GT Software, a global provider of mainframe integration and data access solutions, today announced that its flagship product, Ivory Service Architect, now supports JSON as an option for web service processing.
“This latest enhancement makes Ivory Service Architect easier for developers to use, and opens the door for JavaScript web designers to access the IBM mainframe — enabling more people than ever before to leverage mainframe applications and data,” said Wes Young, Senior Vice President of Sales for GT Software.
“This reinforces Ivory Service Architect’s position as the most cost-effective, flexible mainframe integration tool on the market today.”
Yes, those immortal words take me back to a high school stage in 1978 when life was easy and I really didn’t “pay no mind” to the words being sung. Irving Berlin may not have really known how those words would ring true even today, but I digress.
The possibilities for a play on words here are just too easy. But seriously, what isn’t that easy is trying to take Natural applications and integrate them with modern web applications. It’s just plain hard. Adabas data access can be difficult too. Fortunately, GT Software is also doing what comes naturally and that is making integration easy by extending the powerful capabilities of Ivory Service Architect to also include inbound and outbound web service enablement for Natural applications and Adabas data.
If you have Natural applications that need to call web services, or if you want to web service enable your existing Natural apps and data, give GT a call. You can also view a rebroadcast of our last webinar titled “Boost Development Initiatives with Native Access to Natural / Adabas“ or read the full press release here.
Lightweight Directory Access Protocol (LDAP) is an Internet Protocol for accessing distributed directory services that act in accordance to X.500 data and service models with roots in the Telco industry and honed by 70 years of expertise. X.500? With X.500 there is a single Directory Information Tree which is distributed across one or more servers.
Each entry of the X.500 Directory structure consists of a set of attributes. The server may return the values of an attribute, the attributes in an entry, and the entries found by a search operation in any order. This follows from the formal definitions – an entry is defined as a set of attributes, and an attribute is a set of values, and sets need not be ordered.
So now that you know about the directory abilities of LDAP, what can you do with LDAP?
An LDAP client (JXPlorer for example at http://jxplorer.org) can if programmed accordingly:
Start TLS – Use the LDAPv3 Transport Layer Security (TLS) for Secure Connections
Bind – Authenticate and specify LDAP protocol version
Search/Compare – Look up directory entries and see entry has a certain value
Add/Delete/Modify Entries – Normal directory maintenance
Abandon – Abort Operation
Unbind – Close connection
Hey wait a minute. The LDAP directory doesn’t look anything like my directory system on the mainframe (e.g. RACF). Given all of this information, why in the world would one want to consider putting an LDAP on the mainframe? Think about it for a second.
Isn’t your mainframe the centerpiece of your IT Universe?
RACF in fact can be used as the back-end Database for LDAP (as well as DB/2).
RACF is a robust almost impenetrable security system.
IBM provides an LDAP Server for z/OS which provide centralized control.
The RACF Security Administrator can easily maintain RACF and not have to learn another Security System.
So if you have web or other corporate applications that need a COMMON directory against which to authenticate users then what more natural place than the mainframe especially since a bulk of corporate data resides on the mainframe?
If you want a real surfin’ safari, then catch a wave and join GT Software at the 2011 WAVV Conference in Colorado Springs April 15th – 19th, 2011 at the Crowne Plaza, Colorado Springs. WAVV is a user group promoting the interests of the users of the VSE, VM, and Linux operating systems. WAVV holds an annual conference consisting of over 100 educational sessions as well as a vendor show where vendors of VSE, VM, and Linux related products can show their wares and meet with current customers.
On Sunday at 3:00 PM in Pikes Peak III, Don Spoerke will present “GT Software’s Solutions for Maximizing the Integration and Usability of VSAM files on VSE”. Don will present an in-depth overview of how GT Software’s Ivory suite can help developers maximize the usability of VSAM data without impacting development or IT resources. Reusing these files saves time, money and eliminates the need to re-host the data for the purpose of BI, warehousing, or integration to new applications. Also join Don at the SPLASH Exhibit Hall on Sunday from 7 – 11 PM, and Monday from 12:45 – 3:00 PM and 7:00 – 11 PM. Click here for more information on WAVV 2011.
Please join GT Software at the 2011 IBM Impact Conference in Las Vegas April 10th – 15th, 2011 at the Venetian and Palazzo Hotels. The IBM Impact 2011 Global Conference will bring together more than 6,600 technology and business leaders at a single event for a transformative learning opportunity. Never has it been more important to work smarter for better business outcomes. IT professionals can learn the latest technology trends and quickly build skills in WebSphere, BPM, SOA and Cloud solutions and will come away with the expertise to help advance your career and advance your organization’s ability to improve business outcomes and grow.
Rob Morris will be presenting “Drive Value and Cut Costs with Mainframe Web Services“ on Tuesday, April 12th from 4:45 – 6:00 PM in the Venetian – Delfino 4001A room. Rob will focus on how mainframe integration and Web services using Ivory from GT Software can drive maximum value from your existing mainframe investments, while cutting costs. Many think this problem is completely ‘solved’ with WebSphere MQ, free utilities, or out of date approaches. This session will challenge those beliefs and empower you to drive maximum value from the mainframe while lowering costs. Also join GT Software as we exhibit the Ivory suite at the zZone Solution Center. Solution Center hours can be found here.
IBM VM (Virtual Machine) is an operating system created by IBM that runs on IBM Mainframe Systems. VM provides the virtualization technology that enables multiple copies of operating systems to run as GUEST Operating Systems (commonly referred to as GUESTs) on a common physical hardware platform. VM provides a robust virtual computing platform. The motivating factor behind virtualization technology is realizing huge economies of scale as we will see later on discussion of z/Linux.
Originally released in 1972 as VM/370 because it ran on the IBM/370 mainframe. VM/370 ran a re-implementation of CP/CMS System. CP/CMS has several previous versions including CP-40/CMS and CP-67/CMS. VM/370 was based on a CP-370/CMS. The CP (Control Program) piece is the hypervisor used to share computing resources of the physical hardware and CMS is a User Time-Sharing and Editing environment. Simply put, CP/CMS is the administrative and user environment of VM.
z/VM is the current implementation of IBM’s VM and run on all of IBM latest Mainframe Systems including the z/10 and z/Enterprise Systems (z196). The z/VM Hypervisor CP (Control Program) provides the mechanisms for sharing hardware and software resources that enable virtualization in z/VM. A series of CP commands and scripting can be used to provide the virtual environment with which the GUEST operates.
z/Linux is a complete implementation of Linux on System z. Linux implementations for the IBM Mainframe were developed in labs over a period of late 1998 and early 1999 with a commercially available package available in 2000.
Using a combination of z/VM and z/Linux, a customer can literally run thousands of Linux GUESTs on a single IBM Mainframe platform. As mentioned earlier in this article the user community can realize tremendous economies of scale by establishing a Many to One relationship between the z/Linux GUESTs (MANY) to a common physical hardware platform (ONE). IBM Mainframes have a specialized processor called an Integrated Facility for Linux (IFL) to handle the z/Linux workload. The real beauty of IFLs is that they run at Uniprocessor speed (Full Throttle) and are NOT “knee-capped”) as are the General Processors (GPs) used for running other mainframe workload. With z/Linux, the customer is not hassled with providing commodity based hardware platforms that may only provide a ONE-for-ONE environment.
The market for z/Linux is rapidly expanding and maturing. Production, Development and Test/QA environments have found real relevance for z/VM and z/Linux.
GT Software’s Dusty Rivers talks about the mission-critical nature of the applications on the IBM System z. The mainframe is the platform customers trust for the availability, security and reliability to run their core business applications. The new IBM zEnterprise System will be the basis to begin working over the cloud.
Hear Rob Morris “Shoot it Out” with other CICS Web Service vendors and learn how Ivory Service Architect from GT Software will help your organization drive value while containing costs.
SHARE 2011 will be held in Anaheim, CA, February 27th – March 4th, 2011. The theme of this year’s show is Driving Value While Containing Costs. Rob Morris, Chief Strategy Officer for GT Software, has been invited to speak at the session titled “CICS Web Service Vendor Shootout.”
Rob, along with other CICS vendors, will discuss the use of web services tooling for mainframe integration versus what is offered by IBM. Rob will stress why having choices for how services are developed, what can be included, how the services are called, and where the services are run are critical to maximize your investments while containing costs. He’ll also highlight that Ivory Service Architect includes support for IBM specialty engines which will definitely impact the total cost of an integration framework. To support Rob’s message, he will include testimonials from GT Software customers that have enhanced the value of their mainframe while containing costs. As Chief Strategy Officer for GT Software, Rob has written articles for many industry publications and is a frequent presenter at SHARE and key IBM events.
“The CICS Web Services Vendor Shootout” will be held in Room 205B of the Anaheim Convention Center at 3:00PM on Tuesday March 1, 2011. More information on the SHARE conference can be found at www.share.org. For information on how GT Software can maximize the value of modernizing your mainframe investments while containing costs, please visit www.gtsoftware.com or call 404-253-1300 to speak to one of our Integration experts.
What is a dataset name? A data set name can be one name segment or a series of joined name segments where each name segment represents a level of qualification. For example, the data set name VERA.LUZ.DATA is composed of three name segments. The first name on the left is called the high-level qualifier (HLQ), the last name on the right is the lowest-level qualifier (LLQ).
Segments or qualifiers are limited to eight characters, the first of which must be alphabetic (A to Z) or special (# @ $). The remaining seven characters are either alphabetic, numeric (0 – 9), special characters, a hyphen (-). Name segments are separated by a period (.).
Including all name segments and periods, the length of the data set name must not exceed 44 characters or a maximum of 22 name segments.
For example, the following names are not valid data set names:
Name with a qualifier that is longer than eight characters (HLQ.ABCDEFGHI.XYZ)
Name containing two successive periods (HLQ..ABC)
Name that ends with a period (HLQ.ABC.)
Name that contains a qualifier that does not start with an alphabetic or special character (HLQ.123.XYZ)
The HLQ for a user’s data sets is typically controlled by the security system. The remainder of the name follows conventions, not rules, which may include the following:
LIB in the name indicates that the data set is a library. PDS is a lesser-used alternative
CNTL, JCL, or JOB in the name typically indicates the data set contains JCL
LOAD, LOADLIB, or LINKLIB in the name indicates the data set contains executables
PROC, PRC, or PROCLIB indicate a library of JCL procedures
COBOL, Assembler, FORTRAN, PL/I, etc., are used to indicate language source code
A portion of a data set name may indicate a specific project, such as PAYROLL.
Using too many qualifiers is considered poor practice. For example, the following name is a valid data set name (upper case, does not exceed 44 bytes, no special characters) but it is not very meaningful.
P390A.A.B.C.D.E.F.G.H.I.J.K.L.M.N.O.P.Q.R.S
A good practice is for a data set name to contain three or four qualifiers.
IMS has been around and in production for over 40 years as the backbone system of many world class organizations in all industry verticals. Now with some of the new technologies and systems many are looking to try and replace those tried and true systems. Why replace something that is tried and true, why not just incorporate the new technologies and let them drive the existing IMS systems (without changing the IMS systems).
Already companies are using web-services to drive IMS transactions or sets of transactions to create composite business services needed by the new business initiatives. Now it is also possible to create RESTful services (RESTful interfaces typically require less development effort and use less runtime overhead) and include those in many new technologies easier that using the WSDL or Web service protocol. Also as many systems move to Web 2.0 interfaces they can be used there also with mash-up tools to create the new user facing systems. You can also use both Web Services and RESTful services in mash-up tools depending on designer preferences.
If you are using Microsoft tooling like SharePoint 2010 those services can be easily incorporated into the design of the SharePoint 2010 applications also. In SharePoint 2010 you can also use either service (REST or WSDL).
In all the scenarios mentioned, the underlying IMS applications (transactions) do not need to be changed; they just continue to work as they have for decades. The important part is to focus on the business need required to drive the use of the new technology, and not replacing existing software just because it’s been running for awhile. Use IMS with the new technology, it will be a lot easier and less painful.
For Information on using IMS with REST, Web Services, SharePoint 2010 see www.gtsoftware.com.
