[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

3043.0. "Cant read or print but can edit??" by STUDIO::ALLIN1 () Wed Jul 21 1993 20:49

There is a user on this system with a strange problem - he cannot read 
or print any of his WPSPLUS documents.  Attempting to readprint shows just

-------------------------------------TOP----------------------------------------
-----------------------------------BOTTOM---------------------------------------

its as if the document is empty, but, if you Edit, the text is all there.
He can forward the message and is able to read the text in the mail message.

This happens only with WPS documents (created from WP menu); mail messages 
are ok.

Any ideas??

Thx - 
T.RTitleUserPersonal
Name
DateLines
3043.1KERNEL::SMITHERSJLiving on the culinary edge....Thu Jul 22 1993 10:577
    Check the pagination settings and particularly the values in the
    first page printed and last page printed field.  This may be set to 
    a value which is wrong.  The default value is First page printed 1
    LAst page printed 0.
    
    Hope this helps.
    julia
3043.2Wrong default directory?IOSG::MAURICEDifferently hirsuteFri Jul 30 1993 17:377
    Does the user change his default directory by the SET_DEFAULT function
    or by $set def in the subprocess? Check oaini.com and oaini.scp for
    this user.
    
    Guessing wildly
    
    Stuart
3043.3Anotehr wild oneFORTY2::ASHGrahame Ash @REOFri Jul 30 1993 17:408
And does he have access to another Format form (not the default)? Try 
<form format 
and make sure it comes from the Manager FLB.

(I'd guess that all the experts are on holiday, so the rest of us are just 
trying anything we can at the moment!)

grahame
3043.4Some more suggestions...IOSG::CHINNICKgone walkaboutFri Jul 30 1993 17:4532
    
    I think that you'll have to resort to low-level measures...
    
    This could be something funny with a file like WPSDEF.WPL, so you might
    try putting a new version of that into the users subdirectory. Editing
    might show up such a problem but then again it might not. You could
    also look at any .PRA (printer table) files which the user might have.
    
    Try printing the document to destination TERMINAL or FILE and see if
    that has any joy in reading and formatting the contents of the file.
    Try making a copy of a document and see how that fares and on the copy
    you could try converting it to ASCII EDT format or DT SV to send it to
    a VMS file. I'd like to establish whether this is a formatter problem
    or a text/compound data-set issue. 
    
    If that doesn't help, I'd try a $ SET WATCH FILE/CLASS=MAJOR in
    DCL and run ALL-IN-1 and reproduce the problem. It should show you all
    the files which are being opened or failing to open. Alternatively, you
    could put Auditing on for the user concerned or for all user using 
    $ SET AUDIT/ALARM/ENABLE=FILE_ACCESS:FAILURE:ALL. 
    
    This might give you a clue as to what - if anything - can't be accessed
    and why. Some failures may be legitimate because of the way in which
    ALL-IN-1 works in some places (trys, fails and then uses elevated privs).
    
    It might also be an idea to check resources such as process quotas and
    disk space/disk quota available.
    
    Other than that, I think you'll need some drastic measures. But lets
    try the simple things first.
    
    Paul.
3043.5WPS-PLUS formatterIOSG::NEWLANDRichard Newland, IOSG, REO2-G/L2Mon Aug 02 1993 15:4923
I can see from the trace that ALL-IN-1 has detected that the document is 
WPS-PLUS and called the WPS-PLUS formatter (the FORMAT function) to display 
it.  No output is being produced so the problem must be within the FORMAT 
function.

Could you do the following:

1.  Update the Handling of the document to 'WPSPLUS NO FMT' and Read it.  
    This will use the ASCII formatter instead of the WPS-PLUS formatter, 
    but will show if the RMS file can be accessed.

2.  Select a WPS-PLUS document and issue the function:

	<format oa$curdoc_filename,'tt:','vt100'

    If this gives error messages what are they?



Also, does this user have any unusual logical names defined?


Richard
3043.6Crazy but good solution...LEMAN::UELTSCHIIsabelle necessary on a bicycle ?Sun Aug 08 1993 23:5025
	Hi,

	The problem you have at the moment happened to me several times
	on different sites.

	I solved it in a very strange way: 
	1) select the document
	2) Print the document
	3) Gold Expand (Gold A)
		then you get the WPS-PLUS Formatter Print Settings Menu
 	4) RS Restore Print and Paragraph Numbering Settings: #0
	5) Clear the number 0 (really clear it...)
	6) Put a '0' and press Return to validate 
	7) SS Save Print and Paragraph Numbering Settings: #0
	8) I am not sure now whether you then have to repeat 
	stages (5) and (6), but do it in any case, it can't do any
	damage.
	9) P Print and Save current settings.

	This seems totally illogical and irrelevant with the problem
	but it did the trick for me... Hope it will be of any use to 
	you.

	Regards - Bernard U.
3043.7Another alternative cause !SIOG::GODWYERWed Dec 08 1993 17:449
    Just incase Bernard's fix does not work for you I have also noticed
    that the problem is related to the "first page printed" setting with
    the Pagination Settings. This should be set to 1 and not 0 which it
    might be for some documents.
    
    Regards,
    
    Gary.