• 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:

    • Share on Reddit (Opens in new window) Reddit
    • Share on Facebook (Opens in new window) Facebook
    • Share on LinkedIn (Opens in new window) LinkedIn
    • Share on X (Opens in new window) X
    • Email a link to a friend (Opens in new window) Email

    Tags:

    Sponsored by
    JAMS Software

    One Scheduler. IBM i, Windows, Linux, and More.

    IBM i teams trust JAMS to schedule and orchestrate jobs across every platform in their environment. Centralized visibility, cross-platform dependency management, and alerts that reach the right person before the business feels it.

    Fewer than 5% of IBM i shops run IBM i only. The rest are managing cross-platform dependencies — often without a clear picture of how they connect. JAMS draws that map, enforces those dependencies automatically, and gives your team a single place to monitor, manage, and recover when something goes wrong.

    If you are running hundreds of CL scripts and custom RPG processes, bring them as-is. JAMS runs them exactly as they do today — except now they are visible, monitored, and part of an orchestrated workflow instead of scattered across folders only one person knows about.

    No consumption-based pricing. No surprise bills when your workload spikes. You pay based on how many machines JAMS talks to — that’s it.

    Learn More → https://jamsscheduler.com/lp/ibm-i

    Share this:

    • Share on Reddit (Opens in new window) Reddit
    • Share on Facebook (Opens in new window) Facebook
    • Share on LinkedIn (Opens in new window) LinkedIn
    • Share on X (Opens in new window) X
    • Email a link to a friend (Opens in new window) Email

    Simplify Complex Conditions OS/400 Alert: Trials and Betas

    Leave a ReplyCancel reply

Content archive

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

Recent Posts

  • Big Blue Ships Bob 2.0 And Premium Package For IBM i
  • Your IBM i Jobs Don’t Live On An Island Anymore
  • FalconStor Creates Cloud Clean Room To Prove Backup Recoveries Work
  • Talking Git On IBM i With A Bunch Of IBM i Gits
  • IBM i PTF Guide, Volume 28, Number 22
  • More Power Systems Price Hikes, This Time They Are “Directional”
  • AI Is Not Just For Developers, It Is For Everyone At Your Company
  • Guru: Finding Data In The Forest – Exploring Three-Part Naming In SQL
  • Former IBMer’s New Book Puts The Midrange In The Spotlight
  • Have You Tried To Buy A Server Lately?

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