| Author | Message | ||
     Ashwini Mujumdar |
Hi, Before I ask my question I would like to put forth my understanding based on the CPM 4.3 and various threads in the BB for batch job counting - While counting batch jobs that are time triggered , update files and generate no reports , I check for various things where a 'crossing of Boundary ' happens : A)- the time trigger is provided by another application. B) Data feed is sent by another application. C) external data is referenced . D) If none of the above 3 qualify then I consider the batch job to be an internal process. The next step for me is to find the parent EP to which this 'internal process' belongs. Another important consideration could be to validate in addition that the files/ DBs that this batch job is updating are also getting updated by some other EI. This will ensure that they are indeed ILFs. Now to my query : 1. are the steps followed above, correct and sufficient ? 2. The application that I am counting interfaces with several other applications. The batch job in consideration updates a database which is an ILF in another application. I could not find any other online transaction within the application being counted that updates this DB. The batch job is a monthly process critical to business.No reports are generated. Can anyone help me see through how this should be evaluated ? Both the batch job and the database getting updated. Thanks for help. Ashwini Ashwini CFPS ,INS | ||
| Steve Neuendorf Username: Sneuendorf Post Number: 805 Registered: 07-2002 |
Hello Ashwini, I don't feel comfortable with making generalizations. We can say the rules are generalizations, and usually don't leave a lot of questions if they are understood and applied to any actual counting challenge. My first question would be to ask why you are looking at batch jobs? What you describe as your "next step" should be your first step. If you do that, most batch jobs will fall from consideration. Next to your point A; forget time triggers. I will make a generality - you will never find a transaction that turns solely a time trigger as to whether it is countable or not. I would welcome an example to correct me on this if I am wrong. Your point B is purely physical. If you do your "next step" and identify the EPs from the end user view, how data and CI is obtained physically will be irrelevant. Finally, your point C sort of overlaps with B in that it too is physical. I think you are reaching for "data crossing the boundary" and if you really are logically referencing data (EIF most likely but maybe code data or just implementation) nothing is considered to have crossed the boundary. To your question 2, remember, time and timing mean nothing. Counting is based on if something happens and not when it happens. So you are taking a time dependent physical view of the application you are counting. From your user's perspective, whatever they maintain in the application you are counting, is also maintained in the other application(s) by virtue of the maintenance in your application. I suggest you review the shared ILF scenarios. When you do that, you should see the batch job becomes irrelevant to FP counting. Hope this helps, Steve |
