[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
|
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
3855.0. "Problem with account on SYS$MANAGER" by ZPOVC::CHINGYUE () Mon Feb 07 1994 11:17
A customer has created a user, SYSTEM residing in
SYS$COMMON:[SYSMGR.OA]. Whenever he print to a queue with Background
formatter set, he receives the DOCUMENT_NOT_FO message.
Further investgation showed that OA$FORMATTER is trying to locate the
file in $1$DIA0:[SYSCOMMON.SYSMGR.OA] instead of
$1$DIA0:[SYS0.SYSCOMMON.SYSMGR.OA]
^^^^
I've tried changing the PROFIL.DIRECT to $1$dia0:[sys0.sysmgr.oa]
without any success.
Is there any workaround ?
Server queue OA$FORMATTER, idle, on WDSI02::, mounted form DEFAULT
/BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[SYSTEM]
/PROCESSOR=OA$FORMATTER /PROTECTION=(S:E,O:D,G:R,W:W) /RETAIN=ERROR
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
857 TEST_BY_DEC_PART_II
SYSTEM 7 Retained on error
%NONAME-E-NOMSG, Message number 092F8452
Submitted 7-FEB-1994 17:45 /BURST /FLAG /NOFEED /FORM=DEFAULT
/PARAM=("OA$PARAMS=110,MIS$PRINT,LP11,1","OA$FMTCTL=2") /PRIORITY=100
File: _$1$DIA0:[SYSCOMMON.SYSMGR.OA]SYS001453.WPL;4 /BURST /DELETE
/NOFEED /FLAG /HEADER
Completed 7-FEB-1994 17:45 on queue OA$FORMATTER
Thanks and regards,
ching-U
T.R | Title | User | Personal Name | Date | Lines |
---|
3855.1 | VMS issue | UTRTSC::SCHOLLAERT | Holland goes USA | Tue Feb 08 1994 07:38 | 15 |
| Hi,
Do a $SHOW DEV SYS$SYSDEVICE /FILES
When you see entries like 00000000 [SYSCOMMON.SYSEXE]F11BXQP.EXE;2
there is something wrong with the structure of the system disk.
The file specs should look like [VMS$COMMON.SYSEXE]F11BXQP.EXE;1
Can be fixed with "renames/set file/inter etc". I would
not touch this stuff. Let a VMS specialist have a look at it,
its not an ALL-IN-1 issue.
Regards,
Jan
|