RPL RTNCD and FDB2 return code combinations

This section describes all the RTNCD-FDB2 combinations that can be set in an RPL when it is posted complete. See z/OS Communications Server: SNA Programming for information about return code posting.

The operation has been completed normally or the request has been accepted.

You issued INQUIRE, INTRPRET, or OPNDST OPTCD=RESTORE and specified an input work area that is too small. VTAM® has placed the required length (in bytes) in the RPL's RECLEN field (for INQUIRE) or ARECLEN (for INTRPRET). No data has been placed in the work area.

Obtain a work area that is at least as long as the value set in RECLEN or ARECLEN, place the length in the AREALEN field (for INQUIRE) or AAREALN (for INTRPRET), and reissue INQUIRE or INTRPRET.

A RECEIVE OPTCD=NQ was issued and there was no input of the specified RTYPE available to satisfy the macroinstruction, or a RCVCMD OPTCD=NQ was issued and there was no input available to satisfy the macroinstruction.

The problem might be due to an incorrectly set NAME field in the NIB, an CID that is not valid in the NIB or RPL, a failure on the part of the system programmer to create the appropriate entry during VTAM definition, or a VARY command issued by the VTAM operator that deactivated the entry.

An OPNDST OPTCD=ACQUIRE or SIMLOGON OPTCD=NQ failed for one of the following reasons: the requested logical unit is at its session limit or is not enabled for sessions in which it is to be the SLU. See z/OS Communications Server: SNA Programming for a description of OPNDST and SIMLOGON.

A SIMLOGON OPTCD=Q failed because the requested logical unit is at its session limit and at least one of its current sessions is with the application program that issued the SIMLOGON.

A CLSDST OPTCD=PASS failed for one of two reasons. There is already a queued session between the logical unit being passed and the target primary logical unit, or you attempted to initiate or pass the session to the same PLU APPL.

You attempted to accept a session and indicated that your request should be rejected if no pending active session is waiting to be accepted (OPTCD=NQ). The request is rejected because no CINIT is queued for your application program.

An OPNDST OPTCD=RESTORE failed because the sessions that are requested are not pending recovery. None of the sessions specified by the NIBLIST are restored.

You issued INQUIRE OPTCD=APPSTAT to check an application program's ability to establish sessions. The application program is in an inactive, non-connectable state because the VTAM operator deactivated it. Therefore, the application program is not available for sessions.

Some type of error might have occurred on an APPCCMD macroinstruction. For further problem determination, refer to the primary and secondary return codes in the RPL extension. See the z/OS Communications Server: SNA Programmer's LU 6.2 Reference for further information.

You have issued INQUIRE PERSESS and specified an input work area that is too small. VTAM fills the work area with as much information as possible and places the length used in the RPL's RECLEN. The INQUIRE must be reissued to recover the remainder of the information.

An exception request has been received. The reason for the exception is contained in the RPL's SSENSEI, SSENSMI, and USENSEI fields. If a negative response has not been sent to a request of this chain and if this request (the exception request) requires a response, move the input sense fields to the output sense fields and send a negative response. All requests in the current chain that have been received by the application program should be discarded. If the current request did not end the chain, issue RECEIVE macroinstructions with OPTCD=TRUNC and AREALEN=0 until CHAIN=LAST or CONTROL=CANCEL is received. No responses should be sent for any request in the rest of the chain.

The logical unit (or some other node in the network) has sent a response indicating that an exception condition was detected for one of the requests that the application program sent on this session. The SEQNO field indicates the sequence number of the request to which the negative response applies. The SSENSEI, SSENSMI, and USENSEI fields indicate the reason for the exception condition.

See z/OS Communications Server: SNA Programming for more information on the SEQNO field, and the SSENSEI, SSENSMI, and USENSEI fields.

