|
|
This chapter describes messages issued by the API Common Application Support Routines. These messages include T01AP000 through T01AP999.
Explanation A TPL function has failed and the user has called TERROR to format a description of the status at the time of the failure. See T01AP016D for details on interpreting this failure status description. Additional messages may follow to further describe the error.
Explanation An AOPEN call has failed. Read Cisco IOS for S/390 Assembler API Macro Reference for general information, and read "API Return Codes" in Cisco IOS for S/390 Unprefixed Messages and Codes for information about APCB diagnostic errors.
| function | The specified function. |
| module | The routine containing the function. |
| ret_code | The return code in register 15 returned by the function. |
| func_rsn | The function return code returned by the caller of the function. |
| err_code | The error code and diagnostic code from the APCBERRC and APCBDGNC fields |
Explanation A function has failed. The TPL for the function call is dumped after the message. Read the Cisco IOS for S/390 Assembler API Macro Reference for general information, and read "API Return Codes" in Cisco IOS for S/390 Unprefixed Messages and Codes for information about TPL diagnostic errors.
| function | Specified function. |
| mod_name | Routine containing the function. |
| ret_code | Return code in register 15 returned by the function. |
| func_reason | Function return code returned by the caller of the function. |
Explanation The attempt to load the specified module, mod_name, as single or double byte character set translation table failed.
Recommended Action Verify that the character set name has been created and is a valid table.
Explanation An invalid character set translation table (mod_name) has been specified or defined. This table may have been created incorrectly or was not created for the specified transopt (single or double).
Recommended Action Verify character set matches the translation mode.
Explanation A Cisco IOS for S/390 routine requested PDYNAL to perform the specified request. This involves a call to SVC 99 (dynamic allocation).
| request | Specified request, which can be one of these values:
ALLOCATE -- Allocate a DASD data set. SYSIN - Allocate a file to the JES jobstream reader. SYSOUT - Allocate a file to the JES output spool space. FREE - Free a DASD, SYSOUT, or SYSIN file. RENAME - Rename a DASD data set. MEMCHK - Check to see if a member exists in a PDS. MEMDEL - Delete a member in a PDS. MEMREN - Rename a member in a PDS. |
| error | DAIR error code returned from the SVC 99 call. |
| reason | Return code from the PDYNAL routine, which can be one of these:
0 - Success. 4 - Failure. 8 - Data security violation. C - IDYNAL bug. 10 - ICT error. |
| dataset_name | Data set name |
Recommended Action Examine the DAIR error code; it should direct your action. If the PDYNAL return code is other than 4, contact Customer Support. Save the WTP logs, JES logs and any dumps produced by the job.
Explanation A User Level Protocol (ULP) cannot allocate the memory space necessary for its work area.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Check the ACSNAP DD for any related dump. Use ACTEST to issue the psnap command to print all of Cisco IOS for S/390's storage into the ACSNAP DD. If there is a proliferation of the same kind of storage, a ptask may be allocating storage in a loop.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails again, bring Cisco IOS for S/390 down. Raise the region size on the Cisco IOS for S/390 job. Restart Cisco IOS for S/390 and retry the operation again. If the error recurs, contact Customer Support.
Explanation An internal call to DNR could not be made to resolve a host name, alias name, subsystem name, mail route, etc. A bad parameter list was passed to subroutine GETHBDNR. This indicates a programming error. The two passed parameters are dumped followed by 20 bytes of argument data.
Recommended Action Contact Customer Support. Save the output from the TCP base product job.
Explanation An internal DNR call failed for a request to resolve a host name, alias name, subsystem name, mail route, etc. The DPL for the DIRSRV request is dumped after the message. This can be a configuration, initialization, or user error.
If the message occurred at system startup it could be due to a temporary DNR/ACP initialization coordination problem.
Recommended Action This message, the Cisco IOS for S/390 Assembler API Macro Reference, the Cisco IOS for S/390 C Socket Programmer's Reference, and the DNR logs (as long as TRACE and INTERNALTRACE were set in configuration member DNRCFGxx) can be used to diagnose this problem. There may be related error messages in the WTP logs. The DPL contents and the messages in the DNR logs should guide your actions.
Explanation An invalid parameter was encountered during initialization of an application layer program.
Client or server initialization is terminated.
Recommended Action This error could be temporary or indicative of other problems within Cisco IOS for S/390. If the problems persists, the ACSNAP log should be checked for dumps. The WTP and JES log of the job should be saved. Contact Customer Support.
Explanation The GAT supplied on the SMTP statement was not found.
Recommended Action Add the GAT to the startup parameters.
Explanation The LRECL on the GAT for the SMTP statement was greater than 255.
Recommended Action Lower the LRECL below 255.
Explanation The outbound mailer program USMTP terminated with ABEND aaaaaaaa. The PSW at the time of the ABEND is PSW_value. R12 field csect_loc is the location of csect SMTPEX1.
Recommended Action The TCP base product takes a dump of the USMTP ptask and associated resources. Contact Customer Support. Save all output from the TCP base product job or started task.
Explanation Telnet server configuration specified API buffer parameters that were larger than the API provider could support. The API has negotiated lower numbers, followed by a hex dump of the TPL. module is the module issuing the message.
Explanation An error occurred during an API T-function operation. The program in error and the PTA address are listed in the T01AP016D message. module is the module issuing the message; address is the PTA address of the pseudo-task issuing the message.
Explanation This message is generated in a GETMAIN area in WTO format by the TERROR VERBATIM function. If an actual WTO is issued by the application program, this message may be seen on the system console (depending on the routing code(s) set in the message by the application program).
| job_name | JOB name. |
| step_name | STEP name. |
| appl_id | Application ID from APCBAPPL. |
| user_name | User name from TCEPUID. |
| tpl_addr | Address of TPL. |
| apcb_addr | Address of APCB. |
| listen_count | Listen count from SEPM, in hex. |
| sock_state | Socket state from SEPM, in hex. |
| ep_state | Endpoint state from SEPM, in hex. |
| state_code | Endpoint state, in English. |
| tpl_activ | TPL active flag. |
| tpl_flags | TPL flags. |
| rec_act_code | Recovery action code, in hex. |
| spec_err_code | Specific error code, in hex. |
| spec_code | Specific error code, in English. |
| diag_err_code | Diagnostic error code, in hex. |
| diag_code | Diagnostic error code in English. |
| ep_id | Endpoint ID. |
| ecb/exit_addr | ECB/EXIT routine address. |
| option_codes | TPL option codes, in hex. |
| parm_1 | Contents of TPLPARM1. |
| parm_2 | Contents of TPLPARM2. |
| parm_3 | Contents of TPLPARM3. |
| adbuf_addr | ADBUF buffer address, from TPLADBUF. |
| dabuf_addr | DABUF buffer address, from TPLDABUF. |
| opbuf_addr | OPBUF buffer address, from TPLOPBUF. |
| adbuf_len | ADBUF buffer length, from TPLAPLEN. |
| dabuf_len | DABUF buffer length, from TPLDALEN. |
| opbuf_len | OPBUF buffer length, from TPLOPLEN. |
Explanation A C program, like mail, has written a message to the log. text is the text of the message written to the log.
Explanation This is an internal logic error. A SERVICE statement with an invalid module name was accepted during startup, but the module could not be found.
Recommended Action Correct the module name in the configuration and contact technical support.
Explanation This is a normal startup message. Some services use the TCP base product API. The specified service issued the specified API session initialization macro. The service waits for the API macro to complete.
| service | The service statement defined in the ACPCFGxx member. |
| macro | An API session initialization macro: either AOPEN or TOPEN. |
Explanation This is a normal startup message. Some services use the TCP base product API. The specified service completed an API session initialization macro.
| service | The service statement defined in the ACPCFGxx member. |
| macro | An API session initialization macro: either AOPEN or TOPEN. |
Explanation EBCDIC/ASCII translate has failed to complete successfully.
| tbl_name | The character set table. |
| rc | The return code. |
| ec | The error code. |
This table describes the return and error codes:
| Diagnostic Code | Return Code | Reason |
|---|---|---|
| R15=08 | R0=0 | Invalid parmlist. |
| R15=08 | R0=1 | Invalid parmlist; no Character Set Specified. |
| R15=08 | R0=2 | Invalid parmlist; invalid source text address. |
| R15=08 | R0=3 | Invalid parmlist; invalid source text address. |
| R15=08 | R0=4 | Invalid parmlist; invalid source text length. |
| R15=08 | R0=5 | Invalid parmlist; invalid destination text address. |
| R15=08 | R0=6 | Invalid parmlist; invalid destination text length. |
| R15=08 | R0=7 | Invalid parmlist; pcore failed. |
| R15=08 | R0=8 | DBCS odd length; DBCS specified odd length. |
| R15=12 | R0=0 | Overflow |
| R15=12 | R0=1 | Invalid TRANOPT; operation type not specified. |
| R15=12 | R0=2 | Network direction; Input/Output not specified. |
| R15=12 | R0=3 | Wrong character set; invalid character set for request. |
| R15=12 | R0=4 | Invalid byte; invalid request for char set. |
| R15=12 | R0=5 | Bad Table specified; invalid table definition. |
| R15=12 | R0=6 | Bad DBCS header; DBCS table header invalid. |
| R15=12 | R0=7 | Mixed data error; error processing mixed data. |
| R15=12 | R0=8 | Unknown DBCS character; unknown DBCS character. |
Explanation A user-written exit routine has ABENDed.
Recommended Action Examine the system for dumps relating to this ABEND and correct the user exit.
|
|