|
|
This chapter describes messages written to logs by the Portmapper.
Explanation The MAP task group was successfully started and was able to process the primary configuration member without error.
| dec | The return code from MAPXINIT in decimal. |
| hex | The return code from MAPXINIT in hexadecimal. The MAP task group failed to initialize due to at least one error.
These are the valid values for dec X'hex' : · 4 X'0004' - Processing of primary configuration member MAPCFGxx failed. · 8 X'0008' - IGPOL for ISRB failed. · 12 X'000C' - SCHED failed. |
Recommended Action Correct the problem that caused the task group initialization to fail, then restart the MAP task group.
Explanation The module MAPICNFG either could not locate or could not successfully parse the primary configuration member MAPCFGxx. The single parameter character xx is the suffix of the primary configuration member name.
Recommended Action Make sure the primary configuration member exists and the control statements have the proper syntax and valid values. This message should be preceded by a message from MAPICNFG (messages MAP010E through MAP015E) which explains the error in more detail.
Explanation While parsing the contents of the primary MAP configuration member, an invalid MAP configuration command was encountered.
| mem | The primary MAP configuration member. |
| cmd | The specified invalid command. |
Recommended Action Correct the configuration statements in the MAP configuration member mem, then restart the MAP task group.
Explanation While parsing the contents of the primary MAP configuration member, a command was encountered more than once.
| cmd | The repeated command. |
| mem | The primary MAP configuration member. |
Recommended Action Correct the primary MAP configuration member to contain only one of each command.
Explanation A required keyword was not specified as an operand in the specified command in the specified configuration member.
| k | The required keyword. |
| cmd | The specified command. |
| mem | The primary MAP configuration member. |
Recommended Action Add the required keyword operand to the appropriate command.
Explanation The IPARSE command could not successfully parse a command in the MAP primary configuration member.
| mem | The primary configuration member. |
| dec | The IPARSE return code in decimal. |
| hex | The IPARSE return code in hexadecimal. |
Recommended Action Verify that each keyword on every MAP configuration statement is spelled correctly and that the format of each command is correct, then restart the MAP task group.
Explanation The specified MAP primary configuration member (mem) did not contain a statement that started with the MAP command.
Recommended Action Correct the primary configuration member, adding a statement that starts with the MAP command.
Explanation The MAP primary configuration member (mem) could not be located in the data set concatenation referenced by the SYSPARM DD statement.
Recommended Action Make sure that the MAP 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) operand of the START MAP command contains the valid suffix.
Explanation The TSO parser detected an unidentified keyword in the command statement.
| k | Unidentified keyword. |
| cmd | Specified command. |
| mem | Configuration member. |
Recommended Action Correct the value in the configuration parameters and restart the MAP task group.
Explanation An unexpected error was detected in the configuration file I/O handler. The rc parameter is the error/return code. This message is issued whenever an unexpected return code is received from ACPIPRMS.
ACPIPRMS passes these return codes:
Recommended Action Report this error to the Cisco IOS for S/390 administrator.
Explanation The MAP task group was able to complete processing of directory requests and stop execution.
Explanation The main port map program has exited with the return code specified in this message. The task group has now completed execution.
| dec | The return code from PORTMAP in decimal. |
| hex | The return code from PORTMAP in hexadecimal. |
Recommended Action If the return code is 0, no action is required. If the return code is not 0, check the SYSPRINT output data set for a message (MAP100I through MAP299) which explains why the MAP task group ended with a nonzero return code.
Explanation An ABEND was detected during the processing of the port mapper. All port mapper processing is terminated. Registered services are not unregistered unless the Cisco IOS for S/390 job is stopped. An IFS formatted dump should accompany this message. If the execution JCL included a SYSUDUMP DD statement, an MVS formatted dump should accompany this message.
Recommended Action Contact Customer Support. Have ready for them the IFS formatted dump and the SYSUDUMP, if available. If SYSLOG message IEA995I indicates that the active load module is PORTMAP, query SMP/E for the PTF level of PORTMAP before calling for support. Restart the task group to resume port map processing.
Explanation An ILOAD instruction failed to load module DNRSCALL. This program must exist in the SNSLOAD data set. The SNSLOAD data set must be in either the STEPLIB DD concatenation or in the MVS link list.
Recommended Action Correct the problem causing module DNRSCALL to not load, then restart the MAP task group.
This section describes messages that are issued to the SYSPRINT data set.
These messages have this format:
MAPxxxy timestamp text| MAP | Identifies port mapper message. |
| xxx | Message number, which may be one of these:
· 100 - 129 are Informational. · 130 - 149 are debugging. · 150 - 169 are warning. · 170 - 199 are port mapper specific errors. · 200 - 299 are RPC library errors. |
| y | A one-character indication of one of these valid message types:
· I - Informational message. · D - Debugging message. · W - Warning message. · E - Error messages. |
| timestamp | Date and time in the form shown in this example:
Sat Oct 23 21:33:45 1993 |
| text | Message specific text. |
Messages all go to SYSPRINT unless processed by perror(). If processed by perror(), messages go to SYSTERM and have additional text appended to the end. All messages that may be processed by perror() are noted.
Explanation The port mapper has started operation for the first time of this run of Cisco IOS for S/390 API.
Explanation The port mapper has restarted operation after either an outage by Cisco IOS for S/390 API or because the port mapper was stopped by an operator command and then started again by an operator command.
Explanation The port mapper has received a command from the operator to stop processing. Portmap services are no longer available. Services currently registered are maintained if the port mapper is restarted before Cisco IOS for S/390 API is terminated.
Explanation The port mapper has detected that Cisco IOS for S/390 API has stopped processing. The port mapper periodically attempts to re-establish service with Cisco IOS for S/390 API when it is restarted.
Explanation The port mapper is attempting to establish service with Cisco IOS for S/390 API.
Explanation The port mapper attempts to use the copy of Cisco IOS for S/390 API with the subsystem ID specified. The single parameter, s, is the subsystem ID of Cisco IOS for S/390 API that the port mapper is using.
Explanation This message indicates that the DEBUG PARM was selected when the port mapper was started. When DEBUG mode is used, the port mapper issues messages for most events that occur involving the port mapper. Normally only significant events cause messages to be generated.
Explanation An RPC client contacted the port mapper's NULL procedure.
Explanation An RPC client contacted the port mapper's REGISTER procedure.
Explanation An RPC register service request was received by the port mapper for the RPC program number and version listed.
| xxxxxxxx | Hexadecimal value of RPC program number |
| nnn | Decimal value of RPC program version |
Explanation An RPC register service request was received by the port mapper for the port and protocol listed.
| n | Decimal value of UDP or TCP port |
| protocol | A string identifying the protocol: either UDP or TCP |
Explanation An RPC service register request completed successfully.
Explanation An RPC client contacted the port mapper's UNREGISTER procedure.
Explanation An RPC unregister service request was received by the port mapper for the RPC program number and version listed.
| xxxxxxxx | Hexadecimal value of RPC program number |
| nnn | Decimal value of RPC program version |
Explanation An RPC service unregister request completed successfully.
Explanation An RPC client contacted the port mapper's GET PORT procedure.
Explanation An RPC client requested the port of the RPC program with the number and version listed.
| xxxxxxxx | Hexadecimal value of RPC program number |
| nnn | Decimal value of RPC program version |
Explanation An RPC client requested the port of the RPC program with the protocol listed. The single parameter, protocol, is a string identifying the protocol: either UDP or TCP.
Explanation The requested RPC program is not registered with the port mapper.
Explanation The requested RPC program is registered on the port listed. The single parameter, nnnnn, is returned. nnnnn is the UDP or TCP port number in decimal.
Explanation An RPC client contacted the port mapper's DUMP PORT MAPS procedure.
Explanation An RPC client contacted the port mapper's BROADCAST CALL procedure.
Explanation The port mapper could not establish a session with Cisco IOS for S/390 API at this time. It periodically retries this operation.
Explanation The port mapper periodically tries to re-establish service with the Cisco IOS for S/390 API. To avoid flooding the output queue with the same message indicating that the port mapper is still trying, it prints this message only after a predetermined number of retries.
Explanation An RPC service REGISTER request failed. This is normally due to the service already being registered.
Explanation The port mapper UNREGISTER procedure was contacted by a client but the arguments passed by the client to the port mapper could not be understood.
Explanation The port mapper REGISTER procedure was contacted by a client but the arguments passed by the client to the port mapper could not be understood.
Explanation An RPC service UNREGISTER request failed. This is normally due to the service not being registered.
Explanation The port mapper GET PORT procedure was contacted by a client but the arguments passed by the client to the port mapper could not be understood.
Explanation The port mapper DUMP PORTMAPS procedure was contacted by a client but the arguments passed by the client to the port mapper could not be understood.
Explanation An RPC client attempted to communicate with the port mapper's nonexistent BROADCAST CALL procedure. This procedure is not currently implemented.
Explanation An RPC client attempted to communicate with the port mapper's nonexistent BROADCAST CALL procedure. This procedure is not currently implemented.
Explanation The port mapper could not bind a name to UDP port 111. This indicates a problem with either the port mapper or Cisco IOS for S/390 API. This is a fatal error for the port mapper that now exits.
Recommended Action Recycle both the port mapper and the Cisco IOS for S/390 API to see if the problem clears. This message is followed by a perror() message generated by the socket library. Read the section "perror Messages" in the Cisco IOS for S/390 Unprefixed Messages and Codes manual for more information.
Explanation The port mapper could not create the necessary control blocks to provide port mapper service with its UDP endpoint. This is a fatal error for the port mapper that now exits.
Explanation The port mapper could not allocate storage necessary to register a service. This is a fatal error for the port mapper that now exits.
Explanation The port mapper could not bind a name to UDP port 111. This indicates a problem with either the port mapper or Cisco IOS for S/390 API. This is a fatal error for the port mapper that now exits.
Recommended Action Recycle both the port mapper and the Cisco IOS for S/390 API to see if the problem clears. This message is followed by a perror() message generated by the socket library. Read the section "perror Messages" in the Cisco IOS for S/390 Unprefixed Messages and Codes manual for more information.
Explanation The port mapper could not create the necessary control blocks to provide port mapper service with its TCP endpoint. This is a fatal error for the port mapper that now exits.
Explanation The port mapper could not reply to a request of its NULL procedure. This is a fatal error for the port mapper that now exits.
Explanation The port mapper could not respond properly to an RPC request (rpc_procedure_name). This is a fatal error for the port mapper that now exits.
Explanation A fatal error has occurred in the port mapper. A message describing the nature of this error precedes this one. The port mapper terminates operation.
Explanation An unexpected error occurred while the port mapper was waiting for requests from clients. This error is fatal and the port mapper terminates operation.
Explanation This is the general format of error messages generated by the RPC library used by the port mapper. These errors are normally fatal and are followed by a port mapper specific error.
| csect | The name of the CSECT that encountered the error |
| funcname | The entry point to a function within the CSECT that specifically encountered the error |
Read the Cisco IOS for S/390 RPC/XDR Programmer's Reference for more information.
|
|