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

Conference iosg::all-in-1

Title:	ALL-IN-1 (tm) Support Conference
Notice:	Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:	IOSG::PYECE

Created:	Fri Jul 01 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2716
Total number of notes:	12169

2489.0. "Print 57 attachments - NOSUCHJOB error" by TAV02::CHAIM (Semper ubi Sub ubi .....) Mon Jan 27 1997 11:07

ALL-IN-1 V3.0a

A customer has described the following problem:

For whatever reason they had to print a document which has 57 attachments (the
reason is irrelavent and unless there is an explicit restriction the customer 
insists to do this). If the job is printed via the bacjground formatter, then
it fails with a "No such job" error. If they try printing it in the foreground
it doesn't print anything nor does it give any error.

Thanks,

Cb.

T.R	Title	User	Personal Name	Date	Lines
2489.1	Disk Space? KOA$HEAP_SIZE?	IOSG::ELLIOTTR	Russell Elliott	`Mon Jan 27 1997 11:37`	15
	Both the background and foreground jobs will create 58 (57+1) temporary files in the user's OA$TEMP directory. Perhaps the user is running out of disk space, especially if the documents are large? (Even so, there should be better error handling) Also, there may be a problem with the WPS-PLUS heap (memory allocation) but I would have thought the heap would be cleared after each attachment was processed. Just a couple of thoughts. I haven't done much investigation, apart from successfully printing a mail with 57 small WPS-PLUS attachments. Russell.
2489.2		IOSG::ELLIOTTR	Russell Elliott	`Mon Jan 27 1997 11:42`	8
	Of course, you didn't mention WPS-PLUS, that was just a guess. The temp files are produced whatever the file format. The heap size would just be a problem if using WPS-PLUS. Also, my quick test wasn't done on 3.0a, so it doesn't prove much. Russell.
2489.3	When does the problem occur.	IOSG::NEWLAND	Richard Newland, IOSG, REO2-F/J9	`Mon Jan 27 1997 11:58`	24
	When printing in the background does the failure occur: 1. While ALL-IN-1 is creating the OA$FORMATTER job. 2. While OA$FORMATTER is performing the format operations and creating the print job. 3. While the print job is being processed. When printing in the foreground does the failure occur: 1. While ALL-IN-1 is performing the format operations and creating the print job. 2. While the print job is being processed. The maximum number of attachments that can be processed by an OA$FORMATTER job is 240, so it should be able to handle 57. Richard
2489.4	More info ...	TAV02::CHAIM	Semper ubi Sub ubi .....	`Mon Jan 27 1997 13:22`	31
	> >When printing in the background does the failure occur: > > 1. While ALL-IN-1 is creating the OA$FORMATTER job. > No, the job is created and a show entry shows 58 files, all of which are found. > 2. While OA$FORMATTER is performing the format operations and creating > the print job. > YES, this fails almost immediately with JBC-E-NOSUCHJOB. This error appears for each file. I don't know what happens in the foreground as the customer didn't realize that she must enter "P" for each and every attachment once she issued NEXT-SCREEN to force foreground printing. She's trying it now and will get back to me. Also, this is a mail message which was sent to two users on two different ALL-IN-1 systems running the same version of ALL-IN-1, and this occurs only on one of the systems, the other system prints fine. I had her stop the formatter queue on both systems and print on both systems, and the sho entry for both systems was identical. I also tried increasing the koa$heap_size to 400,000 and restart the formatter queue, but this didn't help, which is not surprising since the failure comes almost immediately, and appears for each and every file. Thanks, Cb.
2489.5	Foreground formats fine...	TAV02::CHAIM	Semper ubi Sub ubi .....	`Mon Jan 27 1997 13:57`	10
	The foreground appears to print fine. I had her remove the background command from PR so that she wouldn't have to use NEXT-SCREEN to bypass the formatter, and the file was formatted and submitted to her printer queue. I have posted a description of this problem in the VMSNOTES conference since it really appears that this might be a VMS problem. Thanks, Cb.
2489.6	Check OA$FORMATTER node	IOSG::NEWLAND	Richard Newland, IOSG, REO2-F/J9	`Mon Jan 27 1997 14:10`	12
	Is the system on which errors occur a cluster? The OA$FORMATTER symbiont job will be running on one node of the cluster, which is displayed by a $SHOW QUEUE OA$FORMATTER command. Is this the same node used by the user? If you log into the OA$FORMATTER node under the SYSTEM account can you access the OA$FORMATTER queue and can you create print jobs? Richard
2489.7	Other docs print fine ...	TAV02::CHAIM	Semper ubi Sub ubi .....	`Tue Jan 28 1997 05:50`	9
	Richard, I don't believe that is the problem since this problem occurs ONLY with this particular document containing the 57 attachments. If your suspicion were correct, then every job would fail. Thanks, Cb.
2489.8	Fails from both nodes in cluster..	TAV02::CHAIM	Semper ubi Sub ubi .....	`Tue Jan 28 1997 05:56`	14
	> >Is the system on which errors occur a cluster? > >The OA$FORMATTER symbiont job will be running on one node of the cluster, >which is displayed by a $SHOW QUEUE OA$FORMATTER command. > >Is this the same node used by the user? I forgot to mention in my previous reply that YES it is a cluster, but it fails from both nodes. Thanks, Cb.
2489.9	Prob solved - queue manager culprit	TAV02::CHAIM	Semper ubi Sub ubi .....	`Tue Jan 28 1997 08:05`	12
	The problem has been solved. I was right in my suspicion that the problem was basically a VMS problem and nothing specififc to oa$formatter. The customer just called me and told me that this morning the entire queue manager on the cluster was corrupted and had to be rebuilt. Once this was done the problem disappeard. Thanks to everyone who sent me ideas. Cb.