If the request with which the negative response is associated is part of an incomplete chain currently being transmitted to the logical unit, the application program should terminate the chain by issuing a SEND STYPE=REQ, CONTROL=DATA, CHAIN=LAST or a SEND STYPE=REQ, CONTROL=CANCEL to indicate that the logical unit can stop discarding the requests it is receiving. Refer to z/OS Communications Server: SNA Programming for information about the use of STSN and CLEAR to alter sequence numbers. Also see the discussion of (RTNCD,FDB2)=(12,13) in this section.

VTAM is temporarily unable to secure enough storage to process the request. The request can usually be reissued (with EXECRPL, for example). For applications running at a priority near to or higher than VTAM's priority, the application should wait a brief time before trying this again.

In certain cases, the macroinstruction processing has not gotten far enough to have done significant work, and the request can be reissued. In other cases, the processing might have gone beyond some irreversible point before failing; as a result, the request cannot simply be reissued. For example, if the LOGON exit routine has been scheduled with a CINIT request and OPNDST OPTCD=ACCEPT is issued, the OPNDST operation can fail before responding to the CINIT, in which case the OPNDST can simply be reissued. If the response to CINIT had been sent, however, and then storage could not be obtained, the OPNDST request could not be reissued as there would no longer be a CINIT to accept. In this case, the application program might wish to initiate another session between itself and the LU, perhaps by using SIMLOGON. These two cases can be distinguished by a bit in the NIB; when the OPNDST OPTCD=ACCEPT is posted, NIBNACLQ is 1 if the response to CINIT is sent; otherwise it is 0.

This RECEIVE operation has been canceled by a RESETSR macroinstruction issued by another part of your application program.

The request has been canceled because the session was terminated. Session termination always cancels any pending requests for the session, and returns this return code in the RPL. See z/OS Communications Server: SNA Programming for a list of the possible causes of session termination.

This return code is also used when an OPNDST OPTCD=(ACCEPT,SPEC,Q) is canceled by CLSDST.

While the RPL-based request was being processed, a CLEAR request was sent or received on the session. This stops all data flow and cancels all pending communication requests on the session. The CLEAR request might have been sent by your application program (SESSIONC macroinstruction), or the request might have been sent on behalf of your application program by VTAM. The CLEAR request might also have been sent from the other end of the session.

A series of chained requests was being sent to the logical unit and a negative response was returned for one of them. All subsequent SEND macroinstructions for that chain are posted complete with this return code; however, for each such SEND, the associated request unit is sent on the session to the session partner where it should be discarded.

The POA issued a SENDCMD after it reached its queue limit (POAQLIM on the APPL definition statement). Subsequent SENDCMDs complete with this return code until you receive all of the messages in the queue. You can empty the message queue by issuing RCVCMD OPTCD=NQ (no queue) until an RCVCMD completes with a return code and feedback of X'0006'. A SENDCMD now returns successfully.

The RPL system-sense (SSENSEI), the system-sense modifier (SSENSMI), and the user-sense (USENSEI) can contain a more detailed explanation of the failure.

The SSENSEI, SSENSMI, and USENSEI fields are set; these fields are described in SNA sense field values for RPL-based macroinstructions.

You attempted to initiate a session and one of the logical units in the requested session is inhibited. For example, a VTAM application program is inhibited for sessions if it issues SETLOGON OPTCD=QUIESCE or has never issued SETLOGON OPTCD=START. Refer to z/OS Communications Server: SNA Programming for more information.

The VTAM operator has issued a HALT command. Depending on the type of HALT, certain macroinstructions can no longer be issued by your application program. Refer to z/OS Communications Server: SNA Programming for more information.

The communication operation has been canceled because the VTAM operator deactivated a necessary portion of the path while the macroinstruction was being processed. If a LOSTERM exit routine is available, it has been scheduled. You can no longer communicate with the LU, and you should issue CLSDST to terminate its session with your application program.

The logical unit has sent an unconditional Terminate request or a character-coded logoff that is a request for unconditional session-termination. No further communication on the session is possible. CLSDST must be issued.

An error occurred in VTAM itself. No further attempts to establish or terminate a session with the logical unit should be made.

