Db2

 View Only

  • 1.  Why are some Stored procedures showing as STARTED and some are not?

    Posted 6 days ago

    Newbie question.

    We have currently about 30 DB2 procedures defined, and all are ACTIVE.  About half of these SPs show a status of "STARTED" in the DB2 Command processor.  Why are some STARTED and some are not started?  Why not just start them all? I assume it's perhaps tied to resources in the machine. Thanks for any and all feedback and answers. 

    Jeff

    ps-I would normally ask the experts in our organisation but most have moved on, and there's no one left to ask..



    ------------------------------
    Jeffery Baker
    ------------------------------


  • 2.  RE: Why are some Stored procedures showing as STARTED and some are not?

    Posted 3 days ago

    Command processor is a generic tool.   what command or what query you executed that shows the "STARTED"  status. ? 



    ------------------------------
    Samuel Pizarro
    ------------------------------

    Original Message


  • 3.  RE: Why are some Stored procedures showing as STARTED and some are not?

    Posted 2 days ago

    First which Db2 product are you using.  Since you mentioned Command Processor I assume LUW.

    More than likely your DB2 LUW system was restart and no user has called the Store Procedures in question .  Db2 would not want to waste resources on processes not being used.



    ------------------------------
    Douglas Partch
    ------------------------------

    Original Message