gtpm5m2g | Messages (Online) |
SIPC0001I | TOTALS FOR HOST-procid |
Where:
Explanation: This is a normal response to the ZSIPC DISPLAY command for Multi-Processor Interconnect Facility Interprocessor Communications (MPIF IPC). This message is followed by a display of the system interprocessor communications (SIPC) transmission counts for the host processor.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSIPC DISPLAY command and for an example of the informational display..
SIPC0001I | COUNTS FOR DEST-procid |
Where:
Explanation: This is a normal response to the ZSIPC command for Multi-Processor Interconnect Facility Interprocessor Communications (MPIF IPC). This message is followed by a display of the system interprocessor communications (SIPC) transmission counts for the destination processor.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSIPC commands and an example of the informational display..
SIPC0002I | COUNTS ZEROED |
Explanation: This is a normal response to the ZSIPC ALTER command for Multi-Processor Interconnect Facility Interprocessor Communications (MPIF IPC).
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0005I | INTERVALS SET |
Explanation: This is a normal response to the ZSIPC ALTER command for Multi-Processor Interconnect Facility Interprocessor Communications (MPIF IPC).
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0006I | MAXIMUM NUMBER OF PATHS ALTERED TO value |
Where:
Explanation: This is a normal response to the ZSIPC ALTER command for Multi-Processor Interconnect Facility Interprocessor Communications (MPIF IPC).
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0007I | IPC CLASS ALTERED TO value |
Where:
Explanation: This is a normal response to the ZSIPC ALTER command for Multi-Processor Interconnect Facility Interprocessor Communications (MPIF IPC).
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0008I | IPC RESTART TIMEOUT VALUE ALTERED TO value |
Where:
Explanation: This is a normal response to the ZSIPC ALTER command for Multi-Processor Interconnect Facility Interprocessor Communications (MPIF IPC).
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0050E | ACTION IS NOT DISPLAY OR ALTER |
Explanation: The ZSIPC ALTER command was entered with an action code specified that is not valid for Multi-Processor Interconnect Facility Interprocessor Communications (MPIF IPC).
The action code must be DISPLAY or ALTER.
System Action: The ZSIPC ALTER command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0052E | INVALID DISPLAY SUBJECT GIVEN |
Explanation: The ZSIPC DISPLAY command was entered with a subject specified that is not valid.
The following subjects are valid:
System Action: The ZSIPC DISPLAY command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSIPC DISPLAY command.
SIPC0053E | INVALID ALTER SUBJECT |
Explanation: The ZSIPC ALTER command was entered with a subject specified that is not valid.
The following subjects are valid:
System Action: The ZSIPC ALTER command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0054E | INVALID PROCESSOR ID |
Explanation: The ZSIPC DISPLAY command was entered with the COUNTS parameter specified and a processor ID that is not valid.
The processor ID must be one of the following:
System Action: The ZSIPC DISPLAY command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSIPC DISPLAY command.
SIPC0055E | INVALID VALUE FOR *TIME OR TOUT* |
Explanation: The ZSIPC ALTER command was entered with the INTERVALS parameter specified and a time or timeout count that is not valid.
System Action: The ZSIPC ALTER command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0071E | IPC INOPERATIVE, REQUEST REJECTED |
Explanation: The system is not a shared database (loosely coupled) system.
System Action: The ZSIPC command is rejected.
User Response: None.
See TPF Operations for more information about the ZSIPC commands.
SIPC0071T | IPC INOPERATIVE, REQUEST REJECTED |
Explanation: The system is not a shared database (loosely coupled) system.
System Action: The ZSIPC command is rejected.
User Response: None.
See TPF Operations for more information about the ZSIPC commands.
SIPC0072E | INVALID PATH PARAMETER |
Explanation: The ZSIPC ALTER command was entered with the PATHS parameter specified and a maximum number of paths that is not valid.
System Action: The ZSIPC ALTER command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0073E | INVALID CLASS PARAMETER |
Explanation: The ZSPIC ALTER command was entered with the CLASS parameter specified and a class ID that is not valid.
System Action: The ZSIPC ALTER command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0074E | UNABLE TO RETRIEVE KEYPOINT RECORD -E- |
Explanation: An error code was returned from CYYM when trying to retrieve Keypoint record E (CTKE) while processing the ZSIPC ALTER command.
System Action: The ZSIPC ALTER command is rejected and the segment is exited.
User Response: Have your system programmer review the CTL-0FB dump from the CYYM segment.
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0075E | UNABLE TO FILE KEYPOINT RECORD -E- |
Explanation: An error code was returned from CYYA when trying to file keypoint record E (CTKE) while processing a ZSIPC ALTER command.
System Action: The ZSIPC ALTER command is rejected and the program is exited.
User Response: Have your system programmer review the CTL-0F2 dump from the CYYA segment.
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0076E | INTERVALS NOT SET -- TIME AND TOUT NOT SPECIFIED |
Explanation: An error resulted from a request to alter the system interprocessor communications (SIPC) timeout interval when the ZSIPC ALTER command with the INTERVAL parameter specified was entered. A new TIME or a new interval (TOUT) was not specified. One or both need to be specified.
System Action: The ZSIPC ALTER command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSIPC ALTER command.
SIPC0077E | IPC INTERVAL NOT SET -- VALUE TOO LARGE |
Explanation: The ZSIPC ALTER command was entered with the RESTART parameter specified and a restart timeout value that is too large. The value must be between 0 and 65535.
System Action: The ZSIPC ALTER command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSIPC ALTER command.
SMTP0001E | SMTPD: FAILED TO BIND TO SMTPD PORT |
Explanation: The Simple Mail Transfer Protocol (SMTP) server was unable to bind to well-known port 25. This indicates that another socket is using this port.
System Action: The entry control block (ECB) exits and the SMTP server stops.
User Response: Do the following:
See TPF Operations for more information about the ZINET and ZSOCK commands. See TPF Transmission Control Protocol/Internet Protocol for more information about TPF Internet mail server support and the SMTP server.
SMTP0002E | SMTPD: FAILED TO LISTEN TO SMTPD PORT: CODE errno |
Where:
Explanation: The Simple Mail Transfer Protocol (SMTP) server was unable to process the listen function for the socket descriptor.
System Action: The entry control block (ECB) exits and the SMTP server stops.
User Response: Do the following:
See TPF Operations for more information about the ZINET commands. See TPF Transmission Control Protocol/Internet Protocol for more information about TPF Internet mail server support and the SMTP server.
SMTP0003E | SMTPD: SELECT FAILED: CODE errno |
Where:
Explanation: The Simple Mail Transfer Protocol (SMTP) server was unable to process the select function for the socket descriptor.
System Action: The entry control block (ECB) continues to run and issue this message until the problem is resolved or until the SMTP server is stopped.
User Response: Do the following:
See TPF Operations for more information about the ZINET commands. See TPF Transmission Control Protocol/Internet Protocol for more information about TPF Internet mail server support and the SMTP server.
SMTP0004E | SMTPD: FAILED TO ACCEPT INCOMING CONNECTION: CODE errno |
Where:
Explanation: The Simple Mail Transfer Protocol (SMTP) server was unable to process the accept function for the socket descriptor.
System Action: The entry control block (ECB) continues to run.
User Response: Do the following:
See TPF Operations for more information about the
ZINET commands. See TPF Transmission Control
Protocol/Internet Protocol for more information about TPF Internet mail
server support and the SMTP server.
Explanation:
ZINET START S-SMTP was entered to start the Simple
Mail Transfer Protocol (SMTP) server for the first time. You must enter
ZMAIL START or ZMAIL START ACCEPT to start the SMTP server for
the first time.
System Action: The entry control block (ECB) exits and the SMTP server stops.
User Response: Enter ZMAIL START or ZMAIL START ACCEPT to start the SMTP
server.
See TPF Operations for more information about the
ZINET and ZMAIL commands. See TPF Transmission
Control Protocol/Internet Protocol for more information about TPF
Internet mail server support and the SMTP server.SMTP0005E SMTPD: USE ZMAIL START OR ZMAIL START ACCEPT TO START SMTP
SNAP0001I | CPU-cpuid SS-ssname SSU-ssu IS-istreamnum PSW-psw PGM-progname CODE-errorcode TERM-ta |
Where:
Explanation: This message is the snapshot dump header.
System Action: None.
User Response: Look up the snapshot error code (lcccccccc) in Messages (System Error and Offline) to determine the corrective action to take.
See TPF General Macros for more information about the SNAPC macro.
SNAP0002W | SNAPC TAPE WRITE ABORTED, NO tape TAPE AVAILABLE. |
Where:
Explanation: The system dump tape is not available.
System Action: None.
User Response: Mount the system dump tape.
See TPF General Macros for more information about the SNAPC macro.
SNDA0001I | REQUEST PROCESSED |
Explanation: This is the normal response to the ZSNDA command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSNDA command.
SNDA0007E | APPLICATION NAME INVALID OR NOT ACTIVE |
Explanation: The ZSNDA command was entered with an application name specified that is not valid or whose program is not currently active.
System Action: The ZSNDA command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZSNDA and ZROUT commands.
SNDA0009E | INVALID CHARACTER(S) IN FIRST OPERAND |
Explanation: The ZSNDA command was entered with characters that are not valid. The first operand contains characters other than:
System Action: Processing is ended.
User Response: Enter the ZSNDA command again by using the correct characters for the first operand.
See TPF Operations for more information about the ZSNDA command.
SNDA0010E | SYSTEM NOT IN NORM STATE |
Explanation: You can only enter the ZSNDA command when the TPF system is in NORM state.
System Action: The ZSNDA command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNDA command.
SNDA0012E | OPERAND MISSING OR INVALID |
Explanation: The ZSNDA command was entered with a required operand that is not valid or is missing.
System Action: Processing is ended.
User Response: Enter the ZSNDA command again with the correct operand.
See TPF Operations for more information about the ZSNDA command.
SNDA0013E | NO EOM FOUND IN MESSAGE |
Explanation: The ZSNDA command was entered without an end-of-message (EOM) character.
System Action: The ZSNDA command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNDA command.
SNDA0016E | TEXT GREATER THAN 255 CHARACTERS |
Explanation: The ZSNDA command was entered with text greater than 255 characters.
System Action: The ZSNDA command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNDA command.
SNDA0018E | APPLICATION NAME TOO LONG |
Explanation: The ZSNDU command was entered with an application name longer than 4 characters. The application name must be from 1 to 4 characters.
System Action: the ZSNDU command is rejected.
User Response: Enter the ZSNDU command again and specify an application name that is from 1 to 4 characters.
See TPF Operations for more information about the ZSNDA command.
SNDU0001I | REQUEST PROCESSED |
Explanation: This is the normal response to the ZSNDU command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSNDU command.
SNDU0009E | INVALID CHARACTER(S) IN FIRST OPERAND |
Explanation: The ZSNDU command was entered with characters that are not valid in the first operand, which is the address operand or the CPU ID.
The following characters are valid for the address operand:
The following characters are valid for the CPU ID:
System Action: Processing is ended.
User Response: Enter the ZSNDU command again and specify the correct characters for the first operand.
See TPF Operations fo more information about the ZSNDU command.
SNDU0010E | SYSTEM NOT IN NORM STATE |
Explanation: The ZSNDU command was entered when the TPF system was not in NORM state.
System Action: The ZSNDU command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNDU command.
SNDU0012E | OPERAND MISSING OR INVALID |
Explanation: The ZSNDU command was entered with a required operand that is not valid or is missing.
System Action: The ZSNDU command is rejected.
User Response: Enter the ZSNDU command again with the correct operand.
See TPF Operations for more information about the ZSNDU command.
SNDU0013E | NO EOM FOUND IN MESSAGE |
Explanation: The ZSNDU command was entered without an end-of-message (EOM) character.
System Action: The ZSNDU command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNDU command.
SNDU0016E | TEXT GREATER THAN 255 CHARACTERS |
Explanation: The ZSNDU command was entered with text greater than 255 characters.
System Action: The ZSNDU command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNDU command.
SNDU0019E | INVALID FORMAT IN ADDRESS OPERAND |
Explanation: The ZSNDU command was entered with an address specified in an incorrect format.
System Action: The ZSNDU command is rejected.
User Response: Enter the ZSNDU command again by using the correct address format.
See TPF Operations for more information about the ZSNDU command and for a description of the correct address format.
SNMP0001I | SNMP CONFIGURATION FILE REFRESHED SUCCESSFULLY |
Explanation: This is the normal response to the ZSNMP command with the REFRESH parameter specified or to a successful refresh when cycling the TPF system to NORM state.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about Simple Network Management Protocol (SNMP) agent support.
SNMP0002E | SNMP CONFIGURATION FILE DOES NOT EXIST |
Explanation: The ZSNMP command was entered with the REFRESH parameter specified, but the /etc/snmp.cfg Simple Network Management Protocol (SNMP) configuration file does not exist in the TPF file system.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0003E | ERROR OPENING SNMP CONFIGURATION FILE, ERRNO-number |
Where:
Explanation: The ZSNMP command was entered with the REFRESH parameter specified, but an error occurred when opening the /etc/snmp.cfg Simple Network Management Protocol (SNMP) configuration file.
System Action: The command is rejected.
User Response: Review the errno.h file to determine the error and do the following:
See TPF Operations for more information about the ZFILE chmod, ZFILE ls, and ZSNMP commands. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0004E | DESTINATION SNMP MANAGER ADDRESS hostname COULD NOT BE RESOLVED |
Where:
Explanation: The host name of the SNMP manager could not be resolved.
System Action: The SNMP enterprise-specific trap message is not sent.
User Response: Review the /etc/snmp.cfg SNMP configuration file to ensure that the host name is coded correctly on the TRAPIP keyword and do one of the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0005E | DESTINATION SNMP MANAGER ADDRESS WAS NOT SPECIFIED |
Explanation: The ZSNMP command was entered with the REFRESH parameter specified, but the trap destination Internet Protocol (IP) address that indicates where to send trap protocol data units (PDUs) was not specified in the /etc/snmp.cfg Simple Network Management Protocol (SNMP) configuration file.
System Action: The command is rejected.
User Response: Review the /etc/snmp.cfg SNMP configuration file to ensure that the IP addresses or host names are coded on the TRAPIP keyword and do one of the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0006E | SNMP COMMUNITY NAME WAS NOT SPECIFIED |
Explanation: The ZSNMP command was entered with the REFRESH parameter specified, but a community name was not specified in the/etc/snmp.cfg SNMP configuration file.
System Action: The command is rejected.
User Response: Review the /etc/snmp.cfg SNMP configuration file to ensure that the community name is coded on the COMMNAME keyword and do the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0007E | SNMP OBJECT IDENTIFIER WAS NOT SPECIFIED |
Explanation: The ZSNMP command was entered with the REFRESH parameter specified, but a system object identifier for this TPF processor was not specified in the /etc/snmp.cfg SNMP configuration file.
System Action: The command is rejected.
User Response: Review the /etc/snmp.cfg SNMP configuration file to ensure that the system object identifier is coded on the SYSOBJID keyword and do the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0008E | SNMP TRAP MESSAGE COULD NOT BE SENT TO SNMP MANAGER ipaddress |
Explanation: An attempt was made to send a Simple Network Management Protocol (SNMP) trap message, but an active link could not be found to allow the TPF system to send the trap.
System Action: The SNMP trap message is discarded.
User Response: Do one of the following:
See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0009E | SNMP MANAGER ipaddress IS NOT ACCEPTING SNMP TRAP MESSAGES, ICMP ERROR-error |
Where:
Explanation: An attempt was made to send an SNMP enterprise-specific trap message, but an ICMP message was received indicating an error.
System Action: None.
User Response: Verify that the destination IP address is set up as an SNMP manager and do one of the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0010W | SNMP CONFIGURATION FILE HAS NOT BEEN SUCCESSFULLY REFRESHED |
Explanation: An attempt was made to refresh the /etc/snmp.cfg Simple Network Management Protocol (SNMP) configuration file during cycle-up, but the configuration file could not be refreshed.
System Action: The /etc/snmp.cfg SNMP configuration file is not refreshed and support is disabled on the TPF system.
User Response: Do one of the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0011E | REJECTED, TCP/IP NATIVE STACK SUPPORT NOT DEFINED |
Explanation: The ZSNMP command was entered with the REFRESH parameter specified, but TCP/IP native stack support is not defined.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about the SNAKEY parameters that are required for TCP/IP native stack support. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.
SNMP0012E | ERROR READING SNMP CONFIGURATION FILE, LINE-number |
Where:
Explanation: The ZSNMP command was entered with the REFRESH parameter specified, but an error occurred while reading a line in the /etc/snmp.cfg SNMP configuration file.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0013E | SYSTEM MUST BE IN CRAS STATE OR ABOVE |
Explanation: The ZSNMP command was entered with the REFRESH parameter specified, but the TPF system was below CRAS state.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0014E | INCORRECT SNMP OBJECT IDENTIFIER, LINE-number |
Where:
Explanation: The ZSNMP command was entered with the REFRESH parameter specified, but the system object identifier in the /etc/snmp.cfg SNMP configuration file does not begin with 1.3.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0015E | SNMP CONFIGURATION FILE HAS NOT BEEN SUCCESSFULLY REFRESHED |
Explanation: An attempt was made to access fields from the /etc/snmp.cfg Simple Network Management Protocol (SNMP) configuration file, but the configuration file has not been refreshed.
System Action: The SNMP agent server stops.
User Response: Do the following:
See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0016E | SNMP AGENT CAN ONLY RUN IN THE BSS |
Explanation: An attempt was made to process a Simple Network Management Protocol (SNMP) request in a subsystem other than the basic subsystem (BSS).
System Action: The SNMP agent server stops.
User Response: Do the following:
See TPF Operations for more information about the ZINET commands. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.
SNMP0017E | ERROR RECEIVING SNMP PROTOCOL DATA UNIT, SOCKERRNO-number |
Where:
Explanation: An error occurred when the Simple Network Management Protocol (SNMP) agent was receiving a protocol data unit (PDU) from the TCP/IP network.
System Action: The SNMP agent server exits.
User Response: Do the following:
See TPF Transmission Control Protocol/Internet
Protocol for more information about socket errors and SNMP agent
support.
Explanation: This is the normal response to the ZSNMP command
with the DISPLAY parameter specified.
System Action: The Management Information Base (MIB) variables that were retrieved from the
TPF MIB database are displayed.
User Response: None.
See TPF Operations for more information about the
ZSNMP command and for an example of the
informational display. See TPF Transmission Control
Protocol/Internet Protocol for more information about Simple Network
Management Protocol (SNMP) agent support.
Where:
Explanation: This is the normal response to the ZSNMP command
with the DISPLAY and FILE parameters specified.
System Action: The MIB variables that were retrieved from the TPF MIB database are sent to
the specified file.
User Response: None.
See TPF Operations for more information about the
ZSNMP command. See TPF
Transmission Control Protocol/Internet Protocol for more information
about Simple Network Management Protocol (SNMP) agent support.
Where:
Explanation: The ZSNMP command was entered with the DISPLAY
parameter specified, but an error occurred while attempting to retrieve the
MIB value.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the
ZSNMP command. See TPF
Transmission Control Protocol/Internet Protocol for more information
about Simple Network Management Protocol (SNMP) agent support.
Where:
Explanation: The ZSNMP command was entered with the DISPLAY and
FILE parameters specified, but an error occurred while attempting to open the
specified file.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZSNMP command. See the TPF C/C++ Language Support User's Guide for more
information about the open function. See TPF Transmission Control Protocol/Internet Protocol for
more information about Simple Network Management Protocol (SNMP) agent
support.
Where:
Explanation: The ZSNMP command was entered with the DISPLAY and
FILE parameters specified, but an error occurred while attempting to write to
the specified file.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZSNMP command. See the TPF C/C++ Language Support User's Guide for more
information about the write function. See TPF Transmission Control Protocol/Internet Protocol for
more information about Simple Network Management Protocol (SNMP) agent
support.SNMP0018I SNMP MIB RETRIEVAL DISPLAY
SNMP0019I SNMP MIB RETRIEVAL CONTENTS SENT TO FILE file
SNMP0020E SNMP ERROR error RETRIEVING MIB VALUE mibval
SNMP0021E ERROR OPENING filename - ERROR errno
SNMP0022E ERROR WRITING TO filename - ERROR errno
SOCK0001E | IP TABLE FULL - OFFLOAD RESTART ABORTED, ADAPTER ID-adapterid PATH ID-pathid |
Where:
Explanation: During the restart of a TCP/IP offload device, the TPF system tried to create an Internet Protocol (IP) entry for an interface address on the TCP/IP offload device but there were no more entries available in the IP table.
System Action: Restart of the TCP/IP offload device ends.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the SNAKEY macro. See TPF Transmission Control Protocol/Internet Protocol for more information about the values to specify for the TCP/IP parameters in the SNAKEY macro.
SOCK0002E | ADAPTER ID-adapterid PATH ID-pathid OFFLOAD RESTART RESPONSE ERROR |
Where:
Explanation: While restarting the TCP/IP offload device, the TPF system tried to issue a claw_send request to send a restart response to the TCP/IP offload device, and an error occurred.
System Action: None.
User Response: Do the following:
See TPF Transmission Control Protocol/Internet Protocol for more information about the claw_send function.
SOCK0003E | SOCKET DESCRIPTOR-filedescriptor ADDRESS-address FILE DESCRIPTOR RELEASE ERROR |
Where:
Explanation: An error occurred when the TPF system tried to release a file descriptor.
System Action: The file descriptor specified by the socket client is not released and processing continues.
User Response: Do the following:
SOCK0004E | ADAPTER ID-adapterid PATH ID-pathid ADDRESS-address IP ENTRY RELEASE ERROR |
Where:
Explanation: An error occurred when the TPF system tried to release an entry in the IP table after issuing a claw_disconnect to a TCP/IP offload device.
System Action: The IP entry specified by the socket client is not released and processing continues.
User Response: Do the following:
See TPF Transmission Control Protocol/Internet Protocol for more information about the claw_disconnect function.
SOCK0010I | SOCKET CONTENTS FORMATTED |
Explanation: This is the normal response to the ZSOCK command with the DISPLAY and FORMAT parameters specified. This message is followed by a formatted display of the Transmission Control Protocol/Internet Protocol (TCP/IP) native stack support socket control block information associated with the specified parameters.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSOCK command.
SOCK0011I | SOCKET CONTENTS |
Explanation: This is the normal response to the ZSOCK command with the DISPLAY parameter specified. This message is followed by a display of the Transmission Control Protocol/Internet Protocol (TCP/IP) native stack support socket control block information associated with the specified parameter.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSOCK command.
SOCK0012E | SYSTEM MUST BE IN CRAS STATE OR ABOVE |
Explanation: The ZSOCK command was entered while the TPF system was below CRAS state.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZCYCL and ZSOCK commands.
SOCK0013E | TCP/IP NATIVE STACK SUPPORT IS NOT DEFINED |
Explanation: The ZSOCK command was entered, but Transmission Control Protocol/Internet Protocol (TCP/IP) native stack support has not been defined for this TPF system.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSOCK, ZTTCP ACTIVATE, and ZTTCP DEFINE commands.
SOCK0014E | REQUIRED PARAMETERS NOT SUPPLIED |
Explanation: The ZSOCK command was entered, but one or more of the required parameters was not specified.
System Action: The command is rejected.
User Response: Enter the ZSOCK command again, specifying all required parameters.
See TPF Operations for more information about the ZSOCK command.
SOCK0015E | sockdesc OUT OF ALLOWED RANGE OF SOCKET DESCRIPTORS |
Where:
Explanation: The ZSOCK command was entered with the SOCKET parameter specified to find a socket control block, but the specified socket descriptor is not in the valid range for TCP/IP native stack support socket descriptors.
System Action: The command is rejected.
User Response: Enter the ZSOCK command again, specifying the correct socket descriptor for the SOCKET parameter.
See TPF Operations for more information about the ZSOCK command.
SOCK0016I | SOCKET sockdesc IS NOW INACTIVE |
Where:
Explanation: This is the normal response to the ZSOCK command with the INACT and SOCKET parameters specified.
System Action: The socket is closed. For a TCP socket, the TCP connection, if established or in the process of being established, is reset.
User Response: None.
See TPF Operations for more information about the ZSOCK command.
SOCK0017E | SOCKET sockdesc IS NOT ACTIVE |
Where:
Explanation: The ZSOCK command was entered with the SOCKET parameter specified, but the socket is not active.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZSOCK command.
SOCK0018I | INACT COMPLETE, numsocks SOCKETS CLOSED |
Where:
Explanation: This is the normal response to the ZSOCK command with the INACT parameter specified and the LIP, RIP, LPORT, RPORT, or PROTOCOL parameters specified.
System Action: All sockets matching the selection criteria specified by the LIP, RIP, LPORT, RPORT, or PROTOCOL parameters have been closed. Any corresponding Transmission Control Protocol (TCP) connections have been reset.
User Response: None.
See TPF Operations for more information about the ZSOCK command.
SOCK0019I | BEGIN CONVERT DISPLAY |
Explanation: This is the normal response to the ZSOCK command with the CONVERT parameter specified. This message is followed by a display of the local IP address, local port, remote IP address, remote port, protocol, and socket descriptor for the selected socket.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSOCK command.
SOCK0020E | REQUEST HAS MULTIPLE ENTIRES |
Explanation: The ZSOCK command was entered with the CONVERT or DISPLAY parameter specified, but the search resulted in multiple socket descriptors that matched the selection criteria specified by the LIP, LPORT, RIP, RPORT, or PROTOCOL parameters.
System Action: The command is rejected.
User Response: Enter the ZSOCK command again with the correct selection criteria as specified by the LIP, LPORT, RIP, ZSOCK, or PROTOCOL parameters.
See TPF Operations for more information about the ZSOCK command.
SOCK0021I | SOCKET SUMMARY INFORMATION |
Explanation: This is the normal response to the ZSOCK command with the SUMMARY parameter specified. This message is followed by a display of all the socket descriptors matching the selection criteria provided by the RIP, RPORT, LIP, LPORT, or PROTOCOL parameters along with selected Transmission Control Protocol/Internet Protocol (TCP/IP) native stack support socket control block fields.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSOCK command.
SOCK0022E | NO SOCKET MATCHING SEARCH CRITERIA |
Explanation: The ZSOCK command was entered with the CONVERT or DISPLAY parameter specified, but the search resulted in no sockets that matched the selection criteria specified by the LIP, LPORT, RIP, RPORT, or PROTOCOL parameters.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZSOCK command.
SOCK0023E | INCORRECT VALUE value NOT SUPPORTED FOR keyword |
Where:
Explanation: The ZSOCK command was entered, but the value is incorrect or not supported for the specified keyword.
System Action: The command is rejected.
User Response: Enter the ZSOCK command again, specifying the correct value for the keyword.
See TPF Operations for more information about the ZSOCK command.
SOCK0024I | BEGIN PROCESSING SOCKET DATAFLOW STATISTICS |
Explanation: This is the normal response to the ZSOCK command with the DATAFLOW parameter specified.
System Action: The TPF system begins the process of determining the number of bytes sent and received across the specified socket.
User Response: None.
See TPF Operations for more information about the ZSOCK command.
SOCK0025I | SOCKET DATAFLOW STATISTICS FOR A 5-SECOND INTERVAL |
Explanation: This is the normal response to the ZSOCK command with the DATAFLOW parameter specified.
System Action: This message is followed by a display of the number of bytes sent and received across the specified socket in a 5-second interval.
User Response: None.
See TPF Operations for more information about the ZSOCK command and for an example of the informational display.
SOCK0026E | SOCKET-socket DOES NOT EXIST |
Where:
Explanation: The ZSOCK command was entered with the DATAFLOW and SOCKET parameters specified, but the socket descriptor specified with the SOCKET parameter does not exist or became inactive in the 5-second interval.
System Action: The command is rejected.
User Response: Enter the ZSOCK command again and specify the SOCKET parameter with a socket descriptor that is valid.
See TPF Operations for more information about the ZSOCK command.
SOCK0027E | SOCKET-socket IS NOT THE RIGHT TYPE |
Where:
Explanation: The ZSOCK command was entered with the DATAFLOW and SOCKET parameters specified, but the socket descriptor specified with the SOCKET parameter is not a Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) socket in the TPF system.
System Action: The command is rejected.
User Response: Enter the ZSOCK command again and specify the SOCKET parameter with a socket descriptor that is either a TCP or UDP socket.
See TPF Operations for more information about the ZSOCK command.
SONS0001I | HALT TIMEOUT VALUE IS value |
Where:
Explanation: This message is a response to the ZSONS ALTER HALT and ZSONS DISPLAY HALT commands. This message shows the current CCSONS halt timeout value.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSONS ALTER HALT and ZSONS DISPLAY HALT commands.
SONS0002I | SCAN TIME VALUE IS value |
Where:
Explanation: This message is a response to the ZSONS ALTER SCAN command with the TIME parameter specified or the ZSONS DISPLAY SCAN command. This message shows the current CYED scan interval time value.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSONS ALTER SCAN and the ZSONS DISPLAY SCAN commands.
SONS0003I | ERROR LIMITS COUNT-value, INTERVAL-value |
Where:
Explanation: This message is a response to the ZSONS ALTER ERROR LIMITS and ZSONS DISPLAY ERROR LIMITS commands. This message shows the current CCSONS error limits threshold values.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSONS ALTER ERROR LIMITSand ZSONS DISPLAY ERROR LIMITS commands.
SONS0004I | hour.minute.second MOD USE DEV COR UNC |
Where:
Explanation: This is the normal response to the ZSONS command. A display of module numbers and error counts follows.
The following gap message that is not valid is entered within the display where appropriate:
modnum1INVALID UP TO MOD modnum2
Where:
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSONS commands.
SONS0005I | ALL ERROR COUNTERS CLEARED |
Explanation: This message indicates that all the error counters (correctable and irrecoverable) in the module file status table (MFST) section 1 were cleared.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSONS commands.
SONS0006I | modnum & FOLLOWING MODS OFFLINE |
Where:
Explanation: This message only occurs for an online-only request when no modules were found to be online, starting from the module number provided in the message text.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSONS commands.
SONS0007I | RCS STATE-CHANGE-PENDING TIMEOUT VALUE IS value |
Where:
Explanation: This message is a response to the ZSONS ALTER SCP and ZSONS DISPLAY SCP commands. This message shows the current RCS state change pending timeout value.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSONS ALTER SCP and ZSONS DISPLAY SCP commands.
SONS0052T | EITHER A MODULE NUMBER OR ALL REQUIRED |
Explanation: The ZSONS ALTER ERROR COUNTS command was entered without specifying the starting module number or the ALL parameter.
System Action: The command is rejected.
User Response: Specify one of the following, as appropriate:
See TPF Operations for more information about the ZSONS commands.
SONS0053T | THIS FUNCTION OF ZSONS IS VALID ONLY FOR THE BSS |
Explanation: The ZSONS command was entered to alter or display the halt or error limit values from a subsystem other than the basic subsystem (BSS).
The system only uses these values from the BSS. Therefore, only the BSS can display or set the values.
System Action: None.
User Response: Enter the ZSCONS command again from the BSS.
See TPF Operations for more information about the ZSONS commands.
SONS0054E | INVALID STARTING MODULE NUMBER |
Explanation: The ZSONS ALTER ERROR COUNTS or ZSONS DISPLAY ERROR COUNTS command was entered with a general file pseudo module number or a real-time disk symbolic module number that is not valid.
Also, if any module in the range specified for an ALTER request is offline, the function issues this message, stops processing of the command, and exits.
System Action: The command is rejected.
User Response: Enter the command again and specify a general file pseudo module number or a real-time disk symbolic module number that is valid.
See TPF Operations for more information about the ZSONS commands.
SPER0001I | PER TRACE keyword ACTIVE, ADDR address1 - address2 {Printer-printername Data-data} |
Where:
Explanation: This is the normal response to the ZSPER command with the DISPLAY parameter specified. If the DATA or PRINTER parameter is specified, the second line is displayed.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSPER command.
SPER0002I | PER TRACE STARTED |
Explanation: This is the normal response to the ZSPER command with the BRANCH, INSTRUCT, or STORE parameter specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSPER command.
SPER0003I | PER TRACE ENDED |
Explanation: This is the normal response to the ZSPER command with the END parameter specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSPER command.
SPER0005I | PER STOPPED -- INTERRUPT LIMIT EXCEEDED |
Explanation: This is an unsolicited message sent to the operator that indicates that the number of program event recording (PER) interrupts received in the last monitoring interval was greater than the limit allowed. The limit is set for a maximum of 10 PER interrupts during a 10 second interval.
System Action: The PER trace facility is stopped.
User Response: Enter the ZSPER command again with an address range that reduces the number of PER interrupts. This user response may be an iterative process.
Use of the DATA parameter does not affect this situation because the hardware PER interrupt occurs on the address whether or not DATA is specified.
See TPF Operations for more information about the ZSPER command.
SPER0006E | PER TRACE ALREADY ACTIVE |
Explanation: An attempt was made to start the program event recording (PER) monitoring while the PER trace facility was currently active.
System Action: The ZSPER command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZSPER command.
SPER0007E | PER TRACE NOT ACTIVE |
Explanation: The response to a ZSPER DISPLAY or ZSPER END command when the program event recording (PER) monitor is not active.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSPER command.
SPER0008E | BRANCH TRACE RESTRICTED TO PER-2 PROCESSORS |
Explanation: The response to an attempt to start PER BRANCH monitoring on a IBM System/370 processor. IBM System/370 processors provide PER storage alteration and instruction fetching functions in a TPF native environment.
IBM System/390 processors provide PER storage allocation, instruction fetching, and branching functions support in a TPF native environment.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSPER command.
SPER0009E | ADDRESS WRAP AROUND NOT SUPPORTED |
Explanation: The address plus the length specified by RANGE or INTO exceeded the maximum 31-bit address (X'7FFFFFFF'). This caused a wrap around condition, which is not supported.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZSPER command.
SPER0010E | INVALID ADDRESS |
Explanation: The high-order bit in the address specified by RANGE or INTO is on. This is not a valid 31-bit address. Any address X'80000000' or higher is not accepted.
System Action: None.
User Response: Enter an address that is less than X'80000000'.
See TPF Operations for more information about the ZSPER command.
SPER0011E | INVALID LENGTH |
Explanation: The ZSPER command was entered with the RANGE or INTO parameter but the length specified is zero.
System Action: The ZSPER command is rejected.
User Response: Enter the ZSPER command again and specify a length greater than zero.
See TPF Operations for more information about the ZSPER command.
SPER0012I | PER TRACE ACTIVE |
Explanation: This is a reminder message that the program event recording (PER) trace facility is active on this processor. The PER trace facility can degrade performance and should not be left on inadvertently.
System Action: None.
User Response: If the PER trace facility is no longer needed, then deactivate the trace by entering the ZSPER command with the END parameter specified.
See TPF Operations for more information about the ZSPER command.