ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

uxhld /uxrls res command in error-> No resource is selected for the operation. command in error!!

book

Article ID: 86621

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

One of the following commands may throw the error: "No resource is selected for the operation."

uxhld res res=XX lock
uxrls res res=XX clear
uxshw res res=XX full

Examples:

[[email protected]_bin]# ${UNI_DIR_EXEC}/uxhld RES res=RESLOG_LOCK2 lock
Command : uxhld res res=RESLOG_LOCK2 lock

No resource is selected for the operation.
command in error!!
[[email protected]_bin]# ${UNI_DIR_EXEC}/uxrls RES res=RESLOG_LOCK2 clear
Command : uxrls res res=RESLOG_LOCK2 clear

No resource is selected for the operation.
command in error!!
[[email protected]_bin]# ${UNI_DIR_EXEC}/uxshw RES res=RESLOG_LOCK2 full
Command : uxshw res res=RESLOG_LOCK2 full esp=* mu=* pdate=* tsoc=* partage

No resource is selected for the operation.
command in error!!


The return code of the commands for this error is: 255

Cause

Cause type: By design
Root Cause: The following prerequisite was not fullfilled:

The resource must have been condition-checked with quotas before being able to execute one of the uxhld, uxrls or uxshw commands

Environment

Component: Dollar Universe 

Version: 6.x

Area: Logical Resources

 

Resolution

Before trying to hold / release a logical resource, please check that this prerequisite has been satisfied:
Extracted from the documentation  around Resources:

#######################################################################################################

The resource must have been condition-checked with quotas before being able to execute one of the uxhld, uxrls or uxshw commands.

#######################################################################################################

You can check that for example via the command uxshw res res=XXX full, in case it throws an error, the Resource Event must be first created.

Else, in case the resource event already exists, you should check first that the resource is not already held, you can do that via the command:

uxrls res res=RESOURCE_NAME clear

Additional Information

To avoid issues post migration from version 5 or when creating logical resources, we advise to perform a

uxhld res res=RESOURCE_NAME lock

right after having created it.

Then, you can do a 

uxrls res res=RESOURCE_NAME  clear

And all the commands above will work from now on.