Anonymous_User Absent Member.
Absent Member.
2431 views

Search ability & multiple abort


Hi guys

I was promised some time ago that the ability to search for a user in
NSM Admin would be implemented, but it hasn't made it into the code.

Could this please be added ? With a container with 20,000 objects
trying to fix one particular user is laboursome. Clicking on a user
and typing the first few characters doesn't always work, and seems to
only work with the objects currently in the screen cache. Ie I have
users starting with A in the user list, if I hit the letter Z nothing
happens.

Secondly, can I please get a multiple abort code that doesn't expire.
Tree name is "CIT". I stress (again) that I shouldn't have to contact
development in order to perform an abort on jobs I've created.

Cheers
Dave

--

0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Search ability & multiple abort

Dave,

Updated searching abilities are slated for version 2.1.

The product architect has decided conditions that require a multiple
abort key requires support to be contacted for benefit of improving the
product.

Do you currently need a multiple abort key? If yes, please tell about
about the conditions and the steps needed to reproduce the issue is
possible. Please send this in an email to storagemanager-at-novell.com,
and we will be glad to assist any way we can.

thanks,

NSM Development



Dave wrote:
> Hi guys
>
> I was promised some time ago that the ability to search for a user in
> NSM Admin would be implemented, but it hasn't made it into the code.
>
> Could this please be added ? With a container with 20,000 objects
> trying to fix one particular user is laboursome. Clicking on a user
> and typing the first few characters doesn't always work, and seems to
> only work with the objects currently in the screen cache. Ie I have
> users starting with A in the user list, if I hit the letter Z nothing
> happens.
>
> Secondly, can I please get a multiple abort code that doesn't expire.
> Tree name is "CIT". I stress (again) that I shouldn't have to contact
> development in order to perform an abort on jobs I've created.
>
> Cheers
> Dave
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Search ability & multiple abort

On Feb 15, 2:57 am, NSM Development <storagemana...@novell.com> wrote:
> Dave,
>
> Updated searching abilities are slated for version 2.1.
>
> The product architect has decided conditions that require a multiple
> abort key requires support to be contacted for benefit of improving the
> product.
>
> Do you currently need a multiple abort key? If yes, please tell about
> about the conditions and the steps needed to reproduce the issue is
> possible. Please send this in an email to storagemanager-at-novell.com,
> and we will be glad to assist any way we can.
>
> thanks,
>
> NSM Development
>
>
>
> Dave wrote:
> > Hi guys

>
> > I was promised some time ago that the ability to search for a user in
> > NSM Admin would be implemented, but it hasn't made it into the code.

>
> > Could this please be added ? With a container with 20,000 objects
> > trying to fix one particular user is laboursome. Clicking on a user
> > and typing the first few characters doesn't always work, and seems to
> > only work with the objects currently in the screen cache. Ie I have
> > users starting with A in the user list, if I hit the letter Z nothing
> > happens.

>
> > Secondly, can I please get a multiple abort code that doesn't expire.
> > Tree name is "CIT". I stress (again) that I shouldn't have to contact
> > development in order to perform an abort on jobs I've created.

>
> > Cheers
> > Dave- Hide quoted text -

>
> - Show quoted text -



When will 2.1 be available ? I really need the search ability now.

I needed an abort code because of a mistake that I made, not because
there was something wrong with the system. The primary issue I have
with your requirement to contact support is that it wastes time. If
I'm in a hurry to delete pending jobs, my only choice is to shut down
the engine waiting for the code, which could take at least 24 hours.
Obviously not an option. I urge you to reconsider this requirement
and give it some practical real-world consideration.

cheers
Dave

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Search ability & multiple abort

Dave,

If you need to get a multiple abort key more quickly you have 2 other
options besides posting to the forums.

1. Call Novell Technical Support and open an incident which is the
fastest way, or
2. Write and email to storagemanager-at-novell.com.

Note: In both cases you will need to provide a description of the
problem, and your tree name.

Thanks,

NSM Development

