gtpm5m2gMessages (Online)

SIPC-SPER

SIPC0001ITOTALS FOR HOST-procid

Where:

procid
The host processor ID.

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..

SIPC0001ICOUNTS FOR DEST-procid

Where:

procid
The destination processor ID.

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..

SIPC0002ICOUNTS 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.

SIPC0005IINTERVALS 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.

SIPC0006IMAXIMUM NUMBER OF PATHS ALTERED TO value

Where:

value
The value to which the maximum number of paths was altered.

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.

SIPC0007IIPC CLASS ALTERED TO value

Where:

value
The value to which the IPC class was altered.

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.

SIPC0008IIPC RESTART TIMEOUT VALUE ALTERED TO value

Where:

value
The value to which the IPC restart timeout was altered.

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.

SIPC0050EACTION 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:

  1. Determine the correct format of the ZSPIC ALTER command.
  2. Enter the command again by using the correct format.

See TPF Operations for more information about the ZSIPC ALTER command.

SIPC0052EINVALID 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:

  1. Determine the correct format of the ZSIPC DISPLAY command.
  2. Enter the command again by using the correct format.

See TPF Operations for more information about the ZSIPC DISPLAY command.

SIPC0053EINVALID 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:

  1. Determine the correct format of the ZSIPC ALTER command.
  2. Enter the command again by using the correct format.

See TPF Operations for more information about the ZSIPC ALTER command.

SIPC0054EINVALID 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:

  1. Ensure that a processor in the SDPS complex exists with the CPU ID that is being specified.
  2. Determine the correct format of the ZSIPC DISPLAY command.
  3. Enter the command again by using the correct format.

See TPF Operations for more information about the ZSIPC DISPLAY command.

SIPC0055EINVALID 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:

  1. Determine the correct format of the ZSIPC ALTER command.
  2. Enter the command again by using the correct format.

See TPF Operations for more information about the ZSIPC ALTER command.

SIPC0071EIPC 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.

SIPC0071TIPC 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.

SIPC0072EINVALID 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:

  1. Determine the correct format of the ZSIPC ALTER command.
  2. Enter the command again by using the correct format.

See TPF Operations for more information about the ZSIPC ALTER command.

SIPC0073EINVALID 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:

  1. Determine the correct format of the ZSIPC ALTER command.
  2. Enter the command again by using the correct format.

See TPF Operations for more information about the ZSIPC ALTER command.

SIPC0074EUNABLE 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.

SIPC0075EUNABLE 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.

SIPC0076EINTERVALS 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:

  1. Determine the correct format of the ZSIPC ALTER command.
  2. Enter the command again by using the correct format and specify a new TIME or a new interval as necessary.

See TPF Operations for more information about the ZSIPC ALTER command.

SIPC0077EIPC 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:

  1. Determine the correct format of the ZSIPC ALTER command.
  2. Enter the command again and specify a restart timeout value of 0 through 65535.

See TPF Operations for more information about the ZSIPC ALTER command.

SMTP0001ESMTPD: 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:

  1. Enter ZSOCK INACT LPORT-25 to deactivate the socket using well-known port 25.
  2. Enter ZINET START S-SMTP to start the SMTP server again.

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.

SMTP0002ESMTPD: FAILED TO LISTEN TO SMTPD PORT: CODE errno

Where:

errno
The value set in errno.

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:

  1. Check the value in errno to determine the cause of the problem.
  2. Correct the problem.
  3. Enter ZINET START S-SMTP to start the SMTP server again.

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.

SMTP0003ESMTPD: SELECT FAILED: CODE errno

Where:

errno
The value set in errno.

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:

  1. Enter ZINET STOP S-SMTP to stop the SMTP server.
  2. Check the value in errno to determine the cause of the problem.
  3. Correct the problem.
  4. Enter ZINET START S-SMTP to start the SMTP server again.

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.

SMTP0004ESMTPD: FAILED TO ACCEPT INCOMING CONNECTION: CODE errno

Where:

errno
The value set in errno.

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:

  1. Enter ZMAIL STATUS to determine if the SMTP server is still running.
  2. If the SMTP server is still running, enter ZINET STOP S-SMTP to stop the server; otherwise, go to step 3.
  3. Check the value in errno to determine the cause of the problem.
  4. Correct the problem.
  5. Enter ZINET START S-SMTP to start the SMTP server again.

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.

SMTP0005ESMTPD: USE ZMAIL START OR ZMAIL START ACCEPT TO START SMTP

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.

SNAP0001ICPU-cpuid SS-ssname SSU-ssu IS-istreamnum PSW-psw PGM-progname CODE-errorcode TERM-ta

Where:

