gtpm5m27Messages (Online)

PAGE-PRSE

PAGE0050INO OUTSTANDING CONTINUATION

Explanation: This message is issued if you enter the ZPAGE command more than one minute after being prompted for output continuation. Any pending output from the original message is no longer available.

System Action: None.

User Response: Enter the original command again (this is the message that prompted for output continuation). When prompted again to enter the ZPAGE command, be sure to specify it within one minute of being prompted.

See TPF Operations for more information about the ZPAGE command.

PATH0010IZPATH PROCESS COMPLETED ON VALID DASD SDA

Explanation: This is a normal response for the ZPATH command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPATH command.

PATH0015ISTATUS DISPLAY FOLLOWS

Explanation: This is the normal response to the ZPATH command with the DISPLAY parameter specified.

This message is followed by one of two displays that show one of the following:

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPATH command and for an example of the informational display.

PATH0016ISTATUS DISPLAY FOLLOWS (DOWN PATHS ONLY)

Explanation: This is the normal response to the ZPATH command with the DISPLAY parameter specified.

This message is followed by one of two displays that show one of the following:

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPATH command and for an example of the informational display.

PATH0017ISTATUS DISPLAY FOLLOWS (ALL DOWN PATHS) THE FOLLOWING PATHS ARE DOWN: path1 path2 path3 path4...

Where:

path1, path2, path3, path4
The DASD paths that are down.

Explanation: This is the normal response to the ZPATH command with the DISPLAY DOWN parameter specified. This message displays all the paths in the TPF system that are down.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPATH command.

PATH0020IMAXIMUM NUMBER OF DEVICES DISPLAYED -- TO DISPLAY MORE: REENTER ZPATH COMMAND WITH NEW PARAMETERS

Explanation: The display function only displays a certain number of lines. It has reached this limit but has not processed every device in the specified range.

System Action: None.

User Response: Enter the command again and specify a range that begins where the display ended.

See TPF Operations for more information about the ZPATH command.

PATH0025ITHERE ARE NO PATHS DOWN

Explanation: This is the normal response to the ZPATH command with the DISPLAY DOWN parameter specified when no paths are down to any device in the TPF system.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPATH command.

PATH0029IEND OF DISPLAY

Explanation: This is the normal response to the ZPATH command with the DISPLAY parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPATH command.

PATH0051TINVALID RANGE SPECIFIED

Explanation: The ZPATH command was entered, but the first symbolic device address (SDA) specified is greater than the second SDA.

System Action: The ZPATH command is rejected.

User Response: Do the following:

  1. Check the SDA range.
  2. Enter the command again.

See TPF Operations for more information about the ZPATH command.

PATH0052TALREADY PROCESSING ZPATH

Explanation: The ZPATH command was entered while a previous request was in progress.

System Action: The ZPATH command is rejected.

User Response: Do the following:

  1. Wait for completion of the previous request.
  2. Enter the command again.

See TPF Operations for more information about the ZPATH command.

PATH0053TINPUT SDA ALL INVALID

Explanation: This message is issued to warn you that all the input symbolic device addresses (SDAs) were not valid.

System Action: The ZPATH command is rejected.

User Response: Do the following:

  1. Determine the correct DASD SDA to bring the path online.
  2. Enter the command again.

See TPF Operations for more information about the ZPATH command.

PATH0054ISOME NON-DASD SDA FOUND

Explanation: This message is issued to warn you that in the input symbolic device address (SDA) range, some SDAs were not DASD.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPATH command.

PATH0055IINPUT SDA NOT MOUNTED OR NON-DASD

Explanation: This message is issued in two cases:

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZPATH command.

PATH0056IINVALID PARAMETERS ENTERED

Explanation: The ZPATH command was not specified correctly.

System Action: The ZPATH command was rejected.

User Response: Do the following:

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

See TPF Operations for more information about the ZPATH command.

PLMT0002IQUEUE FOR lniata PURGED TO TAPE PLM, MSG CNT -- msgcount

Where:

lniata
The requested line number, interchange address, and terminal address (LNIATA).

