Skip to content
CA Datacom Tools - 15.0
Documentation powered by DocOps

Defining Unmodeled Sequential File Dataviews

Last update March 9, 2017

CA Ideal™ for CA Datacom® provides a facility for creating, describing, and maintaining dataview definitions for sequential files without a file model. An unmodeled sequential dataview is recorded as a DATAVIEW entity occurrence in the dictionary. The definition of the fields comprising the dataview is recorded in a VLS member.

The dataview is, like other CA Ideal™ for CA Datacom® dataview types, a logical viefw of the specified fields that can be shared across many applications. The CA Ideal™ for CA Datacom® user sees the data as a named collection of fields in a table. PDL statements for accessing data through dataviews apply. You can find any record or collection of records in the table by using the PDL FOR statement in a PDL procedure definition.

The dataview definition is created and cataloged in CA Ideal™ for CA Datacom®. It can be displayed, edited, duplicated to a new name or a new version, printed, and deleted.

The unmodeled sequential file dataview is unlike other dataview types in several ways:

  • It is created in CA Ideal™ for CA Datacom® and can be edited, duplicated to a new version or a new name, and deleted in CA Ideal™ for CA Datacom®. The test version of the dataview can be edited, even when it is used as the resource of a production program. You cannot edit the production version of the dataview. However, you can duplicate it to a new version, edit it, and recatalog it. You also need to recompile all programs that use the dataview.
  • You can limit access to the dataview to a particular CA Ideal™ for CA Datacom® system only if you are an CA Datacom®/DB site.

This page contains the following topics:

Components of a Sequential File Dataview Definition

A CA Ideal™ for CA Datacom® sequential file dataview definition uses the following components:

  • An identification fill-in that initiates the creation of a sequential file dataview definition and provide descriptive information about it.
  • A field definition fill-in that describes the fields comprising the dataview.
  • parameter definition fill-in that describes the file associated with the dataview.

This section contains detailed explanations of how to complete the fill-ins that construct each component of a sequential file dataview definition presented in the Dataview Menu.

The functions CA Ideal™ for CA Datacom® provides to define and maintain sequential file dataview definitions are presented in the Dataview Menu. To access this menu, select option 2 on the Main Menu or enter the DATAVIEW command. See Dataview Menu in the “Introduction” chapter for instructions on using this menu.

Creating a Dataview Definition

The first step in creating an unmodeled sequential file dataview is identifying the dataview. To identify the dataview, you must first enter the CREATE DATAVIEW command, and then fill in the Dataview Identification screen. Once you name the dataview either in the CREATE DATAVIEW command or on the Identification fill-in, an entry for the dataview definition is stored in the dictionary facility. After the dataview is identified, it becomes the current definition.

The CREATE DATAVIEW command presents a blank dataview identification fill-in. This fill-in establishes the dataview name and provides identification information for the dataview that is kept in the dictionary. CREATE DATAVIEW creates version one in test status. You can modify, duplicate, print, delete, and mark this version to production status, just like any other CA Ideal™ for CA Datacom® entity.

Identifying the Dataview

Use the CREATE DATAVIEW command to display the dataview identification fill-in for a new dataview. To display the Identification fill-in for an existing dataview:

  • If the dataview is not the current definition, enter the EDIT or DISPLAY DATAVIEW command, specifying the IDENTIFICATION component in the command.
  • If the dataview is the current definition, enter the IDE command or press the equivalent PF key.

The dataview identification fill-in shown next enters descriptive information about the sequential file dataview, either when the dataview definition is initially created or when it is subsequently modified.


DATAVIEW Name  __________________
Access-Method  ____ (SEQ|VSAM|PARM)
Operating System MVS (MVS|VSE)

Short Description ________________________

The components of the dataview identification fill-in are as follows:

  • Dataview Name
    Specifies the one- to 18-character name that is assigned to the sequential file dataview definition. CA Ideal™ for CA Datacom® initializes the name to the name entered in the CREATE command or prompter, if a name was supplied.
  • Access Method
    Type of file being defined: VSAM for a VSAM file, SEQ for a sequential file. Once the access method is entered and accepted, you cannot modify this value.
    You can also enter PARM, indicating that this dataview does not represent a physical file. However, PARM is used with COPY DVW to define parameters that are passed between programs as a data flow rather than a data store.
  • Operating System
    Specifies the type of operating system under which the dataview is accessed. The default value for this field is the current system.
  • Created By
    Specifies the initial creation date of the dataview definition and the user ID of the creator. This information appears only after the name is entered and accepted.
  • Last Modified ...
    Identifies the Date, time, and user ID of the last edit access. This field is blank until an EDIT DATAVIEW command accesses this definition. This information appears only after the dataview name is entered and accepted.
  • Last Cataloged ...
    Identifies the Date, time, and user ID of the last catalog.
  • Short Description (Optional)
    Specifies the brief description of the dataview definition the user entered.
  • Description (Optional)
    Specifies the full description of the dataview definition, up to five lines long.

The dataview identification fill-in is shown as follows:



Access-Method  SEQ (SEQ|VSAM|PARM)
Operating System MVS (MVS|VSE)

Created     10/26/93        By KRITZ
Last Modified  10/25/94 at 08:38   By DESANDRES
Last Cataloged  10/26/94 at 10:45

Short Description Employee Log File_______
Log file to track transactions against the Employee Master File


Defining Fields

The FIELD command or equivalent PF key displays the dataview field definition fill-in for the current sequential file dataview definition. The dataview field definition fill-in, shown in the following screen, names and describes the fields in the dataview.


Command Level Field Name   T I Ch/Dg Occur Value/Comments/Clauses
------ ----- --------------- - - ----- -----
====== ===== ======= TOP === = = ===== ===== =================================
====== ===== ===== BOTTOM == = = ===== ===== =================================

The entries on the dataview field definition fill-in are as follows:

  • Command 
    Specifies the area where you can specify line commands. 
  • Level 
    Specifies the number that hierarchically ranks fields. Levels start with level 2. (The dataview is treated as a level-1 item.) Level-2 elementary fields (fields with no subordinate fields) do not require a level number. If no level number is supplied, the level number defaults to 2.
  • Field Name
    Field Name column must contain one of the following:
    • A valid name that identifies an elementary or group field.
      An elementary field is a field that has no subordinate fields. The field name of an elementary field must be unique in the dataview. Elementary fields are further defined by values entered in the T and Ch/Dg field. A group field has subordinate fields. Group field name entries have no T and Ch/Dg values.
      You can continue the field name on a second line by including a semicolon (;) as the last character on the first line. You can break the field name at any character. You can specify the level number and the attributes T, I, Ch/Dg, and Occur on the first line only.
    • A condition name for a condition name definition.
    • A valid subscript of the form (n), (n,o), or (n,o,p) for an initial value of a specific occurring item.
    • A filler, an unnamed field that reserves space. If the field is unnamed, the field name column contains blanks.
    • Blanks, when the Value/Comment/Clauses column contains a continuation line, a comment, or when the rest of the line is blank.
  • T (Type) 
    The field types are as follows:
    • Alphanumeric field. The value of the field can contain alphabetic, numeric, and special characters.
    • Signed numeric field. The value of the field can contain 0-9, a minus sign, and a decimal symbol.
    • Unsigned numeric field. The value of the field can contain 0-9 and a decimal symbol.
    • Date field. This type is a numeric field containing an integer number, reflecting the number of days, plus or minus, from December 31, 1900 (day zero). This is not the same as the Date data type in SQL dataviews.
    • Condition name assigned to a specific value of a field.
    Note: Type defaults to N if you specify the internal representation. Type must be blank for a group item.
    Variable length fields are not supported for sequential files.
    Non-date entry with no type or length information is assumed to be a group name and must have subordinate fields following it.
  • I (Internal Representation)
    Internal representation of numeric (signed and unsigned) and date type fields:
    • P Packed
    • Z Zoned
    • B Binary
    Note: Internal representation must be blank unless the type is N, U, or D. P is the default.
  • CH/DG (Characters/ Digits)
    The length of the field value:
    • CH Number of alphanumeric characters in the field value.
    • DG Sum of the number of integer and decimal places in a numeric or date field value, separated by a decimal point. (Date fields cannot have decimal places.)
      You must specify the characters and digits for all elementary field types except dates and flags. The default for date fields is 7. The minimum length for date fields is 5. For numeric and date fields, the maximum is 31 for packed and zoned and 9 for binary. 
      A non-date entry with no type or length information is assumed to be a group name and must have subordinate fields following it.
      In the following illustration, 42 in the Characters/Digits column for the first alphanumeric field (Type X) indicate a length of 42 characters. A numeric field (Type N) with 7 specified in the Characters/Digits column indicates a seven-digit field with seven integer positions. The next numeric field, with 10.3 specified in the Characters/Digits column, indicates a 13-digit field with ten integer positions and three decimal places. A date field (Type D) with five characters/digits can hold an internal 5-integer date value of up to 273 years from the base year.

      Type CH/DG
      X 42
      N 7
      N 10.3
      D 5
  • Occur (Number of Occurrences)
    Specifies the number of times a group or field occurs. You can specify initial values for the individual occurrences of an occurring field by entering the values on each successive line following the occurring field definition. A valid subscript number (of the form (n), (n,o), or (n,o,p)) is entered on the corresponding line in the Field Name column.
    You cannot specify initial values for repeating groups.
  • Value/Comments/Clauses (Value, Comments, or Redef) 
    Depending on the circumstances, this column specifies a value for the occurrence of the field or a REDEFINITION keyword. You can specify a descriptive comment about the field alone or with any of the others.
    Note: The case of the data entered in this column as CA Ideal™ for CA Datacom® retains it depends on the setting that was determined for case either by default or with a SET EDIT CASE command.
    • Value
      Specific value assigned to an occurrence of a field.
      You can assign a value to an elementary field in the Value/Comments/Clauses column. This value can be a numeric or alphanumeric literal, depending on the type of the elementary field. 
      You must enclose alphanumeric literals in delimiters (“or “). If an alphanumeric literal is longer than the space provided, continue the alphanumeric literal on the next line of the same column surrounded by a new pair of delimiters. Leave all other columns on the continuation line blank. Two or more delimited alphanumeric literals continued in this fashion are concatenated and treated as one. Be sure to include any required spaces in the delimiters, since spaces are not added when the values are concatenated.
      The default value for a numeric field is zero. The default for an alphanumeric field is spaces.
      In the case of an occurring field, the Value column is left blank on the line that contains the field name for the parent field. The following lines in the Value column can contain entries for the value of each occurrence of the field.
      You cannot assign an initial value to a date field. (The default initial value is 0.) This also means that you cannot define a date field with subordinate condition names or flags. However, a date field can redefine a numeric field with an initial value.
    • Comments
      Useful information about the field. A comment is indicated in this column by a preceding colon (:). To continue a comment over multiple lines, start each line of the column with a colon. The other columns can be blank or the continuation of a field name.
    • Redefinition
      Keyword REDEFINITION (or REDEF) in this column indicates that this item is another view of the closest previously defined item at the same level that is not itself a redefinition.
      This item cannot be larger than the item it redefines. The two items can be different types (such as alphanumeric and numeric).
      If a field with a REDEF is a subordinate field, its Type does not affect whether the group is alpha or non-alpha. CA Ideal™ for CA Datacom® uses the Type of the redefined (original) item.
      A field with a REDEF cannot have an initial value. If a group has a REDEF, none of its subordinate fields can have initial values. (However, the original field can have an initial value.) 
      The following example illustrates the various types of data structures that you can define using the dataview field fill-in.


