IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Not under consideration
Workspace Storage Protect Family
Categories Spectrum Protect (Server)
Created by Guest
Created on Feb 17, 2012

RELATED IDEAS

need a method to have rc.acs_ssi startup/shutdown put into the rcn.d dirs for Linux like TSM 6 install does ro start/stop TSM

In our Linux environment things are killed and started in the /etc/rcn,d scripts where n is the run level. Here are the directories:

lrwxrwxrwx 1 root root 10 Oct 25 16:30 rc0.d -> rc.d/rc0.d
lrwxrwxrwx 1 root root 10 Oct 25 16:30 rc1.d -> rc.d/rc1.d
lrwxrwxrwx 1 root root 10 Oct 25 16:30 rc2.d -> rc.d/rc2.d
lrwxrwxrwx 1 root root 10 Oct 25 16:30 rc3.d -> rc.d/rc3.d
lrwxrwxrwx 1 root root 10 Oct 25 16:30 rc4.d -> rc.d/rc4.d
lrwxrwxrwx 1 root root 10 Oct 25 16:30 rc5.d -> rc.d/rc5.d
lrwxrwxrwx 1 root root 10 Oct 25 16:30 rc6.d -> rc.d/rc6.d

and there are already entries for killing and starting the TSM instance; see K10ut83333_dsmserv.rc in the first listing and S90 in the second listing
and there are already entries for killing and starting the TSM instance; see K10ut83333_dsmserv.rc in the first listing and S90 in the second listing

[root@ut83333 /etc/rc0.d]# ls -l|more
total 336
lrwxrwxrwx 1 root root 17 Oct 25 11:10 K01dnsmasq -> ../init.d/dnsmasq
lrwxrwxrwx 1 root root 24 Oct 25 11:11 K01setroubleshoot -> ../init.d/setroubleshoot
lrwxrwxrwx 1 root root 16 Oct 25 11:10 K01smartd -> ../init.d/smartd
lrwxrwxrwx 1 root root 24 Oct 25 11:11 K02NetworkManager -> ../init.d/NetworkManager
lrwxrwxrwx 1 root root 22 Oct 25 11:11 K02avahi-daemon -> ../init.d/avahi-daemon
lrwxrwxrwx 1 root root 24 Oct 25 11:11 K02avahi-dnsconfd -> ../init.d/avahi-dnsconfd
lrwxrwxrwx 1 root root 15 Oct 25 11:11 K03rhnsd -> ../init.d/rhnsd
lrwxrwxrwx 1 root root 22 Oct 25 11:11 K03yum-updatesd -> ../init.d/yum-updatesd
lrwxrwxrwx 1 root root 14 Oct 25 17:08 K04osad -> ../init.d/osad
lrwxrwxrwx 1 root root 17 Oct 25 11:10 K05anacron -> ../init.d/anacron
lrwxrwxrwx 1 root root 13 Oct 25 11:10 K05atd -> ../init.d/atd
lrwxrwxrwx 1 root root 16 Oct 25 11:10 K05conman -> ../init.d/conman
lrwxrwxrwx 1 root root 19 Oct 25 11:10 K05saslauthd -> ../init.d/saslauthd
lrwxrwxrwx 1 root root 14 Oct 25 11:11 K10cups -> ../init.d/cups
lrwxrwxrwx 1 root root 15 Oct 25 16:28 K10hplip -> ../init.d/hplip
lrwxrwxrwx 1 root root 16 Oct 25 11:10 K10psacct -> ../init.d/psacct
lrwxrwxrwx 1 root root 28 Dec 20 12:51 K10ut83333_dsmserv.rc -> ../init.d/ut83333_dsmserv.rc

[root@ut83333 /etc/rc3.d]# ls -l | grep ut
lrwxrwxrwx 1 root root 19 Oct 25 11:10 K05saslauthd -> ../init.d/saslauthd
lrwxrwxrwx 1 root root 16 Oct 25 11:12 S28autofs -> ../init.d/autofs
lrwxrwxrwx 1 root root 28 Dec 20 12:51 S90ut83333_dsmserv.rc -> ../init.d/ut83333_dsmserv.rc
[root@ut83333 /etc/rc3.d]#

What I would think is that we have to start ssi BEFORE TSM starts so it can talk to the ACSLS library. So I'd think it has to start somewhere in run level 2 (rc2.d)

Idea priority Low
  • Guest
    Reply
    |     Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

  • Guest
    Reply
    |     Feb 27, 2014

    Thank you for submitting this request. Our apologies for the delayed response. We understand the request and feel it is valid request but unfotunately it is not in alignment with our current multi-year strategy and we will not be implementing a solution at this time.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.