msgcount
The message count.

Explanation: The XLMA message queue for the requested LNIATA/LEID was purged to the PLM tape.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PLMT0003INO MESSAGES ON QUEUE

Explanation: There are no messages on the XLMA queue to purge or repeat.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PLMT0004IQUEUE FOR lniata PURGED, MSG CNT -- msgcount

Where:

lniata
The requested line number, interchange address, and terminal address (LNIATA).

msgcount
The message count.

Explanation: The XLMA message queue for the requested LNIATA/LEID was purged without a PLM tape.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PLMT0010WNOT ALLOWED BELOW CRAS STATE

Explanation: The TPF system must be computer room agent set (CRAS) state or above before the request can be processed.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PLMT0011EINVALID LNIATA -- lniata

Where:

lniata
The line number, interchange address, and terminal address (LNIATA) that is not valid.

Explanation: The LNIATA/LEID specified in the command is not valid or could not be found in the system network tables.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PLMT0012EINVALID FORMAT

Explanation: The format of the ZPLMT command is incorrect to the input line number, interchange address, and terminal address (LNIATA) or or contains characters that are not valid.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PLMT0013EINVALID RID

Explanation: The output message transmitter (OMT) message purge routines detected a resource identifier (RID) error. This may indicate a possible database problem.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PLMT0015ENODE NOT A PRINTER

Explanation: The pseudo line number, interchange address, and terminal address (LNIATA) specified in the command is not a printer.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PLMT0018TUNABLE TO RETRIEVE NCB FOR lniata

Where:

lniata
The requested line number, interchange address, and terminal address (LNIATA).

Explanation: The node control block (NCB) for the requested LNIATA/LEID could not be retrieved.

System Action: The message queue is not purged and processing is ended.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PLMT0019TUNABLE TO RETRIEVE XLMA FOR lniata

Where:

lniata
The line number, interchange address, and terminal address (LNIATA).

Explanation: The XLMA record for the requested LNIATA could not be retrieved.

System Action: The message queue is not purged and processing is ended.

User Response: None.

See TPF Operations for more information about the ZPLMT command.

PMIG0001IPOOL CONVERSION COMPLETE

Explanation: This is the normal response to the ZPMIG command with the CONVERT parameter specified. The conversion to the new pool format provided by 32-way loosely coupled pool support is completed. The pool data structures that reside in storage for each of the migrated processors, and that are stored on DASD, are in 32-way loosely coupled pool support format.

System Action: The conversion process is completed. All pool data structures in storage and on DASD are in 32-way loosely coupled pool support format.

User Response: None.

See TPF Operations for more information about the ZPMIG command.

PMIG0002IPOOL CONVERSION FALLBACK COMPLETED

Explanation: This is a normal response to the ZPMIG command with the FALLBACK parameter specified. Fallback from the 32-way loosely coupled pool support format is completed.

System Action: All pool data structures that reside on DASD are in the pool expansion (PXP) format.

User Response: None.

See TPF Operations for more information about the ZPMIG command.

PMIG0003TUNABLE TO CONVERT DUE TO UNMIGRATED PROCESSORS

Explanation: The ZPMIG command was entered with the CONVERT parameter specified to begin pool conversion. Pool conversion changes the pool data structures from pool expansion (PXP) format to 32-way loosely coupled pool format. However, pool conversion is not completed because one or more of the active processors do not have 32-way loosely coupled pool support installed. The pool data structures cannot be converted until all active processors in the complex are IPLed from an image containing 32-way loosely coupled pool support.

System Action: The pool conversion process ends. All pool data structures on DASD remain in PXP format.

