Conference iosg::all-in-1_v30

483.0. "JBC error printing attachments in EM" by KURTAN::WESTERBACK (Mimsy were the borogroves) Tue Apr 14 1992 15:01

	Hi,
	
	A customer has a strange problem when printing from ALL-IN-1 2.4:

	When a non-privileged user tries to print a mail with attachments
	he gets the errors:

	%OA-W-SNDJBC_SYNTAX, error parsing send_jbc command line
	-JBC-F-INVITMCOD, invalid item code or option code
	-OA-E-PARSE, error parsing create_job/queue=#print_queue/job_copies=
		#copies/nonotify/formname=#print_form/jobname=#print_jobname/
		nofile_burst=1/nofile_flag=1
	last line followed by some junk characters

	This is both in background and foreground formatting. The manager
	can print the same mail without problems.

	I asked him to make a trace for me, and via modem I had a look at
	it. Some oddities: several places in " .if...then...get " lines
	"get" is replaced by "p<LF>^X^@" or some similar, see examples 
	below. 



     ! [SCP/TRACE] .if #PRINT_MULTIPLE nes "" then p<LF>^X^@#PRINT_MCOPIES = #
 COPIES << WPPRINT 0062

89     !      Value:
89     ! [SCP/TRACE] .if #PRINT_LISTFILE eqs "" then p<LF>^Y^@#PRINT_LISTFILE =
 "PRINT" << WPPRINT 0080


	This seemed very strange, I checked WPPRINT.SCP but looks
	OK, no customisations. When I tried to go further down in the log
	I get an error message:


	Error reading from input file255 characters
	File name:SYS$SPECIFIC:[FAL$SERVER]A1TRACE.LOG;2
	%RMS-W-RTB, 344 byte record too large for user's buffer
	Press return to continue

	And then the log just stops with this:

186     !      Value: get #PRINT_OUTFILE_1= #PRINT_OUTFILE
186     ! [SCP/TRACE] .if #PRINT_COUNT lt #PRINT_OUT_COUNT then .goto NEXT_ATTAC
 HMENT << WPPRINT 0186
186     ! GET Symbol: #PRINT_COUNT
186     !      Value: 1
186     ! GET Symbol: #PRINT_OUT_COUNT
186     !      Value: 3
187     ! [SCP/TRACE] .goto NEXT_ATTACHMENT << WPPRINT 0186
190     ! [SCP/TRACE] GET #PRINT_TEMP = 1 << WPPRINT 0192
190     ! GET Symbol: #PRINT_TEMP = 1
190     !      Value: 1


	(I couldn't get the whole log in here, a bit tedious to cut'n'paste
	all of it with the mouse)

	So I never get to see the offending command which should be in
	WPPSYSTEM or WPPBGFORMAT.

	
	Next thing, to compare I looked at a trace from the successful
	printing by the manager. It turned out he also had the same
	strange substitution of "get", but that didn't stop anything,	
	and the whole trace log was there OK.

	So now I don't really know how to proceed.... 
	Any ideas anyone?

	Thanks,
	Hans Westerback
	TSC, Stockholm

Have the WPPSYSTEM or WPBGFORMAT scripts been customized?

Looking at the SEND_JBC error message I can see errors in the SEND_JBC 
command parameters.
	
	%OA-W-SNDJBC_SYNTAX, error parsing send_jbc command line
	-JBC-F-INVITMCOD, invalid item code or option code
	-OA-E-PARSE, error parsing create_job/queue=#print_queue/job_copies=
		#copies/nonotify/formname=#print_form/jobname=#print_jobname/
		nofile_burst=1/nofile_flag=1
                            ^^            ^^

The /NOFILE_BURST and /NOFILE_FLAG qualifers do not take a value.  The 
Digital versions of WPPSYSTEM and WPPBGFORMAT do not give these qualifiers 
values.

Different code is executed in WPPSYSTEM and WPPBGFORMAT when creating a
single file job and creating a multiple file job.  Printing mail with
attachments will create a multiple file job which may explain why the 
problem only occurs in this case.


I don't know why the manager can print the mail without problems, unless
he/she is using different versions of WPPSYSTEM and WPPBGFORMAT because of 
a different TXL search order.
          

What happens if a normal user runs ALL-IN-1 with /NOCUSTOMIZE?


Richard

	Thanks Richard!
    
    	Problem is solved after I could log into their system and
    	check it out. It turns out WPPSYSTEM was customized. 
    	Actually I had misheard this error message: 
    
	-OA-E-PARSE, error parsing create_job/queue=#print_queue/job_copies=
		#copies/nonotify/formname=#print_form/jobname=#print_jobname/
		nofile_burst=1/nofile_flag=1
                            ^^            ^^  
    
    	Last line should be: /nofile_burst_one/nofile_flag_one
    
    	
    	And that was just the problem! This qualifier should be
    	either /file_burst_one or /no_file_burst. Syntax error by
    	a programmer no longer with them. 
    
    	Hans