Transported Programs not generated after new SP stack

[Former Member]

Hello,

Has anyone experienced this problem? After the program was transported to the production system the changes aren't generated automatically. We have to go into the source code and manually generate the program to see the changes. This error seems to have started after the newest SP Stack was implemented.

Thanks in advance,

Lisa Matthews

[Former Member]

Transport log should have some warning message related this.

What was the status in transport log ?

[Former Member]

There wasn´t any warning. Everything finished successfully

Lisa

[Former Member]

in STMS transaction there is option of "overwrite original" I am not sure if that has any such effect.

[Former Member]

this problem is very new... it started shortly after I upgraded the SP. Which makes me believe it´s connected to the SP upgrade.

I don't use "overwrite original" do you think i should? I don´t think ""overwrite original"" will generate the program though.

Lisa

[oren_harlap]

We experienced a similar problem in October when we upgraded our ECC 6 system to stack 13. Transports with Data Dictionary objects have to be imported twice for the objects to be imported successfully and for the programs to be generated.

We opened an OSS and were told to repalce the Kernel but it didn't solve the problem.

Oren

[Former Member]

Hello All-

I know this post is old, but it describes our situation exactly. From time to time we ahve the same issue in which programs transported to prod need to be manually re-generated to catch the new version. Any ideas?