-- Customer is looking for specific information on a automated method for releasing enqueued transfers. In this case the customer has a group of transfers that are synchronous, one active transfer at a time, while the other transfers wait for the one to finish. The customer has come across issues that will cause an active transfer to fail (connecting server offline or security problems). All transfers in the stream to the same site fail.

There is some complexity to implementing this solution and the customer must perform some tracing. Additionally the customer should have an understanding, from the Installation Manual, of the GENUMSG macro prior to implementing.

If a SITE deactivating or a group of transfers are blocked due to a failure and you have to issue manual InterPel commands to re-activate the site or flag a failing transfer. You will need to create an automation script (JCL that contains IPEL Commands) containing the action you perform. The first step to automating a solution is to perform a trace analysis. You will need to clearly identify the specific log message in InterPel that "announces" the issue will happen or has happened and indicate that manual actions needed to be performed. Once you have identified the message you will need to extract the error message code from the log.

If a SITE becomes deactivated it might be neccessary to remove the ability to retry from the SITE Table.

The third step will be to implement the procedure in the user message table. This will require the review of Section 3.8 USER MESSAGES of the XFB. Inter.Pel V7.3 Installation and Implementation Guide provided with the product distribution. Once an understanding is gained from the Installation and Implementation Guide you will need to "dynamically" add a user message entry. Using the GENUMSG macro defined the MSDID=<trace log message number obtained from the first step> and the PROC=<command set procedure containing the STOPX, CLIPNO, STARTX>. An example of the entry is on page 3-178. Also note that you can pass parameters to the procedure containing the commands.

It is pretty complicated but after go add the first GENUMSG and see it work it will very simple to clone the macro to implement another error message.