User Response: Do the following:

  1. Enter the ZDFPC command on each active processor in the complex. This ensures that all pool data structures in storage on each processor are in 32-way loosely coupled pool format.
  2. Enter the ZPMIG command with the STATUS parameter specified to display the migration state for each active processor in the complex. The migration state can be MIGRATED, UNMIGRATED, or INACTIVE.
  3. IPL all processors listed as UNMIGRATED from an image containing 32-way loosely coupled pool support.
  4. Enter the ZPMIG command with the STATUS parameter specified on each active processor in the complex. If message PMIG0011I is returned, the processor on which the command is entered is using 32-way loosely coupled pool support. If any other message is returned, the processor is not using 32-way loosely coupled pool support and must be re-IPLed using an image containing 32-way loosely coupled pool support before you can enter the ZPMIG command with the CONVERT parameter.
  5. Enter the ZPMIG command with the CONVERT parameter specified to convert the pool data structures on DASD to 32-way loosely coupled pool format.

See TPF Operations for more information about the ZDFPC and ZPMIG commands. See TPF Migration Guide: Program Update Tapes for more information about pool migration and pool conversion.

PMIG0006WPOOL DATA STRUCTURES ARE ALREADY IN THE REQUESTED STATE

Explanation: This is a normal response to the ZPMIG command with the CONVERT or FALLBACK parameter specified. You attempted to do one of the following:

System Action: The command ends and the ECB exits. The pool data structures are not changed.

User Response: Do the following:

  1. Verify that each active processor in the complex is in the correct migration state by entering the ZPMIG command with the STATUS parameter specified. The migration state can be MIGRATED, UNMIGRATED, or INACTIVE.
  2. Do one of the following:

See TPF Operations for more information about the ZPMIG command.

PMIG0007TPARAMETER IS NOT VALID

Explanation: One of the following errors occurred:

System Action: The help message for the ZPMIG command is displayed showing you the list of valid parameters that you can specify.

User Response: Enter the ZPMIG command again and specify the correct parameter.

See TPF Operations for more information about the ZPMIG command.

PMIG0008TPOOL DATA STRUCTURES ARE IN AN INVALID CONVERSION STATE

Explanation: The pool data structures are in a pool conversion state that is not possible at the point the error was detected.

System Action: The function ends and the ECB exits.

User Response: Verify the pool conversion state of the pool data structures and the pool data structure conversion bits set in keypoint 9 (CTK9).

PMIG0009TPOOL CONVERSION PROCESSING IS TERMINATED

Explanation: This is a normal response to the ZPMIG command with the CONVERT or FALLBACK parameter specified. An error occurred during pool conversion and pool conversion has ended.

System Action: Pool conversion ends and the ECB exits.

User Response: See the error message that was displayed before this message because it provides information about the problem with the pool conversion process.

See TPF Operations for more information about the ZPMIG command.

PMIG0011I32-WAY LC POOL MIGRATION STATUS THE POOL DATA STRUCTURES ARE state PROCESSOR procid STATUS status

Where:

state
The conversion state of the pool data structures, which must be one of the following:

procid
The processor ID.

status
The current status of each processor in the complex. Valid status is:

Explanation: This is a normal response to the ZPMIG command with the STATUS parameter specified. Information is provided about the migration status of 32-way loosely coupled pool support for each processor in the complex.

System Action: The migration and conversion information for each processor in the complex is displayed.

User Response: None.

See TPF Operations for more information about the ZPMIG command.

PMIG0012EUNABLE TO FIND #CY2KT

Explanation: An error occurred during pool conversion while attempting to find the #CY2KT fixed file record type.

System Action: Pool conversion ends and the ECB exits. All the pool data structures on DASD remain in pool expansion (PXP) format.

User Response: Do the following:

  1. Verify that the #CY2KT fixed file record type is correctly defined in the FACE table (FCTB) because it may be missing from the FACE table or not defined with enough ordinals.
  2. Correctly define the #CY2KT fixed file record type and generate and load a new FACE table.

See TPF Operations for more information about the ZPMIG command.

PMIG0013EUNABLE TO FIND #STPUR

Explanation: An error occurred during pool conversion while attempting to find the #STPUR fixed file record type.

System Action: Pool conversion ends and the ECB exits. All pool data structures on DASD remain in pool expansion (PXP) format.

User Response: Do the following:

  1. Verify that the #STPUR fixed file record type is correctly defined in the FACE table (FCTB) for each processor in the complex because it may be missing from the FACE table or not defined with enough ordinals.
  2. Correctly define the #STPUR fixed file record type and generate and load a new FACE table.

See TPF System Generation for more information about the #STPUR fixed file record and TPF Operations for more information about the ZPMIG command.

PMIG0014EUNABLE TO FIND #STPCR

Explanation: An error occurred during pool conversion fallback while attempting to find the #STPCR fixed file record type.

System Action: Pool conversion fallback ends and the ECB exits. All the pool data structures on DASD remain in 32-way loosely coupled pool format.

User Response: Do the following:

  1. Verify that the #STPCR fixed file record type is correctly defined in the FACE table (FCTB) because it may be missing from the FACE table or not defined with enough ordinals.
  2. Correctly define the #STPCR fixed file record type and generate and load a new FACE table.

See TPF System Generation for more information about the #STPCR fixed file record and see TPF Operations for more information about the ZPMIG command.

PMIG0015EFALLBACK NOT ALLOWED WITH MORE THAN 8 PROCESSORS

Explanation: The ZPMIG command was entered with the FALLBACK parameter specified in a loosely coupled complex with more than eight processors generated. This is not allowed because processor data beyond the eighth processor would be lost.

System Action: Pool data structures remain unchanged and the entry control block (ECB) exits.

User Response: None.

See TPF Operations for more information about the ZPMIG command.

POP30001EPOP3D: FAILED TO BIND TO POP3D PORT

Explanation: The Post Office Protocol (POP) server was unable to bind to well-known port 110. This indicates that another socket is using this port.

System Action: The entry control block (ECB) exits and the POP server stops.

User Response: Do the following:

  1. Enter ZSOCK INACT LPORT-110 to deactivate the socket using well-known port 110.
  2. Enter ZINET START S-POP3 to start the POP 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 POP server.

POP30002EPOP3D: FAILED TO LISTEN TO POP3D PORT: CODE errno

Where:

errno
The value set in errno.

Explanation: The Post Office Protocol (POP) server was unable to process the listen function for the socket descriptor.

System Action: The entry control block (ECB) exits and the POP 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-POP3 to start the POP 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 POP server.

POP30003EPOP3D: SELECT FAILED: CODE errno

Where:

errno
The value set in errno.

Explanation: The Post Office Protocol (POP) 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 POP server is stopped.

User Response: Do the following:

  1. Enter ZINET STOP S-POP3 to stop the POP server.
  2. Check the value in errno to determine the cause of the problem.
  3. Correct the problem.
  4. Enter ZINET START S-POP3 to start the POP 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 POP server.

POP30004EPOP3D: FAILED TO ACCEPT INCOMING CONNECTION: CODE errno

Where:

errno
The value set in errno.

Explanation: The Post Office Protocol (POP) 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 POP server is still running.
  2. If the POP server is still running, enter ZINET STOP S-POP3 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-POP3 to start the POP 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 POP server.

PROT0000EINVALID MSG FORMAT

Explanation: Too many or too few input characters were specified on the ZPROT command request.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0001EINVALID FUNCTION CODE

Explanation: The secondary action code specified was not recognized on the ZPROT command request.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0002EINVALID RESOURCE TYPE

Explanation: The resource type was not specified as UT or TP on the ZPROT command request.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0003EINVALID DEVICE ADRS/NAME

Explanation: A tape device address or utility name that is not valid was specified on the ZPROT command request.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0004EINVALID FUNCTION FOR TAPE RESOURCE

Explanation: Display (DSP) is the only valid tape function available for a ZPROT command request.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0005EDEVICE/UTILITY NOT IN PROT

Explanation: The device or utility is not in the processor resource ownership table (PROT).

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0006EPROT IS FULL

Explanation: The processor resource ownership table (PROT) is full.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0008ESS INACTIVE

Explanation: The subsystem name specified for a ZPROT utility (UT) function was found to be marked inactive.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0009EDEVICE ADRS RANGE ERROR

Explanation: A tape device address range greater than 255 devices was specified on a ZPROT command request.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0013EUTILITY IS ACTIVE

Explanation: A request to release the BUFC utility was made but the BUFC utility was found to be currently active on the TPF system.

