intro to idms

09/06/16 M Sliming 1

Intro to IDMSIntro to IDMSMargaret SlimingMargaret Sliming

OfOf

DivaProgrammer, LLCDivaProgrammer, LLCwww.web2IDMS.comwww.web2IDMS.com

09/06/16 2M Sliming

Introduction Introduction

This presentation will cover the basic This presentation will cover the basic concepts of IDMS database structure, data concepts of IDMS database structure, data relationships and access methods.relationships and access methods.

09/06/16 3M Sliming

AgendaAgenda Data RelationshipsData Relationships Database ArchitectureDatabase Architecture Database DefinitionDatabase Definition CurrencyCurrency COBOL CommandsCOBOL Commands Error HandlingError Handling Central VersionCentral Version CulpritCulprit SQLSQL Additional Information / SourcesAdditional Information / Sources

09/06/16 4M Sliming

Data RelationshipsData Relationships

TABLE RELATIONSHIPS

PAYROLL

ID TCHR SSN SALARY

TEACHER

ID NAME SSN

DEPT ID

DEPARTMENT

ID NAME

STUD-CRSE

STUD ID CRSE ID

COURSE

ID NAME

TCHR ID

STUDENT

ID NAME ADDR

One-to-One

One-to-Many

Many-to-Many

09/06/16 5M Sliming

Data Relationships (Con’t)Data Relationships (Con’t)

Data relates in three ways:Data relates in three ways: One-to-One (eg. Payroll & Teacher) One-to-One (eg. Payroll & Teacher) One-to-Many (eg. Teacher & Course)One-to-Many (eg. Teacher & Course) Many-to-Many (eg. Course & Student)Many-to-Many (eg. Course & Student)

Relational databases use foreign keys to relate Relational databases use foreign keys to relate records and IDMS uses sets.records and IDMS uses sets.

09/06/16 6M Sliming

Database ArchitectureDatabase Architecture

09/06/16 7M Sliming

Database ArchitectureDatabase Architecture

The preceding page illustrates how records are The preceding page illustrates how records are stored in IDMS.stored in IDMS.

The database is comprised of areas which are The database is comprised of areas which are mapped to disk files. Areas are broken up into mapped to disk files. Areas are broken up into pages which contain the database records. The pages which contain the database records. The records are uniquely identified by the page records are uniquely identified by the page number, they reside on, and a sequence number, number, they reside on, and a sequence number, called a line number. This makes up what is called a line number. This makes up what is known as the database key or DB-KEY. known as the database key or DB-KEY.

09/06/16 8M Sliming

Database ArchitectureDatabase ArchitectureDatabase Page

09/06/16 9M Sliming

Database ArchitectureDatabase ArchitectureDATABASE KEYS

09/06/16 10M Sliming

Database DefinitionDatabase Definition

PAYROLL-100 100 F CALC 100-PYRL-ID DN

ADMIN-AREA STUDENT-500

500 F CALC 500-STUD-ID DN

ADMIN-AREA COURSE-400 400 F CALC 400-CRSE-ID DN ACADEMIC-AREA

TEACHER-200 200 F CALC 200-TCHR-ID DN FACULTY-AREA STUD-CRSE-600

600 F VIA CRSE-STUDCRSE DN ACADEMIC-AREA

DEPT-300 300 F CALC 300-DEPT-ID DN FACULTY-AREA

TEACHER -COURSE

STUDENT-STUDCRSE

COURSE-STUDCRSE

TEACHER-PAYROLL

DEPT-TEACHER



01 PAYROLL-100.01 PAYROLL-100. 01 COURSE-400. 01 COURSE-400.

05 100-PYRL-ID PIC X(9). 05 100-PYRL-ID PIC X(9). 05 400-CRSE-ID PIC X(3).05 400-CRSE-ID PIC X(3).

05 100-PYRL-SSN PIC 9(9). 05 100-PYRL-SSN PIC 9(9). 05 400-CRSE-TITLE PIC X(20). 05 400-CRSE-TITLE PIC X(20).

05 100-PYRL-SALARY PIC 9(6)V9(2). 05 100-PYRL-SALARY PIC 9(6)V9(2). 05 400-CRSE-TCHR PIC X(5).05 400-CRSE-TCHR PIC X(5).