The association between VTAM and your application program (ACB) that was established with OPEN has been broken; the ACB is in the process of being closed. This might have occurred because you have elsewhere issued a CLOSE that has not yet completed, or it might have occurred because VTAM has become inactive, or a VARY INACT was issued for your application program.

VTAM has abnormally terminated a request because of an error detected while processing the request or because of an error in the associated session, task, or address space (for example, an abend). See z/OS Communications Server: SNA Programming for more information about error isolation and recovery.

Previously VTAM had received an RU; the application program did not have an appropriate EXLST exit routine or outstanding RECEIVE for the RU and there was no buffer space left for VTAM to queue the RU. Under these circumstances, VTAM discards that RU and any other RUs queued for the session and schedules the LOSTERM exit routine (if there is one) with reason code 36. If appropriate for the TS Profile for this session, a Clear is sent to the session partner. In all cases, the end of the session that experienced the buffer shortage is put into data-traffic-reset state (at least momentarily). Any SEND or RECEIVE issued while the session is in this state is rejected with (RTNCD,FDB2)=(X'10',X'0F'). This mode of operation continues until a Start Data Traffic response is processed (or until the Clear function completes, if SDT is not appropriate for the TS profile).

A negative response was sent by a logical unit in reply to a Start Data Traffic (SDT) request. The OPNDST was not completed successfully. The SSENSEI, SSENSMI, and USENSEI fields are set; these fields are described in SNA sense field values for RPL-based macroinstructions.

A REQSESS, TERMSESS, or OPNSEC has failed. A sense code (SSENSEI, SSENSMI, and USENSEI field) is returned in the RPL for the failing macroinstruction.

An LU 6.2 application has tried to start an LU 6.2 session independent of VTAM. No pending sessions have been disturbed. This occurs when an OPNDST is issued with an LU 6.2 user-specified BIND.

An LU 6.2 application has tried to start an LU 6.2 session independent of VTAM. The pending session has been terminated. This occurs when the LOGMODE specified on an OPNDST resolves to an LU 6.2 BIND or when OPNSEC is issued for an LU 6.2 BIND.

An OPNDST or CLSDST has been issued for a pending LU 6.2 session. An APPCCMD CONTROL=OPRCNTL, QUALIFY=ACTSESS or QUALIFY=DACTSESS macroinstruction must be issued for this session. See the z/OS Communications Server: SNA Programmer's LU 6.2 Reference for more information.

The application issues a SIMLOGON or OPNDST OPTCD=ACQUIRE macroinstruction using the application supplied dial-out function. The specified LU is nonswitched and the request failed.

You attempted to request encryption on a send, but session does not support encryption.

You attempted to use either the INQUIRE OPTCD=SESSNAME, SETLOGON OPTCD=GNAMEADD, SETLOGON OPTCD=GNAMEDEL, SETLOGON OPTCD=GNAMESUB, OPNDST, OPNSEC, or the CHANGE OPTCD=ENDAFFIN macroinstruction, but the coupling facility for this host is inaccessible.

VTAM attempted to SUSPEND an RPL request issued in either cross-memory mode or in synchronous SRB mode with OPTCD=KEEPSRB specified. The attempt failed.

VTAM attempted to RESUME an RPL request issued in either cross-memory mode or in synchronous SRB mode with OPTCD=KEEPSRB specified. The attempt failed. VTAM is unable to post the request complete. If the application has a LOSTERM exit, it will be scheduled with a reason code of 44.

For more information about the LOSTERM exit, see the z/OS Communications Server: SNA Programming. The RPL is now available for reuse.

A macroinstruction request required the use of an operating system service which is not supported by the active operating system level.

An error was encountered when attempting to invoke the security management program. The APPL definition statement for this application specifies VERIFY=REQD or VERIFY=OPTIONAL, indicating that the use of an installed security manager was required for APPC sessions by this application program. However, VTAM was unable to successfully invoke the security manager. The SETLOGON START macroinstruction is rejected.

The RPL contains a VSAM or other non-VTAM request code. No ECB has been posted and no RPL exit routine has been scheduled.

