Monday Morning Blues…
Monday Morning Blues…
Monday mornings can be tough for anyone but for IT and help desk staff it can really be blue. Typically our call volume is highest on Monday where systems have gone offline over the weekend or perhaps error messages were sent that need to be investigated.
Maybe some of these tips will help you…..
Common reasons why your system is not active or sent an error notification:
- Verify your FastFax subsystem is running – WRKACTJOB SBS (FASTFAX)
- Verify iSeries NetServer is started (See below).
- Verify iSeries ODBC & Additional TCPIP jobs are running (See below)
Viewing iSeries NetServer status –
The iSeries(TM) NetServer(TM) Status dialog box contains important statistical information that can help you to effectively administer iSeries NetServer.
You can refresh the current statistics for the system, reset all values to 0, or set the time between refresh requests from the iSeries NetServer Status dialog box.
When you set the time, in minutes, between refresh requests to the host for iSeries NetServer status, the timed refresh values are saved so that you do not have to refresh each time the iSeries NetServer Statusdialog box is opened. Timed refresh values are saved for each system, not for each user.
To display iSeries NetServer status, follow these steps:
- Open iSeries Navigator and connect to the system you want to work with.
- Expand Network > Servers.
- Click TCP/IP to display a list of TCP/IP servers available.
- Right-click iSeries NetServer and select Status.
The iSeries Navigator online help provides more details about each field on the iSeries NetServer Status dialog.
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=%2Frzaii%2Frzaiiodbc25.htm
Additional TCP/IP considerations
Use NETSTAT, STRTCP, and STRHOSTSVR to verify and start TCP/IP functions when troubleshooting an iSeries connection.
Verify that TCP/IP is started with the following command:
NETSTAT *CNN
Note:To verify that TCP/IP is started with iSeries Navigator, you must already have configured your server with TCP/IP , then do the following:
|
Use the command STRTCP to start the desired protocol if it is not running.
Verify the necessary daemons are running by browsing the information returned from the NETSTAT *CNN command:
Remote Remote Local
Address Port Port Idle Time State
* * as-cent > 000:09:31 Listen
* * as-signon 000:09:41 Listen
* * as-svrmap 002:57:45 Listen
* * as-data > 002:57:45 Listen
Use the command STRHOSTSVR SERVER(*ALL) to start them if necessary.
- Verify QZDASRVSD, the ODBC socket daemon, is running in the QSERVER subsystem.
- as-database should be in theListenState
- WRKJOB QZDASRVSD should be used to check the job log of the daemon for any error messages.
- Verify that socket daemon QZSOSMAPD is running in QSYSWRK subsystem.
- as-svrmap should be in theListenStateas shown by NETSTAT *CNN.
- WRKJOB QZSOSMAPD should be used to check the job log of the daemon for any error messages.
The PC locates the socket used by the database server by connecting to the server mapper socket. It retrieves the socket used by as-database. It then connects to the proper socket which is being monitored by the database server daemon, QZDASRVSD. The server daemon will attach the client’s connection to a QZDASOINIT prestart job in QUSRWRK. If this is the first connection made to the server from this PC, then two other servers are used: Central server for licensing and signon server for userid/password validation.
For more information about verifying that TCP/IP is started, see General TCP/IP problems.
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=%2Frzaii%2Frzaiiodbc25.htm
