81 PGU-00100 to PGU-50101

Cause: When using the SPOOL command, you specified the name of a file that already exists.

Cause: There were unrecognized commands or other text on the command line.

Cause: An invalid option for the SET ECHO command was specified.

Cause: An invalid option for the SET TERMOUT command was specified.

Cause: An invalid option for the SET TIMING command was specified.

Cause: An invalid option for the SET command was specified.

Cause: An invalid option for the SHOW command was specified.

Cause: An option was specified without the required arguments.

Cause: An invalid options switch was specified for the SET STOPONERROR command.

Cause: A character or an invalid value was specified when a number was expected as a value for a SET command option.

Cause: A numeric value was specified that was too large.

Cause: The specified value was out of range. The valid range is given by the error message.

Cause: The hostname/password was not specified.

Cause: A variable was incorrectly specified using the VARIABLE command.

Cause: The PL/SQL block contains a syntax error.

Cause: The specified object type, owner, or name was not recognized.

Cause: The specified variable was not recognized.

Cause: The specified object type was not TABLE, VIEW, or PROCEDURE.

Cause: The specified table, view, stored procedure, or function was not recognized.

Cause: An invalid option was specified for the SET SERVEROUTPUT command.

Cause: You have encountered an internal error.

Cause: You must be connected to the database for the requested operation.

Cause: A command file used as input to PGAU is corrupt or invalid.

Cause: The SQL statement size exceeds PGAU's buffer size.

Cause: You entered an invalid number for the cycle interval.

Cause: PGAU tried to open a spool file after you entered SPOOL filename, but could not open the file. Possible causes are not enough disk space or inadequate privileges to create a file.

Cause: You entered SPOOL OFF, but you were not spooling currently so there was no file to close.

Cause: SPOOL OFF could not close the currently open spool file.

Cause: PGAU cannot locate or open the file specified by the PFILE option, either because the file does not exist or because PGAU has insufficient privilege to open the file.

Cause: The results returned by a SQL query exceed the internal PGAU buffer.

Cause: An unrecognzed parameter was given on the PGAU command line.

Cause: PGAU cannot locate the specified command file.

Cause: This version of the PGAU tool cannot process the DATA in the database.

Cause: You made a syntax or typing error while entering a PGAU command line.

Cause: File mentioned cannot be located.

Cause: File mentioned cannot be opened.

Cause: You entered too many command line arguments and the PGAU buffer was exceeded.

Cause: The file you specified using PFILE is too large (exceeds 8K).

Cause: You have specified a command that is not available in this mode.

Cause: You attempted to display a MONITOR display without sufficient privileges.

Cause: There is not enough memory for the current SQL buffer.

Cause: The instance name was not specified in the connect statement.

Cause: The SQL statement refers to an undefined bind variable.

Cause: The list box of set tablespace online contained 0 elements.

Cause: An instantiation of this monitor is already active.

Cause: The object in a DESCRIBE FUNCTION/PROCEDURE/PACKAGE statement does not exist.

Cause: An unexpected error occurred during a describe.

Cause: The named object is a package. DESCRIBE does not currently describe an entire package specification.

Cause: The named package does not contain the procedure or function specified.

Cause: The specified object name contains a database link, or is a synonym that resolves to a name with a database link. Such objects cannot currently be described.

Cause: The object must have been successfully compiled.

Cause: The name may have at most 3 parts and a dblink.

Cause: You tried to execute the dialog before filling in all required items.

Cause: You pressed the Help Key or chose an item from the Help Menu.

Cause: You pressed the Help Key or chose an item from the Help Menu.

Cause: You pressed the Help Key or chose an item from the Help Menu.

Cause: You pressed the Help Key or chose an item from the Help Menu.

Cause: You pressed the Help Key or chose an item from the Help Menu.

Cause: Attempted to navigate to the next/previous item.

Cause: Attempted to navigate to the next/previous item.

Cause: Attempted to obtain help before selecting an item.

Cause: Attempted SHOW VAR[IABLES] [var-name] and the variable was not defined, or no variables were specified or defined.

Cause: Attemt to execute a statement that requires the Procedural option was made, but the Procedural option is not installed.

Cause: Most likely the package DBMS_OUTPUT not installed. Check the accompanying messages for more information.

Cause: The value for the PGAU initialization variable (which points to the initialization file) is not a recognizable file name.

Cause: The file name pointed to by the PGAU initialization variable could not be opened.

Cause: The specified file could not be opened.

Cause: The specified file could not be located.

Cause: The specified file could not be opened.

Cause: The specified file could not be located.

Cause: A variable was not properly set.

Cause: The specified file could not be located.

Cause: Terminal type specified by <variable> may not be valid.

Cause: The PGAU mode has been incorrectly defined.

Cause: PGAU encounterred a syntax error during parse operation <oper> of the statement <statement> for the table <table> with the indicated return code <rc>.

Cause: The operation <oper> on the variable <varname> for the statement <statement> against the PG DD table <table> failed with return code <rc>.

Cause: An error occurred attempting to logon to the Oracle server. Syntax checking only continues with the next statement.

Cause: Internal PGAU logic error - should not occur. An error occurred opening an SQL statement cursor. Syntax checking only continues with the next statement.

Cause: Internal PGAU logic error - should not occur. An error occurred closing an SQL statement cursor. Syntax checking only continues with the next statement.

Cause: Internal PGAU logic error - should not occur. An error occurred attemtping to commit changes to the PG DD. Syntax checking only continues with the next statement.

Cause: Internal PGAU logic error - should not occur. An error occurred during logoff from the Oracle server. Syntax checking only continues with the next statement.

Cause: Internal PGAU logic error - should not occur. An error occurred attemtping to rollback changes from the PG DD. Syntax checking only continues with the next statement.

Cause: PGAU successfully completed generation of the TIP specification for transaction <tranname> and version <version> into file <fileid>.

Cause: An internal PGAU operation error has occurred.

Cause: This record is written to the Trace or Log file upon initialization.

Cause: PGAU successfully completed generation of the TIP body for transaction <tranname> and version <version> into file <fileid>.

Cause: Before complete initialization of LMS functions, PGAU tracing or logging to disks was requested, but PGAU failed to open the indicated trace or log file. <fileid>.

Cause: After termination of LMS functions,PGAU tracing or or logging to disks had been requested, but PGAU failed to close the indicated trace or log file. <fileid>.

Cause: Before complete initialization of LMS functions, PGAU failed to obtain <bytes> of storage for <use>, commensurate with LMS initialization.

Cause: Before complete initialization of LMS functions, the environment variable LANGUAGE specified an invalid Oracle NLS language <lang>. The language environment variable SSTDLANG setting was used as the default.

Cause: Before complete initialization of LMS functions, the PGAU message file <fileid> could not be located.

Cause: Insufficient memory available. Storage failed to be allocated for the reason <purpose> of the size <len> specified.

Cause: Error during fopen processing <file> for <mode> access.

Cause: An error occurred during <oper> processing for the file <fileid> with return code <rc>. File operations include: 'fclose' to close input or output files 'remove' to erase, delete, or remove output files

Cause: Error during fgets <oper> processing for <file> at <offset> bytes into the file.

Cause: Error during fputs <oper> processing for <file> from buffer at <addr> for <len> bytes of data.

Cause: fprintf returned the error code <rc> attempting to print PGAU error message number <msgno>. The indicated event message was being written when the error occured.

Cause: fprintf returned the error code <rc> attempting to print PGAU trace message number <msgno>. The indicated trace message was being written when the error occured.

Cause: Error during control function <oper> processing for <file> with error code <rc> returned.

Cause: The ORACLE_HOME environment variable setting is missing or invalid.

Cause: The parameter <parm> specifies an aggregate data record for which field <field> with PG DD field id number <f#> was being processed, but the field had no relative level attribute <attr>. Typical relative level attributes are: nn ... COBOL-clauses for IBMVSCOBOLII 'LEVEL' attribute Each attribute is stored as a separate row in the PG DD, and the missing attribute's row may have been deleted from the PG DD.

Cause: PGAU was processing nested records when the next field <f#> for nest level <lev> exceeded the product defined minimum or maximum nest level <limit>.

Cause: PGAU was processing nested records when the next field at at level <levN>, identified by <fld#>, occurred after fields at current level <levC>. Additional fields at intermediate levels should have preceded this field. This error happens when special fields such as COBOL RENAMES (at LEVEL 66) appear next after the level 01 definition.

Cause: Insufficient memory available for the specified purpose. Requestor attempted to allocate a <type> control block of <len> size specified.

Cause: Control block of the specified <type> was being loaded with a row from the PG Data Dictionary when an error occurred. A preceding message issued specifies the cause.

Cause: A control block of the specified <type> was being loaded with attribute rows from the PG Data Dictionary when the <limit> was exceeded.

Cause: PGAU encountered an error writing a PL/SQL code segment to the indicated work file <fileid>.

Cause: PGAU encountered an error appending the work file <infile> to the TIP output file <outfile>.

Cause: PGAU encountered an error appending the TIP function definition <func> to the work output file <file>. Error occurred during generation of the TIP Package Specification.

Cause: PGAU encountered an error appending the TIP variable definition <var> to the work output file <file>. Error occurred during generation of the TIP Package Specification.

Cause: This is a warning of possible non-unique PL/SQL names. PGAU encountered record field names which combined exceed the maxmimum PL/SQL name length, and the last field name specified <field> was truncated to the length <len>. The condition occurred during generation of the TIP Package Specification for parameter variables.

Cause: An occured during generation of a nested record type <type> for the indicated field name <name>. This message should be preceded by the specific error. Condition occurred during generation of the TIP Package Specification for parameter variables.

Cause: The parameter call mode <mode> specified for the parameter <parm>. Valid parameter modes are IN, OUT or IN OUT. Probable PG DD content error.

Cause: An invalid PL/SQL record type <type> was encountered while generating conversion statements for the data field <field>. The indicated <type> is neither valid PL/SQL nor a nested record type, for the indicated record field <field>. Probable PG DD content error.

Cause: The number of nested groups and lengths of their field names in the input data, when concatenated to form a fully qualified PL/SQL record field variable name <recname.varname>, exceeded the maximum length allowed by PL/SQL <maxlen>. Condition occurred during generation of the TIP Package Specification for parameter variables.

Cause: The TIP function call <cname> at parm <pname> exchanges too many parameters for the <type> buffers on a PGAXFER RPC. The PGAXFER parameter limit is <limit>. The indicated <type> is either 'SEND' or RECEIVE'. Probable PGAU DEFINE CALL error, coding too many parameters. Note also that IN OUT mode parameters are present in both send and receive buffers and may be causing the excess.

Cause: An occured during generation of PL/SQL statements for conversion of a nested record type <type> for the indicated field name <name>. This message should be preceded by the specific error. Condition occurred during generation of the TIP Package Specification for parameter variables.

Cause: Failure to generate PL/SQL conversion statements for the indicated parameter data <dname> for function <call>. This message may be preceeded by specific messages describing the error. Possible errors include disk access, invalid datatype, and/or missing nested record or field datatype definitions.

Cause: Failure to generate PL/SQL statement <stmt> used to control TIP processing of the field <fname> for compiler clause <clause>. Typical IBMVSCOBOLII clauses are: OCCURS (requires FOR/LOOP logic) OCCURS DEPENDING ON (requires FOR/LOOP logic) REDEFINES (requires IF/END IF logic) This message may be preceeded by specific messages describing the error. Possible errors include disk access, invalid datatype, and/or missing nested record or field datatype definitions.

