Problem with User Account

[owilliams]

New to VMS. Can someone tell me what these errors mean.
Error opening SYS$MANAGER:NRC_WELCOME.TXT as input
File not found
Last interactive login on Wednesday, 11-APR-2007 14:00:42.70
Main Menu Login In Progress
Standard application logicals for DB now set up properly
%DCL-I-SUPERSEDE, previous value of DB_DATABASE has been superseded
RDB Set version
Current PROCESS Oracle Rdb environment is version V7.0-3 (MULTIVERSION)
Current PROCESS SQL environment is version V7.0-3 (MULTIVERSION)
Current PROCESS Rdb/Dispatch environment is version V7.0-3 (MULTIVERSION)
Running main menu
%OTS-F-INTDATCOR, internal data corrupted in Run-Time Library

Notify S & DP of this error. Press RETURN to continue...:

[Hein van den Heuvel · Accepted solution]

>> Error opening SYS$MANAGER:NRC_WELCOME.TXT as input
File not found

That's easy... It means exactly what it says and it indicates sloppy system management.


>> Last interactive login on Wednesday, 11-APR-2007 14:00:42.70
Main Menu Login In Progress
Standard application logicals for DB now set up properly

That's all good fluff

>> %DCL-I-SUPERSEDE, previous value of DB_DATABASE has been superseded

This could indicate a problem. A logical name is being defined for the second time, instead of doing a right in the first place.

It may indicate an attempt at hiding a lack of understanding of the system. Maybe redefining that logical requires redefining other logicals also?

>> RDB Set version
Current PROCESS Oracle Rdb environment is version V7.0-3 (MULTIVERSION)
Current PROCESS SQL environment is version V7.0-3 (MULTIVERSION)
Current PROCESS Rdb/Dispatch environment is version V7.0-3 (MULTIVERSION)
Running main menu

Good fluff

>> %OTS-F-INTDATCOR, internal data
corrupted in Run-Time Library

Ouch. That's for real. An internal function was called with corrupted parameters.
It could be a caused by an earlier problem not being react on (sloppy code), or mismatch between libraries, or a real memory corruptor. Be sure to check all log files you can find.


>> Notify S & DP of this error. Press RETURN to continue...:

Did you? Or are you per chance representing "S & DP" ?

Anyway...

Did it ever work?
What was changed (recently)
Does it still work for some instances?
How are the working instances different from the broken ones?

The subject line SUGGESTS that a fresh user was added. Carefully check the SYLOGIN.COM and the LOGIN.COM for that user. Walk through them (code review) seeing how they migh act differently for a different user.

Find the place in a command file where 'Running main menu' is displayed.
Put in some debug statements like
$SHOW DEFAULT
$SHOW LOG/PROC
$SHOW LOG/JOB
$SHOW PROC/PRIV

Compare a good user with a bad user.

Good luck!

Hope this helps some,
Hein van den Heuvel (at gmail dot com)
HvdH Performance Consulting

[Robert Gezelter]

owilliams,

In most sites, the file SYS$MANAGER:SYLOGIN.COM is executed at login. From your output, it would appear that there is a reference to SYS$MANAGER:NRC_WELCOME.TXT in that file (or a related file). It is also possible that the file exists, but is protected in some way from the user reporting the problem.

The OTS$ error, is coming from some program that is being invoked.

I would suggest tracking down both references. It is likely to be illuminating. I would also consider doing a SET VERIFY so that it is possible to see where in the command procedures these two events occur (a note of caution: the output from SET VERIFY may be extensive).

Depending upon what has been done with the login scripts on your site in the past, there may be more efficient ways to track down this problem.

I hope that the above is helpful. If I can be of further assistance, please let me know.

- Bob Gezelter, http://www.rlgsc.com

[Edwin Gersbach_2]

>> Error opening SYS$MANAGER:NRC_WELCOME.TXT as input
File not found

Check the logicals SYS$ANNOUNCE and SYS$WELCOME. One of these could point to this file.

Edwin

[Jon Pinkley]

owilliams,

>>>Running main menu
>>>%OTS-F-INTDATCOR, internal data corrupted in Run-Time Library

If your are running on an Alpha, the following probably will fix it. Otherwise, we need more info.

My guess is that you have recently upgraded VMS and it the Fortran RTL was changed.

The menu was probably written in Fortran, compiled on a VAX, VESTed (image translated to AXP).

Every time I upgrade, I have to reinstall the the DEC AXPVMS FORRTL_TV T6.0-1 patch, since we still use some translated images.

A Google for FORRTL_TV found this:

http://vmsone.com/~decuslib/vmssig/vmslt00b/vu/forrtl_tv-t0600-1.zipexe

You can verify that this is the problem by doing an analyze/image on the menu program.

Since I don't know what the imagename of the program that is causing the error is, I will assume it is MENU. Replace "MENU" with the correct imagename in the following:

$ pipe analyze/image MENU | search/nowindow sys$input "FORRTL_TV"

If the output looks similar to this:

global section name: "FORRTL_TV_001"
1) "FORRTL_TV"

then you need to apply the patch.

Oh, you can also do a show product

$ product show history forrtl_tv/ful

To see it this was ever installed.

If you are not the system manager, you are going to need to get their assistance.

Jon

[Jon Pinkley]

Have you ever taken care or your muliple cluster files?

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1107988

Not related to this problem, but if you have a cluster with multiple system disks, you are going to need to apply the patch to each system disk.

Jon

[owilliams]

thanks for your help guys.