System Action: The ZPROT command is rejected.

User Response: Wait for the BUFC utility to complete before trying to release from this processor.

See TPF Operations for more information about the ZPROT command.

PROT0014EPROT IS EMPTY

Explanation: The processor resource ownership table (PROT) is empty.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0015EPROC NOT IN PID TABLE

Explanation: The processor identification indicated for a utility owner was not found in the system processor ID (PID) table.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0018ERESTRICTED BELOW 1052

Explanation: An attempt was made to the Display (DSP) utility or tape information from the processor resource ownership table (PROT) for all processors while the TPF system was cycling to 1052 state.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0020EINVALID SUBSYSTEM NAME

Explanation: The subsystem name specified on a ZPROT request is not a valid subsystem defined to the TPF system.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0021EENTRY ALREADY IN PROT

Explanation: A request was made to add a utility name to the processor resource ownership table (PROT) but the utility name was already defined in the PROT.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0022EDEVICE/UTILITY CURRENTLY ASSIGNED

Explanation: A request was made to delete a utility name from the processor resource ownership table (PROT) but the utility name is currently assigned.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0023EREQUEST VALID FROM BASIC SUBSYSTEM ONLY

Explanation: The request is only valid from the basic subsystem (BSS).

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0050IPROT DSP UT parm

Where:

parm
Is one of the following:

Explanation: This is a normal message for the ZPROT command. This message is followed by a display indicating the processors and their system utilities or the processor associated with a specified entry in the processor resource ownership table (PROT).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0051APROT parm1 UT utilname subsname parm2

Where:

parm1
Is ASN or REL.

utilname
The utility name.

subsname
The subsystem name.

parm2
Is ASSIGNED or RELEASED.

Explanation: This is the normal message for the ZPROT command with the ASN or REL parameter.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0052IPROT DSP TP parm

Where:

parm
Is one of the following:

Explanation: This is the normal response to the ZPROT command. The display that follows this message depends on the parameter that is specified:

If an asterisk (*) is displayed, this indicates that the device address is not in PROT.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0053APROT parm1 UT utilname subsname parm2

Where:

parm1
Is ADD or DEL.

utilname
The utility name.

subsname
The subsystem name.

parm2
Is ADDED or DELETED.

Explanation: This is the normal message for the ZPROT command with the ADD or DEL parameter.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0054EPROT REL UT utilname subsname RELEASE AN UNASSIGNED ENTRY

Where:

utilname
The utility name.

subsname
The subsystem name.

Explanation: A request to release ownership of a utility is issued but the utility is not found in the processor resource ownership table (PROT).

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0055EPROT ASN UT utilname subsname ALREADY ASSIGNED TO THE PROCESSOR

Where:

utilname
The utility name.

subsname
The subsystem name.

Explanation: A request to assign ownership of a utility is made but the utility is already owned by the requesting processor.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT command.

PROT0056EPROT ASN UT utilname subsname ALREADY ASSIGNED TO ANOTHER PROCESSOR

Where:

utilname
The utility name.

subsname
The subsystem name.

Explanation: A request to assign ownership of a utility is made but the utility is already owned by another processor.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT commands. See TPF Main Supervisor Logic for more information.

PROT0057EPROT REL UT utilname subsname NOT RELEASED-PROC ACTIVE

Where:

utilname
The utility name.

subsname
The subsystem name.

Explanation: A request to release ownership of a utility is issued but the utility is found to be owned by another currently active processor.

System Action: The ZPROT command is rejected.

User Response: None.

See TPF Operations for more information about the ZPROT commands. See TPF Main Supervisor Logic for more information.

PROT0058EPOOL UTILITY CAN ONLY BE ASSIGNED TO ONE OF THE FIRST 8 PROCESSORS IN THE COMPLEX

Explanation: The ZPROT command was entered with the ASN parameter and the POOL utility specified. The command was entered on a processor other than one of the first eight processors in the loosely coupled complex. The owner of the POOL utility can only be one of the first eight processors in a loosely coupled complex.

System Action: The ZPROT command is rejected.