Dave wrote:
> On Feb 15, 2:57 am, NSM Development <storagemana...@novell.com> wrote:
>> Dave,
>>
>> Updated searching abilities are slated for version 2.1.
>>
>> The product architect has decided conditions that require a multiple
>> abort key requires support to be contacted for benefit of improving the
>> product.
>>
>> Do you currently need a multiple abort key? If yes, please tell about
>> about the conditions and the steps needed to reproduce the issue is
>> possible. Please send this in an email to storagemanager-at-novell.com,
>> and we will be glad to assist any way we can.
>>
>> thanks,
>>
>> NSM Development
>>
>>
>>
>> Dave wrote:
>>> Hi guys
>>> I was promised some time ago that the ability to search for a user in
>>> NSM Admin would be implemented, but it hasn't made it into the code.
>>> Could this please be added ? With a container with 20,000 objects
>>> trying to fix one particular user is laboursome. Clicking on a user
>>> and typing the first few characters doesn't always work, and seems to
>>> only work with the objects currently in the screen cache. Ie I have
>>> users starting with A in the user list, if I hit the letter Z nothing
>>> happens.
>>> Secondly, can I please get a multiple abort code that doesn't expire.
>>> Tree name is "CIT". I stress (again) that I shouldn't have to contact
>>> development in order to perform an abort on jobs I've created.
>>> Cheers
>>> Dave- Hide quoted text -

>> - Show quoted text -

>
>
> When will 2.1 be available ? I really need the search ability now.
>
> I needed an abort code because of a mistake that I made, not because
> there was something wrong with the system. The primary issue I have
> with your requirement to contact support is that it wastes time. If
> I'm in a hurry to delete pending jobs, my only choice is to shut down
> the engine waiting for the code, which could take at least 24 hours.
> Obviously not an option. I urge you to reconsider this requirement
> and give it some practical real-world consideration.
>
> cheers
> Dave
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Search ability & multiple abort

NSM Development wrote:

> Dave,
>
> If you need to get a multiple abort key more quickly you have 2 other
> options besides posting to the forums.
>
> 1. Call Novell Technical Support and open an incident which is the
> fastest way, or 2. Write and email to storagemanager-at-novell.com.
>
> Note: In both cases you will need to provide a description of the
> problem, and your tree name.
>
> Thanks,
>
> NSM Development
>
> Dave wrote:
> >On Feb 15, 2:57 am, NSM Development <storagemana...@novell.com>

> wrote:
> > > Dave,
> > >
> > > Updated searching abilities are slated for version 2.1.
> > >
> > > The product architect has decided conditions that require a
> > > multiple abort key requires support to be contacted for benefit
> > > of improving the product.
> > >
> > > Do you currently need a multiple abort key? If yes, please tell
> > > about about the conditions and the steps needed to reproduce the
> > > issue is possible. Please send this in an email to
> > > storagemanager-at-novell.com, and we will be glad to assist any
> > > way we can.
> > >
> > > thanks,
> > >
> > > NSM Development
> > >
> > >
> > >
> > > Dave wrote:
> > > > Hi guys
> > > > I was promised some time ago that the ability to search for a
> > > > user in NSM Admin would be implemented, but it hasn't made it
> > > > into the code. Could this please be added ? With a container
> > > > with 20,000 objects trying to fix one particular user is
> > > > laboursome. Clicking on a user and typing the first few
> > > > characters doesn't always work, and seems to only work with the
> > > > objects currently in the screen cache. Ie I have users starting
> > > > with A in the user list, if I hit the letter Z nothing happens.
> > > > Secondly, can I please get a multiple abort code that doesn't
> > > > expire. Tree name is "CIT". I stress (again) that I shouldn't
> > > > have to contact development in order to perform an abort on
> > > > jobs I've created. Cheers
> > > > Dave- Hide quoted text -
> > > - Show quoted text -

> >
> >
> > When will 2.1 be available ? I really need the search ability now.
> >
> > I needed an abort code because of a mistake that I made, not because
> > there was something wrong with the system. The primary issue I have
> > with your requirement to contact support is that it wastes time.
> > If I'm in a hurry to delete pending jobs, my only choice is to shut
> > down the engine waiting for the code, which could take at least 24
> > hours. Obviously not an option. I urge you to reconsider this
> > requirement and give it some practical real-world consideration.
> >
> > cheers
> > Dave
> >


Thanks -
However, both options aren't really suitable.

(1) I don't have Novell support, meaning I'd have to pay a substantial
fee to open an incident (US$650 last time I checked?). Having a
support contract with novell isn't cost effective (in fact it's
extremely expensive). Even if the money was refunded, that doesn't
really make it any easier - we're an educational organisation, I don't
exactly have a credit card I can use at the drop of a hat, and Novell
won't open Incidents (even for bugs) without first paying for it.

(2) I appreciate you guys respond as quickly as you can to emails,
however, there's a massive time difference between USA and Australia,
so I still wouldn't get a response for up to 24 hours depending on the
time.

It's not the end of the world, but I'm just trying to point out that
your methodology (whilst I do understand it) is flawed. How about
adding a question field or something that you have to fill out before
performing a multiple abort that sends you guys an email as to the
circumstances ? That way you know when and why people are doing it.


Cheers
Dave
--

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.