cpuid
CPU ID

ssname
The subsystem name.

ssu
The subsystem user (SSU).

istreamnum
The I-stream, which is displayed as a decimal number.

psw
The program status word (PSW).

progname
The program name.

errorcode
Snapshot error code. The first character is the prefix.

ta
The terminal address (TA).

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.

SNAP0002WSNAPC TAPE WRITE ABORTED, NO tape TAPE AVAILABLE.

Where:

tape
The system dump tape (RTL or RTA).

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.

SNDA0001IREQUEST 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.

SNDA0007EAPPLICATION 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.

SNDA0009EINVALID 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.

SNDA0010ESYSTEM 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:

  1. Cycle the TPF system to NORM state.
  2. Enter the ZSNDA command again.

See TPF Operations for more information about the ZSNDA command.

SNDA0012EOPERAND 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.

SNDA0013ENO 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:

  1. Enter the command again.
  2. If the problem continues, see your coverage programmer.

See TPF Operations for more information about the ZSNDA command.

SNDA0016ETEXT 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:

  1. Shorten the text to less than 255 characters.
  2. Enter the ZSNDA command again.

See TPF Operations for more information about the ZSNDA command.

SNDA0018EAPPLICATION 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.

SNDU0001IREQUEST 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.

SNDU0009EINVALID 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.

SNDU0010ESYSTEM 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:

  1. Cycle the TPF system to NORM state.
  2. Enter the ZSNDU command again.

See TPF Operations for more information about the ZSNDU command.

SNDU0012EOPERAND 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.

SNDU0013ENO 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:

  1. Enter the ZSNDU command again.
  2. If the problem continues, see your coverage programmer.

See TPF Operations for more information about the ZSNDU command.

SNDU0016ETEXT 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:

  1. Shorten the text to less than 255 characters.
  2. Enter the ZSNDU command again.

See TPF Operations for more information about the ZSNDU command.

SNDU0019EINVALID 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.

SNMP0001ISNMP 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.

SNMP0002ESNMP 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:

  1. Create the snmp.cfg SNMP configuration file.
  2. Transfer the file to the /etc directory in the TPF file system.
  3. Enter the ZSNMP command again with the REFRESH parameter specified to apply the changes.

See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.

SNMP0003EERROR OPENING SNMP CONFIGURATION FILE, ERRNO-number

Where:

number
The 1-byte number that indicates the error in the errno.h file.

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:

  1. Enter ZFILE ls -l to allow the /etc/snmp.cfg SNMP configuration file to get the current file access permission settings.
  2. If the configuration file does not have read permission set, do the following:
    1. Enter ZFILE chmod to set read permission for the /etc/snmp.cfg SNMP configuration file.
    2. Enter the ZSNMP command with the REFRESH parameter specified to apply the changes.
  3. If the configuration file has read permission set, see your system programmer.

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.

SNMP0004EDESTINATION SNMP MANAGER ADDRESS hostname COULD NOT BE RESOLVED

Where:

hostname
The first 30 characters of the Simple Network Management Protocol (SNMP) host name that could not be resolved.

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.

SNMP0005EDESTINATION 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:

  1. If the community name is not coded, code a valid value for the COMMNAME keyword in the /etc/snmp.cfg SNMP configuration file.
  2. Enter the ZSNMP command again with the REFRESH parameter specified to apply the changes.

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:

  1. If the system object identifier is not coded, code a valid value for the SYSOBJID keyword in the /etc/snmp.cfg SNMP configuration file.
  2. Enter the ZSNMP command again with the REFRESH parameter specified to apply the changes.

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:

ipaddress
The Internet Protocol (IP) address of the Simple Network Management Protocol (SNMP) destination manager.

error
The error number received on the Internet control message protocol (ICMP) message that is returned from the SNMP destination manager.

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:

  1. Code the TCP/IP native stack support parameters in the SNAKEY macro.
  2. Reassemble keypoint record 2 (CTK2) against the SNAKEY macro.
  3. Reload CTK2.
  4. IPL the TPF system.
  5. Enter the ZSNMP command again with the REFRESH parameter specified to apply the changes.

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:

number
The line in the /etc/snmp.cfg Simple Network Management Protocol (SNMP) configuration file where the error was found.

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:

  1. Locate the line in the /etc/snmp.cfg SNMP configuration file that contains the error.
  2. Ensure that the length of the value of the keyword in the /etc/snmp.cfg SNMP configuration file is from 1 to 255 characters.
  3. Ensure that the keyword names are valid.
  4. Enter the ZSNMP command again with the REFRESH parameter specified to apply the changes.

See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.

SNMP0013ESYSTEM 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:

  1. Cycle the TPF system to CRAS state or higher.
  2. Enter the ZSNMP command again with the REFRESH parameter specified to apply the changes.

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:

number
The line in the /etc/snmp.cfg Simple Network Management Protocol (SNMP) configuration file where the error was found.

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:

  1. Locate the line in the /etc/snmp.cfg SNMP configuration file that contains the error.
  2. Ensure that the system object identifier begins with 1.3.
  3. Enter the ZSNMP command again with the REFRESH parameter specified to apply the changes.

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:

  1. Create the snmp.cfg SNMP configuration file.
  2. Transfer the file to the /etc directory in the TPF file system.
  3. Enter the ZSNMP command with the REFRESH parameter specified to apply the changes.

See TPF Operations for more information about the ZSNMP command. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.

SNMP0016ESNMP 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:

  1. Delete the Internet daemon from the non-BSS server by entering the ZINET DELETE command.
  2. Define the SNMP server to the Internet daemon in the BSS by entering the ZINET ADD command.
  3. Start the SNMP server in the BSS by entering the ZINET START command.

See TPF Operations for more information about the ZINET commands. See TPF Transmission Control Protocol/Internet Protocol for more information about SNMP agent support.

SNMP0017EERROR RECEIVING SNMP PROTOCOL DATA UNIT, SOCKERRNO-number

Where:

number
The socket error number.

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:

  1. Determine the cause of the socket error.
  2. Correct the error.

See TPF Transmission Control Protocol/Internet Protocol for more information about socket errors and SNMP agent support.

SNMP0018ISNMP MIB RETRIEVAL DISPLAY

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.

SNMP0019ISNMP MIB RETRIEVAL CONTENTS SENT TO FILE file

Where:

file
The name of the file in which the Management Information Base (MIB) variables were saved.

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.

SNMP0020ESNMP ERROR error RETRIEVING MIB VALUE mibval

Where:

error
One of the following:

NOSUCHNAME
The specified Management Information Base (MIB) variable does not exist.

GENERR
An error occurred while encoding the MIB value.

mibval
The specified MIB variable.

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.

SNMP0021EERROR OPENING filename - ERROR errno

Where:

filename
The name of the file specified on the command.

errno
The error number that was returned from the open function.

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:

  1. Examine the return codes from the open function to determine why the error occurred.
  2. Correct the error.
  3. Enter the ZSNMP command again with the DISPLAY and FILE parameters specified.

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.

SNMP0022EERROR WRITING TO filename - ERROR errno

Where:

filename
The name of the file specified on the command.

errno
The error number that was returned from the write function.

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:

  1. Examine the return codes from the write function to determine why the error occurred.
  2. Correct the error.
  3. Enter the ZSNMP command again with the DISPLAY and FILE parameters specified.

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.

SOCK0001EIP TABLE FULL - OFFLOAD RESTART ABORTED, ADAPTER ID-adapterid PATH ID-pathid

Where:

adapterid
The adapter block address for the TCP/IP offload device.

pathid
The path ID for the TCP/IP offload device.

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:

  1. Increase the value of the CLAWIP parameter in the SNAKEY macro.
  2. Reassemble keypoint record 2 (CTK2) against the SNAKEY macro.
  3. Reload CTK2.
  4. IPL the TPF system again.

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.

SOCK0002EADAPTER ID-adapterid PATH ID-pathid OFFLOAD RESTART RESPONSE ERROR

Where:

adapterid
The adapter block address for the TCP/IP offload device.

pathid
The path ID for the TCP/IP offload device.

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:

  1. Check the status of the TCP/IP offload device and restart the offload application if necessary.
  2. Send additional messages through the TCP/IP offload device again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the claw_send function.

SOCK0003ESOCKET DESCRIPTOR-filedescriptor ADDRESS-address FILE DESCRIPTOR RELEASE ERROR

Where:

filedescriptor
The socket number for the file descriptor.

address
The address of the file descriptor.

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:

  1. Process the 009102 system error dump.
  2. Have your system programmer review the system error dump to determine the cause of the problem and correct the error.

SOCK0004EADAPTER ID-adapterid PATH ID-pathid ADDRESS-address IP ENTRY RELEASE ERROR

Where:

adapterid
The adapter block address for the TCP/IP offload device.

pathid
The path ID for the TCP/IP offload device.

address
The address of the Internet Protocol (IP) entry.

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:

  1. Process the 009102 system error dump.
  2. Have your system programmer review the system error dump to determine the cause of the problem and correct the error.

See TPF Transmission Control Protocol/Internet Protocol for more information about the claw_disconnect function.

SOCK0010ISOCKET 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.

SOCK0011ISOCKET 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.

