IBMi (AS400) fans only : How to check the display size on 5250 screen. *DS3 80 columns or *DS4 132 columns

By -



#IBMiSample



In this example CHKDS4.RPGLE detects the screen setting.

As an example I propose a CLP that calls PGM1 if the setting of 80 columns is detected, or calls PGM2 if the setting of 132 columns is detected.


             PGM                                         
                                                         
             DCL        VAR(&ROW) TYPE(*CHAR) LEN(5)     
             DCL        VAR(&COL) TYPE(*CHAR) LEN(5)     
                                                         
             CALL       PGM(CHKDS4) PARM(&ROW &COL)      
                                                         
            /* DISPLAY  80 COLUMNS */                    
            IF         COND(&COL *EQ '00080') THEN(CALL +
                         PGM(PGM1))                      
                                                         
            /* DISPLAY 132 COLUMNS */                    
            IF         COND(&COL *EQ '00132') THEN(CALL +
                         PGM(PGM2))                      
                                                         
             ENDPGM                                      






This is the display which simply writes X to row 2 column 2
whether the display is set to 80 columns or 132 columns.


CHKDS4.DSPF


     A                                      DSPSIZ(27 132 *DS4 +
     A                                             24 80 *DS3)  
     A          R SCREEN                                        
     A                                  2  2'X'                 
     A                                                          













This is the RPGFREE program that check the infds ScreenSize values position 152 and 154.

CHKDS4.RPGLE

**free                                               
//********************************                   
//chk ScreenSize 80/132 colonne  *                   
//********************************                   
dcl-f CHKDS4V workstn infds(ScreenSize) ;            
                                                     
dcl-ds ScreenSize qualified ;                        
  Rows int(5) pos(152) ;                             
  Columns int(5) pos(154) ;                          
end-ds ;                                             
                                                     
dcl-pi CHKDS4;                                       
  p_Rows char(5);                                    
  p_Columns char(5);                                 
end-pi;                       
                
  p_Rows    = %editc(ScreenSize.Rows   :'X');        
  p_Columns = %editc(ScreenSize.Columns:'X');        
*inlr = *on ;                                        





I appreciate all the comments made on this blog.

Comments

  1. AnonymousJanuary 22, 2023 at 5:54 PM

    alternate way to determine the device display size without opening a dspf.
    pardon the spacing...


    DCL &supp *CHAR 1
    CALLPRC PRC('QsnQryModSup') PARM(('4') (&SUPP) (*OMIT) (*OMIT))
    if cond(&supp = '0') then(do) /* only 24x80 screen support */



    * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    * Procedure to check if a given screen mode is valid. The
    * first argument, Mode, can be '3' for 24x80 or '4' for 27x132.
    P ChkScrMode B Export

    D ChkScrMode PI N
    D Mode 1A Const

    D IsValid S 1A

    D QryMode PR ExtProc( 'QsnQryModSup' )
    D DspMode 1A Const
    D IsValid N
    D Handle 10I 0 Options( *Omit )
    D ErrorDS Options( *Omit: *Varsize )
    D Like( ApiErrorDS )

    C Callp QryMode( Mode: IsValid: *Omit: *Omit )
    C Return IsValid
    P ChkScrMode E

    ReplyDelete

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