15
Tue, Oct
6 New Articles

Managing SQL Is Easy with Change Management Tools

SQL
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

There's no reason not to forge ahead with new techniques such as SQL as long as you have the right tools in place.

 

Structured Query Language (SQL) is a keyword-oriented language, which makes it easy to learn and use, and it's an excellent application development tool. You can define data, manipulate it, and query it to get fast results.

 

SQL is also an industry standard, so learning it on the IBM i means you've learned it for other platforms as well. And that means you can increase your application's portability, yet keep the way you access the database standard. That simplifies maintenance of your systems, and it makes development easier, which in turn leads to productivity. SQL is required if you want to move data between platforms effectively and efficiently.

 

SQL can be used interactively on the IBM i, or it can be embedded within the programs that make up your applications. This article examines some SQL techniques and the issues with using those techniques. It also offers some solutions to help you manage SQL items.

Setting the Stage

Let's assume you've been asked to develop a new employee time-tracking system. This system will need to run on the IBM i as well as other platforms. Because SQL is the same regardless of platform, it's a good choice for designing this new system.

 

To start, you would figure out what information the system would need and design the database. In this example, you would surely need an employee master file that would contain information like name, date of hire, type of employee, salaried or hourly, etc. The information in this file would relate to other files, like the employee type code file, the employee status code file, and so on. To keep the data clean, you would probably include a few constraints and possibly use a few foreign keys.

 

In order to create the database tables, you would more than likely start an SQL session and interactively issue SQL statements. To create the employee master table, you would use the CREATE TABLE statement. (An SQL table is really nothing more than an externally described physical file object.) In that table, you would define the columns (fields) found in the rows (records). It's basically the same architecture you're used to; we're just using some different terms to describe it.

 

The statement you use to create the employee master table might look like the one shown here:

 

CREATE TABLE EMPLOYEE (                                           

  EMPNO DECIMAL(5, 0) NOT NULL DEFAULT 0 ,                        

  EMPLNM CHAR(25) CCSID 37 NOT NULL DEFAULT '' ,                  

  EMPFNM CHAR(25) CCSID 37 NOT NULL DEFAULT '' ,                  

  EMPMIN CHAR(1) CCSID 37 DEFAULT NULL ,                          

  EMPTYP CHAR(1) CCSID 37 NOT NULL DEFAULT '' ,                   

  CONSTRAINT Q_DEMO_SQL_EMPLOYEE_EMPNO_00001 PRIMARY KEY( EMPNO ) )  NOT VOLATILE ;          

 

As you can see, this statement creates the table and identifies the columns that will be in each row. As you proceed through your design, you create other tables that contain other information you need for your system. At some point, you might decide that fields within the employee master table must match fields found in other tables. In other words, you want referential integrity built into the database. You do this with constraints and foreign keys. To make sure the data found in the employee type field in the employee master table is good, you might add a foreign key constraint, as seen here:

 

ALTER TABLE EMPLOYEE                               

  ADD CONSTRAINT Q_DEMO_SQL_EMPLOYEE_EMPTYP_00001 

  FOREIGN KEY( EMPTYP )                           

  REFERENCES EMPTYPE ( TYPCDE )                   

  ON DELETE NO ACTION                             

  ON UPDATE NO ACTION ;         

 

Again, you would use an SQL statement in an interactive setting to perform this operation.

 

Once the database is built, you would start programming over it, again using SQL embedded within your RPG to get the job done efficiently. Code within your programs that accesses these tables might look like what you see here:

 

C/exec sql                          

C+ select count(*)                  

C+   into :counter                  

C+   from demo_sql/employee         

C/end-exec                              

 

This statement would give you an employee count if used in a program.

 

You can see the techniques used here are efficient, easy to use, and portable across platforms.

 

The Issues