Command Level Field Name     T I Ch/Dg Occur Value/Comments/Clauses
------ ----- --------------- - - ----- ----- ---------------------------------
====== ===== ======= TOP === = = ===== ===== =================================
000006   2   REC-TYPE        X       2
000007   2   DATA            X      98
000008   2   CUST-ADDR                         REDEF
000009   3   CA-CUST-ID      X       5
000010   3   CA-NAME         X      30
000011   3   CA-ADDRESS      X      30
000012   3   CA-STATE        X       2
000013   3   CA-ZIP          N Z     9
000014   3   CA-CITY         X      15
000015   2    ORD-INFO                          REDEF
000016   3   OI-ORD-ID       X       5
000017   3   OI-CUST-ID      X       5
000018   3   OI-ORD-DT       X      10
000019   3   OI-DISC-PCT     N P   2.1
000020   3   OI-STAT         X       1
000021   3   OI-SHIP-DT      X      10
000022   3   OI-TERMS        X      15
000023   3   OI-CUST-PO      X      10
000024   3   OI-SHIP-ID      X       5
000025   3   OI-ORDER-TOTAL  N P   7.2
000026   3   OI-FRT-AMT      N P   7.2
====== ===== ===== BOTTOM == = = ===== ===== =================================

Defining the File Parameters

The dataview parameter definition describes the sequential file corresponding to the dataview as follows. Use the PARAMETER command or equivalent PF key to display this fill-in for the current sequential file dataview definition.



Update Intent    Y     (Y=Yes, N=No)
Filename      SEQDVW1

The components of the dataview parameter fill-in are as follows:

  • Update Intent
    Dataview can update the table.
    Dataview cannot update the table.
  • Filename File name from the CA Ideal™ for CA Datacom® startup JCL: 
    z/OS One- to eight-character ddname from the DD statement.
    VSE One- to seven-character DLBL or TLBL name from the DLBL or TLBL statement.

For VSE Only

The following components display when the operating system is VSE:

  • Record Length Required. It must be from 1 to 32,000.
  • Block Size Required. It must be a multiple of the record length and cannot exceed 32,000.
  • Record Format One of the following:
    • FBLK Fixed block
    • FUNB Unblocked
  • Device Type One of the following:
    • PRT
    • PUNCH
  • Tape Labels One of the following:
    • Y Tape labels
    • No tape labels
Was this helpful?

Please log in to post comments.