01 TEACHER-200.01 TEACHER-200. 01 STUDENT-500.01 STUDENT-500.

05 200-TCHR-ID PIC X(4).05 200-TCHR-ID PIC X(4). 05 500-STUD-ID PIC X(4).05 500-STUD-ID PIC X(4).

05 200-TCHR-SSN PIC 9(9).05 200-TCHR-SSN PIC 9(9). 05 500-STUD-NAME PIC X(30).05 500-STUD-NAME PIC X(30).

05 200-TCHR-NAME PIC X(30). 05 200-TCHR-NAME PIC X(30). 05 500-STUD-ADDR PIC X(40).05 500-STUD-ADDR PIC X(40).

05 200-TCHR-DEPT PIC X(4). 05 200-TCHR-DEPT PIC X(4).

01 DEPT-300.01 DEPT-300. 01 STUD-CRSE-600.01 STUD-CRSE-600.

05 300-DEPT-ID PIC X(4).05 300-DEPT-ID PIC X(4). 05 600-STUD-ID PIC X(4).05 600-STUD-ID PIC X(4).

05 300-DEPT-NAME PIC X(15). 05 300-DEPT-NAME PIC X(15). 05 600-CRSE-ID PIC X(3).05 600-CRSE-ID PIC X(3).

Record Descriptions


Database Definition Database Definition

A Schema contains the record, set and area A Schema contains the record, set and area definitions for an IDMS database.definitions for an IDMS database.

A Subschema contains the records, sets and A Subschema contains the records, sets and areas that can be referenced by an application areas that can be referenced by an application and whether they can be updated or retrieved and whether they can be updated or retrieved only.only.

A DMCL maps the database areas to file A DMCL maps the database areas to file blocks.blocks.


Database Definition Database Definition

To program IDMS applications, our most To program IDMS applications, our most valuable tool is the schema definition and/or valuable tool is the schema definition and/or diagram, seen on slide 10, known as the diagram, seen on slide 10, known as the “Bachman” diagram. “Bachman” diagram.

In order to retrieve and/or update information In order to retrieve and/or update information in the database, we have to know how to get to in the database, we have to know how to get to it.it.

The following pages will detail how we define The following pages will detail how we define data relationships in IDMS.data relationships in IDMS.



Record Attributes Record Attributes Location ModesLocation Modes Set AttributesSet Attributes Indexed SetsIndexed Sets Area SweepsArea Sweeps


Database Definition - Record AttributesDatabase Definition - Record Attributes


Database Definition - Record Attributes Database Definition - Record Attributes

Record ID:Record ID: Unique numeric value within the Unique numeric value within the schema assigned to the record. It’s helpful to schema assigned to the record. It’s helpful to include this number in the record name and to also include this number in the record name and to also prefix each record element with it. prefix each record element with it.

Storage Mode:Storage Mode: This means storing the record as This means storing the record as fixed or variable. Fixed is the most desirable so the fixed or variable. Fixed is the most desirable so the record does not change size when it gets updated. record does not change size when it gets updated. Variable records can get fragmented and thus take Variable records can get fragmented and thus take more I/O to retrieve.more I/O to retrieve.


Database Definition - Record Attributes Database Definition - Record Attributes

Record Length:Record Length: This value includes the total length of This value includes the total length of all data elements plus four bytes for each pointer all data elements plus four bytes for each pointer database key associated with the record. Pointers will database key associated with the record. Pointers will be discussed later with set options.be discussed later with set options.

Location ModeLocation Mode, , Set NameSet Name and and Duplicates Duplicates IndicatorIndicator will we discussed in more detail later in this will we discussed in more detail later in this section.section.

Area Name:Area Name: Name of the database area the record is Name of the database area the record is stored in.stored in.


Database Definitiion - Location ModesDatabase Definitiion - Location Modes

The manner in which a record occurrence is physically The manner in which a record occurrence is physically located in an area of the database. The three types are: located in an area of the database. The three types are: CALC, VIA and DIRECT.CALC, VIA and DIRECT.

CALC: A method of determining the target page for CALC: A method of determining the target page for storage of a record in the database. The target page is storage of a record in the database. The target page is calculated is calculated by means of a randomizing calculated is calculated by means of a randomizing routine executed against the value of the Calc key in the routine executed against the value of the Calc key in the record.record.


