mmm communication error occurred during the function issued by the UAP processing. function name=aa....aa name=bb....bb error location=cc....cc reason code=dd....dd detail code=ee....ee

mmm: MCF identifier

aa....aa: Name of issued function

adltap: dc_mcf_adltap function

tactcn: dc_mcf_tactcn function

tactle: dc_mcf_tactle function

tdctcn: dc_mcf_tdctcn function

tdctle: dc_mcf_tdctle function

tdlqle: dc_mcf_tdlqle function

tlscn: dc_mcf_tlscn function

tlscom: dc_mcf_tlscom function

tlsle: dc_mcf_tlsle function

tlsln: dc_mcf_tlsln function

tofln: dc_mcf_tofln function

tonln: dc_mcf_tonln function

bb....bb: MCF communication process identifier, logical terminal name, or connection name

Outputs ******** if the MCF communication process identifier, logical terminal name, or connection name is unknown.

cc....cc: Maintenance information (location of error)

dd....dd: Maintenance information (reason code)

ee....ee: Maintenance information (detail code)

S: The function issued by the UAP returns an error.

O: Contact an OpenTP1 administrator.

Countermeasure: Make sure the MCF manager process or MCF communication process is running.

If corrective action is not possible, obtain the following maintenance documentation (OpenTP1 standard output and file where standard errors are output).

In UNIX:

/tmp/betran.log (default file name) in $DCDIR/spool directory

In Windows, if using the standard output redirect function:

File in %DCDIR%\spool folder