ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahl_5.4.0.1/rzahlqzlsfile.htm

105 lines
8.1 KiB
HTML

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow"/>
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="keywords" content="troubleshooting, administering, iSeries NetServer,
user profile connection problems, Troubleshooting, QZLSFILE, jobs, QZLSFILET" />
<title>Troubleshoot iSeries NetServer user profile connections</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<a name="qzlsfile"></a>
<h2 id="qzlsfile">Troubleshoot iSeries NetServer user profile connections</h2><a id="idx26" name="idx26"></a><a id="idx27" name="idx27"></a><a id="idx28" name="idx28"></a><a id="idx29" name="idx29"></a><a id="idx30" name="idx30"></a>
<p>When you are trying to access a file share, an error code may appear for
any of the following reasons:</p>
<p><span class="bold">Lack of authorization</span></p>
<p>User profiles may not be authorized to a particular shared directory. If
this occurs, ensure that the user can access the directory by using i5/OS
control language (CL) commands, such as Work with Object Links (WRKLNK).</p>
<p><span class="bold">Attempting to connect with incorrect password</span></p>
<p>Users may be unable to use iSeries NetServer&trade; if they attempt to connect to iSeries with
an incorrect password too many times. If this occurs, then iSeries sends a message
(CPIB682) to the <tt class="xph">QSYSOPR</tt> message queue. This message indicates
that the user profile has been disabled for iSeries NetServer access. This does not disable
the user profile for iSeries or iSeries Access for Windows, but it does stop the user profile from
accessing iSeries NetServer.</p>
<a name="wq119"></a>
<div class="notetitle" id="wq119">Note:</div>
<div class="notebody">In V5R1, Management Central has a function
to monitor messages from QSYSOPR. An administrator could use this function
to be alerted to profiles being disabled for iSeries NetServer use. Also in V5R1, the
administrator could use iSeries Navigator to periodically look at a list of disabled
users and re-enable users from the panel. To find all disabled user profiles,
right-click <span class="bold">iSeries NetServer</span> and select <span class="bold">Disabled Profiles</span>.</div>
<p><span class="bold">QZLSFILE and QZLSFILET jobs are not configured for a subsystem</span></p>
<p><img src="delta.gif" alt="Start of change" />Clients should connect to iSeries NetServer by using their valid user profiles
and not the guest user profile. The <tt class="xph">QZLSFILET</tt> or <tt class="xph">QZLSFILE</tt> job might be in the <tt class="xph">QSERVER</tt> subsystem for each active client
[user] that connects to an iSeries NetServer [file share]. However, QZLSFILET and QZLSFILE
jobs can run in another subsystem if the user has configured other subsystems
to run iSeries NetServer jobs. Message CPIAD12 in the job log indicates which user/client
the QZLSFILE job is servicing (a QZLSFILET job may have numerous messages
in the job log because it services mulitple clients). From iSeries Navigator under <span class="bold">Network </span>> <span class="bold">Servers </span>> <span class="bold">TCP/IP</span>, double-click <span class="bold">iSeries NetServer</span> and
then click <span class="bold">Sessions</span>. A listing of users and
their respective workstation name, logon type, and server session is displayed.<img src="deltaend.gif" alt="End of change" /></p>
<p><img src="delta.gif" alt="Start of change" /><span class="bold">Trying to access a non threadsafe file system
while running threaded</span><img src="deltaend.gif" alt="End of change" /></p>
<p><img src="delta.gif" alt="Start of change" />A client that is running threaded will receive "access denied"
type errors when trying to access a non threadsafe file system (such as QDLS
or QNetWare). The client will also receive errors when attempting to map
a drive to a non threadsafe file system when the client session is running
threaded. For a listing of file systems that are not threadsafe, see <a href="../rzahw/rzahwfscco.htm">File system considerations for multithreaded programming</a> in the Multithreaded
applications topic.<img src="deltaend.gif" alt="End of change" /></p>
<p><img src="delta.gif" alt="Start of change" />As of V5R4, iSeries NetServer by default services file shares
in a multi-threaded job. The threaded activity for all sessions in a subsystem
runs in the pool of threads in the QZLSFILET job for that subsystem. Non
threaded client activity is still run in QZLSFILE jobs.<img src="deltaend.gif" alt="End of change" /></p>
<p><img src="delta.gif" alt="Start of change" />A QZLSFILE job in the correct subsystem is still required to
launch a threaded session. Whether a client can run threaded is determined
when it first maps a drive to the integrated file system (IFS). The first
phase of mapping the first drive for a client runs in a QZLSFILE job. If the
session can run threaded, the session is transferred into the single QZLSFILET
job in the subsystem. If the file system is not threadsafe, or the ADDEXITPGM
THDSAFE() option for the QIBM_QPWFS_FILE_SERV exit point is specified as *UNKNOWN
or *NO, or QZLSFILET is not present in the subsystem, the client runs in
a QZLSFILE job for this session. The QZLSFILE job log records when a client
starts. When a client ends the session, the QZLSFILE job returns to prestart
wait status and its job log is cleared. When a client starts a session with
a QZLSFILET job, message CPIAD12 is written into its job log. Since the QZLSFILET
job is used by multiple client sessions, the session end message, CPIAD13,
is written to its job log when a user/client session is ended. These messages
will accumulate in the job log.<img src="deltaend.gif" alt="End of change" /></p>
<p><img src="delta.gif" alt="Start of change" />To prevent "access denied" type errors, the recommended solution
is to not have the QZLSFILET job started in the QSERVER subsystem (or other
user subsystems) . This may involve configuring user subsystems in iSeries
Navigator so that some clients run threaded and others non-threaded. Use
the following command to remove the prestart job entry for QZLSFILET from
the QSERVER subsystem. </p>
<pre class="xmp">RMVPJE SBSD(QSYS/QSERVER) PGM(QSYS/QZLSFILET)</pre><p class="indatacontent">If a prestart job entry is to be removed from a different subsystem,
then that subsystem would need to be specified instead of QSERVER along with
its correct library (the program would remain the same).<img src="deltaend.gif" alt="End of change" /></p>
<p>For more information on subsystem configuration, see <a href="rzahlsbsysjbs.htm#sbsysjbs">Specify subsystems for iSeries NetServer</a>.</p>
<p><span class="bold">Active print users</span></p>
<p>Active print users will have a job in QUSRWRK that connects to iSeries NetServer.
A message in the job log indicates to which user the <tt class="xph">QNPSERVS</tt> job
belongs.</p>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>