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

Conference spezko::cluster

Title:	+ OpenVMS Clusters - The best clusters in the world! +
Notice:	This conference is COMPANY CONFIDENTIAL. See #1.3
Moderator:	PROXY::MOORE

Created:	Fri Aug 26 1988
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5320
Total number of notes:	23384

5271.0. "configure print queue not to loose current printing job" by COWBOY::MIRGHANE () Fri Mar 28 1997 11:22

    What happens to a printing job when there is a cluster transition.
    We supppose that the node  leaving the cluster is the one that was 
    processing the print job.
    
    We mainly need to know if there is a way to configure the cluster 
    as not to loose the current printing job.
    
    
    Soumetty.

T.R Title User Personal
Name Date Lines

5271.1 Try /RESTART, or f$getqui... XDELTA::HOFFMAN Steve, OpenVMS Engineering Mon Mar 31 1997 15:45 11

T.R	Title	User	Personal Name	Date	Lines
5271.1	Try /RESTART, or f$getqui...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon Mar 31 1997 15:45`	11
	It should pause, then continue -- unless the node was the one that was printing the job, then I'd expect there to be an error -- some DCL f$getqui calls should be able to resurrect the print job from another node, if RETAIN or similar is used. Are you seeing jobs dropped? How are your votes configured? Have you looked at using /RESTART?

   It should pause, then continue -- unless the node was the one that
   was printing the job, then I'd expect there to be an error -- some
   DCL f$getqui calls should be able to resurrect the print job from
   another node, if RETAIN or similar is used.

   Are you seeing jobs dropped?

   How are your votes configured?

   Have you looked at using /RESTART?