Starting the Host Database Server Daemon After an OS/400 V5R1 Upgrade

September 4, 2002 Timothy Prickett Morgan

Hey, Joe:

We just upgraded our V4R5 AS/400 to OS/400 V5R1, and we have a problem. After the upgrade, the host database server daemon (as-database) won’t start when we issue the Start Host Server (STRHOSTSVR) command with the *ALL option. This is affecting some of our remote access applications, including some WebSphere applications.

What’s going on here, and how do I get this host server running again?

— Jake

I ran into this problem on a recent OS/400 V5R1 upgrade, and it’s an easy fix once you know what’s going on. As you already know, issuing the STRHOSTSVR command in one of two configurations will start your host database server daemon. The daemon can be started individually by specifying *DATABASE under the STRHOSTSVR Server type (SERVER) parameter, as per the following example:

STRHOSTSVR   SERVER(*DATABASE) 

Or it can be started in conjunction with all the other OS/400 host servers by entering *ALL in the SERVER parameter, as shown here:

STRHOSTSVR  SERVER(*ALL)

The problem with starting the database server daemon after a V5R1 upgrade is that IBM moved the programs that start the daemon to a different library, but your OS/400 upgrade didn’t necessarily change the routing entries in the QSERVER subsystem that start the server. OS/400 is getting confused as it tries to execute a program that isn’t in the right place anymore. Fortunately, fixing the call is easy. Here’s how to do it.

The program that controls host database server daemon activation is QZDASRVSD, and in OS/400 V4R5, it resided in the QIWS library. With OS/400 V5R1, IBM moved QZDASRVSD to the QSYS library. When you use the STRHOSTSVR command to start the database server, a request is sent to the QSERVER subsystem, which, in turn, uses a routing entry that calls the QZDASRVSD program to activate the server. The QSERVER routing entry that triggers QZDASRVSD probably looks something like this on your system:

In addition, there may be a second QZDA program referenced in a QSERVER routing entry that has also moved from the QIWS library to the QSYS library, and that routing entry should also be changed. This program’s name is QZDAINIT, and its QSERVER routing entry probably looks like this:

You can view the QSERVER routing entries for your system by entering the Work with Subsystem Descriptions (WRKSBSD) command as follows:

WRKSBSD   SBSD(QSERVER)

Next, select option 5, Display, followed by option 7, Routing Entries. The problem that’s occurring here is that the QSERVER routing entry is still pointing to library QIWS for QZDASRVSD and QZDAINIT, while the V5R1 upgrade has moved these programs to library QSYS.

To change the routing entries to point to the QSYS library for these programs, you can execute the following Change Routing Entry (CHGRTGE) commands for the QSERVER subsystem:

CHGRTGE SBSD(QSERVER) SEQNBR(600) PGM(QSYS/QZDASRVSD)

CHGRTGE SBSD(QSERVER) SEQNBR(400) PGM(QSYS/QZDAINIT)

By entering the CHGRTGE commands this way, any parameters that aren’t changed will retain their previous value. Also note that your routing entry parameters may be slightly different from this example. Double-check the actual location of the QZDASRVSD and QZDAINIT programs on your system, as well as the QSERVER routing entries before you start. And be sure to include your values in this CHGRTGE statement, if they are different from what’s shown here.

You can execute this command while the QSERVER subsystem is active and the change will take effect immediately. Once changed, try to restart the host database server using the STRHOSTSVR command with the *DATABASE option, and your database server should now properly start up.

— Joe

Sponsored By ADVANCED SYSTEMS CONCEPTS

SEQUEL meets all your iSeries and AS/400 data access needs in a single, integrated solution: Windows, Web or host user interfaces Convert AS/400 data into PC file formats E-mail or FTP query results, reports and spool files Run-time prompted queries and reports for end users IF-THEN-ELSE logic in queries and reports Report, form and label formatting second to none Easily convert date fields, character-to-numeric, numeric-to-character and other data manipulation SORT or JOIN using a calculated field Quick summarization of data with Tabling function Run multiple SEQUEL requests as one with the SEQUEL Scripting function OLAP Business Intelligence at a fraction of the cost of comparable solutions Take 6 minutes to view a SEQUEL ViewPoint ScreenCam movie to see how simple Windows-based AS/400 and iSeries data access can be! In just a few short minutes, you can find out ways to make your job easier and improve data access throughout your organization. Download the ViewPoint movie here . For more information or a FREE trial of SEQUEL, call 847/605-1311 or visit Advanced Systems Concepts.