Database Definition - Location ModesDatabase Definition - Location Modes

VIA: Clusters member records in the same physical VIA: Clusters member records in the same physical location for efficient database access. Optionally, Via location for efficient database access. Optionally, Via can cluster member records with their owners.can cluster member records with their owners.

DIRECT: Populates an area in the order the records DIRECT: Populates an area in the order the records are loaded. This mode is best used for data which is are loaded. This mode is best used for data which is static and will be retrieved in the order it physically static and will be retrieved in the order it physically resides in the database.resides in the database.


Database Definition - Location Modes Database Definition - Location Modes

Example – CALC mode


Database Definition - Location Modes Database Definition - Location Modes Example – VIA mode


Database Definition – Location Modes Database Definition – Location Modes This example illustrates how records are stored VIA when the owner and member reside in different areas.


Database Definition - Location Modes Database Definition - Location Modes

Example – DIRECT mode


Database Definition - Set AttributesDatabase Definition - Set Attributes Sets relate records to each other in IDMS using a Sets relate records to each other in IDMS using a

number of parameters.number of parameters. PointersPointers: Next, Prior, Owner, Index, Index Owner: Next, Prior, Owner, Index, Index Owner MembershipMembership: Mandatory Automatic, Mandatory : Mandatory Automatic, Mandatory

Manual, Optional Automatic, Optional ManualManual, Optional Automatic, Optional Manual OrderOrder (Unsorted sets): First, Last, Next, Prior (Unsorted sets): First, Last, Next, Prior

(Sorted sets): Ascending or (Sorted sets): Ascending or descending by key descending by key

A database record contains a pointer (aka Db-key) A database record contains a pointer (aka Db-key) for each record it relates to. ie. If it is stored Next, for each record it relates to. ie. If it is stored Next, Prior and Owner in a set, it will contain the pointer Prior and Owner in a set, it will contain the pointer for the owner, previous and next record in the set. for the owner, previous and next record in the set.


Database Definition – Indexed SetsDatabase Definition – Indexed Sets

SYSTEM-OWNED INDEX


Database Definition – Indexed SetsDatabase Definition – Indexed Sets

USER-OWNED INDEX


Database Definition – Area SweepsDatabase Definition – Area Sweeps

This method of retrieval is used when records cannot This method of retrieval is used when records cannot be retrieved using key information. The entire area is be retrieved using key information. The entire area is read from beginning to end and the program selects the read from beginning to end and the program selects the desired records.desired records.

This can be a good method when all occurrences of a This can be a good method when all occurrences of a record type are needed and there are not too many record type are needed and there are not too many different record types in the area.different record types in the area.

The programmer must pay close attention to currency The programmer must pay close attention to currency when retrieving owner records with an area sweep and when retrieving owner records with an area sweep and then getting their member records when both records then getting their member records when both records reside in the same area. Looping can occur if the reside in the same area. Looping can occur if the owner record is not made current of area before each owner record is not made current of area before each obtain.obtain.


CurrencyCurrency

IDMS keeps track of record occurrences, IDMS keeps track of record occurrences, being processed, by area, set, record type and being processed, by area, set, record type and run-unit (program).run-unit (program).

The current record is usually the last The current record is usually the last record retrieved or updated. record retrieved or updated.

Currency is extremely important to Currency is extremely important to understand, especially when updating a understand, especially when updating a database, for maintaining data integrity. database, for maintaining data integrity.


COBOL CommandsCOBOL Commands ACCEPTACCEPT BINDBIND COMMITCOMMIT CONNECTCONNECT DISCONNECTDISCONNECT ERASEERASE FIND/OBTAINFIND/OBTAIN FINISHFINISH IFIF MODIFYMODIFY READYREADY ROLLBACKROLLBACK


COBOL Commands - COBOL Commands - ACCEPTACCEPT

Retrieves information pertaining to the status of the Retrieves information pertaining to the status of the database.database.

Format:Format:ACCEPT {TASK CODE } INTO ACCEPT {TASK CODE } INTO return-locationreturn-location..

{TASK ID }{TASK ID }

{LTERM ID }{LTERM ID }

{PTERM ID }{PTERM ID }

{SYSVERSION}{SYSVERSION}

{USER ID }{USER ID }

{SCREENSIZE}{SCREENSIZE}


