Sidebar

The CL Corner: More on View Flexibility

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

Let's review of some of the SQL functions available.

 

In the February 2015 CL Corner, A More Flexible Interface to the RUNSQL CL Command, we saw how to create a command of our own, CRTSQLVIEW, to create views by utilizing some of the built-in functions provided by the SQL language. The CRTSQLVIEW command removed the need for us to write a custom program per view (which was covered in the January 2015 article Enhancing WRKQRY Reports the Easy Way. These previous articles used the SQL built-in functions of VarChar and DayName to return the mixed-case name of the day for a date field. This month, using CRTSQLVIEW, we'll be looking at additional built-ins that are available to you.

 

Deciding which built-in to start with today turned out to be quite easy. I have received quite a few notes from readers who have a little problemnamely, that the previous articles used date fields while their production databases store dates in a combination of alphanumeric and packed-decimal fields. To look at what's available using a view approach, we'll first create a new physical file where we're storing date values using a variety of formats and data types. This file will be called TESTDATA, and here's the DDS definition for the file.

 

R RECORD                    

  DATFLD          L         

  MDYALPHA       6A         

  YMDALPHA       6A         

  MDYNBR         6P 0       

 

The first field, DatFld, is defined as a date field, which is similar to how we defined TskStrDat in the previous articles. The second field, MDYAlpha, is defined as a 6-byte character field and will be used to store date values using a MDY format. The third field, YMDAlpha, is defined as a 6-byte character field and will be used to store date values using a YMD format. The fourth field, MDYNbr, is defined as a 6-digit packed-decimal field and will be used to store date values using a MDY format.

 

Assuming that the previous source is stored in member TESTDATA of QDDSSRC, then you can create the file using this command:

 

CRTPF FILE(TESTDATA)

 

To write two test records to the file, prompt and then run the following RUNSQL commands:

 

                           Run SQL Statements (RUNSQL)                          

                                                                                

 Type choices, press Enter.                                                     

                                                                                

 SQL  . . . . . . . . . . . . . . > Insert into TESTDATA Values('2015-03-21', '0

32115', '150321', 032115)                                                       

                                                                     ...        

 Commitment control . . . . . . . > *NONE         *CHG, *UR, *CS, *ALL, *RS...  

 Naming . . . . . . . . . . . . .   *SYS          *SYS, *SQL                    

 

 

                           Run SQL Statements (RUNSQL)                          

                                                                                

 Type choices, press Enter.                                                     

                                                                                

 SQL  . . . . . . . . . . . . . . > Insert into TESTDATA Values('2015-12-25', '1

22515', '151225', 122515)                                                       

                                                                     ...        

 Commitment control . . . . . . . > *NONE         *CHG, *UR, *CS, *ALL, *RS...  

 Naming . . . . . . . . . . . . .   *SYS          *SYS, *SQL                    

 

The first command writes one record with the date March 21 2015 stored in each of the four fields defined to TESTDATA. The second command writes a second record using the date December 25 2015.

 

Now let's see what we can do to get those non-date data type fields MDYAlpha, YMDAlpha, and MDYNbr to become "true" date fields.

 

We'll first tackle the alphanumeric fields MDYAlpha and YMDAlpha. SQL provides the built-in TIMESTAMP_FORMAT, which returns a timestamp that's based on a string definition of how to interpret an input character value. This string definition allows you to indicate where in the input character value to find, among other things, a 2-digit year (YY), a 4-digit year (YYYY), a 2-digit month (MM), and a 2-digit day (DD). For instance, using TIMESTAMP_FORMAT as in

 

TIMESTAMP_FORMAT(MDYAlpha, 'MMDDYY')

 

indicates that the field MDYAlpha contains a formatted value that should be converted to a timestamp, where the first two bytes identify a 2-digit month, the next two bytes a 2-digit day, and the last two bytes a 2-digit year. So a MDYAlpha value such as '032115' (like the first record we wrote to TESTDATA) would be converted to a timestamp value of '2015-03-21-00.00.00.00000'.

 

Along the same lines, using TIMESTAMP_FORMAT as in

 

TIMESTAMP_FORMAT(YMDAlpha, 'YYMMDD')

 

indicates that the field YMDAlpha contains a YMD formatted value that should be converted to a timestamp. A YMDAlpha value such as '151225' (like the second record we wrote to TESTDATA) would then be converted to a timestamp value of '2015-12-25-00.00.00.000000'.

 

With that introduction let's now use CRTSQLVIEW to create a view, using the fields MDYAlpha and YMDAlpha, to again determine the name of the day they represent. Prompt and fill in the CRTSQLVIEW command as shown below:

 

                          Create SQL View (CRTSQLVIEW)                  

                                                                        

 Type choices, press Enter.                                             

                                                                        

 View . . . . . . . . . . . . . . > TESTVIEW      Name                  

   Library  . . . . . . . . . . .     *CURLIB     Name, *CURLIB         

 Table  . . . . . . . . . . . . . > TESTDATA      Name                  

   Library  . . . . . . . . . . .     *LIBL       Name, *LIBL, *CURLIB  

                                                                                

 Columns:                                                                       

   To column  . . . . . . . . . . > DATFLD        Name                          

   From . . . . . . . . . . . . .   *SAME                                       

                                                                                

   To column  . . . . . . . . . . > DATFLDDOW     Name                          

   From . . . . . . . . . . . . . > Varchar(DayName(DatFld), 10)              

                                                                                

   To column  . . . . . . . . . . > MDYDOW        Name                          

   From . . . . . . . . . . . . . > Varchar(DayName(Timestamp_Format(MDYAlpha, 

'MMDDYY')), 10)                                                              

                                                                                

   To column  . . . . . . . . . . > YMDDOW        Name                          

   From . . . . . . . . . . . . . > Varchar(DayName(Timestamp_Format(YMDAlpha, 

'YYMMDD')), 10)                            

 

 

The previous command creates a view named TESTVIEW. If you now go into WRKQRY, select the file TESTVIEW, and use F5 to run the query, you should see this:

 

        DATFLD      DATFLDDOW   MDYDOW      YMDDOW     

 000001 2015-03-21  Saturday    Saturday    Saturday   

 000002 2015-12-25  Friday      Friday      Friday     

 

As with the two earlier articles, the first column (titled DATFLD) is simply the value of the DatFld field followed by the day of the week (DATFLDDOW). What's new is that now we also see the day of the week for the alphanumeric fields MDYAlpha (MDYDOW) and YMDAlpha (YMDDOW).

 

Before handling the packed-decimal field MDYNbr, let's also see how we might be able to simplify existing queries that have been working with alphanumeric "date" fields such as MDYAlpha and YMDAlpha. Some of you may in the past have constructed date fields within WRKQRY such as the MyDate field shown below.

 

Field       Expression                         Column Heading        Len   Dec

MYDATE      Date(Substr(MDYAlpha, 1, 2) || '/                                 

            ' || Substr(MDYAlpha, 3, 2) || '/                                 

            ' || Substr(MDYAlpha, 5, 2))                                      

 

 

While you can continue to construct date fields in this manner, you could also have CRTSQLVIEW do it using the SQL DATE built-in. For instance, adding the following COLUMNS entry to our previous command will create the field MyDate in TESTVIEW, allowing you to eliminate the construction shown above.

 

Columns:                                                                       

   To column  . . . . . . . . . . > MYDATE        Name                          

   From . . . . . . . . . . . . . > Date(Timestamp_Format(MDYAlpha, 'MMDDYY'))

 

 

Returning to the handling of "date" values being stored in numeric fields, the TIMESTAMP_FORMAT built-in only supports an input character value for the "date" to be interpreted. So what we need to do is convert the numeric field MDYNbr to a character string. There are several SQL built-ins that can accomplish this, with each of them having slightly different characteristics. There is, for instance, the built-in CHAR, which is often used as it returns a fixed-length character string representation of a number. This built-in, however, has a definite consideration when it comes to handling numeric valuesnamely, that it removes leading zeroes. So if we have a numeric value such as 032115 (the value of MDYNbr for the first record we wrote to TESTDATA), the CHAR built-in will return a character value of '32115' rather than a value of '032115'. This will be a problem as TIMESTAMP_FORMAT is looking for a 2-digit month (though a MDYNbr value of 122515 would work just fine). As the number of significant digits in a numeric date can vary, we will want to use the DIGITS built-in. DIGITS returns the character-string representation of the absolute value of a number and retains leading zeroes.

 

With this knowledge, we can now get the day of the week for MDYNbr by adding another column definition to our CRTSQLVIEW command. This addition will be:

 

 Columns:                                                                       

   To column  . . . . . . . . . . > MDYNBRDOW     Name                          

   From . . . . . . . . . . . . . > Varchar(DayName(Timestamp_Format(Digits(MDYN

br), 'MMDDYY')), 10)                                       

 

This 'From' parameter value is a nesting of several SQL built-ins that result in:

  1. Getting the absolute value of MDYNbr, with leading zeroes, using DIGITS
  2. Converting the value obtained in step 1 to a date using TIMESTAMP_FORMAT, interpreting this value as being MMDDYY
  3. Obtaining the date portion of the value obtained in step 2 and getting the name of that day using DAYNAME
  4. Truncating the name of day value obtained in step 3 to the first 10 characters using VARCHAR

 

Today, we have reviewed several additional built-ins that can used from CL to create views over data, views that can in turn be used by utilities such as WRKQRY or processed as an input file by a CL program. The built-ins introduced were TIMESTAMP_FORMAT (which can also be accessed using the name TO_DATE if you prefer less typing, though note that all of the Information Center documentation is found under the name TIMESTAMP_FORMAT), DATE, CHAR, and DIGITS. We have only touched on what all could be used, though in terms of the built-ins found here, so I encourage you to review what's possible.

 

More CL Questions?

Wondering how to accomplish a function in CL? Send your CL-related questions to me at This email address is being protected from spambots. You need JavaScript enabled to view it.. I'll try to answer your burning questions in future columns.

 

Bruce Vining

Bruce Vining is president and co-founder of Bruce Vining Services, LLC, a firm providing contract programming and consulting services to the System i community. He began his career in 1979 as an IBM Systems Engineer in St. Louis, Missouri, and then transferred to Rochester, Minnesota, in 1985, where he continues to reside. From 1992 until leaving IBM in 2007, Bruce was a member of the System Design Control Group responsible for OS/400 and i5/OS areas such as System APIs, Globalization, and Software Serviceability. He is also the designer of Control Language for Files (CLF).A frequent speaker and writer, Bruce can be reached at bvining@brucevining.com. 


MC Press books written by Bruce Vining available now on the MC Press Bookstore.

IBM System i APIs at Work IBM System i APIs at Work
Leverage the power of APIs with this definitive resource.
List Price $89.95

Now On Sale

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things


    Read Node.js for Enterprise IBM i Modernization Now!

     

  • Profound Logic Solution Guide

    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 companyare not aligned with the current IT environment.

    Get your copy of this important guide today!

     

  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.

     

  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline

     

     

  • The Power of Coding in a Low-Code Solution

    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:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Why Migrate When You Can Modernize?

    LANSABusiness 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.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.

     

  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    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:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact

     

  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.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. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using NodeRun.com as a pre-built development environment

     

     

  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.

     

     

  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.

     

     

  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails

     

  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.

     

     

  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen 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:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave 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.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY 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.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine 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:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. 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:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot 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:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.