This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
-- | |
-- Subject: HTTP Servers and FRCA | |
-- Author: Scott Forstie | |
-- Date : February, 2024 | |
-- Features Used : This Gist uses SQL PL, qsys2.object_statistics, qsys2.syspartitionstat, | |
-- SQL aliases, SQL built-in functions, UDTF, qsys2.ifs_read, and pipe | |
-- | |
-- HTTP Server configuration detail resides in the IFS. | |
-- The HTTP Server instance file (QUSRSYS/QATMHINSTC *FILE) | |
-- points to the IFS path to use for each specific server. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
-- | |
-- Author: Scott Forstie | |
-- Date : July 14, 2020 | |
-- | |
-- Question: How can I use SQL to validate that a string only contains an approved list of characters? | |
-- Answer : The TRANSLATE() built-in function. | |
-- | |
-- TRANSLATE replaces the allowed characters with blanks. | |
-- Then, RTRIM throws all the blanks away. | |
-- Then, if the resulting LENGTH is zero, you can conclude that the string only contained allowed characters. |