NETV* - VTAM Line Driver Messages

An undocumented error has occurred.

Normal operations continue.

Contact your Software AG technical support representative.

An error has occurred during VTAM control block generation. R0 and RF are the values returned by VTAM.

The VTAM driver OPEN command fails.

Refer to the IBM VTAM documentation for a description of the error indicated by the values in R0/RF. Correct the problem and restart Entire Net-Work.

An error occurred while attempting to open the ACB. The hexadecimal value 'cc' is the ACBERFLG value; the text describes the error.

The VTAM driver OPEN command fails.

Refer to the IBM VTAM documentation for a description of the error indicated by ACBERFLG. Correct the problem and restart Entire Net-Work.

The function vector, which describes VTAM characteristics, could not be located.

Normal processing continues.

None.

The version of VTAM installed on this system does not support 31-bit applications.

The Entire Net-Work VTAM line driver will execute in AMODE=24.

Relink ADARUN with AMODE=24, or upgrade VTAM.

The version of VTAM installed on this system does not support Authorized Path.

Authorized Path is disabled, and processing continues.

None.

MVS - One or more of the libraries in the STEPLIB for Entire Net-Work is not authorized.

GCS - The virtual machine is not defined as authorized.

Authorized Path is disabled, and processing continues.

MVS - Authorize all STEPLIB libraries.

GCS - Define the virtual machine as authorized.

The SETLOGON START macro failed. RC and FB2 indicate the error.

No new connections can be accepted.

Refer to the IBM VTAM documentation for a description of the error as indicated by the values in RC/FB2. Correct the problem and restart Entire Net-Work.

The SETLOGON START macro completed successfully.

New connections can be accepted now.

None.

The module mmmmmmmm has been successfully loaded, and resides at address aaaaaaaa.

Normal processing continues.

None.

The module mmmmmmmm could not be loaded from the STEPLIB libraries.

The module is not used, and processing continues.

Make sure the module is in one of the STEPLIB libraries.

The system type for link llllllll indicates that the remote node does not support connections from this local node. All connections must be initiated from the remote node.

The connection fails, but processing continues.

Specify ACQ=No in the LINK statement.

The MODEENT= parameter for link llllllll specifies LUTYPE=6.3 and parallel sessions, but the log mode table specified in the LOGMODE= parameter does not contain an SNASVCMG entry.

The connection fails.

Add an SNASVCMG entry to the log mode table and reassemble it.

The MAXRU= parameter or the MAXBLK= parameter specifies a value larger than the maximum allowed. The value is reduced to the maximum.

Normal processing continues.

None.

The MAXRU= parameter or the MAXBLK= parameter specifies a value smaller than the minimum allowed. The value is increased to the minimum.

Normal processing continues.

None.

An attempt to allocate xxxxxxxx bytes of storage from the buffer pool or the private storage area has failed due to insufficient storage.

If the storage request is on behalf of a specific link, that link is disconnected. Otherwise, the Entire Net-Work VTAM line driver is closed.

Increase the size of the buffer pool or the amount of private storage allocated to Entire Net-Work.

VTAM has delivered a CINIT for LU=llllllll; cccccccc is the unique session identifier.

The connection is accepted if this LU matches a LINK statement LUNAME= or ASSOCLU= parameter, or if ACCEPTUI=YES was specified in the DRIVER statement. Otherwise, the connection is rejected. If the connection is accepted for an LU without a link, all control blocks are dynamically allocated.

None.

VTAM has delivered a Bind for LU=llllllll; cccccccc is the unique session identifier.

The connection is accepted. If this LU matches a LINK statement's LUNAME= or ASSOCLU= parameter, or if ACCEPTUI=YES was specified in the DRIVER statement. Otherwise, the connection is rejected. If the connection is accepted for an LU without a link, all control blocks are dynamically allocated.

None.

VTAM delivered a CINIT or Bind for LU=llllllll; cccccccc is the unique session identifier. The LU does not match any LUNAME= or ASSOCLU= parameter on any LINK statement, and ACCEPTUI=NO. The driver user exit indicated that the connection should be rejected.

The connection is rejected.

If a connection is desired, either code a LINK statement for this LU, or code ACCEPTUI=YES, or change the user exit.

VTAM has delivered an Unbind for the LU=llllllll; cccccccc is the unique session identifier; xx is the unbind code.

The session between NETVTAM and this LU that has the unique session identifier cccccccc is terminated.

None.

The VTAM request rrrrrrrr for LU=llllllll on the session with the unique session identifier cccccccc has failed.

All sessions between NETVTAM and this LU are terminated, and the connection is closed.

Refer to the IBM VTAM documentation for a description of the error indicated by the values in RC/FB2 and the sense data ssssssss.

The session between NETVTAM and LU=llllllll that has the unique session identifier cccccccc is being terminated.

All sessions between NETVTAM and this LU are terminated, and the connection is terminated.

Refer to the IBM VTAM documentation for a description of the Losterm code=xx.

VTAM has delivered an FMH7 RU with sense data=ssssssss for the LU=llllllll session with the unique identifier=cccccccc.

