Re: AS/400 Support for Windows Network Neighborhood (AS/400 NetServer) was unable to start. -- MIDRANGE-L

 APAR        Status       Abstract

  MA24264 CLOSED PER OSP-MSGCPIB683-RC3409 NETSERVER FAILS TO START WITH
CPIB683 RC6
RC3409.
  MA22413 CLOSED PER OSP-MSGCPIB683-RC3409 NETSERVER WILL NOT START

  SA91678 CLOSED PER OSP - INTERNAL EXTENSIONS FOR MAINTAINABILITY

  MA17778 CLOSED PER OSP-INCORROUT NETSERVER DOES NOT START W/ MULTIPLE
INTERFACE

  MA17738 CLOSED PER OSP-INCORROUT NETSERVER DOES NOT START W/ MULTIPLE
INTERFACE

  SA71556 CLOSED PER OSP-INCORROUT NETSERVER DOES NOT HANDLE MULTIHOMED
SYSTEMS
  II11081 CLOSED CAN V4R2 PTF INFO FOR AS/400 SUPPORT FOR WINDOWS NETWRK
NEIGHBORHOOD
(AS/400 NETSERVER)
  II11239 CLOSED CAN AS/400 SUPPORT FOR WINDOWS NETWRK NEIGHBORHOOD (AS/400
NETSERVER
) TIPS AND TECHNIQUES

----- Original Message -----
From: "Connie Webster" <ConnieW@jupiter.fl.us>
To: <midrange-l@midrange.com>
Sent: Wednesday, February 13, 2002 8:43 AM
Subject: AS/400 Support for Windows Network Neighborhood (AS/400 NetServer)
was unable to start.


> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> --
> [ Picked text/plain from multipart/alternative ]
> We are having problems getting AS/400 NetServer to start.  We have just
now
> started experiencing this problem about two weeks ago.  We upgraded to the
> 820 model in December 2001 but this problem started a couple of weeks ago,
> OS v5r1.  We have tried the RESET and START in OpsNav and we have Ended
> TCP/IP and started it again and AS/400 NetServer still does not start.
Any
> Suggestions?
>
> Problem:
> AS/400 Support for Windows Network Neighborhood (AS/400 NetServer) was
> unable to start.
>                          Additional Message Information
>
>
>
>  Message ID . . . . . . :   CPIB683       Severity . . . . . . . :   40
>
>  Message type . . . . . :   Information
>
>  Date sent  . . . . . . :   02/13/02      Time sent  . . . . . . :
> 07:54:58
>
>
>  Message . . . . :   AS/400 Support for Windows Network Neighborhood
(AS/400
>
>    NetServer) was unable to start.
>
>  Cause . . . . . :   The required AS/400 NetServer job QZLSSERVER was
unable
> to
>    start because of reason code 5.  See the following reason codes and
their
>
>    meanings:
>
>      1 - Unable to retrieve user credentials.
>
>      2 - Unable to retrieve credentials.
>
>      3 - Exchange user profile failed.
>
>      4 - Unable to obtain lock for service program QZLSSRV1 in library
QSYS.
>
>      5 - Start of the NetBIOS over TCP/IP failed with return code 3420.
>
>      6 - Start of the internal server failed with return code 3420. Note:
>
>    Return code 16 indicates that there is another computer on the network
>
>
>
>   already using the same name as the AS/400 NetServer server name.
>
>     7 - Error occurred when sharing resources with the network.
>
>     8 - Unable to retrieve maximum incorrect sign-on attempts system
value.
>
>     9 - Unable to retrieve code page information.
>
>     10 - Unable to retrieve host IP address because of return code 3420.
>
>     11 - AS/400 NetServer requires the services of TCP/IP, which is not
>
>   started.
>
> Recovery  . . . :   Complete recovery for the specified reason code.
>
>     1 - Contact your service provider.
>
>     2 - Contact your service provider.
>
>     3 - Contact your service provider.
>
>     4 - Use the Work with Object Locks (WRKOBJLCK) command to find the
owner
>
>   of the lock and take steps to remove the lock.
>
>    5 - Start AS/400 NetServer with the reset option using the Start Server
>
>  (QZLSSTRS) API.  If the problem continues, restart TCP/IP with the End
>
>  TCP/IP (ENDTCP) and Start TCP/IP (STRTCP) commands.  Note:  This may
affect
>
>  other users.  When TCP/IP is active, start AS/400 NetServer with the
reset
>
>  option using the Start Server (QZLSSTRS) API. If the problem continues,
>
>  contact your service provider.
>
>    6 - If the return code is 16, verify that the AS/400 NetServer server
> name
>  is unique on the network.  For all other return codes, restart the
QSERVER
>
>  subsystem with the End Subsystem (ENDSBS) and Start Subsystem (STRSBS)
>
>  commands. Note:  This may affect other users. After the QSERVER subsystem
> is
>  started, start the AS/400 NetServer using either the Start Server
> (QZLSSTRS)
>  API or the Start TCP/IP Server (STRTCPSVR *NETSVR) command. If the
problem
>
>  continues, contact your service provider.
>
>    7 - Use the Display Message (DSPMSG) command to see messages in the
>  QSYSOPR message queue related to resource sharing failures.
>    8 - Contact your service provider.
>    9 - Contact your service provider.
>    10 - Contact your service provider.
>    11 - Use the Start TCP/IP (STRTCP) command to start TCP/IP services.
>
> More...
>
> Connie Webster
> IBM Certified Specialist, AS/400 RPG IV Programmer
> Senior Programmer
> Town of Jupiter
>  <mailto:conniew@jupiter.fl.us> conniew@jupiter.fl.us
> FAX:  561-741-0904
> Phone:  561-746-5134
>
>
>
> Please visit the Town of Jupiter online at http://www.jupiter.fl.us
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>