From:	MERC::"uunet!CRVAX.SRI.COM!RELAY-INFO-VAX" 17-NOV-1992 16:15:26.23
To:	thompson@cheme.tn.cornell.edu
CC:	info-vax@kl.sri.com
Subj:	Re: retrofitting the old VMS queue manager

Steve,

> I need to return to using the old VMS queue manager (as used in VMS A5.5 and
> previous versions) on a cluster running 5.5-1, while retaining everything
> else the same (ie I don't want to reinstall A5.5). This is not related
> to any problems with the new queue manager - I have other reasons for
> doing this which I can't go into here. Anyone know how to retrofit the
> old queue manager? Thanks,

	Below, is a previous response I sent INFO-VAX last August.

						-Regis

============================================================================
> If you want to have a V5.4-3 compatible queman and jobcontroller, you'll
> have to install 5.5 from the May condist and say "NO" to "do you want to
> convert your que database?". This will leave you at VMS a5.5. Then you
> can't upgrade to 5.5-1, if memory serves.

	The "hackers" way, even if you've upgraded to VMS 5.5 or have a
	Factory installed newer (4000's etc) machines with VMS 5.5, or
	whatever, is to take advantage of a little known undocumented
	"workaround":

	Edit SYS$STARTUP:VMS$CONFIG-050_JOBCTL.COM and define the symbol
	newjobctl = 0  before the commands to actually run the job controller:

		$newjobctl = 0			  ! Added line
		$define/user sys$output nl:	  ! Old line
		$if newjobctl			  !   ""
		$then				  !   ""
		$run sys$system:jbc$job_control - !   ""
				.
				.
				.
				.
		$else				  ! Else, if set to 1
		$run sys$system:jobctl -	  ! run the "old" job controller
				.
				.
				.

	If 'newjobctl' is set to 0, it will run the old SYS$SYSTEM:JOBCTL.EXE
	instead of the new SYS$SYSTEM:JBC$JOB_CONTROL.  Deleting the 'Added
	line' or setting newjobctl = 1 will give you back the new queue
	manager.
	
	This also allows you the ability of being able to run a cluster of
	pre-VMS 5.5 machines with your VMS 5.5 one, if necessary.

	(Don't forget to save a copy of the original file and restore
	*before* any VMS upgrades !)


							-Regis