COBOL commands - COBOL commands - BINDBIND

Initiates a run-unit and establishes addressability Initiates a run-unit and establishes addressability in variable storage to the IDMS communication in variable storage to the IDMS communication block, record types and optionally to procedure block, record types and optionally to procedure control information.control information.

Format:Format:BIND {RUN-UNIT } .BIND {RUN-UNIT } .

{record-name }{record-name }


COBOL Commands - COBOL Commands - COMMITCOMMIT

Makes database updates permanent. Ie. If a Makes database updates permanent. Ie. If a program abends without having issued any program abends without having issued any ‘COMMIT’s, all updates issued by the program ‘COMMIT’s, all updates issued by the program will be rolled back.will be rolled back.

Format:Format: COMMIT { } .COMMIT { } .

{ALL} {ALL}


COBOL Commands - COBOL Commands - CONNECTCONNECT

Establishes a record occurrence as a member of Establishes a record occurrence as a member of a set occurrence. The set must not be defined as a set occurrence. The set must not be defined as Mandatory Automatic.Mandatory Automatic.

Format:Format: CONNECT CONNECT record-namerecord-name TO TO set-nameset-name . .


COBOL Commands - COBOL Commands - DISCONNECTDISCONNECT

Removes a member record occurrence from a Removes a member record occurrence from a set but does not delete the record from the set but does not delete the record from the database. This command is only valid for database. This command is only valid for records which are optional members of a set.records which are optional members of a set.

Format:Format:DISCONNECT DISCONNECT record-namerecord-name FROM FROM set-nameset-name . .


COBOL Commands - COBOL Commands - ERASEERASE

Deletes a record occurrence from the database Deletes a record occurrence from the database and optionally deletes records subordinate to it.and optionally deletes records subordinate to it.

Format:Format: ERASE record-name { } .ERASE record-name { } .

{ALL MEMBERS}{ALL MEMBERS}


COBOL Commands - COBOL Commands - FIND / OBTAINFIND / OBTAIN

The FIND statement locates a record The FIND statement locates a record occurrence in the database; the OBTAIN occurrence in the database; the OBTAIN statement locates a record and moves the data statement locates a record and moves the data associated with the record to the record buffers. associated with the record to the record buffers. Because the FIND and OBTAIN command Because the FIND and OBTAIN command statements have identical formats, they are statements have identical formats, they are discussed together. The six formats of the discussed together. The six formats of the FIND/OBTAIN statement are as follows: FIND/OBTAIN statement are as follows:



FIND/OBTAIN CALC FIND/OBTAIN CALC accesses a record occurrence by using accesses a record occurrence by using its CALC key value. its CALC key value.

FIND/OBTAIN CURRENT FIND/OBTAIN CURRENT accesses a record occurrence by accesses a record occurrence by using established currencies. using established currencies.

FIND/OBTAIN DB-KEY FIND/OBTAIN DB-KEY accesses a record occurrence by accesses a record occurrence by using its database key. using its database key.

FIND/OBTAIN OWNER FIND/OBTAIN OWNER accesses the owner record of a set accesses the owner record of a set occurrence. occurrence.

FIND/OBTAIN WITHIN SET USING SORT KEY FIND/OBTAIN WITHIN SET USING SORT KEY accesses a record occurrence in a sorted set by using its sort key accesses a record occurrence in a sorted set by using its sort key value. value.

FIND/OBTAIN WITHIN SET/AREA FIND/OBTAIN WITHIN SET/AREA accesses a record accesses a record occurrence based on its logical location within a set or on its occurrence based on its logical location within a set or on its physical location within an area. physical location within an area.



Formats:Formats: FIND / OBTAIN CALC FIND / OBTAIN CALC record-namerecord-name . . FIND / OBTAIN CURRENT { FIND / OBTAIN CURRENT { record-namerecord-name } . } .

{WITHIN {WITHIN set-nameset-name } }

{WITHIN {WITHIN area-namearea-name } }

FIND / OBTAIN DB-KEY IS FIND / OBTAIN DB-KEY IS db-keydb-key . . FIND / OBTAIN OWNER WITHIN FIND / OBTAIN OWNER WITHIN set-nameset-name . . FIND / OBTAIN FIND / OBTAIN record-namerecord-name WITHIN WITHIN set-nameset-name USING USING sort-keysort-key.. FIND / OBTAIN {NEXT} { } WITHIN { set-name } . FIND / OBTAIN {NEXT} { } WITHIN { set-name } .

