[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

531.0. "Printing via DQS, incorrect directory syntax being used." by KERNEL::SIMPSONR (fred) Tue Apr 21 1992 12:32

ALL-IN-1 2.4  WPS-PLUS V4.0
---------------------------

The customer sets host from a PC attached to a Microvax to an 8650:


   +-------------+           Connects to           +------------+
   | MICROVAX    |      --------------------->     | 8650       |
   | (User's     |         Prints to queue         | (ALL-IN-1) |
   | Login Node) |      <---------------------     |            |
   +-------------+                                 +------------+    

Print Queues:

     LN05$PRINT <---- LN05$ANSI <-------- MVAX33$LN05$ANSI <---- LN05_ANSI_DQS

When printing from EM. I found that the cause of the problem was that a logical
had been incorrectly translated.

   The logical :       "sys$sysroot" = "$1$DIA0:[SYS0.]"

The job on the queue has:

   MVAX33$LN05$ANSI :  SYS$SYSROOT:[SYSCOMMON.DQS$SERVER]MAN000S11_WP4.LIS
   LN05$ANSI        :  $1$DIA0:[SYSCOMMON.DQS$SERVER]MAN000S11_WP4.LIS

It should have been:

   LN05$ANSI        :  $1$DIA0:[SYS0.SYSCOMMON.DQS$SERVER]MAN000S11_WP4.LIS


Does anyone have any ideas as to why it is not translating it correctly....

Cheers,
Richard Simpson (CSC).
T.RTitleUserPersonal
Name
DateLines
531.1Mainly because its not translating the logicalIOSG::TALLETTJust one more fix, then we can ship...Tue Apr 21 1992 20:0931
    
    	Yes. This is a fairly common one. The queue subsystem uses file
    	ids not filenames, so when it prints filenames it actually uses
    	LIB$FID_TO_NAME to convert the file-id to a name. This uses
    	a field in the file header to get the name of the file. This field
    	is not always correct, and is nearly always wrong for SYSCOMMON.DIR
    	due to the way the VMS installation procedure creates the
    	directory. Note that the logical name didn't get involved at all.
    
    	I have *NEVER* seen this actually cause a problem though, since
    	only people read the filespec, it is not used by the queue system.
    	However, you are using DQS which I am unsure about.
    
    	A simple fix would be to create a directory pointer to
    
   	$1$DIA0:[SYSCOMMON] to make the 
    	$1$DIA0:[SYSCOMMON.DQS$SERVER]MAN000S11_WP4.LIS
    
    	a valid filespec. Something like
    
    	$ SET FILE/ENTER=[000000]SYSCOMMON.DIR [SYS0]SYSCOMMON.DIR
    
    	or you could try renaming [SYS0]SYSCOMMON.DIR to something else and
    	then back again (RENAME re-writes the back pointer I think). This
    	might be a bit risky as I'm not sure whether the image used by
    	RENAME would be found if you rename the directory....
    
    	In any case, fireproof underpants and good backups are in order...
    
    Regards,
    Paul