Skip to main content

Discussion posted 3/28/08 by Serenity Thompson
Details:



supportadmin
Topic: ZMF Automatic demotion at Baseline (1 of 2), Read 46 times
Conf: ZMF
From: Everett Harper everett.harper@worldspan.com
Date: Thursday, April 12, 2007 08:18 AM
I am running ZMF V553, is there any way to stop the automatic demotion of packages at baseline time by CMN application? As a last resort can it be done by hardcoding each application ID in the skels?
Thanks
Everett
Topic: ZMF Automatic demotion at Baseline (2 of 2), Read 19 times
Conf: ZMF
From: Glenn Dove gdove@jasmattcorp.com
Date: Tuesday, May 15, 2007 05:54 AM
Hey Everett,
Just customize your baseline ripple process (CMNINLPM) to exclude the cleanup based on the applications you don't want the cleanup to happen for. Check the application, set a flag and then have the cleanup happen based on the flag being set to yes or no. You might even want to set up a separate skel just to check the application and set the flag and imbed that. It will keep CMNINLPM cleaner because it will only have the )SEL for the flag check.
Hope this helps.
Posted 5/30/2007 5:52 PM



ekielmeyer

Everett,
Glenn's idea will certainly work, however, If you want to give the users the choice of promotion cleanup. I created another promotion level to a stagnant library. I turned off the promotion cleanup when promoting to this level. Once the package installs CM cleans up the stagnant library. Doing it this way not every package is left in the promotion libraries.
Good Luck
Posted 6/6/2007 6:44 AM

#posta857fd1755
#oldforumpost
#ChangeManZMF

Discussion posted 3/28/08 by Serenity Thompson
Details:



supportadmin
Topic: ZMF Automatic demotion at Baseline (1 of 2), Read 46 times
Conf: ZMF
From: Everett Harper everett.harper@worldspan.com
Date: Thursday, April 12, 2007 08:18 AM
I am running ZMF V553, is there any way to stop the automatic demotion of packages at baseline time by CMN application? As a last resort can it be done by hardcoding each application ID in the skels?
Thanks
Everett
Topic: ZMF Automatic demotion at Baseline (2 of 2), Read 19 times
Conf: ZMF
From: Glenn Dove gdove@jasmattcorp.com
Date: Tuesday, May 15, 2007 05:54 AM
Hey Everett,
Just customize your baseline ripple process (CMNINLPM) to exclude the cleanup based on the applications you don't want the cleanup to happen for. Check the application, set a flag and then have the cleanup happen based on the flag being set to yes or no. You might even want to set up a separate skel just to check the application and set the flag and imbed that. It will keep CMNINLPM cleaner because it will only have the )SEL for the flag check.
Hope this helps.
Posted 5/30/2007 5:52 PM



ekielmeyer

Everett,
Glenn's idea will certainly work, however, If you want to give the users the choice of promotion cleanup. I created another promotion level to a stagnant library. I turned off the promotion cleanup when promoting to this level. Once the package installs CM cleans up the stagnant library. Doing it this way not every package is left in the promotion libraries.
Good Luck
Posted 6/6/2007 6:44 AM

#posta857fd1755
#oldforumpost
#ChangeManZMF

This is an old migrated post that has been assigned status Complete.