• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • Retrieve the System Name

    January 28, 2004 Hey, Ted

    At the end of reports, I print a special line that indicates that the report is complete. In addition to the message “end of report,” I print the qualified job name, qualified program name, and in the case of SQL programs, the last value of the SQL status variable. These values help me to debug and troubleshoot problems. I’d like to add one more bit of information.

    We recently got a new machine with logical partitioning, and we have set up a partition to use as a test environment. I would like to add the system name to the end-of-report line to help me distinguish between reports generated on the two systems.

    –Andrew

    There are several ways to retrieve the system name.

    One method is to create a small CL program that runs the Retrieve Network Attributes (RTVNETA) command and passes the system back to the caller through a parameter.

    pgm       parm(&SysName)         
    
    dcl       &SysName    *char     8
    
    rtvneta   sysname(&SysName)  
    
    endpgm                       
    

    Assuming the CL program has the name GETSYSNAME, an RPG caller would look something like this:

    Fqsysprt   o    f  132        printer oflind(*inof)             
                                                                    
    D PrtLine         ds           132                              
    D SysName         s              8                              
                                                                    
    D GetSysName      pr                  extpgm('GETSYSNAME')      
    D  SysName                       8a                             
                                                                    
    D psds           sds                                            
    D  psdsProcName           1     10                              
    D  psdsLibName           81     90                              
    D  psdsJobName          244    253                              
    D  psdsUserName         254    263                              
    D  psdsJobNbr           264    269                              
                                                                    
    C                   callp     GetSysName (SysName)              
    C                   eval      PrtLine = '* End of report *  ' 
    C                             + 'Job(' + psdsJobNbr + '/'       
    C                             + %trim(psdsUserName) + '/'    
    C                             + %trim(psdsJobName)           
    C                             + ')  Program('                
    C                             + %trim(psdsLibName) + '/'     
    C                             + %trim(psdsProcName)          
    C                             + ')  System(' + %trim(SysName)
    C                             + ')'                          
    C                   write     qsysprt       PrtLine          
    C                   eval      *inlr = *on                    
    

    The output of the program shows the system name, as you requested:

    * End of report * Job(877501/THOLT/S9) Program(THOLT/E1) System(TS400)
    

    A second method is to use a SQL special register. You may spell the special register CURRENT SERVER or CURRENT_SERVER.

    C/exec sql                  
    C+     values current server
    C+       into :SysName      
    C/end-exec                  
    

    –Ted

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Tags:

    Sponsored by
    ARCAD Software

    Embrace VS Code for IBM i Development

    The IBM i development landscape is evolving with modern tools that enhance efficiency and collaboration. Ready to make the move to VS Code for IBM i?

    Join us for this webinar where we’ll showcase how VS Code can serve as a powerful editor for native IBM i code and explore the essential extensions that make it possible.

    In this session, you’ll discover:

    • How ARCAD’s integration with VS Code provides deep metadata insights, allowing developers to assess the impact of their changes upfront.
    • The role of Git in enabling seamless collaboration between developers using tools like SEU, RDi, and VS Code.
    • Powerful extensions for code quality, security, impact analysis, smart build, and automated RPG conversion to Free Form.
    • How non-IBM i developers can now contribute to IBM i projects without prior knowledge of its specifics, while ensuring full control over their changes.

    The future of IBM i development is here. Let ARCAD be your guide!

    Watch Now

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Bsafe Bolsters OS/400 Security Software with New Logging, Alerts New Domino and Blue Domino: A Little of Both At Lotusphere

    Leave a Reply Cancel reply

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • Liam Allan Shares What’s Coming Next With Code For IBM i
  • From Stable To Scalable: Visual LANSA 16 Powers IBM i Growth – Launching July 8
  • VS Code Will Be The Heart Of The Modern IBM i Platform
  • The AS/400: A 37-Year-Old Dog That Loves To Learn New Tricks
  • IBM i PTF Guide, Volume 27, Number 25
  • Meet The Next Gen Of IBMers Helping To Build IBM i
  • Looks Like IBM Is Building A Linux-Like PASE For IBM i After All
  • Will Independent IBM i Clouds Survive PowerVS?
  • Now, IBM Is Jacking Up Hardware Maintenance Prices
  • IBM i PTF Guide, Volume 27, Number 24

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2025 IT Jungle