• 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

    DevSecOps & Peer Review – The Power of Automation

    In today’s fast-paced development environments, security can no longer be an afterthought. This session will explore how DevSecOps brings security into every phase of the DevOps lifecycle—early, consistently, and effectively.

    In this session, you’ll discover:

    • What DevSecOps is and why it matters?
    • Learn how to formalize your security concerns into a repeatable process
    • Discover the power of automation through pull requests, approval workflows, segregation of duties, peer review, and more—ensuring your data and production environments are protected without slowing down delivery.

    Whether you’re just getting started or looking to enhance your practices, this session will provide actionable insights to strengthen your security posture through automation and team alignment to bring consistency to the process.

    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

    One thought on “Retrieve the System Name”

    • Chejo QR says:
      October 24, 2019 at 1:41 pm

      MUCHAS GRACIAS, THANK YOU VERY MUCH !!! you saved me !!! me salvaste !!!, The SQL Solution was the easiest and simply !

      Reply

    Leave a Reply Cancel reply

Volume 4, Number 2 -- January 28, 2004
THIS ISSUE
SPONSORED BY:

T.L. Ashford
Profound Logic Software
WorksRight Software
Twin Data
SuSE Linux

Table of Contents

  • Application and Data Integration Between Linux and OS/400
  • To Commit or Not to Commit?
  • Simplify Complex Conditions
  • Retrieve the System Name
  • OS/400 Alert: Trials and Betas

Content archive

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

Recent Posts

  • What You Will Find In IBM i 7.6 TR1 and IBM i 7.5 TR7
  • Three Things For IBM i Shops To Consider About DevSecOps
  • Big Blue Converges IBM i RPG And System Z COBOL Code Assistants Into “Project Bob”
  • As I See It: Retirement Challenges
  • IBM i PTF Guide, Volume 27, Number 41
  • Stacking Up Power11 Entry Server Performance To Older Iron
  • Big Blue Boosts IBM i Support In Instana, Adds Tracing
  • It Is Time To Tell Us What You Are Thinking And Doing
  • IBM i PTF Guide, Volume 27, Number 40
  • The GenAI Boom Is Only Slightly Louder Than The Dot Com Boom

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