The RPL indicates that the ECB-EXIT field is being used as an EXIT field, but the RPL exit routine address in it is 0. No RPL exit routine has been scheduled.

The RPL indicates that the ECB-EXIT field is being used to point to an external ECB, but the address in the field is 0. No ECB has been posted.

CHECK was issued for an inactive RPL (an RPL that had been posted complete and for which CHECK has already been issued successfully). All RPL-based macroinstructions must use an inactive RPL. All CHECK macroinstructions, however, must use an active RPL; an RPL cannot be checked twice.

The RPL's ACB field does not contain the address of a valid ACB or the ACB is closed. This can mean that the ACB field of the RPL was incorrectly set or the ACB has been destroyed.

A RECEIVE has been issued with the RTYPE field set to NDFSYN, NDFASY, and RESP.

At the time this macroinstruction was executed, a CLSDST request was pending for the session. The CLSDST request takes priority, and the request that received this return code cannot be honored.

The RPLARG field or the NIBCID field does not contain a valid CID, or a valid CID was issued with the wrong ACB, or INTRPRET is being used for a cross-domain LU.

You might have inadvertently modified the field, initially failed to set it, or used the CID of a session that no longer exists.

Another possibility is that you violated the following rule: when placing a CID into the RPLARG field, always use the ARG keyword (ARG=(6), for example), and when placing an NIB address into the RPL's NIB field, always use the NIB keyword (for example, NIB=(6)). Because these two fields occupy the same 4 bytes in the RPL, VTAM can distinguish between an NIB address and a CID only through your use of the ARG or NIB keyword. Thus, the presence of this return code could mean that you placed an NIB address in the RPL with the ARG keyword, and VTAM has rejected your CID as not valid.

This feedback information is also used when a CID is specified for INTRPRET, and the LU implied by the CID is in another domain.

A request was issued that specified a work area address that is beyond the addressable range of your application program. Here a work area is defined to be any storage area addressed by an RPL operand, for example, the areas referenced by AREA and AAREA.

Check the work area address and work area length fields in the RPL for an incorrect setting. See the RPL macroinstruction description in z/OS Communications Server: SNA Programming to determine which fields must point to valid work areas for each macroinstruction.

If your application program resides in an authorized library, check for correct load module characteristics.

When an RPL-based macroinstruction is issued, VTAM sets the REQ field in the RPL to indicate the type of macroinstruction that is using the RPL. The presence of this return code indicates that you modified that code before the requested operation completed. To avoid this and other related errors, never modify an RPL while it is in use. Compare with VSAM request, (RTNCD,FDB2)=(X'14',X'00').

You attempted to issue one of the following macroinstructions in other than the session address space: RECEIVE OPTCD=SPEC, RESETSR, SEND, or SESSIONC (except request rejected response to BIND).

You attempted to send a response with the RESPOND field set to NFME and NRRN. A response must be identified as FME, RRN, or both; in effect, you have identified the response as neither.

You issued a SEND POST=SCHED, a SEND for an expedited data-flow-control request, or a SESSIONC macroinstruction before a previous macroinstruction of the same type had been completed. Only one macroinstruction of the three preceding types can be outstanding on a session at a time. After the previous macroinstruction has been completed, this macroinstruction can be reissued.

You modified the bits in the CONTROL field, or you used a CONTROL value for a SESSIONC macroinstruction that was not BIND, RQR, SDT, CLEAR, STSN, or SWITCH.

You attempted to communicate on a session for which no SDT request had been sent or for which a CLEAR is in progress. For certain TS profiles, until an SDT request/response exchange has occurred on the session, no traffic flow is possible; only SDT, Set and Test Sequence Numbers (STSN), Request Recovery (RQR), and Clear requests can be exchanged. Every time a Clear request is sent on a session, a new SDT request might be required before traffic flow can resume (this depends upon the transmission services profile used). For further information, refer to z/OS Communications Server: SNA Programming.

