How can I use message IDs to track a Sterling Connect:Direct FASP-related failure?

You can create a rule so that IBM® Sterling Control Center Monitor detects when there is a FASP-related failure for a Sterling Connect:Direct® server.

When you are creating a rule, you can use message IDs specific to FASP transfers on Sterling Connect:Direct servers. The following table lists message IDs that you can use in a rule parameter to track Sterling Connect:Direct FASP-related failures:

Message ID Message Text
XFAS001E XFAS001E: FASP server session creation failed.
XFAS002E XFAS002E: FASP client session creation failed.
XFAS003E XFAS003E: FASP could not be initialized.
XFAS004E XFAS004E: Lock timeout.
XFAS005E XFAS005E: Memory allocation failure.
XFAS006E XFAS006E: Condition wait time out.
XFAS007E XFAS007E: No FASP listen ports available.
XFAS008E XFAS008E: FASP disabled due to file size &FILESIZE < threshold &THRESHOLD.
XFAS009E XFAS009E: FASP session terminated unexpectedly.
XFAS010E XFAS010E: SNODE refused FASP, FASP disabled.
XFAS011E XFAS011E: FASP CRC verification failed.
XFAS020E XFAS020E: Session Manager received invalid FASP control message.
XFAS021E XFAS021E: FASP control message fragmented or invalid.
XFAS022E XFAS022E: Session Manager failed to receive FASP control message.
XFAS023E XFAS023E: The FASP control message exceeds the buffer size.
XFAS024E XFAS024E: Session Manager failed to send FASP control message.
XFAS030E XFAS030E: FASP license file not found.
XFAS031E XFAS031E: FASP license file expired.
XFAS032E XFAS032E: FASP license in error.
XFAS033E XFAS033E: Malformed FASP license.
XFAS034E XFAS034E: FASP license is malformed.
XFAS035E XFAS035E: FASP License file at &LOCATION will expire in &VALUE day(s).
XFAS036E XFAS036E: FASP initialization failed - remote &TYPE &NODE. Error=&ERROR.
XFAS041E XFAS041E: FASP initialization failed - local &TYPE &NODE. Error=&ERROR
XFAS042E FASP initialization failed.