HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- status of queues during system shutdown
Operating System - OpenVMS
        1839859
        Members
    
    
        2500
        Online
    
    
        110156
        Solutions
    
Forums
        Categories
Company
Local Language
                
                  
                  back
                
        
                
        
                
        
                
        
        
        
                
        
                
        
        
        
                
        
              
              Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
                
                  
                  back
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
            
                
            
                
            
                
            
                
            
            
                
            
                
            
            
                
            
                
              
            Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
        Information
        Community
Resources
Community Language
        Language
        Forums
Blogs
	
		
			
            
                
            Go to solution
        
            
		
		
			
            	
	
		
        
		
	
	
		Topic Options
			
				
					
	
			
		
	- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2006 06:54 AM
10-13-2006 06:54 AM
			
				
					
					
						Hi,
I have 4 node cluster running OpenVMS 7.3-2 with a common system disk housed in the main server.
I have 4 batch queues I que manager and 3-4 execution queues per batch queu
so e.g batch1queu -> exec1_b1,exce2_b2,exec3_b3
batch2queue -> exec1_b2,exec2_b2,exec3_b2,exec4_b2
.
.
batch4queue ->
Note: I do not use sys$batch queue
Apart from this I also have the printer queue
Now my question is if I shut down the server what happens to the job while these queues are:
1) If the execution que is in the "executing state"
2) If the execution and/or batch(1,..4) que is in the "holding state"
3) If the execution execution and/or batch(1,..4) queue is in the "paused state"
Please let me know your thoughts on this...
	
			
				
		
			
			
			
			
			
			
		
		
		
	
	
	
I have 4 node cluster running OpenVMS 7.3-2 with a common system disk housed in the main server.
I have 4 batch queues I que manager and 3-4 execution queues per batch queu
so e.g batch1queu -> exec1_b1,exce2_b2,exec3_b3
batch2queue -> exec1_b2,exec2_b2,exec3_b2,exec4_b2
.
.
batch4queue ->
Note: I do not use sys$batch queue
Apart from this I also have the printer queue
Now my question is if I shut down the server what happens to the job while these queues are:
1) If the execution que is in the "executing state"
2) If the execution and/or batch(1,..4) que is in the "holding state"
3) If the execution execution and/or batch(1,..4) queue is in the "paused state"
Please let me know your thoughts on this...
Solved! Go to Solution.
		1 REPLY 1
	
	            
            
		
		
			
            
                - Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2006 07:59 AM
10-13-2006 07:59 AM
Solution
			
				
					
					
						Nipun,
the "first" question here, yoy did not ask:
What happens to the QUEUE MANAGER?
Answer: if it is running on the shutting down node, it fails over to another node, and simply resumes control. In general, things go on just smoothly (forget about the details for now, but some things might become interesting).
Now your questions:
1) The QUEUE is not in execution state, but job(s) IN the queue might be.
Those are aborted, and then take the specified RESTART action (default: job failed)
2) more of the same: the QUEUE is not "holding", JOBs can be.
Nothing changes, they remain holding.
3) They stay in their state. _UNLESS_ the execution queue is specified to only run on that node, then they become "stopped".
For completeness: PRINT queus just fail over, if correctly INITed.
hth
Proost.
Have one on me.
jpe
		
		
	
	
	
the "first" question here, yoy did not ask:
What happens to the QUEUE MANAGER?
Answer: if it is running on the shutting down node, it fails over to another node, and simply resumes control. In general, things go on just smoothly (forget about the details for now, but some things might become interesting).
Now your questions:
1) The QUEUE is not in execution state, but job(s) IN the queue might be.
Those are aborted, and then take the specified RESTART action (default: job failed)
2) more of the same: the QUEUE is not "holding", JOBs can be.
Nothing changes, they remain holding.
3) They stay in their state. _UNLESS_ the execution queue is specified to only run on that node, then they become "stopped".
For completeness: PRINT queus just fail over, if correctly INITed.
hth
Proost.
Have one on me.
jpe
	Don't rust yours pelled jacker to fine doll missed aches.
			
			
				
			
			
			
			
			
			
		The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
		
	
	
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP
