FTP from NetWare for SAA server to AS/400 failed
(Last modified: 18Jan2002)
This document (10064338) is provided subject to the disclaimer at the end of this document.
goal
FTP from NetWare for SAA server to AS/400 failed
fact
NetWare for SAA
Formerly document SAA3194
symptom
When a customer is running FTP, the "PWS0008" error message is issued on the AS/400. This message states that the AS/400 database server cannot run because the fetch is only supported through the QSERVER subsystem.
fix
The customer has applied all NetWare and NetWare for SAA maintenance and gets "PWS0008" or "CWBDB0053" errors when running FTP.
Run a global trace, and format it.
Search on QSERVER.
If QSERVER is found in the trace, then NetWare for SAA is working correctly and the appropriate maintenance is applied.
If QSERVER is not in the trace, then recheck the server side and client side maintenance.
If one of the above messages appears when NWSAA is sending QSERVER, then it is a mode description problem at the AS/400.
Note: QCMN must be a subsystem, and QSERVER must be a "defined" subsystem.
The customer can also check to make sure QZDASOINIT and QPWFSERVSO are up by performing a WRKSBS at an AS/400 command line:
Find QSERVER - (use option 8 - work with subsystem jobs) to make sure the above two PJ's (prestart jobs) are running.
If PJ's are not running, enter STRHOSTSVR at the AS/400 command line.
If PJ's are still not up, call the AS/400 Client Access Support to edit the prestart job entries.
document
Document Title: | FTP from NetWare for SAA server to AS/400 failed |
Document ID: | 10064338 |
Solution ID: | NOVL56306 |
Creation Date: | 20Aug2001 |
Modified Date: | 18Jan2002 |
Novell Product Class: | Connectivity Products |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.