Cause: Failure to generate PL/SQL control logic <stmt> to process TIP parameter <dataname> in function <callname>. This message may be preceeded by specific messages describing the error. Possible errors include disk access, invalid datatype, and/or missing nested record or field datatype definitions.

Cause: Data field <d-field> <f#> was referenced by other fields which required PL/SQL statements <stmt> be generated for the value <num>, but an error occurred during the generation of the statements. This message may be preceeded by specific messages describing the error. Possible errors include disk access and memory exceeded.

Cause: TIP execution diagnostics for PG Data Dictionary References PKGEX(DR) was requested on the PGAU GENERATE statement, but the PG DD reference for <type> <id#> couldn't be generated. This message may be preceeded by specific messages describing the error. Possible errors include disk access and memory exceeded.

Cause: The COBOL data field <field> specifies conflicting or invalid PIC <mask> and USAGE <maskopts> clauses. The invalid PIC and USAGE definitions were selected from the PG DD to identify field conversion function calls. PGAU also issues messages 30601 for <mask> and 30602 for <maskopts> .

Cause: Issued to identify <mask> for the preceding message.

Cause: Issued to identify <maskopts> for the preceding message.

Cause: A COBOL field <field> containing a clause of the form <syntax> required a missing attribute <attr> corresponding to <token>. PGAU issues messages 30603 and 30604 consecutively for <field>, <syntax>, <attr>, and <token>. Typical IBMVSCOBOLII required token attributes are: field OCCURS int-1 TIMES where 'int-1' is the token for attribute 'repgrpff' field OCCURS int-1 TO int-2 TIMES DEPENDING ON name-1 where 'int-1' is the token for attribute 'repgrpvf' 'int-2' is the token for attribute 'repgrpvl' 'name-1' is the token for attribute 'repgrpvm' field RENAMES name-1 THRU name-2 where 'name-1' is the token for attribute 'renamemf' 'name-2' is the token for attribute 'renameml' field REDEFINES name-1 WHEN name-2 = value where 'name-1' is the token for attribute 'remapsmf' 'name-2' is the token for attribute 'remapsml' 'value' is the token for attribute 'remapswc' or for attribute 'remapswn' field LENGTH IS name-1 where 'name-1' is the token for attribute 'length' Each attribute is stored as a separate row in the PG DD, and the missing attribute's row may have been deleted from the PG DD.

Cause: An unidentified COBOL field specifies conflicting or invalid PIC <mask> and USAGE <maskopts> clauses. The invalid PIC and USAGE definitions were selected from the PG DD to identify global TIP conversion variables. PGAU also issues messages 30601 for <mask> and 30602 for <maskopts> .

Cause: The COBOL data field <field> specifies character data in the the PIC <mask> and USAGE <maskopts> clauses which require translation with a multi-byte character set (MBCS), but no Oracle MBCS NLS name was specified. The MBCS-oriented PIC and USAGE definitions were selected from the PG DD to identify field conversion function calls. PGAU also issues messages 30601 for <mask> and 30602 for <maskopts> .

Cause: The data field <d-field> containing a clause of the form <syntax> references a missing field <r-field> specified by the clause word <token>. PGAU issues messages 30610 and 30611 consecutively for <d-field> <syntax> <r-field> and <token>. Typical IBMVSCOBOLII clause syntax for this error includes: d-field OCCURS int-1 TIMES d-field OCCURS int-1 TO int-2 TIMES DEPENDING ON name-1 d-field RENAMES name-1 THRU name-2 d-field REDEFINES name-1 WHEN name-2 = value d-field LENGTH IS name-1 The clause references a field <r-field> specified by the word <token>. PGAU GENERATE searched previous fields within the current parameter but failed to find the named field <r-field>. The word <token> may be misspelled in the defining clause or the referenced field whose name should match <token> may be missing from, or misspelled in the PG DD.

Cause: During TIP generation, an attempt to insert a new attribute value for the <attr> attribute for the named field <fname> failed.

Cause: The data field <d-field> <f#> specified an attribute which specifies remote host boundary alignment. The PG DD environment tables were searched for alignment information for environment <ename> compiler <compno> datatype <dtype> datatype alignment group <dagno>, but no entries were found matching these characteristics. PGAU issues messages 30630 and 30631 consecutively for <d-field> <f#> and <ename> <compno> <dtype> <dagno>. PGAU requires the alignment information to properly align the remote host data in the TIP transfer buffers. Supported: envrionment and compilers are; IBM370 for compiler IBMVSCOBOLII alignment attributes are; <d-field> ... PIC S9(n) <dtype> SYNC <d-field> ... PIC S9(n) <dtype> SYNCHRONIZE datatype values <dtype> may be; COMP COMPUTATIONAL COMP-4 COMPUTATIONAL-4 datatypes grouped under <dagno> by length/alignment: dagno = 1 for 2-byte length aligned on 2-byte boundary dagno = 2 for 4-byte length aligned on 4-byte boundary Possible causes are:

- The TRANSACTION entry in the PG DD for the TIP being generated may have specified an invalid ENVIRONMENT.

- The DATA entry in the PG DD being referenced in the TIP function call being generated may have specified an invalid LANGUAGE.

- The field datatype and/or length within the DATA entry may be invalid or unsupported.

- The PG DD may be unavailable, in which case previous error messages will indicate problems accessing the PG DD.

Cause: The data field <d-field> <f#> specified a modifying clause <clause> which is ignored for datatype <dtype> by thecompiler in the remote host environment. For supported: envrionment and compilers; IBM370 for compiler IBMVSCOBOLII <clause> is ignored when <dtype> is; SYNC | SYNCHRONIZE COMP-3 | COMPUTATIONAL-3 SYNC | SYNCHRONIZE DISP | DISPLAY

Cause: The data field <d-field> <f#> specified a repeating group clause <clause> while a previous repeating group is active. The repeating group in <d-field> cannot be nested within a previous repeating group. TIP's use PL/SQL tables to implement repeating groups, and PL/SQL tables are limited to a single key or subscript which cannot support nested repeating groups (a table of tables).

