IBMi (AS400) fans only : UTILITIES - How to retrieve physical file description

By -





                               






FFD Utility program

 

This program allows you to see the information relating to a physical file (or Table) and its logical views on a 132-column screen.
This program also allows you to filter the columns of the key fields. This is very handy to check if the logical view we are looking for already exists.







Type FFD (F4)

FFD Command





Type physical file name end press ENTER

FFD Command





The program lists all column names with their attributes.

list of all column names with their attributes





The program lists all column names with their attributes.

list of all column names with their attributes






Type F5 to work with Logical wiew.

FFD Logical wiew list





You can filter each column in this way:

FFD Logical wiew list







Type 1 to select a row then ENTER:

FFD Logical wiew list





The program show the keyfield list:

FFD keyfield list

Finally, you can print the processing result: 



FFD Field list



FFD Index list





This is a way to retrieve physical file description and its logical view




If you are interested in this program Download FFD *SAVF 


If you have a profile on PUB400, type ADDLIBLE FFD11
then type FFD (F4)
then fill in the fields
TABLE_NAME (your table name on PUB400)
LIBRARY (your PUB400 library or *LIBL)

to test my FFD (Phisical file description) utility.






#IBMiSample



Need some help loading the *savf? 
HOW TO GET *SAVF FROM YOUR DESKTOP TO YOUR IBM I SYSTEM

I appreciate all the comments made on this blog.




I added a new feature - Create Phisical file Sql Source in QTEMP

Generate SQL


For example, from the CLANA00F physical file I get the DLL:

--  Generate SQL                                                              
--  Version:                   V7R5M0 220415                                  
--  Generated on:              11/21/22 10:52:57                              
--  Relational Database:       PUB400                                         
--  Standards Option:          Db2 for i                                      
                                                                              
CREATE TABLE VDOTEST1/CLANA00F (                                              
--  SQL150B   10   REUSEDLT(*NO) in table CLANA00F in VDOTEST1 ignored.       
  STATO_CLIENTE_A_ANNULLATO FOR COLUMN CLANN0     CHAR(1) CCSID 273 NOT NULL  
  DEFAULT '' ,                                                                
  CODICE_CLIENTE FOR COLUMN CLCCL0     NUMERIC(7, 0) NOT NULL DEFAULT 0 ,     
  CODICE_INTESTAZIONE FOR COLUMN CLCIB0     CHAR(3) CCSID 273 NOT NULL DEFAULT
  '' ,                                                                        
  NOME_COGNOME_CLIENTE FOR COLUMN CLNOM0     CHAR(50) CCSID 273 NOT NULL      
  DEFAULT '' )                                                                
                                                                              
  RCDFMT CLANA      ;                                                         
                                                                              
LABEL ON COLUMN VDOTEST1/CLANA00F           

Comments

  1. TristanproApril 20, 2022 at 2:18 PM

    I liked this a lot. I need the program behind this.

    ReplyDelete
    Replies
    1. Aldo SUCCIApril 26, 2022 at 10:33 AM

      If you are interested in this program write me at: aldo.succi.63 (at) gmail.com

      Delete

Post a Comment

Popular posts from this blog

(IBM i fans only) Efficient WRKSPLF with WSF - How to Search string into spooled files, Sort, and Generate PDFs on IBMi

By -
Image
Searching Spooled Files Made Easy: A Unique Solution Managing spooled files efficiently is crucial for users dealing with numerous rows of print data. IBM's WRKSPLF command provides a standard way to interact with spooled files, but it lacks certain features that can significantly enhance user experience. In this article, we'll delve into a powerful functionality that IBM doesn't offer — the ability to search among spooled file lists. Our goal is to highlight the advantages of this capability and introduce a practical solution. The Limitations of Standard WRKSPLF While the WRKSPLF command is a handy tool for working with spooled files, it falls short in certain aspects. One prominent limitation is the inability to search efficiently through the list of spooled file rows. Users often find it challenging to quickly locate specific files based on criteria like creation date, status, or content. Introducing a Unique Solution: WSF (WorkSpooledFiles) To address the limitations of...
Read more

(IBM i fans only) Detecting and Handling Non-Printable Characters in DB2 SQL Using LOCATE() and REPLACE() Functions

By -
Image
When working with DB2 SQL on the IBMi platform, one of the challenges we might encounter is dealing with non-printable characters in our data. These are characters that don't have a direct representation on a standard keyboard and can cause display programs to crash if not handled properly. For this example, we'll be working with the CLANA00F file, which contains customer data. You can find details on how to create this file on my blog post here . Non-printable characters can sneak into our records for various reasons, and to prevent issues, we can run an SQL query that uses the LOCATE() function. This function returns the position of the first occurrence of a substring within a string, allowing us to detect these problematic characters. Suppose we have a customer name with a non-printable character, specifically the EBCDIC '0D' character, which corresponds to the "Carriage Return" (CR) control character in ASCII. To find this character in our records, we can ...
Read more

(IBM i fans only) How to Sniff User Access

By -
Image
If you need to monitor user access on your IBM i system, you can use SQL to query the history log. Note: At the end of this post, you'll find a request directly addressed to you, the readers. Here’s a simple example of how you can do this: SELECT MESSAGE_ID,        MESSAGE_TIMESTAMP,        FROM_USER,        MESSAGE_TEXT     FROM TABLE (             QSYS2.HISTORY_LOG_INFO()         )     WHERE message_id IN ('CPF1164', 'CPF1124')           AND FROM_USER IN ('QSECOFR', 'QSYS', 'QSYSOPR')     ORDER BY MESSAGE_TIMESTAMP In this query: - QSYS2.HISTORY_LOG_INFO(): This function retrieves information from the history log. -  message_id IN ('CPF1164', 'CPF1124') : Filters the results to include only specific message IDs, which indicate sign-on and sign-off events. - FROM_USER in ('QSECOFR', 'QSYS', 'QSYSOPR'): Filters the resu...
Read more