Unable to override a PF member

15 pts.
Tags:
CBLLE
CL
DLTOVR
OVRDBF
PF
Physical File
Hi, I am trying to override a physical file using CL. The CL program is being called by a CBLLE program. In the CBLLE program, I want to process the overridden member.But,all the processing is going on the first member only.It looks like as soon as the CL program terminates DLTOVR gets executed automatically (though i am not sure). Please let me know how to get around this problem. Any help will be highly appreciated

Answer Wiki

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

Not a cobol guy but here’s a thought – the Override must be executed before the open.

The OVRDBF must also be at a previous call level (unless you specify otherwise on the OVRDBF command).

The following will work :-

PGM
OVRDBF Youroverride details
CALL YourProgram
DLTOVR
ENDPGM

The following will NOT work

PGM
CALL Aprogram
CALL YourProgram
DLTOVR
ENDPGM

Where Aprogram runs the OVRDBF command.

When the Aprogram program completes, the OVRDBF is removed, therefore it is not in effect for YourProgram.

Regards,

Martin Gilbert.

Discuss This Question: 2  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
  • philpl1jb
    Martin Thanks, you're right for the OvrDbf might end with the call level. To get it to work as described 1. File cannot be open when it's issued 2. The COBOL program can call a CL to do the over ide -- the ovrdbf command needs the OVRSCOPE *JOB Phil
    49,960 pointsBadges:
    report
  • TomLiotta
    Alternatively, the CL program might be compiled as DFTACTGRP(*NO) ACTGRP(*CALLER) so that the override is in the same actvation group as the caller. That could avoid having the override affect other parts of the job that shouldn't see it, i.e., parts that run in a different activation group. Or the CL could be compiled only as a *MODULE. It could then be bound with the COBOL as a single *PGM object and called as a procedure. The choice would depend on how the entire job is constructed and what behavior is needed. Tom
    125,585 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