• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 10042
  • Last Modified:

CWBC01049 The iseries server application is not started.

I have a client the is using ODBC to import/export shipping information from the UPS Worldship.  This has work for them for years, until recently we had to replace their AS400.  They went from a 170 V4R5 to another 170 V5R1.  Only the user libraries were restored to the replacement everything else like the profiles and devices had to be manually configured.

So after everything was set back up on the replacement we tested the import/export on the UPS and it still work with no problem, except every once in awhile the export (UPS --> AS400) pops up the error "CWBC01049 The iseries server application is not started." and that shipment information does not reach the AS400.

There is no specific day or time when this happens.  Sometimes it will not happen for a week or two and sometimes it will happen a few times a day a few times a week.

Has anyone ever had this problem or ell me where to begin to look.  I've tried looking through jobs logs but can not seem to find what is causing the connection issue.

Thank You
1 Solution
Gary PattersonVP Technology / Senior Consultant Commented:
This usually just happens when one or more of the Client Access service jobs that run on the AS/400 aren't started.  Usual cure is to start the missing services using STRHOSTSVR command.  A lot of shops just include the STRHOSTSVR *ALL command int heir system startup program.  

Maybe the old startup program didn't get migrated to the new system, or the QSTRUPPGM system value didn't get pointed to the correct startup program.

Maybe some process runs at night that needs the host servers without restarting them, or maybe you have a bug (did you apply the most recent cume PTF for V5R1 when swapping systems?) that is causing the server jobs to crash?

Open System i Navigator (iseries navigator, navigator, whatever it is called in your version, and navigate to your system.  Select Network - Servers - System i Access (varies by version), and look at the status of the various Client Access server jobs.  Odds are a critical one is Not Started.  In your case, it will probably be Database, Sign On, or Server Mapper.

Start the necessary services.  If something is shutting them down, you can probably find an indication on the system history log, the QSYSOPR message queue, or in the job log from one of the completed server jobs (ODBC server jobs are named QZDASOINIT).

WRKJOB QZDASOINIT to view a list of started database server jobs, plus jobs that ended but left a job log.


- Gary Patterson
DCS12Author Commented:
Sorry for not getting back so soon.  
I had already checked the things you had mentioned and there was nothing when looking at the jobs.  I think maybe the problem was on the UPS PC side and I think (hope) I have fixed it by re-creating everything from scratch.  

I deleted the Maps in UPS software, the ODBC data source on the PC, the SQL package on the AS/400 and the journal over the export file.  After re-creating everything they have had no problems since.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now