CRTBNDRPG Vs CRTPGM

[venky2903]

Helllo,

Do we have any differences between CRTBNDRPG and CRTPGM in case of file opening condition.

The initial program overriding all the file with Share(*Yes) and OPNDBF OPT(*all)
then all calling programs (created with CRTBNDRPG) using the over ride done before
but one program (CRTPGM) opened the file with *SHRRD lock. It is not using already opened file

there is no seton LR in any program

Thanks
Venkat

[B.Hauser]

Re: CRTBNDRPG Vs CRTPGM

Check the activation group of your programs are they identical or not?
Did you do the overrides with OVRSCOPE *JOB or with the default *ACTGRP?

Birgitta

[venky2903]

Re: CRTBNDRPG Vs CRTPGM

Check the activation group of your programs are they identical or not?
Did you do the overrides with OVRSCOPE *JOB or with the default *ACTGRP?

Birgitta

made the OVRDBF with default *ACTGRP
then OPNDBF OPT(*ALL)

It seems activation groups are changing- For program created with CRTPGM is QILE


and the rest programs are *Caller


So Is it the problem with activation groups. Can you explain ??

Thanks
Venkat

[venky2903]

Re: CRTBNDRPG Vs CRTPGM

made the OVRDBF with default *ACTGRP
then OPNDBF OPT(*ALL)

It seems activation groups are changing- For program created with CRTPGM is QILE
[ATTACH=CONFIG]2678[/ATTACH]

and the rest programs are *Caller
[ATTACH=CONFIG]2679[/ATTACH]

So Is it the problem with activation groups. Can you explain ??

Thanks
Venkat

All the programs/modules created with *Caller - where CL is the driver program
Please ignore the previous message
So I think all the programs using same activation group

[tomliotta]

Re: CRTBNDRPG Vs CRTPGM

All the programs/modules created with *Caller...

If that's true, then the program will not show "QILE" as its activation group attribute. Did you change it to be *CALLER after posting your earlier comment?

Or is the calling CL running in the "QILE" activation group? If so, then any programs that are either "QILE" or "*CALLER" will be okay.