STYPE=RESP has been specified for a SESSIONC CONTROL=CLEAR or a SESSIONC CONTROL=RQR macroinstruction. Only STYPE=REQ is valid. Also, if the NIB used to establish the session specified SDT=SYSTEM, then STYPE=RESP is not valid for SESSIONC CONTROL=SDT.

The number of outstanding SEND POST=RESP macroinstructions for a session exceeds the RESPLIM value set in the NIB used to establish the session.

The RPL specified by your LU type 0 3270 SEND macroinstruction had one or more of the following fields not valid: STYPE, RESPOND, CHAIN, or CONTROL. See z/OS Communications Server: SNA Programming for more information about exception conditions.

If the RPL was last used for a RECEIVE for the 3270, check the RESPOND field first; you might have failed to reset the field following the RECEIVE (RECEIVE sets the RESPOND field to (NEX,NFME,NRRN) in this case).

For more information, refer to z/OS Communications Server: SNA Programming.

Refer to z/OS Communications Server: SNA Programming for more information.

You issued an INTRPRET macroinstruction; VTAM has located the appropriate entry in the interpret table, and found that the system programmer has specified a logon-interpret exit routine to do the interpret function. That routine, however, has not been loaded.

After your application program has been tested and debugged and you have eliminated the possibility of the three situations listed above, you can assume that the terminal operator or program that initiated the logon must have passed an invalid logon sequence to your application program.

You issued an INQUIRE, OPNDST, SIMLOGON, REQSESS, or CLSDST OPTCD=PASS macroinstruction. Either the NIB for this request specified a logon mode name that could not be found in the logon mode table for the logical unit named in that NIB, or the SSCP discovered that cryptography had been specified for the requested session, but at least one of the logical units in the requested session did not support cryptography.

Refer to z/OS Communications Server: SNA Programming for a description of the INQUIRE macroinstruction.

Assuming that the system programmer properly defined the entry in the VTAM configuration tables for the logical unit, you have probably: (1) failed to set a valid symbolic name in the NIB's NAME field or (2) correctly issued INQUIRE OPTCD=SESSPARM or INQUIRE OPTCD=DEVCHAR but the session has been terminated.

You issued an INTRPRET macroinstruction, but there is no interpret table for the logical unit. The system programmer might have failed to include an interpret table for this logical unit during the VTAM definition process or the logical unit might be in another domain.

You issued OPNDST OPTCD=ACCEPT without setting the NIB's LISTEND field to YES, or you specified a NIB list in which more than one NIB indicated PROC=NEGBIND.

The OPNDST or INQUIRE request fails because bits in the OPTCD field have been incorrectly set. From the OPNDST and the INQUIRE option code settings, you must specify only one value for the mutually exclusive sets of option codes. Because you cannot cause the field to be incorrectly set by using VTAM macroinstructions, you might have inadvertently modified the OPTCD field with assembler instructions.

The OPNDST, CLSDST, SIMLOGON, or REQSESS failed because the bits in the RPL's OPTCD or AAREA field were found to be not valid.

If an OPNDST or SIMLOGON failed, the particular bits that have been incorrectly set are those that form the CONANY-CONALL option code. This return code does not mean that the CONANY option was erroneously used in place of CONALL, or vice versa; it means that neither CONALL nor CONANY is indicated in the OPTCD field. Because you cannot cause the field to be incorrectly set in this manner by using VTAM macroinstructions, you might have inadvertently modified the OPTCD field with assembler instructions.

If a REQSESS failed, either OPTCD=NQ was not specified or the AAREA field of the RPL was not set to zero.

If a CLSDST failed, OPTCD=SENSE was specified and a zero sense was provided in the SSENSEO, SSENSMO, USENSEO fields of the RPL. A zero sense is not permitted for CLSDST OPTCD=SENSE.

The request failed because there is no NIB at the location indicated in the RPL's NIB field.

If you were using an NIB list, no sessions have been established.

