NETD001I: | NETD002I: | NETD003E: | NETD004I: | NETD005I: | NETD006I: | NETD007I: | NETD008E: | NETD009I: | NETD010I: | NETD011I: | NETD012E: | NETD013E: | NETD014E: | NETD015I: | NETD016E: | NETD017I: | NETD018I: | NETD020E: | NETD021W: | NETD023I: | NETD024I: | NETD027W: | NETD036I:
NETD001I: | UNEXPECTED RETURN CODE rc FROM id | ||||||||||||||||||||
Explanation |
A function, a BS2000/OSD or DCAM macro call, received unexpected return code rc from the function or macro call identified by id. Possible values for id are:
Initialization is aborted (INIT). Operation continues (YCLOSE). |
||||||||||||||||||||
Action |
No action is required. This message is informational only. |
NETD002I: | UNEXPECTED RETURN CODE rc/rc2 FROM id | ||||||||||
Explanation |
A function, a BS2000/OSD or DCAM macro call, received an unexpected return code rc. Return code rc2 gives further information. The id identifies the function or macro call. Possible values for id are:
Initialization is aborted (1). Warning (2). |
||||||||||
Action |
No action is required. This message is informational only. |
NETD003E: | INVALID ERROR NUMBER |
Explanation |
The module NDCMSG was called with an error number that is not contained in its table. |
Action |
Contact your Software AG technical support representative. |
NETD004I: | LOGON ACCEPTED FROM APPLICATION partner ON PROCESSOR |
Explanation |
The Logon Contingency accepted a LOGON request from the application partner on processor host. |
Action |
No action is required. This message is informational only. |
NETD005I: | UNSOLICITED LOGON REJECTED FROM APPLICATION partner |
Explanation |
The Logon Contingency received a LOGON request from the application partner on processor host, which was not defined in the start parameters, and the parameter ACCEPTUI=N does not allow the connection. |
Action |
No action is required. This message is informational only. |
NETD006I: | UNSOLICITED LOGON ACCEPTED FROM APPLICATION partner ON |
Explanation |
The Logon Contingency received a LOGON request from the application partner on processor host, which was not defined in the start parameters, but the parameter ACCEPTUI=Y allows the connection. |
Action |
No action is required. This message is informational only. |
NETD007I: | LOST CONNECTION TO APPLICATION partner ON PROCESSOR |
Explanation |
The LOSCON contingency detected that the connection to the application partner on processor host was lost for reason rc. |
Action |
No action is required. This message is informational only. |
NETD008E: | DCAM RPB FOR request REQUEST STILL ACTIVE |
Explanation |
The DCAM request was posted completely but is still marked active. The values for request
OPNCNASY - YOPNCON ASY,Q,ACQUIRE |
Action |
Contact your Software AG technical support representative. |
NETD009I: | DCAM APPLICATION appname OPENED |
Explanation |
The DCAM application appname was opened. |
Action |
No action is required. This message is informational only. |
NETD010I: | DCAM PARTNER APPLICATION partner NOT ACTIVE |
Explanation |
The connection request failed because the partner application is currently not active. |
Action |
No action is required. This message is informational only. |
NETD011I: | DCAM CONNECT ERROR rc TO partner |
Explanation |
The connection request failed with the DCAM reason code given in the message (rc). If the RESTART parameter is specified, the node may retry the connect. |
Action |
No action is required. This message is informational only. |
NETD012E: | MESSAGE FROM link TRUNCATED BY hex |
Explanation |
A message received from the link was truncated. The value specified for the MAXBLK parameter in the partner's LINK statement is too large by at least hex number of bytes. The DCAM driver is stopped. |
Action |
Modify the MAXBLK parameter specifications for both nodes so that the value in the local DRIVER statement is equal to or greater than the value in the LINK statement of the partner node. |
NETD013E: | GATEWAY ROUTINE r-name LOAD ERROR hex |
Explanation |
A gateway routine r-name required for the gateway link could not be loaded. The node terminates. |
Action |
Check JCL and Entire Net-Work libraries. |
NETD014E: | REQUIRED PARAMETER xxx MISSING |
Explanation |
A required parameter xxx was not specified. The node terminates. |
Action |
Correct the parameter and start again. |
NETD015I: | CONNECT DATA hex-data RECEIVED |
Explanation |
The CONNECT data sent from the partner node does not match that defined by LOGUDATA. The connection request is rejected. |
Action |
No action is required. This message is informational only. |
NETD016E: | ERROR rc IN ADAIOR FUNCTION fc |
Explanation |
ADAIOR returned the error rc for function call with code fc. The ADAIOR function is skipped. |
Action |
Contact your Software AG technical support representative. |
NETD017I: | LOGON REJECTED FROM APPLICATION partner ON PROCESSOR |
Explanation |
A connection request cannot be accepted, either because the link is not in a proper state, or the logon user data does not match that defined in the LINK statement parameters (see also message NETD015). |
Action |
No action is required. This message is informational only. |
NETD018I: | decnum MORE-DATA SEGMENTS xxxxxxxx |
Explanation |
This message is logged when a link is terminated and the More Data Function was used for the line driver. The value decnum specifies the number of extra segments, and xxxxxxxx specifies received or sent. |
Action |
No action is required. This message is informational only. |
NETD020E: | UNRECOVERABLE ERROR IN CONTINGENCY: xxxxxxxxxxxxxx |
Explanation |
This message indicates a program error in the DCAM line driver during an unsolicited logon. The logon is rejected. |
Action |
Contact your Software AG technical support representative. |
NETD021W: | IGNORED DCAM WARNING: CONTRADICTION ENCODING |
Explanation |
A message was received warning that the encoding/decoding have contradictions, probably because the SYSCODE parameter is different between the two communication partners. |
Action |
Restart Entire Net-Work with the correct SYSCODE set. |
NETD023I: | DCAM DRIVER STOPPED ON xxxxxx REQUEST |
Explanation |
The DCAM application was closed by an asynchronous external request (via COMEND contingency). The type of request xxxxxx is OPERATOR if the application was forced to terminate by operator interaction (/BCLOSE command, for example) or DCAM-SYS if a shutdown of the DCAM communication system was in progress. Entire Net-Work stops all DCAM activities. After DCAM is brought up again, the DCAM driver can be reactivated with the START operator command. |
Action |
No action is required. This message is informational only. |
NETD024I: | DCAM CLOSE COMPLETE |
Explanation |
The DCAM application was closed by an Entire Net-Work main program request. |
Action |
No action is required. This message is informational only. |
NETD027W: | MAXIMUM MESSAGE LENGTH nn REDUCED TO nn ON xxxxxxxx |
Explanation |
The value specified for the MAXBLK parameter in the LINK statement is greater than the value specified for the MAXTSDU parameter in the /BCIN command or the XPRO macro. The maximum message length accepted is reduced to the value specified for MAXTSDU. Messages larger than this will be lost. |
Action |
Increase the MAXTSDU specification if the larger block size is needed; otherwise, specify a smaller value for MAXBLK. |
NETD036I: | STAGNATION ON LINK linkname: dddd MESSAGES HANDLED |
Explanation |
This message is printed when a return code on a DCAM YSEND macro indicates that a DCAM congestion occurred on the link identified in the message (linkname). The number of outgoing messages that queued up on the link is also given in the message (dddd). All messages have been sent after the GO signal was received. |
Action |
If this message occurs frequently, increase the DCAM and BCAM internal buffers or the MAXBLK parameter value, as needed. |