What is Pcron? How does it differ from the way Perform Manager used cron to schedule its scripts?

Version 5
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    Applies all versions.



    QUESTION:

    Pcron is a scheduler similar to cron in that it schedules the execution of scripts. It was created to keep Perform from submitting a large number of entries to the user's crontab file. This helps to keep cron from being congested with numerous tasks to run at the same time.

     


    ANSWER:

     

    Legacy ID:KA310089

      
       
       How pcron works  
       
    During the submission of a Manager run, a few files are updated behind the scenes:  
    Manager will create an entry in the user's crontab file. This entry is a reference to a PERL script that is going to execute every minute of every day. The PERL script polls the content of a user's 'pcrontab' file for scripts that have been scheduled.  
     
    Example of the PERL script entry in the user's crontab file:  
        
       * * * * * /usr/adm/best1_default/bgs/bin/perl -w -I /usr/adm/best1_default/bgs/lib/PERL /usr/adm/best1_default/bgs/scripts/pcron 2>/dev/null  
       
    Manager will create two files for the user under the $BEST1_HOME/bgs/pcron/repository directory. These two files are:  
    [nodename]-[username].pcron - This file is similar in format to a user's 'crontab' file, containing the dates and times for a specific script to execute. Each entry contains a pcron 'ID', referenced when scheduling and unscheduling tasks via the pcron utility.  
    [nodename]-[username].counter - Contains a numeric value that represents the number of entries that have been submitted to pcron by the user.  
     
    The scripts that are created by Manager (*.Manager, *.Collect, *.ProcessDay, etc) are scheduled in the user's *.pcron file instead of being placed directly to the user's crontab file. The advantage to scheduling scripts in this way allows for multiple Manager-related scripts to be executed simultaneously without interfering with other non-Manager scripts scheduled via cron.  
     
    For more information on TSCO Gateway Server and pcron, check the KA  https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000140607 

     


    Article Number:

    000029513


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles