|
|
|
The following messages are produced by the CA-GSS Common Service.
Reason:
This node requested a CNOS operation with nodename. The request was accepted without negotiation.
Action:
No action is required.
Reason:
This node requested a CNOS operation with nodename. The request was negotiated successfully.
Action:
No action is required.
Reason:
This node requested a CNOS operation with nodename. The operation failed because the target node is not connected to VTAM.
Action:
No action is required.
Reason:
This node requested a CNOS operation with nodename. The operation failed.
Action:
No action is required.
Reason:
record is the text read from the GOALNET initialization parameter. It contains network definition data.
Action:
No action is required.
Reason:
A new GoalNet log is attempting to open. However, the GoalNet log function is already active, so the new log does not open.
Action:
No action is required.
Reason:
The current GoalNet log is terminating due to a request.
Action:
No action is required.
Reason:
The current GoalNet log is terminating due to a failure of the logging IMOD, $GNET_LOG. GoalNet messages will now be logged to the main ISERVE log, ISRVLOG.
Action:
Restart the GoalNet log through the ISERVE command GOALNET START LOG.
Reason:
A CNOS request has been received from another node and has been processed.
Identifies the logical unit making the CNOS request.
Displays the name of the logmode table on which the CNOS request is based.
Displays the desired number of sessions.
Displays the minimum contention-winner sessions desired.
Displays the minimum contention-loser sessions desired.
Displays the hexadecimal flags passed with the request.
Action:
No action is required.
Reason:
The GoalNet link with node nodename has been lost. No further communications with that node are possible.
Action:
Make sure that the node is available. Issue the ISERVE command GOALNET START nodename to reactivate the link.
Reason:
Communication between GoalNet node ournode and node has been lost.
Action:
Make sure that the node is available. Issue the ISERVE command GOALNET START nodename to reactivate the link.
Reason:
Communication between GoalNet node ournode and node has been established.
Action:
No action is required.
Reason:
Communications have been established with node.
Action:
No action is required.
Reason:
An IMOD has been notified by VTAM that its conversation with nodename has been terminated. The IMOD ends. Communication with nodename is terminated.
Action:
Make sure that the affected node is available and issue the ISERVE command GOALNET START nodename to reestablish communication.
Reason:
A receiver IMOD has received a request to execute the IMOD named imod. The request was from node callernode and was made by an execution of IMOD caller, with an IMOD ID of callerid. recs is the total number of records to be passed across the network, and bytes is the total number of bytes to be passed across the network.
Action:
No action is required.
Reason:
All records pertaining to the current request (see message GNT116) have been successfully received. The request is now ready for execution.
Action:
No action is required.
Reason:
The IMOD caller, with an IMOD ID of callerid, has begun to transmit the results of a prior request to execute the IMOD called, with IMOD ID calledid, at node node. The called IMOD was executed at node node. prty is the transmission priority, recs is the total number of records to be passed across the network, and bytes is the total number of bytes to be passed across the network.
Action:
No action is required.
Reason:
All records pertaining to the current request (see message GNT118) have been successfully received. The results are now ready to be returned to the requestor.
Action:
No action is required.
Reason:
An invalid record has been received on GoalNet. data is the record received.
Action:
If other errors or unwanted conditions occur, capture the log and any pertinent data.
Reason:
The transmitter IMOD attempted to allocate a conversation with nodename, but the allocation failed.
Action:
Determine why VTAM refused the request to start a conversation.
Reason:
A transmitter IMOD has received a request to execute the IMOD imod at remote node node. The request was from node node and was made by an execution of IMOD caller, with an IMOD ID of callerid. Return notification is through stack number stack. recs is the total number of records to be passed across the network, and bytes is the total number of bytes to be passed across the network.
Action:
No action is required.
Reason:
All records pertaining to the current request (see message GNT124) have been successfully transmitted.
Action:
No action is required.
Reason:
The IMOD caller, with an IMOD ID of callerid, has begun to transmit the results of a prior request to execute the IMOD called, with IMOD ID calledid, at node node. The request was originated by an execution of IMOD caller, with an IMOD ID of callerid. prty is the transmission priority, recs is the total number of records to be passed across the network, and bytes is the total number of bytes to be passed across the network.
Action:
No action is required.
Reason:
All records pertaining to the current request (see message GNT126) have been successfully transmitted. The results are now ready to be returned to the requestor.
Action:
No action is required.
Reason:
Following completion of a request to execute an IMOD, it was found that the results could not be returned to the requestor because the conversation was lost. The results are discarded.
Action:
No action is required.
Reason:
A request has been received from a node that is not defined to this node. The request is rejected. luname identifies the logical unit that initiated the request.
Action:
Ensure that the GoalNet definition for this node includes all desired partners.
Reason:
A request to execute an IMOD has been received from a node that is flagged as stopped. The request is refused. node is the requesting node name.
Action:
Determine if the node is stopped due to an operator GOALNET STOP command. The node may be restarted with the GOALNET START command.
Reason:
During transmission of a request to execute an IMOD, the requesting node indicated that it was terminating communications. The incomplete request is discarded. node is the name of the requestor.
Action:
No action is required.
Reason:
A VTAM operation terminated with an error. name is the name of the IMOD, and inst is the instruction number within the IMOD. req.qual indicates the request type and qualifier being executed at the time of error.
Action:
This message is probably the result of a fault in the VTAM environment and will be an isolated occurrence. Look up the primary and secondary return codes (rcpri and rcsec) in VTAM Programming for LU 6.2 (or the equivalent manual for the version of VTAM that you are using).
Reason:
As a result of a GOALNET TERMINATE command, this node has severed its connections to all other nodes.
Action:
No action is required.
Reason:
VTAM is shutting down. GoalNet participation is ending.
Action:
Restart VTAM and then GoalNet.
Reason:
VTAM is shutting down in response to a HALT QUICK command, or a VARY INACT command has been issued against the logical unit assigned to CA‑GSS/ISERVE. GoalNet participation is ending.
Action:
Restart VTAM or activate CA‑GSS/ISERVE’s application ID and then start GoalNet.
Reason:
VTAM has terminated due to operator cancel of an abend condition. GoalNet participation is ending.
Action:
Restart VTAM and then GoalNet.
Reason:
VTAM has terminated for unknown reasons.
Action:
Restart VTAM and then GoalNet.
Reason:
The specified GoalNet node is not available for use.
Action:
If communication is desired with this node, reactivate it with the GOALNET START command.
Reason:
record is the data portion of a LOGON initialization parameter or descriptive data.
Action:
No action is required.
Reason:
The immediately preceding GNT139 message displays a duplicate specification of the LOGON LUNAME initialization parameter. The first specification is retained, and the duplicate is ignored.
Action:
Remove the unwanted definition from the initialization parameters.
Reason:
The value specified for the LUNAME in the immediately preceding GNT139 message is not a syntactically valid LUNAME.
Action:
Correct the LUNAME specification in the initialization parameters and restart.
Reason:
The value specified for the password in the immediately preceding GNT139 message is not a syntactically valid password.
Note: For security reasons, the password field in the GNT139 has been replaced with XXXX. You will need to examine the initialization parameters’ source to determine the problem with the password.
Action:
Correct the password specification in the initialization parameters and restart.
Reason:
The indicated value of luname has been assigned as the appropriate LUNAME for communications with terminals desiring to logon. Note that this message does not indicate that VTAM will accept the request to use this LUNAME.
Action:
No action is required.
Reason:
The immediately preceding GNT139 message displays a LOGON initialization parameter record whose first word is not a recognized LOGON sub-verb.
Action:
Correct or remove the invalid record.
Reason:
Although you have defined applications for terminal logon requests, you have not defined an LUNAME to be used for communication.
Action:
If terminal logons are to be accepted, supply an appropriate LUNAME specification and restart.
Reason:
An operator entered a GOALNET TERMINATE command and all nodes have been disconnected and the VTAM ACB closed.
Action:
GoalNet functions are unavailable until a GOALNET RESTART command is entered.
Reason:
During operation of GoalNet, its connection to VTAM was lost. This may be due to VTAM failure or a VARY INACT against GoalNet’s application ID. At GoalNet initialization, RESTART WTOR was specified.
Action:
The following actions can be taken:
Issued after VTAM is restarted or the application ID has been reactivated, this option will cause GoalNet to reinitialize itself.
Issued prior to VTAM being restarted, this reply will eliminate the WTOR and cause GoalNet to await the issuance of message IST020 by VTAM. At that time, an automatic GoalNet restart will be attempted. AUTO is not an appropriate reply if VTAM is not being restarted or if VTAM restarting is already complete.
This option will eliminate the WTOR and no further action will be taken by GoalNet. Following restoration of the VTAM environment, you will need to issue a GOALNET RESTART command to CA‑GSS.
Reason:
An operator entered a reply in response to GNT147 but it was invalid. The GNT147 message is redisplayed.
Action:
Issue a reply to the redisplayed GNT147 message.
Reason:
The initialization call to the TCP/IP interface failed for the indicated return code. This failure may occur because the system TCP/IP task has not been started, and CA‑GSS is attempting to connect with it. This failure could also be the result of an invalid port address or job name that is specified on the CA‑GSS TCP/IP initialization statements.
Action:
Make sure that the system TCP/IP task has been started. Also make sure that any port address or job name that is specified on the initialization statements is valid.
Reason:
The interface to TCP/IP has successfully initialized.
Action:
No action is required.
Reason:
The $TCP_TIMER IMOD could not be started.
Action:
Examine ISRVLOG and GNETLOG for additional information on the failure.
Reason:
The $TCP_TIMER IMOD has stopped running or abended.
Action:
Examine ISRVLOG and GNETLOG for additional information.
Reason:
CA-GSS failed to obtain a valid host ID for the active TCP/IP task.
Action:
Ensure the TCP/IP proc has been started on your system.
Reason:
CA-GSS successfully connected to the TCP/IP host and obtained the host ID.
Action:
No action is required.
Reason:
Informational message indicating that CA-GSS is purging requests for IMODs that have completed.
Action:
No action is required.
Reason:
An attempt was made to transmit a request to a node with a stopped path.
Action:
Issue the NET START command for the indicated path and retry the request.
Reason:
Informational message indicating a node has started.
Action:
No action is required.
Reason:
CA-GSS received an inbound request from a remote GMF node. An ACK will be sent back to the originating node.
Action:
No action is required.
Reason:
A locally initiated request has received a reply from the indicated gmfname.
Action:
No action is required.
Reason:
An unsolicited request was received from the indicated gmfname.
Action:
No action is required.
Reason:
The indicated imodname failed to spawn. Any associated message text was lost.
Action:
Examine ISRVLOG and GNTLOG for additional diagnostic information.
Reason:
The indicated imodname was activated and passed any associated message text for the request.
Action:
No action is required.
Reason:
An attempt to transmit to gmfname failed.
Action:
Examine ISRVLOG and GNTLOG for additional diagnostic information.
Reason:
Negative acknowledgement received from gmfname.
Action:
No action is required.
Reason:
An unsolicited reply was received from gmfname.
Action:
Examine ISRVLOG and GNTLOG for additional diagnostic information.
Reason:
CA-GSS acknowledged an incoming message from a remote CA-GSS system.
Action:
No action is required.
Reason:
An out-of-sequence ACK or NAK was received from the remote system. Message is logged and request is ignored.
Action:
No action is required.
Reason:
The READ time-out value was exceeded prior to a response from the remote CA‑GSS system.
Action:
Verify the remote system is active.
Reason:
ACK response has been received from the remote CA-GSS system prior to the expiration of the ACK timer.
Action:
No action is required.
Reason:
A response was received from the remote CA-GSS system prior to the expiration of the READ timer.
Action:
No action is required.
Reason:
The time-out ACK timer was set following a transmit to a remote CA-GSS system.
Action:
No action is required.
Reason:
The time-out READ timer was set following a transmit to a remote CA-GSS system.
Action:
No action is required.
Reason:
CA-GSS is routing a request from srcgname to targname.
Action:
No action is required.
Reason:
The TCP/IP interface failed to initialize.
Action:
Verify that the TCP/IP started task is active and that the CA-GSS port is available.
Reason:
The TCP/IP interface is down. CA-GSS will attempt to retry the failed operation.
Action:
No action is required.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |