Putting a change request in HELD status causes email requesting AUTH to be sent. How do we code CLIP2 so that the email is not sent when the user holds the request?

Document ID : KB000050234
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

You can use TPHASE = 'H' in CLIP2 to identify if the user entered a manual HOLD on the request. This capability was added with Alchemist 5.3.1 PTF SU02466 and 5.2.1 PTF SU02437.

Solution:

CLIP2 is invoked when a request is released (E) or held (H). Held indicates that the request is done as far as input is concerned, don't process it yet but begin gathering approvals.

So it all depends upon how your CLIP2 is coded. This fix added exactly the capabilities that you need:

Alchemist 5.3.1 PTF SU02466 and 5.2.1 PTF SU02437:

PROBLEM(S) FIXED:
When a user enters a change request and does a manual HOLD, Clip 2 is invoked. Clients would like the ability to tell if their users entered a manual HOLD on the request.

In this case, they could choose to not send any authorization notice and wait for the release to do so.
This change will provide this ability. Sample PCL to test for a manual hold would look like:

   // SET TPHASE = ASRRID.PHASE<<F,L>>   
   //* TEST FOR MANUAL HOLD.   
   // IF TPHASE = 'H'   
   //* MANUAL HOLD IS TRUE   
   // ELSE   
   //* MANUAL HOLD IS NOT TRUE   
   // ENDIF  

Hence,
IF TPHASE = 'H' then EXIT 8. This will result in no authorizations being set or emails sent.

In the ELSE part of the IF, you can place the regular security checking and email sending that will be done when the request is released (E).