Cause: The data field <d-field> <f#> specified an attribute <attr> whose value <attrval> is being ignored. Attribute values are ignored for supported: envrionment and compilers; IBM370 for compiler IBMVSCOBOLII when <attr> is the <attrval> is ignored: SYNC | SYNCHRONIZE LEFT JUST | JUSTIFY LEFT

Cause: The data field <d-field> <f#> specified an attribute <attr> whose value <attrval> is invalid or unsupported.

Cause: Open of an Oracle cursor for the PGAU SQL statement <stmtname> failed with Oracle error <rc>. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: Parsing of the PGAU SQL statement <stmtname> for Oracle cursor <curno> failed with Oracleerror <rc>. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: Binding input variable <invar> for Oracle cursor <curno> to the PGAU SQL statement <stmtname> failed with Oracle error <rc>. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: Defining output variable <outvar> for Oracle cursor <curno> to the PGAU SQL statement <stmtname> failed with Oracle error <rc>. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: Executing Oracle cursor <curno> PGAU SQL statement <stmtname> failed with Oracle error <rc>. Possible error in PGAU GENERATE statement transaction or version parameters, or possible missing rows or misspelled in the PG DD for the requested transaction. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: Fetch using Oracle cursor <curno> PGAU SQL statement <stmtname> failed with Oracle error <rc>. Possible error in PGAU GENERATE statement transaction or version parameters, or possible missing rows or misspelled in the PG DD for the requested transaction. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: Close of Oracle cursor <curno> for PGAU SQL statement <stmtname> failed with rc <rc>. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: No Transaction rows were fetched from the PG DD for PGAU SQL statement <stmt> with transaction name <tname> and transaction version <tver>. The Oracle error code is <rc>. Either the transaction name and version supplied on the GENERATE statement were invalid or the transaction entry is missing from the PG DD. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: No <type> rows were fetched from the PG DD for PGAU SQL statement <stmt> with id number <idno>. The Oracle error code is <rc>. Either the parent PG DD entry references an invalid subordinate entry or the entry is missing from the PG DD. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: No Environment rows were fetched from the PG DD for PGAU SQL statement <stmt> with environment name <ename> and compiler number <compno>. The Oracle error code is <rc>. Either the environment specified for the transaction or the compiler specified for the data entry in the transaction were invalid, or the entries are missing from the PG DD. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: The transaction <tname> <tver> was not found in the PG DD. Either the transaction name and version requested in the GENERATE statement were invalid or the transaction specified in a previous DEFINE TRANSACTION <tname> may have been deleted from or altered in the PG DD. This message may be preceded by specific messages describing the error.

Cause: A call entry under transaction definition <tname> <tver> (<tin>) was not found in the PG DD. The call entry associated with the transaction (as specified in a previous DEFINE TRANSACTION ... CALL(cname)) may have been deleted from or altered in the PG DD. This message may be preceded by specific messages describing the error.

Cause: A parameter or data entry for transaction <tname> <tver> (<tin>), call <cname> <cver> (<cin>) was not found in the PG DD. The parm or data entry associated with the call (as specified in a previous DEFINE CALL <cname> ... PARMS(dname)) may have been deleted from or altered in the PG DD. This message may be preceded by specific messages describing the error.

Cause: A data field entry for transaction <tname> <tver> (<tin>), call <cname> <cver> (<cin>), parm <relno> data <dname> <dver> (<din>) was not found in the PG DD. The field entry associated with this data (as specified in the input file field position or FIELD(fname) of a previous DEFINE or REDEFINE DATA statement) may have been deleted from or altered in the PG DD. This message may be preceded by specific messages describing the error.

Cause: For transaction <tname> <tver>, the data field usage, mask, and maskopts entries were not found in the PG DD. PG DD field entries are selected with usage='PASS' and not null mask and maskopts columns, to identify which data fields will use UTL_RAW MAKE_..._FORMAT conversions. Possible invalid entries in pga_fields( usage,mask,maskopts ) columns. This message may be preceded by specific messages describing the error.

Cause: The combined environment <ename> <compno> was not found in the PG DD for transaction id# <tin> and data id# <din>. The environment name stored in the transaction entry and the compiler no stored in a call parameter data entry have no environment rows stored in the PG DD environment tables. This message may be preceded by specific messages describing the error.

Cause: No information was fetched from Oracle dual for SQL statement <stmt> with date format <dfmt> and time format <tfmt>. The Oracle error code is <rc>. Either the date and time formats specified are invalid or some other Oracle server error occurred. This message is preceded by an Oracle Server message for the specific error encountered.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine is returning with the return code shown.

Cause: Subroutine Call Tracing Active. The GPG main routine was called from PGAU.

Cause: Subroutine Call Tracing Active. The indicated subroutine is returning from its indicated exit with the non-success return code shown.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Subroutine Call Tracing Active. The indicated subroutine was called.

Cause: Initialization/Termination Tracing Active. Successful initialization by indicated subroutine.

Cause: Initialization/Termination Tracing Active. Failed initialization by indicated subroutine.

Cause: Initialization/Termination Tracing Active. Successful termination by indicated subroutine.

Cause: Initialization/Termination Tracing Active. Failed termination by indicated subroutine.

Cause: Queue Management Tracing Active. Successful alteration of the TDT.

Cause: Queue Management Tracing Active. Failed alteration of the TDT.

Cause: Queue Management Tracing Active. Successful alteration of the TDT.

Cause: Queue Management Tracing Active. Requested structure not located.

Cause: Initation/Termination Tracing Active. Successful read of file or segment data.

Cause: I/O Tracing Active. Successful file control operation.

Cause: I/O Tracing Active. Successful read/write of file or segment data.

Cause: Data Dictionary Tracing Active. Successful select and load of a PG DD entry

Cause: Data Dictionary Tracing Active. Failed select and/or load of a PG DD entry

