Manualshelf

NET/MASTER Messages Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series
251252253254255256257258259260
NNM1239
Messages
2–246 106159 Tandem Computers Incorporated
NNM1239 TOP-LEVEL NCL FILE NOT FOUND
Cause. While servicing your logon request, the NonStop NET/MASTER MS system
could not find the top-level NCL procedure specified in your UMS profile.
Effect. The logon request fails.
Recovery. Ensure that the correct name is specified for the main menu procedure in
your UMS profile. You can use another account to check or modify your UMS profile.
Ensure that the procedure is in one of the following libraries:
The NCL library subvolume specified in your UMS profile
The library specified in the NCLCUSTSRC startup parameter
The library specified in the NCLDISTSRC startup parameter
You can use the SHOW PARAM command to determine the libraries specified in the
startup parameters.
NNM1240 ERROR IN YOUR TOP-LEVEL NCL FILE
Cause. While servicing your logon request, the NonStop NET/MASTER MS system
could not compile the top-level NCL procedure (the main menu procedure) specified
in your UMS profile. There was a syntactic error in your procedure.
Effect. The logon request fails.
Recovery. You can log on through another user ID and refer to the activity log for
messages that relate to your procedure to get more information; or, you can, from an
OCS window, start your top-level NCL procedure and note the error messages.
NNM1241 GENERAL FAILURE WHEN COMPILING YOUR TOP-LEVEL NCL
Cause. While servicing your logon request, the NonStop NET/MASTER MS system
could not allocate an NCL ID to your top-level NCL procedure. You may have
exceeded the maximum number of NCL processes that a user can own concurrently in
a region (set by the NCLUMAX system parameter) or there are more than 999999 NCL
processes in the NonStop NET/MASTER MS system already.
Effect. The logon request fails.
Recovery. Retry the logon. If the problem persists, refer the message to your system
manager. The system manager can use the SHOW SYSPARMS=NCLUMAX
command to check its setting. The manager can use the FLUSH command to
terminate NCL processes, if appropriate.