{PRIOR} {{PRIOR} {record-name } { area-name }

{FIRST}

{LAST}

{seq-nbr}


COBOL Commands - COBOL Commands - FINISHFINISH

Causes affected database sessions to terminate.Causes affected database sessions to terminate. Format:Format:

FINISH .FINISH .


COBOL Commands - COBOL Commands - IFIF

The IF statement allows the program to test for the The IF statement allows the program to test for the presence of member record occurrences in a set and to presence of member record occurrences in a set and to determine the membership status of a record determine the membership status of a record occurrence in a specified set; once the set has been occurrence in a specified set; once the set has been evaluated, the IF statement specifies further action evaluated, the IF statement specifies further action based on the outcome of the evaluation. For example, based on the outcome of the evaluation. For example, an IF statement might be used to determine whether a an IF statement might be used to determine whether a set occurrence is empty and, if it is empty, to erase the set occurrence is empty and, if it is empty, to erase the owner record. owner record.

Note: DML IF statements cannot be nested within COBOL IF statements.



Depending on its format, the IF statement uses set or run-unit currency. The object set occurrence of an IF statement is determined by the owner of the current record of the named set; the object record occurrence is determined by the current of run unit.

Each IF statement contains a conditional phrase and an imperative statement. When an IF is issued, the precompiler first generates a call to the DBMS to execute the conditional phrase; the results of the test determine whether or not the imperative statement is executed.



Formats:Formats: IF IF set-nameset-name EMPTY EMPTY imperative-statementimperative-statement . . IF IF set-nameset-name NOT EMPTY NOT EMPTY imperative-statement . . IF IF set-nameset-name MEMBER MEMBER imperative-statementimperative-statement . . IF NOT IF NOT set-nameset-name MEMBER MEMBER imperative-statementimperative-statement . .


COBOL Commands - COBOL Commands - ModifyModify

Replaces the contents of a database record occurrence Replaces the contents of a database record occurrence with the values in it’s corresponding variable storage.with the values in it’s corresponding variable storage.

Note: The database record being modified, must Note: The database record being modified, must always be current of run-unit.always be current of run-unit.

Format:Format:

MODIFY MODIFY record-namerecord-name . .


COBOL Commands - COBOL Commands - READYREADY

Prepares a database area for access by DML functions and specifies that area's usage mode.

Format: READY { } USAGE-MODE {UPDATE } .READY { } USAGE-MODE {UPDATE } .

{ { area-namearea-name } {RETRIEVAL} } {RETRIEVAL}


COBOL Commands - COBOL Commands - ROLLBACKROLLBACK

Rolls back uncommitted changes made to the database Rolls back uncommitted changes made to the database through an individual run unit.through an individual run unit.

Format:Format:

ROLLBACK { CONTINUE } . ROLLBACK { CONTINUE } . The CONTINUE option allows the run-unit to remain The CONTINUE option allows the run-unit to remain

active after the changes have been backed out. active after the changes have been backed out. Database access can be resumed without issuing BIND Database access can be resumed without issuing BIND and READY statements.and READY statements.


ERROR HANDLINGERROR HANDLING After each IDMS command executes, a value is After each IDMS command executes, a value is

returned into a field called ERROR-STATUS which is returned into a field called ERROR-STATUS which is ‘0000’ if the command was successful, or a 4-byte value ‘0000’ if the command was successful, or a 4-byte value indicating the command in error and the reason for the indicating the command in error and the reason for the error. The first two bytes of ERROR-STATUS error. The first two bytes of ERROR-STATUS indicate the command and the last two bytes indicate indicate the command and the last two bytes indicate the cause of the error.the cause of the error.

Every IDMS error should be trapped and the Every IDMS error should be trapped and the appropriate action should be taken. This action may be appropriate action should be taken. This action may be an error message or an Abort of the program an error message or an Abort of the program depending on the severity of the error.depending on the severity of the error.

A list of these error status codes can be found in A list of these error status codes can be found in Volume 4, Chapter 11 of the ‘IDMS Messages and Volume 4, Chapter 11 of the ‘IDMS Messages and Codes’ manuals.Codes’ manuals.


ERROR HANDLINGERROR HANDLINGComponent Major code DML functionComponent Major code DML function

00 Any DML function00 Any DML function 01 FINISH01 FINISH 02 ERASE02 ERASE 03 FIND/OBTAIN03 FIND/OBTAIN 05 GET05 GET 06 KEEP06 KEEP 07 CONNECT07 CONNECT 08 MODIFY08 MODIFY 09 READY09 READY 11 DISCONNECT11 DISCONNECT 12 STORE12 STORE 14 BIND14 BIND 15 ACCEPT15 ACCEPT 16 IF16 IF 17 RETURN17 RETURN 18 COMMIT18 COMMIT 19 ROLLBACK19 ROLLBACK 20 LRF requests20 LRF requests


Central Version / Local ModeCentral Version / Local Mode CENTRAL VERSIONCENTRAL VERSION is an IDMS system that enables is an IDMS system that enables

multiple applications to access the database concurrently. A multiple applications to access the database concurrently. A central version controls access to data at the individual record central version controls access to data at the individual record (or row) level thus providing integrity while maximizing (or row) level thus providing integrity while maximizing concurrency. It also provides automatic recovery in the event of concurrency. It also provides automatic recovery in the event of failure. All applications executing within a TP monitor failure. All applications executing within a TP monitor (including DC/UCF) use central version services to access (including DC/UCF) use central version services to access IDMS data. Batch applications can access data in central IDMS data. Batch applications can access data in central version or local mode.version or local mode.

LOCAL MODELOCAL MODE is a mode of operation in which a batch is a mode of operation in which a batch program uses a dedicated copy DBMS to access the database. program uses a dedicated copy DBMS to access the database. In local mode, only one program can update the database at a In local mode, only one program can update the database at a time. Updates in local mode are usually rare and only done time. Updates in local mode are usually rare and only done when it is faster to back of the database, run the update program when it is faster to back of the database, run the update program and restore in the event of an abend than running under Central and restore in the event of an abend than running under Central Version.Version.


Central Version / Local ModeCentral Version / Local Mode


CulpritCulprit

Advantage CA-Culprit is a batch utility that generates reports from conventional and database files. Data Input: As shown in the diagram on the following page, Advantage CA-Culprit can extract data from several database and conventional file structures. As many as 32 conventional files can be read and processed in one Advantage CA-Culprit run. Each run can generate up to 100 reports from the same input data. Reports can be formatted as printed output, stored tables, or written to cards, tape, or disk.

The diagram shows The Advantage CA-Culprit Data Access and Transfer Network. Advantage CA-Culprit can extract data from and write reports to several database and file structures. Advantage CA-Culprit is fully integrated with other products, such as Advantage CA-IDMS/DB, the Integrated Data Dictionary (IDD), and CA-ICMS.


CulpritCulprit


CulpritCulpritSample program to list Service Office Address History for a Provider:Sample program to list Service Office Address History for a Provider:

DATABASE DICTNAME=DICT05 DATABASE DICTNAME=DICT05 IN DB SS=DPU001 IN DB SS=DPU001 PATHAA DPR-PROVSVOFC DPR-ADDRHIST PATHAA DPR-PROVSVOFC DPR-ADDRHIST 01OUT 132 1330 D PS(3375) DD=SYS036,36 LT=S 01OUT 132 1330 D PS(3375) DD=SYS036,36 LT=S 0151*010 339-BILL-PROV-ID-NBR SZ=6 0151*010 339-BILL-PROV-ID-NBR SZ=6 0151*020 339-SERVICE-OFC-NBR SZ=2 0151*020 339-SERVICE-OFC-NBR SZ=2 0151*030 364-SERVICE-OFC-ADDR-GRP SZ=79 0151*030 364-SERVICE-OFC-ADDR-GRP SZ=79 0151*040 364-SVCOFC-STATUS-CODE SZ=1 0151*040 364-SVCOFC-STATUS-CODE SZ=1 0151*050 364-SVCOFC-ADDR-EFFDATE-FULL SZ=8 0151*050 364-SVCOFC-ADDR-EFFDATE-FULL SZ=8 0151*060 364-SVCOFC-ADDR-ENDDATE-FULL SZ=8 0151*060 364-SVCOFC-ADDR-ENDDATE-FULL SZ=8 0151*070 364-SVCOFC-PROVL-DATE-TIME SZ=14 0151*070 364-SVCOFC-PROVL-DATE-TIME SZ=14 017 IF 339-BILL-PROV-ID-NBR = 'B20000' 010 017 IF 339-BILL-PROV-ID-NBR = 'B20000' 010 017 DROP 017 DROP 017010 TAKE 017010 TAKE


CulpritCulprit Output from Sample program: Output from Sample program:

B20000 52 7117 DAWN VIEW CT SUITE 5225 CITRUS HEIGHTS CA956100000C20 C 20040910 20040910 20040910140146 B20000 52 7117 DAWN VIEW CT SUITE 5225 CITRUS HEIGHTS CA956100000C20 C 20040910 20040910 20040910140146 B20000 52 11432123N VIEW CT SUITE CITRUS HEIGHTS CA956100000C20 C 20040901 20040910 20040910135446 B20000 52 11432123N VIEW CT SUITE CITRUS HEIGHTS CA956100000C20 C 20040901 20040910 20040910135446 B20000 52 11432123N VIEW CT CITRUS HEIGHTS CA956100000C20 C 20040901 20040910 20040910135041 B20000 52 11432123N VIEW CT CITRUS HEIGHTS CA956100000C20 C 20040901 20040910 20040910135041 B20000 52 7117 DAWN VIEW CT CITRUS HEIGHTS CA956100000A20 A 20040828 20040910 20040910124434 B20000 52 7117 DAWN VIEW CT CITRUS HEIGHTS CA956100000A20 A 20040828 20040910 20040910124434 B20000 56 NEW ADDRESS DIAMOND SPRINGS CA956190000A20 A 20050801 20050830 20050826105313 B20000 56 NEW ADDRESS DIAMOND SPRINGS CA956190000A20 A 20050801 20050830 20050826105313 B20000 47 7505 SYLVAN VALLEY WAY CITRUS HEIGHTS CA956100000C20 C 20041001 20041005 20041005100933 B20000 47 7505 SYLVAN VALLEY WAY CITRUS HEIGHTS CA956100000C20 C 20041001 20041005 20041005100933 B20000 30 7117 NEW ADDRESS CITRUS HEIGHTS CA956213501C20 C 20050829 20050829 20050829143219 B20000 30 7117 NEW ADDRESS CITRUS HEIGHTS CA956213501C20 C 20050829 20050829 20050829143219 B20000 54 75 CH CA956100000A20 A 20040901 20040907 20040907150639 B20000 54 75 CH CA956100000A20 A 20040901 20040907 20040907150639 B20000 55 TEST ADDRESSS TT CITY CA956100000C20 C 20030901 20040830 20041026154158 B20000 55 TEST ADDRESSS TT CITY CA956100000C20 C 20030901 20040830 20041026154158 B20000 55 TEST ADDRESSS CITY CA956100000A20 A 20040901 20041026 20040923141317 B20000 55 TEST ADDRESSS CITY CA956100000A20 A 20040901 20041026 20040923141317 B20000 50 785 CH CA956100000A20 A 20040701 20041005 20040830143345 B20000 50 785 CH CA956100000A20 A 20040701 20041005 20040830143345 B20000 48 12123 DH CA956100000C20 C 20041002 20041005 20041005101456 B20000 48 12123 DH CA956100000C20 C 20041002 20041005 20041005101456 B20000 5 7117 DAWN VIEW CT CITRUS HEIGHTS CA956284011C20 C 20060316 20060328111055 B20000 5 7117 DAWN VIEW CT CITRUS HEIGHTS CA956284011C20 C 20060316 20060328111055 B20000 5 7117 DAWN VIEW CT CITRUS HEIGHTS CA956284011C20 C 20040901 20040910 20040907150441 B20000 5 7117 DAWN VIEW CT CITRUS HEIGHTS CA956284011C20 C 20040901 20040910 20040907150441 B20000 5 7505 SYLVAN VALLEY WAY CITRUS HEIGHTS CA956284011C20 C 20040828 20040907 20040907132818 B20000 5 7505 SYLVAN VALLEY WAY CITRUS HEIGHTS CA956284011C20 C 20040828 20040907 20040907132818 B20000 53 75 X CH CA956100000C20 C 20041001 20041005 20041005101533B20000 53 75 X CH CA956100000C20 C 20041001 20041005 20041005101533 B20000 53 75 CH CA956100000A20 A 20040401 20041005 20040901155604B20000 53 75 CH CA956100000A20 A 20040401 20041005 20040901155604 B20000 1 5555555555555ET PLACERVILLE CA956213501C20 C 20060314 20060315113330B20000 1 5555555555555ET PLACERVILLE CA956213501C20 C 20060314 20060315113330 B20000 1 555 MAIN STREET PLACERVILLE CA956213501C20 C 20060308 20060315 20060309113516B20000 1 555 MAIN STREET PLACERVILLE CA956213501C20 C 20060308 20060315 20060309113516 B20000 1 555 MAIN STREET PLACERVILLE CA956213501C20 C 20060207 20060216 20060207161221B20000 1 555 MAIN STREET PLACERVILLE CA956213501C20 C 20060207 20060216 20060207161221 B20000 1 555 MAIN STREET PLACERVILLE CA956213501C20 C 20060205 20060207 20060206131043B20000 1 555 MAIN STREET PLACERVILLE CA956213501C20 C 20060205 20060207 20060206131043 B20000 1 555 MAIN STREET PO BOX 5 PLACERVILLE CA956213501C20 C 20040830 20041207 20040901160019 B20000 1 555 MAIN STREET PO BOX 5 PLACERVILLE CA956213501C20 C 20040830 20041207 20040901160019 B20000 46 DD X CC CA956100000C20 C 20041001 20041005 20041005101738B20000 46 DD X CC CA956100000C20 C 20041001 20041005 20041005101738 B20000 51 7505 SYLVAN VALLEY WAY CITRUS HEIGHTS CA956100000A20 A 20040828 20041005 20040831153728 B20000 51 7505 SYLVAN VALLEY WAY CITRUS HEIGHTS CA956100000A20 A 20040828 20041005 20040831153728


CulpritCulprit

ADDITIONAL INFORMATIONADDITIONAL INFORMATION

G:\SYSGRP\IDMS R16 Manuals\IDMS Manuals – PDF\B01287-1EG:\SYSGRP\IDMS R16 Manuals\IDMS Manuals – PDF\B01287-1E

TSO DATASETS:TSO DATASETS: DLST.CULP.SOURCEDLST.CULP.SOURCE DLST.CULP.JCLDLST.CULP.JCL DLST.CULP.PROC DLST.CULP.PROC


SQLSQL With the SQL feature, non-SQL defined IDMS With the SQL feature, non-SQL defined IDMS

databases can be accessed using SQL DML (IDMS databases can be accessed using SQL DML (IDMS version of SQL). This is done by either using the version of SQL). This is done by either using the Online Command Facility (OCF) or the batch program Online Command Facility (OCF) or the batch program IDMSBCF. IDMSBCF.

An SQL schema is created which maps to that of the An SQL schema is created which maps to that of the non-SQL IDMS database.non-SQL IDMS database.

Records defined in the non-SQL schema can then be accessed as tables in SQL.

The following page show an example of executing a The following page show an example of executing a SELECT statement using OCF.SELECT statement using OCF.


SQLSQL


Additional Information / SourcesAdditional Information / Sources

List of manuals and file names located on G: List of manuals and file names located on G: drive at: G:\SYSGRP\IDMS R16 Manualsdrive at: G:\SYSGRP\IDMS R16 Manuals Glossary: B01251-1EGlossary: B01251-1E DML Reference – COBOL: B01247-1E DML Reference – COBOL: B01247-1E Messages and Codes – Volume 4: B01259-2EMessages and Codes – Volume 4: B01259-2E SQL Option Self-Training Guide B01274-1ESQL Option Self-Training Guide B01274-1E

G:\SYSGRP\2006 IUA WorkshopG:\SYSGRP\2006 IUA Workshop CDMMIS Schema Definition:CDMMIS Schema Definition:

DDLST.IDMS.RPTS(CV5SCHEM)LST.IDMS.RPTS(CV5SCHEM)

intro to idms

Documents

pic x30

pic x15

tchrid pic x4

studid pic x4

deptid pic x4

tchrssn pic

crseid pic x3

tchrdept pic x4