This chapter describes the three types of messages generated by the CA IDMS Schema Mapper Audit Report: informative, warning, and error. This chapter lists the codes for each message, gives reasons for their occurrences, and suggests remedial actions when appropriate. The severity codes are explained below.
Informative--Prefixed by an Innn message code. Informative messages report processing starts, stops, and parameter information.
Warning--Prefixed by an Wnnn message code. Warning messages report conflicting parameter data. When CA IDMS Schema Mapper reports a warning messages, it performs corrective actions to continue processing.
Error--Prefixed by an Ennn message code. Error messages report erroneous and conflicting parameter data that causes processing to terminate. CA IDMS Schema Mapper continues, however, to scan the parameter statements for other syntactical errors.
Note: If CA IDMS Schema Mapper encounters a blank field to be printed in amessage, it prints the field as four question marks.
Reason: Displays the date in month, day, and year and the time in hour, minute, and second that CA IDMS Schema Mapper started processing.
Action: None.
Reason: Displays the parameter statements for this execution of CA IDMS Schema Mapper.
Action: None.
Reason: Displays the date in month, day, and year and the time in hour, minute, and second that CA IDMS Schema Mapper ended processing.
Action: None.
Reason: Display of the maximum coordinates for which space was allocated.
Action: None.
Reason: The diagram cannot be generated because of fatal errors. CA IDMS Schema Mapper continues to scan the parameter statements for syntactical errors.
Action: Review error messages and resolve errors after CA IDMS Schema Mapper finishes processing.
Reason: Displays a parameter statement that CA IDMS Schema Mapper has generated. Generally, this is a LOCATE statement for a record block that you did not manually LOCATE.
Action: None.
Reason: Displays the version of CA IDMS used to compile the schema and the date of the schema compile (in month, day, and year). (If the DATE FIELD from the SCHEMA DESCRIPTION has been filled in, that date is displayed instead of the compile date.)
Action: None.
Reason: Displays the date of the subschema compile (in month, day, and year). The version of CA IDMS used to compile a subschema is not available in the dictionary/directory. (If the DATE FIELD from the SUBSCHEMA DESCRIPTION has been filled in, that date is displayed instead of the compile date.)
Action: None.
Reason: Displays the version of the schema.
Action: None.
Reason: Displays the version of CA IDMS under which CA IDMS Schema Mapper is running.
Action: None.
Reason: RECLINE or SETLINE statements did not include this key in the Data Structure Diagram or Cross-Reference Report. Number corresponds to the implied subscript in LOC-CTRL or SET-ORDER. Kind is RECORD, SET, or INDEX. Name is the name of the record, set, or index.
Action: None.
Reason: This message is a continuation of I011. The name of the key referred to in the preceding I011 is indicated by key-name in this message.
Action: None.
Reason: CA IDMS Schema Mapper did not find any schema records in the requested dictionary.
Action: Add schemas to this dictionary or use a different dictionary.
Reason: CA IDMS Schema Mapper uses this message when listing the contents of a dictionary.
Action: None.
Reason: CA IDMS Schema Mapper uses this message when listing the contents of a dictionary.
Action: None.
Reason: CA IDMS Schema Mapper did not find any subschemas defined for the current schema.
Action: None.
Reason: CA IDMS Schema Mapper uses this message when assigning actual membership option.
Action: None.
Reason: CA IDMS Schema Mapper uses this message when a statistic file is created.
Action: None.
Reason: User specified COMPNAME= or DCOMNAME= but did not enter a value. Schema Mapper will default to IDMSCOMP or IDMSDCOM.
Action: None.
Reason: This is a debugging message which displays the db procedure Schema Mapper will use.
Action: None.
Reason: More than one LOCATE statement is used for the
designated record. CA IDMS Schema Mapper processes the first LOCATE and ignores the second statement.
Action: Verify that the record is located where you want it. Delete the extra statement.
Reason: This message is reserved for technical support purposes.
Action: Contact Technical Support.
Reason: A LOCATE statement requests space already allocated to another record through a previous LOCATE. The LOCATE statement is skipped, which can create a ripple effect in which subsequent LOCATEs are flagged with the W005 message number. CA IDMS Schema Mapper places the first record specified in the LOCATE statement in the diagram after all LOCATE statements are processed.
Action: Verify placement of the records. Revise or delete LOCATEs as needed.
Reason: The record ID number for the record indicated is either less than 1 or greater than 9999. A record ID value of 0 is used for this record.
Action: Check the record ID value in the CA IDMS dictionary. The value is created using the Record Description paragraph in the Schema Data Description Language. The value is stored in the SR-ID-113 element of the SRCD-113 record in the dictionary.
Reason: The second record name in a LOCATE statement is used as a reference. It must be LOCATEd before the current LOCATE can be processed. A LOCATE statement is missing, or the LOCATE statements are out of sequence. The current LOCATE statement is skipped, which can create a ripple effect in which subsequent LOCATEs are flagged with the same warning. CA IDMS Schema Mapper places the first record of the LOCATE statement in the diagram after all LOCATE statements are processed.
Action: Check to see that a LOCATE statement is not missing or out of sequence.
Reason: This message is reserved for technical support purposes.
Action: Contact Technical Support.
Reason: For the set or index indicated (by set-name), the set connect value obtained from the CA IDMS dictionary is not consistent with the set order value obtained from the dictionary. The case number in the message indicates what has occurred:
CASE 0 The set order is 0 (last or prior) and the set connect is not 0 or 1.
CASE 1 The set order is 1 (sorted) and the set connect is not 0.
CASE 2 The set order is 2 (first or next) and the set connect is not 0 or 1.
Action: Check your dictionary for the values of these two elements. Set order is stored in the SET-ORD-046 element of the SOR-046 record for both schemas and subschemas. Set connect is stored in the ORD-052 element of the SMR-052 record for schemas and in the ORD-068 element of the SSMR-068 record for subschemas.
The meaning of set connect values are:
0 = linked on owner (for first, last, or sorted)
1 = connect on current of set (for next, prior)
Reason: For the set or index indicated (by set-name), the sort sequence value was not 0 or 1.
Action: Check your dictionary for the value of this element. Sort sequence is stored in SORT-054 for schemas and SORT-070 for subschemas.
Reason: For the set or index indicated (by set-name), the duplicates value was not -1, 0, 1, or 2.
Action: Check your dictionary for the value of this element. Duplicates is stored in DUP-052 for schemas and DUP-068 for subschemas.
Reason: For the set or index indicated (by set-name), the sort order value was not 0, 1, or 2.
Action: Check your dictionary for the value of this element. Sort order is stored in SORT-046 for both schemas and subschemas.
Reason: For the set or index indicated (by set-name), the membership options value was inappropriate. The case number in the message indicates what has occurred:
CASE 1 The membership options value is -1.
CASE 2 The membership options value is not -1, 0, 1, 2, or 3.
Action: Check your dictionary for the value of this element. Membership options are stored in MR-CNTRL-052 for schemas and MCTL-068 for subschemas.
Reason: A LOCATE statement requests placement of a record block in a location that is outside of the work space used by CA IDMS Schema Mapper to construct the diagram. The LOCATE statement is skipped, which can create a ripple effect in which subsequent LOCATEs are flagged with the W005 message number. CA IDMS Schema Mapper places the first record specified in the LOCATE statement in the diagram after all LOCATE statements are processed.
Action: Verify placement of the records. Change the displacement value(s) in the LOCATE statement.
Reason: CA IDMS Schema Mapper allows only 26 pages across and 26 pages down for the diagram. The indicated item is at least partially outside of this limit. The part of the item that is outside does not appear in the diagram. By the time CA IDMS Schema Mapper detected this problem, the location of the item could not be changed.
Action: Use LOCATE statements to change either the location of the indicated record block or the locations of the record blocks that participate in the indicated set or index.
Reason: The CA IDMS dictionary entry specified a minimum fragment for the indicated record, but the record is a non-compressed fixed record. The LENGTH-MODE shown for the record in the diagram may be incorrect.
Action: Check the dictionary for the schema. You may find an error in the definition of this record. For example, if you wanted a length-mode of FC, you may have forgotten to request COMPRESS/DECOMPRESS.
Reason: CA IDMS Schema Mapper has already included the indicated name in the diagram. This was done when processing an earlier INCLUDE statement. The kind-of-name is AREA, RECORD, SET, or INDEX. CA IDMS Schema Mapper ignores the INCLUDE statement preceding this message.
Action: Remove the redundant INCLUDE statement from the input file (SYSIPT).
Reason: INCLUDE statements have been used, and the indicated record was not included in the diagram. Therefore, a LOCATE statement for this record has no meaning. The LOCATE statement preceding this message is ignored.
Action: Remove the irrelevant LOCATE statement from the input file (SYSIPT).
Reason: The indicated record participates as an owner or a member in more than 128 sets. CA IDMS Schema Mapper does not draw some of the set connections in the diagram. (See message W018.)
Action: Notify Technical Support.
Reason: CA IDMS Schema Mapper has previously used message W017 for a record that participates in this set.
Action: Notify Technical Support.
Reason: For the set or index indicated by set-name, the set mode value was inappropriate. Legal values for set-mode are 13, 15, 21, and 32 (decimal).
Action: Check your dictionary for the value of this element. Set mode is stored in SET-MODE-046 for both schemas and subschemas.
Reason: The SET-MODE field was requested in a SETLINE statement, but a set mode of INDEX is not available in the version of CA IDMS under which CA IDMS Schema Mapper is running. (See message I010 in the Audit Report.) CA IDMS Schema Mapper uses a blank SET-MODE value and continues processing.
Action: Do not use the SET-MODE field with this version of CA IDMS.
Reason: A subscript was used with the LOC-CTRL field in a RECLINE statement or the SET-ORDER field in a SETLINE statement. Subscripts on these fields are used only by the multiple CALC, sort, and index key feature that is not available in the version of CA IDMS under which CA IDMS Schema Mapper is running. (See message I010 in the Audit Report.) The first LOC-CTRL or SET-ORDER field has its normal value. (The use of LOC-CTRL(1) and SET-ORDER(1) is always allowed and does not trigger this message.) CA IDMS Schema Mapper uses a blank value for any additional LOC-CTRL or SET-ORDER fields and continues processing.
Action: Do not use LOC-CTRL or SET-ORDER subscripts with this version of CA IDMS.
Reason: You can place record fields in both the diagram and the cross-reference listing by using DRECLINE and XRECLINE statements respectively. Because these statements replace the RECLINE statement, any use of the RECLINE statement is interpreted as a DRECLINE statement by CA IDMS Schema Mapper.
Action: Translate RECLINE statements to DRECLINE statements.
Reason: You can place set fields in both the diagram and the cross-reference listing by using DSETLINE and XSETLINE statements respectively. Because these statements replace the SETLINE statement, any use of the SETLINE statement is interpreted as an XSETLINE statement by CA IDMS Schema Mapper.
Action: Translate SETLINE statements to XSETLINE statements.
Reason: Fields defined for DRECLINE, XRECLINE, DSETLINE, or XSETLINE require information from the STATFILE. The JCL does not reference a valid STATFILE.
Action: Change the xxxxLINE parameters or correct the JCL.
Reason: Fields defined for DSETLINE or XSETLINE require information from the STATFILE. The schema/subschema being mapped contains set-name, but STATFILE does not contain statistics for that set.
Action: Change the XSETLINE parameters or supply a proper STATFILE.
Reason: Fields defined for DRECLINE, XRECLINE, DSETLINE, or XSETLINE require information from the STATFILE. The schema/subschema being mapped contains set-name and member-name, but STATFILE does not contain statistics for that set.
Action: Change the XSETLINE parameters or supply a proper STATFILE.
Reason: Fields defined for DRECLINE, XRECLINE, DSETLINE, or XSETLINE require information from the STATFILE. The schema/subschema being mapped contains set-name and member-name, but STATFILE contains a record ID for member-name that is different than the record ID in the schema/subschema.
Action: Change the XSETLINE parameters or supply a proper STATFILE.
Reason: The feature described has not been implemented. The feature will be available in future versions of CA IDMS Schema Mapper.
Action: Do not try to use the feature.
Reason: The indicated keyword is required.
Action: Add the keyword to the parameter statement.
Reason: The designated schema name is misspelled or not in the dictionary. When ANY is given as the version number in this message, the designated schema could not be found with any version number in the dictionary.
Action: Check the spelling of the schema name and verify the version number specified.
Reason: The designated subschema name is misspelled or not defined for the requested schema and version.
Action: Check the spelling of the subschema name and verify it for the requested schema and version.
Reason: The PROCESS statement is not included or is not the first statement.
Action: Verify that the PROCESS statement is in the input and that it is the first statement supplied.
Reason: The second record name in the LOCATE parameter statement is missing.
Action: Add the second record name to the LOCATE statement.
Reason: The schema version number in the PROCESS parameter statement is not valid.
Action: Check the syntax of the schema version number on the PROCESS statement.
Reason: A character such as an exclamation point, which is not legal in any statement, or a character such as a hyphen, which is only legal within a name, is used. The character is skipped and syntax analysis continues. The erroneous statement appears immediately before this message.
Action: Check the statement for a character that is invalid or used out of context.
Reason: The OPTIONS parameter statement is used but does not immediately follow the PROCESS statement.
Action: Place the OPTIONS statement immediately following the PROCESS statement.
Reason:
Action:
Reason: A name is required in place of the indicated symbol. Either the name is missing or its syntax is incorrect. The erroneous statement appears immediately before this message.
Action: Verify that a name is in the indicated position and check its syntax.
Reason: A keyword is required at the location of the indicated symbol. The erroneous statement appears immediately before this message.
Action: Check the syntax of the statement for a missing keyword.
Reason: A field name specified in the RECLINE parameter statement is not predefined by CA IDMS Schema Mapper.
Action: Check the syntax of the field name and verify that it is a name known to CA IDMS Schema Mapper.
Reason: A field name specified in the SETLINE parameter statement is not predefined by CA IDMS Schema Mapper.
Action: Check the syntax of the field name and verify that it is a name known to CA IDMS Schema Mapper.
Reason: The data structure diagram exceeds the maximum layout space allowed (26 by 26 pages). The incomplete diagram is printed and the program terminates.
Action: Divide the schema into subschema sections and resubmit the job.
Reason: A parameter statement is not recognizable.
Action: Check the first word of the statement.
Reason: This message is reserved for technical support purposes.
Action: Contact Technical Support.
Reason: This message is reserved for technical support purposes.
Action: Contact Technical Support.
Reason: This message is reserved for technical support purposes.
Action: Contact Technical Support.
Reason: This message is reserved for technical support purposes.
Action: Contact Technical Support.
Reason: An internal integrity check in the program failed. The message is followed by output (printed without page ejects) that helps Technical Support personnel locate the error.
Action: Notify Technical Support and forward a full copy of the Audit Report to them.
Reason: The first record name in the LOCATE parameter statement is missing. The erroneous statement appears immediately before this message.
Action: Add the first record name to the LOCATE statement.
Reason: An integer is required in place of the indicated symbol. The integer is missing or its syntax is incorrect. The erroneous statement appears immediately before this message.
Action: Verify that an integer is in the indicated position and check its syntax.
Reason: A comma is required at the location of the indicated symbol. The erroneous statement appears immediately before this message.
Action: Check the syntax of the statement for a missing comma.
Reason: The indicated name is not a record in the schema or subschema being processed. Instead, the name identifies a set or index. Only record names can be used in this position of the statement. The erroneous statement appears immediately before this message.
Action: Delete the statement or replace the name with a valid record name.
Reason: Either UP, DOWN, LEFT, or RIGHT is required at the location of the designated symbol in a LOCATE statement.
Action: Verify that UP, DOWN, LEFT, or RIGHT is in the LOCATE statement and check the syntax.
Reason: The indicated name is not in the schema or subschema being processed. The name appears in the statement immediately preceding this message.
Action: Delete the statement or use a valid name.
Reason: This error can be caused by a number that is too large.
Action: Check the range of legal values for the number in this parameter statement.
Reason: CA IDMS Schema Mapper cannot perform the bind for this run-unit. This error is most likely caused by an unknown dictionary name. It can also occur if CA IDMS is not available. The normal CA IDMS error status is printed.
Action: Verify the dictionary name and check the syntax. Verify that CA IDMS is available.
Reason: A keyword is unknown. As an example, TURKEY is unknown to CA IDMS Schema Mapper in the statement PROCESS=SCH,TURKEY=7. The first seven positions of the unknown keyword are shown.
Action: Verify that the keyword is part of CA IDMS Schema Mapper's syntax.
Reason: A value is unknown. As an example, NEVER is an unknown value in the statement OPTIONS, IXSET=NEVER.
Action: Verify that the value is part of CA IDMS Schema Mapper's syntax.
Reason: An index corner value other than 2 or 4 is in the OPTIONS parameter statement. The IXCORNER value must be either 2 or 4; no other values are allowed.
Action: Change the IXCORNER value in the OPTIONS statement to either 2 or 4.
Reason: A border space value less than 2 or greater than 50 is in the OPTIONS parameter statement. The BORDER value must be between 2 and 50, inclusive; no other values are allowed.
Action: Change the BORDER value in the OPTIONS statement to a number between 2 and 50, inclusive.
Reason: A diagram page length value less than 33 or greater than 132 is in the OPTIONS parameter statement. The DPAGELEN value must be between 33 and 132, inclusive; no other values are allowed.
Action: Change the DPAGELEN value in the OPTIONS statement to a number between 33 and 132, inclusive.
Reason: A schema name is not specified in the PROCESS parameter statement.
Action: Add the schema name to the PROCESS statement.
Reason: A subschema name is not specified in the PROCESS parameter statement with PROCESS=SUBSCHEMA specified.
Action: Add the subschema name to the PROCESS statement.
Reason: The PROCESS keyword value in the PROCESS parameter statement is invalid.
Action: Check the syntax of the PROCESS keyword value indicated.
Reason: This message is reserved for technical support purposes.
Action: Contact Technical Support.
Reason: Optional parameter statements precede the PROCESS parameter statement.
Action: Place the PROCESS statement before optional parameter statements.
Reason: A LOCATE parameter statement is out of sequence.
Action: Check to see that all LOCATE statements are entered in a group after all of the other parameter statements.
Reason: The image value indicated is not valid.
Action: Check the validity of the IMAGE value.
Reason: The diagram page eject value indicated is not valid.
Action: Check the validity of the DPEJECT value.
Reason: This message is reserved for technical support purposes.
Action: Contact Technical Support.
Reason: This message is reserved for technical support purposes.
Action: Contact Technical Support.
Reason: The keywords UP, DOWN, LEFT, and RIGHT must always be followed by a number in a LOCATE parameter statement.
Action: Add a number to the LOCATE statement.
Reason: Multiple vertical displacements, as indicated with the UP and DOWN keywords, cannot be used in a LOCATE parameter statement.
Action: Delete the extra vertical displacements from the LOCATE statement.
Reason: Multiple horizontal displacements, as indicated with the LEFT and RIGHT keywords, cannot be used in a LOCATE parameter statement.
Action: Delete the extra horizontal displacements from the LOCATE statement.
Reason: One of the four direction keywords must appear before each number in a LOCATE parameter statement.
Action: Add the appropriate direction keyword before the indicated number in the LOCATE statement.
Reason: Extra characters follow the required syntax of a parameter statement. The extra characters are ignored. The kind of statement is indicated by type-of, which may be LOCATE, INCLUDE, RECLINE, or SETLINE. The erroneous statement immediately precedes this message.
Action: Delete the extra characters in the indicated statement.
Reason: The first LOCATE statement entered cannot include the direction keywords UP, DOWN, LEFT, or RIGHT.
Action: Revise the first LOCATE statement so it is in this form: LOCATE record-name
Reason: The first LOCATE statement in a series of LOCATEs cannot include a FROM clause.
Action: Revise the first LOCATE statement so it is in this form: LOCATE record-name
Reason: At least one displacement clause (UP/DOWN/LEFT/RIGHT number) must appear in all but the first LOCATE parameter statement you enter.
Action: Add a displacement clause to the LOCATE statement or delete the incomplete statement.
Reason: A number following UP/DOWN/LEFT/RIGHT in a LOCATE parameter statement you entered is not between 1 and 10,000, inclusive.
Action: Change the displacement value in the LOCATE statement to a valid number.
Reason: The syntax of a parameter statement indicated that the statement continued on another line; however, CA IDMS Schema Mapper encountered an end-of-file before finding the rest of the statement.
Action: Add the line(s) necessary to complete the statement or remove the comma that indicates continuation.
Reason: The schema or subschema specified on the PROCESS parameter statement does not contain any records. A schema/subschema must contain at least one record before CA IDMS Schema Mapper can diagram it.
Action: Verify that you have correctly specified the schema/subschema. Specify a different schema/subschema in the PROCESS statement. If you specified the schema/subschema you wanted, but it does not contain any records, add one or more records to it.
Reason: A diagram page width value less than 33 or greater than 132 is in the OPTIONS parameter statement. The DPAGEWID value must be between 33 and 132, inclusive; no other values are allowed.
Action: Change the DPAGEWID value in the OPTIONS statement to a number between 33 and 132, inclusive.
Reason: The COMPRESS value specified in the OPTIONS parameter statement is invalid.
Action: Check the validity of the COMPRESS value indicated.
Reason: The file or dataset used for the parameter statements input file either was completely empty or did not exist.
Action: Check the spelling of the file name or the dataset name used for SYSIPT. If the spelling of the name is correct, and the file or dataset exists, check the content of it.
Reason: The INCLUDE statement must appear after any SETLINE statements and before any LOCATE statements.
Action: Check the order of parameter statements in the input file (SYSIPT).
Reason: The INCLUDE statement preceding this message does not contain a name. The kind-of name is AREA, RECORD, SET, or INDEX.
Action: Check the syntax of the statement and add a name to it.
Reason: The indicated name is not an area in the schema or subschema being processed. Instead, the name identifies a record, set, or index. You may use only area names in this position of the statement. The erroneous statement appears immediately before this message.
Action: Delete the statement or replace the name with a valid area name.
Reason: A comma is missing before the indicated symbol. The erroneous statement precedes this message. For RECLINE and SETLINE statements, the statement in error may be two lines back.
Action: Check the syntax of the statement for a missing comma.
Reason: A blank field was requested in a RECLINE or SETLINE statement, but no length was given for the field.
Action: Check the syntax of the statement and add the missing number.
Reason: Either a previous RECLINE statement contains two commas in a row, or a RECLINE statement ends with a comma.
Action: Check the syntax of the RECLINE statement and add the missing field name or delete the extra comma.
Reason: Either a previous SETLINE statement contains two commas in a row, or a SETLINE statement ends with a comma.
Action: Check the syntax of the SETLINE statement and add the missing field name or delete the extra comma.
Reason: The keyword BLANK must precede a number in a RECLINE or SETLINE field.
Action: Add the missing keyword or delete the number.
Reason: A space must separate the keyword BLANK from the number that specifies the length of the field.
Action: Add the missing space or delete the field name.
Reason: Only 20 blank fields may be requested in a series of RECLINE or SETLINE statements. Kind-of-text indicates whether the excess fields were requested for a record block or a set description.
Action: Delete the extra blank fields.
Reason: The sum of the field sizes for each line of a record block or set description must be no more than 120. Be sure to allow for a space between adjacent fields. Kind-of-text indicates whether this was for a record block, or a set description.
Action: Check the RECLINE or SETLINE statement preceding this message. Either delete a field or move a field to another statement.
Reason:
Action:
Reason: The indicated field may only be used in SETLINE statements.
Action: Remove the field from the preceding RECLINE statement.
Reason: The indicated field may only be used in SETLINE statements.
Action: Remove the field from the preceding RECLINE statement.
Reason: More than 14 RECLINE statements have been used.
Action: Remove the extra RECLINE statements.
Reason: More than 9 SETLINE statements have been used.
Action: Remove the extra SETLINE statements.
Reason: Indicated field name appeared twice in a group of RECLINE or SETLINE statements.
Action: Remove extra occurrences of the indicated field name.
Reason: The RECLINE or SETLINE statement preceding this message is missing a parenthesis in a subscript. The kind-of parenthesis is LEFT or RIGHT.
Action: Check the syntax of the statement and add the appropriate parenthesis.
Reason: The indicated subscript value is invalid. A subscript can be an integer from 1 to 256 or the letter N.
Action: Check the syntax of the indicated subscript and correct it.
Reason: The RECLINE or SETLINE statement preceding this message contains parentheses but no subscript value.
Action: Check the syntax of the statement and add the subscript value or remove the parentheses.
Reason: Subscripts may only be used with the LOC-CTRL and SET-ORDER fields.
Action: Check the syntax of the RECLINE or SETLINE statement preceding this message and remove the erroneous subscript.
Reason: Subscripts, which begin with a left parenthesis, must follow the LOC-CTRL field in a RECLINE statement or the SET-ORDER field in a SETLINE statement.
Action: Check the syntax of the RECLINE or SETLINE statement and add the missing field name or remove the extra subscript value.
Reason: A right parenthesis may be used only as part of a subscript in a RECLINE or SETLINE statement. CA IDMS Schema Mapper may have encountered a subscript where only a simple number was expected (e.g., with the BLANK field).
Action: Check the syntax of the RECLINE or SETLINE statement and remove the right parenthesis or correct its position.
Reason: A left parenthesis may be used only as part of a subscript in a RECLINE or SETLINE statement. CA IDMS Schema Mapper may have encountered a subscript where only a simple number was expected (e.g., with the BLANK field).
Action: Check the syntax of the RECLINE or SETLINE statement and remove the left parenthesis or correct its position.
Reason: The indicated subscript value is either too large or too small for the indicated field. The valid range of subscript values is 1 through 256.
Action: Correct the invalid subscript value.
Reason:
Action:
Reason: All character definition parameters must be given in the CHARDEF statement. These parameters are not allowed in the OPTIONS statement. The first seven positions of the keyword are shown.
Action: Move the indicated keyword and its associated value to the CHARDEF statement.
Reason: This message is turned on by the schema or subschema compiler when it detects an error during a compile. The dictionary may only contain part of the schema or subschema.
Action: Correct the error(s) and recompile the schema or subschema.
Reason: CA IDMS Schema Mapper did not find an OOAK-012 record in the requested dictionary.
Action: Check the integrity of the dictionary.
This message may appear in certain circumstances as defined below and is followed by a program abend when Schema Mapper is run in a Z/VSE system. Note that there is no message number associated with this message.
Reason: This message is created by the runtime support runtimes when no logic module for a particular device is found in the DTF table. This message usually appears if the device associated with the transfer file is defined at IPL time as a type 2520B2 and has been assigned to SYSPCH.
Action: To avoid this message, ensure that you define the transfer file assigned to SYSPCH as device type 2540P in your IPL procedures. Alternatively, you can add ASSGN SYSPCH,IGN in your Schema Mapper JCL.
|
Copyright © 2013 CA.
All rights reserved.
|
|