• You attempted to acquire a logical unit (SIMLOGON or OPNDST), but the installation has denied you authorization to do so. The system programmer might have specified during VTAM definition that your application program is not authorized to acquire any logical units. If you are authorized to acquire logical units and you still receive this return code, this means that an authorization exit routine has been invoked and has determined that you cannot acquire the specific logical unit indicated in your request.
• You attempted to initiate a session, but the authorization exit routine has denied you authorization.
• You issued an INTRPRET macroinstruction; VTAM located the appropriate entry in the interpret table and found that the installation has specified an exit routine to convert the input sequence into an output sequence. That routine was loaded, but it failed to do the conversion.
• You issued one of the following macroinstructions in SRB mode without specifying the required task association: CLSDST, INQUIRE, INTRPRET, OPNDST, OPNSEC, REQSESS, RCVCMD, SENDCMD, SETLOGON, SIMLOGON, TERMSESS.

  Refer to z/OS Communications Server: SNA Programming for more information.

• An application that is not authorized to supply dial parameters attempted to supply dial parameters, or a PU that is not authorized to accept dial parameters attempted to accept dial parameters.

Refer to the z/OS Communications Server: SNA Resource Definition Reference for information about coding an application program major node (the AUTH operand of the APPL definition statement).

You issued an OPNDST or OPNSEC macroinstruction and failed to set the NIB's MODE field to RECORD.

CLSDST OPTCD=PASS is a function whose use is authorized by the installation. You attempted to use this function, but the installation has not authorized you to pass logical units to other primary logical units. This CLSDST macroinstruction should have been issued with RELEASE in effect, not PASS.

Refer to the z/OS Communications Server: SNA Resource Definition Reference for a description of the AUTH operand of the APPL definition statement.

You attempted to terminate a session with a logical unit that is not in session with your application program, or had no CINIT queued for your application program. This return code applies to CLSDST used with a logical unit's symbolic name.

You issued a SESSIONC macroinstruction to send a request rejected response to BIND, but the LU name field in the NIB does not match any BIND currently queued for the application program.

You issued an OPNSEC macroinstruction and a queued BIND could not be found for the LU name passed in the NIB.

Either you opened the ACB with its MACRF field set to NLOGON, or you issued SETLOGON OPTCD=QUIESCE and permanently closed the CINIT queue. Because you attempted to either open a CINIT queue that cannot be opened or close a CINIT queue that is closed, SETLOGON START, STOP, and QUIESCE are not valid.

You might have issued a SETLOGON OPTCD=PERSIST or NPERSIST with a PSTIMER value that is greater than the allowed value (86400 seconds).

You attempted to issue an RCVCMD macroinstruction while a previous RCVCMD was outstanding. The limit on outstanding RCVCMD requests is one.

Your application program is not authorized to issue the SENDCMD and RCVCMD macroinstructions, or your CNM application program attempted to send something other than a formatted Forward RU to the SSCP.

Refer to the z/OS Communications Server: SNA Resource Definition Reference for a description of the AUTH operand of the APPL definition statement.

In reply to a VTAM operator message, you issued a SENDCMD macroinstruction that contained a syntax error in the REPLY command.

The portion of VTAM that processes SENDCMD and RCVCMD macroinstructions is currently inactive for your application program, and the application program issued a SENDCMD or RCVCMD macroinstruction. The request cannot be processed because an ACB has not been opened for the portion of the application program that issued the SENDCMD or RCVCMD, or because a final CLOSE has been issued for this ACB but has not yet completed.

Your application program is in the process of closing its ACB, and you (1) issued a SENDCMD macroinstruction for a command other than REPLY or (2) issued a RCVCMD OPTCD=Q and there were no VTAM messages available to satisfy the request.

You attempted to send a VTAM operator command to VTAM using the SENDCMD macroinstruction; however, the command was not recognized by VTAM, or it was a command (START or HALT) that cannot be sent by the application program.

You issued a SEND macroinstruction when using a CNM application program and you have specified a parameter that is not valid.

You attempted to issue an OPNSEC PROC=NEGBIND to a non-negotiable BIND request. A request-rejected response to the BIND is sent with a sense code indicating resource unavailable (X'08010000').