Cause: Data Dictionary Tracing Active. Successful select and load of a format conversion block

Cause: Oracle Call Tracing Active. Successful cursor operation

Cause: Data Dictionary Tracing Active. Successful select from dual for current session attributes

Cause: Oracle Call Tracing Active. Successful BIND variable operation

Cause: Oracle Call Tracing Active. Successful DEFINE operation

Cause: Oracle Call Tracing Active. Successful EXECUTE operation

Cause: Oracle Call Tracing Active. Successful FETCH operation

Cause: TIP package generation tracing active. Successful generation of TIP specification function definition.

Cause: TIP package generation tracing active. Successful generation of TIP specification variable definition.

Cause: TIP package generation tracing active. Successful generation of TIP data conversion logic. This trace entry is written at the completion of generation for every data parameter of a TIP call and field of a data parameter. There should be one trace for every parameter exchanged by the TIP and one trace for every data field of each parameter.

Cause: TIP package generation tracing active. Successful generation of specified PGA gateway server RPC.

Cause: TIP package generation tracing active. Successful generation of specified PL/SQL variable conversion.

Cause: TIP package generation tracing active. Successful syntax check of cobol field.

Cause: TIP package generation tracing active. Successful syntax check of cobol field. This trace entry is supplemental to 39605.

Cause: TIP package generation tracing active. Successful syntax check of cobol field numeric attribute This trace entry is supplemental to 39605.

Cause: TIP package generation tracing active. Successful syntax check of cobol field numeric attribute This trace entry is supplemental to 39605.

Cause: TIP package generation tracing active. Successful syntax check of cobol field date attribute This trace entry is supplemental to 39605.

Cause: TIP package generation tracing active. Successful generation of TIP Function. This trace entry is written at the completion of generation for every TIP public function. There should be one trace of this type for every Call defined in the Transaction.

Cause: TIP package generation tracing active. Successful alignment/offset computation

Cause: An field definition is invalid. There may be invalid punctuation or an invalid keyword present.

Cause: An unexpected end-of-file condition has occurred in the PGAU command stream.

Cause: There is a syntax error in the REPORT statment.

Cause: A DEFINE or REDEFINE DATA statement has specified an invalid field name for a field definition. The field name may be missing. A field name must begin with an alphabetic character and contain only alphanumeric characters or an underscore ('_'). Syntax checking only continues with the next statement.

