The following tables give possible reasons for and corrective actions to solve some of the errors reported via SQLCODEs -933 and -30080 and via message ARI0197E. They include errors where either the IPCODE field or IPRCODE field contains a valid value for the error. Note that this is simply a list of errors which the user may encounter most frequently, and which are potentially correctable by the user. It is NOT a complete list of errors, and does not attempt to list errors which are not user-correctable.
If the error you encounter is reported using different fields, if the error
code is not found in the following tables, or if the corrective action
suggested in the tables does not solve the problem, refer to the CMS and CP
documentation of the CMSIUCV, HNDIUCV, IUCV or APPC/VM function named in the
FUNCTION field. See your system programmer and the bibliography to
determine the appropriate VM reference manual for your system. Review
the discussion in the previous section. Then use the values from the
error indicator fields (REG15, CC, IPRCODE, IPCODE, IPWHATRC and IPAUDIT) and
the CMS or CP documentation, to determine the cause of the error. The
error you encounter may not be user-correctable. In that case, make a
record of what went wrong and contact the designated IBM support group for
your installation.
Table 3. Errors Related to a Valid IPCODE
| IPCODE | Possible Reason | Corrective Action |
|---|---|---|
| x'0111' | No AVS sessions are available for connection. | Ask the AVS operator to activate another session and retry the connection. |
| x'0130' | Attempted connection with unlike database server while AR is running with SQLINIT P(SQLDS). | Issue SQLINIT with P(AUTO) or P(DRDA) to communicate in DRDA flows with unlike database. |
| x'0141' | Either the target server or VTAM has exceeded the maximum number of connections. | Try again when the system is not so busy. If the condition persists, then ask your system administrator to increase the maximum number of connections for either the target server or VTAM as appropriate. |
| x'0142' | TPN specified in user or system communications directory can not be found, or the server is not logged on. | Ensure that TPN specified for the target server is correct, and that the server is logged on. Reload the communication directory. |
| x'0160' | Invalid userid/password in user or system communication directory entry for the application server named. | Ensure all security information and passwords are valid, and that any mapping performed by AVS is correct. Reload the communication directory. |
| x'0210' | Database has severed the link. | Attempt to reconnect and continue processing. |
| x'0220' | Database has severed the link. | Attempt to reconnect and continue processing. |
| x'0301' | Invalid LU name specified in the user or system communication directory for the target server. | Ensure LU name in the communication directory is correct. Reload the communication directory. |
| x'0302' | Invalid mode name specified in user or system communication directory for the target server. | Ensure mode name in the communication directory is correct. Reload the communication directory. |
| x'0610' | The communications link has been severed. | Attempt to reconnect and continue processing. |
Table 4. Errors Related to a Valid IPRCODE
| IPRCODE | Possible Reason | Corrective Action |
|---|---|---|
| x'0B' | Invalid TPN or application server is not logged on. | Ensure TPN is correct and that the application server is logged on. |
| x'0D' | Your virtual machine already has the maximum number of connections. | Increase the MAXCONN parameter in the VM directory. |
| x'0E' | Your application server or intermediate server already has the maximum number of connections. | Try again when the system is not so busy. If the condition persists, then ask your system administrator to increase the maximum number of connections for either the target server or VTAM as appropriate. |
| x'0F' | Your machine is not authorized to connect to the resource. | Ensure that your AVS machine's VM directory and your application's server VM directory are set up correctly. |
| x'28' | Invalid locally known LU name. | Ensure LU name in the communication directory is correct. Reload the communication directory. |
| x'29' | Invalid mode name specified in user or system communication directory for the target application server. | Ensure mode name in the communication directory is correct. Reload the communication directory. |
| x'34' | There is no APPCPASS directory statement, and your connection attempted COMDIR resolution requiring either userid or password from the APPCPASS directory statement. | Ensure combination of communication directory and APPCPASS is valid. Reload communication directory. |