The issues arise when you need to maintain these items or enhance an existing system that was built using SQL. Because the database was built using SQL statements in an interactive setting, there's no source code for it. It's possible that the developer who built the system did create some source members containing the SQL statements needed to create a particular file, but what if an ALTER TABLE statement has been used since then? How can you efficiently make changes to these tables and maintain referential integrity without source? The programs using these files may not refer to them in an F-spec. They may only contain embedded SQL as seen above. How do you know what programs a certain table is used in? Where is this table updated? What views and indexes exist over this table?

  

Using SQL is not the issue; everybody should be using it by now. Managing a system created using SQL is the issue. Shops that develop programs using these modern techniques need a modern solution in order to gain control over the process. That's where change management systems come into play.

 

Solutions

Repository-based change management solutions can help you handle the SQL issues mentioned above and more. The central repository contains all the information needed to control a given set of libraries or directories. When the repository is created, automatic processes in a modern change management system can actually parse through your code and find references to files, even if they are found in embedded SQL statements. Look at Figure 1:

 

091008Ray001.jpg

Figure 1: WDSc plug-ins let a developer access the repository. (Click images to enlarge.)

                              

 

In the above screen shot, WDSc plug-ins let a developer access the repository and use the information found there for impact analysis and for making changes. In this example, we can see the employee table has an index and a view associated with it.

 

Figure 2 shows the programs that use the CUSTMAST file in embedded SQL statements. They are located and displayed by the change management tool.

 

091008Ray002.jpg

 

Figure 2: The change management tool displays the programs that use the CUSTMAST file in embedded SQL statements.

 

You can see all references to this table in the system, and further, in most instances, the change management tool can identify how that file is being used in a particular program.

 

The change management repository is the backbone of managing modern applications created with techniques like SQL. Let's examine an SQL change using change management software, and you'll quickly see how useful and effective it is.

 

An SQL Change

All changes within the change management tool are accomplished in a version. A version is nothing more than a container for all the objects, source, and documentation associated with a particular set of changes.

 

In Figure 3, you see the WDSc plug-ins displaying a version, and in this version, you see several tables, an index, and a view. Also, note the command line on the lower left corner of the screen. Using this command line, you can create all the tables and views you would like.

 

091008Ray003.jpg

Figure 3: The WDSc plug-ins display a version.

 

Notice the command that is entered in the command line in the above example: Retrieve SQL Source (RTVSQLSRC). If you need to change a table, you can use the command line and the ALTER TABLE statement and then use the RTVSQLSRC command to quickly and easily create the source needed by the change management system.

 

Figure 4 shows the created source:

 

091008Ray004.jpg

Figure 4: This is the created source code.

 

Notice that the source contains all the statements required not only to recreate the table, but to manage any constraints that may be present. Simply put, it means you can right-click the table and ask the system to compile it for you now. You could make a quick change to the source and issue the compile or make the change and then retrieve the source for use within the change management system when needed. Either way is valid. The RTVSQLSRC command makes it easy to meet the need for source code.

 

Within this version, the CUSTMAST table has been recompiled. Remember that the change management system's repository contains cross-reference information for programs, even if the file is specified in embedded SQL. As a result of recompiling the CUSTMAST table, the list shown in Figure 5 was generated:

 

091008Ray005.jpg

Figure 5: This list was generated as a result of recompiling the CUSTMAST table.

 

These are the programs that need to be recompiled in order to avoid problems in the production environment as this change moves forward. Click one icon, and these will be recompiled for you within the version, and you'll be ready to test them.

 

Your change management system will make sure, even when using SQL, that all items that need to be considered are considered for complete version integrity.

 

Manage Your Apps

Using modern techniques like SQL to create your applications is a must. As applications spread out and move onto other platforms, it just makes sense to implement a simple way to manage these applications.

 

A good change management tool will allow you to create tables, views, and indexes and embed SQL code in your programs with ease. You'll be able to create or make changes to SQL items and transfer them to testing and production using the same proven process that handles your native PF, LF, and RPG source. You will have complete cross-reference support, and your system's referential integrity will be maintained automatically. A modern, comprehensive change management tool will manage all of it for you. There's no reason not to forge ahead with new techniques such as SQL as long as you have the right tools in place.

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: