Using Console Commands › Console Commands › RESET DATABASE,SUBSYS Command—Reset Subsystem Database Storage

RESET DATABASE,SUBSYS Command—Reset Subsystem Database Storage

Use the RESET DATABASE,SUBSYS command to reclaim a database storage area allocated by a subsystem which shared the database in the past but is not expected to share the database in the future.

Each subsystem that shares the database allocates a 1MB area of database storage to maintain cryptographic statistics. These 1MB areas are not automatically freed. Any subsystems which shared the database in the past continue to take up database space.

This command returns the subsystem areas to the available pool of database space. You can specify a sussytem area or be prompted through a list of eligible subsystems one at a time. No keys are removed from the database as a result of this command.

Before issuing this command, use the DISPLAY DATABASE,SUBSYS command to display the list of subsystems. Only subsystems which are not currently running and are not shown as *NKMKEYS* can be reset.

This command has the following format:

BESn RESET DATABASE,SUBSYS=[lpar.BESn|ALL]

n

Indicates the BES task number.

lpar.BESn

Specifies a specific subsystem area to be reset. You are prompted with the following WTOR which you must respond to:

BESnX0210I Reset this subsystem (YES, NO or QUIT)

YES

Reset the subsystem, returning its database storage to the available database storage pool.

NO

Do not reset this subsystem. (The command terminates and no action is taken.)

QUIT

Do not reset this subsystem. (The command terminates and no action is taken.)

Note: The following abbreviation can be used for this command:

BESn RESET DB,SUB=lpar.BESn

ALL

This option prompts you through a list of eligible subsystem areas one at a time. You are prompted with the following WTOR for each eligible subsystem, which you must respond to:

BESnX0210I Reset this subsystem (YES, NO or QUIT)

YES

Reset the subsystem, returning its database storage to the available database storage pool.

NO

Do not reset this subsystem. (The command terminates and no action is taken.)

QUIT

Do not reset this subsystem. (The command terminates and no action is taken.)

Note: The following abbreviation can be used for this command:

BESn RESET DB,SUB=ALL

Example: RESET DATABASE,SUBSYS=ALL command

This example allows the system to prompt for each eligible subsystem. This allows you to reset specific subsystems which shared the database in the past while leaving other subsystems untouched.

BES1 RESET DATABASE,SUBSYS=ALL  

BES1X0103I Command Accepted: BES1 RESET DATABASE,SUBSYS=ALL
  SY0A.BES6         October 18, 2010              
*19 BES1X0210I Reset this subsystem (YES, NO or QUIT)  
 R 19,NO                                        
 IEE600I REPLY TO 19 IS;NO             
  SY0A.BES7         August 24, 2009   
*20 BES1X0210I Reset this subsystem (YES, NO or QUIT) 
 R 20,YES                      
 IEE600I REPLY TO 20 IS;YES         
 BES1X0216I Reset completed successfully    
  SY0A.BES8         August 24, 2009   
*21 BES1X0210I Reset this subsystem (YES, NO or QUIT) 
 R 21,QUIT               
 IEE600I REPLY TO 20 IS;QUIT                      
 BES1X0217I Reset aborted

Example: RESET DATABASE,SUBSYS =lpar.BESn command

This example resets a specific subsystem which had shared the database in the past but is not currently sharing the database.

BES1 RESET DATABASE,SUBSYS=SY0A.BES6                             

BES1X0103I Command Accepted: BES1 RESET DATABASE,SUBSYS=SY0A.BES6
  SY0A.BES6         October 18, 2010              
*18 BES1X0210I Reset this subsystem (YES, NO or QUIT)             
 R 18,YES                                                         
 IEE600I REPLY TO 18 IS;YES                                       
 BES1X0216I Reset completed successfully                          
 BES1X0211I Database Subsystems 121                               
  Subsystem         Last Known Activity    Status                 
  ----------------- ---------------------  ---------              
  SY0A.BES1         January 27, 2011       Running         
  SY0A.BES2         January 27, 2011       Running              
  SY0A.BES7         August 24, 2009              
  SY0A.BES8         August 24, 2009              
  SY0B.BES1         January 27, 2011       Running         
  SY0B.BES2         January 27, 2011       Running              
  ES00.BES1         February 04, 2010      *NKMKeys*       
  ES01.BES1         February 04, 2010      *NKMKeys*       
   End of subsystems