Using Quantitative resources was one of the most used.<\/p>\n
Request<\/u><\/strong><\/h3>\nWe need to trigger a workflow on demand without having to hold the jobs or release them manually.<\/p>\n
For example, launch it and stop it at specifics time (on demand).
\nOr preventing side effect if an operation that can impact the application is scheduled (holding the workflow then release it)<\/p>\n
Solution<\/u><\/strong><\/h3>\nCreate 2 jobs updating quantitative resources for the application (workflow) we want to trigger.<\/p>\n
Quantitative resource creation<\/h2>\nDefinition
\n<\/u><\/h3>\n
A quantitative<\/span> resource represents a measure that can be quantified such as percentage of CPU, megabytes of storage, or number of tape drives. It provides the ability to avoid overwhelming the physical and logical resources in an environment by limiting the number of jobs that use the same resource at the same time.<\/p>\nCmdline method<\/strong><\/h2>\nUsing ecaqrtab<\/strong> utility to list the existing QR:
\nUnder control user :<\/p>\nCTMSRVCENTOS% ecaqrtab list\n\nDate: 15-Jun-2020.\u00a0\u00a0 Page: 1\n\n\n\n\nQuantitative resource list\n\n\n\n\n+-------------------------------------------------------------------------------------------------+\n\nResource Name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Max-Avail\u00a0 Reserved Used Free\n\n+-------------------------------------------------------------------------------------------------+<\/pre>\nUsing ecaqrtab utility to create your QR (here named QRSTOP<\/strong>):<\/p>\nCTMSRVCENTOS%\n\nCTMSRVCENTOS% ecaqrtab ADD QRSTOP\n\n\n\n\nTotal :99\n\nQuantitative resource 'QRSTOP', Max availability '99' was added.\n\nCTMSRVCENTOS%<\/pre>\n <\/p>\n
Check if QR is created :<\/p>\n
CTMSRVCENTOS% ecaqrtab LIST\nDate: 17-Jun-2020. Page: 1\n\nQuantitative resource list\n\n+-------------------------------------------------------------------------------------------------+\n Resource Name Max-Avail Reserved Used Free\n+-------------------------------------------------------------------------------------------------+\n QRSTOP 99 0 0 99\n\nCTMSRVCENTOS%<\/pre>\nUsing GUI method<\/strong><\/h2>\nBy selecting tools in monitoring pane:<\/p>\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/QRBLOG3.png\")
<\/a><\/u><\/strong><\/p>\nClick on add resource and define resource name Control-M server name and maximum resources you want to allocate.<\/p>\n
<\/a><\/strong><\/p>\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/QRBLOG1.png\")
<\/a><\/u><\/strong><\/p>\nNote<\/h3>\n
If you did the cmdline method, your resource will be displayed as well in QR( quantitative resource ) \u00a0part.<\/p>\n
This first step done; we will assign the jobs which will be managed by this resource.<\/p>\n
QR allocation<\/h3>\n
Affect to all job by find and update method<\/a> ( see my previous topic ) the QR created above. ( QRSTOP )<\/p>\nEach job must need 1 QR to be submitted.<\/p>\n
The aim is to switch the maximum QR from 99 to 0 in order to block the workflow.<\/p>\n
Starting from that it will be easy to manage when this application can be triggered.<\/p>\n
Assigning QR to your workflow<\/h3>\n
For our example I will create an Application composed by jobs that will depend of QR.<\/p>\n
I will use the mass create option to create 10 jobs with QR assigned:<\/p>\n
Note<\/h3>\nTon increment the jobs you can use the syntax JOBNAME{Counter} don\u2019t forget the Uppercase for “C”or it will not work<\/h3>\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/QRBLOG4.png\")
<\/a><\/u><\/strong><\/p>\nTo assign the QR to the jobs , add it to prerequisites part with the quantity needed and the total amount (here, 1 QR per job and total amount 99 )<\/p>\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/QRBLOG5.png\")
<\/a><\/u><\/strong><\/p>\nUse jobs to update QR<\/h3>\n
Now we have all jobs depending of the CR we will create 2 jobs: 1 that update QR to 99 and another that update QR to 0 (which will block the workflow)<\/p>\n
Command to use in the job will be<\/p>\n
To update Quantitative resource ‘QRSTOP’ to 99:<\/p>\n
CTMSRVCENTOS% ecaqrtab UPDATE QRSTOP 99<\/pre>\nQuantitative resource 'QRSTOP', was updated from '0' to '99'<\/pre>\nTo reset the Quantitative resource ‘QRSTOP’ to 0:<\/p>\n
CTMSRVCENTOS% ecaqrtab UPDATE QRSTOP 0\n\nQuantitative resource 'QRSTOP', was updated from '99' to '0'.<\/pre>\nFor more security you can configure your QR jobs to be launched manually (or define a specific \u00a0\u00a0time to start)
\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/QRBLOG6.png\")
<\/a><\/u><\/strong><\/p>\nWe can see that jobs are waiting for the QR that we defined (QRSTOP) as for the moment total amount is 0.<\/p>\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/QRBLOG7.png\")
<\/a><\/u><\/strong><\/p>\nTo submit these jobs, all that remains to be done is to release the job JOB_TEST_QR_TO_99<\/strong><\/p>\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/QRBLOG8.png\")
<\/a><\/u><\/strong><\/p>\nResult<\/u><\/h3>\n
The jobs are submitted as expected:
\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/QRBLOG12.jpg\")
<\/a><\/strong>
\nTo stop the workflow, we can start run the JOB_TEST_QR_TO_0<\/strong>.
\nThis will reset the QR in order to stop the workflow.
\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/QRBLOG10.png\")
<\/a>\u00a0<\/strong><\/p>\nNote<\/h3>\n
Now you can set as you want the execution time of your \u201cQR manager\u201d 😊: JOB_TEST_QR_TO_0 and JOB_TEST_QR_TO_99.
\nDepending of your need you can modulate it<\/p>\n
Example<\/h3>\n
\nOr preventing side effect if an operation that can impact the application is scheduled (holding the workflow then release it)<\/p>\n
Create 2 jobs updating quantitative resources for the application (workflow) we want to trigger.<\/p>\n
Quantitative resource creation<\/h2>\nDefinition
\n<\/u><\/h3>\n
\n<\/u><\/h3>\n
A quantitative<\/span> resource represents a measure that can be quantified such as percentage of CPU, megabytes of storage, or number of tape drives. It provides the ability to avoid overwhelming the physical and logical resources in an environment by limiting the number of jobs that use the same resource at the same time.<\/p>\n Using ecaqrtab<\/strong> utility to list the existing QR: Using ecaqrtab utility to create your QR (here named QRSTOP<\/strong>):<\/p>\n <\/p>\n Check if QR is created :<\/p>\n By selecting tools in monitoring pane:<\/p>\n Click on add resource and define resource name Control-M server name and maximum resources you want to allocate.<\/p>\n If you did the cmdline method, your resource will be displayed as well in QR( quantitative resource ) \u00a0part.<\/p>\n This first step done; we will assign the jobs which will be managed by this resource.<\/p>\n Affect to all job by find and update method<\/a> ( see my previous topic ) the QR created above. ( QRSTOP )<\/p>\n Each job must need 1 QR to be submitted.<\/p>\n The aim is to switch the maximum QR from 99 to 0 in order to block the workflow.<\/p>\n Starting from that it will be easy to manage when this application can be triggered.<\/p>\n For our example I will create an Application composed by jobs that will depend of QR.<\/p>\n I will use the mass create option to create 10 jobs with QR assigned:<\/p>\n To assign the QR to the jobs , add it to prerequisites part with the quantity needed and the total amount (here, 1 QR per job and total amount 99 )<\/p>\n Now we have all jobs depending of the CR we will create 2 jobs: 1 that update QR to 99 and another that update QR to 0 (which will block the workflow)<\/p>\n Command to use in the job will be<\/p>\n To update Quantitative resource ‘QRSTOP’ to 99:<\/p>\n To reset the Quantitative resource ‘QRSTOP’ to 0:<\/p>\n For more security you can configure your QR jobs to be launched manually (or define a specific \u00a0\u00a0time to start) We can see that jobs are waiting for the QR that we defined (QRSTOP) as for the moment total amount is 0.<\/p>\n To submit these jobs, all that remains to be done is to release the job JOB_TEST_QR_TO_99<\/strong><\/p>\n The jobs are submitted as expected: Now you can set as you want the execution time of your \u201cQR manager\u201d 😊: JOB_TEST_QR_TO_0 and JOB_TEST_QR_TO_99.Cmdline method<\/strong><\/h2>\n
\nUnder control user :<\/p>\nCTMSRVCENTOS% ecaqrtab list\n\nDate: 15-Jun-2020.\u00a0\u00a0 Page: 1\n\n\n\n\nQuantitative resource list\n\n\n\n\n+-------------------------------------------------------------------------------------------------+\n\nResource Name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Max-Avail\u00a0 Reserved Used Free\n\n+-------------------------------------------------------------------------------------------------+<\/pre>\n
CTMSRVCENTOS%\n\nCTMSRVCENTOS% ecaqrtab ADD QRSTOP\n\n\n\n\nTotal :99\n\nQuantitative resource 'QRSTOP', Max availability '99' was added.\n\nCTMSRVCENTOS%<\/pre>\n
CTMSRVCENTOS% ecaqrtab LIST\nDate: 17-Jun-2020. Page: 1\n\nQuantitative resource list\n\n+-------------------------------------------------------------------------------------------------+\n Resource Name Max-Avail Reserved Used Free\n+-------------------------------------------------------------------------------------------------+\n QRSTOP 99 0 0 99\n\nCTMSRVCENTOS%<\/pre>\n
Using GUI method<\/strong><\/h2>\n
<\/a><\/u><\/strong><\/p>\n<\/a><\/strong><\/p>\n<\/a><\/u><\/strong><\/p>\nNote<\/h3>\n
QR allocation<\/h3>\n
Assigning QR to your workflow<\/h3>\n
Note<\/h3>\n
Ton increment the jobs you can use the syntax JOBNAME{Counter} don\u2019t forget the Uppercase for “C”or it will not work<\/h3>\n
<\/a><\/u><\/strong><\/p>\n<\/a><\/u><\/strong><\/p>\nUse jobs to update QR<\/h3>\n
CTMSRVCENTOS% ecaqrtab UPDATE QRSTOP 99<\/pre>\n
Quantitative resource 'QRSTOP', was updated from '0' to '99'<\/pre>\n
CTMSRVCENTOS% ecaqrtab UPDATE QRSTOP 0\n\nQuantitative resource 'QRSTOP', was updated from '99' to '0'.<\/pre>\n
\n<\/a><\/u><\/strong><\/p>\n<\/a><\/u><\/strong><\/p>\n<\/a><\/u><\/strong><\/p>\nResult<\/u><\/h3>\n
\n<\/a><\/strong>
\nTo stop the workflow, we can start run the JOB_TEST_QR_TO_0<\/strong>.
\nThis will reset the QR in order to stop the workflow.
\n<\/a>\u00a0<\/strong><\/p>\nNote<\/h3>\n
\nDepending of your need you can modulate it<\/p>\nExample<\/h3>\n