Skip to main content

How do you have the same library for baseline and production?

  • June 13, 2013
  • 6 replies
  • 0 views
D

I wonder if anyone has any experience of using the same library for both Baseline and Production? The manual recommends this as a valid scenario in certain circumstances, but doesn’t expand upon how precisely it is accomplished –

"If your production applications run at the same site as your baseline libraries, you may not need to set up separate ChangeMan ZMF production libraries. Remember, ChangeMan ZMF baseline libraries can be standard PDSs and can be accessed by external tasks. Eliminating ChangeMan ZMF production libraries where possible could result in significant DASD savings."

The obvious answer would be to set up your baseline level (0) library to be your production library. Whilst this works to an extent, it doesn’t do the Baseline Ripple, as this process compares the staging library to baseline after installation in to production. As baseline is production in this case, there are no differences and hence no baseline ripple. Thus is it not possible to book out earlier versions of code.

The other option I can see is to set the “Install in Prod” flag to N when configuring your baseline libraries. In this case the baseline ripple is performed, but since you’re not installing in to production there is no copy of the old production code to the production backup library. Thus the only option for a backout is to rely on a reverse baseline ripple. I’d be more comfortable with usable code in it’s own PDS which can be manually copied back or pointed to with a JCLLIB, etc.

Does anyone have any thoughts on this?

