|
|
This chapter describes messages issued by the Domain Name Resolver (DNR) task group. These messages are T01DN000 through T01DN999.
Explanation The DNR task group was successfully started and was able to process the primary and secondary configuration members without error.
The DNR task group failed to initialize due to at least one error. These are valid values for dec X'hex':
| 4 X'0004' | Processing of primary configuration member NRCFGxx failed. |
| 8 X'0008' | Getmain of NDSA storage (Subpool 241) failed. |
| 12 X'000C' | GPOL for TIMER or SEND thread DSRB failed. |
| 16 X'0010' | SCHED failed for TIMER or SEND thread. |
| 20 X'0014' | GPOL for RECEIVER thread DSRB failed. |
| 24 X'0018' | SCHED failed for RECEIVE thread. |
| 28 X'001C | One or more DNRxxxxx modules could not be loaded. |
Recommended Action Correct the problem that caused the task group initialization to fail. Then restart the DNR task group.
Explanation Module DNRICNFG could either not locate or successfully parse the primary configuration member DNRCFGxx (where xx is the primary configuration member name suffix).
Recommended Action Make sure that the primary configuration member exists and that the control statements have the proper syntax and valid values. This message should be preceded by a message from DNRICNFG (T01DN015E - T01DN021E) which explains the error in more detail.
Explanation The DNR task group was able to complete processing of directory requests and stop execution.
Explanation During DNR task group shutdown, the FREEMAIN of the NDSA failed. Register 15 following the FREEMAIN request is displayed in the message. The NDSA storage, which is in Subpool 241 (CSA), was not freed and cannot be recovered. The single parameter, x, indicates the contents of R15 after the FREEMAIN request
Recommended Action Contact Customer Support for assistance in resolving this problem.
Explanation During DNR task group shutdown, the FREEMAIN of the DNR ASVT failed. Register 15 following the FREEMAIN request is displayed in the message. The DNR ASVT storage, if not successfully freed, is freed by the operating system at task termination.
The single parameter, x, indicates the contents of register 15 after the FREEMAIN request.
The contents of R15 following the FREEMAIN request
Recommended Action Contact Customer Support for assistance in resolving this problem.
Explanation The Timer thread successfully initialized.
Explanation The Timer thread terminated normally.
Explanation A STIMER/TTIMER request failed due to a damaged CPU clock. Timing services for the task group cannot continue. The directory requests may or may not complete following this error.
Recommended Action Correct the problem with the CPU clock on the CPU that caused the problem. Then stop and restart the DNR task group.
Explanation The Receiver thread successfully initialized.
Explanation The Receiver thread terminated normally.
Explanation An ABEND occurred while the receive thread was in control. The unit of work being processed may not have completed and the associated directory request may not complete normally. This problem may cause other DNR requests not to complete normally. An IFS formatted dump should accompany this message. An MVS formatted dump should accompany this message if the execution JCL included a SYSUDUMP DD statement.
Recommended Action Contact Customer Support. Have ready for them the IFS formatted dump and the SYSUDUMP, if possible. If SYSLOG message IEA995I indicates that the active load module is DNRSCALL, query SMP/E for the PTF level of DNRSCALL before calling for support.
Explanation The MVS operator requested that the DNR task group be shutdown normally by issuing either a %STOP DNR or %P command for the first time.
Explanation The MVS operator requested that the DNR task group be shutdown immediately by issuing either a %STOP DNR or %P command for the second time.
Recommended Action Any Directory service requests that were not completed before the second operator command have been flushed. Any application programs waiting for the associated directory request to complete may not complete and may have to be cancelled.
Explanation While parsing the contents of the primary DNR configuration member, a command was encountered that was not a valid DNR configuration command.
Recommended Action Correct the configuration statements in the DNR configuration member. Then restart the DNR task group.
Explanation While parsing the contents of the primary DNR configuration member, a command was encountered more than once. The mem_name variable is the primary DNR configuration member.
Recommended Action Correct the primary DNR configuration member mem_name to contain only one of each DNR command.
Explanation A required keyword was not specified as an operand on the specified command.
Recommended Action Correct the DNR primary configuration member mem_name.Add the required keyword operand to the appropriate command.
Explanation The IPARSE command could not successfully parse a command in the DNR primary configuration member.
Recommended Action Verify that each keyword on every DNR configuration statement is spelled correctly and that the format of each command is correct. Then restart the DNR task group.
Explanation DNR primary configuration member (mem_name) did not contain a statement that started with the command DNR.
Recommended Action Correct the primary configuration member, adding a statement that starts with the command DNR.
Explanation The primary DNR configuration member (mem_name) did not include a valid POOLDEF statement for the pool with the name DSRB.
Recommended Action Correct or add a POOLDEF statement for the pool with the name DSRB in the primary DNR configuration member.
Explanation The DNR primary configuration member (mem_name) could not be located in the data set concatenation referenced by the SYSPARM DD statement.
Recommended Action Make sure that the DNR primary configuration member does exist in one of the data sets in the SYSPARM DD statement. If it does exist, then verify that the CNFG(xx) argument of the START DNR command contains the valid suffix.
Explanation A parsing error occurred while processing the command shown in the message. stmnt is the failing parameter and parameter value, up to 40 characters.
Recommended Action Correct the error and restart the DNR task group.
Explanation The TSO parser detected an unidentified keyword in the command statement.
Recommended Action Correct the value in the configuration parameters and restart the DNR task group.
Explanation An unexpected error was detected in the configuration file I/O handler. ret_code is the error/return code. This message is issued whenever an unexpected return code is received from ACPIPRMS. This message is preceded by another message that provides more information.
ACPIPRMS passes these return codes:
| 00 | OK |
| 04 | EOF on member |
| 08 | Member not found or unreadable |
| 12 | DCB not open |
| 16 | Invalid parameter list |
| 20 | Assembly buffer too small |
Recommended Action Refer to preceding message for information to help resolve the problem.
Explanation If TEST is turned on for the DNR task group, this message is issued each time a new directory request is received and processing begins.
Explanation If TEST is turned on for the DNR task group, this message is issued each time a directory request has completed execution unless the request timed out, the requesting task or address space terminated or the request terminated due to an ABEND.
Explanation If TEST is turned on for the DNR task group, this message is issued each time a directory request has completed execution due to the time limit being exceeded for that request.
Explanation If TEST is turned on for the DNR task group, this message is issued each time a DNR request cannot be completed as the issuing task or address space terminated before the request could complete normally.
Explanation This message is issued for each DNR request that cannot be completed normally due to the operator requesting that the DNR task group shutdown.
Explanation A DSRB, a pool element that represents one directory request, could not be found on one of the two internal DSRB chains. Since the DNR chains are maintained under the control of the local lock, this error represents either a serious DNR logic error or a storage overlay.
Recommended Action Contact Customer Support. Have ready for them the IFS formatted dump and the SYSUDUMP, if possible.
Explanation An ABEND occurred while a Request thread was in control. The unit of work being processed was ABENDed and the directory request terminated. This problem may or may not cause other DNR requests to terminate abnormally. An IFS formatted dump should accompany this message. An MVS formatted dump should accompany this message if the execution JCL included a SYSUDUMP DD statement.
Recommended Action Contact Customer Support. Have ready for them the IFS formatted dump and the SYSUDUMP, if possible. If SYSLOG message IEA995I indicates that the active load module is DNRSCALL, query SMP/E for the PTF level of MOD DNRSCALL before calling for support.
Explanation The Send thread was able to successfully initialize.
Explanation The Send thread was able to terminate normally.
Explanation An ABEND occurred while the Send thread was in control. The unit of work being processed may not have completed and the associated directory request may not complete normally, if at all. This problem may cause other DNR requests not to complete. An IFS formatted dump should accompany this message. An MVS formatted dump should accompany this message if the execution JCL included a SYSUDUMP DD statement.
Recommended Action Contact Customer Support. Have ready for them the IFS formatted dump and the SYSUDUMP, if possible. If SYSLOG message IEA995I indicates that the active load module is DNRSCALL, query SMP/E for the PTF level of DNRSCALL before calling for support.
Explanation Acknowledges that the DNR is processing a dump command for the request type returned (req_type).
Explanation The DNR dump command that was entered was invalid. Either it could not be correctly parsed or a required suboperand was missing.
Recommended Action Determine why the DUMP command was invalid and reissue the dump command. Verify that each keyword was entered correctly and if the CACHE DATA option was used that a data field was included. (i.e., DNR DUMP CACHE(DATA(SATURN.ACC.COM.)).
Explanation The dump command has completed execution.
Explanation An unexpected ABEND occurred while trying to process the dump command. This is most likely a software error.
Recommended Action Make sure that both an IFS formatted dump and SYSUDUMP have been produced, then contact Customer Support.
Explanation The dump command requires a Direct Services Request Block (DSRB) to process a dump request. However, the IGPOL service returned with a non-zero return code when it was called to allocate a DSRB. This problem can be caused by having either a too small region size or incorrect POOLDEF statements in the DNRCFG00 customization member.
Recommended Action Verify that the POOLDEF statements in the DNRCFG00 TCPPARM member are correct and that a sufficiently large enough region size has been specified on either the job or execute statement in the Cisco IOS for S/390 start-up JCL.
Explanation Acknowledges that the DNR is processing the PURGE command.
Explanation The PURGE command has completed execution.
The decimal code is represented by dec_comp_code; the hexadecimal completion code is represented by hex_ret_code.
Explanation An unexpected ABEND occurred while trying to process the PURGE command. This is most likely a software error.
Recommended Action Make sure that both an IFS formatted dump and SYSUDUMP have been produced, then contact Customer Support.
Explanation The PURGE command requires a Direct Services Request Block (DSRB) to process a dump request. However, the IGPOL service returned with a non-zero return code when it was called to allocate a DSRB. This problem can be caused by having either a too small region size or incorrect POOLDEF statements in the DNRCFG00 customization member.
The decimal code is represented by dec_comp_code; the hexadecimal completion code is represented by hex_ret_code.
Recommended Action Verify that the POOLDEF statements in the DNRCFG00 TCPPARM member are correct and that a sufficiently large region size has been specified on either the job or execute statement in the Cisco IOS for S/390 startup JCL.
|
|