User Response: Enter the ZPROT command with the ASN parameter and the POOL utility specified on one of the first eight processors in the loosely coupled complex.

See TPF Operations for more information about the ZPROT command.

PRSE0001Estring - TOO MANY PARAMETERS ENTERED parameters

Where:

string
The string that identifies the function calling IPRSE_parse.

parameters
May contain additional information regarding the error. It may contain LAST VALID PARAMETER IS and a parameter.

Explanation: Too many parameters were specified in the input string during the parsing of the string for the cccc function.

System Action: None. Processing is completed for parsing the input string.

User Response: Enter the input string again with the appropriate number of parameters.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.

PRSE0004Estring - INVALID USE OF PERIOD.

Where:

string
The string that identifies the function calling IPRSE_parse.

Explanation: The period (.) was used in a way that is deemed illegal by the parser.

System Action: None. Processing is completed for parsing the input string.

User Response: Enter the input string again correctly.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.

PRSE0005Estring - INVALID ALPHANUMERIC CHARACTER

Where:

string
The string that identifies the function calling IPRSE_parse.

Explanation: An alphanumeric character was required by a parameter during the parsing of the string for the cccc function but a non-alphanumeric character was specified

System Action: Processing is completed for parsing the input string.

User Response: Enter the input string again correctly.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.

PRSE0006Estring - INVALID DECIMAL CHARACTER

Where:

string
The string that identifies the function calling IPRSE_parse.

Explanation: A decimal character was required by a parameter during the parsing of the string for the cccc function but a non-decimal character was specified.

System Action: Processing is completed for parsing the input string.

User Response: Enter the input string again correctly.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.

PRSE0007Estring - INVALID CHARACTER

Where:

string
The string that identifies the function calling IPRSE_parse.

Explanation: An uppercase letter was required by a parameter during the parsing of the string for the cccc function but a non-uppercase letter was specified.

System Action: Processing is completed for parsing the input string.

User Response: Enter the input string again correctly.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.

PRSE0008Estring - INVALID HEXADECIMAL CHARACTER

Where:

string
The string that identifies the function calling IPRSE_parse.

Explanation: A hexadecimal character was required by a parameter during the parsing of the string for the cccc function but a non-hexadecimal character was specified.

System Action: Processing is completed for parsing the input string.

User Response: Enter the input string again correctly.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.

PRSE0009Estring -- MANDATORY PARAMETER NOT GIVEN parameters

Where:

string
The string that identifies the function calling IPRSE_parse.

parameters
This may contain the text PARAMETER IN ERROR and the parameter that was in error.

Explanation: A mandatory parameter was not found in the input string during the parsing of the string for the cccc function.

System Action: Processing is completed for parsing the input string.

User Response: Enter the input string again correctly.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.

PRSE0011Estring -- INVALID INPUT PARAMETER parameters.

Where:

string
The string that identifies the function calling IPRSE_parse.

parameters
Possible additional information regarding the error. It may contain either LAST VALID PARAMETER IS and a parameter or KEYWORD IN ERROR and the keyword name.

Explanation: A mandatory parameter was not found in the input string during the parsing of the string for the cccc function.

If a keyword is in error, it is identified in the error message. Otherwise, the TPF system tries to provide the last valid parameter in the error message.

System Action: Processing is completed for parsing the input string.

User Response: Enter the input string again correctly.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.

PRSE0014Estring - TOO MANY CHARACTERS ENTERED

Where:

string
The string that identifies the function calling IPRSE_parse.

Explanation: Too may characters were specified for a specific parameter.

System Action: Processing is completed for parsing the input string.

User Response: Enter the input string again correctly.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.

PRSE0015Estring - TOO FEW CHARACTERS ENTERED FOR PARAMETER

Where:

string
The string that identifies the function calling IPRSE_parse.

Explanation: Too few characters were specified for a specific parameter.

System Action: Processing is completed for parsing the input string.

User Response: Enter the input string again correctly.

See the TPF C/C++ Language Support User's Guide for more information about IPRSE_parse and the format of the syntax for the cccc function.