PELI140B  XCF ERREUR PIXCO in the log of a batch PELICA2 or INTBAL

This anomaly related to a problem XCF induced by a specific overload of network XCF.

Description of the kinematics of this incident:

1. The PELICA2 asks a "Row number" to the SRQ >> OK
2. The SRQ asks a new "Row number" to the MailBox >> OK
3. The mailbox turns over it to the SRQ after a time higher than XTMOUT.

  In this case the key is created but timer "XTMOUT" fell before that the SRQ had time to give to the PELICA2 the "Row number".

All these operations are asynchronous and are based on values of Time-out calculated on a relative fluidity of traffic XCF.

Here some councils which will allow you to avoid this problem:

- Parameter FILESIZ=R is very penalizing for network XCF if it is to use with files of big size. It is necessary to avoid using it. In the case or it is imperative, it is necessary to increase the values of parameters XTMOUT and XTMOUT1 consequently.

- To avoid twice carrying out the same transfer because the PELICA2 or INTBAL which finished in error are subjected again, you can use the parameter DUPFILE=N which controls the presence of a key with the same file name for the same recipient.