| Oracle Procedural Gateway® for APPC Messages Guide 10g Release 2 (10.2) for UNIX and Microsoft Windows Part Number B16213-01 |
|
|
View PDF |
| Oracle Procedural Gateway® for APPC Messages Guide 10g Release 2 (10.2) for UNIX and Microsoft Windows Part Number B16213-01 |
|
|
View PDF |
This chapter lists the messages issued by the Procedural Gateway Administration Utility (PGAU) and provides a possible cause and recommended action for each message.
This chapter contains the following sections:
PGAU tried to open a spool file after you entered SPOOL file name, but it could not open the file. Possible causes could be lack of disk space or inadequate privileges to create a file.PGAU could not create a new file, and then retry.PGAU cannot locate or open the file specified by the PFILE option, either because the file does not exist, or because PGAU has insufficient privileges to open the file.PGAU and that it can be opened.PGAU cannot process the DATA in the database.DATA is greater than the version of the tool, then you are using the wrong version of the tool. If the version of the tool is greater than the version of the DATA, then check for an Oracle-supplied SQL script to update the DATA to the correct version level.PGAU initialization variable that points to the initialization file is not a recognizable file name.PGAU encountered a syntax error during the parse operation (oper) of the statement (statement) for the table (table) with the indicated return code (rc).PGAU statement identifier names for proper spelling and punctuation or other syntax errors.oper) on the variable (varname) for the statement (statement) against the PG DD table (table) failed with return code (rc).PGAU script.PGAU logic error that should not occur. An error occurred opening a SQL statement cursor. Only syntax checking continues with the next statement.PG DD is operational. Otherwise, regenerate the error with symptom documentation. Supported customers should contact Oracle Support Services for assistance.PG DD is operational. Otherwise, regenerate the error with symptom documentation. Supported customers should contact Oracle Support Services for assistance.PGAU logic error that should not occur. An error occurred, while attempting to commit changes to the PG DD. Only syntax checking continues with the next statement.PG DD is operational. Otherwise, regenerate the error with symptom documentation. Supported customers should contact Oracle Support Services for assistance.PGAU logic error that should not occur. An error occurred during logoff from the Oracle server. Only syntax checking continues with the next statement.PG DD is operational. Otherwise, regenerate the error with symptom documentation. Supported customers should contact Oracle Support Services for assistance.PGAU logic error that should not occur. An error occurred attempting to roll back changes from the PG DD. Only syntax checking continues with the next statement.PG DD is operational. Otherwise, regenerate the error with symptom documentation. Supported customers should contact Oracle Support Services for assistance.PGAU successfully completed generation of the TIP specification for the transaction (tranname) and the version (version) into the file (fileid).LMS functions, PGAU tracing or logging to disks was requested, but PGAU failed to open the indicated trace or log file (fileid).LMS functions, PGAU tracing or logging to disks was requested, but PGAU failed to close the indicated trace or log file(fileid).LMS functions, PGAU failed to obtain bytes of storage for use thatmeets the requirements specified in the with LMS initialization.PGAU during operation.LMS functions, the environment variable LANGUAGE specified an invalid Oracle NLS language, lang. The language environment variable (SSTDLANG) setting was used as the default.LANGUAGE environment variable to specify a valid Oracle NLS language.LMS functions, the PGAU message file (fileid) could not be located.$ORACLE_HOME/pg4appc/mesg directory and is not damaged. Valid file IDs are of the form pguxx.msb, where xx is the country code.oper processing for the file, fileid, with return code, rc. File operations include fclose to close input or output files, or remove to erase, delete, or remove output files.PGAU has access to the file specified and write access if the file is used for output.fprintf routine returned the indicated error code rc when attempting to print PGAU error message number msgno. The indicated event message was being written when the error occurred.PGAU has write access to the pgau.log file and that disk space is available for file growth.fprintf routine returned the indicated error code rc when attempting to print PGAU trace message number msgno. The indicated trace message was being written when the error occurred.PGAU has write access to the pgau.trc file and that disk space is available for file growth.parmname parameter specified an aggregate data record for which the 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 is:
Each attribute is stored as a separate row in the PG DD, and the row for the missing attribute might have been deleted from the PG DD.
PG DD to ensure that the failing field has a level attribute assigned.PGAU was processing nested records when the next field f# for nest level count exceeded the defined minimum or maximum nest level limit for the product.PGAU was processing nested records when the next field 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 occurs when special fields such as COBOL RENAMES (at LEVEL 66), appear next after the level 01 definition.GENERATE operation.PG DD rows are exceeding the attribute limit. Delete any possible duplicates. Supported customers should contact Oracle Support Services for assistance.func) to the work output file (file). An error occurred during generation of the TIP Package Specification.PGAU encountered an error appending the TIP variable definition var to the work output file (file). An error occurred during generation of the TIP Package Specification.PGAU has write access to the file specified and that disk space is available for TIP output work file growth.PL/SQL names. PGAU encountered record field names that, when combined, exceed the maximum PL/SQL name length. The last field name specified (field) was truncated to the length len. This condition occurred during generation of the TIP Package Specification for parameter variables.type) for the indicated field name (name). This message should be preceded by the specific error. This condition occurred during the generation of the TIP Package Specification for parameter variables.(mode) specified for the parameter (parm). Valid parameter modes are IN, OUT, or IN OUT. This is a probable PG DD content error.PG DD entries for the indicated parameter, and correct the PL/SQL parameter call mode for the indicated parameter.PL/SQL record type (type) was encountered while generating conversion statements for a data field (field). The indicated type is neither valid PL/SQL nor a nested record type for the indicated record field. This is a probable PG DD content error.PG DD entries for the indicated parameter, and either correct the PL/SQL variable type for the field, or define a corresponding nested record for the field.PL/SQL record field variable name (recname.varname), exceeded the maximum length allowed by PL/SQL, maxlen. This error occurred during generation of the TIP package specification for parameter variables.PG data dictionary entries for the defined parameters, and either reduce the number of nested record levels, or shorten the record field names.TIP function call, cname at parameter, parm, 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. This is probably a PGAU DEFINE CALL error, coding too many parameters. The IN OUT mode parameters are present in both send and receive buffers and might be causing the limit problem.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. The condition occurred during the generation of the TIP Package Specification for parameter variables.PL/SQL conversion statements for the indicated parameter data (dname) for function call, could not be generated. This message might be preceded by specific messages describing the error. Possible errors include disk access, invalid datatype and missing nested record or field datatype definitions.PG DD entries for the indicated parameter are correct and that disk access is allowed to output work files.PL/SQL statement, stmt, that is used to control TIP processing of the field, fname for compiler clause, clause, could not be generated.
Typical IBMVSCOBOLII clauses are:
OCCURS - requires FOR/LOOP logicOCCURS DEPENDING ON - requires FOR/LOOP logicREDEFINES - requires IF/END IF logicThis message might be preceded by specific messages describing the error. Possible errors include disk access, invalid datatype, missing nested record or field datatype definitions.
PG DD entries for the indicated parameter are correct and that disk access is allowed to output work files.PL/SQL control logic statements (stmt) to process the TIP parameter dname in the function cname failed. This message might follow more specific messages describing the error. Possible errors include disk access, invalid datatype, and missing next record or field datatype definitions.PG DD entries for the indicated parameter are correct and that disk access is allowed to the output work files.d-field f#, was referenced by other fields, which required that PL/SQL statements (stmt) be generated for the value num, but an error occurred during the generation of the statements. This message might follow specific messages describing the error. Possible errors include disk access and memory exceeded.TIP execution diagnostics for PG DD references PKGEX(DR) was requested on the PGAU GENERATE statement, but the PG DD reference for type id# could not be generated. This message might be preceded by specific messages describing the error. Possible errors include disk access and memory exceeded.(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.pgddsf.sql script to regenerate the selected rows and then correct the mask and maskopts columns for the stated field in the PG DD.field, containing a clause of the form syntax required a missing attribute, attr, corresponding to token. PGAU issues messages PGU-30603 and PGU-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-1TOint-2 TIMES DEPENDING ON name-1
where:
int-1 is the token for attribute repgrpvf
int-2 is the token for attribute repgrpv1
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 renamem1
field REDEFINES name-1 WHEN name-2 = value
where:
name-1 is the token for attribute remapsmf
name-2 is the token for attribute remapsm1
value is the token for attribute remapswc or 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 attributes row might have been deleted from the PG DD.
PG DD, redefine the referencing data item to restore the missing attribute row.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.pgddsxf.sql script to regenerate the selected rows and then correct the mask and maskopts columns for the invalid row in the PG DD.field) specifies character data in the PIC mask and USAGE maskopts clauses that require translation with a multibyte 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 PGU-30601 for mask and PGU-30602 for maskopts.pgddsxa.sql script to regenerate the selected rows, and then either correct the mask and maskopts columns for the stated field in the PG DD to not require MBCS translation, or use the PGAU REDEFINE DATA FIELD NLS_LANGUAGE (nlsname) parameter to specify an Oracle MBCS NLS name for the field, or specify the NLS_MBCS (nlsname) parameter on the PGAU DEFINE TRANSACTION statement.d-field, containing a clause of the form syntax, references a missing field, r-field, specified by the clause word, token. PGAU issues messages PGU-30610 and PGU-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 might be misspelled in the defining clause, or the referenced field whose name matches token might be missing from, or misspelled in, the PG DD.
PG DD, redefine the entry for d-field to change its clause token to specify the correct name of the intended field, r-field. You can also redefine the data name of the intended field, r-field, to match the subsequent clauses token reference. Also, ensure that the data field, d-field, containing the clause follows the intended field, r-field, in the data definition.TIP generation, a data field d-field was encountered for which no attr attribute existed. A new attribute row was created but could not be inserted into the PG DD.d-field f# specified an attribute that specifies remote host boundary alignment. The PG DD environment tables were searched for alignment information for environment (ename) compiler (compno), data type (dtype), data type alignment group dagno, but no entries were found matching these characteristics. PGAU issues messages PGU-30360 and PGU-30631 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 environment and compilers are IBM370 for IBMVSCOBOLII compiler.
Supported alignment attributes are:
d-field ... PIC S9(n) dtype SYNCd-field ... PIC S9(n) dtype SYNCHRONIZESupported datatype values are:
COMPCOMPUTATIONALCOMP-4COMPUTATIONAL-4Datatype grouped under dagno by length and alignment are:
dagno = 1 for 2-byte length aligned on 2-byte boundarydagno = 2 for 4-byte length aligned on 4-byte boundaryPossible causes are:
The TRANSACTION entry in the PG DD for the TIP that was being generated might have specified an invalid ENVIRONMENT.
The DATA entry in the PG DD was being referenced in the TIP function call that was generated might have specified an invalid LANGUAGE.
The field data type and length within the DATA entry might be invalid or unsupported.
The PG DD might be unavailable. Preceding messages indicate problems accessing the PG DD.
PG DD, redefine the TRANSACTION or DATA entries to correct the specification of the ENVIRONMENT, LANGUAGE, or field data type and attributes. Ensure that the Oracle server that supports the PG DD is active. If the error persists, then regenerate the error with tracing enabled. Supported customers can contact Oracle Support Services for assistance.d-field f# data field specified a modifying clause (clause) that is ignored for dtype data typeby the compiler in the remote host environment.
Supported environment and compiler is IBM370 for the IBMVSCOBOLII compiler.
SYNC/SYNCHRONIZE is ignored when dtype is one of the following:
COMP-3/COMPUTATIONAL-3DISP/DISPLAYd-field f# data field 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. TIPs use PL/SQL tables to implement repeating groups, and PL/SQL tables are limited to a single key or subscript that cannot support nested repeating groups (a table of tables).d-field f# data field specified an attribute (attr)and its value, attrval, is ignored.
Supported environment and compiler is IBM370 for the IBMVSCOBOLII compiler.
The LEFT attrval is ignored when attr is one of the following:
JUST/JUSTIFYSYNC/SYNCHRONIZEPGAU SQL statement, stmtname, failed with the Oracle error rc. This message is preceded by an Oracle server message for the specific error encountered.PG DD is active. If the error persists, then regenerate the error with tracing enabled. Supported customers should contact Oracle Support Services for assistance.PGAU SQL statement, stmtname, for Oracle cursor, curno, failed with Oracle error rc. This message is preceded by an Oracle server message for the specific error encountered.PG DD is active. If the error persists, then regenrate the error with tracing enabled. Supported customers should contact Oracle Support Services for assistance.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.PG DD is active. If the error persists, then regenerate the error with tracing enabled. Supported customers should contact Oracle Support Services for assistance.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.PG DD is active. If the error persists, then regenerate the error with tracing enabled. Supported customers should contact Oracle Support Services for assistance.curno, to the PGAU SQL statement, stmtname, failed with Oracle error rc. This is possible error in a PGAU GENERATE statement transaction or version parameters, the missing rows, or misspelling in the PG DD for the requested transaction. This message is preceded by an Oracle server message for the specific error encountered.PG DD. If the error persists, then regenerate the error with tracing enabled. Supported customers should contact Oracle Support Services for assistance.curno, to the PGAU SQL statement, stmtname, failed with Oracle error rc. This is possible error in a PGAU GENERATE statement transaction or version parameters, the missing rows, or misspelling in the PG DD for the requested transaction. This message is preceded by an Oracle server message for the specific error encountered.PG DD. If the error persists, then regenerate the error with tracing enabled. Supported customers should contact Oracle Support Services for assistance.curno, for PGAU SQL statement, stmtname, failed with Oracle error rc. This message is preceded by an Oracle server message for the specific error encountered.PG DD is active. If the error persists, then regenerate the error with tracing enabled. Supported customers should contact Oracle Support Services for assistance.PG DD for the PGAU SQL statement, stmtname, with the 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 was missing from the PG DD. This message is preceded by an Oracle server message for the specific error encountered.PG DD, or correct the GENERATE statement.The type rows were not fetched from the PG DD for the PGAU SQL statement, statement, 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.PG DD, or correct the GENERATE statement.statement, 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 were missing from the PG DD. This message is preceded by an Oracle server message for the specific error encountered.PG DD, or correct the GENERATE statement.tname tver was not found in the PG DD. Either the transaction name and version supplied on the GENERATE statement were invalid, or the transaction specified in a previous DEFINE TRANSACTION, tname, might have been deleted from, or altered in, the PG DD. This message might be preceded by specific messages describing the error.PG DD, or correct the GENERATE statement.tname tver (tin), was not found in the PG DD. The call entry that is associated with the transaction (as specified in a previous DEFINE TRANSACTION ... CALL(cname)) might have been deleted from, or altered in, the PG DD. This message might be preceded by specific messages describing the error.PG DD, or correct the GENERATE statement to request a different 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)) might have been deleted from, or altered in, the PG DD. This message might be preceded by specific messages describing the error.PG DD, or correct the GENERATE statement to request a different transaction.tname tversion (tin), call cname cversion (cin) parmeter relno and data dname dversion (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) might have been deleted from, or altered in, the PG DD. This message might be preceded by specific messages describing the error.GENERATE statement to request a different transaction.tname tver, the data field usage, mask, and maskopts entries were not found in the PG DD. All PG DD tables are searched, starting with pga_trans through pga_fields, to select rows having usage=PASS and not null mask and maskopts columns. These are used to identify data fields use UTL_PG MAKE_..._FORMAT conversions.
Possible invalid entries in pga_fields ( usage, mask, maskopts ) columns. This message might be preceded by specific messages describing the error.
PG DD.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 number stored in a call parameter data entry have no environment rows stored in the PG DD environment tables. This message might be preceded by specific messages describing the error.PG DD is active and that the TRANSACTION ENVIRONMENT name and the DATA LANGUAGE name are defined in the PG DD with supported values. If the error persists, then regenerate the error with tracing enabled. Supported customers can contact Oracle Support Services for assistance.statement, with date format dfmt and time format tfmt. The Oracle error code is rc. Either the date and time formats that are specified are invalid, or some other Oracle server error occurred. This message is preceded by an Oracle server message for the specific error encountered.TIP package generation tracing active. Successful generation of TIP data conversion logic. This trace entry is written at the completion of the generation for every data parameter of a TIP call and for every 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.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.DEFINE or REDEFINE DATA statement has specified an invalid name (field) or invalid punctuation for the field definition. A field name must begin with an alphabetic character and contain only alphanumeric characters or an underscore (_). Only syntax checking continues with the next statement.keyword) was correctly specified, but the parameter value was not found. Only syntax checking continues with the next statement.PGAU statement. PGAU parameter values should be enclosed in parentheses immediately following the keyword with no intervening space.DEFINE DATA or REDEFINE DATA statement. A DATA identifier (dname) must begin with an alphabetic character and must contain only alphanumeric characters. Only syntax checking continues with the next statement.DATA identifier dname in the statement.PLSDNAME clause of a DEFINE or REDEFINE DATA statement does not comply with PL/SQL syntax for PL/SQL variable names. Only syntax checking continues with the next statement.PLSDNAME parameter to use a name that complies with PL/SQL syntax for data variables.LANGUAGE parameter in a DEFINE or REDEFINE DATA statement is not a valid PGA compiler language. Only syntax checking continues with the next statement.LANGUAGE parameter to specify a valid PGA compiler language. The only valid language is IBMVSCOBOLII.USAGE parameter was specified more than once in a DEFINE or REDEFINE DATA statement. This parameter can be specied only once for each data definition. Only syntax checking continues with the next statement.USAGE from the PGAU statement.LANGUAGE parameter was specified more than once in a DEFINE or REDEFINE DATA statement. This parameter can be specied only once for each data definition. Only syntax checking continues with the next statement.LANGUAGE from the PGAU statement.PLSDNAME parameter was specified in a DEFINE or REDEFINE DATA statement. This parameter can be specied only for each data definition. Only syntax checking continues with the next statement.PLSDNAME from the statement.COMPOPTS parameter in a DEFINE or REDEFINE DATA statement is not a valid compiler option string recognized by PGAU. Only syntax checking continues with the next statement.COMPOPTS parameter to specify valid options. The only valid option is TRUNC(BIN).COMPOPTS parameter was specified more than once in a DEFINE or REDEFINE DATA statement. This parameter can be specied only once, for each data definition. Syntax checking only continues with the next statement.COMPOPTS from the PGAU statement.DEFINE CALL statement. A CALL identifier (cname) must begin with an alphabetic character and contain only alphanumeric characters. Only syntax checking continues with the next statement.CALL identifier (cname) in the statement.PKGCALL parameter keyword, was specified more than once in a DEFINE CALL statement. This parameter can be specied only once for each call definition. Only syntax checking continues with the next statement.PKGCALL from the statement.PKGCALL parameter of a DEFINE CALL statement does not comply with PL/SQL syntax for PL/SQL function names. Only syntax checking continues with the next statement.PKGCALL parameter to use a name that complies with PL/SQL syntax for function calls.PGAU DEFINE, UNDEFINE CALL, TRANSACTION, or GENERATE statement. Valid version numbers are all numeric and must match the Oracle sequence object value reported by a previous DEFINE statement. Only syntax checking continues with the next statement.VERSION number in the statement.DEFINE CALL statement. This parameter can be specied only once for each call definition. Only syntax checking continues with the next statement.PARMS from the statement.DEFINE TRANSACTION statement. A CALL identifier (cname) must begin with an alphabetic character and contain only alphanumeric characters and it must have originated in a previous DEFINE CALL statement. Only syntax checking continues with the next statement.TRANSACTION CALL parameter (cname) in the statement.NLS_LANGUAGE parameter was specified more than once in a DEFINE TRANSACTION statement. This parameter can be specied only once for each transaction definition. Only syntax checking continues with the next statement.NLS_LANGUAGE from the statement.PGAU parameter (parm) specifies an Oracle NLS language name (nlsname) that is not defined on the Oracle server to which PGAU is connected. The language (nlsname) is not defined, possibly because it was not selected when Oracle was installed, or the GENERATED TIPs are intended to run on another Oracle.* or it is not a valid Oracle NLS Language, because it is misspelled or unsupported. Only syntax checking continues with the next statement.NLS Language, or install the language, or ensure the TIPs execute on a server which has the NLS language installed, (in which case this message can be considered a warning). Valid languages must begin with an alphabetic character, contain only alphanumeric characters, and not exceed 40 characters in length. Supported customers can contact Oracle Support Services for assistance with installing or determining NLS language support for your platform.ENVIRONMENT parameter was specified more than once in a DEFINE TRANSACTION statement. This parameter can be specied only once for each transaction definition. Only syntax checking continues with the next statement.ENVIRONMENT from the statement.ENVIRONMENT parameter in a DEFINE TRANSACTION statement was not a valid PGA ENVIRONMENT. Only syntax checking continues with the next statement.ENVIRONMENT parameter to specify a valid PGA ENVIRONMENT. The only valid environment is IBM370.SIDEPROFILE parameter was specified more than once in a DEFINE TRANSACTION statement. This parameter can be specied only once for each transaction definition. Only syntax checking continues with the next statement.SIDEPROFILE from the statement.SNA Side Profile in a DEFINE TRANSACTION statement. A Side Profile name must begin with an alphabetic character and contain only alphanumeric characters. Only syntax checking continues with the next statement.TRANSACTION SIDEPROFILE parameter in the statementLUNAME parameter was specified more than once in a DEFINE TRANSACTION statement. This parameter can be specied only once for each transaction definition. Only syntax checking continues with the next statement.LUNAME from the statement.SNA LU name in a DEFINE TRANSACTION statement. An LU name must begin with an alphabetic or national ($, #, @) character and contain only alphanumeric or national characters. If the LU name is fully qualified, then it can contain a single period (.) separating the network name from the LU name. Only syntax checking continues with the next statement.TRANSACTION LUNAME parameter in the statement.TPNAME parameter was specified more than once in a DEFINE TRANSACTION statement. This parameter can be specied only once for each transaction definition. Only syntax checking continues with the next statement.TPNAME from the statement.SNA TP name in a DEFINE TRANSACTION statement. A TP name must begin with an alphabetic or national ($, #, @) character and contain only alphanumeric or national characters. If the TP name must include a UNIX path specification, then it can contain any characters valid in a UNIX directory or file name, but it must be enclosed in quotes. Only syntax checking continues with the next statement.TRANSACTION TPNAME parameter in the statement.LOGMODE parameter was specified more than once in a DEFINE TRANSACTION statement. This parameter can be specied only once for each transaction definition. Only syntax checking continues with the next statement.LOGMODE from the statement.SNA logmode in a DEFINE TRANSACTION statement. A log mode must begin with an alphabetic or national ($, #, @) character and contain only alphanumeric or national characters. Only syntax checking continues with the next statement.TRANSACTION LOGMODE parameter in the statement.SYNCLEVEL parameter was specified more than once in a DEFINE TRANSACTION statement. This parameter can be specied only once for each transaction definition. Only syntax checking continues with the next statement.SYNCLEVEL from the statement.APPC SYNCLEVEL in a DEFINE TRANSACTION statement. The only values allowed for SYNCLEVEL are 0 and 1. Only syntax checking continues with the next statement.TRANSACTION SYNCLEVEL parameter in the statement.DEFINE TRANSACTION statement. A transaction name must begin with an alphabetic character and contain only alphanumeric characters. Only syntax checking continues with the next statement.TRANSACTION name parameter in the statement.SNA SIDEPROFILE parameter was not specified, then the LUNAME, TPNAME, and LOGMODE parameters must be specified in a DEFINE TRANSACTION statement. Only syntax checking continues with the next statement.DEFINE TRANSACTION statement to specify either the SIDEPROFILE parameter, the LUNAME, TPNAME and LOGMODE parameters, or the SIDEPROFILE parameter and any combination of the LUNAME, TPNAME, and LOGMODE parameters.CALL parameter was specified more than once in a DEFINE TRANSACTION statement. This parameter can be specied only once for each transaction definition. Only syntax checking continues with the next statement.CALL parameter from the statement.parm parameter was specified more than once in a DEFINE TRANSACTION statement. This parameter can be specied only once for each transaction definition. Only syntax checking continues with the next statement.parm parameter from the DEFINE TRANSACTION statement.VERSION parameter was specified more than once but this parameter can be specied only once in a GENERATE or REDEFINE statement. Only syntax checking continues with the next statement.VERSION from the statement.VERSION keyword enclosed in parenthesis in a GENERATE or REDEFINE statement. Only syntax checking continues with the next statement.VERSION parameter.FIELD or PLSFNAME parameter in a REDEFINE DATA statement. A field identifier name must begin with an alphabetic character and contain only alphanumeric characters. Only syntax checking continues with the next statement.FIELD or PLSFNAME identifier name in the statement.GENERATE statement. A transaction identifier name must begin with an alphabetic character and contain only alphanumeric characters. In addition, it must originate in a previous DEFINE TRANSACTION statement. Only syntax checking continues with the next statement.PKGNAME parameter was specified more than once in a GENERATE statement. This parameter can be specied only once for each GENERATE request. Only syntax checking continues with the next statement.PKGNAME from the statement.PL/SQL TIP package name in a GENERATE statement. A package name identifier must begin with an alphabetic character and contain only alphanumeric characters. Only syntax checking continues with the next statement.GENERATE PKGNAME parameter in the statement.OUTFILE parameter was specified more than once in a GENERATE statement. This parameter can be specied only once for each GENERATE request. Only syntax checking continues with the next statement.OUTFILE from the statement.DIAGNOSE parameter has already been specified more than once in a GENERATE statement and is only allowed once for each GENERATE request. Only syntax checking continues with the next statement.DIAGNOSE from the statement.PGANODE parameter was specified more than once in a GENERATE statement. This parameter can be specied only once for each GENERATE request. Only syntax checking continues with the next statement.PGANODE from the statement.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 it must be a valid Oracle database link name. Only syntax checking continues with the next statement.PGANODE parameter in the statement.INFILE parameter in a DEFINE or REDEFINE DATA statement. Only syntax checking continues with the next statement.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.COBOL data definition starts on a line following a left parenthesis.OPTIONS parameter was specified more than once in a GENERATE statement. This parameter can be specied only once for each GENERATE request. Only syntax checking continues with the next statement.OPTIONS from the statement.OPTIONS parameter. The only valid OPTIONS subparameter is UDF. It can be specified only once for each GENERATE statement. Only syntax checking continues with the next statement.OPTIONS specification.TRACE parameter was specified more than once in a GENERATE statement. This parameter can be specied only once for each GENERATE request. Only syntax checking continues with the next statement.TRACE from the statement.DIAGNOSE TRACE or PKGEX parameter. The valid parameters are SE, IT, QM, IO, DD, TG, OC, DC and DR, and each can be specified only once for each GENERATE statement. Only syntax checking continues with the next statement.TRACE or PKGEX specification.PKGEX parameter was specified more than once in a GENERATE statement. This parameter can be specied only once for each GENERATE request. Only syntax checking continues with the next statement.PKGEX from the statement.PGAU inserted the transaction definition, tname, with the version number ,tver, as the result of processing a DEFINE TRANSACTION statement.VERSION number of the transaction definition for future reference.DEFINE CALL referenced a data definition name (dname) that does not exist, or specified a nonexistent version (dver) of the data definition (dname).DEFINE TRANSACTION referenced a call definition name (cname) that does not exist, or specified a nonexistent version (cver) of the call definition (cname).DEFINE TRANSACTION statement.UNDEFINE DATA referenced a data definition name (dname) that does not exist, or specified a non-existent version (dver) of the data definition (dname).UNDEFINE DATA statement.UNDEFINE CALL referenced a call definition name (cname) that does not exist, or specified a nonexistent version (cver) of the call definition (cname).UNDEFINE CALL statement.UNDEFINE TRANSACTION referenced a transaction definition name (tname) that does not exist, or specified a non-existent version (tver) of the transaction definition (tname).UNDEFINE TRANSACTION statement.LANGUAGE parameter in a REDEFINE DATA statement for a given data name specified a different language from the one originally specified in the DEFINE DATA statement.LANGUAGE parameter in the REDEFINE DATA statement to that of the original DEFINE DATA statement. The associated language-dependent field definitions must also be changed.REDEFINE with the FIELD parameter specified a field name, (fname), that does not currently exist in the data object being redefined.FIELD parameter. Use the REPORT DATA statement to list current field names.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 DEFINE DATA statement.INFILE instance or the inline data definition.INFILE parameter was found in a DEFINE DATA or REDEFINE DATA statement. One of these is required in a DEFINE DATA statement. One of these might be required in a REDEFINE DATA statement, depending on which other parameters are specified.INFILE parameter or an inline data definition.INFILE parameter was specified more than once in a DEFINE DATA or REDEFINE DATA statement. This parameter can be specied only once for each data definition or redefinition. Only syntax checking continues with the next statement.INFILE from the statement.REDEFINE statement for a field specified a field that does not exist in the given data definition.REPORT verb to find out what exists.REDEFINE specified a field name that was defined more than once.FIELD1.SUBFIELD2. It might be easier to just REPORT the DATA designation into an output file, edit the output file and REDEFINE the DATA object.param parameter was specified without the FIELD parameter. The FIELD parameter, is a prerequisite to specify the parm parameter because parm applies to FIELDs within a DATA redefinition. PGAU REDEFINE parameters that require FIELD are:
PLSFNAMECODEPAGEFIELD parameter in the REDEFINE statement to indicate to the FIELD to which the redefinition of parm applies, or remove the parm specification.REPORT command requested information about a PGAU data object with a type specified by type and named name. However, an object with that name was not found.REPORT command requested information about a specified by PGAU data object with a type specified by type, a name specified byname, and a version of ver. However, an object with that name and version was not found.PKGCALL parameter was defaulted in a DEFINE CALL statement. By default, it takes the value of the CALL object name. However, the length of the CALL object name was greater than the maximum length allowed for the PKGCALL parameter, which is 30. The default value used was value.PLSDNAME parameter was defaulted in a DEFINE DATA statement. By default, it takes the value of the DATA object name. However, the length of the DATA object name was greater than the maximum length allowed for the PLSDNAME parameter, which is 30. The default value used was value.COPY reserved word was used as operand-1 or operand-2 in the REPLACING clause of a COPY statement, and this is not alowed.COPY with some other word here and in the copied source file. If it is operand-2, then check the offending COPY clause for missing terminator or reserved words.A and B.VALUES keyword can only be specified in a data definition describing a condition and only at level 88.VALUE IS rather than VALUES ARE.type cannot come after a phrase introduced by phrase. Certain phrases must precede other phrases in a data definition. For instance, an ASCENDING [KEY] phrase must appear before an INDEXED clause.COPY statement for the file, filename, was found while processing a previous occurrence of a COPY for the same file.COBOL source for the recursive COPY. A single COPY file may need to be replaced with multiple, uniquely named COPY files to achieve your desired results.DEPENDING ON clause was missing. An OCCURS clause describes a variable length table. The DEPENDING ON phrase is required to determine the size of the current instance of the table.DEPENDING ON clause, or make the table a fixed-length table.