[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

2755.0. "MUA/create acount get "invalid queue name"." by HTSC19::SIMONLAU () Wed May 26 1993 04:19

    Hi,
    
    A customer has just upgraded his ALL-IN-1 from V2.3 to V2.4, he created
    new account thru. MUA and after completing all the entries he got 
    a error message : "failed to submit to batch, invalid queue name"
    
    I suppose that ALL-IN-1 will submit all the batch to queue SYS$BATCH,
    but I couldn't find out anything wrong with it. Anybody could suggest
    some hints to check it out ?
    
    
    Your input would be appreciated.
    
    
    Thanks
    Simon

T.R	Title	User	Personal Name	Date	Lines
2755.1		JGODCL::SHERLOCK	L.U.F.C. The phoenix has risen	`Wed May 26 1993 09:05`	6
	Hi Simon, It looks to me as though the queue that is defined in SM DAP DPS (or DPH) no longer exists, might be worthwhile checking that first. Tim
2755.2	What should be checked in DPS & DPH ?	HTSC19::SIMONLAU		`Fri May 28 1993 09:28`	21
	Re: .1 Hi Tim, Thanks for your input. I've tried to go into the SM DAP DPS and DPH, but I couldn't find anything related to queue entry in both menu ! Mmmm .... did I miss anything ? Besides, I've checked that the logical OA$MTI_QUEUE is pointing to SYS$BATCH which is defined as a generic queue and has been used without problem for a long time. Waiting for your kind advice. Thanks a lot. Regards Simon
2755.3	Try SM MSY SSP....	IOSG::PYE	Graham - ALL-IN-1 Sorcerer's Apprentice	`Fri May 28 1993 11:13`	0
2755.4	V2.4 doesn't have MSY	SCOTTC::MARSHALL	Spitfire Drivers Do It Topless	`Fri May 28 1993 16:11`	10
	The base note says V2.4; I don't think that has MSY or DPS. Not having a V2.4 system to hand, I can't find the right options, but: - OA$MTI_QUEUE has nothing to do with it. - Go to the SM menu and look for an option relating to 'policies'. Type that option. Somewhere amongst the set of screens that takes you to will be one or more fields for batch queues. Check that they have valid queue names. Scott
2755.5	v2.4 you say?	AIMTEC::WICKS_A	Alphatraz - Coming Summer 93	`Fri May 28 1993 16:13`	7
	Scott, SM DAP DPH? Regards, Andrew.D.Wicks
2755.6	What's in a name?	SCOTTC::MARSHALL	Spitfire Drivers Do It Topless	`Fri May 28 1993 16:46`	6
	Andrew, The base noter said he had no luck with SM DAP DPH; I'm far too young to remember ALL-IN-1 V2.4, so I'll leave someone else to give the answer. :-) Scott
2755.7	I think he should look again	AIMTEC::WICKS_A	Alphatraz - Coming Summer 93	`Fri May 28 1993 16:52`	16
	Scott, Well both DPH and DPS have queue fields so maybe the base noter wasn't looking hard enough.... from DPH Batch queue for Housekeeping Procedures: SYS$BATCH from DPS Batch queue for Manage User accounts: SUTHRN_BATCH Regards, Andrew.D.Wicks
2755.8	More info.	HTSC19::SIMONLAU		`Tue Jun 01 1993 04:43`	59
	Re: Hi all, Thanks for your input. I visited the customer's site yesterday and found the following facts (they've given me some wrong info.): . They're running ALL-IN-1 Starter V2.4 on VMS V5.5-2. . In DPH Batch queue for Housekeeping Procedures: SYS$BATCH . In DPS Batch queue for Manage User accounts: SYS$BATCH . The SYS$BATCH is a generic queue and works fine for all other process. . In MUA/create, after all entries input and press RETURN, invalid queue message is displayed. . I turned on the TRACE and in the A1TRACE.LOG, I've found where the "invalid queue name" comes from: ......... ......... 662 ! [SCP/TRACE] .if qui$queue:"BATCH".queue_queue_name[#queue_name] eqs "" then .goto invalid_queue << SM_SUBMIT_CREATE 0102 662 ! GET Symbol: #QUEUE_NAME 662 ! Value: SYS$BATCH 667 ! GET Symbol: QUI$QUEUE:"BATCH".QUEUE_QUEUE_NAME[#QUEUE_NAME] 667 ! Value: 668 ! GET Symbol: "" 668 ! Value: 668 ! [SCP/TRACE] .goto invalid_queue << SM_SUBMIT_CREATE 0102 *************** 676 ! [SCP/TRACE] get oa$display=oa$_sm_submit_f_bad_queue << SM_SUBMIT_CREATE 0154 676 ! %OA-I-LOGFUN, Function: GET oa$display=oa$_sm_submit_f_bad_queue 677 ! GET Symbol: oa$display=oa$_sm_submit_f_bad_queue 677 ! Value: Failed to submit to batch - Invalid queue name ........ ........ . Then, I went to the SM_SUBMIT_CREATE.SCP file, and commented the first statement list above, that is .if qui$queue:"BATCH".queue_queue_name[#queue_name] eqs "" then .goto invalid_queue and redo the MUA/create, everything becomes normal, no more error message !! Anybody has an idea on this ?? Please ! Thanks a lot. Simon
2755.9	LOGICAL ?	UTRTSC::SCHOLLAERT	Ajax, Ajax, Ajax...	`Tue Jun 01 1993 06:29`	8
	Hello Simon, Just a guess, but could it be the SYS$BATCH is a system LOGICAL pointing to a real queue ? Regards, Jan
2755.10	Yea, good guess.	HTSC19::SIMONLAU		`Wed Jun 02 1993 03:23`	10
	Jan, Yes, SYS$BATCH is defined as a logical pointing to a queue in the customer's system. Would it cause problem .. ? Thanks Simon
2755.11	Yip	UTRTSC::SCHOLLAERT	Ajax, Ajax, Ajax...	`Wed Jun 02 1993 06:58`	23
	Hello Simon, > Yes, SYS$BATCH is defined as a logical pointing to a queue in the > customer's system. > > Would it cause problem .. ? Yes, thats the problem. Have a look at the trace.... 662 ! [SCP/TRACE] .if qui$queue:"BATCH".queue_queue_name[#queue_name] eqs "" then .goto invalid_queue << SM_SUBMIT_CREATE 0102 662 ! GET Symbol: #QUEUE_NAME 662 ! Value: SYS$BATCH 667 ! GET Symbol: QUI$QUEUE:"BATCH".QUEUE_QUEUE_NAME[#QUEUE_NAME] 667 ! Value: Just replace the queue name with the the real queue name in the policies settings. Regards, Jan