DISKQUOTA error not allowing login

[Swain]

>>>this file calls other command files --- what do they do? Could they be causing the problem?

I searched in all command procedures in SYLOGIN.COM for INQUIRE command.

$ type sys$manager:ams$setup.com
$!
$ ams :== @ams$code:[com]define_logicals.com
$ amslite :== @ams$code:[com]ams_lite.com
$!
$ exit


$ sea ams$code:[com]define_logicals.com inquire
$ inquire P1 "Enter application name (? for help)"
$ inquire P2 "Enter database (? for help)"
$ if (P2 .eqs. "?") then inquire P2 "LIVE, TEST"
$ inquire P3 "Enter site (? for help)"
$ if (P3 .eqs. "?") then inquire P3 'default_site
$ inquire P4 "Enter version (? for help)"
$ if (P4 .eqs. "?") then inquire P4 "PROD, BETA1"

But, these run for all other users and they face no issue.

>>>Do other users have this problem, or only
this user?

No. Issue is with this user only.

If user logs in through the hummingbird tool, he gets the blue screen at start-up saying "Starting new session for open VMS"which gets hung. If however he gets into his ams account through someone else's login (i.e.. set host alpha - login), he can get to the terminal window.

Hope it helps.


Thanks Steven! you have answered all other queries.



Thanks,
Swain

[Volker Halle]

Swain,

the best way to further diagnose this problem would be to instrument SYLOGIN.COM with a SET VERIFY for exactly this user. Did you try that ?

Do other users also use the 'Hummingbird' tool (you're talking about Exceed ?) ?

Volker.

[Zeni B. Schleter]

Sounds like one of the decwindows detached processes is hitting an Inquire. What I do in my login.com is
$ Save_Verify := 'F$Verify(0)
$ if f$mode().eqs. "OTHER" then exit .

First line was for FTP copies and the next was for decwindows detached processes.

-for what it is worth-

[RBrown_1]

This is a problem when logging in to decwindows (ie, the gui). DECW$SM.LOG is a decwindows log file.

You say that if ROLAND logs in by SET HOST, the he doesn't have the problem. But if he logs in by SET HOST, then he is not logging in to the gui, so he would not have the problem.

You say that other users do not have the problem. Do they ever log in to the gui?

[Hein van den Heuvel]

This is somewhat intriguing...

Swain>> I searched in all command procedures in SYLOGIN.COM for INQUIRE command.

We hope you searched for "INQ", not just the full word.


Many warned about not using the inquire command except for interactive sessions.
But it IS valid in batch jobs.
It will just read the next line as the value.

inquire is a build-in DCL command, not an image. It is hard to see how it would ever create an error message with anything other then DCL- or just the plain (RMS) message. I tried:
- Long line: %RMS-W-TNS, terminator not seen
- : %RMS-W-BES, bad escape sequence
- ^Z : silent

The only way i can get the specific output is convoluted, and has nothing to do with the inquire dcl command.
Watch this....

$ create tmp.tmp
$ set prot=(o,s,g,w) tmp.tmp
$ define INQUIRE tmp.tmp
$ write sys$output F$file("INQUIRE","ORG")
%SYSTEM-F-NOPRIV, insufficient privilege or object protection violation
\INQUIRE\


:-)


Hein





I searched in all command procedures in SYLOGIN.COM for INQUIRE command.

[Volker Halle]

Hein,

I was going along the same route ;-)

The error message seen does seem to come directly from DCL without an additional image being invoked. Otherwise you would get SYSTEM-F-NOPRIV as a secondary error message preceeded a message from the image or facility (e.g. RMS) itself.

Swain,

please turn on SET VERIFY in SYLOGIN.COM for this user ...

Volker.

[Volker Halle]

Swain,

please also see the following thread for a similar problem and a solution. That problem involved DECW$SM.LOG filling the disk, so you're lucky that you're using disk quotas !

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1351472

Volker.

[Swain]

I added following lines to SYLOGIN.COM

$ IF F$MODE() .EQS. "OTHER" THEN EXIT
$ IF F$EDIT(f$getjpi("","USERNAME"),"TRIM") .EQS. "ROLAND" THEN $ SET VERIFY

When ROLAND loggedin, the login was succesful but thrown following warning.

%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\AMS\

But this warning came for other users also and AMS did not work for anyone.

Since it's a critical application environment, I had to revert the changes in SYLOGIN.COM.

Please let me know of any alternative.

Thanks,
Swain

[Volker Halle]

Swain,

you should NOT have included

$ IF F$MODE() .EQS. "OTHER" THEN EXIT

Depending on the process environment, in which SYLOGIN is being used, this statement would EXIT your SYLOGIN and fail to invoke the necessary procedures for defining your AMS environment.

But what you've learned from this execerise is: the login problem of user ROLAND DOES depend on SYLOGIN.COM AND/OR some procedure it calls !

Please try again with just the line turning on SET VERIFY for user ROLAND.

Volker.

[Zeni B. Schleter]

I did say LOGIN.COM not SYLOGIN.COM just because users can put queries in the LOGIN.COM that are not friendly with detached processes. Your environment may not allow such usage.