Cause: An invalid delmiter has been found (such as a parenthesis or comma in the wrong place.

Cause: A token has been found which is not a valid PGAU keyword, delimiter, or identifer name. Syntax checking only continues with the next statement.

Cause: The parameter keyword <keyword> was properly specified but parameter value was not found. Syntax checking only continues with the next statement.

Cause: The parameter <dupparm> has been specified earlier in a PGAU statement and is only allowed once. Syntax checking only continues with the next statement.

Cause: An invalid token has been specified for the data name for a DEFINE DATA or REDEFINE DATA statement. A DATA identifier dname must begin with an alphabetic character and contain only alphanumeric characters. Syntax checking only continues with the next statement.

Cause: The parameter specified in the PLSDNAME clause of a DEFINE or REDEFINE DATA statement does not comply with PL/SQL syntax for PL/SQL variable names. Syntax checking only continues with the next statement.

Cause: The LANGUAGE parameter in a DEFINE or REDEFINE DATA statement is not a valid PGA Compiler Language. Syntax checking only continues with the next statement.

Cause: The USAGE parameter in a DEFINE or REDEFINE DATA statement is not a valid PGAU usage. Syntax checking only continues with the next statement.

Cause: The USAGE parameter has already been specified in a DEFINE or REDEFINE DATA statement and is only allowed once per data definition. Syntax checking only continues with the next statement.

Cause: The LANGUAGE parameter has already been specified in a DEFINE or REDEFINE DATA statement and is only allowed once per data definition. Syntax checking only continues with the next statement.

Cause: The PLSDNAME parameter has already been specified in a DEFINE or REDEFINE DATA statement and is only allowed once per data definition. Syntax checking only continues with the next statement.

Cause: The COMPOPTS parameter in a DEFINE or REDEFINE DATA statement is not a valid compiler option string recognized by PGAU. Syntax checking only continues with the next statement.

Cause: The COMPOPTS parameter has already been specified in a DEFINE or REDEFINE DATA statement and is only allowed once per data definition. Syntax checking only continues with the next statement.

Cause: The token is not a valid call identifier name for a DEFINE CALL statement. A CALL identifier cname must begin with an alphabetic character and contain only alphanumeric characters. Syntax checking only continues with the next statement.

Cause: The PKGCALL parameter has already been specified in a DEFINE CALL statement and is only allowed once per call definition. Syntax checking only continues with the next statement.

Cause: The function name specified in the PKGCALL parameter of a DEFINE CALL statement does not comply with PL/SQL syntax for PL/SQL function names. Syntax checking only continues with the next statement.

Cause: The token is not a valid version number in a PGAU DEFINE or UNDEFINE CALL or TRANSACTION statement, or in a GENERATE statement. Valid version numbers are all numeric and must match a the Oracle sequence object value reported by a previous DEFINE statement. Syntax checking only continues with the next statement.

Cause: The PARMS parameter has already been specified in a DEFINE CALL statement and is only allowed once once per call definition. Syntax checking only continues with the next statement.

Cause: The token is not a valid call identifier name for specifying CALLs in a DEFINE TRANSACTION statement. A CALL identifier cname must begin with an alphabetic character and contain only alphanumeric characters, and must have originated in a previous DEFINE CALL statement. Syntax checking only continues with the next statement.

Cause: The NLS_LANGUAGE parameter has already been specified in a DEFINE TRANSACTION statement and is only allowed once per transaction definition. Syntax checking only continues with the next statement.

Cause: The PGAU parameter <parm> specifies an Oracle NLS language name <nlsname> which is not defined on the Oracle server to re PGAU executes. which PGAU is connected. The language <nlsname> is not defined possibly because it was not selected when Oracle was installed, or the GENERATE'd TIPs are intended to execute on another Oracle, or it is not a valid Oracle NLS Language, i.e. misspelled or unsupported. Syntax checking only continues with the next statement.

Cause: The ENVIRONMENT parameter has already been specified in a DEFINE TRANSACTION statement and is only allowed once per transaction definition. Syntax checking only continues with the next statement.

Cause: The ENVIRONMENT parameter in a DEFINE TRANSACTION statement is not a valid PGA ENVIRONMENT. Syntax checking only continues with the next statement.

Cause: The SIDEPROFILE parameter as already been specified in a DEFINE TRANSACTION statement and is only allowed once per transaction definition. Syntax checking only continues with the next statement.

Cause: The token is not a valid name for specifying an SNA Side Profile in a DEFINE TRANSACTION statement. A Side Profile name must begin with an alphabetic character and contain only alphanumeric characters. Syntax checking only continues with the next statement.

Cause: The LUNAME parameter has already been specified in a DEFINE TRANSACTION statement and is only allowed once per transaction definition. Syntax checking only continues with the next statement.

Cause: The token is not a valid name for specifying an SNA LU name in a DEFINE TRANSACTION statement. An LU name must begin with an alphabetic character and contain only alphanumeric characters. Syntax checking only continues with the next statement.

Cause: The TPNAME parameter has already been specified in a DEFINE TRANSACTION statement and is only allowed once per transaction definition. Syntax checking only continues with the next statement.

Cause: The token is not a valid name for specifying an SNA TP name in a DEFINE TRANSACTION statement. A TP name must begin with an alphabetic character and contain only alphanumeric characters. Syntax checking only continues with the next statement.

Cause: The LOGMODE parameter has already been specified in a DEFINE TRANSACTION statement and is only allowed once per transaction definition. Syntax checking only continues with the next statement.

Cause: The token is not a valid name for specifying an SNA logmode in a DEFINE TRANSACTION statement. A logmode must begin with an alphabetic character and contain only alphanumeric characters. Syntax checking only continues with the next statement.

Cause: The SYNCLEVEL parameter has already been specified in a DEFINE TRANSACTION statement and is only allowed once per transaction definition. Syntax checking only continues with the next statement.

Cause: The token is not a valid value for specifying an APPC SYNC level in a DEFINE TRANSACTION statement. The only values allowed for SYNC level are 0 and 1. Syntax checking only continues with the next statement.

Cause: The token is not a valid transaction identifier name in a DEFINE TRANSACTION statement. A transaction name must begin with an alphabetic character and contain only alphanumeric characters. Syntax checking only continues with the next statement.

Cause: PGAU DEFINE TRANSACTION syntax requires a call name which was not found. Syntax checking only continues with the next statement.

Cause: If the SNA SIDEPROFILE parameter is not specified, then all three of the LUNAME, TPNAME and LOGMODE parameters must be specified in a DEFINE TRANSACTION statement. Syntax checking only continues with the next statement.

Cause: The CALL parameter has already been specified in a DEFINE TRANSACTION statement and is only allowed once per transaction definition. Syntax checking only continues with the next statement.

Cause: The parameter <parm> has already been specified in a DEFINE TRANSACTION statement and is only allowed once per transaction definition. Syntax checking only continues with the next statement.

Cause: The VERSION parameter has already been specified, and is only allowed once in a GENERATE or REDEFINE statement. Syntax checking only continues with the next statement.

Cause: The version number must follow the VERSION keyword enclosed in parenthesis in a GENERATE or REDEFINE statement. Syntax checking only continues with the next statement.

Cause: The token is not a valid field identifier name in the specified language for specifying a FIELD or PLSFNAME parameter in a REDEFINE DATA statement. A field identifier name must obey the naming conventions of the specified language. In COBOL, only alphamerics may be used in addition to the hyphen character and the first character must be alphabetic. Syntax checking only continues with the next statement.

Cause: The token is not a valid transaction identifier name for a GENERATE statement. A transaction identifier name must begin with an alphabetic character and contain only alphanumeric characters, and must have originated in a previous DEFINE TRANSACTION statement. Syntax checking only continues with the next statement.

Cause: The PKGNAME parameter has already been specified in a GENERATE statement and is only allowed once per GENERATE request. Syntax checking only continues with the next statement.

Cause: The token is not a valid identifier name for specifying the PL/SQL TIP package name in a GENERATE statement. A package name identifier must begin with an alphabetic character and contain only alphanumeric characters. Syntax checking only continues with the next statement.

Cause: The OUTFILE parameter has already been specified in a GENERATE statement and is only allowed once per GENERATE request. Syntax checking only continues with the next statement.

Cause: The DIAGNOSE parameter has already been specified in a GENERATE statement and is only allowed once per GENERATE request. Syntax checking only continues with the next statement.

Cause: The PGANODE parameter <keyword> has already been specified in a GENERATE statement and is only allowed once per GENERATE request. Syntax checking only continues with the next statement.

Cause: The token is not a valid PGA node identifier name in a GENERATE statement. A PGA node identifier name must begin with an alphabetic character and contain only alphanumeric characters, and be a valid Oracle DB link name. Syntax checking only continues with the next statement.

Cause: An error occurred opening the input definition file specified with the INFILE parameter in a DEFINE or REDEFINE DATA statement. Syntax checking only continues with the next statement.

Cause: A COBOL inline definition starts with a left parenthesis. The left parenthesis must be the last character on the line preceding any COBOL data definition statements.

Cause: PGAU DEFINE or REDEFINE DATA syntax requires a LANGUAGE parameter which was not found. Syntax checking only continues with the next statement.

Cause: The OPTIONS parameter has already been specified in a GENERATE statement and is only allowed once per GENERATE request. Syntax checking only continues with the next statement.

Cause: The indicated subparameter was previously specified in an OPTIONS parameter. The only valid OPTIONS subparameter is UDF. It may be specified only once per GENERATE statement. Syntax checking only continues with the next statement.

Cause: The TRACE parameter has already been specified in a GENERATE statement and is only allowed once per GENERATE request. Syntax checking only continues with the next statement.

Cause: The indicated parameter was previously specified in a DIAGNOSE TRACE or PKGEX parameter. The valid TRACE parameters are SE, IT, QM, IO, OC, DD, and TG. The valid PKGEX parameters are DC and DR. Each may be specified only once per GENERATE statement. Syntax checking only continues with the next statement.

Cause: The PKGEX parameter has already been specified in a GENERATE statement and is only allowed once per GENERATE request.

Cause: PGAU inserted the data definition <dname> with version number <dver> as the result of processing a DEFINE DATA statement.

Cause: PGAU inserted the call definition <cname> with version number <cver> as the result of processing a DEFINE CALL statement.

Cause: PGAU inserted the transaction definition <tname> with version number <tver> as the result of processing a DEFINE TRANSACTION statement.

Cause: PGAU updated the data definition <dname> with version number <dver> as the result of processing a REDEFINE DATA statement.

Cause: PGAU deleted the data definition <dname> with version number <dver> as the result of processing an UNDEFINE DATA statement.

Cause: PGAU deleted the call definition <cname> with version number <cver> as the result of processing an UNDEFINE CALL statement.

Cause: PGAU deleted the transaction definition <tname> with version number <tver> as the result of processing an UNDEFINE TRANSACTION statement.

Cause: The object name of type <var> is longer than the maximum length <len> allowed by PGAU. Only syntax checking continues with the next statement.

Cause: A DEFINE CALL references a data definition name <dname> that does not exist.

Cause: A DEFINE CALL references a data definition name <dname> that does not exist, or specified a non-existent version <dver> of the data definition <dname>.

Cause: A DEFINE TRANSACTION references a call definition name <cname> that does not exist.

Cause: A DEFINE TRANSACTION references a call definition name <cname> that does not exist, or specified a non-existent version <cver> of the call definition <cname>.

Cause: An UNDEFINE DATA references a data definition name <dname> that does not exist.

Cause: An UNDEFINE DATA references a data definition name <dname> that does not exist, or specified a non-existent version <dver> of the data definition <dname>.

Cause: An UNDEFINE CALL references a call definition name <cname> that does not exist.

Cause: An UNDEFINE CALL references a call definition name <cname> that does not exist, or specified a non-existent version <cver> of the call definition <cname>.

Cause: An UNDEFINE TRANSACTION references a transaction definition name <tname> that does not exist.

Cause: An UNDEFINE TRANSACTION references a transaction definition name <tname> that does not exist, or specified a non-existent version <tver> of the transaction definition <tname>.

Cause: The LANGUAGE parameter in a REDEFINE DATA statement for a given dataname specifies a language different than the language originally specified in the DEFINE DATA statement for the given dataname.

Cause: A REDEFINE with the FIELD parameter specifies a field name <fname> that does not currently exist in the data object being REDEFINEd.

Cause: An INFILE parameter was found on a DEFINE DATA statement, but an inline data definition was also found. Only one of the two forms is allowed in a single DEFINE DATA statement.

Cause: Neither an inline data definition nor an INFILE parameter was found in a DEFINE DATA or REDEFINE DATA statement. One of these is required in a DEFINE DATA. One of these may be required in a REDEFINE DATA depending on other parameters given.

Cause: The INFILE parameter has already been specified in a DEFINE DATA or REDEFINE DATA statement and is only allowed once per data definition or redefinition. Syntax checking only continues with the next statement.

Cause: An attempt to allocated memory failed.

Cause: Left parenthesis must immediately follow a GROUP verb

Cause: A GROUP was found within a GROUP.

Cause: A data name, <name>, was specified but does not exist.

Cause: The field name <fld> does not exist in the data definition named <dnm>.

Cause: A REDEFINE specifies the field name <fld>; this field name is multiply defined in the data definition <dnm>. The field name must be sufficiently qualified to remove the ambiguity so that a unique field may be referenced.

Cause: A DEFINE or REDEFINE statement is missing the name of a transaction object, a call object, or a data object. <token> is the type of object.

Cause: The identifier name in an UNDEFINE statement is invalid. An identifier name must begin with an alphabetic character and contain only alphanumeric characters. <token> is the type of object.

Cause: The token is not a valid operand in a WITH phrase. Only DATA and CALLS are valid.

Cause: An identical WITH phrase has been previously found in this statement.

Cause: A WITH phrase has been found in an invalid context. The phrase WITH CALLS can appear only in an UNDEFINE TRANSACTION; the phrase WITH DATA cannot appear in an UNDEFINE DATA.

Cause: One of DATA, CALL, or TRANSACTION must be given to specify what type of object is to be defined.

Cause: A VERSION parameter was found in an UNDEFINE ALL.

Cause: An invalid sub-parameter was found within a DIAGNOSE parameter.

Cause: The transaction name is missing.

Cause: DATA was expected to be found at this point in the REDEFINE.

Cause: One of DATA, CALL, or TRANSACTION must be given to specify what type of object is to be deleted.

Cause: The type of object (DATA, CALL, or TRANSACTION) must be followed by a name for the object.

Cause: There are two succesive WITH tokens in the command input stream.

Cause: There is a missing WITH token before DATA or CALLS

Cause: A WITH token was found as the last token in an UNDEFINE or REPORT command.

Cause: The FIELD parameter is a pre-requisite to specify the <parm> parameter because <parm> applies to FIELDs within a DATA redefinition. PGAU REDEFINE parameters which require FIELD are:

- PLSFNAME

- CODEPAGE

Cause: The FIELD keyword must be accompanied by at least one of the following keywords: USAGE, PLSFNAME, INFILE.

Cause: A REDEFINE DATA with the FIELD option indicates that a single field is being redefined. The language input contained definitions for more than one field.

Cause: A REDEFINE DATA with the FIELD option indicates that a single field is being redefined. However, the language input contained no field definitions.

Cause: A REPORT command requested information about a group of unnamed PGAU data objects with a type specified by <token>. But there were no objects of that type.

Cause: A REPORT command requested information about a PGAU data object with a type specified by <type> and a name of <name>. But there were no objects of that <type> with the given <name>.

Cause: A REPORT command requested information about a specific PGAU data object with a type specified by <type>, a name of <name>, and a version of <vsn>. But there is no object with that name and version.

Cause: The VERSION parameter of a REPORT request has too many sub-parameters; the <maximum> is specified in the message.

Cause: The <object> name is missing in a REPORT statement.

Cause: A VERSION parameter has been found. But an ALL parameter has also been found (denoting all versions)

Cause: A version number was expected at this point.

Cause: A non-numeric string was found when scanning for a version number.

Cause: The VERSION parameter has already been found.

Cause: The WITH phrase is invalid with respect to an object of type <type>. For example, REPORT DATA ... WITH DATA is invalid,

Cause: The PKGCALL parameter was defaulted in a DEFINE CALL statement and normally takes the value of the CALL object name. However, the length of the CALL object name is greater than the maximum length allowed for the PKGCALL parameter (which is 30). The default value actually used is <value>.

Cause: The PLSDNAME parameter was defaulted in a DEFINE DATA statement and normally takes the value of the DATA object name. However, the length of the DATA object name is greater than the maximum length allowed for the PLSDNAME parameter (which is 30). The default value actually used is <value>.

Cause: The INFILE parameter in a DEFINE or REDEFINE DATA statement does not designate a valid filename. Syntax checking only continues with the next statement.

Cause: ALL cannot be specified in a level 88 (condition-names) entry

Cause: There are missing operands in the COPY clause

Cause: COPY clause found embedded within another COPY clause

Cause: COPY reserved word not allowed as operand-1 or operand-2 in the REPLACING clause of a COPY statement.

Cause: No filename operand given in COPY clause

Cause: An unrecognzied token <token> was found when checking for a COBOL reserved word

Cause: An EJECT statement cannot be given with operands

Cause: A SKIP1, SKIP2, or SKIP3 statment cannot have operands

Cause: This is an echo of the offending source line, <sourceline>.

Cause: A level-number was found with <number> digits. Level-numbers are restricted to a maximum of two digits

Cause: Level numbers are restricted to 01-49, 66, 77, or 88; <number> was found.

Cause: Record definition must start at level 01 or 77; a level other than 01 or 77 has been found.

Cause: Missing level 01 or 77 in source file or the 01 or 77 did not start within the column limits specified by <margin-A> and <margin-B>.

Cause: The RENAMES reserved word may be used ONLY at level 66.

Cause: Multiple instances of a clause of type <type> were found.

Cause: This is an internal error.

Cause: The VALUES keyword can only be specified in a data definition describing a condition and only at level 88.

Cause: The specified input file <file> could not be opened for reading.

Cause: A REDEFINES clause must appear before any other clause in a data definition.

Cause: If a RENAMES clause appears in a data definition, it must be the ONLY clause.

Cause: An end-of-file was found before the ending statement terminator. This also results from COBOL definitions which extend beyond column 72.

Cause: The only clause allowed at level 88 is a VALUE or VALUES clause.

Cause: A TITLE statement is not ended by a period separator.

Cause: Invalid format for TITLE statement.

Cause: The source file copied by a COPY statement cannot contain a COPY ... REPLACING statment; or the source file copied by a COPY ... REPLACING statement cannot have a COPY statement.

Cause: This message follows another message that describes the actual error. The line following this message echoes the input COBOL source line. The source line was found in line <line> of file <filename>.

Cause: An invalid word, <token> follows USAGE in a USAGE clause. <token> may be valid in some COBOL dialects.

Cause: A reserved word, <token>, was used as a PICTURE operand.

Cause: A clause of type <type> has ended but there are missing operands.

Cause: A phrase introduced by <key-word-1> cannot come after a phrase introduced by <key-word-2>. Certain phrases must precede other phrases in a data definition. For instance, an ASCENDING [KEY] phrase must appear before an INDEXED phrase.

Cause: An internal error has occurred in the PGAU COBOL parser. State <state> is either valid or invalid according to <validity>.

Cause: Extraneous text has been found at the end of a record definition. It starts in column <column> of the source input record.

Cause: A COPY statement for file <filename> has been found while processing a previous occurrence of a COPY specifying the same file.

Cause: The first operand in a REPLACING clause of a COPY statment is pseudo-text but the pseudo-text is null.

Cause: Invalid syntax in a <special> clause or paragraph.

Cause: An END-EXEC was not found while processing an EXEC clause.

Cause: A reserved word, <reserved>, was found in an illegal context.

Cause: This message follows another message that describes the actual error. The line following this message echos the input COBOL source line.

Cause: An OCCURS clause describes a variable length table. One needs a DEPENDING ON phrase to tell how large is the current instance of the table. The DEPENDING ON clause is missing. DEPENDING ON phrase that tells how large the current instance

Cause: A PICTURE clause specifies a DBCS datatype, but the required USAGE IS DISPLAY-1 clause is misisng or inavlid.

Cause: A LENGTH IS clause was specified for a data item that is not non-edited character data.

Cause: An error occured reading the log file.

Cause: The predicate that was chosen to delete the row from the PGA_TCP_IMSC table is not found.

Cause: The parameter, <parm> length, <len>, passed to PG4TCPMAP tool was larger than the maximum allowed, <max>.

Cause: An error occured processing pg4tcpmap tool. This message is preceded by additional messages providing more information about the error.

Cause: This is a warning that you have entered an invalid value.