What is Open Data path in OVRDBF?

185 pts.
Tags:
CL programming
CLP
Open Data Path
OVRDBF
What is meaning of Share(*yes) In Ovrdbf?

Answer Wiki

Thanks. We'll let you know when a new response is added.

that file will be used, shared by subsequent programs within the scope of the override.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    The Open Data Path (ODP) is the set of structures built in memory by the operating system when you open a file. It contains pointers to all of the operating system routines that are valid for the file. It also contains the buffers used to transfer records (or blocks of records) between your program and the file. Other related elements are included. For example, there will be a pointer to the system routine that writes records to database files. If the file was opened to a printer file, the pointer in that part of the ODP would point to the routine that outputs to a printer. Everything related to the type of device is linked to through the ODP. When you apply an override, the job applies it to the ODP that is created when the file is opened. The library name might be changed. The file name might be changed. Device attributes might be changed. Even the device type might be changed. Every program within the scope of the ODP will see the same changes. When an ODP is shared, the scope of the ODP grows. Multiple programs will be connected to the same set of data structures. That includes record buffers, device attributes, whatever was used to build the ODP. Since the record buffers are shared, if program A reads a record from the file and calls program B, then if program B opens the same file and reads a record, it will get the second record in the file. Program B can end and return to program A. If program A then reads another record, it will get the third record in the file even though program A has only issued two reads. In short, the ODP is what gets built in memory to connect a program to a file. Tom
    125,585 pointsBadges:
    report
  • philpl1jb
    Absolutely wonderful explaination Tom, as usual. ...connect a job to a file I think the last line should read job instead of program. Phil
    49,590 pointsBadges:
    report
  • TomLiotta
    …connect a job to a file I think the last line should read job instead of program. In light of the question about "SHARE(*YES)", that might be a worthwhile way to think of it. Programs connect to files through ODPs, but the ODPs can be accessed by multiple programs in the same job. When shared, they are reasonably thought of at the job or activation group level. Tom
    125,585 pointsBadges:
    report
  • habeel
    It means that if the member is opened more than once then the same open data path is shared with each program in the job.
    10 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following