If you need source code for a certain session say tdpur4101m000, all you have to do is two steps:
1) Make a file <> 0 bytes with the name $BSE/application/tdB40U_c4_stnd/ptdpur/ppur41010
- (or your place for updates)
- (add the p for program script, add the 0 for variant 0 = original)
2) Install a solution containing the program source, this will overwrite the dummy script.

OmeLuuk,

could you explain the need for the first step? I've applied patches that have included source and the source found it's way to the patch PVRC without creating a dummy file first. Is this not always the case?

Ev

I found a patch for tibom1415m000 that inculded the source code (solution 128807). I create the file on our server, installed the patch, and the file is still empty. This patch is installed in our update VRC, and that is where the file was created.

OmeLuuk: 1) Make a file <> 0 bytes with the name $BSE/application/tdB40U_c4_stnd/ptdpur/ppur41010
- (or your place for updates)
- (add the p for program script, add the 0 for variant 0 = original)
[ve1sup3]/usr4/b40_c4/bse/application/tdB40U_c4_stnd/ptdilc> ls -altr
total 6912
-rw-rw---- 1 bsp bsp 3484 Feb 28 2001 pilc15100
-rw-rw---- 1 bsp bsp 16209 Feb 28 2001 pilc45130
-rw-rw---- 1 bsp bsp 4027 Mar 1 2001 pilc15170
-rw-rw---- 1 bsp bsp 11933 Mar 1 2001 pilc02300
-rw-rw---- 1 bsp bsp 2230 Mar 2 2001 pilc15130
-rw-rw---- 1 bsp bsp 9580 Mar 2 2001 pilc11410
-rw-rw---- 1 bsp bsp 6070 Mar 2 2001 pilc15190
-rw-rw---- 1 bsp bsp 742 Mar 3 2001 pilc55100
-rw-rw---- 1 bsp bsp 17233 Mar 4 2001 pilc02100
-rw-rw---- 1 bsp bsp 15445 Mar 6 2001 pilcdll01010
-rw-rw---- 1 bsp bsp 2473 Mar 6 2001 pilc41010
-rw-rw---- 1 bsp bsp 252 Mar 7 2001 pilc4201.bu0
-rw-rw---- 1 bsp bsp 252 Mar 7 2001 pilc4201.b.bu0
-rw-rw---- 1 bsp bsp 252 Mar 7 2001 pilc44030
-rw-rw---- 1 bsp bsp 252 Mar 7 2001 pilc15150
-rw-rw---- 1 bsp bsp 252 Mar 7 2001 pilc4204.b0
-rw-rw---- 1 bsp bsp 252 Mar 7 2001 pilc42130
...
Odd is it not? all kind of program scripts with the same small size?
[ve1sup3]/usr4/b40_c4/bse/application/tdB40U_c4_stnd/ptdilc> cat pilc42130
|*******************************************************************************
|* Dummy script - to be replaced by PMC
|* Lucas Ledelay
|* Wed Mar 7 12:00:00 2001
|*******************************************************************************
^Z

I hope not too tired yet...ltannous: I found a patch for tibom1415m000 that inculded the source code (solution 128807). I create the file on our server, installed the patch, and the file is still empty. This patch is installed in our update VRC, and that is where the file was created. You did make the file, but did you add a trailing 0 to the file name?(BSE="/usr4/b40_c4/bse")
[ve1sup3]/home/bsp> explode6.1 ptibom1415
explode6.1:
No definition in definition file for explode6.1(F_SRC:ptibom1415, ptibom1415)
First exploded '/usr4/b40_c4/bse/application/tiB40O_c4_bb1/ptibom/pbom1415' errno 2
Last exploded 'ptibom1415' errno 2
(BSE="/usr4/b40_c4/bse")
[ve1sup3]/home/bsp> explode6.1 ptibom14150
/usr4/b40_c4/bse/application/tiB40U_c4_stnd/ptibom/pbom14150Otherwise you will not be able to see it as a program script...
(BSE="/usr4/b40_c4/bse")
[ve1sup3]/home/bsp> ls -altr `explode6.1 ptibom14150`
-rw-r----- 1 bsp bsp 13118 Sep 30 15:26 /usr4/b40_c4/bse/application/tiB40U_c4_stnd/ptibom/pbom14150
(BSE="/usr4/b40_c4/bse")
[ve1sup3]/home/bsp> head -5 `explode6.1 ptibom14150`
|***********************************************************************
|* bom1415 Print Where-Used PBOM Components (summarized)
|* MFG group
|* 1994 Jan
|* This source has been cleaned for reasons of readability (Baan IV)Should do. The solution was installed on sept 30th and it contained and updated the script...

I split this thread per OmeLuuks request. The other piece of this post is here (http://www.baanboard.com/baanboard/showthread.php?s=&threadid=7415). Hope I got it right this time.

Mark

When I installed the solution again, it deleted the file i created on the server??

I have read that the latest version of PMC (or maybe any version of PMC) will only install the source of a solution if the source is already present. Maybe this thread was a solution to this ???

I do not use PMC and I can "see" the source for all installed solutions (I do not have the original sources)

Thanks, Nick.

That answers my earlier question... the source that is currently on our system must be from solution installs prior to pmc. Now I understand the need for the dummy file.

Ev

nick_rogers: Maybe this thread was a solution to this ???This thread is a documented (see booklet delivered with SP's) work around to obtain these sources nevertheless.

If I understand right, there is still no solution, why, in certain cases a present source in the update VRC is not updatet with installation of a SP or a "solution"?

Spartacus

imho, they are always updated, but I never checked...
One time I created p files for all of my o files, but still I have a lot of objects where I still have the old dummy script...

I am not good in scripting, but it is possible to write a script telling what o-files with a similar code as the p-files that have a specific file size (because it is the same dummy script, in my case 252 bytes) are on the system where the date of the o-file is later than the date of the p-file...

what do you mean with "they are always updated, but never checked..." .... the "p" or the "o" files?

Once more for my understanding:

During installation of a SP or solution, Baan updates a lot of "o-files" (objects). But threre are also a lot of this "dummy-scripts" untouched. According to a normal behaviour, source files (our dummy scripts) in the update VRC should be replaced in case, if the related object is also replaced. But this, obviously don't happen all the time.

Spartacus

I never checked the "p" files when a script/object is installed (the o file).spartacus: According to a normal behaviour, source files (our dummy scripts) in the update VRC should be replaced in case, if the related object is also replaced. But this, obviously don't happen all the time.In case the object has to be rebuild because a function (include) is modified, the objects may be delivered without a new program script. In those cases the include files should be delivered (and (dummy) scripts there should be overwritten with newer versions).

It may well be that Baan decided to make installation of souces conditional... (developers license y/n) that I do not know.