home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
nsc12.zip
/
nschelp.HLP
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1996-07-18
|
65KB
|
2,211 lines
ΓòÉΓòÉΓòÉ 1. Network SignON Coordinator/2 ΓòÉΓòÉΓòÉ
Network SignON Coordinator/2 allows you to signon, change passwords, and
signoff at the locations you have specified in your NSC configuration file.
The icons displayed in this window indicate the status of each location where
you can sign on (icons are not displayed for locations where signon is not
allowed).
If you are currently signed on to a location, the icon is displayed with a
shaded workstation screen and a connection indicator if the location is not
Local, and the User ID signed on is displayed (in this case, if the User ID is
displayed as "<Unknown>", this indicates NSC is not certain of the signed on
User ID). If you are signed on to a host emulation session, the session id is
displayed after the host name. Double clicking on the icon will sign you off.
If you are not currently signed on to a location, the icon is displayed with a
clear workstation screen and no connection indicator, and no User ID is
displayed (in this case, if the User ID is displayed as "<Unknown>", this
indicates NSC is not certain of the signon state). Double clicking on the icon
will sign you on using the User ID for the first definition for this location.
Clicking the right mouse button on an icon will cause a menu of available
actions to be displayed for the location. If the signon action is selected and
there are multiple User IDs defined for the location, a list of available User
IDs is displayed. Clicking the right mouse button in the client area but not on
an icon will cause a menu of available actions to be displayed for all
locations.
As actions are performed, messages are written to the list box in the Messages
window. The window may be scrolled back to review messages. New messages will
always cause the list box to be scrolled to the end so the new message will be
visible. Help for error messages is provided by selecting the message in the
list box.
You can perform the following functions via the Actions pull-down:
Signon to the locations for which you specified the ON option in your
configuration.
Signon to the currently selected (cursored) location.
Change passwords at all configured locations.
Signoff of all locations where you are currently signed on.
Signoff of the currently selected (cursored) location.
For a detailed explanation of each menu option, select from the list below:
Actions
Options
Help
ΓòÉΓòÉΓòÉ 1.1. Actions ΓòÉΓòÉΓòÉ
Use Actions to perform the following functions:
Signon to the locations for which you specified the ON option in your
configuration.
Signon to the currently selected (cursored) location.
Change passwords at all configured locations.
Signoff of all locations where you are currently signed on.
Signoff of the currently selected (cursored) location.
Exit NSC.
For a detailed explanation of each action, select from the list below:
Signon
Change Password
Signoff
Exit
ΓòÉΓòÉΓòÉ 1.1.1. Signon ΓòÉΓòÉΓòÉ
Use Signon to perform the following functions:
Signon to the locations for which you specified the ON option in your
configuration.
Signon to the currently selected (cursored) location.
For a detailed explanation of each action, select from the list below:
Default Systems
Selected System
ΓòÉΓòÉΓòÉ 1.1.2. Default Systems ΓòÉΓòÉΓòÉ
Use Default Systems to initiate a signon at each of the locations you have
configured with the ON option. If you have not yet entered your password, or
did not configure SavePW=On, the Signon dialog will be displayed, allowing you
to enter your password.
ΓòÉΓòÉΓòÉ 1.1.3. Selected System ΓòÉΓòÉΓòÉ
Use Selected System to initiate a Signon for the currently selected (cursored)
location. If only one User ID is defined for the location, that User ID will be
signed on. If multiple User IDs are defined for the location, a list of
available User IDs is displayed, allowing you to select which User ID you wish
to signon. In either case, if you have not yet entered your password, or did
not configure SavePW=On, the Signon dialog will be displayed, allowing you to
enter your password.
ΓòÉΓòÉΓòÉ 1.1.4. Change Password ΓòÉΓòÉΓòÉ
Use Change Password to change your password at all of the locations you have
configured.
If you are already signed on at a location, you will remain signed on. If you
are not already signed on at a location, Network SignON Coordinator/2 may have
to sign you on, change your password, and sign you back off.
ΓòÉΓòÉΓòÉ 1.1.5. Signoff ΓòÉΓòÉΓòÉ
Use Signoff to perform the following functions:
Signoff of all locations where you are currently signed on.
Signoff of the currently selected (cursored) location.
For a detailed explanation of each action, select from the list below:
All Systems
Selected System
ΓòÉΓòÉΓòÉ 1.1.6. All Systems ΓòÉΓòÉΓòÉ
Use All Systems to initiate a Signoff from each of the configured locations
where you are currently signed on.
ΓòÉΓòÉΓòÉ 1.1.7. Selected System ΓòÉΓòÉΓòÉ
Use Selected System to initiate a Signoff from the currently selected
(cursored) location.
ΓòÉΓòÉΓòÉ 1.1.8. Exit ΓòÉΓòÉΓòÉ
Use Exit to Exit Network SignON Coordinator/2.
Press F3 to bypass selecting this action and immediately Exit Network SignON
Coordinator/2.
ΓòÉΓòÉΓòÉ 1.2. Options ΓòÉΓòÉΓòÉ
Use Options to display or hide the Messages window.
For a detailed explanation of each action, select from the list below:
Show/Hide Messages
ΓòÉΓòÉΓòÉ 1.2.1. Show/Hide Messages ΓòÉΓòÉΓòÉ
Use Show Messages to display the Messages window. Use Hide Messages to hide the
Messages window. If the Messages window is currently closed or minimized, the
"Show Messages" option will be displayed; selecting this option will cause the
Messages window to be opened. If the Messages window is currently open, the
"Hide Messages" option will be displayed; selecting this option will cause the
Messages window to be minimized.
ΓòÉΓòÉΓòÉ 1.3. Help ΓòÉΓòÉΓòÉ
Select Help and use the choices in the Help menu to display:
General information about the help facility
General information about Network SignON Coordinator/2
A list and description of keys you can use
Reference information about Network SignON Coordinator/2
Product information about Network SignON Coordinator/2
For more information on the help information available, select from the list
below:
Using help
General help
Keys help
Reference information
Product information
ΓòÉΓòÉΓòÉ 1.3.1. Using the help facility ΓòÉΓòÉΓòÉ
Use Using help to find out how to use the help facility.
ΓòÉΓòÉΓòÉ 1.3.2. General help ΓòÉΓòÉΓòÉ
Use General help to display information about the contents of the Network
SignON Coordinator/2 window.
ΓòÉΓòÉΓòÉ 1.3.3. Keys help ΓòÉΓòÉΓòÉ
Use Keys help to display a description about each key you can use in Network
SignON Coordinator/2.
ΓòÉΓòÉΓòÉ 1.3.4. Reference information ΓòÉΓòÉΓòÉ
Use Reference information to view the online documentation for Network SignON
Coordinator/2.
ΓòÉΓòÉΓòÉ 1.3.5. Product information ΓòÉΓòÉΓòÉ
Use Product information to view the product name, part number and copyright
information for Network SignON Coordinator/2.
ΓòÉΓòÉΓòÉ <hidden> Key assignments ΓòÉΓòÉΓòÉ
When two key names are joined by a plus sign (+), use these two keys together.
Press and hold the first key, press the second key, and then release them
together.
Key Function
Alt+F4 Exit the active window.
Alt+F5 Return the window to the size it was and the location it was
in before you maximized the window.
Alt+F6 Move the cursor between windows that are associated (for
example, move between the active NSC program window and the
help window for NSC).
Alt+F7 Enables you to move the active window to a different location.
Alt+F8 Enables you to size the active window with the arrow keys.
Alt+F9 Minimize Network SignON Coordinator/2 and all windows
associated to it.
Alt+F10 Enlarge the active window to its largest possible size
(maximize).
Alt+Spacebar Switch to or from the title-bar icon.
Backspace In an entry field, delete one character to the left of the
cursor.
Backtab In a dialog, move to the previous entry field or control.
Ctrl+End (1) Move to the last choice in a menu. (2) In an entry field,
move the cursor to the end of the line.
Ctrl+Home (1) Move to the first choice in a menu. (2) In an entry field,
move the cursor to the start of the line.
Ctrl+Left Arrow (1) Move to the left-most choice in a menu. (2) In an entry
field, move the cursor to the start of the line.
Ctrl+Right Arrow (1) Move to the right-most choice in a menu. (2) In an entry
field, move the cursor to the end of the line.
Ctrl+Tab Move the cursor to the next field (entry field, or first push
button).
Del In an entry field, delete the character to the right of the
cursor.
Down Arrow (1) Move the cursor down, if possible. (2) Move the cursor to
the next field in a group (for example, the Signon group box
or the push buttons).
End (1) Move to the last choice in a menu. (2) In an entry field,
move the cursor to the end of the line.
Enter Perform the default action that applies to the cursor
location. If the cursor is on a menu item or push button, this
selects the item or button. If the cursor in an entry field in
the Signon or Change Password window, this initiates the
signon or change password action. If the cursor is on a
message in the list box, this displays help for the message.
Esc (1) Remove the window without sending any changes (for
example, remove the Signon or Change Password window). (2)
Remove a menu that is displayed below a menu-bar choice, but
keep the menu-bar choice selected.
F1 Display specific help for the selected object or active
window. The help is related to the position of the cursor (for
example, on a menu item or in a data entry field).
F3 From the Network SignON Coordinator/2 window, exit Network
SignON Coordinator/2 if Actions are enabled.
F10 Move the cursor to or from the menu bar.
Home (1) Move to the first choice in a menu. (2) In an entry field,
move the cursor to the start of the line.
Insert In an entry field, switch between insert and replace modes for
typing text.
Left Arrow Move the cursor left, if possible.
Right Arrow Move the cursor right, if possible.
Shift+Esc Switch to or from the title-bar icon.
Shift+Tab Move the cursor to the previous field (entry field, or first
push button).
Tab Move the cursor to the next field (entry field, or first push
button).
Up Arrow (1) Move the cursor up, if possible. (2) Move the cursor to
the previous field in a group (for example, the Signon group
box or the push buttons).
ΓòÉΓòÉΓòÉ 2. User ID ΓòÉΓòÉΓòÉ
Use this window to enter your default User ID. This window will not be
displayed if your default User ID has been specified via either:
a UserId definition in your NSC configuration file, or
entering your User ID as a command line parameter.
If you cancel out of this dialog, no actions will be allowed.
For a detailed explanation of each field, select from the list below:
User ID
ΓòÉΓòÉΓòÉ 2.1. User ID ΓòÉΓòÉΓòÉ
Type the User ID that identifies you to the system. You can type lowercase
characters, but they are stored as uppercase.
ΓòÉΓòÉΓòÉ 3. Signon ΓòÉΓòÉΓòÉ
Use this window to enter your password to initiate a signon for a selected
location, or at each of the locations you have configured with the ON option.
For a detailed explanation of each field, select from the list below:
Current Password
ΓòÉΓòÉΓòÉ 3.1. Current Password ΓòÉΓòÉΓòÉ
Type your current password. The password will not be displayed on the screen.
You can type lowercase characters, but they are stored as uppercase.
ΓòÉΓòÉΓòÉ 4. Change Password ΓòÉΓòÉΓòÉ
Use this window to initiate a password change at all of the locations you have
configured.
For a detailed explanation of each field, select from the list below:
Current Password
New Password
Confirmation Password
ΓòÉΓòÉΓòÉ 4.1. Current Password ΓòÉΓòÉΓòÉ
Type your current password. The password will not be displayed on the screen.
You can type lowercase characters, but they are stored as uppercase.
ΓòÉΓòÉΓòÉ 4.2. New Password ΓòÉΓòÉΓòÉ
Type the new password. The password will not be displayed on the screen.
If the default configuration is used, the password can contain from 1 to 8
characters and contain any of the following characters:
Uppercase or lowercase letters A to Z
Digits 0 to 9
Special characters #, @ and $
You can type lowercase characters, but they are stored as uppercase.
Different systems have different restrictions on the length and valid
characters in a password. The following configuration definitions may be
specified to tailor the valid entries for passwords allowed by Network SignON
Coordinator/2:
MaxPWLen sets the maximum number of characters allowed in the password.
MinPWLen sets the minimum number of characters required in the password.
CharSet specifies the characters allowed in a password (other than
uppercase or lowercase letters A to Z and digits 0 to 9, which are always
allowed).
ΓòÉΓòÉΓòÉ 4.3. Confirmation Password ΓòÉΓòÉΓòÉ
Type the new password again to verify it to the system. The password will not
be displayed on the screen.
ΓòÉΓòÉΓòÉ 5. Signon Location Actions ΓòÉΓòÉΓòÉ
Use this window to signon to the selected location using one of your configured
User IDs for this location. If you are not currently signed on to the location,
all configured User IDs for the location are displayed. If you are signed on,
the currently signed on User ID is not displayed; if you select a different
User ID to signon, you will first be signed off and then signed on using the
selected User ID. If you have not yet entered your password, or did not
configure SavePW=On, the Signon dialog will be displayed, allowing you to enter
your password.
ΓòÉΓòÉΓòÉ 6. Error Message Helps ΓòÉΓòÉΓòÉ
The following topics explain NSC/2 error messages.
ΓòÉΓòÉΓòÉ 6.1. NSC0100 The requested action is complete. ΓòÉΓòÉΓòÉ
Message:
NSC0100 The requested action is complete.
Explanation: The indicated action has completed successfully.
User Response: None.
ΓòÉΓòÉΓòÉ 6.2. NSC0101 The requested action completed, but the password will expire soon. ΓòÉΓòÉΓòÉ
Message:
NSC0101 The requested action completed, but the password will expire soon.
Explanation: The signon has completed successfully. Your password will expire
shortly. For local UPM and IBM LAN Server domain accounts, this warning is
returned when your password will expire within 5 days. For host emulator
sessions, this warning is returned when the host notifies you at signon of this
condition (as determined by the search string in your host information file).
User Response: Change your password.
ΓòÉΓòÉΓòÉ 6.3. NSC0102 The user is already signed on. ΓòÉΓòÉΓòÉ
Message:
NSC0102 The user is already signed on.
Explanation: You attempted to signon to the location indicated in the preceding
in-progress message, and you were already signed on. For host emulator sessions
or NetWare servers, you may be signed on under a different User ID. For IBM LAN
Servers, you may be signed on to the requested domain under a different User
ID, or you may be signed on to a different domain.
User Response: None.
ΓòÉΓòÉΓòÉ 6.4. NSC0103 The user has already signed off. ΓòÉΓòÉΓòÉ
Message:
NSC0103 The user has already signed off.
Explanation: You attempted to signoff from the location indicated in the
preceding in-progress message, and you were not signed on.
User Response: None
ΓòÉΓòÉΓòÉ 6.5. NSC0104 The password change completed successfully, but Signon failed. ΓòÉΓòÉΓòÉ
Message:
NSC0104 The password change completed successfully, but Signon failed.
Explanation: RACF has changed the password, however it was then unable to
complete a signon process.
User Response: If you have any subsequent problem signing on at this location,
contact the security administrator of that location.
ΓòÉΓòÉΓòÉ 6.6. NSC0105 The requested action completed successfully, but the password has expired. ΓòÉΓòÉΓòÉ
Message:
NSC0105 The requested action completed successfully, but the password has expired.
Explanation: The signon has completed successfully, but the password has
expired. This error can be returned for a local logon on a LAN Server with
local security.
User Response: Change your password.
ΓòÉΓòÉΓòÉ 6.7. NSC0106 The requested action is in progress. ΓòÉΓòÉΓòÉ
Message:
NSC0106 The requested action is in progress.
Explanation: NSC has begun processing the indicated action.
User Response: None.
ΓòÉΓòÉΓòÉ 6.8. NSC0107 The password change completed successfully, but could not Signon again. ΓòÉΓòÉΓòÉ
Message:
NSC0107 The password change completed successfully, but could not Signon again.
Explanation: The password was changed and no user is currently signed on.
To make the change, it was necessary to signon the user whose password was
changed. There was a different user signed on before the request was processed
and NSC could not sign the original user back on.
NSC probably had the wrong password for the original user when it tried the
Signon.
User Response: If you need to sign the original user back on, make a Signon
request with the correct password.
ΓòÉΓòÉΓòÉ 6.9. NSC0126 The requested action completed, with warnings. ΓòÉΓòÉΓòÉ
Message:
NSC0126 The requested action completed, with warnings.
Explanation: One or more signon requests have completed with warning
conditions.
User Response: Review messages preceding this one to determine the locations
with warnings and take any further actions needed.
ΓòÉΓòÉΓòÉ 6.10. NSC0127 The requested action completed, with errors. ΓòÉΓòÉΓòÉ
Message:
NSC0127 The requested action completed, with errors.
Explanation: One or more signon requests have failed with error conditions.
User Response: Review messages preceding this one to determine which locations
failed and why.
ΓòÉΓòÉΓòÉ 6.11. NSC0128 Error executing NSCPM.EXE. ΓòÉΓòÉΓòÉ
Message:
NSC0128 Error executing NSCPM.EXE.
Explanation: NSC was unable to successfully execute the PM executable
NSCPM.EXE. This message is displayed if the session for the NSCPM.EXE program
could not be started.
User Response: Make sure the NSCPM.EXE program is in the same directory as the
NSC.EXE program. Reinstall the NSC OS/2 Client if necessary.
ΓòÉΓòÉΓòÉ 6.12. NSC0130 The user ID is not valid. ΓòÉΓòÉΓòÉ
Message:
NSC0130 The user ID is not valid.
Explanation: The security facility at the location indicated in the preceding
in-progress message did not recognize your User ID.
User Response: Resubmit the request with the correct User ID.
ΓòÉΓòÉΓòÉ 6.13. NSC0131 The user ID or password is not valid. ΓòÉΓòÉΓòÉ
Message:
NSC0131 The user ID or password is not valid.
Explanation: The security facility at the location indicated in the preceding
in-progress message failed the request. Possible reasons for the failure could
be:
The security facility did not recognize your User ID.
The current password entered for signon or change password was not valid.
The User ID is not allowed to signon at this time.
User Response: Resubmit the request with the correct User ID and password. It
the failure persists, try the signon using the normal signon facility for the
location to more precisely identify the problem.
ΓòÉΓòÉΓòÉ 6.14. NSC0132 The password is not valid. ΓòÉΓòÉΓòÉ
Message:
NSC0132 The password is not valid.
Explanation: The current password entered for signon or change password was not
valid at the location indicated in the preceding in-progress message.
User Response: Resubmit the request with the correct password. If your
passwords are out of sync, change your password.
ΓòÉΓòÉΓòÉ 6.15. NSC0133 The password has expired. ΓòÉΓòÉΓòÉ
Message:
NSC0133 The password has expired.
Explanation: Your password has expired at the location indicated in the
preceding in-progress message.
User Response: Change your password.
ΓòÉΓòÉΓòÉ 6.16. NSC0134 The password or the new password is not valid. ΓòÉΓòÉΓòÉ
Message:
NSC0134 The password or the new password is not valid.
Explanation: Either the current password entered for change password was not
valid at the location indicated in the preceding in-progress message, or the
location did not accept your new password. If you are certain you entered your
current password correctly, the new password was rejected because it violated
some rule for passwords enforced by the security facility at the location.
User Response: Resubmit the request with the correct current password and a
different new password. If you successfully changed the password to the
offending password at other locations, you will need to change the password at
those locations to the new password. Both of these requests can be submitted
using NSC -- simply ignore the errors from the locations where the operation
was not necessary.
ΓòÉΓòÉΓòÉ 6.17. NSC0135 The password cannot be changed. ΓòÉΓòÉΓòÉ
Message:
NSC0135 The password cannot be changed.
Explanation: The LAN Server will not let you change your password for one of
two reasons:
The LAN Server administrator has specified that you are not allowed to
change your own password.
The LAN Server administrator has specified a minimum password age before
the password may be changed.
User Response: Contact your LAN Server administrator to remove the
restriction, or do not attempt to change your password on the LAN Server at
this time.
ΓòÉΓòÉΓòÉ 6.18. NSC0136 The password change request failed. The new password is not valid. ΓòÉΓòÉΓòÉ
Message:
NSC0136 The password change request failed. The new password is not valid.
Explanation: You attempted to change passwords, and the location indicated in
the preceding in-progress message did not accept your new password. The new
password was rejected because it violated some rule for passwords enforced by
the security facility at the location.
User Response: Resubmit the request with a different new password. If you
successfully changed the password to the offending password at other locations,
you will need to change the password at those locations to the new password.
Both of these requests can be submitted using NSC -- simply ignore the errors
from the locations where the operation was not necessary.
ΓòÉΓòÉΓòÉ 6.19. NSC0137 Error executing LOGON program. ΓòÉΓòÉΓòÉ
Message:
NSC0137 Error executing LOGON program.
Explanation: The installed level of UPM did not support APIs for logon and
logoff, so NSC attempted to execute the LOGON.EXE program. An error occurred
attempting this operation. The most likely causes are:
The appropriate software is not installed.
The appropriate paths for the software were not set up.
User Response: Either install the appropriate software, or do not attempt to
configure a LOCAL option.
ΓòÉΓòÉΓòÉ 6.20. NSC0138 Error executing LOGOFF program. ΓòÉΓòÉΓòÉ
Message:
NSC0138 Error executing LOGOFF program.
Explanation: The installed level of UPM did not support APIs for logon and
logoff, so NSC attempted to execute the LOGOFF.EXE program. An error occurred
attempting this operation. The most likely causes are:
The appropriate software is not installed.
The appropriate paths for the software were not set up.
User Response: Either install the appropriate software, or do not attempt to
configure a LOCAL option.
ΓòÉΓòÉΓòÉ 6.21. NSC0140 IBM NETWKSTA.200 is not started. ΓòÉΓòÉΓòÉ
Message:
NSC0140 IBM NETWKSTA.200 is not started.
Explanation: The NETWKSTA.SYS device driver was not started. The most likely
cause is that the appropriate software support for NETBIOS has not been
installed.
User Response: Install the appropriate software or remove the configuration
option from your configuration file.
ΓòÉΓòÉΓòÉ 6.22. NSC0141 The IBM Requester is not started. ΓòÉΓòÉΓòÉ
Message:
NSC0141 The IBM Requester is not started.
Explanation: The IBM LAN Requester is not started (or possibly not installed).
The request was not queued because the NSC Retry Process was not started. If
you were attempting to change passwords, your password will be out of sync on
the LAN Server. If you were attempting to signon, you will not be signed on to
the LAN Server.
User Response: Start the LAN Requester and resubmit the request.
If you start the NSC Retry Process at startup, failures such as this can be
queued and automatically retried when the LAN Requester has started.
ΓòÉΓòÉΓòÉ 6.23. NSC0142 The IBM Requester is not started. The operation has been queued. ΓòÉΓòÉΓòÉ
Message:
NSC0142 The IBM Requester is not started. The operation has been queued.
Explanation: The LAN Requester is not started. The request was queued to be
retried. The operation will be retried by the NSC Retry Process. If the LAN
Requester is not started and you were attempting to change passwords, your
password will be out of sync at the location indicated in the preceding
in-progress message. If you were attempting to signon, you will not be signed
on to the location.
User Response: Start the LAN Requester. Once the LAN Requester has been
started, check the NSC Retry Process to verify that the operation was
successfully retried. If the retry was not successful, resubmit the request.
ΓòÉΓòÉΓòÉ 6.24. NSC0143 Cannot change password on additional server. ΓòÉΓòÉΓòÉ
Message:
NSC0143 Cannot change password on additional server.
Explanation: You attempted to change your password locally on a workstation
installed as an additional server for an IBM LAN Server. The UPM account
database for an additional server is replicated from the LAN Server domain
controller, and passwords can only be modified by changing the password on the
LAN Server domain controller.
User Response: If you configured a LANSERVER or DOMAIN option for the LAN
Server domain controller that controls your additional server, you can ignore
this error, since the password change to the domain controller is replicated to
the additional server. Otherwise, your password on the LAN Server domain
controller may be out of sync. Use a LANSERVER option for the LAN Server domain
controller instead of a LOCAL option for the additional server.
ΓòÉΓòÉΓòÉ 6.25. NSC0144 Unable to execute IBM NET program. ΓòÉΓòÉΓòÉ
Message:
NSC0144 Unable to execute IBM NET program.
Explanation: NSC either attempted to call a LAN Requester function in OS/2 or
attempted to execute its NSCNET.EXE program in order to execute a NET LOGON or
NET LOGOFF command for DOS. An error occurred attempting this operation. The
most likely causes are:
The appropriate software is not installed.
The appropriate paths for the software were not set up.
User Response: Either install the appropriate software, or do not attempt to
configure a LANSERVER or DOMAIN option.
ΓòÉΓòÉΓòÉ 6.26. NSC0145 LAN Server logon has active sessions. ΓòÉΓòÉΓòÉ
Message:
NSC0145 LAN Server logon has active sessions.
Explanation: A LAN Server logoff failed because some session has a redirected
drive as the current drive. The request was not queued because the NSC Retry
Process was not started. You are not logged off of the domain.
User Response: Determine which session is using the redirected drive and change
the current drive for the session. Resubmit the request.
If you start the NSC Retry Process at startup, failures such as this can be
queued and automatically retried later.
ΓòÉΓòÉΓòÉ 6.27. NSC0146 LAN Server logon has active sessions. The operation has been queued. ΓòÉΓòÉΓòÉ
Message:
NSC0146 LAN Server logon has active sessions. The operation has been queued.
Explanation: A LAN Server logoff failed because some session has a redirected
drive as the current drive. NSC has queued your request to be retried. The
logoff will be retried by the NSC Retry Process. If the use of the redirected
drive by other sessions is not resolved, you will remain logged on to the LAN
Server.
User Response: Determine which session is using the redirected drive and change
the current drive for the session.
Once the redirected drive is no longer in use, check the NSC Retry Process to
verify that the operation was successfully retried. If the retry was not
successful, resubmit the request.
ΓòÉΓòÉΓòÉ 6.28. NSC0147 <Userid> is already signed on at another workstation. ΓòÉΓòÉΓòÉ
Message:
NSC0147 <Userid> is already signed on at another workstation
Explanation: For IBM LAN Servers, you have specified 'multilogon = no' in the
IBMLAN.INI file in the C:\IBMLAN directory, and <userid> is already signed on
to this IBM LAN Server on another client workstation. For host emulator
sessions, <userid> is already signed on to the host from another emulator
session (possibly from another workstation).
User Response: For IBM LAN Servers, signoff the LAN Server from the other
client workstation, or specify 'multilogon = yes' in the IBMLAN.INI file in the
C:\IBMLAN directory and restart the LAN Requester services. For host emulator
sessions, signoff the host from the other emulator session.
ΓòÉΓòÉΓòÉ 6.29. NSC0148 No mailslots are configured for DOS LAN Services. ΓòÉΓòÉΓòÉ
Message:
NSC0148 No mailslots are configured for DOS LAN Services.
Explanation: No mail slots have been configured for the DOS LAN Requester in
the DOSLAN.INI file where DOS LAN Requester is installed. NSC requires at least
one mail slot for the DOS LAN Requester functions it uses.
User Response: Edit the DOSLAN.INI file in the directory where DOS LAN
Requester is installed and configure at least one mail slot. For example,
adding "/NMS:1" at the end of the configuration will configure one mail slot.
Restart the DOS LAN Requester before attempting to use NSC.
ΓòÉΓòÉΓòÉ 6.30. NSC0150 NETBIOS is not installed. ΓòÉΓòÉΓòÉ
Message:
NSC0150 NETBIOS is not installed.
Explanation: NSC could not connect to an NSC Server because NETBIOS is not
installed. NETBIOS is included as part of PCLP or DOS Lan Requester for DOS, or
as part of OS/2 LAN Requester, OS/2 LAN Server, or OS/2 Communications Manager
in EE or ES for OS/2.
User Response: Install the appropriate software and restart the machine before
attempting to connect to an NSC Server.
ΓòÉΓòÉΓòÉ 6.31. NSC0151 NETBIOS Connection error (see LOG file). ΓòÉΓòÉΓòÉ
Message:
NSC0151 NETBIOS Connection error (see LOG file).
Explanation: NSC could not connect to an NSC Server to perform the indicated
action. If the action is Initialization, an error may have occurred accessing a
configuration file or host information file on the NSC Server. The connection
request was not queued because the NSC Retry Process was not started. If you
were attempting to change passwords, your password will be out of sync on hosts
accessed from the NSC Server and local accounts on the NSC Server. If you were
attempting to signon, your signon password was not verified at the APPC host
connected to the NSC Server.
User Response: Examine the NETBIOS messages in the LOG files on the NSC Client
and NSC Server and follow the directions indicated in the User Response for the
message to resolve the NETBIOS problem. If you were attempting to change
passwords, resubmit the password change.
If you start the NSC Retry Process at startup, failures other than
Initialization can be queued and automatically retried when the LAN Server or
host becomes available.
ΓòÉΓòÉΓòÉ 6.32. NSC0152 NETBIOS Connection error (see LOG file). The operation has been queued.s queued. ΓòÉΓòÉΓòÉ
Message:
NSC0152 NETBIOS Connection error (see LOG file). The operation has been queued.
Explanation: NSC could not connect to an NSC Server to perform the indicated
action. NSC has queued the connection request to be retried. The connection
will be retried by the NSC Retry Process. The operation will be retried once
the connection retry is successful. If the NETBIOS connection problem is not
resolved and you were attempting to change passwords, your password will be out
of sync on hosts accessed from the NSC Server and local accounts on the NSC
Server. If you were attempting to signon, your signon password was not
verified at the APPC host connected to the NSC Server.
User Response: Examine the NETBIOS messages in the LOG file and follow the
directions indicated in the User Response for the message to resolve the
NETBIOS problem. If you were attempting to change passwords, once the NETBIOS
connection is established, check the NSC Retry Process to verify that the
connection was successfully retried. If the retry was not successful, resubmit
the password change.
ΓòÉΓòÉΓòÉ 6.33. NSC0153 <Host> is not available. ΓòÉΓòÉΓòÉ
Message:
NSC0153 <Host> is not available.
Explanation: The configured location <location> did not respond to the
preceding NSC request. The computer location is probably down (i.e., powered
off, software not started, etc.), too busy to respond, or the location name is
incorrectly specified in the NSC configuration file.
The request was not queued because the NSC Retry Process was not started. If
you were attempting to change passwords, your password was not changed at the
location and will be out of sync with your other locations. If you were
attempting to signon, you will not be signed on to the location.
User Response: Verify the location name <location> is correct. Check the
following based on the type of location:
LANSERVER or NSC Server, machine is powered on and software started.
HOST, host computer is available.
LOCAL or NODE, the local UPM was probably busy... retry the request.
Resolve the problem and resubmit the request. If the location is an NSC
Server, the log file on the NSC Server may help in determining the problem.
If you start the NSC Retry Process at startup, failures other than
Initialization can be queued and automatically retried when the location
becomes available.
ΓòÉΓòÉΓòÉ 6.34. NSC0154 <Host> is not available. The operation has been queued. ΓòÉΓòÉΓòÉ
Message:
NSC0154 <Host> is not available. The operation has been queued.
Explanation: The configured location <location> did not respond to the
preceding NSC request. The computer location is probably down (i.e., powered
off, software not started, etc.), too busy to respond, or the location name is
incorrectly specified in the NSC configuration file.
The request was queued to be retried. The operation will be retried by the NSC
Retry Process. If you were attempting to change passwords, your password was
not changed at the location and will be out of sync with your other locations.
If you were attempting to signon, you will not be signed on to the location.
User Response: Verify the location name <location> is correct. Check the
following based on the type of location:
LANSERVER or NSC Server, machine is powered on and software started.
HOST, host computer is available.
LOCAL or NODE, the local UPM was probably busy... retry the request.
If the location is an NSC Server, the log file on the NSC Server may help in
determining the problem.
Resolve the problem before the NSC Retry Process reaches its retry limit. Once
the problem has been resolved, check the NSC Retry Process to verify that the
operation was successfully retried. If the retry was not successful, resubmit
the request.
ΓòÉΓòÉΓòÉ 6.35. NSC0160 Communications Manager is not started. ΓòÉΓòÉΓòÉ
Message:
NSC0160 Communications Manager is not started.
Explanation: Communications Manager has not been started or had not completed
its startup when your request was processed. The request was not queued because
the NSC Retry Process was not started. If you were attempting to change
passwords, your password will be out of sync on the host. If you were
attempting to signon, you will not be signed on to the host.
User Response: Start Communications Manager and retry your request.
If you start the NSC Retry Process at startup, failures such as this can be
queued and automatically retried when the LAN Server or host becomes available.
ΓòÉΓòÉΓòÉ 6.36. NSC0161 Communications Manager is not started. The operation has been queued. ΓòÉΓòÉΓòÉ
Message:
NSC0161 Communications Manager is not started. The operation has been queued.
Explanation: Communications Manager has not been started or had not completed
its startup when your request was processed. NSC has queued your request to be
retried. The operation will be retried by the NSC Retry Process. If the problem
with the host is not resolved, and you were attempting to change passwords,
your password will be out of sync on the host; if you were attempting to
signon, you will not be signed on to the host.
User Response: Start Communications Manager.
Once Communications Manager has started, check the NSC Retry Process to verify
that the operation was successfully retried. If the retry was not successful,
resubmit the request.
ΓòÉΓòÉΓòÉ 6.37. NSC0162 APPC is not installed. ΓòÉΓòÉΓòÉ
Message:
NSC0162 APPC is not installed.
Explanation: APPC has not been installed with Communications Manager.
User Response: Contact the person who installed Communications Manager and have
them assist you in determining whether or not APPC was installed with
Communications Manager.
ΓòÉΓòÉΓòÉ 6.38. NSC0163 APPC is not available. ΓòÉΓòÉΓòÉ
Message:
NSC0163 APPC is not available.
Explanation: APPC has not been installed or configured with Communications
Manager.
User Response: Contact the person who installed Communications Manager and have
them assist you in determining whether or not APPC was installed with
Communications Manager.
ΓòÉΓòÉΓòÉ 6.39. NSC0164 APPC allocate error. ΓòÉΓòÉΓòÉ
Message:
NSC0164 APPC allocate error.
Explanation: APPC has indicated an allocation error that should not be retried.
User Response: The most likely cause for this error is a mismatch in your APPC
definitions and those made at the Host computer. You should:
Contact the person who has installed and configured NSC for assistance.
Review the Communications Manager Message file for any additional
information.
See the Network SignON Coordinator/2 User's Guide and make sure the DEBUG
option is enabled as it may produce additional information to help pin
point the problem.
ΓòÉΓòÉΓòÉ 6.40. NSC0165 APPC Partner LU is not defined. ΓòÉΓòÉΓòÉ
Message:
NSC0165 APPC Partner LU is not defined.
Explanation: An APPC PLU could not be found or is not configured correctly.
User Response: You should have seen a more detailed message preceding this
which will better determine the cause. See the Network SignON Coordinator/2
User's Guide on how to locate the LOG, if it is not on your screen.
ΓòÉΓòÉΓòÉ 6.41. NSC0166 Communications Manager is not installed. ΓòÉΓòÉΓòÉ
Message:
NSC0166 Communications Manager is not installed.
Explanation: NSC could not access the host because Communications Manager is
not installed.
User Response: Install Communications Manager and restart the machine before
attempting to access a host.
ΓòÉΓòÉΓòÉ 6.42. NSC0167 Communications Manager must be restarted. ΓòÉΓòÉΓòÉ
Message:
NSC0167 Communications Manager must be restarted.
Explanation: NSC could not access the host because Communications Manager has
experienced a fatal error.
User Response: Restart Communications Manager and retry the request.
ΓòÉΓòÉΓòÉ 6.43. NSC0170 EHLLAPI is not installed. ΓòÉΓòÉΓòÉ
Message:
NSC0170 EHLLAPI is not installed.
Explanation: EHLLAPI has not been installed or configured correctly.
User Response: Refer to the Network SignON Coordinator/2 User's Guide, and the
emulator's support information to determine how to install and configure
EHLLAPI support.
ΓòÉΓòÉΓòÉ 6.44. NSC0171 Host emulator session is in use. ΓòÉΓòÉΓòÉ
Message:
NSC0171 Host emulator session is in use.
Explanation: The host emulator session is in use by another user. NSC is not
able to access it. The request was not queued because the NSC Retry Process was
not started. If you were attempting to change passwords, your password will be
out of sync on the host. If you were attempting to signon, you will not be
signed on to the host.
User Response: Try the operation again at a later time.
If you start the NSC Retry Process at startup, failures such as this can be
queued and automatically retried when the host session becomes available.
ΓòÉΓòÉΓòÉ 6.45. NSC0172 Host emulator session is in use. The operation has been queued. ΓòÉΓòÉΓòÉ
Message:
NSC0172 Host emulator session is in use. The operation has been queued.
Explanation: The host emulator session is in use by another user. NSC is not
able to access it. NSC has queued your request to be retried. The operation
will be retried by the NSC Retry Process. If the host emulator session does not
become available, and you were attempting to change passwords, your password
will be out of sync on the host; if you were attempting to signon, you will not
be signed on to the host.
User Response: Once the host emulator session has become available, check the
NSC Retry Process to verify that the operation was successfully retried. If the
retry was not successful, resubmit the request.
ΓòÉΓòÉΓòÉ 6.46. NSC0173 Host info file open/access error. ΓòÉΓòÉΓòÉ
Message:
NSC0173 Host info file open/access error.
Explanation: The host information file was not found, or could not be accessed.
User Response: Refer to the relevant log file for more detailed information.
See the Network SignON Coordinator/2 User's Guide for more details. Review the
ParseHIF function's log messages near the end of the log file. The last
ParseHIF log message will tell you the host information file name, the line
number, and the column number where the file open/access error was encountered.
Verify the host information file is named correctly, resides in the correct
directory, and can be accessed successfully.
ΓòÉΓòÉΓòÉ 6.47. NSC0174 Host emulator session id is invalid. ΓòÉΓòÉΓòÉ
Message:
NSC0174 Host emulator session id is invalid.
Explanation: The host emulator session id specified in the host information
file's configuration section does not correspond to a configured/started host
emulator session.
User Response: Verify that the one character session id specified in the host
information file's configuration section corresponds to a host emulator session
that has been configured/started.
ΓòÉΓòÉΓòÉ 6.48. NSC0175 Host info file contains a syntax error. ΓòÉΓòÉΓòÉ
Message:
NSC0175 Host info file contains a syntax error.
Explanation: The host information file contains a syntax error, i.e.: a
misspelled keyword, a missing comma, a missing double quote for a string, etc.
User Response: Refer to the relevant log file for more detailed information.
See the Network SignON Coordinator/2 User's Guide for more details. Review the
ParseHIF function's log messages near the end of the log file. The last
ParseHIF log message will tell you the host information file name, the line
number, and the column number of syntax error. The contents of the host
information file line in error will appear in the log file on a following line.
Edit the host information file, correcting the syntax error.
ΓòÉΓòÉΓòÉ 6.49. NSC0176 Host info file contains a parameter that is not valid. ΓòÉΓòÉΓòÉ
Message:
NSC0176 Host info file contains a parameter that is not valid.
Explanation: The host information file contains a parameter that is not valid.
User Response: Refer to the relevant log file for more detailed information.
See the Network SignON Coordinator/2 User's Guide for more details. Review the
ParseHIF function's log messages near the end of the log file. The last
ParseHIF log message will tell you the host information file name, the line
number, and the column number of the parameter in error. The contents of the
host information file line in error will appear in the log file on a following
line. Edit the host information file, correcting the parameter.
ΓòÉΓòÉΓòÉ 6.50. NSC0178 Host info file exceeds maximum line length. ΓòÉΓòÉΓòÉ
Message:
NSC0178 Host info file exceeds maximum line length.
Explanation: The host information file contains a line that exceeds the maximum
line length allowed.
User Response: Refer to the relevant log file for more detailed information.
See the Network SignON Coordinator/2 User's Guide for more details. Review the
ParseHIF function's log messages near the end of the log file. The last
ParseHIF log message will tell you the host information file name, the line
number, and the column number of the line exceeding the maximum length allowed.
The contents of the host information file line in error will appear in the log
file on a following line. Edit the host information file, reducing the length
of the line in error.
ΓòÉΓòÉΓòÉ 6.51. NSC0180 Cannot start from the host session's current screen. ΓòÉΓòÉΓòÉ
Message:
NSC0180 Cannot start from the host session's current screen.
Explanation: The host emulator session is not in one of the specified start
screens for the requested signon operation. If you were attempting to change
passwords, your password will be out of sync on the host. If you were
attempting to signon, you will not be signed on to the host.
User Response: Check the host emulator session. If the host is in a valid start
screen for the requested operation, edit the host information file, adding a
corresponding new sequence of screen definitions, or correct an existing one.
Otherwise, reset the host emulator session to a valid start screen and try the
operation again.
ΓòÉΓòÉΓòÉ 6.52. NSC0181 Cannot continue from the host session's current screen. ΓòÉΓòÉΓòÉ
Message:
NSC0181 Cannot continue from the host session's current screen.
Explanation: The host emulator session did not enter one of the required
screens for the requested signon operation. Thus, the operation cannot be
continued.
User Response: Refer to the relevant log file for more detailed information.
See the Network SignON Coordinator/2 User's Guide for more details. Review the
PerfAct function's log messages near the end of the log file. The last PerfAct
log message will tell you the host screen that was required but not
encountered.
Edit the host information file, adding a corresponding new screen definition,
or correcting an existing one for the requested operation. If the screen
definition already exists and is correct, you may need to increase the value of
the configuration option HOSTWAIT until NSC waits long enough for the host to
finish changing screens.
Check the host emulator session. If the host has not already been reset, reset
it to a valid start screen.
ΓòÉΓòÉΓòÉ 6.53. NSC0182 No host screen definitions configured. ΓòÉΓòÉΓòÉ
Message:
NSC0182 No host screen definitions configured.
Explanation: The host information file does not contain any screen definitions
for the requested operation.
User Response: Edit the host information file, adding the required screen
definitions for the desired operation.
ΓòÉΓòÉΓòÉ 6.54. NSC0183 No available host emulator session. ΓòÉΓòÉΓòÉ
Message:
NSC0183 No available host emulator session.
Explanation: The host emulator session ids specified in the host information
file's configuration section are all either in use, invalid, or not available.
User Response: Modify the session ids specified in the host information file's
configuration section, or make sure the desired host emulator session is
configured/started.
ΓòÉΓòÉΓòÉ 6.55. NSC0190 An unexpected system error was encountered. ΓòÉΓòÉΓòÉ
Message:
NSC0190 An unexpected system error was encountered.
Explanation: An internal NSC function detected a software failure.
User Response: Submit an NSC problem report along with your NSC LOGs.
ΓòÉΓòÉΓòÉ 6.56. NSC0191 Not enough memory is available. ΓòÉΓòÉΓòÉ
Message:
NSC0191 Not enough memory is available.
Explanation: Not enough memory is available to perform the desired operation.
User Response: Free up system resources. Resubmit the request.
ΓòÉΓòÉΓòÉ 6.57. NSC0192 User Exit could not be executed. ΓòÉΓòÉΓòÉ
Message:
NSC0192 User Exit could not be executed.
Explanation: NSC was unable to successfully execute the user exit routine for
the location just processed. This message is displayed in DOS if the exit
routine could not be started, or in OS/2 if the session for a user exit program
could not be started.
User Response: Review the preceding messages to determine the location
definition being processed. Look in the configuration file to determine the
user exit program or command file specified for the definition. Check the file
name specification and make sure the program or command file is in the path.
ΓòÉΓòÉΓòÉ 6.58. NSC0193 User Exit failed. Return code = <Code>. ΓòÉΓòÉΓòÉ
Message:
NSC0193 User Exit failed. Return code = <Code>.
Explanation: The user exit routine for the location just processed return the
return code rc to NSC.
User Response: Review the preceding messages to determine the location
definition being processed. Look in the configuration file to determine the
user exit program or command file specified for the definition. Consult your
administrator if necessary to determine the cause of the error.
ΓòÉΓòÉΓòÉ 6.59. NSC0200 You are not authorized at this time of day. ΓòÉΓòÉΓòÉ
Message:
NSC0200 You are not authorized at this time of day.
Explanation: You attempted to Signon in a time period which you have not been
authorized by the system administrator.
User Response: Contact the system administrator to verify your authorization to
use the LAN Server. This may have been caused by an incorrect clock setting.
ΓòÉΓòÉΓòÉ 6.60. NSC0201 You are not authorized from this computer. ΓòÉΓòÉΓòÉ
Message:
NSC0201 You are not authorized from this computer.
Explanation: You attempted to Signon from a computer which you have not been
authorized by the system administrator.
User Response: Contact the system administrator to verify your authorization.
ΓòÉΓòÉΓòÉ 6.61. NSC0202 Your account is empty. ΓòÉΓòÉΓòÉ
Message:
NSC0202 Your account is empty.
Explanation: Your account either has a zero balance, no credit, or it has been
disabled by the system administrator.
User Response: Contact the system administrator to reset your account.
ΓòÉΓòÉΓòÉ 6.62. NSC0220 Novell NetWare not installed. ΓòÉΓòÉΓòÉ
Message:
NSC0220 Novell NetWare not installed.
Explanation: NSC can not access Novell NetWare to process the request.
User Response: Install NetWare or change the LANSERVER definition in the
configuration file to not specify NOVELL.
ΓòÉΓòÉΓòÉ 7. Data Entry and Command Line Message Helps ΓòÉΓòÉΓòÉ
The following topics explain NSC/2 messages displayed as a result of user
input.
ΓòÉΓòÉΓòÉ 7.1. NSC0301 The User ID is too short or was not entered. ΓòÉΓòÉΓòÉ
Message:
NSC0301 The User ID is too short or was not entered.
Explanation: Either you failed to enter your User ID, or you entered a User ID
that is shorter than the minimum length specified in the configuration file for
the MinUIDLen definition.
User Response: Enter the correct User ID, or exit NSC and modify the MinUIDLen
option in the configuration file.
ΓòÉΓòÉΓòÉ 7.2. NSC0302 The password is too short or was not entered. ΓòÉΓòÉΓòÉ
Message:
NSC0302 The password is too short or was not entered.
Explanation: Either you failed to enter your Password, or you entered a
Password that is shorter than the minimum length specified in the configuration
file for the MinPWLen definition.
User Response: Enter the correct password, or choose a different new password,
or exit NSC and modify the MinPWLen option in the configuration file.
ΓòÉΓòÉΓòÉ 7.3. NSC0303 The User ID is too long. ΓòÉΓòÉΓòÉ
Message:
NSC0303 The User ID is too long.
Explanation: You entered a User ID that is longer than the maximum length
specified in the configuration file for the MaxUIDLen definition.
User Response: Enter the correct User ID, or exit NSC and modify the MaxUIDLen
option in the configuration file.
ΓòÉΓòÉΓòÉ 7.4. NSC0304 The password is too long. ΓòÉΓòÉΓòÉ
Message:
NSC0304 The password is too long.
Explanation: You entered a Password that is longer than the maximum length
specified in the configuration file for the MaxPWLen definition.
User Response: Enter the correct password, or choose a different new password,
or exit NSC and modify the MaxPWLen option in the configuration file.
ΓòÉΓòÉΓòÉ 7.5. NSC0305 The new and confirmation passwords are not the same. ΓòÉΓòÉΓòÉ
Message:
NSC0305 The new and confirmation passwords are not the same.
Explanation: You entered a Confirmation Password that did not match the entered
New Password. Both entries must be identical.
User Response: Enter the new password correctly in both fields.
ΓòÉΓòÉΓòÉ 7.6. NSC0306 The current and new passwords are the same. ΓòÉΓòÉΓòÉ
Message:
NSC0306 The current and new passwords are the same.
Explanation: You entered a New Password that was identical to the entered
Current Password.
User Response: Enter a new password that is different than the current
password.
ΓòÉΓòÉΓòÉ 7.7. NSC0307 User ID or password contains invalid characters. ΓòÉΓòÉΓòÉ
Message:
NSC0307 User ID or password contains invalid characters.
Explanation: You typed an invalid character in the User ID or password command
line parameter. For the User ID, any graphic ASCII character is valid (ASCII
controls are not valid). For passwords, each character must either be
alphanumeric or in the character set specified by the CHARSET definition in the
configuration file (or in the default character set (#, @ or $) if the CHARSET
definition is not specified in the configuration file).
User Response: Restart the command with a valid User ID and/or password.
ΓòÉΓòÉΓòÉ 7.8. NSC0308 Too many command line parameters specified. ΓòÉΓòÉΓòÉ
Message:
NSC0308 Too many command line parameters specified.
Explanation: You attempted to execute either
"NSC ON" with more than two additional command line parameters (valid
parameters for ON are User ID and Password), or
"NSC OFF" with more than one additional command line parameters (the only
valid parameter for OFF is User ID), or
"NSC CHGPW" with more than three additional command line parameters
(valid parameters for CHGPW are User ID, Current Password and New
Password).
User Response: Restart the command with a valid number of command line
parameters.
ΓòÉΓòÉΓòÉ 7.9. NSC0309 A command line parameter that is not valid <Parameter> was specified. ΓòÉΓòÉΓòÉ
Message:
NSC0309 A command line parameter that is not valid <Parameter> was specified.
Explanation: You specified something other than "ON", "OFF" or "CHGPW" as the
first command line parameter.
User Response: Restart the command with a valid parameter.
ΓòÉΓòÉΓòÉ 7.10. Confirm Exit ΓòÉΓòÉΓòÉ
Message:
Confirm Exit
If you select OK, Network SignON Coordinator/2 will exit.
Select Cancel if you do not want to exit.
ΓòÉΓòÉΓòÉ 7.11. Confirm Signoff ΓòÉΓòÉΓòÉ
Message:
Confirm Signoff
If you select OK, Network SignON Coordinator/2 will initiate a Signoff to the
locations you have configured.
Select Cancel if you do not want to Signoff.
ΓòÉΓòÉΓòÉ 8. Configuration Message Helps ΓòÉΓòÉΓòÉ
The following topics explain NSC/2 messages displayed as a result of
configuration conditions.
ΓòÉΓòÉΓòÉ 8.1. NSC0401 Actions are not available because of errors. ΓòÉΓòÉΓòÉ
Message:
NSC0401 Actions are not available because of errors.
Explanation: NSC encountered errors during initialization, or detected a
configuration error.
User Response: Close the window to exit NSC. Correct the errors and restart the
program.
ΓòÉΓòÉΓòÉ 8.2. NSC0403 <Keyword> not allowed with definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0403 <Keyword> not allowed with definition on line <Number> of NSC config file.
Explanation: One of the following has occurred:
You specified the APPC, EMULATOR or EHLL parameter for a LANSERVER,
DOMAIN, LOCAL, NODE or SERVER definition. These parameters can be used
only with a HOST definition.
You specified the IBM or NOVELL parameter for a DOMAIN, HOST, LOCAL, NODE
or SERVER definition. These parameters can be used only with a LANSERVER
definition.
You specified a HIF parameter or HIF Variable parameter for a LANSERVER,
DOMAIN, LOCAL, NODE or SERVER definition, or a HOST definition of type
APPC. The HIF parameter and HIF Variable parameter are only allowed with
a HOST definition of type EMULATOR.
User Response: Delete the parameter or change the definition.
ΓòÉΓòÉΓòÉ 8.3. NSC0404 <Keyword> definition on line <Number> of NSC config file not allowed after a SERVER definition. ΓòÉΓòÉΓòÉ
Message:
NSC0404 <Keyword> definition on line <Number> of NSC config file not allowed after a SERVER definition.
Explanation: You placed a NODE, LANSERVER or DOMAIN definition after a SERVER
definition in your configuration file. Definitions for node logons or LAN
Servers can be configured only for the local workstation, and must precede all
SERVER definitions.
User Response: For node logons, place the NODE definition preceding all SERVER
definitions. For password synchronization to the LAN Server, place the
LANSERVER definition preceding all SERVER definitions; the definition would
then cause NSC to process password changes for the LAN Server from the local
workstation.
ΓòÉΓòÉΓòÉ 8.4. NSC0405 Configuration file <File> was not found. ΓòÉΓòÉΓòÉ
Message:
NSC0405 Configuration file <File> was not found.
Explanation: The configuration file identified by config-file was not found in
the current directory or in the DPATH.
User Response: Either change the current directory before executing or calling
NSC, or modify the DPATH.
ΓòÉΓòÉΓòÉ 8.5. NSC0406 EXIT or EXITID not allowed with SERVER definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0406 EXIT or EXITID not allowed with SERVER definition on line <Number> of NSC config file.
Explanation: You specified an EXIT or EXITID parameter on a SERVER definition.
No signon or password synchronization is associated with the SERVER definition.
Because no action is taken that can be passed on to an exit routine, the EXIT
or EXITID parameter is not allowed.
User Response: Remove the EXIT or EXITID parameter from the SERVER definition.
If a user exit needs the results of access to the local UPM on the Server,
specify the EXIT or EXITID parameter on a LOCAL definition following the SERVER
definition.
ΓòÉΓòÉΓòÉ 8.6. NSC0407 Configuration definition on line <Number> of NSC config file is not valid. ΓòÉΓòÉΓòÉ
Message:
NSC0407 Configuration definition on line <Number> of NSC config file is not valid.
Explanation: NSC did not recognize the definition on the indicated line from
the configuration file.
User Response: Either correct the spelling of the definition, or start the line
with an asterisk if the line should be ignored.
ΓòÉΓòÉΓòÉ 8.7. NSC0408 Definition or parameter value <Value> on line <Number> of NSC config file is not valid. ΓòÉΓòÉΓòÉ
Message:
NSC0408 Definition or parameter value <Value> on line <Number> of NSC config file is not valid.
Explanation: The value vvvv is outside the range of valid values for this
definition or parameter on the indicated line from the configuration file For
Menu Parameter Length definitions (MinUIDLen, MaxUIDLen, MinPWLen, and
MaxPWLen), valid values are 1 to 8. For Beep and ConfirmExit definitions, valid
values or ON and OFF. For the ID parameter, valid values are 1 to 40. For the
ExitID parameter, the value must match a value specified in an ID parameter for
an Exit definition.
User Response: Correct the value.
ΓòÉΓòÉΓòÉ 8.8. NSC0409 The parameter <Parameter> on line <Number> of NSC config file is not valid. ΓòÉΓòÉΓòÉ
Message:
NSC0409 The parameter <Parameter> on line <Number> of NSC config file is not valid.
Explanation: The parameter pppp is not a valid parameter for this definition.
For LOCAL definitions, the only valid parameters are ON, USERID, EXIT and
EXITID.
For NODE definitions, the only valid parameters are ON, NAME, USERID,
EXIT and EXITID.
For LANSERVER definitions, the only valid parameters are ON, NAME, IBM,
NOVELL, USERID, EXIT and EXITID.
For DOMAIN definitions, the only valid parameters are ON, NAME, USERID,
EXIT and EXITID.
For HOST definitions, the only valid parameters are ON, NAME, APPC,
EMULATOR, USERID, EXIT and EXITID.
For SERVER definitions, the only valid parameter is NAME.
For EXIT definitions, the only valid parameters are NAME, ID, FG, BG,
WAIT, NOWAIT, NOMSGS, MSGS, RC, and NORC.
For GETDEFS definitions, the only valid parameter is SERVER.
User Response: Remove the invalid text from the definition, or insert a space
in the definition prior to the text that should be ignored.
ΓòÉΓòÉΓòÉ 8.9. NSC0410 NSC0410 <Keyword> definition not allowed before SERVER definition in DOS on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0410 NSC0410 <Keyword> definition not allowed before SERVER definition in DOS on line <Number> of NSC config file.
Explanation: You defined a LOCAL definition preceding a SERVER definition on
the DOS Client. NSC does not support local signons for your NSC DOS Client.
User Response: Remove the LOCAL definition. A NODE definition is valid on a DOS
Client and can be used to run a User Exit routine.
ΓòÉΓòÉΓòÉ 8.10. NSC0411 MINPWLEN cannot be greater that MAXPWLEN. ΓòÉΓòÉΓòÉ
Message:
NSC0411 MINPWLEN cannot be greater that MAXPWLEN.
Explanation: You specified a value for the minimum length of a password
(MINPWLEN) that is greater than the value you specified for the maximum length
of a password (MAXPWLEN).
User Response: Either change the MINPWLEN Option value to be less than or equal
to MAXPWLEN (it must remain greater than or equal to 1), or change the MAXPWLEN
Option value to be greater than or equal to MINPWLEN (it must remain less than
or equal to 8).
ΓòÉΓòÉΓòÉ 8.11. NSC0412 MINUIDLEN cannot be greater that MAXUIDLEN. ΓòÉΓòÉΓòÉ
Message:
NSC0412 MINUIDLEN cannot be greater that MAXUIDLEN.
Explanation: You specified a value for the minimum length of a User ID
(MINUIDLEN) that is greater than the value you specified for the maximum length
of a User ID (MAXUIDLEN).
User Response: Either change the MINUIDLEN Option value to be less than or
equal to MAXUIDLEN (it must remain greater than or equal to 1), or change the
MAXUIDLEN Option value to be greater than or equal to MINUIDLEN (it must remain
less than or equal to 8).
ΓòÉΓòÉΓòÉ 8.12. NSC0413 More than one LANSERVER (type IBM) or DOMAIN definition with the ON option on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0413 More than one LANSERVER (type IBM) or DOMAIN definition with the ON option on line <Number> of NSC config file.
Explanation: You specified more than one LANSERVER or DOMAIN definition of type
IBM with the ON parameter. Only one LAN Server logon may be active at a time
for a workstation.
User Response: Remove the ON parameter from one of the LANSERVER or DOMAIN
definitions to allow password synchronization or delete one of the LANSERVER or
DOMAIN definitions.
ΓòÉΓòÉΓòÉ 8.13. NSC0414 More than one LOCAL definition with ON parameter on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0414 More than one LOCAL definition with ON parameter on line <Number> of NSC config file.
Explanation: You specified more than one LOCAL definition with the ON parameter
for the local workstation. Only one Local Logon may be active for a session.
User Response: Remove the ON parameter from one of the LOCALs definition to
allow password synchronization or delete one of the LOCAL definitions.
ΓòÉΓòÉΓòÉ 8.14. NSC0415 NAME not allowed with LOCAL definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0415 NAME not allowed with LOCAL definition on line <Number> of NSC config file.
Explanation: A NAME parameter was specified for a LOCAL definition. For LOCAL
definitions, the only valid parameters are ON, USERID and EXIT.
User Response: Remove the NAME parameter from the LOCAL definition. To specify
the User ID for the LOCAL definition, use the USERID parameter.
ΓòÉΓòÉΓòÉ 8.15. NSC0416 NAME is too long on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0416 NAME is too long on line <Number> of NSC config file.
Explanation: You specified a Host name, IBM LAN Server domain name, NetWare
Server name, or NSC Server name for the NAME parameter of a HOST, LANSERVER,
DOMAIN or SERVER definition that is too long. The maximum length of node names
and host names is 8 characters. The maximum length of IBM LAN Server names and
NSC Server names is 15 characters. The maximum length of a NetWare Server name
is 47 characters.
User Response: Determine the correct name and modify the parameter. For HOST
definitions defining APPC hosts, this is the name of the LU profile in the APPC
configuration. For HOST definitions defining emulator sessions, this is the
name of the host information file for the emulator session (not including the
file extension of ".INI"). For SERVER definitions, this is the computername
specified when installing LAN Requester or LAN Server (this can be found in the
IBMLAN.INI file in the C:\IBMLAN directory). For IBM LANSERVER or DOMAIN
definitions, this is the IBM LAN Server domain name. For NOVELL LANSERVER
definitions, this is the NetWare file server name. For NODE definitions, this
is the Server Node Name configured in the OS/2 Database Manager Workstation
Directory for a database server, or the PLU Name for an APPC application.
ΓòÉΓòÉΓòÉ 8.16. NSC0417 No host type specified for HOST definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0417 No host type specified for HOST definition on line <Number> of NSC config file.
Explanation: You specified a HOST definition without a host type of either
EMULATOR or APPC, or you did not specify the host type prior to an optional
parameter.
User Response: For the HOST definition, specify the host type as either
EMULATOR or APPC preceding any optional parameters.
ΓòÉΓòÉΓòÉ 8.17. NSC0418 NSC terminated because of configuration errors. ΓòÉΓòÉΓòÉ
Message:
NSC0418 NSC terminated because of configuration errors.
Explanation: NSC was not able to execute because of errors detected in your
configuration file.
User Response: Correct the configuration errors and restart the program.
ΓòÉΓòÉΓòÉ 8.18. NSC0419 Signon not allowed at an NSC Server on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0419 Signon not allowed at an NSC Server on line <Number> of NSC config file.
Explanation: You specified the ON parameter for a SERVER definition, or for a
LOCAL definition or HOST definition with a host type of EMULATOR or EHLL
following a SERVER definition. Signon is not supported at the Server.
User Response: Remove the ON parameter from the definition to allow password
synchronization at the location, or delete the definition.
ΓòÉΓòÉΓòÉ 8.19. NSC0420 Path Name is too long on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0420 Path Name is too long on line <Number> of NSC config file.
Explanation: You specified a path name for an EXIT definition or an EXIT or HIF
parameter that is longer than 80 characters. The complete path specification
must be less than 80 characters in length.
User Response: Correct the path name. If necessary, make sure the current path
includes the path where the exit routine resides, and specify only the file
name of the exit routine.
ΓòÉΓòÉΓòÉ 8.20. NSC0421 Too many Exits on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0421 Too many Exits on line <Number> of NSC config file.
Explanation: You specified more than 40 different EXIT definitions or unique
filenames as exit routines on the EXIT parameters for location definitions in
the configuration file. NSC supports a maximum of 40 EXIT definitions. Each
EXIT parameter that specifies a filename that is not specified in any EXIT
definition or any other EXIT parameter is also counted. Filename uniqueness is
case-sensitive.
User Response: Remove one or more EXIT definitions, or remove the EXIT
parameter from one or more of the definitions, or combine the functions of one
or more exit routines into a single exit routine.
ΓòÉΓòÉΓòÉ 8.21. NSC0422 Too many location definitions in NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0422 Too many location definitions in NSC config file.
Explanation: More than 255 LOCAL, NODE, LANSERVER, DOMAIN, HOST and SERVER
definitions were specified in the configuration file. NSC supports a maximum of
255 configured location definitions.
User Response: Delete the extra definitions. It may be possible to support
additional signon and password synchronization using user exits.
ΓòÉΓòÉΓòÉ 8.22. NSC0424 User ID contains characters that are not valid on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0424 User ID contains characters that are not valid on line <Number> of NSC config file.
Explanation: You specified a User ID containing an ASCII control character.
Only graphic ASCII characters are valid in User IDs.
User Response: Correct the User ID.
ΓòÉΓòÉΓòÉ 8.23. NSC0425 User ID is too long on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0425 User ID is too long on line <Number> of NSC config file.
Explanation: You specified a User ID that is longer than the maximum length
specified in the configuration file for the MaxUIDLen definition.
User Response: Correct the User ID.
ΓòÉΓòÉΓòÉ 8.24. NSC0426 USERID not allowed with SERVER definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0426 USERID not allowed with SERVER definition on line <Number> of NSC config file.
Explanation: You specified a USERID parameter on a SERVER definition. No signon
or password synchronization is associated with the SERVER definition. Thus, the
USERID parameter is not allowed.
User Response: Remove the USERID parameter from the SERVER definition. If
password synchronization with the local UPM on the Server is required, specify
the USERID parameter on a LOCAL definition following the SERVER definition.
ΓòÉΓòÉΓòÉ 8.25. NSC0427 No NAME parameter specified for <Keyword> definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0427 No NAME parameter specified for <Keyword> definition on line <Number> of NSC config file.
Explanation: You specified a NODE, LANSERVER, DOMAIN, HOST, SERVER or EXIT
definition without a NAME parameter.
User Response: Specify a NAME parameter. For a LANSERVER (type IBM) or DOMAIN
definition, specify the IBM LAN Server domain name using the NAME parameter.
For a LANSERVER (type NOVELL) definition, specify the NetWare Server name using
the NAME parameter. For a HOST definition, specify the host name using the NAME
parameter. For a SERVER definition, specify the machine name using the NAME
parameter. For an EXIT definition, specify the user exit filename using the
NAME parameter. For NODE definitions, specify the Server Node Name configured
in the OS/2 Database Manager Workstation Directory for a database server, or
the PLU Name for an APPC application.
ΓòÉΓòÉΓòÉ 8.26. NSC0428 I/O error reading <File> after line <Number>. ΓòÉΓòÉΓòÉ
Message:
NSC0428 I/O error reading <File> after line <Number>.
Explanation: NSC detected an I/O error when reading the NSC configuration file
or host information file identified by config-file. The error was detected
after reading line <nn>.
User Response: Retry the operation. If the disk error persists, take steps to
circumvent the error. Possible corrective actions include:
Rename the file so that the faulty disk space is not reused, then
recreate the file.
Reformat the disk to eliminate bad sectors, then restore your system.
Replace your disk, then restore your system.
ΓòÉΓòÉΓòÉ 8.27. NSC0429 Line <Number> in NSC config file is too long. ΓòÉΓòÉΓòÉ
Message:
NSC0429 Line <Number> in NSC config file is too long.
Explanation: Line <nn> contains too many characters.
User Response: Edit the NSC configuration file and delete unneeded characters,
then retry the operation.
ΓòÉΓòÉΓòÉ 8.28. NSC0431 No server type specified for LANSERVER definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0431 No server type specified for LANSERVER definition on line <Number> of NSC config file.
Explanation: You specified a LANSERVER definition without a host type of IBM or
NOVELL, or you did not specify the host type prior to an optional parameter.
User Response: For the LANSERVER definition, specify the host type as IBM or
NOVELL preceding any optional parameters.
ΓòÉΓòÉΓòÉ 8.29. NSC0432 User ID is too short on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0432 User ID is too short on line <Number> of NSC config file.
Explanation: You specified a User ID that is shorter than the minimum length
specified in the configuration file for the MinUIDLen definition.
User Response: Correct the User ID.
ΓòÉΓòÉΓòÉ 8.30. NSC0433 Host type already specified for HOST definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0433 Host type already specified for HOST definition on line <Number> of NSC config file.
Explanation: You specified a host type of both EMULATOR (EHLL) and APPC for the
HOST definition. You may only specify one host type.
User Response: Remove the incorrect host type.
ΓòÉΓòÉΓòÉ 8.31. NSC0434 Server type already specified for LANSERVER definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0434 Server type already specified for LANSERVER definition on line <Number> of NSC config file.
Explanation: You specified a LAN Server type of both IBM and NOVELL for the
LANSERVER definition. You may only specify one LAN Server type.
User Response: Remove the incorrect LAN Server type.
ΓòÉΓòÉΓòÉ 8.32. NSC0435 Too much variable length text on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0435 Too much variable length text on line <Number> of NSC config file.
Explanation: The length of your location names, userid, and user exit paths,
combined with the large number of location definitions you have configured,
requires too much memory.
User Response: If the same user exit path is specified more than once, try
using specifying it once with an EXIT definition and referencing it using the
EXITID parameter. If this does not help, reduce the number of location
definitions,
ΓòÉΓòÉΓòÉ 8.33. NSC0436 No ID specified for an EXIT definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0436 No ID specified for an EXIT definition on line <Number> of NSC config file.
Explanation: You specified an EXIT definition without an ID parameter.
User Response: Specify a unique ID number for the user exit using the ID
parameter.
ΓòÉΓòÉΓòÉ 8.34. NSC0440 V<Variable Number> already specified for HOST definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0440 V<Variable Number> already specified for HOST definition on line <Number> of NSC config file.
Explanation: You specified the same HIF Variable parameter twice for the HOST
definition.
User Response: Remove one of the HIF Variable parameters.
ΓòÉΓòÉΓòÉ 8.35. NSC0441 V<Variable Number> string syntax error for HOST definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0441 V<Variable Number> string syntax error for HOST definition on line <Number> of NSC config file.
Explanation: The HIF Variable parameter contains a syntax error (for example, a
missing comma, a missing double quote for a string, etc.).
User Response: Correct the HIF Variable parameter.
ΓòÉΓòÉΓòÉ 8.36. NSC0442 Too much variable string text for HOST definition on line <Number> of NSC config file. ΓòÉΓòÉΓòÉ
Message:
NSC0442 Too much variable string text for HOST definition on line <Number> of NSC config file.
Explanation: The combined length of all of the HIF Variable parameters for the
HOST definition is greater than 80. The HIF Variable parameters for a single
HOST definition are limited to a total of 80 characters.
User Response: Reduce the number of HIF Variable parameters or reduce the
length of the values for one or more of the HIF Variable parameters.
ΓòÉΓòÉΓòÉ 8.37. NSC0443 Multiple GETDEFS found; or an EXIT or location definition used with a GETDEFS definition. ΓòÉΓòÉΓòÉ
Message:
NSC0443 Multiple GETDEFS found; or an EXIT or location definition used with a GETDEFS definition.
Explanation: One or more of the following configuration errors has occurred:
The NSC.INI file has multiple GETDEFS.
The NSC.INI file contained a GETDEFS as well as an EXIT definition or
location definition.
User Response: Determine which configuration error occurred and correct it. In
the first case, delete the extraneous GETDEFS. In the second case, either
remove the GETDEFS or remove the location and EXIT definitions.
ΓòÉΓòÉΓòÉ 8.38. NSC0444 A linked to definition file contained a GETDEFS definition. ΓòÉΓòÉΓòÉ
Message:
NSC0444 A linked to definition file contained a GETDEFS definition.
Explanation: The configuration file loaded because of a GETDEFS in the NSC.INI
file contains a GETDEFS.
User Response: Either remove the GETDEFS from the NSC.INI file or the file
referenced by the GETDEFS.
ΓòÉΓòÉΓòÉ 8.39. NSC0445 Unable to create local copy of HIF file <File>. ΓòÉΓòÉΓòÉ
Message:
NSC0445 Unable to create local copy of HIF file <File>.
Explanation: When NSC loads a configuration file from an NSC Server, it
attempts to copy all HIF files referenced from the server and created a local
copy of the HIFs. NSC was attempting to copy the filename HIF file.
User Response: Investigate the following:
Is there adequate disk space on the drive where NSC is installed at the
Client workstation to hold the HIF?
Does the HIF exist on the NSC Server in the NSC execution directory?
Correct the problem and restart NSC.