Table Of Contents
MAPnnn - Portmapper Log Messages
MAPnnn - Portmapper Log Messages
This chapter describes messages written to logs by the Portmapper.
MAPnnn
MAP000I
PORTMAP INITIALIZATION SUCCESSFULLY COMPLETED.Explanation The MAP task group was successfully started and was able to process the primary configuration member without error.
MAP001E
PORTMAP INITIALIZATION FAILED - REASON CODE = dec X'hex'.Syntax Description
Recommended Action Correct the problem that caused the task group initialization to fail, then restart the MAP task group.
MAP002E
PORTMAP PROCESSING OF CNFG STATEMENTS FAILED. SYSPARM MEMBER 'MAPCFGxx'EITHER NOT FOUND OR IS IN ERROR.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.
MAP010E
PORTMAP UNKNOWN COMMAND IN CONFIGURATION MEMBER mem. COMMAND 'cmd' IS NOTVALID.Explanation While parsing the contents of the primary MAP configuration member, an invalid MAP configuration command was encountered.
Syntax Description
Recommended Action Correct the configuration statements in the MAP configuration member mem, then restart the MAP task group.
MAP011E
PORTMAP ONLY ONE cmd COMMAND IS ALLOWED IN THE CONFIGURATION MEMBER mem.Explanation While parsing the contents of the primary MAP configuration member, a command was encountered more than once.
Syntax Description
Recommended Action Correct the primary MAP configuration member to contain only one of each command.
MAP012E
PORTMAP REQUIRED KEYWORD k WAS NOT SPECIFIED ON THE cmd STATEMENT INCONFIGURATION MEMBER mem.Explanation A required keyword was not specified as an operand in the specified command in the specified configuration member.
Syntax Description
Recommended Action Add the required keyword operand to the appropriate command.
MAP013E
PORTMAP PARSING OF INPUT PARAMETERS IN CONFIGURATION MEMBER mem FAILED,REASON CODE = dec X'hex'.Explanation The IPARSE command could not successfully parse a command in the MAP primary configuration member.
Syntax Description
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.
MAP014E
PORTMAP CONFIGURATION MEMBER mem DID NOT CONTAIN A 'MAP' OPTIONS STATEMENTExplanation 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.
MAP015E
PORTMAP CONFIGURATION MEMBER mem DOES NOT EXIST IN 'SYSPARM' DATASET.MAP INITIALIZATION FAILED.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.
MAP017E
UNDEFINED KEYWORD(k) ON COMMAND(cmd) MEMBER(mem).Explanation The TSO parser detected an unidentified keyword in the command statement.
Syntax Description
Recommended Action Correct the value in the configuration parameters and restart the MAP task group.
MAP018E
RETURN CODE (rc) RECEIVED FROM CONFIGURATION FILE I/O HANDLER.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:
•
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 Report this error to the Cisco IOS for S/390 administrator.
MAP020I
PORTMAP SHUTDOWN SUCCESSFULLY COMPLETED.Explanation The MAP task group was able to complete processing of directory requests and stop execution.
MAP030I
PORTMAP COMPLETED EXECUTION --- RETURN CODE = dec X'hex'.Explanation The main port map program has exited with the return code specified in this message. The task group has now completed execution.
Syntax Description
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.
MAP031E
PORTMAP AN ABEND WAS DETECTED DURING PORT MAPPER PROCESSING. PORT MAPPERTASK GROUP TERMINATING.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.
MAP032E
PORTMAP LOAD FAILED FOR LMOD DNRSCALL. PORT MAPPER TASK GROUP TERMINATING.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.
Sysprint MAP Messages
This section describes messages that are issued to the SYSPRINT data set.
These messages have this format:
MAPxxxy timestamp 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.
MAP100I
timestamp HAS STARTED SUCCESSFULLYExplanation The port mapper has started operation for the first time of this run of Cisco IOS for S/390 API.
MAP101I
timestamp has restarted successfullyExplanation 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.
MAP102I
timestamp EXIT COMMAND RECEIVED. PORTMAP TERMINATINGExplanation 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.
MAP103I
timestamp SNS/API HAS ENDEDExplanation 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.
MAP104I
timestamp STARTING OPERATIONExplanation The port mapper is attempting to establish service with Cisco IOS for S/390 API.
MAP105I
timestamp SNS/API SUBSYSTEM ID IS sExplanation 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.
MAP130D
timestamp DEBUGGING MODE IS ENABLEDExplanation 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.
MAP131D
timestamp NULL PROCEDURE CALLEDExplanation An RPC client contacted the port mapper's NULL procedure.
MAP132D
timestamp REGISTER REQUEST RECEIVEDExplanation An RPC client contacted the port mapper's REGISTER procedure.
MAP133D
timestamp PROGRAM 0xxxxxxxxx VERSION nnnExplanation An RPC register service request was received by the port mapper for the RPC program number and version listed.
Syntax Description
MAP134D
timestamp PORT n PROTOCOL protocolExplanation An RPC register service request was received by the port mapper for the port and protocol listed.
Syntax Description
MAP135D
timestamp REGISTER REQUEST SUCCEEDEDExplanation An RPC service register request completed successfully.
MAP136D
timestamp UNREGISTER REQUEST RECEIVEDExplanation An RPC client contacted the port mapper's UNREGISTER procedure.
MAP137D
timestamp PROGRAM 0xxxxxxxxx VERSION nnnExplanation An RPC unregister service request was received by the port mapper for the RPC program number and version listed.
Syntax Description
MAP138D
timestamp UNREGISTER REQUEST SUCCEEDEDExplanation An RPC service unregister request completed successfully.
MAP139D
timestamp GET PORT REQUEST RECEIVEDExplanation An RPC client contacted the port mapper's GET PORT procedure.
MAP140D
timestamp PROGRAM 0xxxxxxxxx VERSION nnnExplanation An RPC client requested the port of the RPC program with the number and version listed.
Syntax Description
MAP141D
timestamp PROTOCOL protocolExplanation 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.
MAP142D
timestamp SERVICE NOT REGISTERED ON PORTExplanation The requested RPC program is not registered with the port mapper.
MAP143D
timestamp SERVICE REGISTERED ON PORT nnnnnExplanation 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.
MAP144D
timestamp DUMP MAPS PROCEDURE REQUEST RECEIVEDExplanation An RPC client contacted the port mapper's DUMP PORT MAPS procedure.
MAP145D
timestamp CALL BROADCAST PROCEDURE REQUESTEDExplanation An RPC client contacted the port mapper's BROADCAST CALL procedure.
MAP150W
timestamp 1API IS NOT YET OPERATIONAL.Explanation The port mapper could not establish a session with Cisco IOS for S/390 API at this time. It periodically retries this operation.
MAP151W
timestamp WAITING FOR SNS/CISCO IOS FOR S/390 API TO BECOME OPERATIONALExplanation 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.
MAP152W
timestamp REGISTER REQUEST FAILEDExplanation An RPC service REGISTER request failed. This is normally due to the service already being registered.
MAP153W
timestamp UNREGISTER PROCEDURE PASSED BAD ARGUMENTSExplanation 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.
MAP154W
timestamp REGISTER PROCEDURE PASSED BAD ARGUMENTSExplanation 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.
MAP155W
timestamp UNREGISTER REQUEST FAILEDExplanation An RPC service UNREGISTER request failed. This is normally due to the service not being registered.
MAP156W
timestamp GET PORT PROCEDURE PASSED BAD ARGUMENTSExplanation 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.
MAP157W
timestamp DUMP MAPS PROCEDURE PASSED BAD ARGUMENTSExplanation 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.
MAP158W
timestamp CALL PROCEDURE NOT CURRENTLY SUPPORTEDExplanation An RPC client attempted to communicate with the port mapper's nonexistent BROADCAST CALL procedure. This procedure is not currently implemented.
MAP159W
timestamp UNSUPPORTED PROCEDURE REQUESTEDExplanation An RPC client attempted to communicate with the port mapper's nonexistent BROADCAST CALL procedure. This procedure is not currently implemented.
MAP170E
timestamp CANNOT BIND TO UDP PORT 111Explanation 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.
MAP171E
timestamp COULD NOT CREATE UDP SERVICEExplanation 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.
MAP172E
timestamp COULD NOT ALLOCATE STORAGE FOR PMAPLISTExplanation The port mapper could not allocate storage necessary to register a service. This is a fatal error for the port mapper that now exits.
MAP173E
timestamp CANNOT BIND TO TCP PORT 111Explanation 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.
MAP174E
timestamp COULD NOT CREATE TCP SERVICEExplanation 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.
MAP175E
timestamp NULL PROCEDURE COULD NOT SEND REPLYExplanation 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.
MAP177E
timestamp rpc_procedure_name ERRORExplanation 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.
MAP178E
timestamp TERMINATING DUE TO PREVIOUS ERRORExplanation 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.
MAP200E
timestamp (SVCRUN SVCRUN) SELECT FAILEDExplanation An unexpected error occurred while the port mapper was waiting for requests from clients. This error is fatal and the port mapper terminates operation.
MAP2xxE
timestamp (csect.func_name) textExplanation 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.
Syntax Description
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.