NetEx EFT213 Reference Manual Rel 5.4

UA-501 Protocol error - expected [CC] - got [CC]Severity: ErrorExplanation: The protocol type in NetEx/eFT did not match the protocol type of the remote host.The probable cause is either a network interruption or a revision-level incompatibility between the Initiatorand the Responder.UA-4106 The requested blocksize NNN was reduced to NNNSeverity: InformationalExplanation: The reduction (and resultant message) will only occur during the connect process.First, the local NETEX and remote NETEX perform a blocksize negotiation, and then there is a secondaryblocksize negotiation between the NetEx/eFT Responder and Initiator. During negotiation therequested blocksize gets sent to the remote host and a negotiated blocksize gets returned. The negotiatedblocksize is always the smaller of the two hosts. When connecting to a version 1 Responder, thismessage may occur erroneously during a CONNECT. The blocksize is renegotiated during a version1 file transfer.UA-4109 There were NNN CONNECT records ignoredSeverity: WarningExplanation: The records that are ignored are typically records coming from a newer release of theResponder than the Initiator. In this case the Responder sends more CONNECT information than theInitiator knows how to use. The message provides a warning that the connection may not support allof the functionality offered by the Responder.UA-4127 The MESSAGE stack is emptySeverity: ErrorExplanation: An error has occurred, but there is no message associated with the error.UA-4131 Failed to establish secondary NETEX connectionSeverity: ErrorExplanation: Some NETEX Responders need a second connection to perform file transfers. Thereis likely to be a NETEX error (e.g. too many sessions); check the NETEX message if one is providedand retry. This error could occur as a result of a timeout or because of a revision-level incompatibilitybetween the Initiator and the Responder.UA-4132 Restricted command in server startup fileSeverity: ErrorExplanation: For security reasons, NetEx/eFT server startup files may not contain any of the followingcommands: CONNECT, DISCONNECT, LOCAL, RECEIVE, REMOTE, or SEND. Thesecommands may not be embedded within NetEx/eFT aliases.UA-4133 ProdConfRead ErrorSeverity: ErrorExplanation: This message is displayed when there are errors in reading the PRODCONF file. Thespecific message text will vary depending on the cause of the problem. The messages that could bereported are:• “Failed to open product config file ‘SSSSSS’” where SSSSSS is the name of the prodconf file thelicense verification program attempted to access.• “No data in file ‘SSSSSS’” indicates that the prodconf file, indicated by SSSSSS, is empty.• “Missing LICPATH value in file ‘SSSSSS’” indicates that the prodconf file does not contain avalue for the LICPATH parameter.Page 226 Appendix B. NetEx/eFT Error Messages for IBM z/OS REF-eFT213-R5.4-08