#Baseline
#ChangeManZMF
#Production

    6 replies

    D
    • Dominique SacreRocketeer
    • Author
    • Rocketeer
    • 19312 replies
    • June 13, 2013

    I wonder if anyone has any experience of using the same library for both Baseline and Production? The manual recommends this as a valid scenario in certain circumstances, but doesn’t expand upon how precisely it is accomplished –

    "If your production applications run at the same site as your baseline libraries, you may not need to set up separate ChangeMan ZMF production libraries. Remember, ChangeMan ZMF baseline libraries can be standard PDSs and can be accessed by external tasks. Eliminating ChangeMan ZMF production libraries where possible could result in significant DASD savings."

    The obvious answer would be to set up your baseline level (0) library to be your production library. Whilst this works to an extent, it doesn’t do the Baseline Ripple, as this process compares the staging library to baseline after installation in to production. As baseline is production in this case, there are no differences and hence no baseline ripple. Thus is it not possible to book out earlier versions of code.

    The other option I can see is to set the “Install in Prod” flag to N when configuring your baseline libraries. In this case the baseline ripple is performed, but since you’re not installing in to production there is no copy of the old production code to the production backup library. Thus the only option for a backout is to rely on a reverse baseline ripple. I’d be more comfortable with usable code in it’s own PDS which can be manually copied back or pointed to with a JCLLIB, etc.

    Does anyone have any thoughts on this?

    #Baseline
    #ChangeManZMF
    #Production

    Hi David,

    You should *not* use the same dataset for production, that you have defined for baseline. I would suggest that you open a Support ticket with Serena, to discuss this issue with a Support Engineer.

    Thanks,

    David Hadden

    Serena Support
    D
    • Dominique SacreRocketeer
    • Author
    • Rocketeer
    • 19312 replies
    • June 13, 2013

    I wonder if anyone has any experience of using the same library for both Baseline and Production? The manual recommends this as a valid scenario in certain circumstances, but doesn’t expand upon how precisely it is accomplished –

    "If your production applications run at the same site as your baseline libraries, you may not need to set up separate ChangeMan ZMF production libraries. Remember, ChangeMan ZMF baseline libraries can be standard PDSs and can be accessed by external tasks. Eliminating ChangeMan ZMF production libraries where possible could result in significant DASD savings."

    The obvious answer would be to set up your baseline level (0) library to be your production library. Whilst this works to an extent, it doesn’t do the Baseline Ripple, as this process compares the staging library to baseline after installation in to production. As baseline is production in this case, there are no differences and hence no baseline ripple. Thus is it not possible to book out earlier versions of code.

    The other option I can see is to set the “Install in Prod” flag to N when configuring your baseline libraries. In this case the baseline ripple is performed, but since you’re not installing in to production there is no copy of the old production code to the production backup library. Thus the only option for a backout is to rely on a reverse baseline ripple. I’d be more comfortable with usable code in it’s own PDS which can be manually copied back or pointed to with a JCLLIB, etc.

    Does anyone have any thoughts on this?

    #Baseline
    #ChangeManZMF
    #Production

    Hi Dave,

    Thanks for the info. But I'm slightly confused as that contradicts what the manual says. Is the manual wrong or have I misinterpreted something?

    Thanks

    David
    D
    • Dominique SacreRocketeer
    • Author
    • Rocketeer
    • 19312 replies
    • June 13, 2013

    I wonder if anyone has any experience of using the same library for both Baseline and Production? The manual recommends this as a valid scenario in certain circumstances, but doesn’t expand upon how precisely it is accomplished –

    "If your production applications run at the same site as your baseline libraries, you may not need to set up separate ChangeMan ZMF production libraries. Remember, ChangeMan ZMF baseline libraries can be standard PDSs and can be accessed by external tasks. Eliminating ChangeMan ZMF production libraries where possible could result in significant DASD savings."

    The obvious answer would be to set up your baseline level (0) library to be your production library. Whilst this works to an extent, it doesn’t do the Baseline Ripple, as this process compares the staging library to baseline after installation in to production. As baseline is production in this case, there are no differences and hence no baseline ripple. Thus is it not possible to book out earlier versions of code.

    The other option I can see is to set the “Install in Prod” flag to N when configuring your baseline libraries. In this case the baseline ripple is performed, but since you’re not installing in to production there is no copy of the old production code to the production backup library. Thus the only option for a backout is to rely on a reverse baseline ripple. I’d be more comfortable with usable code in it’s own PDS which can be manually copied back or pointed to with a JCLLIB, etc.

    Does anyone have any thoughts on this?

    #Baseline
    #ChangeManZMF
    #Production

    Hi David,

    I believe you are misinterpreting the documentation. The section you quoted is really meant to indicate that 'production' libraries are not 'needed' if the baseline DASD is accessible from where the code needs to execute. You can simply execute from the baseline and not have to duplicate the data.

    Thanks,

    David Hadden

    Serena Support
    D
    • Dominique SacreRocketeer
    • Author
    • Rocketeer
    • 19312 replies
    • June 13, 2013

    I wonder if anyone has any experience of using the same library for both Baseline and Production? The manual recommends this as a valid scenario in certain circumstances, but doesn’t expand upon how precisely it is accomplished –

    "If your production applications run at the same site as your baseline libraries, you may not need to set up separate ChangeMan ZMF production libraries. Remember, ChangeMan ZMF baseline libraries can be standard PDSs and can be accessed by external tasks. Eliminating ChangeMan ZMF production libraries where possible could result in significant DASD savings."

    The obvious answer would be to set up your baseline level (0) library to be your production library. Whilst this works to an extent, it doesn’t do the Baseline Ripple, as this process compares the staging library to baseline after installation in to production. As baseline is production in this case, there are no differences and hence no baseline ripple. Thus is it not possible to book out earlier versions of code.

    The other option I can see is to set the “Install in Prod” flag to N when configuring your baseline libraries. In this case the baseline ripple is performed, but since you’re not installing in to production there is no copy of the old production code to the production backup library. Thus the only option for a backout is to rely on a reverse baseline ripple. I’d be more comfortable with usable code in it’s own PDS which can be manually copied back or pointed to with a JCLLIB, etc.

    Does anyone have any thoughts on this?

    #Baseline
    #ChangeManZMF
    #Production

    Hi David,

    But that's exactly what I want to do. Sorry if I didn't explain myself very well, but I do want to execute from the baseline library.

    So how do I set that up? With the proviso that I also want to do a baseline ripple and have a backup of the code somewhere that is usable, i.e.; doesn't rely on a reverse baseline ripple to recreate it.

    Many thanks.
    D
    • Dominique SacreRocketeer
    • Author
    • Rocketeer
    • 19312 replies
    • June 14, 2013

    I wonder if anyone has any experience of using the same library for both Baseline and Production? The manual recommends this as a valid scenario in certain circumstances, but doesn’t expand upon how precisely it is accomplished –

    "If your production applications run at the same site as your baseline libraries, you may not need to set up separate ChangeMan ZMF production libraries. Remember, ChangeMan ZMF baseline libraries can be standard PDSs and can be accessed by external tasks. Eliminating ChangeMan ZMF production libraries where possible could result in significant DASD savings."

    The obvious answer would be to set up your baseline level (0) library to be your production library. Whilst this works to an extent, it doesn’t do the Baseline Ripple, as this process compares the staging library to baseline after installation in to production. As baseline is production in this case, there are no differences and hence no baseline ripple. Thus is it not possible to book out earlier versions of code.

    The other option I can see is to set the “Install in Prod” flag to N when configuring your baseline libraries. In this case the baseline ripple is performed, but since you’re not installing in to production there is no copy of the old production code to the production backup library. Thus the only option for a backout is to rely on a reverse baseline ripple. I’d be more comfortable with usable code in it’s own PDS which can be manually copied back or pointed to with a JCLLIB, etc.

    Does anyone have any thoughts on this?

    #Baseline
    #ChangeManZMF
    #Production

    Hi David,

    You should open a ticket with Support, to facilitate this discussion

    Thanks,

    David Hadden

    Serena Support
    D
    • Dominique SacreRocketeer
    • Author
    • Rocketeer
    • 19312 replies
    • June 14, 2013

    I wonder if anyone has any experience of using the same library for both Baseline and Production? The manual recommends this as a valid scenario in certain circumstances, but doesn’t expand upon how precisely it is accomplished –

    "If your production applications run at the same site as your baseline libraries, you may not need to set up separate ChangeMan ZMF production libraries. Remember, ChangeMan ZMF baseline libraries can be standard PDSs and can be accessed by external tasks. Eliminating ChangeMan ZMF production libraries where possible could result in significant DASD savings."

    The obvious answer would be to set up your baseline level (0) library to be your production library. Whilst this works to an extent, it doesn’t do the Baseline Ripple, as this process compares the staging library to baseline after installation in to production. As baseline is production in this case, there are no differences and hence no baseline ripple. Thus is it not possible to book out earlier versions of code.

    The other option I can see is to set the “Install in Prod” flag to N when configuring your baseline libraries. In this case the baseline ripple is performed, but since you’re not installing in to production there is no copy of the old production code to the production backup library. Thus the only option for a backout is to rely on a reverse baseline ripple. I’d be more comfortable with usable code in it’s own PDS which can be manually copied back or pointed to with a JCLLIB, etc.

    Does anyone have any thoughts on this?

    #Baseline
    #ChangeManZMF
    #Production

    OK, thanks for your help David, I will do.


    Terms & ConditionsAccessibility statement