SOCK0012ESYSTEM 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:

  1. Enter the ZCYCL command to cycle the TPF system to CRAS state or above.
  2. Enter the ZSOCK command again.

See TPF Operations for more information about the ZCYCL and ZSOCK commands.

SOCK0013ETCP/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:

  1. In keypoint record 2 (CTK2), update SNAKEY parameters MAXSOCK, MAXIPCCW, IPMTSIZE, IPRBUFFS, and IPRBUFSZ to define TCP/IP native stack support.
  2. Assemble CTK2.
  3. Load CTK2 to the TPF system.
  4. Perform an initial program load (IPL) of the TPF system.
  5. Enter the ZTTCP DEFINE command with the IP parameter specified to define local IP addresses for the channel-attached IP routers.
  6. Enter the ZTTCP DEFINE command with the IP and SDA parameters specified to define local symbolic device addresses (SDAs) for the channel-attached IP routers.
  7. Enter the ZTTCP ACTIVATE command with the ALL or SDA parameter specified to activate links to the channel-attached IP routers.
  8. Enter the ZSOCK command again.

See TPF Operations for more information about the ZSOCK, ZTTCP ACTIVATE, and ZTTCP DEFINE commands.

SOCK0014EREQUIRED 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.

SOCK0015Esockdesc OUT OF ALLOWED RANGE OF SOCKET DESCRIPTORS

Where:

sockdesc
The Transmission Control Protocol/Internet Protocol (TCP/IP) native stack support socket descriptor.

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.

SOCK0016ISOCKET sockdesc IS NOW INACTIVE

Where:

sockdesc
A Transmission Control Protocol/Internet Protocol (TCP/IP) native stack support socket descriptor.

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.

SOCK0017ESOCKET sockdesc IS NOT ACTIVE

Where:

sockdesc
A Transmission Control Protocol/Internet Protocol (TCP/IP) native stack support socket descriptor.

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.

SOCK0018IINACT COMPLETE, numsocks SOCKETS CLOSED

Where:

numsocks
The number of sockets closed.

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.

SOCK0019IBEGIN 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.

SOCK0020EREQUEST 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.

SOCK0021ISOCKET 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.

SOCK0022ENO 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.

SOCK0023EINCORRECT VALUE value NOT SUPPORTED FOR keyword

Where:

value
The value specified for the keyword.

keyword
The requested keyword.

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.

SOCK0024IBEGIN 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.

SOCK0025ISOCKET 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.

SOCK0026ESOCKET-socket DOES NOT EXIST

Where:

socket
The socket descriptor.

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.

SOCK0027ESOCKET-socket IS NOT THE RIGHT TYPE

Where:

socket
The socket descriptor.

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.

SONS0001IHALT TIMEOUT VALUE IS value

Where:

value
Decimal value

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.

SONS0002ISCAN TIME VALUE IS value

Where:

value
Decimal value

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.

SONS0003IERROR LIMITS COUNT-value, INTERVAL-value

Where:

value
Decimal values

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.

SONS0004Ihour.minute.second MOD USE DEV COR UNC

Where:

hour
The hours.

minute
The minutes.

second
The seconds.

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:

modnum1
The first module number that is not valid.

modnum2
The last module number that is not valid (or is not used) for the module number gap that is not valid..

System Action: None.

User Response: None.

See TPF Operations for more information about the ZSONS commands.

SONS0005IALL 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.

SONS0006Imodnum & FOLLOWING MODS OFFLINE

Where:

modnum
The input module number.

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.

SONS0007IRCS STATE-CHANGE-PENDING TIMEOUT VALUE IS value

Where:

value
Decimal value

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.

SONS0052TEITHER 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.

SONS0053TTHIS 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.

SONS0054EINVALID 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.

SPER0001IPER TRACE keyword ACTIVE, ADDR address1 - address2 {Printer-printername Data-data}

Where:

keyword
Is replaced by the appropriate keyword for the currently active program event recording (PER) trace facility. The valid keywords are BRANCH, INSTRUCT, and STORE.

address1 - address2
Represents the address range.

printername
The printer name specified by the operator when PER is activated. The printer information is installation specific.

data
Data specified by the operator when PER is activated.

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.

SPER0002IPER 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.

SPER0003IPER 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.

SPER0005IPER 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.

SPER0006EPER 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:

  1. End the active PER trace facility.
  2. Enter the ZSPER command again.

See TPF Operations for more information about the ZSPER command.

SPER0007EPER 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.

SPER0008EBRANCH 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.

SPER0009EADDRESS 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.

SPER0010EINVALID 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.

SPER0011EINVALID 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.

SPER0012IPER 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.