You specified negotiable BIND parameters on an OPNSEC macroinstruction that are not valid. A request rejected response to the BIND is sent with a sense code indicating resource unavailable (X'0801000').

You specified a negotiable BIND response on OPNSEC that was greater than 256 bytes. A request rejected response to the BIND is sent with a sense code indicating resource unavailable (X'08010000').

You issued a SEND OPTCD=BUFFLST or a SEND OPTCD=LMPEO and the RU specified was not an FMD request unit.

You issued a SEND OPTCD=(BUFFLST,USERRH) in which multiple chains or multiple partial chains were specified in the buffer list. Only requests from a single chain might be specified in a buffer list.

You issued a SEND OPTCD=BUFFLST, and RECLEN did not contain a nonzero multiple of 16.

You specified a SESSIONC macroinstruction with OPTCD=USERRH.

A protocol error has occurred during the processing of a SIMLOGON or OPNDST macroinstruction.

SIMLOGON for a backup XRF request is processed by setting the "backup XRF session request" indicator in the INITIATE RU. This indicator is set based on the setting of the RPL bit indicating OPTCD=BACKUP (RPLBCKUP). If an Initiate is received specifying a backup XRF session and queue, it is rejected.

The RPL system-sense (SSENSEI), the system-sense modifier (SSENSMI), and the user-sense (USENSEI) can contain a more detailed explanation of the failure.

An application program issued a non-APPCCMD macroinstruction to establish an LU 6.2 session, or issued a non-APPCCMD macroinstruction against a current LU 6.2 session.

You specified SETLOGON OPTCD=NPERSIST or PERSIST for an application that is not capable of persistence.

A TERMSESS macroinstruction is issued for a pending active session without specifying OPTCD=UNBIND.

The length of an application-supplied dial parameter is not valid. Refer to z/OS Communications Server: SNA Programming for a description of the valid lengths.

Either a subfield is not supported, or a combination of subfields that is not valid is specified. Refer to z/OS Communications Server: SNA Programming for information about the valid subfields that can be specified.

The value of NIBASDPA is 0. The NIBASDP indicator was on, indicating that the application is providing dial parameters; however, no address for the control block was given. This probably resulted from the application program passing an address that is not valid to the NIB.

A SEND, RECEIVE, RESETSR, or SESSIONC request is rejected because it is issued for a session that is pending recovery. Use OPNDST OPTCD=RESTORE to restore the session and reissue the request.

You attempted to issue either SETLOGON OPTCD=GNAMEADD, SETLOGON OPTCD=GNAMESUB, or SETLOGON OPTCD=GNAMEDEL using a generic name that was the same as the application network name; they must be different.

You issued either CHANGE OPTCD=ENDAFFIN or INQUIRE OPTCD=SESSNAME, but the values specified in the NIB do not correspond to any known association.

The generic name has not been authorized using a security management product such as RACF®.

The application program is registered already as a generic resource, but with a different name.

You used SETLOGON OPTCD=GNAMEDEL to deregister generic resources but VTAM determined that generic mapping does not exist; no VTAM message is issued.

This generic resource exists already with another network identifier.

Two applications with the same application network name are simultaneously attempting to register a generic name.

All applications registering as generic resources must have the same APPC capabilities specified on their APPL statements.

VTAM owns the affinity. Your application cannot delete it.

You issued SETLOGON OPTCD=GNAMEADD to register generic resources. VTAM detected a conflict (the generic resource exists already as a USERVAR name).

Either a non-TSO application is attempting to use the generic name already being used by TSO, or TSO is attempting to use the generic name already being used by a non-TSO application.

PROC=STOKEN is specified and the NIBSTKN field contains an invalid STOKEN.

No LU name was passed on the SETLOGON OPTCD=START or on the REQSESS.

No RDTE was found that matched the LU name passed on the SETLOGON OPTCD=START or on the REQSESS.

An RDTE was found that matched the LU name passed on the SETLOGON OPTCD=START or on the REQSESS, but its characteristics or state was not appropriate.