All sessions between NETVTAM and this LU are terminated, and the connection is terminated.

Refer to the IBM VTAM documentation for a description of sense data=ssssssss.

VTAM has delivered a Cleanup RU with Reason Code rr for the LU=llllllll session with the unique identifier cccccccc.

All sessions between NETVTAM and this LU are terminated and the connection is terminated.

Refer to the IBM VTAM documentation for a description of the Cleanup Reason Code=rr.

Connection initiation for link llllllll has failed because the link is considered a model link. By definition, a model link has an invalid LUNAME / APPLID.

Connection initiation fails, and normal processing continues.

Code ACQ=NO in the LINK statement.

An operator command specified an unknown link name.

Normal processing continues.

Reissue the operator command with a valid link name.

The operator command cccccccc.... has completed successfully.

Normal processing continues.

None.

The operator command cccccccc.... was rejected for one of the following reasons:

• The link name specified was not found.

• The command is not valid.

• The required operands were not entered (ALTER command).

• The driver is not in the proper state.

Normal processing continues.

Correct the operator command and reissue the command.

This is the first of a group of messages generated in response to the HELP operator command.

All valid operator commands are listed on the console. For more information, see the section Entire Net-Work Operator Commands.

None.

An ALTER operator command was entered with an invalid keyword or an invalid value. Some DRIVER statement and LINK statement parameters can be altered only when the driver or link is closed.

All parameters following the invalid keyword or value are ignored.

Either correct the keyword or value, or close the driver or link. Then reissue the command.

This is the first of a group of messages generated in response to the SHOW or STATS operator command.

This message is written to the console.

None.

One of a group of messages generated in response to the SHOW or STATS operator command. It shows the driver or link name, its state, and the number of messages sent/received.

This message is written to the console.

None.

One of a group of messages generated in response to the SHOW or STATS operator command. It shows the total number of bytes sent and received.

This message is written to the console.

None.

One of a group of messages generated in response to the SHOW or STATS operator command. It shows the number of receive RPLs, the total number of receives that have completed, and the number and percentage of receive overruns. An overrun occurs when all receive RPLs are inactive at the same time. A high percentage of overruns may indicate a need to increase the number of receive RPLs in use.

This message is written to the console.

None.

The LINK statement for link llllllll specifies encryption, but the version of VTAM installed on this system does not support it.

Link initialization fails.

Specify CRYPT=NO in the LINK statement. Restart Entire Net-Work.

The partner on link xxxxxxxx returned a positive response to a bind sent from NETVTAM. However, the RU size parameter, which determines the maximum RU size that VTAM can deliver to NETVTAM, was increased above the maximum that NETVTAM can accept.

The inbound connection request is rejected.

Either increase the value of the MAXRU= parameter in the DRIVER statement to allow NETVTAM to accept a larger RU size, or decrease the value of the RU parameter in the partner's communications software.

The logon exit was driven with a bind image named SNASVCMG, which is reserved for independent LUs and should never be received by the logon exit. The bind image was received for link xxxxxxxx.

The inbound connection request is rejected.

Define a logmode entry other that SNASVCMG in the partner's communications software.

For an OS/2 partner, this problem is caused by the parameter PARALLEL_SESSION_SUPPORT(YES) which is specified on the DEFINE_PARTNER_LU statement in the NDF file. Change this value to PARALLEL_SESSION_SUPPORT(NO).

A message from a partner was received by link xxxxxxxx. A flag in the message indicates that it was processed by a user exit before it was sent. Link xxxxxxxx does not have a user exit and therefore cannot process the message.

The message is discarded and the link is disconnected.

Either remove the user exit on the partner's side or code EXIT=exitname in the LINK statement on the local side.

A message was sent to link cccccccc, but VTAM shows that the message was not received by the link.

After the SNDTMOUT value is exceeded, the link is disconnected.

Verify the link s status.

The VTAM ACB has been closed for APPLID=aaaaaaaa.

The VTAM line driver is closed.

None.

An operator command specified a new value for RECVRPLS, and the storage needed to support the new value could not be obtained.

RECVRPLS is reset to its previous value.

Specify a lower value for RECVRPLS, i.e., a value for which there is sufficient available storage.

This message is generated in response to the VTAM link STATS operator command; llll is the link name, pppppppp is either blanks or the node name, nnnnnnnn is the APPLID name or the LU Name, and aaaaaaaa is the Associate LU Name.

None

This message is generated in response to the VTAM link STATS operator command; sssssssss is the link's current status (see message NET0117 for possible status), hh:mm:ss is time in hours, minutes, and seconds since the last request to display statistics.

None

This message is generated in response to the VTAM link STATS operator command.

None

This message is generated in response to the VTAM link STATS operator command; cccccccc is the LU CID, llllllll is the LU name, iiii Inb (Inbound) Outb (Outbound), nnnnnnnn is the number of bytes since last status reset, mmmmmmm is the total number of messages either sent or recv on this LU since last status reset, and ooooooo is the number of I/Os.

None

This message is generated in response to the VTAM link STATS operator command; nnnnnnnnn is the number of Kbytes per second.

None