IBMi (AS400) fans only : Fully Free RPG: Example to get day of week

By -

day of week




#IBMiSample


GETDAY.RPGLE

      **FREE
      // ***********************************************
      // *  Fully Free RPG Sample to get day of week   *
      // *                                             *
      // *  Parameters:                                *
      // *  ppXDT0         6s 0 Date to decode ymd     *
      // *  ppXDAY        10A   day of week            *
      // *                                             *
      // *  How to call (for example):                 *
      // *  CALL PGM(ROUT58) PARM('190202' '   ')      *
      // ***********************************************
       ctl-opt DFTACTGRP(*NO);

       dcl-s tmpDate   char(10) Inz('2010-10-31');
       dcl-s tmpDate2  char(10) Inz('2010-10-31');
       dcl-s dayNbr    packed(11: 0) Inz(0);
       //    * PARAMETRI RICEVUTI (EX *ENTRY PLIST PARM)
       Dcl-pi GETDAY;
         ppXDT0 zoned(6);
             ppXDAY char(3);
       End-pi;
       tmpDate  = %char(%date(ppXDT0:*ymd):*iso0); // yymmdd to ccyymmdd
       tmpDate2 = %subst(tmpDate:1:4) + '-' + %subst(tmpDate:5:2) + '-'
       +%subst(tmpDate:7:2);
       // 0=Mon, 1=Tue, 2=Wed, 3=Thu, 4=Fri, 5=Sat, 6=Sun
       dayNbr = %rem(%diff(%date(tmpDate2):d'0001-01-01':*days):7);
       select;
       when dayNbr = 0;
         ppXDAY = 'Mon';
       when dayNbr = 1;
         ppXDAY = 'Tue';
       when dayNbr = 2;
         ppXDAY = 'Wed';
       when dayNbr = 3;
         ppXDAY = 'Thu';
       when dayNbr = 4;
         ppXDAY = 'Fri';
       when dayNbr = 5;
         ppXDAY = 'Sat';
       when dayNbr = 6;
         ppXDAY = 'Sun';
       endsl;
       *inlr = *on;






Thanks to Anonymous this second version using SQL dayname is better:


GETDAYSQL.sqlrpgle 

      **FREE                                               
      // ********************************************      
      // Fully Free RPG Sample to get day of week   *      
      // Parameters:                                *      
      // ppXDT0         6s 0 Date ymd to decode     *      
      // ppXDAY         3A   day of week            *      
      // ********************************************      
      // CALL PGM(GETDAYSQL) PARM('210209' 'xxx')   *      
      // ********************************************      
       ctl-opt DFTACTGRP(*NO);                             
       dcl-s wkDate    date(*iso) ;                        
       // Received parms        
       Dcl-pi GETDAYSQL;                                   
         ppXDT0 zoned(6);                                  
         ppXDAY char(3);                                   
       End-pi;                                             
       wkDate = %date(ppXDT0: *ymd);                       
       exec sql set :ppXDAY = substr(dayname(:wkDate), 1, 3);
       dsply ppXDAY;                                          
              *inlr = *on;   

 

 I appreciate all the comments made on this blog.

 


Comments

  1. AnonymousFebruary 4, 2021 at 5:46 PM

    Well done! Thank you.

    ReplyDelete
    Replies
    1. www.parvez.comMay 26, 2024 at 1:16 PM

      PGM
      DCL VAR(&DAYOFWEEK) TYPE(*CHAR) LEN(4)
      RTVSYSVAL SYSVAL(QDAYOFWEEK) RTNVAR(&DAYOFWEEK)
      CHGVAR VAR(&DAYOFWEEK) VALUE(%SST(&DAYOFWEEK 2 3))
      SNDPGMMSG MSG("DOW: "&DAYOFWEEK)
      ENDPGM

      Delete
    2. Aldo SUCCIMay 26, 2024 at 8:00 PM

      Thank you for your beautiful example

      Delete
  2. AnonymousFebruary 9, 2021 at 6:01 AM

    //--Simpler with SQL:

    exec sql set :Nbr = dayofweek(:wkDate) ;

    exec sql set :Nbr = dayofweek_iso(:wkDate) ;

    The DAYOFWEEK and DAYOFWEEK_ISO functions are basically the same, they return an number that represents the day of the week.

    The difference is when the week starts. For DAYOFWEEK 1 is Sunday and 7 is Saturday. For DAYOFWEEK_ISO 1 is Monday and 7 is Sunday.

    ReplyDelete
  3. AnonymousFebruary 9, 2021 at 2:32 PM

    I would do this on this way:

    Create free compileTime array as ds.

    dcl-ds Week;
    *n char(3) inz('Mon');
    *n char(3) inz('Tue');
    *n char(3) inz('Wed');
    *n char(3) inz('Thu');
    *n char(3) inz('Fri');
    *n char(3) inz('Sat');
    *n char(3) inz('Sun');
    Weekday char(3) dim(7) pos(1);
    end-ds;

    dsply Weekday(dayNbr);

    I don't like CTA's at the end of the programs

    ReplyDelete
  4. AnonymousFebruary 9, 2021 at 9:49 PM

    If your goal is to get the name of the day, you can do it in one line using SQL:

    exec sql set :day = dayname(:wkDate);

    For example, to get the name of today:

    exec sql set :day = dayname(Current_Date);

    ReplyDelete
  5. AnonymousFebruary 9, 2021 at 10:01 PM

    If you want just the first three characters of the day name as your program does, you can do it in one line using SQL:

    exec sql set :day = substr(dayname(:wkDate),1,3);

    ReplyDelete
  6. Aldo SUCCIFebruary 10, 2021 at 2:35 PM

    thanks again.
    I updated the example with
    exec sql set :ppXDAY = substr(dayname(:wkDate),1,3);

    ReplyDelete

Post a Comment

Popular posts from this blog

IBMi (AS400) 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

IBMi (AS400) 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 results to include only messages from specific users. Update 28/07/2024: A Smart Enhancem
Read more

IBMi (AS400) 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